Systems for multi-blockchain, multi-token interoperability via common blockchain integration and methods of use thereof

1. A method comprising:

receiving, by a controller of a membered common distributed crypto-ledger, a first instruction to perform at least one operation between a first user, associated with a first entity-specific distributed crypto-ledger of a first entity, and a second user, associated with a second entity-specific distributed crypto-ledger of a second entity;

wherein the first instruction comprises:

a first encrypted storage identifier that identifies a first encrypted storage associated with the first user and

a second encrypted storage identifier that identifies a second encrypted storage associated with the second user;

wherein the first entity is different from the second entity;

wherein the first entity and the second entity are members of the membered common distributed crypto-ledger;

wherein the first entity-specific distributed crypto-ledger of the first entity is operatively linked to the membered common distributed crypto-ledger via a first common encrypted storage, stored on a first common node of the membered common distributed crypto-ledger;

wherein the second entity-specific distributed crypto-ledger of the second entity is operatively linked to the membered common distributed crypto-ledger via a second common encrypted storage, stored on a second common node of the membered common distributed crypto-ledger;

wherein the first common encrypted storage is a first entity encrypted storage for all users of the first entity-specific distributed crypto-ledger;

wherein the second common encrypted storage is a second entity encrypted storage for all users of the second entity-specific distributed crypto-ledger;

determining, by the controller, a first quantity of first entity-specific crypto-tokens on the first entity-specific distributed crypto-ledger based at least in part on the at least one operation;

determining, by the controller, a second quantity of common crypto-tokens that is equivalent to the first quantity of the first crypto-tokens;

instructing, by the controller, the first common node to burn the first quantity of first entity-specific crypto-tokens from the first entity-specific distributed crypto-ledger;

instructing, by the controller, the membered common distributed crypto-ledger to mint the second quantity of the common crypto-tokens in the first common distributed crypto-ledger encrypted storage on the membered common distributed crypto-ledger;

instructing, by the controller, the membered common distributed crypto-ledger to move the second quantity of common crypto-tokens from the first common distributed crypto-ledger encrypted storage to a second common distributed crypto-ledger encrypted storage;

determining, by the controller, a third quantity of second entity-specific crypto-tokens that is equivalent to the second quantity of the common crypto-tokens;

instructing, by the controller, the second common node of the common distributed crypto-ledger to burn the second quantity of the common crypto-tokens from the second common distributed crypto-ledger encrypted storage;

instructing, by the controller, the second entity-specific distributed crypto-ledger to mint the third quantity of the second entity-specific crypto-tokens on the second entity-specific distributed crypto-ledger so as to convert the common crypto-tokens to the second entity-specific crypto-tokens; and

returning, by the controller, a confirmation that confirms the at least one operation based at least in part on the third quantity of the at least one second crypto-token being minted in the second encrypted storage.

2. The method as recited in claim 1 , further comprising:

accessing, by the controller, a user-entity registry comprising a mapping of encrypted storage identifiers enrolled with the membered common distributed crypto-ledger to entity-specific distributed crypto-ledgers enrolled with the membered common distributed crypto-ledger; and

determining, by the controller, the second common distributed crypto-ledger encrypted storage based at least in part on the second encrypted storage identifier and the user-entity registry.

3. The method as recited in claim 1 , further comprising:

utilizing, by the controller, a first interoperability smart contract to instruct the first common node to burn the first quantity of first crypto-tokens from the first encrypted storage; and

utilizing, by the controller, a second interoperability smart contract to instruct the second common node to mint the third quantity of second entity-specific crypto-tokens from the first encrypted storage.

4. The method as recited in claim 3 , wherein the first interoperability smart contract to further instructs the first common node to produce at least one operation record representing the at least one operation; and

wherein the at least one operation record comprises the second encrypted storage identifier.

5. The method as recited in claim 4 , further comprising:

receiving, by the controller, the at least one operation record from the first common node;

