One action based processing of a contingent asset secure token

Abstract

A method includes a computing entity issuing to an asset authenticity computing entity a request to select and authenticate a digital record that represents an available contingent asset based on a digital record representing a hypothetical contingent asset to produce a selected contingent asset. The method further includes determining that authenticity information associated with the selected contingent asset indicates that the selected contingent asset matches the hypothetical contingent asset. The method further includes, when approved, generating a smart contract to indicate availability of the selected contingent asset and obtaining a copy of an object distributed ledger. The method further includes causing inclusion of a next block on the object distributed ledger that includes the smart contract to represent the selected contingent asset.

What is claimed is: 
     
         1 . A computer-implemented method of using a computing infrastructure, the method comprising:
 generating, by a computing entity of the computing infrastructure, a digital record representing a hypothetical contingent asset to securely establish a contingent asset solution for a secure first token representing a first pending transaction associated with a transaction item, wherein the secure first token representing the first pending transaction includes identity of the transaction item, identity of a requesting computing entity associated with the secure first token, and an authenticated value of the transaction item, wherein the contingent asset solution includes updating the secure first token to subsequently represent a selected contingent asset to subsequently provide conversion of the selected contingent asset to complete the first pending transaction, wherein the digital record representing the hypothetical contingent asset includes an asset identifier, a lifecycle status indicator, a potential payer liability level, a payer identifier, a seller identifier, and an owner identifier, wherein, when the contingent asset is a public benefit asset, the digital record representing the hypothetical contingent asset further includes a negative factor area identifier, a negative factor area level, an offsetting area identifier, and an offsetting area level, 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 in consideration for activities of the offsetting area identifier in accordance with the offsetting area level providing a right to facilitate activities associated with the negative factor area identifier in accordance with the negative factor area level;   identifying, by the computing entity, an asset authenticity computing entity of the computing infrastructure based on at least one of the identity of the transaction item, the asset identifier, the payer identifier, the seller identifier, the negative factor area identifier, and the offsetting area identifier;   issuing, by the computing entity to the asset authenticity computing entity, a request to select and authenticate a digital record that represents an available contingent asset based on the digital record representing the hypothetical contingent asset to produce the selected contingent asset;   issuing, by the asset authenticity computing entity to the computing entity, a digital record of the selected contingent asset that includes authenticity information associated with the selected contingent asset utilizing the at least one of the asset identifier, the payer identifier, the seller identifier, the negative factor area identifier, and the offsetting area identifier;   determining, by the computing entity, that the authenticity information associated with the selected contingent asset indicates that the selected contingent asset matches the hypothetical contingent asset;   generating, by the computing entity, a smart contract to include the authenticity information and to indicate that the selected contingent asset is to facilitate completion of the first pending transaction;   obtaining, by the computing entity, a portion of a copy of an object distributed ledger associated with at least one of the first pending transaction and the selected contingent asset;   hashing, by the 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 computing entity, the next transaction hash value utilizing a private key of one of the computing entity and the requesting computing entity to produce a next transaction signature;   generating, by the 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 computing entity, inclusion of the next block in the object distributed ledger as the contingent asset solution.   
     
     
         2 . The method of  claim 1  further comprises:
 updating, by the computing entity, the secure first token to include the smart contract to produce an updated secure first token; and 
 facilitating, by the computing entity, inclusion of a representation of the updated secure first token in the object distributed ledger as the contingent asset solution. 
 
     
     
         3 . The method of  claim 1  further comprises:
 establishing, by the computing entity, selected contingent asset available terms when the authenticity information includes an available lifecycle status indicator; 
 obtaining, by the computing entity, a one action selection approval indicator from the requesting computing entity with regards to the selected contingent asset; and 
 updating, by the computing entity, the smart contract to include the selected contingent asset available terms. 
 
     
     
         4 . The method of  claim 1  further comprises:
 interpreting, by the asset authenticity computing entity, a multitude of ingested data to produce time-varying and time-sensitive evaluation data associated with a multitude of contingent assets that includes the available contingent asset; 
 comparing, by the asset authenticity computing entity, the digital record representing the hypothetical contingent asset to the time-varying and time-sensitive evaluation data to produce a level of match for each of the multitude of contingent assets; and 
 selecting, by the asset authenticity computing entity, the available contingent asset as the selected contingent asset when a level of match associated with the available contingent asset has reached a threshold level to trigger declaration of an approved match. 
 
     
     
         5 . The method of  claim 1  further comprises:
 receiving, by the computing entity from the asset authenticity computing entity, a multitude of time-varying and time-sensitive evaluation data associated with a multitude of contingent assets that includes the available contingent asset; 
 comparing, by the computing entity, the digital record representing the hypothetical contingent asset to the time-varying and time-sensitive evaluation data to produce a level of match for each of the multitude of contingent assets; and 
 selecting, by the computing entity, the available contingent asset as the selected contingent asset when a level of match associated with the available contingent asset has reached a threshold level to trigger declaration of an approved match. 
 
     
     
         6 . The method of  claim 1  further comprises:
 updating, by the computing entity, a generative artificial intelligence knowledge base with a multitude of time-varying and time-sensitive evaluation data associated with a multitude of contingent assets that includes the available contingent asset; and 
 accessing, by the computing entity, the generative artificial intelligence knowledge base using the digital record representing the hypothetical contingent asset to identify the available contingent asset as the selected contingent asset. 
 
     
     
         7 . A computing infrastructure system, the computing infrastructure system comprising:
 a 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;   an asset authenticity 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;   wherein the first processor performs functions to:
 generate a digital record representing a hypothetical contingent asset to securely establish a contingent asset solution for a secure first token representing a first pending transaction associated with a transaction item, wherein the secure first token representing the first pending transaction includes identity of the transaction item, identity of a requesting computing entity associated with the secure first token, and an authenticated value of the transaction item, wherein the contingent asset solution includes updating the secure first token to subsequently represent a selected contingent asset to subsequently provide conversion of the selected contingent asset to complete the first pending transaction, wherein the digital record representing the hypothetical contingent asset includes an asset identifier, a lifecycle status indicator, a potential payer liability level, a payer identifier, a seller identifier, and an owner identifier, wherein, when the contingent asset is a public benefit asset, the digital record representing the hypothetical contingent asset further includes a negative factor area identifier, a negative factor area level, an offsetting area identifier, and an offsetting area level, 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 in consideration for activities of the offsetting area identifier in accordance with the offsetting area level providing a right to facilitate activities associated with the negative factor area identifier in accordance with the negative factor area level; 
 identify the asset authenticity computing entity of the computing infrastructure based on at least one of the identity of the transaction item, the asset identifier, the payer identifier, the seller identifier, the negative factor area identifier, and the offsetting area identifier; and 
 issue, via the first interface to the asset authenticity computing entity, a request to select and authenticate a digital record that represents an available contingent asset based on the digital record representing the hypothetical contingent asset to produce the selected contingent asset; 
   wherein the second processor performs functions to:
 issue, via the second interface to the computing entity, a digital record of the selected contingent asset that includes authenticity information associated with the selected contingent asset utilizing the at least one of the asset identifier, the payer identifier, the seller identifier, the negative factor area identifier, and the offsetting area identifier; and 
   wherein the first processor performs further functions to:
 determine that the authenticity information associated with the selected contingent asset indicates that the selected contingent asset matches the hypothetical contingent asset; 
 generate a smart contract to include the authenticity information and to indicate that the selected contingent asset is to facilitate completion of the first pending transaction; 
 obtain, via the first interface, a portion of a copy of an object distributed ledger associated with at least one of the first pending transaction and the selected contingent asset; 
 hash 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; 
 encrypt the next transaction hash value utilizing a private key of one of the computing entity and the requesting computing entity to produce a next transaction signature; 
 generate a next block of a blockchain of the object distributed ledger to include the smart contract and the next transaction signature; and 
 cause, via the first interface, inclusion of the next block in the object distributed ledger as the contingent asset solution. 
   
     
     
         8 . The computing infrastructure system of  claim 7 , wherein the first processor performs further functions to:
 update the secure first token to include the smart contract to produce an updated secure first token; and   facilitate inclusion of a representation of the updated secure first token in the object distributed ledger as the contingent asset solution.   
     
     
         9 . The computing infrastructure system of  claim 7 , wherein the first processor performs further functions to:
 establish selected contingent asset available terms when the authenticity information includes an available lifecycle status indicator;   obtain, via the first interface, a one action selection approval indicator from the requesting computing entity with regards to the selected contingent asset; and   update the smart contract to include the selected contingent asset available terms.   
     
     
         10 . The computing infrastructure system of  claim 7 , wherein the second processor performs further functions to:
 Interpret a multitude of ingested data to produce time-varying and time-sensitive evaluation data associated with a multitude of contingent assets that includes the available contingent asset;   compare the digital record representing the hypothetical contingent asset to the time-varying and time-sensitive evaluation data to produce a level of match for each of the multitude of contingent assets; and   select the available contingent asset as the selected contingent asset when a level of match associated with the available contingent asset has reached a threshold level to trigger declaration of an approved match.   
     
     
         11 . The computing infrastructure system of  claim 7 , wherein the first processor performs further functions to:
 receive, via the first interface from the asset authenticity computing entity, a multitude of time-varying and time-sensitive evaluation data associated with a multitude of contingent assets that includes the available contingent asset;   compare the digital record representing the hypothetical contingent asset to the time-varying and time-sensitive evaluation data to produce a level of match for each of the multitude of contingent assets; and   select the available contingent asset as the selected contingent asset when a level of match associated with the available contingent asset has reached a threshold level to trigger declaration of an approved match.   
     
     
         12 . The computing infrastructure system of  claim 7 , wherein the first processor performs further functions to:
 update a generative artificial intelligence knowledge base with a multitude of time-varying and time-sensitive evaluation data associated with a multitude of contingent assets that includes the available contingent asset; and   access, via the first interface, the generative artificial intelligence knowledge base using the digital record representing the hypothetical contingent asset to identify the available contingent asset as the selected contingent asset.