Migrate your TCu29 from BNB Chain to Ethereum
A user guide to the 1:1 TCu29 migration. Read this before you connect a wallet.
At a glance
| What | 1:1 swap of TCu29 from BNB Chain to Ethereum |
| Window | 90 days, opens May 15, 2026 (closes ~August 13, 2026) |
| You pay | Network gas only (BNB for lock, ETH for claim) |
| Migration site | https://tcu29.io/migration |
| Bridge Scanner | https://tcu29.io/scan |
Do you need to do anything?
Holding on Phemex (or another supported CEX) - No action required.
Your balance is migrated automatically and credited as Ethereum TCu29.
Holding in a self-custody wallet (MetaMask, Rabby, Trust wallet, hardware wallet) - Yes.
You must run the 4-step migration yourself before the window closes.
Holding inside a DeFi position (LP) - Yes but unwind first.
Withdraw the underlying TCu29 to your wallet, then migrate. Tokens locked in third-party contracts cannot be migrated for you.
Before you start
Have these ready:
- The wallet that holds your TCu29 on BNB Chain
- A small amount of BNB for gas on BNB Chain (covers Approve + Migrate)
- A small amount of ETH for gas on Ethereum (covers Claim)
- Confirmation that the destination address is one you control on Ethereum. If your BNB-Chain address is a smart contract (Safe, Argent, etc.), the same address on Ethereum may have different signers - double-check before migrating.
Sanity checks:
- The site URL exactly matches the one published in official channels
- The contract address shown in your wallet matches the bridge contract address published in the official announcement
- Your wallet shows you on BNB Chain (chain ID 56) for the first two steps
- You are not being asked for a seed phrase. The flow only ever asks for transaction signatures.
The migration, step by step
The site shows a progress bar at the top: Connect → Approve → Migrate → Claim.
1Connect
Open the migration page and click Connect Wallet. Approve the connection in your wallet. The site detects your TCu29 balance on BNB Chain and prompts you to switch networks if needed.
2Approve
A one-time on-chain approval that lets the bridge contract move your TCu29 out of your wallet. Confirm in your wallet. Costs a few cents of BNB.
In the wallet prompt, verify:
- Spender = the official TCu29 bridge contract
- Amount = your balance (avoid unlimited approval unless you understand the trade-off)
3Migrate
Click Migrate. This calls the bridge contract on BNB Chain and locks your TCu29. Confirm the transaction. Once it confirms, your BNB-Chain balance drops to zero and the lock is recorded on-chain - you now have a verifiable claim to the same amount on Ethereum.
4Claim
After the BNB-Chain lock confirms, the relayer picks up the event and makes the matching amount claimable on Ethereum. The site switches you to Ethereum and shows Claim. Confirm in your wallet to receive your ERC-20 TCu29.
The whole flow typically takes ~60 seconds. Most of that is block confirmations on both chains.
If something looks stuck: the Bridge Scanner
The Bridge Scanner (/scan) is the public source of truth for the relayer.
- Relayer Health - shows whether the off-chain relayer is up and processing events. If it's degraded, claims may queue briefly. Your lock is still on-chain and remains claimable.
- Wallet Lookup - paste your address to see your lock, the relayer attestation, and your claim status.
Use the Scanner when:
- The site hangs between Migrate and Claim
- You closed the tab after Migrate and need to come back later to Claim
- You want to confirm a claim was credited to the correct Ethereum address
- You want to verify the relayer is healthy before starting
Things to consider
Same wallet, both chains. Your Ethereum claim is allocated to the same address you migrated from. EOAs (MetaMask, Ledger, Trezor) work the same on both chains. Smart-contract wallets (Safe, Argent) may not - confirm you control the same address on Ethereum before migrating.
You can split the flow over time. Approve and Migrate must happen in order on BNB Chain. Claim can happen any time after the lock confirms, as long as you're still inside the 90-day window. Closing the tab is fine - come back via the Scanner.
Don't push it to the deadline. The window closes ~August 13, 2026. Migrating in the final hours leaves no margin if you hit a network issue, a relayer hiccup, or a wallet problem. Aim to be done at least a week before.
It's not a swap, it's a 1:1 lock-and-claim. No slippage, no price impact, no AMM. The amount in equals the amount out.
Gas on both chains. Don't start with an empty BNB or empty ETH balance. Top up before connecting.
Troubleshooting
| Symptom | What to do |
|---|---|
| "Wrong network" prompt | Switch to BNB Chain (56) for Approve + Migrate, Ethereum (1) for Claim. The site prompts automatically. |
| Approve confirmed, Migrate greyed out | Refresh and reconnect. The site re-reads allowance from chain. |
| Migrate confirmed, Claim never appears | Open /scan, look up your address, check relayer health. Claim activates once the relayer attests. |
| Lost which address you used | /scan → Wallet Lookup with each candidate address. |
| Site looks slightly different than usual | Stop. Verify the URL character-for-character against the official announcement. Treat anything unusual as a phishing risk. |
| Smart-contract wallet, unsure about Ethereum control | Do not migrate. Confirm signer setup on Ethereum first, or migrate from an EOA you fully control. |
TL;DR
- CEX user? Do nothing. Phemex handles it.
- Self-custody holder? Go to /migration → Connect → Approve → Migrate → Claim. ~60 seconds.
- Anything weird? Check /scan.
- Deadline: ~90 days from May 15, 2026. Don't wait until the last day.