Your next chapter.
With a little clarity.

General migrations are not open. HANTAHOUSE has completed a one-token canary and a ten-million-token permanent migration, with a funded pool. Further holders still need passing price/depth checks and a reviewed campaign. Projects can apply now; applying does not enable transfers.

The project selects one migration model before launch. Each holder chooses whether to participate under those published terms. Holders of the same destination token do not receive conflicting return rights.

Two-way migration locks participating originals as backing for a return. Permanent migration burns participating originals. Tokens that holders do not migrate can remain on Solana, and the old market may keep trading.

Yes. The project can keep its existing name and symbol with a snapshot of available artwork, description and social links, or propose a new identity in the application. Missing source fields need to be supplied and reviewed. The original Solana mint always stays attached to the proposal. This is a project choice before deployment; holders do not choose different names for each transfer.

No. The current Genesis receiver sets its name and symbol when deployed and has no update function for them. A project approves those fields before deployment and before holders migrate. A new application does not rename the existing HANTAHOUSE contract or change its supply, token amounts or route.

Not automatically. The destination contract exposes its name, symbol and decimals; its logo, description and social links use separate metadata. Wallets, explorers and DEXes may require a token import or their own indexing before displaying the artwork. Keeping the source metadata does not copy listings or guarantee recognition by another app.

Cross-chain delivery takes verification. After a successful permanent source burn, the route must track and recover delivery of the same message. There is no Solana refund for that completed burn. If the source transaction itself fails, its burn is rolled back. The HANTAHOUSE pilot tracks the original source message through delivery; do not burn again to retry. Broader campaigns still require their own review.

We can aim to match the opening price using a fresh reference and funded liquidity. Trading then changes it. Two-way conversion can help traders narrow price gaps in both directions; a permanent route cannot close an RH discount by returning tokens to Solana.

The project, community or another willing provider supplies destination tokens and quote assets. The planned Genesis Migration Fund may cover part of the quote funding, subject to an approved cap and actual available funds.

Only assets a contributor has the right to withdraw and use can be contributed. Being the token developer does not automatically grant those rights. Original tokens backing a two-way bridge must stay in escrow and cannot also fund liquidity.

No blanket lock is promised. Every launch must publish the position owner, fees and withdrawal policy. Locking requires an actual enforced arrangement; a multisig or a label on a website is not enough.

Genesis’s own coin is planned to launch on Robinhood Chain through Pons. Its verified token address and launch date are not yet published. The proposed revenue allocation is 60% for migration liquidity, 25% for development and security, and 15% for reserves.

Bring your original mint address, public developer wallet, contact email, migration preference, destination identity choice and a liquidity proposal. Review the source metadata or prepare a new name, symbol, image and project links. Include who provides the tokens and quote assets, any requested Genesis contribution, and proposed ownership or lock terms.

Submissions and contact details stay private for review. Applying does not automatically create a public migration card or reserve a grant. Explicitly saved drafts stay on your device.

Open your private receipt in the browser you submitted from and select Refresh review status. If the reviewer requests more information, a reply form appears there. Notes and replies stay in that application; no automatic email is sent. Shortlisting means planning can continue, not that funding or transfers are approved.

Save the receipt link and use the same browser with its cookies intact. Receipt access is tied to that browser session for up to 180 days. Changing devices or clearing cookies can remove access. A saved draft is separate from a submitted application.

You need a Solana wallet for source tokens and an EVM wallet on Robinhood Chain for destination tokens. The pilot supports compatible injected EVM wallets, including Rabby and MetaMask. On mobile, use the wallet app’s browser. The pilot only accepts its configured participant addresses.

The reviewed transaction shows network and messaging costs. Solana operations use SOL, and Robinhood Chain operations use ETH. A token conversion, liquidity deposit and DEX trade are separate actions with their own costs. Genesis does not publish a fixed all-inclusive migration fee today.

No. A token and a Uniswap pool on Robinhood Chain are separate from a listing in Robinhood’s brokerage app. Genesis does not promise a brokerage listing.