Bring the familiar details.
Keep the existing name and symbol, with a snapshot of available artwork, description and social links. Review the imported details and supply anything the source does not provide.
HOW GENESIS WORKS
The project chooses its route before launch. Holders choose whether to move. Everyone who migrates that coin gets the same terms.
03 / CHOOSE YOUR DIRECTION
A new market or a new home.
The project sets the route. Holders opt in.
Participating tokens are locked on Solana. They back the matching tokens you receive on Robinhood Chain.
FROM APPLICATION TO ARRIVAL
Identify the original token, choose a migration type and destination identity, and propose who will fund the new pool. Ownership and token settings must be verified before launch.
The destination name and symbol, token contract, migration model, and liquidity terms are confirmed before migrations open. A two-way project cannot quietly remove holders’ return rights.
Each holder reviews the project’s terms and approves their own migration. Originals are locked for a two-way bridge or burned for a permanent migration.
After the source transaction and cross-chain message are verified, matching RH tokens arrive in the holder’s destination wallet. A funded Uniswap v4 pool lets people trade them for ETH.
YOUR TOKEN’S IDENTITY
Keep the existing name and symbol, with a snapshot of available artwork, description and social links. Review the imported details and supply anything the source does not provide.
Propose a new name, symbol, image and project links in the application. The original Solana mint stays attached to the proposal so holders can verify which token they are migrating.
The project confirms the name and symbol before the destination contract is deployed. Every migrating holder receives that same token. An application does not rename an existing deployed token.
Artwork and project links live in separate metadata. Wallets, explorers and trading apps may need their own token import or indexing before the new image appears.
THE NEW MARKET
The developer, treasury, community, or another liquidity provider supplies RH tokens they own alongside ETH. New buyers can trade on Robinhood Chain without visiting Solana.
The provider owns the liquidity position and can normally withdraw it unless a separate lock is arranged. That policy should be visible before launch.
Genesis’s planned Migration Fund will use part of its own coin’s collected creator revenue to help approved projects with a capped initial contribution.
Explore matching support See how the opening price worksThe proposed exchange is 1:1 in token units. Liquidity, demand, fees, and trading determine price; a matching dollar value is never guaranteed.
Unmigrated tokens and the old pool can remain on Solana. A permanent migration only destroys the originals that holders choose to migrate.
Cross-chain transfers are asynchronous. Permanent burns cannot be refunded on Solana; tracking and recovery of delayed destination delivery must be tested before launch.
A Uniswap pool on Robinhood Chain does not automatically list the coin in the Robinhood brokerage app.
HANTAHOUSE has completed a one-token canary and a ten-million-token permanent migration, with a funded pool. Further holders still need passing price and depth checks and a reviewed campaign. The two-way bridge has passed public testnet testing. General migrations are not open; applications and destination identity proposals are open for review.
View the HANTAHOUSE console Read the build notesA FEW THINGS TO KNOW
Each project shows completed milestones divided by its total milestones. HANTAHOUSE tracks five milestones covering delivery, its pool, price alignment and trading depth. Percentages do not measure token value, market cap, or the share of supply migrated.
Only when a funded market exists. A developer, treasury, community or other provider must supply the tokens and quote asset for the new pool. Migration and pool funding are separate transactions; a funded pool still needs adequate trading depth.
Applications are private submissions for review. Submitting does not publish your contact details, approve your project, or automatically create a public migration card.