ChainRender cross-chain
No wallet

Home chain

Sepolia

Latest block …
Tokens made here are proven elsewhere
Robinhood can prove Sepolia state up to block
…
checking the root source

Host chain

Robinhood Testnet

Latest block …
Checks Sepolia facts by storage proof
Nothing on this page bridges. Only a 32-byte Sepolia block hash crosses to Robinhood, and every cross-chain fact you see is checked against it by a contract, which also prints the grade it can stand behind.

Two chains, one source of truth per token, no bridge

A token lives on exactly one chain, its home. Other chains don't get a copy; they get proof. When value has to change hands across chains, both people lock on their own chain and one secret settles both locks. Here is each mechanism, then the order to try them in.

How a Sepolia balance is proven on Robinhood The Sepolia block hash is delivered to Robinhood through the rollup's own inbox. A cache on Robinhood checks the block header, the token account and the balance slot against it. A resolver renders the result with its grade. Sepolia Robinhood Testnet Your token balancea storage slot of the token Block headercommits to all state ArbRootSendersends one block hash ArbParentRootSourcestores the hash, nothing else Proof cacheheader → account → slot Resolverprints value + grade + facet 32-byte block hash via the rollup's own inbox proof bytes (anyone can fetch them; they are checked, not trusted)
Proven, not bridged: the balance stays on Sepolia. Robinhood learns it by checking a Merkle proof against a Sepolia block hash that arrived through Robinhood's own parent-chain inbox. That makes the result Grade A relative to Robinhood, so it is always printed with Robinhood's own trust facet.
A cross-chain swap with no bridge Alice locks token X on Sepolia under the hash of a secret. The lock is proven on Robinhood. Bob locks token Y on Robinhood; his lock only opens if the proof shows Alice's lock pays him with the same hash and lasts longer. Alice claims Y by revealing the secret, and the secret then claims X for Bob. Sepolia Robinhood Testnet 1 Alice locks X under hash(secret), until T1pays Bob if the secret appears before T1, else back to Alice 2 A Sepolia block hash arrives;the lock is proven on Robinhood 3 Bob locks Y until T2. It opens only if the proof shows Alice's lock is open, pays Bob, uses the same hash and T1 ≥ T2 + gap 4 Alice claims Y before T2, revealing the secret on-chain 5 The same secret claims X for Bob before T1; anyone can submit it
X never leaves Sepolia and Y never leaves Robinhood; only who owns them changes. If nobody claims, each lock pays its owner back after its own deadline. The step that is new here is 3: the second lock checks the first one by proof, on-chain, so Bob doesn't rely on an RPC read or Alice's word for her lock's terms or her token. Seeing the secret in time is still his part; the page watches both chains for it.
A bridge compared with this page With a bridge, token X is held in a gateway escrow on Sepolia and a second token is minted on Robinhood; the escrow follows whoever can upgrade the gateway. Here, X stays in its own contract on Sepolia, and nothing is minted on Robinhood. A canonical bridge This page X held in gateway escrow Second token minted The escrow holds everyone's X at once. Who can upgrade the gateway decides what it does. Robinhood testnet: instant upgrades, 1-of-2 Safe X stays in its contract Nothing minted Only a block hash crosses. Each swap lock can pay only its own sender or recipient. Still Grade C at most: inclusion before each deadline
Both approaches still run on Robinhood, so anything held there is under Robinhood's keys either way. The difference is that no Sepolia value sits in an escrow those keys can redirect. The Trust tab compares this with Robinhood's bridge, tacit and EEZ in full.

Try it in order

  1. Create a token on Sepolia (its home). Pick the name, symbol, decimals and supply; the factory derives a definition id from them.
  2. Send some of it on Sepolia, or create and send a second token on Robinhood. Sends stay on their chain.
  3. Prove your Sepolia balance on Robinhood: deliver a block hash, then let the Robinhood cache check the proof and print the grade.
  4. Swap your Sepolia token for a Robinhood token with someone, or with yourself using one wallet on both sides.
  5. Watch every step land on its own chain in the Explorer, and read exactly what each grade does not establish in Trust.

Your activity on this page

  • Transactions you send from this page appear here with explorer links.