HYPED
HYPED
Robinhood Chain → HyperEVM
A token that trades on Robinhood Chain and pays its holders in native HYPE on HyperEVM. Two chains, one loop, no claim button to forget about.
Contract: loading…
Robinhood Chain has no idea HYPE exists. It pays creator fees in ETH and stops there. Everything after that is a bot we run, on purpose, in public.
A 1% fee is collected on every trade by the PONS locker on Robinhood Chain. Read on-chain, not from a marketing deck: locker.feeBps() = 100.
Their operator sweeps fees into an escrow contract and credits the creator. Measured from a real sweep: 92.5% to the creator, 7.5% to the protocol.
Our bot calls escrow.claim() and pulls that ETH out. It knows the exact amount before it moves — it reads escrow.balanceOf(), it doesn't guess from a wallet balance.
80% is the holder pot. 20% stays with the keeper for marketing and gas. That split is ours, not the protocol's, and it's stated up front rather than discovered later.
The holder pot crosses 4663 → 999 through Relay in a single step, about 3 seconds, and lands as native HYPE.
Holders are snapshotted pro-rata and HYPE is sent directly to their wallets. No claim page. Nothing expires. Nothing to sign.
If you see a bigger number on a site like this one, ask which of those three factors they quietly rounded up.
Pulled from stats.json, which the keeper rewrites every cycle from RPC reads. Balances are actual balances, not cumulative totals dressed up as a treasury.
…
reading…
ETH claimable by the keeper…
sitting in the locker, PONS sweeps it…
cumulative, to holders…
payout count, all time…
cycles runLast write: …
The keeper wakes up every 5 minutes. It doesn't always send, and that's deliberate. The bridge between these two chains punishes small amounts through price impact — measured, repeatedly:
| Amount | Price impact | |
|---|---|---|
| 0.004 ETH | −5.2% … −3.0% | swings 2 points |
| 0.010 ETH | −3.1% … −2.1% | our floor |
| 0.030 ETH | −2.0% … −1.6% | stable |
Forcing a send every 5 minutes regardless would burn a chunk of the holder pot on slippage. So a slot that's too small is skipped and carried — the fee is not lost, it joins the next one. After 6 hours of quiet the keeper sends anyway, so there's always proof of life.
Honest consequence: busy market means payouts really are every 5 minutes. Quiet market means several slots merge into one payout that's actually worth receiving.
yes, the art is AI slop. the numbers aren't.
The stuff usually buried in a Discord thread after someone gets burned.
No on-chain claim function exists for holders. Distribution depends on our keeper running and its key being alive. If it stops, holders have no other route. That's the same design as the $SOL and BNB versions this copies — the difference is we're telling you.
Contract holders — multisigs, vaults — are skipped. HYPE could be stranded permanently if the same address isn't controlled by the same person on HyperEVM. 325 of 362 "contract" addresses we tested were actually delegated EOAs, and those do get paid.
HYPE lands on the EVM side. If you only check your HyperCore spot account you won't see it. Check the EVM side.
Below 0.0001 HYPE a payout costs more in attention than it's worth, so it rolls into your next one instead of being dropped.
Not 0%. It funds marketing and the gas that makes the loop run. If a project tells you 100% goes to holders, ask who pays for the bridge.
Fees only become claimable after PONS's operator sweeps them. We can't force that. The unswept figure above is pending, not missing.
