Mainnet setup
What is left before a token launched here shows up on GMGN by itself — and the tool that answers the hardest part of it.
Where did my ETH go?
Paste the hash of a launch transaction. This follows the money: what the launchpad took, what went to the vault, what came back, and what moves it from here.
What is left before GMGN
3 of 5Read from this deployment’s configuration and from the chain, not from a box somebody ticked. Mainnet only — no aggregator indexes a testnet.
1.The DEX router is known
Set to 0x89e5DB8B…649eba.
2.The contracts are deployed on mainnet
Factory at 0x41304fa5…34229f.
3.The app is pointed at mainnet
NEXT_PUBLIC_DEFAULT_CHAIN_ID is 4663.
4.The GMGN link is configured
The template is a fixed URL: it has no {address} in it, so every button would open the same token. Replace the address in it with {address}. Set NEXT_PUBLIC_GMGN_TOKEN_URL_4663 to https://gmgn.ai/robinhood/token/{address} — the braces stay, the app fills them.
5.A token has launched and traded
Reading the factory…
1. Paste the candidates
Search your block explorer for UniswapV2Router02 and paste everything it returns — labels, tags and all. Only the addresses are read. They all look alike in the ABI; what separates them is how much liquidity sits behind each one.
Paste at least one address above.
Your revenue
Read from the factoryFour streams, one wallet. Nothing here is claimed: the first three land in the fee recipient’s wallet as they happen; Pons fees land in a splitter and are paid out with one click by anyone.
- Creation fee
- …
- per launch, in the launch transaction
- ETH
- Trade cut
- …
- on each trade, the moment it happens
- paid in the token itself; sell it whenever you like
- LP share
- …
- when the liquidity is seeded
- LP tokens, unlocked; withdraw the liquidity on the DEX to turn them into ETH
- Pons launches
- 3% of every trade
- on each trade, into a fee splitter per creator
- 97% to the fee recipient, 3% to the token's creator; anyone can pay it out, from the dashboard
- Forging a site
- nothing — and it costs you almost nothing
- each visitor gets a couple of uses on this site’s model key
- after that they forge on their own Anthropic key, billed to them, never through you
The trade cut and the LP share are frozen into each token at birth, along with the recipient. Changing them here affects tokens launched from then on and nothing already trading.
Deploy the factory
Signed by your walletThree steps on Robinhood Chain. The first brings up the factory, the token template, the liquidity locker and the vesting vault in one go; the second points it at the DEX router; the third sets your cut of every trade and every LP. Your private key never leaves your wallet.
Use MetaMask or Rabby for this. Deploying a contract is a transaction with no recipient, and some wallets — Phantom among them — refuse those. Everything else on the site works with any wallet.
Two things you cannot undo
The router can be set once and is then frozen forever — there is no function to change it. And these contracts are unaudited. Everything below puts real money behind both facts.
Deploy the fee splitter
One transactionA Pons launch from this site pays its 3% per-trade fee to a splitter, which pays 97% to your platform wallet and 3% to the token’s creator. This factory is what addresses those splitters. Each network needs its own: deploy it on the network your wallet is on, put the address in your deploy dashboard, redeploy the site. Until then a Pons launch on that network is blocked.
Read Pons’s launch arguments
Robinhood ChainPons’s launcher is not verified on this explorer, so there is no ABI to copy. Its launch function takes a ten-field struct, four of them strings — and which string is the name rather than the image URL is not something to guess with somebody’s money in the transaction. Paste the hash of any Pons launch that worked and the values say which is which.
- Launcher
0x3a46…828c- Launch method
0xadcbd10a- Shape
- struct + 4 × uint256, payable