Processing a contingent action token securely

A computing infrastructure system, the computing infrastructure system comprising:

• a user 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;
• and
• a user information 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, one or more digital records of non-authenticated user information for subsequent utilization in establishing of a contingency-action token (CAT) to be represented on an object distributed ledger, the one or more digital records comprising a user computing entity identifier (ID) associated with the user computing entity, a triggered outcome timeframe, a triggered outcome level, a user ID, a contingency entity ID, an obligation provider ID, and an outcome recipient ID, wherein the obligation provider ID is associated with providing of an obligation tied to an obligation recipient ID in accordance with obligation requirements, wherein the outcome recipient ID is associated with a result of a triggered outcome tied to an outcome provider ID in accordance with contingent outcome rules and an obligation status, wherein a positive obligation status indicates that the obligation has historically been provided in accordance with the obligation requirements, wherein a contingency status indicates whether the triggered outcome has been triggered for the contingency entity ID in accordance with the contingent outcome rules as a function of one of the triggered outcome timeframe and a longevity status associated with the contingency entity ID;
• and
• wherein the second processor performs functions to:
• identify the user information authenticity computing entity based on at least one of the user ID, the contingency entity ID, the obligation provider ID, the outcome recipient ID, the triggered outcome level, and the longevity status associated with the contingency entity ID;
• wherein the third processor performs functions to:
• generate authenticity information utilizing, from the marketplace computing entity, the at least one of the user ID, the contingency entity ID, the obligation provider ID, the outcome recipient ID, the triggered outcome level, and the longevity status associated with the contingency entity ID;
• and
• wherein the second processor performs further functions to:
• interpret the authenticity information from the user information authenticity computing entity to produce an authenticity indicator associated with the non-authenticated user information, the authenticity indicator comprising one of an authenticated status, a pending status, and an unauthenticated status;
• convert the non-authenticated user information into authenticated user information when the authenticity indicator indicates the authenticated status;
• generate a smart contract based on the authenticated user information to include the obligation recipient ID, the obligation requirements, the obligation, the triggered outcome, the outcome provider ID, the contingent outcome rules, an initial obligation status, an initial contingency status, the triggered outcome timeframe, a current longevity status associated with the contingency entity ID, the triggered outcome level, the contingency entity ID, the obligation provider ID, the outcome recipient ID, and the authenticity indicator;
• obtain a copy of a portion of the object distributed ledger;
• hash the smart contract utilizing a receiving public key of the object distributed ledger to produce a next transaction hash value;
• encrypt the next transaction hash value based on one of a private key of the marketplace computing entity and a private key of the user 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 as the CAT;
• and
• cause inclusion of the next block in the object distributed ledger.