Abstract: A distributed ledger technology (DLT) network may include a plurality of participant nodes. The participant nodes may respectively validate a distributed ledger based on a consensus protocol. A blockchain export system may send, to a data receiver not included in the DLT network, a participant public key for a participant node of the DLT network. The blockchain export system may receive, from the data receiver, a request to share token data stored in a blockchain of the distributed ledger. The blockchain export system may generate a certification that the token data is stored on the blockchain. The certification may include a digital signature based on a participant private key paired to the participant public key. The blockchain system may transmit the certification to the data receiver. The data receiver may verify the certification based on the participant public key.

Abstract: A method for anonymously communicating data that defines a token from a source system to a destination system via a block-chain distributed database includes receiving, at a token distribution system, request information from a source system. The request information specifies source identifying information and an address for receiving one or more tokens. The token distribution system determines one or more tokens for allocation to the source system and communicates the allocated tokens to the address defined in the request information via a zero-knowledge transaction. The source system moves the tokens to a different address for communicating a block-chain transaction and communicates the tokens at the different address to a destination address associated with the destination system via a block-chain transaction.

Abstract: A master oracle may receive an oracle network identifier for an oracle network. The master oracle may receive a plurality of data messages respectively generated by the oracles. The master oracle may verify, based on respective public keys for the oracles, that each of the data messages are digitally signed by a different corresponding one of the oracles. The master oracle may aggregate the data messages into an aggregated data message. The master oracle may digitally sign the aggregated data message with a private key and public key pair. The master oracle may transmit the aggregated data message to a participant node of a distributed ledger network. A smart contract stored on a blockchain may verify the aggregated data. After receiving and verifying the aggregated data message the smart contract may execute to perform operations based on the aggregated data message.

Abstract: Systems and methods for active state synchronization between distributed ledger technology (DLT) platforms are provided. A system may store an origin blockchain compliant with an origin DLT. The system may further store a target blockchain compliant with a target DLT. The target DLT may be different from the origin DLT. The system may include a DLT object synchronizer with access to the origin blockchain and the target blockchain. The DLT object synchronizer may receive, from an exchange node, a request to synchronize an origin instance of a DLT object between the origin blockchain and the target blockchain. The DLT object synchronizer may select a target instance of the DLT object on the target blockchain. The DLT object synchronizer may format origin data from the origin instance for compliance with the target DLT. The DLT object synchronizer may synchronize the origin instance and the target instance.

Abstract: A system supports asset transfers among blockchains of differing distributed ledger technologies using interop circuitry. The interop circuitry may receive asset permissions from origin and target participant circuitry. The asset permissions may support transfer of an asset from an origin blockchain to a target blockchain. The interop circuitry, acting on behalf of the origin and target participant circuitry, locks an asset on the origin blockchain. Then the interop circuitry creates the asset on the target blockchain. The locking of the asset on the origin blockchain may prevent a double-expend opportunity, where the asset can be redeemed on the origin blockchain and on the target blockchain.

Abstract: For shielded cryptographic data exchange interoperation, an interoperability node is in communication with a furnisher participant node of a furnisher distributed ledger technology (DLT) network and a receiver participant node of a receiver DLT network. The interoperability node may obtain a shielded exchange instruction. The shielded exchange instruction may include a zero-knowledge proof, a selected token nullifier, a new token nullifier, and a new token digest. The zero-knowledge proof may be indicative of the furnisher participant having access to the selected token identifier. When the interoperability node determines that the new token nullifier is not present on a receiver blockchain, the interoperability node may submit the shielded exchange instruction to a furnisher smart contract and a receiver smart contract. The furnisher smart contract may retire the selected token nullifier on the furnisher blockchain.

Abstract: A system supports asset transfers among blockchains of differing distributed ledger technologies using interop circuitry. The interop circuitry may receive asset permissions from origin and target participant circuitry. The asset permissions may support transfer of an asset from an origin blockchain to a target blockchain. The interop circuitry, acting on behalf of the origin and target participant circuitry, locks an asset on the origin blockchain. Then the interop circuitry creates the asset on the target blockchain. The locking of the asset on the origin blockchain may prevent a double-expend opportunity, where the asset can be redeemed on the origin blockchain and on the target blockchain.

Abstract: Systems and methods for cryptologic blockchain interoperability are provided. A furnisher participant of a furnisher DLT network may receive a request to export or share token data stored on a furnisher blockchain that stores the token data based on a furnisher DLT. The furnisher participant may transmit, to a plurality of validator participants of the furnisher DLT network, a consensus request to certify the token data is stored on a furnisher blockchain. The furnisher participant may receive certifications that the token data is stored on the furnisher blockchain. The certifications may include digital signatures respectively signed by the validator participants. The furnisher participant may generate a multi-signature certification message. The furnisher participant may communicate the multi-signature certification message to the data receiver. The data receiver may verify the digital signatures based on public keys of the validator participants of the furnisher DLT network.

