| CPC G06Q 20/3672 (2013.01) [G06Q 20/3674 (2013.01); G06Q 20/401 (2013.01); H04L 9/50 (2022.05); G06Q 2220/00 (2013.01)] | 6 Claims |
|
1. A computer-implemented method of using a computing infrastructure for utilizing an object distributed ledger, the method comprising:
issuing, by a requesting computing entity of the computing infrastructure to a marketplace computing entity of the computing infrastructure, a digital record representing a request to securely establish a contingent asset solution for a secure first pending transaction associated with a transaction item, wherein the secure first pending transaction includes identity of the transaction item, identity of the requesting computing entity, identity of the marketplace computing entity, and an authenticated value of the transaction item, wherein the contingent asset solution includes a secure digital record representing a set of contingent assets associated with at least one of each of an asset identifier, a lifecycle status indictor, a potential payer liability level, a payer identifier, a seller identifier, and an owner identifier, wherein, the secure digital record further includes a representation that, for a particular asset identifier, 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;
determining, by the marketplace computing entity, a set of candidate contingent assets for the secure first pending transaction based on the identity of the transaction item, the identity of the requesting computing entity, and the authenticated value of the transaction item, wherein each candidate contingent asset of the set of candidate contingent assets includes a proposed unique smart contract between the identifier of the requesting computing entity and an identifier of a provider of the proposed unique smart contract;
identifying, by the marketplace computing entity, an asset authenticity computing entity of the computing infrastructure based on at least one of the asset identifier, payer identifier, and the seller identifier of at least one candidate contingent asset of the set of candidate contingent assets;
generating, by the asset authenticity computing entity, authenticity information utilizing the at least one of the asset identifier, the payer identifier, and the seller identifier of the at least one candidate contingent asset of the set of candidate contingent assets from the marketplace computing entity;
determining, by the marketplace computing entity, that the authenticity information confirms the pending status level of the lifecycle status indictor of the at least one candidate contingent asset;
facilitating, by the marketplace computing entity, selection of the at least one candidate contingent asset of the set of candidate contingent assets utilizing an asset selection approach to produce a set of selected contingent assets;
generating, by the marketplace computing entity, a set of smart contracts for the set of selected contingent assets to provide the contingent asset solution for the secure first pending transaction;
obtaining, by the marketplace computing entity, a portion of a copy of the object distributed ledger;
hashing, by the marketplace computing entity, the set of smart contracts utilizing a receiving public key 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 set of smart contracts and the next transaction signature; and
causing, by the marketplace computing entity, inclusion of the next block in the object distributed ledger.
|