Generating a token for a contingent asset

A computing infrastructure, the computing infrastructure comprising:

• a requesting computing entity comprising a first interface, a first local memory, and a first processor operably coupled to the first interface and the first local memory;
• a marketplace computing entity comprising a second interface, a second local memory, and a second processor operably coupled to the second interface and the second local memory;
• an asset authenticity computing entity comprising a third interface, a third local memory, and a third processor operably coupled to the third interface and the third local memory;
• wherein the first processor performs functions to:
• issue, via the first interface to the marketplace computing entity, 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;
• wherein the second processor performs functions to:
• determine 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;
• and
• identify the asset authenticity computing entity 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;
• wherein the third processor performs functions to:
• generate 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;
• wherein the second processor performs further functions to:
• determine that the authenticity information confirms the pending status level of the lifecycle status indictor of the at least one candidate contingent asset;
• facilitate 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;
• generate a set of smart contracts for the set of selected contingent assets to provide the contingent asset solution for the secure first pending transaction;
• obtain, via the second interface, a portion of a copy of the object distributed ledger;
• hash the set of smart contracts utilizing a receiving public key of the object distributed ledger to produce a next transaction hash value;
• encrypt the next transaction hash value utilizing a private key of the marketplace computing entity to produce a next transaction signature;
• generate a next block of a blockchain of the object distributed ledger to include the set of smart contracts and the next transaction signature;
• and
• cause, via the second interface, inclusion of the next block in the object distributed ledger.