Splunk Inc.

Cisco Technology, Inc.

Ryan Russell Moore

Nathaniel Gerard McKervey

Stephen Robert Luedtke

Jeffrey Yung Wu

Antoine Toulme

Siegfried Puchbauer

Christopher Yan-Loon Chan

Matthew Buckle

Kelly Kong

Benjamin D Dearinger

Casing Chu

Melanie Marsollier

Himanshu Goyal

Systems and methods are described to correlate different types of data obtained from a distributed ledger system. The distributed ledger system can generate transaction notifications, log data, and/or metrics data. At least some of the data generated by the distributed ledger system can be obtained by a data intake and query system via a distributed ledger system monitor. The data from the distributed ledger system can be stored in the data intake and query system and correlated. Based on the correlation, the data intake and query system can determine a history of a transaction in the distributed ledger system, relationships between components of the distributed ledger system, and/or an architecture of the distributed ledger system.

Correlating different types of data of a distributed ledger system

Systems and methods for ingesting data from distributed ledger systems. To ingest data from the distributed ledger systems, all or a portion of the distributed ledger systems can be assigned a connector. One or more connectors can be initialized for a particular distributed ledger system. For example, the data intake and query system can include a first connector that is initialized for a first distributed ledger system and a second connector that is initialized for a second distributed ledger system. The connectors can be initiated with processing schema that can indicate how the connectors ingest, enrich, filter, etc. data from the distributed ledger systems. All or a portion of the connectors can be initiated with different processing schemas. The connectors can obtain data from nodes of the distributed ledger systems according to the processing schemas and route the data to the data intake and query system.

Versioned connectors for data ingestion from distributed ledger systems

Token minting environment includes a physical token minter that is accessible to a group of users. A user initiates a session to mint a non-fungible token associated with an image that the physical token minter generates. When the session is established, the physical token minter connects with a digital wallet associated with the user. The physical token minter identifies a physical interaction provided by the user, such as the user pulling a lever or pressing an input button that is proximate to the physical token minter. Upon identifying the user interaction, the physical token minter responds by triggering the creation of an image and the minting of a non-fungible token that links the image to the wallet of the user. The physical token minter then provides a digital representation of the image and an indication that a token for the image has been added to the digital wallet.

Physical device for real-time minting of non-fungible tokens

Systems and methods are disclosed for authenticating a chunk of data identified in a query received by a data intake and query system. The data intake and query system receives a query that identifies a set of data and manner for processing the set of data, and identifies a chunk of data that is part of the set of data. The system generates a content identifier, such as a hash, of the chunk of data. The system further authenticates the chunk of data based on the generated content identifier and a content identifier stored by a distributed ledger system.

Authenticating data associated with a data intake and query system using a distributed ledger system

Systems and methods for decoding distributed ledger transactions by data intake and query systems. An example method includes: receiving a transaction of a distributed ledger, wherein the transaction includes transaction data and an identifier of an account of the distributed ledger; receiving a bytecode module, wherein the bytecode module is associated with the account of the distributed ledger; computing a bytecode digital fingerprint associated with the bytecode module; identifying, among a plurality of stored application binary interface (ABI) definitions, an ABI definition having an ABI digital fingerprint that matches the bytecode digital fingerprint; and producing decoded transaction data by decoding, using the identified ABI definition, the transaction data.

Decoding distributed ledger transaction records

Apparatus and methods are disclosed for storing, transporting, grinding, and/or dispensing/pouring herbs and/or similar materials and things. A compressing/urging plate/platform is disclosed, which can selectively move the herbs or other materials toward a grinding assembly, and the ground material can be captured on the other side of the grinding assembly, for subsequent dispense and/or use. The inventions can reduce and simplify the steps and the overall apparatus needed to accomplish transportation, storage, consumption, and/or use of herb-like materials and things.

Apparatus and methods for storing, transporting, and/or grinding herbs and/or similar things

A blockchain consortium network can be implemented in which nodes of one or more blockchains generate data for pipeline-based processing by a consortium pipeline system. The generated data can include private blockchain data, public blockchain data, and machine data, such as logs or operational metrics from the nodes. The data is collected from different network levels and can be transformed via pipeline processes of the consortium pipeline system to securely share data in the blockchain consortium network.

Securely sharing public and private blockchain data

Systems and methods are described to associate data from different nodes of a distributed ledger system. The nodes can generate transaction notifications, log data, and/or metrics data. At least some of the data generated by the nodes can be obtained by a data intake and query system via a distributed ledger system monitor. The data from the distributed ledger system can be stored in the data intake and query system and correlated. Based on an association between at least some of the data of the first node and at least some of the data of the second node, the data intake and query system can determine at least a partial history of a transaction in the distributed ledger system, relationships between components of the distributed ledger system, and/or an architecture of the distributed ledger system.

Growing community of inventors

St. Augustine, FL, United States of America

Ryan Russell Moore