How one transaction is built
scroll to build the transaction
Robinhood Chain / EIP-7702
One block.
Eight wallets.
Eight separate wallets act in the same block from a single transaction. A sponsor pays the gas. The wallets hold no gas money and the target sees eight different buyers.
EIP-7702no admin keyno feelive-chain simulation
click the octopus to fire
The point
Same block, not same wallet.
Eight transactions land in eight different blocks. Octo puts all eight in one. The blocks here are about a tenth of a second.
Eight transactions8 wallets, each needs gas
One Octo transaction1 sponsor pays, 0 gas in wallets
Each square is an arm. Each cell is one block.
Playground
Arm. Sign. Fire.
Real wallets, real EIP-7702 authorizations, real signatures, made in your browser. A pretend ledger. Then try to break it.
One minute
See it first.
The idea, the real app, and the attempts to break it. With sound.
Anatomy
What goes in one transaction.
A type-4 transaction
It carries an authorization list: one signed note per wallet saying "borrow the Octo code for this transaction". The chain applies them all, then runs one call to the coordinator.
0ETH of gas in the wallets
0block for all arms
0distinct buyers seen by the curve
Signed calls
Each wallet signs the exact calls it allows, with a nonce and a deadline. Nobody else can speak for it.
Atomic or not
All eight succeed together, or none runs. Or skip a failed arm and let the rest go through. You choose.
No owner
No admin key, no pause, no upgrade, no fee. The coordinator holds no funds and only calls wallets that carry the trusted code.
Proof, not promises
Run on the real chain.
Nothing is deployed and no transaction is sent. The script runs the whole flow in a read-only call: eight fresh wallets, a signed authorization list, eight buys on a live Pons curve. The price rises from one buy to the next, so they really run one after another inside the same block.
$ node scripts/real-chain-check.mjs
chain 4663 block 84176731 (Robinhood Chain, Nitro v3.12)
live Pons curve 0xF04F72...0131
NOMINAL 8 fresh wallets, ONE EIP-7702 authorization list, 8 buys
arm 1 ok tokens received 570,782
arm 2 ok tokens received 570,130 (the curve price rises)
...
arm 8 ok tokens received 566,245
controls
refused no authorizations (wallets not delegated)
refused calls changed after signing
refused a signature from another wallet
refused atomic mode: one bad arm cancels all eight
Versus the usual way
Why not eight transactions?
| Eight transactions | Octo | |
|---|---|---|
| Blocks used | spread over several | one |
| Gas money in each wallet | needed first | none, a sponsor pays |
| Wallets visible as callers | eight | eight |
| Who can change the calls | nobody | nobody, each wallet signs |
| If one buy fails | the others already happened | you choose: cancel all or skip it |
| Cheaper? | no | no, roughly the same gas |
Read this part
What it is not.
Not audited, not deployed. The contracts are written and tested. The playground runs on a pretend ledger.
Delegation lasts. Wallets stay delegated after firing until they sign a revoke. The CLI does it in one command.
No shortcuts. Launch taxes and limits still apply. Octo only lets wallets act together.