IP Library › Granted Patent US 12,657,582
Granted Patent B2
US 12,657,582 · App. 18/455,398 · Granted Jun 16, 2026

Converting bridged tokens to native tokens on a blockchain

Inventors: Long Nguyen (Boston, MA); Adrian Soghoian (Brooklyn, NY); Boyan Lin (Woodside, CA); Marcus Boorstin (Somerville, MA); James Hinck (Brooklyn, NY)
Assignee: CIRCLE INTERNET GROUP, INC.
G06Q20/3825G06Q20/389G06Q2220/00
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,657,582
App. No.
18/455,398
Granted
Jun 16, 2026
Kind
B2
Abstract

Certain aspects of the present disclosure provide techniques for converting a bridged token on a blockchain to a native token on the blockchain. An example method generally includes pausing a token bridge between a first blockchain and a second blockchain. Minting privileges on the second blockchain are adjusted such that a designated user is granted privileges to control token minting on the second blockchain and no other users are allowed to control token minting on the second blockchain. It is validated that a quantity of a bridged token has remained unchanged since a freeze time at which the token bridge was paused. Based on validating that the quantity of the bridged token has remained unchanged since the freeze time, the bridged token is converted to a native token existing on the second blockchain.

Claims (61)

1 . A processor-implemented method, comprising:

pausing a token bridge between a first blockchain and a second blockchain;

adjusting minting privileges on the second blockchain by:

granting a designated user exclusive privileges to control token minting on the second blockchain,

revoking at least minting privileges from parties other than the designated user, and

granting zero-allowance minting privileges to a designated token burning entity;

validating that a quantity of a bridged token has remained unchanged since a freeze time at which the token bridge was paused;

based on validating that the quantity of the bridged token has remained unchanged since the freeze time, converting the bridged token to a native token existing on the second blockchain; and

revoking zero-allowance minting privileges from the designated token burning entity subsequent to converting the bridged token.

2 . The method of claim 1 , wherein pausing the token bridge between the first blockchain and the second blockchain comprises:

locking a quantity of extant tokens on the first blockchain and a corresponding quantity of extant bridged tokens on the second blockchain; and

finalizing pending transactions using the bridged token on the first blockchain and the second blockchain.

3 . The method of claim 1 , further comprising:

retrieving, from the first blockchain and the second blockchain, transaction records related to transactions using the bridged token;

calculating a quantity of extant tokens on the first blockchain based on the transaction records retrieved from the first blockchain;

calculating a quantity of extant bridged tokens on the second blockchain based on the transaction records retrieved from the second blockchain; and

verifying that the quantity of extant tokens on the first blockchain matches the quantity of extant bridged tokens on the second blockchain.

4 . The method of claim 3 , wherein converting the bridged token to the native token is further based on verifying that the quantity of extant tokens on the first blockchain matches the quantity of extant bridged tokens on the second blockchain.

5 . The method of claim 1 , further comprising:

validating a contract defining the bridged token against one or more reference contracts, wherein converting the bridged token to the native token is further based on validating the contract.

6 . The method of claim 1 , further comprising:

based on failing to validate that the quantity of the bridged token has remained unchanged since the freeze time, restoring minting privileges to other users on the second blockchain and unpausing the token bridge between the first blockchain and the second blockchain.

7 . The method of claim 1 , wherein the designated token burning entity comprises a smart contract associated with the token bridge.

8 . The method of claim 1 , wherein converting the bridged token to a native token existing on the second blockchain comprises executing one or more update operations defined in a smart contract to convert the bridged token to the native token.

9 . The method of claim 1 , wherein converting the bridged token to a native token existing on the second blockchain comprises burning tokens on the first blockchain corresponding to the bridged token on the second blockchain.

10 . A processing system, comprising:

a memory having executable instructions stored thereon; and

one or more processors configured to execute the executable instructions in order to cause the processing system to:

pause a token bridge between a first blockchain and a second blockchain;

