Move your project
Already live on another chain?
Bring it to Chaingentic.
Your project runs on Base, Polygon or another EVM chain. Enter a contract address and we read it on that chain: how it was deployed, what it depends on, and what moves with it. You then redeploy from your own wallet.
Step 1
Check your project.
Reading a contract changes nothing on either chain and needs no wallet. Check each contract your project uses: the token, the main contract and any proxy.
Step 2
Take a snapshot of your holders.
We read every transfer of your token on its current chain, up to a block you choose, and work out each holder's balance at that block. The snapshot is sealed with one fingerprint (a Merkle root), and each holder gets a short proof of their own balance. Anyone can rebuild the same snapshot from the same chain and check it.
Step 3
Redeploy through the mint gate.
Every contract born on Chaingentic goes through the mint gate. The AI Consensus reads the exact code you send. If it is clean, the gate deploys exactly that code from your own wallet and records that it was born clean. If it is not, nothing is deployed. If Step 1 found a contract deployed directly by a wallet, its original code is filled in below. Change any address inside it that points to your other contracts to their new Chaingentic addresses before you send it.
Step 4
Open the claim for your holders.
The claim contract holds your token on Chaingentic and lets each holder in your Step 2 snapshot claim exactly their balance, once. It goes through the same mint gate. When the claim window closes, you can take back whatever was not claimed.
Step 5 · For holders
Claim your balance on Chaingentic.
Paste the claim contract address the project gave you. We read which token and block it was set up for, rebuild that snapshot from the original chain, and check it matches the fingerprint stored in the contract. Then your wallet claims your balance to your own address. You pay only the network fee.
How a migration works
What moves, and how.
Your contracts, from your wallet
Every contract born on Chaingentic goes through the mint gate. The AI Consensus reads the exact code first, and the gate deploys exactly what it read. A contract that does not pass is never deployed. Addresses inside your code that point to your other contracts are swapped for their new Chaingentic addresses. You deploy from your own wallet and pay your own network fee.
Your holders, in a snapshot
Token balances move by a snapshot taken on your current chain at a recorded block. Each holder then claims their own balance on Chaingentic.
One address map
Every old address is listed beside its new Chaingentic address, so your users, partners and front end can switch over with confidence.
Some things don't move on their own: open positions, vesting schedules, roles and settings stored inside a contract. The check lists them so you can set them again after you deploy. Your contracts on the original chain keep running until you choose otherwise.
Chaingentic runs as a testnet today, so you can rehearse your whole migration now with test funds. Real value moves when mainnet opens. Every step on this page is live on the testnet. During testnet our team runs the mint-gate check with you: write to us when your contracts are ready.
Network settings
Point your tools here.
Point your wallet and tools here. New contracts go through the mint gate rather than straight to the network. A plain contract deployment sent to this RPC is stopped unless you have chosen to be told about flagged transactions instead.
- Network
- Chaingentic Testnet
- Chain ID
- 1002
- Currency
- AIERC
- RPC
- https://rpc.chaingentic.app/v1/chaingentic
- Explorer
- testnet.chaingenticscan.com