How to buy BOBBY on Robinhood Chain

BOBBY is on Robinhood Chain (chain ID 4663), created by the Pons V2 launchpad on a public bonding curve. The curve is quoted in USDG, the chain's gas token is ETH, and the contract address is published on this site and on @BobbyKnitted in the same minute the token goes live.

The facts to have in front of you

The chain values above are published by Robinhood Chain's own documentation at docs.robinhood.com/chain/connecting, and were re-read from the RPC before this page was published.

1 · A wallet that holds its own keys

Any EVM wallet that accepts a custom network works — MetaMask and Rabby are two, and a hardware wallet works the same way behind them. The wallet has to be one whose keys are held by its owner, because on Robinhood Chain there is no account to recover and no support line that can move a balance.

• A rule with no exceptions: a recovery phrase or private key is never entered into a website, a wallet-connect prompt, a support chat or a form on any page, this one included.
• The recovery phrase is written down and kept offline. A phrase that exists in a screenshot, a cloud note or a chat message is a phrase someone else will eventually have.
• A wallet created by somebody else — a "managed" or "recovery" service, an assistant, a helper in a group chat — is not a wallet. Nobody from this project offers one.

2 · Adding Robinhood Chain by its RPC endpoint

The network is added by hand, from these five values, in the wallet's own network settings:

After the network is added, the wallet's network selector shows Robinhood Chain and the balance shown beside ETH is the balance that pays for transactions.

3 · ETH for gas, and USDG for the swap

Two different balances are needed, and they are not the same money:

• ETH pays for gas on every transaction. A transaction without ETH does not run at all.
• USDG is what the curve quotes in, so a curve buy is paid in USDG.

On 17 September 2026 the chain's gas price read 0.054 gwei; the exact gas cost of a trade is shown in the wallet before a confirmation is signed, and it moves with the network.

ETH reaches Robinhood Chain through the routes the chain itself documents: the canonical Arbitrum bridge between Ethereum and Robinhood Chain, where a deposit typically confirms in about ten minutes and a withdrawal is subject to the seven-day challenge period, plus the partner routes listed on the same page — LayerZero/Stargate, Chainlink CCIP/Transporter, Relay, Across, and the LiFi and 0x aggregators. USDG is listed among the assets those routes move. The list, with the exact links, lives at the chain's own bridging documentation.

A rule of transfer: an address belongs to one network. A withdrawal from an exchange reaches this chain only if the sending side lists Robinhood Chain as the destination network; sending to a chain the sending side does not support can lose the money, and no project can reverse that.

4 · The two ways a BOBBY trade happens

There are two, and which one applies depends on one number: whether the curve has completed.

5 · What is charged, and by whom

One cost that is not on that list, because a buyer never pays it: the deployment transaction cost a fixed 0.0005 ETH launch fee to the launchpad. It was paid once, by the project, when the token was created.

6 · What the project itself holds

One buy, inside the deployment transaction that created the token: 25 USDG for 7,590,278 BOBBY — 0.759% of supply, at the price every other buyer pays. That wallet is published before launch:

• Launch wallet (the opening buy): 0x42217a344bEea21b417308E798b6d03C38Fe5911
• Fee recipient, which receives the 0.70% creator share: 0xe9608248b1Cde102Fb557E7406C29Ff98805a99d

There is no reserved allocation, no presale, no whitelist and no vesting cliff: the full supply was minted to the curve, and the only position the project holds is the one it bought on that curve. Every move either wallet makes is public the second it happens, and both are listed on the verification page.

7 · Telling the real address from a copy

Copies arrive within minutes of any real launch — same name, same ticker, same art. Six checks separate them:

1. There will be exactly one BOBBY address, published here and on @BobbyKnitted at the same moment.
2. Compare the whole address, or at least its first six and last six characters, in the wallet against the address on this page. Clipboard-hijacking malware replaces a copied address with a lookalike that matches at a glance.
3. Open the address on the explorer and read the token page: total supply exactly 1,000,000,000, creator tax 0%, no transfer tax. A token with a different supply is not this token.
4. The largest project wallet holds 7,590,278 BOBBY (0.759%), bought in the deployment transaction. Any wallet that received tokens at creation is not part of this launch.
5. A token that is not at that address is somebody else's, whatever it is named and whatever it shows as a price.
6. No claim step exists. There is no airdrop, no claim page, no staking contract, no "connect to receive" step — the only transaction a buyer makes is the swap. An approval requested in BOBBY's name is a drain.

8 · If a post claims a listing, a partnership or a migration

The wording to recognise, because these are the same four scripts every time:

• "New contract" / "v2" / "migrate your tokens" — a migration asks the holder to approve an unlimited spend and send the balance to a new contract. That approval is what empties the wallet.
• "Claim your airdrop" / "connect your wallet to receive" — nothing is claimable here, so any claim page is a lie about this project.
• "Listed on an exchange" / "partnership with X" — no listing and no partnership is published by this project. A listing announcement that does not come from this site and @BobbyKnitted is not one.
• "Support" or "recovery" contact in a direct message — nobody from this project ever messages first, anywhere.

What to do instead of acting on the post: read the two places the project publishes (this site and @BobbyKnitted), check the address on the chain, and treat the post as hostile until the chain says otherwise. A correction or a warning is published in the same two places, with the account tagged.

9 · What can go wrong

Nothing on this page is a forecast, and these are the specific ways a buyer loses:

• The price can fall, and stay down. Meme coins are volatile and many go to zero. The token has no utility and no revenue of its own, so nothing underneath it earns the price back.
• The opening three seconds are hostile by design. A buy in the first instant pays a 98% anti-snipe tax, and it is still 6.18% one second later. The tax exists to make the first seconds worthless to a sniper — which also means it is the worst moment for anyone else to buy.
• The curve is not an exit all the way to the top. The curve's sell function refuses once graduation is ready, so sells stop on the curve and continue in the pool, where depth — not intention — sets what a large sale can get.
• Every transaction can fail and still cost gas. A failed transaction is paid for. Gas price also moves.
• The wallet is the whole security boundary. A stolen recovery phrase, a wallet used on a hostile site, or an approval signed into the wrong contract loses money with no recourse — the contract has no admin path over holder balances and no project can reverse a transaction.
• The public RPC is rate-limited. A wallet reading through an overloaded endpoint can show a stale price or a pending state that is no longer true.
• Copies and DMs are the standard attack. Both are covered above, and both work on urgency: a claim, a migration and a listing offer are all built to be acted on in a hurry.
• The project itself can sell. Its 0.759% is a real position and its plan includes selling into strength, in pieces, from the published wallet. That is why the wallet is published: so the movement is visible rather than discovered.
• The joke can stop being funny. The one risk a meme coin cannot be engineered out of is that the volume leaves. Nothing in the contract prevents it, and no page can promise against it.

Verify the contract yourself → Read the FAQ