# US 12,192,317 B2 · Systems for multi-blockchain, multi-token interoperability via common blockchain integration > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,192,317 B2 - Document ID: US12192317B2 - Status: Granted - Kind: B2 - Application number: 18/183,035 - Filed: 2023-03-13 - Published: 2023-08-03 - Granted: 2025-01-07 - Earliest claimed: 2022-02-03 - Assignees: Tassat Group Inc. - Applicants: Tassat Group Inc. - Inventors: Kevin Lupowitz; Eric Couillard; Sanjaya Kulkarni; Brian Bruce; Sanjay Deshpande; Omari Edwards; Joe Grastara; Al Gleicher - Web page: https://patentgrep.com/patent/US12192317B2 ## CPC - H04L 9/00: {Cryptographic mechanisms or cryptographic} arrangements for secret or secure communications; Network security protocols - H04L 9/3213: {using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807)} - H04L 9/50: {using hash chains, e.g. blockchains or hash trees} - H04L 2209/56: Financial cryptography, e.g. electronic payment or e-cash - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Systems and/or methods of the present disclosure enable ledger interoperability using a controller to perform an operation between a first user and a second user on separate entity-specific distributed ledgers, where the separate entity-specific distributed ledgers are both operatively linked to a membered common distributed ledger. The controller burns a first quantity of first entity-specific tokens from the first entity-specific distributed ledger and mints a second quantity of the common tokens on the membered common distributed ledger, where the first quantity of first entity-specific tokens and the second quantity of the common tokens represent an equivalency. The controller moves the second quantity of common tokens from a first encrypted storage to a second encrypted storage of the membered common distributed ledger, burns the second quantity of the common tokens and mints a third quantity of the second entity-specific tokens on the second entity-specific distributed ledger to complete the operation. ## Claims ### Claim 1 A system for performing at least one operation regarding an asset between a first user, associated with a first entity-specific distributed ledger of a first entity, and a second user, associated with a second entity-specific distributed ledger of a second entity, wherein the first entity is different from the second entity, the system comprising: a common member platform comprising a common distributed ledger operatively linked to the first entity-specific ledger of the first entity and the second entity-specific ledger of the second entity, the common distributed ledger comprising a first common distributed ledger encrypted storage and a second common distributed ledger encrypted storage; a controller and a non-transitory computer readable storage medium storing instructions, which when operated by the controller, cause the controller to: determine a first quantity of first tokens on the first entity-specific ledger that represents an equivalence to the asset; determine a second quantity of common tokens having equivalent value to the first quantity of first entity-specific tokens; instruct the first entity-specific ledger of the first entity to burn the first quantity of first tokens; mint the second quantity of common tokens in the first common distributed ledger encrypted storage; transfer the second quantity of common tokens from the first common distributed ledger encrypted storage to the second common distributed ledger encrypted storage; instruct the first entity-specific platform to transfer the asset from the first entity-specific platform to the second entity-specific platform; determine a third quantity of second entity-specific tokens having an equivalent value to the second quantity of common tokens; instruct the second entity-specific ledger of the second entity to mint the third quantity of second entity-specific tokens on the second entity-specific ledger; and burn the second quantity of common tokens from the second common distributed ledger encrypted storage. ### Claim 2 (depends on 1) The system as recited in claim 1, further comprising a user-entity registry comprising a mapping of first and second encrypted storage identifiers enrolled with the common distributed ledger to the first and second entity-specific distributed ledgers enrolled with the common distributed ledger. ### Claim 3 (depends on 2) The system as recited in claim 2, wherein the controller is configured to determine the second common distributed ledger encrypted storage based on the second encrypted storage identifier and the user-entity registry. ### Claim 4 (depends on 1) The system as recited in claim 1, further comprising a first common node on the common distributed ledger, wherein the first entity-specific distributed ledger of the first entity is operatively linked to the common distributed ledger via a first common encrypted storage stored on the first common node. ### Claim 5 (depends on 4) The system as recited in claim 4, further comprising a second common node on the common distributed ledger, wherein the second entity-specific distributed ledger of the second entity is operatively linked to the common distributed ledger via a second common encrypted storage stored on the second common node. ### Claim 6 (depends on 5) The system as recited in claim 5, wherein the controller is further configured to utilize a first interoperability smart contract to instruct the first common node to burn the first quantity of first entity-specific tokens from the first entity-specific ledger. ### Claim 7 (depends on 5) The system as recited in claim 5, wherein the controller is further configured to utilize a utilize a second interoperability smart contract to instruct the second common node to mint the third quantity of second entity-specific tokens from the second entity encrypted storage. ### Claim 8 (depends on 6) The system as recited in claim 6, wherein the controller is further configured to utilize the first interoperability smart contract to instruct 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. ### Claim 9 (depends on 4) The system as recited in claim 4, 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 tokens in the first common distributed ledger encrypted storage on the membered common distributed ledger; and utilize a common interoperability smart contract to instruct the membered common distributed ledger to move the second quantity of common tokens from the first common distributed ledger encrypted storage to the second common distributed ledger encrypted storage based at least in part on the at least one operation record. ### Claim 10 (depends on 1) The system as recited in claim 1, wherein the controller is further configured to return a first confirmation that confirms transfer the second quantity of common tokens from the first common distributed ledger encrypted storage to the second common distributed ledger encrypted storage; and return a second confirmation that confirms completion of the asset transfer providing the asset to the second entity specific platform. ### Claim 11 A system for performing at least one operation regarding an asset between a first user, associated with a first entity-specific distributed ledger of a first entity, and a second user, associated with a second entity-specific distributed ledger of a second entity, wherein the first entity is different from the second entity, the system comprising: a common member platform comprising a common distributed ledger operatively linked to the first entity-specific ledger of the first entity and the second entity-specific ledger of the second entity, the common distributed ledger comprising a first common distributed ledger encrypted storage and a second common distributed ledger encrypted storage; a controller and a non-transitory computer readable storage medium storing instructions, which when operated by the controller, cause the controller to: determine a first quantity of first tokens on the first entity-specific ledger that represents an equivalence to the asset; determine a second quantity of common tokens having equivalent value to the first quantity of first entity-specific tokens; mint the second quantity of common tokens in the first common distributed ledger encrypted storage; transfer the second quantity of common tokens from the first common distributed ledger encrypted storage to the second common distributed ledger encrypted storage; instruct the first entity-specific platform to transfer the asset from the first entity-specific platform to the second entity-specific platform; determine a third quantity of second entity-specific tokens having an equivalent value to the second quantity of common tokens; and instruct the second entity-specific ledger of the second entity to mint the third quantity of second entity-specific tokens on the second entity-specific ledger. ### Claim 12 (depends on 10) The system as recited in claim 10, further comprising a first entity-specific platform comprising the first entity-specific ledger of the first entity defining a first user encrypted storage and a first entity encrypted storage. ### Claim 13 (depends on 10) The system as recited in claim 10, further comprising a second entity specific platform comprising the second entity-specific ledger of the second entity defining a second entity encrypted storage and a second user encrypted storage. ### Claim 14 (depends on 12) The system as recited in claim 12, wherein the controller is further configured to: after minting the third quantity of second entity-specific tokens on the second entity encrypted storage, transfer the third quantity of second entity-specific tokens from the second entity encrypted storage to the second user encrypted storage. ### Claim 15 (depends on 10) The system as recited in claim 10, further comprising a user-entity registry comprising a mapping of first and second encrypted storage identifiers enrolled with the common distributed ledger to the first and second entity-specific distributed ledgers enrolled with the common distributed ledger. ### Claim 16 (depends on 14) The system as recited in claim 14, wherein the controller is configured to determine the second common distributed ledger encrypted storage based on the second encrypted storage identifier and the user-entity registry. ### Claim 17 (depends on 10) The system as recited in claim 10, further comprising a first common node on the common distributed ledger, wherein the first entity-specific distributed ledger of the first entity is operatively linked to the common distributed ledger via a first common encrypted storage stored on the first common node. ### Claim 18 (depends on 16) The system as recited in claim 16, further comprising a second common node on the common distributed ledger, wherein the second entity-specific distributed ledger of the second entity is operatively linked to the common distributed ledger via a second common encrypted storage stored on the second common node. ### Claim 19 (depends on 17) The system as recited in claim 17, wherein the controller is further configured to utilize a first interoperability smart contract to instruct the first common node to burn the first quantity of first entity-specific tokens from the first entity-specific ledger. ### Claim 20 (depends on 18) The system as recited in claim 18, wherein the controller is further configured to utilize a utilize a second interoperability smart contract to instruct the second common node to mint the third quantity of second entity-specific tokens from the second entity encrypted storage. ### Claim 21 (depends on 16) The system as recited in claim 16, wherein the controller is further configured to utilize the first interoperability smart contract to instruct 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. ### Claim 22 (depends on 16) The system as recited in claim 16, 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 tokens in the first common distributed ledger encrypted storage on the membered common distributed ledger; and utilize a common interoperability smart contract to instruct the membered common distributed ledger to move the second quantity of common tokens from the first common distributed ledger encrypted storage to the second common distributed ledger encrypted storage based at least in part on the at least one operation record. ### Claim 23 (depends on 11) The system as recited in claim 11, wherein the controller is further configured to return a first confirmation that confirms transfer the second quantity of common tokens from the first common distributed ledger encrypted storage to the second common distributed ledger encrypted storage; and return a second confirmation that confirms completion of the asset transfer providing the asset to the second entity specific platform.