| CPC H04L 9/32 (2013.01) [G06Q 20/02 (2013.01); G06Q 20/363 (2013.01); G06Q 20/367 (2013.01); G06Q 20/3825 (2013.01); G06Q 20/3827 (2013.01); G06Q 20/3829 (2013.01); G06Q 20/389 (2013.01); G06Q 20/4014 (2013.01); G06Q 40/06 (2013.01); H04L 9/0891 (2013.01); H04L 9/14 (2013.01); H04L 9/3213 (2013.01); H04L 9/3234 (2013.01); H04L 9/3236 (2013.01); H04L 9/3247 (2013.01); H04L 9/50 (2022.05); G06Q 40/08 (2013.01); H04L 2209/56 (2013.01)] | 18 Claims |
|
1. A computer-implemented security method of using a computing system, the method comprises:
selecting, by a computing device of the computing system, a contingency-action token (CAT) of an object distributed ledger to produce a selected CAT, wherein the CAT includes one of a non-fungible token (NFT) and another token linked to the NFT by the object distributed ledger when the CAT is not the NFT, wherein the CAT meets minimum CAT requirements that includes:
a recovered cryptographic token value of the CAT matches a calculated cryptographic token value of the CAT,
an obligation provider identifier record of the CAT that includes an original obligation provider identifier (ID) of the CAT when the CAT was initially generated and a timeframe-specific obligation provider ID, wherein the timeframe-specific obligation provider ID is valid for a specific timeframe, wherein the obligation provider identifier is associated with providing of an obligation tied to an obligation recipient identifier in accordance with obligation requirements, wherein a positive obligation status indicates that the obligation has historically been provided in accordance with the obligation requirements,
an outcome recipient identifier record of the CAT that includes an original outcome recipient identifier of the CAT when the CAT was initially generated and a timeframe-specific outcome recipient ID, wherein the timeframe-specific outcome recipient ID is valid for the specific timeframe, wherein the outcome recipient identifier is associated with a result of a triggered outcome tied to an outcome provider identifier in accordance with contingent outcome rules and the positive obligation status, wherein a contingency status indicates whether the triggered outcome has been triggered for a contingency entity identifier in accordance with the contingent outcome rules,
a timeframe-specific mapping of the triggered outcome to the original outcome recipient ID and the timeframe-specific outcome recipient ID, and
a utilization status of the CAT that indicates a life insurance investment utilization;
facilitating, by the computing device in accordance with a securely passing process, taking control over the CAT of a blockchain of the object distributed ledger in response to a change of contingency status of the CAT, wherein only a device possessing control over the CAT may modify the CAT;
determining, by the computing device, whether the triggered outcome is valid for the CAT based on the change of contingency status of the CAT, wherein the triggered outcome further includes resolution of the life insurance investment utilization; and
when the triggered outcome is valid for the CAT:
updating, by the computing device, the CAT to indicate that the triggered outcome is valid and that the resolution of the life insurance investment utilization is valid for the CAT to produce an updated CAT; and
causing, by the computing device in accordance with the securely passing process, generation of a new block affiliated with the updated CAT via the blockchain of the object distributed ledger, wherein the new block includes the updated CAT.
|