utilizing, by the controller, a common interoperability smart contract to mint the second quantity of the common crypto-tokens in the first common distributed crypto-ledger encrypted storage on the membered common distributed crypto-ledger; and

utilizing, by the controller, a common interoperability smart contract to instruct the membered common distributed crypto-ledger to move the second quantity of common crypto-tokens from the first common distributed crypto-ledger encrypted storage to the second common distributed crypto-ledger encrypted storage based at least in part on the at least one operation record.

6. The method as recited in claim 5 , wherein the common interoperability smart contract causes the membered common distributed crypto-ledger to create a membered common distributed crypto-ledger entry comprising the second quantity of common crypto-tokens and the at least one operation record.

7. The method as recited in claim 1 , wherein the first entity-specific crypto-tokens comprise a first stablecoin;

wherein the second entity-specific crypto-tokens comprise a second stablecoin; and

wherein the common crypto-tokens comprise a third stablecoin.

8. The method as recited in claim 1 , wherein the first instruction causes the first entity-specific crypto-ledger to move the first quantity of the first entity-specific crypto-tokens from the first encrypted storage to a first common node encrypted storage of the first common node.

9. The method as recited in claim 1 , further comprising instructing, by the controller, the second entity-specific distributed crypto-ledger to move the third quantity of the second entity-specific crypto-tokens from a second common node encrypted storage of the second common node to the second encrypted storage.

10. The method as recited in claim 1 , further comprising:

receiving, by the controller, a first notification indicative of the asset quantity being stored in a first common omnibus associated with the first entity;

instructing, by the controller, the membered common distributed crypto-ledger to mint the second quantity of the common crypto-tokens in the first common distributed crypto-ledger encrypted storage on the membered common distributed crypto-ledger based on the notification so as to create in the first common distributed crypto-ledger encrypted storage the second quantity of the common crypto-tokens based on the asset quantity;

receiving, by the controller, a second notification indicative of the asset quantity being received by a second common omnibus associated with the second entity; and

instructing, by the controller, the second common node of the common distributed crypto-ledger to burn the second quantity of the common crypto-tokens from the second common distributed crypto-ledger encrypted storage in response to the second notification.

11. A system comprising:

a controller configured to perform steps to:

receive, from a membered common distributed crypto-ledger, a first instruction to perform at least one operation between a first user, associated with a first entity-specific distributed crypto-ledger of a first entity, and a second user, associated with a second entity-specific distributed crypto-ledger of a second entity;

wherein the first instruction comprises:

a first encrypted storage identifier that identifies a first encrypted storage associated with the first user and

a second encrypted storage identifier that identifies a second encrypted storage associated with the second user;

wherein the first entity is different from the second entity;

wherein the first entity and the second entity are members of the membered common distributed crypto-ledger;

wherein the first entity-specific distributed crypto-ledger of the first entity is operatively linked to the membered common distributed crypto-ledger via a first common encrypted storage, stored on a first common node of the membered common distributed crypto-ledger;

wherein the second entity-specific distributed crypto-ledger of the second entity is operatively linked to the membered common distributed crypto-ledger via a second common encrypted storage, stored on a second common node of the membered common distributed crypto-ledger;

wherein the first common encrypted storage is a first entity encrypted storage for all users of the first entity-specific distributed crypto-ledger;

wherein the second common encrypted storage is a second entity encrypted storage for all users of the second entity-specific distributed crypto-ledger;

determine a first quantity of first entity-specific crypto-tokens on the first entity-specific distributed crypto-ledger based at least in part on the at least one operation;

determine a second quantity of common crypto-tokens that is equivalent to the first quantity of the first crypto-tokens;

instruct the first common node to burn the first quantity of first entity-specific crypto-tokens from the first entity-specific distributed crypto-ledger;

instruct the membered common distributed crypto-ledger to mint the second quantity of the common crypto-tokens in the first common distributed crypto-ledger encrypted storage on the membered common distributed crypto-ledger;

