TCu29 is migrating from BNB Chain to Ethereum. The move consolidates TCu29 on a single chain as an ERC-20 token, aligning with the token design set out in the whitepaper and improving liquidity and institutional accessibility. The migration is 1:1: every token you hold on BNB Chain becomes the same amount of ERC-20 TCu29 on Ethereum. You pay only network gas, and a typical claim completes in about a minute. The migration window opens May 15, 2026 and closes around August 13, 2026.
Who needs to act
If you hold TCu29 on a centralized exchange, you generally do not need to do anything, since the exchange handles the migration for you (confirm the details with your exchange). If you self-custody with a wallet like MetaMask, Rabby, Trust, or a hardware wallet, or you hold TCu29 inside a DeFi position, you run the four-step migration yourself before the window closes. If your tokens are in a liquidity pool or another DeFi position, unwind that first so the tokens sit in a wallet you control.
Before you start
Have three things ready: the wallet that holds your TCu29 on BNB Chain, a small amount of BNB for gas (it covers the Approve and Migrate steps), and confirmation that your destination address is one you control on Ethereum. If your BNB-Chain address is a smart-contract wallet such as Safe or Argent, the same address on Ethereum may have different signers, so double-check that you control it before migrating.
The migration, step by step
Connect. Open the migration page and connect your wallet. The site detects your TCu29 balance on BNB Chain automatically.
Approve. Authorize the bridge to move your tokens. Check that the spender is the official TCu29 bridge contract, and set the amount to your balance. Avoid an unlimited approval unless you understand the trade-off.
Migrate. Lock your TCu29 on BNB Chain. Your BNB-Chain balance drops to zero and the lock is recorded on-chain for verification.
Claim. Once the relayer confirms your lock, switch your wallet to Ethereum and claim the equivalent amount of ERC-20 TCu29, allocated to the same address you migrated from.
Key things to know
It is a lock-and-claim, not a swap: 1:1, with no slippage, no price impact, and no AMM involved. Your Ethereum claim is always allocated to the same address you migrated from. Approve and Migrate must happen in order on BNB Chain (chain ID 56); Claim happens on Ethereum (chain ID 1), any time after the lock confirms.
If something goes wrong
A wrong-network prompt simply means you need to switch chains (BNB Chain for Approve and Migrate, Ethereum for Claim), and the site prompts you automatically. If Migrate is greyed out after Approve, refresh and reconnect so the site re-reads your allowance from the chain. If your claim never appears, open the bridge scanner, look up your address, and check relayer health; the claim activates once the relayer attests to your lock. If you are unsure which address you used, or you hold via a smart-contract wallet and are not certain you control it on Ethereum, pause and confirm before continuing.
Stay safe from phishing
Before signing anything, verify three things: that the site URL matches the one published in official channels character-for-character, that the contract address shown in your wallet matches the bridge contract in the official announcement, and that your wallet shows you on BNB Chain (chain ID 56) for the first two steps. The flow only ever asks for transaction signatures, never a seed phrase. If the site looks even slightly different than usual, stop and treat it as a phishing risk.
Timeline
The migration window opens May 15, 2026 and closes around August 13, 2026. We recommend completing your migration at least a week before the deadline to avoid last-minute network congestion. You can track your migration status at any time through the bridge scanner.
