Abstract: A system described herein may identify a chaincode record recorded to a blockchain, and may output chaincode discovery information to a chaincode discovery system. A client device may receive the chaincode discovery information from the chaincode discovery system, and may output a request to invoke the chaincode. The system may obtain verification, from the chaincode discovery system, that the client device is authorized to invoke the chaincode, and may instruct a node that maintains the blockchain to execute the chaincode. The system may receive output values resulting from executing the chaincode and may output, to the client device, the output values resulting from executing the chaincode.

Abstract: A system described herein may receive a cross-ledger recordation request that includes an information payload, an indication of a target distributed ledger to which the information payload should be recorded, and an indication of a second distributed ledger to which a reference that refers to the first distributed ledger should be recorded. The system may provide the information payload to a second system that implements the first distributed ledger. The system may determine that at least a portion of the information payload has been recorded to the first distributed ledger based on providing the information payload to the second system that implements the first distributed ledger. Based on determining that at least the portion of the information payload has been recorded to the second distributed ledger, the system may record the reference, that refers to the first distributed ledger, to the second distributed ledger.

Abstract: A system may receive a request to migrate a first distributed ledger, maintained by a first distributed ledger management system, to a second distributed ledger management system, and may generate first verification information based on information recorded to the first distributed ledger. The system may instruct the second distributed ledger management system to establish a second distributed ledger, such that the second distributed ledger management system maintains the second distributed ledger. The system may also instruct the second distributed ledger management system to record the information, recorded to the first distributed ledger, to the second distributed ledger. The system may generate second verification information based on the information recorded to the second distributed ledger, and verify that the first distributed ledger has been migrated to the second distributed ledger management system by comparing the first verification information to the second verification information.

Abstract: A system described herein may utilize artificial intelligence/machine learning (“AI/ML”) or other suitable techniques to automatically identify blocks added to or proposed to be added to a blockchain, with conflicting and/or otherwise incompatible information, and to automatically remediate the blockchain based on the identified conflict and/or incompatibility. The model may associate different types of conflicts and/or incompatibilities with different types of remedial measures. The remedial measures may include the rejection of a proposed block, recording a new block that takes precedence or priority over a previously recorded block, or other suitable remedial measures.

Abstract: A system described herein may receive a distributed ledger creation request that specifies a quantity of nodes. The system may provision a plurality of sets of hardware resources to implement a set of nodes which includes the requested quantity of nodes. Provisioning the plurality of sets of hardware resources may include generating communication information associated with each node of the set of nodes. The system may instruct at least one node, of the set of nodes, to establish a distributed ledger. The at least one node may communicate with one or more other nodes of the set of nodes to establish the distributed ledger. The system may output, in response to the distributed ledger creation request, communication information associated with one or more nodes of the plurality of nodes. The communication information may be used to interact with the established distributed ledger.

Abstract: A system described herein may receive a proposed interaction with a distributed ledger, including a reference to a value that has been previously recorded to the distributed ledger. The system may attempt to obtain the value from an associated cache. If the value is unable to be obtained from the cache, the system may communication with an external device via a network to obtain the value. The system may execute the proposed interaction based on the obtained first value. The system may receive a finalized block based on the executed interaction, and may update the cache based on one or more values included in the finalized block.

Abstract: A system described herein may generate a group of distributed ledgers that are each associated with a respective set of ledger parameters, receive a data item that is associated with a set of attributes, identify a distributed ledger that is associated with ledger parameters that meet the set of attributes, and record the data item to the distributed ledger that is associated with ledger parameters that meet the particular set of attributes. The system may determine that a set of archival parameters, associated with a particular distributed ledger, have been met; and may remove the particular distributed ledger from the group of distributed ledgers based on determining that the set of archival parameters, associated with the particular distributed ledger, have been met. Nodes that maintain the group of distributed ledgers may remove ledger data, associated with the removed distributed ledger, from one or more storage resources associated with the nodes.

Abstract: A system described herein may receive a proposed interaction with a distributed ledger, including a reference to a value that has been previously recorded to the distributed ledger. The system may attempt to obtain the value from an associated cache. If the value is unable to be obtained from the cache, the system may communication with an external device via a network to obtain the value. The system may execute the proposed interaction based on the obtained first value. The system may receive a finalized block based on the executed interaction, and may update the cache based on one or more values included in the finalized block.

Abstract: A system described herein may generate a group of distributed ledgers that are each associated with a respective set of ledger parameters, receive a data item that is associated with a set of attributes, identify a distributed ledger that is associated with ledger parameters that meet the set of attributes, and record the data item to the distributed ledger that is associated with ledger parameters that meet the particular set of attributes. The system may determine that a set of archival parameters, associated with a particular distributed ledger, have been met; and may remove the particular distributed ledger from the group of distributed ledgers based on determining that the set of archival parameters, associated with the particular distributed ledger, have been met. Nodes that maintain the group of distributed ledgers may remove ledger data, associated with the removed distributed ledger, from one or more storage resources associated with the nodes.

Abstract: A system described herein may generate a hash value based on a set of data stored in an off-chain repository. The system may record an association between the set of data and the hash value to a blockchain system, receive a query from a client device, determine that the query is associated with the set of data, output a response to the query based on the set of data. The response may include the hash value. The system may authenticate the query (e.g., the client device) using one or more suitable authentication mechanisms, thus securing access to the set of data. The client device may verify the set of data based on determining that the hash value included in the response matches the hash value recorded to the blockchain system as being associated with the set of data.

Abstract: A system described herein may utilize artificial intelligence/machine learning (“AI/ML”) or other suitable techniques to automatically identify blocks added to or proposed to be added to a blockchain, with conflicting and/or otherwise incompatible information, and to automatically remediate the blockchain based on the identified conflict and/or incompatibility. The model may associate different types of conflicts and/or incompatibilities with different types of remedial measures. The remedial measures may include the rejection of a proposed block, recording a new block that takes precedence or priority over a previously recorded block, or other suitable remedial measures.