instruct the membered common distributed crypto-ledger to move the second quantity of common crypto-tokens from the first common distributed crypto-ledger encrypted storage to a second common distributed crypto-ledger encrypted storage;

determine a third quantity of second entity-specific crypto-tokens that is equivalent to the second quantity of the common crypto-tokens;

instruct the second common node of the common distributed crypto-ledger to burn the second quantity of the common crypto-tokens from the second common distributed crypto-ledger encrypted storage;

instruct the second entity-specific distributed crypto-ledger to mint the third quantity of the second entity-specific crypto-tokens on the second entity-specific distributed crypto-ledger so as to convert the common crypto-tokens to the second entity-specific crypto-tokens; and

return confirmation that confirms the at least one operation based at least in part on the third quantity of the at least one second crypto-token being minted in the second encrypted storage.

12. The system as recited in claim 11 , wherein the controller is further configured to perform steps to:

access a user-entity registry comprising a mapping of encrypted storage identifiers enrolled with the membered common distributed crypto-ledger to entity-specific distributed crypto-ledgers enrolled with the membered common distributed crypto-ledger; and

determine the second common distributed crypto-ledger encrypted storage based at least in part on the second encrypted storage identifier and the user-entity registry.

13. The system as recited in claim 11 , wherein the controller is further configured to perform steps to:

utilize a first interoperability smart contract to instruct the first common node to burn the first quantity of first crypto-tokens from the first encrypted storage; and

utilize a second interoperability smart contract to instruct the second common node to mint the third quantity of second entity-specific crypto-tokens from the first encrypted storage.

14. The system as recited in claim 13 , wherein the first interoperability smart contract to further instructs the first common node to produce at least one operation record representing the at least one operation; and

wherein the at least one operation record comprises the second encrypted storage identifier.

15. The system as recited in claim 14 , wherein the controller is further configured to perform steps to:

receive the at least one operation record from the first common node;

utilize a common interoperability smart contract to mint the second quantity of the common crypto-tokens in the first common distributed crypto-ledger encrypted storage on the membered common distributed crypto-ledger; and

utilize a common interoperability smart contract to instruct the membered common distributed crypto-ledger to move the second quantity of common crypto-tokens from the first common distributed crypto-ledger encrypted storage to the second common distributed crypto-ledger encrypted storage based at least in part on the at least one operation record.

16. The system as recited in claim 15 , wherein the common interoperability smart contract causes the membered common distributed crypto-ledger to create a membered common distributed crypto-ledger entry comprising the second quantity of common crypto-tokens and the at least one operation record.

17. The system as recited in claim 11 , wherein the first entity-specific crypto-tokens comprise a first stablecoin;

wherein the second entity-specific crypto-tokens comprise a second stablecoin; and

wherein the common crypto-tokens comprise a third stablecoin.

18. The system as recited in claim 11 , wherein the first instruction causes the first entity-specific crypto-ledger to move the first quantity of the first entity-specific crypto-tokens from the first encrypted storage to a first common node encrypted storage of the first common node.

19. The system as recited in claim 11 , wherein the controller is further configured to perform steps to instruct the second entity-specific distributed crypto-ledger to move the third quantity of the second entity-specific crypto-tokens from a second common node encrypted storage of the second common node to the second encrypted storage.

20. The system as recited in claim 11 , wherein the controller is further configured to perform steps to:

receive a first notification indicative of the asset quantity being stored in a first common omnibus associated with the first entity;

instruct the membered common distributed crypto-ledger to mint the second quantity of the common crypto-tokens in the first common distributed crypto-ledger encrypted storage on the membered common distributed crypto-ledger based on the notification so as to create in the first common distributed crypto-ledger encrypted storage the second quantity of the common crypto-tokens based on the asset quantity;

receive a second notification indicative of the asset quantity being received by a second common omnibus associated with the second entity; and

instruct the second common node of the common distributed crypto-ledger to burn the second quantity of the common crypto-tokens from the second common distributed crypto-ledger encrypted storage in response to the second notification.