Abstract: A data furnisher may append, to a furnisher blockchain, an interoperability smart contract comprising a cryptologic committal. The cryptologic committal may include logic configured to cause a data receiver to commit token data to the receiver blockchain based on a pre-commit authorization. The data furnisher may encrypt, based on a committal key, a pre-commit authorization to transfer token data stored on the furnisher blockchain to the receiver blockchain. The data furnisher may transmit the pre-commit authorization to the data receiver. After transmission of the pre-commit authorization, the data furnisher may receive a pre-commit acknowledgement of the pre-commit authorization. The data furnisher may lock the token data on the furnisher blockchain in response to verification that the token data is appended to the data receiver blockchain. The data furnisher may send the predetermined committal key to the data receiver to commit the token data to the data receiver blockchain.

Abstract: This document generally describes systems, methods, devices, and other techniques for using distributed ledgers, such as a blockchain database, to facilitate secure distribution and use of 3D model files to 3D printers over a computing network. A 3D printer controller may access an electronic ledger that identifies a plurality of 3D model files that have been made available for distribution. A particular 3D model file and a secret key may be obtained by the printer, where the 3D model file is encrypted based on the secret key. The secret key can be decrypted using a private key associated with the computing device that corresponds to the public key. After decrypting the secret key, the particular 3D model file can be decrypted using the secret key, and after decrypting the particular 3D model file, the particular 3D model file can be executed on the printer to print a physical 3D object.

Abstract: This document generally describes techniques for using a distributed ledger to implement a framework for the validation and distribution of virus signatures, which may be used by antivirus engines on computing devices to detect and remove malware. Some implementations can include accessing, by a computing system, data that identifies a plurality of virus signatures. A signature score associated with a first virus signature can be identified that is determined based on a number of signature authorities that have submitted or endorsed the first virus signature. The computing system may determine whether the first virus signature is valid based on whether the signature score satisfies a threshold score. In response to determining that the first virus signature is valid, the first virus signature can be used by the computing system to perform virus scans of one or more files maintained by the computing system.

Abstract: A method for anonymously communicating data that defines a token from a source system to a destination system via a block-chain distributed database includes receiving, at a token distribution system, request information from a source system. The request information specifies source identifying information and an address for receiving one or more tokens. The token distribution system determines one or more tokens for allocation to the source system and communicates the allocated tokens to the address defined in the request information via a zero-knowledge transaction. The source system moves the tokens to a different address for communicating a block-chain transaction and communicates the tokens at the different address to a destination address associated with the destination system via a block-chain transaction.

Abstract: This document describes systems, methods, devices, and other techniques for managing healthcare records. In some implementations, a computing system is provided that includes an electronic ledger, a first program module, and a second program module. The electronic ledger can store entries of medical record management events invoked by participants in a distributed computing network. The first program module can be assigned to an account of a first user on the distributed computing network and can identify (i) medical records of the first user and (ii) accounts of users other than the first user that are authorized to access the medical records of the first user. The second program module can be assigned to an account of a second user on the distributed computing network and can call the first program module to request access to a set of one or more of the medical records of the first user.

Abstract: This document generally describes systems, methods, devices, and other techniques for using distributed ledgers, such as a blockchain database, to facilitate secure distribution and use of 3D model files to 3D printers over a computing network. A 3D printer controller may access an electronic ledger that identifies a plurality of 3D model files that have been made available for distribution. A particular 3D model file and a secret key may be obtained by the printer, where the 3D model file is encrypted based on the secret key. The secret key can be decrypted using a private key associated with the computing device that corresponds to the public key. After decrypting the secret key, the particular 3D model file can be decrypted using the secret key, and after decrypting the particular 3D model file, the particular 3D model file can be executed on the printer to print a physical 3D object.

Abstract: This document generally describes techniques for using a distributed ledger to implement a framework for the validation and distribution of virus signatures, which may be used by antivirus engines on computing devices to detect and remove malware. Some implementations can include accessing, by a computing system, data that identifies a plurality of virus signatures. A signature score associated with a first virus signature can be identified that is determined based on a number of signature authorities that have submitted or endorsed the first virus signature. The computing system may determine whether the first virus signature is valid based on whether the signature score satisfies a threshold score. In response to determining that the first virus signature is valid, the first virus signature can be used by the computing system to perform virus scans of one or more files maintained by the computing system.

Abstract: A commodity-measuring device for autonomously selecting a commodity supplier among a plurality of commodity suppliers being specified within a blockchain distributed database is provided. A microcontroller unit is configured to provide commodity consumption data to the transaction manager. A storage is configured to store a private key, and a communication module is configured to retrieve a commodity supplier file stored in the blockchain distributed database, and the commodity supplier file includes parameters of a commodity supplier and a program. A transaction manager is configured to determine autonomously, based on the commodity consumption data and parameters in the commodity supplier file, whether to select the commodity supplier; and if the determination is positive, the transaction manager is configured to, using the private key, send a transaction to the blockchain distributed database calling a function in the program to associate the commodity supplier file with the identifier.