Launch a coin. Get a chain. Every coin gets its own chain ID, RPC and live explorer, settled on @RobinhoodCrypto.
Robinhood
Joined October 2026
- Tweets109
- Following2
- Followers130
- Likes0
Pinned Tweet
$RETICLE is live on robinhood chain.
0x8e8d9d2fd121b97c8760b0c3abf64b631348edb7
launch a coin on pons, get its own chain: reticlechain.site
15 more tokenized stocks and 11 new pools on robinhood chain. it keeps getting busier, and every trade on it is public data. that's exactly what reticle chains are built from.
Ondo Stocks, now on Robinhood Chain.
Live today, 15 Ondo tokenized stocks and ETFs can be bridged from Ethereum and BNB Chain to Robinhood Chain.
11 new @Uniswap StablePair pools connect Ondo Stocks and Robinhood Stock Tokens, bringing 24/7 liquidity to the chain’s DeFi ecosystem.
What this unlocks:
→ New potential arbitrage opportunities
→ More ways to trade and earn LP fees
→ Connectivity to Ondo Stocks’ 24/7 liquidity
With this expansion, more traders can access Ondo Stocks and more developers can build financial applications around them.
same site, same account, new rails. pons for the coins, one contract for the chains, robinhood chain under both.
a coin launched from reticlechain.site/launch is a normal pons coin: same curve, same graduation to uniswap v4. the chain sits on top.
vnet_getHolders on any reticle chain returns the top holders and their share. same data as the explorer, as json.
if two coins ever land on the same id, the later one moves to the next free number. first registered keeps it.
nothing to install, nothing to bridge. a reticle chain lives at reticlechain.site/chain/<id> and answers json-rpc at /rpc/<id>.
a chain per coin sounds heavy. it's one contract call: the coin, its id and who registered it, written once on robinhood chain. the rest is read from the chain itself.
how the id shows up before you sign: the launch page predicts the address pons will deploy your coin at, then asks the registry which id that address gets.
the registry doesn't take our word for who launched a coin. it asks pons. deployer or creator-fee wallet: chain written. anyone else: revert.
every chain is named after its ticker: <ticker>-vnet-<id>. the native token is the coin itself, and it settles on robinhood chain.
curl it:
curl -X POST reticlechain.site/rpc/<chain id> -d '{"jsonrpc":"2.0","id":1,"method":"vnet_blockNumber"}'
that's the current height of that coin's chain.
the explorer on each chain: latest blocks, busiest blocks, every trade with its trader, top holders, and an rpc playground right on the page.
block height is the time since registration divided by 2 seconds. every trade lands in the block whose window it happened in. that's the whole trick, and anyone can recompute it.
for builders: reticlechain.site/api/chains returns every registered chain with its coin, creator and genesis tx. no key, no signup. bots, dashboards, alerts, go.
launched on pons before reticle existed? doesn't matter. paste the coin address on reticlechain.site/register, sign once from the creator wallet, and the chain is written.
a reticle chain isn't a new l1 and nothing runs validators. the blocks are 2-second windows over your coin's real trades on robinhood chain, and the id is written on-chain by the registry. virtual, and we say so.
a slice of that dex volume is pons curve trades. on reticle, each of those trades lands in a 2-second block on its coin's own chain, readable over rpc.
