Start

Overview

One transaction. Many wallets. The same block.

Octo lets a single transaction make many separate wallets act at the same moment, each as itself. Eight wallets buy the same coin in the same block. The coin sees eight different buyers. None of the wallets holds any gas money, because one sponsor pays for the whole transaction.

The problem

• Eight wallets mean eight transactions. They land in different blocks, in an order you do not control.
• Each wallet needs its own gas, so you first have to top every one of them up.
• Wallets that move on the same trail look linked. A script that fires them one by one is slow and clumsy.

The idea in four lines

1. Each wallet signs an EIP-7702 authorization: "for this transaction, borrow the Octo code".
2. Each wallet also signs the exact calls it allows, for example "buy 0.05 ETH on this curve".
3. A sponsor sends one transaction that carries all the authorizations and calls fire.
4. The chain applies the authorizations, then the coordinator reaches into each wallet. Every call is made by the wallet itself.

What you get on Robinhood Chain

• The chain supports EIP-7702 (type 4 transactions). It runs Arbitrum Nitro v3.12 and follows delegation designators, checked live.
• Blocks arrive in about 0.1 s, so "same block" is a tight window.
• Launchpad curves such as Pons see each wallet as the caller, so buys are not merged into one address.

Where it stands

The contracts are written and tested (16 Foundry tests, 9 JavaScript tests). A real type-4 transaction ran on a local node with 8 fresh wallets, and the full flow was simulated on the real chain against a live Pons curve. They are not audited and not deployed. The playground on the site uses a simulated ledger with real wallets and real signatures. See Limits and risks.