adjust minting privileges on the second blockchain by:

granting a designated user exclusive privileges to control token minting on the second blockchain;

revoking at least minting privileges from parties other than the designated user, and

granting zero-allowance minting privileges to a designated token burning entity;

validate that a quantity of a bridged token has remained unchanged since a freeze time at which the token bridge was paused;

convert, based on validating that the quantity of the bridged token has remained unchanged since the freeze time, the bridged token to a native token existing on the second blockchain; and

revoke zero-allowance minting privileges from the designated token burning entity subsequent to converting the bridged token.

11 . The processing system of claim 10 , wherein to pause the token bridge between the first blockchain and the second blockchain, the one or more processors are configured to cause the processing system to:

lock a quantity of extant tokens on the first blockchain and a corresponding quantity of extant bridged tokens on the second blockchain; and

finalize pending transactions using the bridged token on the first blockchain and the second blockchain.

12 . The processing system of claim 10 , wherein the one or more processors are further configured to cause the processing system to:

retrieve, from the first blockchain and the second blockchain, transaction records related to transactions using the bridged token;

calculate a quantity of extant tokens on the first blockchain based on the transaction records retrieved from the first blockchain;

calculate a quantity of extant bridged tokens on the second blockchain based on the transaction records retrieved from the second blockchain; and

verify that the quantity of extant tokens on the first blockchain matches the quantity of extant bridged tokens on the second blockchain.

13 . The processing system of claim 12 , wherein the one or more processors are configured to convert the bridged token to the native token further based on verifying that the quantity of extant tokens on the first blockchain matches the quantity of extant bridged tokens on the second blockchain.

14 . The processing system of claim 10 , wherein the one or more processors are further configured to cause the processing system to:

validate a contract defining the bridged token against one or more reference contracts, wherein the one or more processors are configured to cause the processing system to convert the bridged token to the native token is further based on validating the contract.

15 . The processing system of claim 10 , wherein the one or more processors are further configured to cause the processing system to:

based on failing to validate that the quantity of the bridged token has remained unchanged since the freeze time, restore minting privileges to other users on the second blockchain and unpause the token bridge between the first blockchain and the second blockchain.

16 . The processing system of claim 10 , wherein the designated token burning entity comprises a smart contract associated with the token bridge.

17 . The processing system of claim 10 , wherein to convert the bridged token to a native token existing on the second blockchain, the one or more processors are configured to cause the processing system to execute one or more update operations defined in a smart contract to convert the bridged token to the native token.

18 . The processing system of claim 10 , wherein to convert the bridged token to a native token existing on the second blockchain, the one or more processors are configured to cause the processing system to burn tokens on the first blockchain corresponding to the bridged token on the second blockchain.

19 . A non-transitory computer-readable medium having executable instructions stored thereon which, when executed by one or more processors, causes the one or more processors to perform an operation comprising:

pausing a token bridge between a first blockchain and a second blockchain;

adjusting minting privileges on the second blockchain by:

granting a designated user exclusive privileges to control token minting on the second blockchain,

revoking at least minting privileges from parties other than the designated user, and

granting zero-allowance minting privileges to a designated token burning entity;

validating that a quantity of a bridged token has remained unchanged since a freeze time at which the token bridge was paused;

based on validating that the quantity of the bridged token has remained unchanged since the freeze time, converting the bridged token to a native token existing on the second blockchain; and

