Abstract: The processor may collect, from a first peer, a first data set associated with a channel. The channel may include one or more assets associated with a first peer. The channel may link the first peer to a second peer. The processor may analyze the first data set to determine a first status for the one or more assets. The processor may provide the first status of the one or more assets in a viewable channel to the blockchain network.

Abstract: A processor may define an available resource set in the blockchain network. The available resource set may be the one or more peers. The processor may collect one or more metrics associated with the one or more peers in the blockchain network. The processor may analyze the one or more metrics and may identify a first workload level for the one or more peers. The processor may determine an optimal status for a first particular peer of the one or more peers, based in part on the available resource set and the first workload level. The processor may compare the optimal status to a current status of the first particular peer. The processor may determine if the optimal status and the current status are different. The processor may execute a status change of the first particular peer from the current status to the optimal status.

Abstract: A processor may register one or more verifiable asset credential schemas. A verifiable asset credential schema may prescribe the format and content of asserting blockchain-backed asset state. The processor may register an issuer policy for the verifiable asset credentials. The issuer policy may be associated with a schema and intended credential holder(s). The processor may subscribe the asset credential issuer to one or more peers on the blockchain. The processor may issue commit notifications to a subscribing asset credential issuer in the form of schema-compliant committing-peer verifiable credentials. The processor may collect the committing-peer verifiable credentials from one or more peers. The processor may validate the committing-peer verifiable credentials satisfy the security policy and schema for a designated intended credential holder. The processor may issue a schema-compliant verifiable asset credential to the policy-designated credential holder(s).

Abstract: A computer-implemented system and related method address malfunctioning peers in a blockchain, the method comprising receiving endorsement results from peers in the blockchain, where the endorsement results are for one or more transactions in the blockchain. The endorsement results include successful and failed endorsements. The method further comprises distributing the successful and failed endorsements to two or more endorsement collectors, determining which peers are successful endorsement peers (SEPs) that provided successful endorsements, and which peers are failed endorsement peers (FEPs) that provided failed endorsements. A reputation score is calculated for each peer based on endorsement information from the endorsement collectors. The reputation score is then sent to at least one of a client and a system administrator. This reputation score is then used to determine peer selection in a subsequent transaction.

Abstract: A processor may incorporate one or more keys in a media. The one or more keys may each be associated with a specific instance and the one or more keys may be included in a blockchain. The processor may identify that a first specific instance has been encountered. The processor may provide a first key associated with the first specific instance. The processor may determine to allow access to content of the media.

Abstract: A node in a blockchain network may receive a request for information regarding a token, retrieve token information regarding the token from the blockchain network, generate based on the token information, a token connection object (TCO) for the token, wherein the TCO includes a subset of the token information, and send the TCO to a requestor.

Abstract: A system and related method coordinate data and transactions between an enterprise transaction system (ETS) of an enterprise and a blockchain network (BN). A coexistence mediator intercepts an ETS transaction comprising ETS transaction information (ETS-TI) associated with an enterprise. The ETS-TI includes transaction context information (ETS-TCI) regarding the ETS transaction. The system determines an ETS transaction context from the ETS-TCI. Responsive to determining the ETS transaction context represents an in-flight ETS transaction, rerouting, the coexistence mediator reroutes the transaction from the ETS to the BN. The rerouting comprises converting the ETS-TI to BN transaction information (BN-TI), and interfacing with the BN to record a processed BN transaction as a transaction record. The coexistence mediator, upon recording the BN transaction, provides a new BN-TI associated with the BN transaction. The new BN-TI comprises a BN transaction id.

Abstract: An example operation may include one or more of receiving, via a payment network, a request to detokenize a payment token to process a payment transaction between a source and a target, detokenizing the payment token based on mapping data stored in a token vault, transmitting information about the detokenized payment token to a computing device associated with the request, generating a settlement token that comprises identifiers of the source and the target and an identifier of the payment token, and transmitting the settlement token to a blockchain on a blockchain settlement network which is parallel to the payment network.

Abstract: An example operation may include one or more of encrypting a private key with an encryption key, generating a plurality of keys based on the encryption key and converting the plurality of keys into a plurality of key shares based on a secret input value, storing the encrypted private key on a blockchain, and distributing the plurality of key shares to a plurality of blockchain peers of the blockchain, where the distributing comprises transmitting a different key share from among the plurality of key shares to each blockchain peer among the plurality of blockchain peers.

