| CPC G06Q 20/4016 (2013.01) [G06Q 20/123 (2013.01); G06Q 30/0619 (2013.01); H04L 9/3247 (2013.01); H04L 9/50 (2022.05); G06Q 2220/00 (2013.01); H04L 2209/56 (2013.01)] | 12 Claims |

|
1. A computer-implemented method of using a computing infrastructure for utilizing an object distributed ledger, the method comprising:
issuing, by an object owner computing entity of the computing infrastructure to a marketplace computing entity of the computing infrastructure, a digital record representing a contingent asset, the digital record comprising an asset identifier, a lifecycle status indictor, a potential payer liability level, a payer identifier, a seller identifier, and an owner identifier, wherein the digital record further includes a representation that the payer identifier is obligated for the potential payer liability level to at least one of the seller identifier and the owner identifier when the lifecycle status indictor transitions from a pending status level to an approved status level in response to a contingency aspect of the contingent asset being satisfied;
identifying, by the marketplace computing entity, an asset authenticity computing entity of the computing infrastructure based on at least one of the asset identifier, the payer identifier, and the seller identifier of the contingent asset;
generating, by the asset authenticity computing entity, an authenticity indicator associated with the contingent asset utilizing the at least one of the asset identifier, the payer identifier, and the seller identifier of the contingent asset from the marketplace computing entity, the authenticity indicator comprising the pending status level;
determining, by the marketplace computing entity, that the authenticity indicator associated with the contingent asset from the asset authenticity computing entity is the same as the lifecycle status indictor of the digital record representing the contingent asset;
generating, by the marketplace computing entity, a smart contract to indicate availability of the contingent asset to include available terms and the authenticity indicator comprising the pending status level;
obtaining, by the marketplace computing entity, a portion of a copy of the object distributed ledger;
hashing, by the marketplace computing entity, the smart contract utilizing a receiving public key associated with a receiving computing entity of the object distributed ledger to produce a next transaction hash value;
encrypting, by the marketplace computing entity, the next transaction hash value utilizing a private key of the marketplace computing entity to produce a next transaction signature;
generating, by the marketplace computing entity, a next block of a blockchain of the object distributed ledger to include the smart contract and the next transaction signature; and
causing, by the marketplace computing entity, inclusion of the next block in the object distributed ledger.
|