revoking zero-allowance minting privileges from the designated token burning entity subsequent to converting the bridged token.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 23, 2026
From: NGUYEN, LONG; SOGHOIAN, ADRIAN; LIN, BOYAN; BOORSTIN, MARCUS; HINCK, JAMES
To: CIRCLE INTERNET GROUP, INC.
Reel/Frame 074151/0368 →
Continuity (2)
Provisional Application 63515910 · Jul 27, 2023
Related Publication 20250037119A1 · Jan 30, 2025
References Cited (30)
US 5892900A · Ginter · 1999 [cited by examiner]
US 11880836B1 · Nemethi · 2024 [cited by examiner]
US 20200013027A1 · Zhu · 2020 [cited by examiner]
US 20200143471A1 · Jackson · 2020 [cited by examiner]
US 20200328892A1 · Gangal · 2020 [cited by examiner]
US 20210241243A1 · Wiklof · 2021 [cited by examiner]
US 20220337439A1 · McCOY · 2022 [cited by examiner]
US 20220351186A1 · Quigley et al. · 2022 [cited by applicant]
US 20230006976A1 · Jakobsson · 2023 [cited by examiner]
US 20230018175A1 · Kaplan · 2023 [cited by examiner]
US 20230205784A1 · Dusek · 2023 [cited by examiner]
US 20230334470A1 · Beller · 2023 [cited by examiner]
US 20230367776A1 · Padmanabhan · 2023 [cited by examiner]
US 20230367788A1 · Grant · 2023 [cited by examiner]
US 20230401580A1 · Forson · 2023 [cited by examiner]
US 20240037537A1 · Kleinman · 2024 [cited by examiner]
US 20240146554A1 · Shetty · 2024 [cited by examiner]
US 20240202679A1 · Mayerchak · 2024 [cited by examiner]
Multichan.org, “Multichain,” retrieved from https://web.archive.org/web/20230607183944/https://docs.multichain.org/getting-started/introduction on Jun. 7, 2023 (Year: 2023). [cited by examiner]
K.-E. Marstein, A. Chiriac, L. Riley, T. Hardjono and G. Verdian, “Implementing Secure Bridges: Learnings from the Secure Asset Transfer Protocol,” 2023 IEEE International Conference on Blockchain and Cryptocurrency (IC… [cited by examiner]
Patrick McCorry et al, “SoK: Validating Bridges as a Scaling Solution for Blockchains,” (Year: 2021). [cited by examiner]
P. Merrill, T. Austin, J. Thakker, Y. Park and J. Rietz, “Lock and Load: A Model for Free Blockchain Transactions through Token Locking,” 2019 IEEE International Conference on Decentralized Applications and Infrastructu… [cited by examiner]
Cronje, A, “AnyswapV5ERC20.sol” retrieved on May 20, 2021, from https://github.com/connext/chaindata/commits/main/AnyswapV5ERC20.sol (Year: 2021). [cited by examiner]
Zhaojun-sh, “Update AnyswapV6ERC20.sol,” retrieved on Feb. 25, 2022 from https://github.com/anyswap/chaindata/commits/main/AnyswapV6ERC20.sol (Year: 2022). [cited by examiner]
OpenZepellin, “Access control,” retrieved from https://web.archive.org/web/20230521044909/https://docs.openzeppelin.com/contracts/4.x/access-control#granting-and-revoking on May 21, 2023, 2023, (Year: 2023). [cited by examiner]
Llamarisk, “Cross-Chain Gauges & Ecosystem Assessment: Multichain,” retrieved on Mar. 19, 2023 from https://web.archive.org/web/20230319173155/https://cryptorisks.substack.com/p/cross-chain-gauges-and-ecosystem (Year: 2… [cited by examiner]
X. Niu, L. Kong, F. Jin, X. Song, X. Min and Q. Li, “NFT Cross-Chain Transfer Method Under the Notary Group Scheme,” 2023 26th International Conference on Computer Supported Cooperative Work in Design (CSCWD), Rio de Ja… [cited by examiner]
PCT/US2024/037500, International Search Report and Written Opinion dated Oct. 2, 2024, 15 pages. [cited by applicant]
Lucius Fang et al., How to DEFI (Advanced, May 31, 2021, CoinGecko, 289 pages. [cited by applicant]
Ivanov Nikolay et al., Rectifying Administrated ERC20 Tokens, Sep. 17, 2021, 16 pages. [cited by applicant]