Controlling a secure 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 an instant asset solution for a secure first token representing a first pending transaction associated with a transaction item, wherein the secure first token includes a set of smart contracts of the first pending transaction, wherein the set of smart contracts pertains to a selected contingent asset of a set of candidate contingent assets for the first pending transaction, wherein the 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 instant asset solution includes updating the secure first token to represent a selected instant asset to subsequently provide conversion of the selected contingent asset to complete the first pending transaction, wherein the set of smart contracts for the selected contingent asset includes an asset identifier, a lifecycle status indictor, a potential payer liability level, a payer identifier, a seller identifier, and an owner identifier, wherein the set of smart contracts 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:
• identify the asset authenticity computing entity based on at least one of the asset identifier, payer identifier, and the seller identifier of the selected contingent asset of the set of candidate contingent assets;
• wherein the third processor performs functions to:
• generate authenticity information for the selected contingent asset utilizing the at least one of the asset identifier, the payer identifier, and the seller identifier of the selected contingent asset 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 selected contingent asset;
• obtain, in accordance with an instant asset selection approach, a selection of a first instant asset of a set of candidate instant assets as the selected instant asset that may be utilized to subsequently provide the conversion of the selected contingent asset to complete the first pending transaction, wherein at least one candidate instant asset of the set of candidate instant assets pertains to satisfying a portion of another liability in accordance with a digital record representing a delinquently paying consumer to the payer identifier of the selected contingent asset;
• generate an updated set of smart contracts for an updated secure first token to represent the selection of the first instant asset to subsequently provide the conversion of the selected contingent asset to complete the first pending transaction;
• obtain, via the second interface, a portion of a copy of the object distributed ledger;
• hash the updated 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 updated 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 as the updated secure first token for the instant asset solution.