$BV7X is migrating from Base to Robinhood Chain. The migration runs on migrate.fun, which holds the escrow and issues the receipt, and it is a two-step process: you migrate now on Base and receive a receipt token, then you claim the new token on Robinhood Chain after the window closes. Both steps are yours to make — nothing is airdropped to you, and nothing happens to your tokens if you do nothing. The announcement, and why the token is moving at all, is in the previous post; this is the guide it promised.
The window
| Stage | When | What |
|---|---|---|
| Migration opens | 9 Sep 2026, 08:00 UTC | Live now. Migrate at the full rate and receive an MFT receipt. |
| Migration closes | 16 Sep 2026, 08:00 UTC | The full rate ends here. |
| Claims open | After the close | Exchange your MFT for the new token on Robinhood Chain. The project page states no deadline — claim promptly regardless, and see the note below. |
| Late migration | After the close | Still possible on Base, at a 10% reduction. No end date published. |
Both timestamps are UTC. The one that matters is 16 September, 08:00 UTC — migrate before it and you get the full rate, migrate after it and you get 10% less.
The contracts
Three token contracts are involved across two chains. The old token and the receipt live on Base; the new token lives on Robinhood Chain.
| Role | Chain | Contract |
|---|---|---|
| Old token BV7X · ERC-20 · 18 dec | Base 8453 | 0xD88FD4a11255E51f64f78b4a7d74456325c2d8dC"BitVault Signal" — the token you hold today. 100,000,000,000 total supply. |
| Receipt token MFT-b8bfcd0c35e169d1 · ERC-20 · 18 dec | Base 8453 | 0x47E08dBB3Aa7F3259EbA911316431fb8…Minted to you when you migrate. This is your claim on the new token. |
| New token BV7X · ERC-20 · 18 dec | Robinhood Chain 4663 | 0x459476869aF797Eb9061B41fA04dE46A…What you claim with your MFT once claims open. |
| Project ID | — | 0xb8bfcd0c35e169d1b3d2c219e77f045e698da999dc9f46c4f53b270a7e5a4ab0 |
| Admin | Base 8453 | 0xd8B71d23e1a8da9867497C0E757A1143B94C3e1eThe same wallet that has signed the protocol's on-chain attestations since February. |
The receipt and new-token addresses above are shown truncated because that is how the project page displays them, and a token address is the one thing you should never take from a blog post, a DM or a search result. Open the project page, use its copy button, and check the first and last four characters against what your wallet shows you before you sign.
The platform, and what has been audited
migrate.fun is built by Emblem Vault and has been running since July 2025, moving token liquidity across Solana, Ethereum, BNB, Base and Robinhood Chain. It has been audited by Halborn — a security assessment run from 19 August to 12 September 2025, scoped to the hustle-migration program in Emblem's repository. Halborn's recommendations were addressed by the team: validating that the new-token amount is greater than zero, adding explicit checks that separate protected from unprotected projects before emergency_withdraw can be called, and correcting how finalize_swap updates the refund accounting. The report is public at halborn.com.
The assessment names the hustle-migration program, which is the Solana side of the platform. This migration is Base to Robinhood Chain, so the contracts your tokens actually pass through are the EVM ones, and nothing published states they were the artifact Halborn reviewed. Take it as what it is — a real third-party assessment of the platform, addressed and closed — rather than a line-by-line review of the two contracts in the table above. It is a reason for more confidence, not a reason to skip the checks in this guide.
The rate: 100 to 1
The exchange rate is 100 old BV7X to 1 new BV7X. A hundred thousand tokens on Base becomes a thousand tokens on Robinhood Chain, and the 100,000,000,000 supply becomes 1,000,000,000. This is a redenomination, so what you own is unchanged in every respect except the unit it is counted in — the number in your wallet gets two decimal places shorter and nothing else about your position moves.
Migrating, step by step
- Open the BV7X project page on migrate.fun and connect the wallet that holds your BV7X. It must be a wallet you control the keys to.
- Make sure the wallet is on Base (chain ID
8453) and holds a little ETH for gas. The first step happens entirely on Base. - Enter the amount and approve the migration contract to spend your BV7X. This is a standard ERC-20 approval and moves nothing on its own.
- Migrate. Your old BV7X goes into escrow and the MFT receipt is minted to the same wallet in the same transaction.
- Add the MFT to your wallet's token list so you can see it, and leave it where it is. It is the only thing that proves what you are owed.
- After 16 September, 08:00 UTC, return to the project page, switch to Robinhood Chain (chain ID
4663) and claim. The MFT is consumed and the new BV7X arrives.
Robinhood Chain network details
| Chain ID | 4663 (hex 0x1237) |
| RPC | https://rpc.mainnet.chain.robinhood.com |
| Explorer | https://robinhoodchain.blockscout.com |
If your BV7X is staked, unstake first
This is the step most holders will miss. 37,988,627,830 BV7X — about 38% of the entire supply — is currently staked in the MultiRewards contract at 0xfd991bC5A8a864F37D4Ef8E119e932D9a7D90E41 on Base. Staked tokens are held by that contract, not by you, so the migration cannot see them and cannot move them.
To migrate a staked balance you have to withdraw it to your own wallet first, at app.bv7x.ai/compute, and claim any rewards owed to you while you are there. Then migrate as above. The staking contract itself is audited, immutable and unaffected by the migration — this is about where your tokens physically sit on the day the window closes, not about the contract changing.
If you miss the window
Missing 16 September, 08:00 UTC is recoverable and it is not free. Late migration stays open on Base at a 10% reduction — you receive 90% of what you would have received during the window — and no end date has been published for it. Claiming is the opposite in one respect — once your MFT is minted, exchanging it carries no penalty whatever — but do not read that as unlimited time.
The BV7X project page states that claims have no deadline. Emblem's own platform documentation describes something different: a 90-day claim window after migration ends, with unclaimed tokens returning to the project admin. We cannot reconcile those two from the outside, and the difference is the whole of your position, so treat the shorter one as if it binds — claim as soon as claims open. Holding an MFT is not holding the new token, and nothing is lost by exchanging it early.
The asymmetry that does hold: step one has a hard, priced deadline, and step two does not reward waiting.
Four things that cost tokens
- Migrating from an exchange. A CEX deposit address is not your wallet. Tokens sent from one, or held on one during the migration, cannot receive an MFT and there is no support desk that can reverse it. Withdraw to a wallet you hold the keys to and migrate from there. If your BV7X is on an exchange, that withdrawal is the first thing to do, not the last.
- Selling or sending your MFT. It is a transferable ERC-20, which means it can be sold, and whoever holds it at claim time is who gets the new token. Treat it the way you would treat a bearer receipt.
- Claiming on the wrong network. The claim is on Robinhood Chain, chain ID
4663. Add the network from the details above rather than from a search result, and confirm the chain ID your wallet reports before signing. - Leaving BV7X in a liquidity position. LP tokens are not BV7X, and the pool cannot migrate on your behalf. Withdraw the position first if you want the underlying migrated.
Liquidity on the other side will sit in a Uniswap V4 pool on Robinhood Chain. The project page lists it as pending while the migration is in its first days, which is expected — the pool is seeded around the close, not at the open.
What this does not change
This is a migration of the token. The arena, the strategy agents and the on-chain attestation record are not part of it: the first-party oracle continues attesting on Base, agents continue predicting on their existing rails, and staking on Base is untouched by anything described here. If and how the protocol itself follows the token is a separate question with its own answer, and we will not pre-empt it in a migration guide.
Questions
The project page carries the live state — how much has migrated, which stage is current, and the countdown to the close. If something in this guide disagrees with what the dApp shows you, the dApp is right: it reads the contracts, and this is a document. Ask in the group or reply on the thread and we will answer.