| CPC H04L 9/3213 (2013.01) [G06F 21/10 (2013.01); H04L 9/0825 (2013.01); H04L 9/3236 (2013.01); H04L 9/50 (2022.05); H04L 2209/60 (2013.01)] | 3 Claims |

|
1. A computer-implemented method, the method comprises:
establishing, by a computing entity of a computing system, a set of required public benefit asset information for subsequent selection of a set of public benefit credit assets based on a record of a first pending transaction, wherein a particular public benefit credit asset of the set of public benefit credit assets includes a smart contract that assigns a corresponding credit level from a corresponding payer identifier (ID) to a corresponding owner ID associated with the particular public benefit credit asset, wherein the record of the first pending transaction includes an identifier of a transaction item, identity of a requesting computing entity, and an authenticated value of the transaction item, wherein the establishing the set of required public benefit asset information includes one or more of:
determining an asset type of the required public benefit asset information based on the identifier of the transaction item,
determining the asset type of the required public benefit asset information based on the identity of the requesting computing entity, and
determining an asset level of the required public benefit asset information based on the authenticated value of the transaction item;
indicating, by the computing entity, selection of a secure first token on an object distributed ledger representing the set of public benefit credit assets when the set of required public benefit asset information matches a corresponding portion of the secure first token to produce a selected secure first token;
updating, by the computing entity, the smart contract to produce an updated smart contract to represent reassignment of the corresponding credit level from the corresponding payer identifier to a new corresponding owner identifier associated with the identity of the requesting computing entity;
obtaining, by the computing entity, a copy of the object distributed ledger;
hashing, by the computing entity, the updated smart contract utilizing a receiving public key 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 the 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 updated smart contract and the next transaction signature; and
causing, by the computing entity, inclusion of the next block as an updated secure first token of the selected secure first token in the object distributed ledger.
|