Abstract: A processor may register one or more verifiable asset credential schemas. A verifiable asset credential schema may prescribe the format and content of asserting blockchain-backed asset state. The processor may register an issuer policy for the verifiable asset credentials. The issuer policy may be associated with a schema and intended credential holder(s). The processor may subscribe the asset credential issuer to one or more peers on the blockchain. The processor may issue commit notifications to a subscribing asset credential issuer in the form of schema-compliant committing-peer verifiable credentials. The processor may collect the committing-peer verifiable credentials from one or more peers. The processor may validate the committing-peer verifiable credentials satisfy the security policy and schema for a designated intended credential holder. The processor may issue a schema-compliant verifiable asset credential to the policy-designated credential holder(s).

Abstract: An example operation may include one or more of dividing a neural network that corresponds to an artificial intelligence (AI) model into a plurality of sub-models, assigning the plurality of sub-models to a plurality of blockchain peers, respectively, training the sub-models, via the plurality of blockchain peers, to generate training results within an iteration, and committing the training results to a blockchain which is accessible by the plurality of blockchain peers.

Abstract: An example operation may include one or more of identifying a new block to be created for a blockchain via a new block creation cycle, executing chaincode stored in the blockchain, identifying one or more credentials assigned as one credential per registered member organization of the blockchain based on the chaincode, validating the one or more credentials and determining consensus is satisfied via a consensus service, and creating the new block responsive to the consensus being satisfied.

Abstract: A node in a blockchain network may agree, on an authority accept a compliance module from the authority, accept the compliance module. The node may also receive an operation, verify a compliance of the operation based on the compliance module, add the verified operation to a ledger on the blockchain network.

Abstract: A computer-implemented method for configuring a blockchain network, a computer program product for integrating device identity into a permissioning framework of a blockchain network, and a blockchain network. One embodiment may comprise registering a device at a delineate node of a blockchain network, creating, by a processor of the delineate node based on the registering, a profile for the device; an performing, by the processor of the delineate node, a pass-through service for the device. The registering may include receiving, by a network interface, an immutable device identity from the device.

Abstract: Embodiments of the present invention provide a method, system and computer program product for the seamless integration of an application with an in memory data grid. In an embodiment of the invention, a method for intercepting database queries from a computer program for delegation to an in memory data grid is provided. The method includes retrieving database queries from a database driver for a database management system from a requesting computer program and comparing at least a portion of each of the database queries to a listing of database queries. Thereafter, the database queries are selectively routed to a data grid, such as an in memory data grid, in lieu of the database management based upon the comparison.

Abstract: A plurality of ledger nodes within a blockchain infrastructure is continuously updated via a set of conduit nodes. The set of conduit nodes share a secure provision ledger. The secure provision ledger includes a set of updates for the blockchain infrastructure. Each conduit node within the set propagates the set of updates to a subset of the plurality of ledger nodes.

Abstract: Described are techniques for generating and employing decentralized asset identifiers for cross-blockchain network asset transfers, the techniques including registering a decentralized asset identifier to an asset with a local asset identifier, where the decentralized asset identifier is immutable. The techniques further include endorsing a proposed transaction for transferring the asset from a first controller associated with a first blockchain network to a second controller associated with a second blockchain network, where the proposed transaction utilizes the decentralized asset identifier. The techniques further include exchanging, in a document associated with the decentralized asset identifier and retrieved from an identity network, the first controller for the second controller.

Abstract: A node in a blockchain network may receive a digital asset transfer request for a digital asset transfer, create a path object containing one or more jurisdictional requirements for the digital asset transfer request, pass the path object to a blockchain network, verify the path object, and record the path object on a blockchain network.

Abstract: A processor may analyze each instance of digital assets. The processor may identify, respectively, one or more rules that are applicable to each of the digital assets. The determination of the one or more rules is identified by a compliance mechanism. The processor may validate the one or more rules against each of the digital assets in context of a first user and a second user. The processor may endorse the transfer of the multi-asset digital wallet with a compliance mechanism signature.

Abstract: An example operation may include one or more of connecting, by an asset server, to a source blockchain configured to store a digital asset of an asset owner, enciphering and locking, by the asset server, the asset in the source blockchain, manifesting, by the asset server, the asset as a linked asset in a target blockchain, tracking, by the asset server, a life cycle of the asset, detecting, by the asset server, an end of the life cycle of the asset, reflecting, by the asset server, the end of the life cycle of the asset in the source blockchain, and creating, by the asset server, the asset in the target blockchain.