01 / Overview
Gas abstraction without hiding the transaction.
RouteOS lets a wallet sell a supported Robinhood Chain token for native ETH even when that wallet starts with no ETH for network gas. The user chooses the token, amount and recipient. RouteOS builds and sponsors the bounded operation.
Quick Gas is live on Robinhood Chain mainnet in public beta. Portfolio Sweep is visible but locked while its multi-token approval and recovery model is hardened.
02 / Product
Quick Gas
Quick Gas is an exact-input token-to-ETH operation. The user selects a held token and specifies how much to sell. RouteOS quotes the native ETH output after its service fee and delivers that ETH to the selected recipient.
The connected wallet is always the source of tokens. Changing the recipient changes only where the resulting ETH is delivered; it does not allow RouteOS to debit a third-party wallet.
03 / Execution
The route lifecycle
Every operation moves through visible, bounded stages. A quote alone cannot move funds, and the sponsor cannot rewrite a signed intent.
- 01
Connect
Connect the wallet that owns the tokens. RouteOS reads account and token state without requesting control of the wallet.
- 02
Discover
Held Robinhood Chain tokens are discovered and checked against current contract, market and routing requirements.
- 03
Configure
Choose an eligible token, exact input amount and the Robinhood Chain address that should receive native ETH.
- 04
Quote
RouteOS requests an executable route and returns output, minimum received, fee, price impact, expiry and required authorization state.
- 05
Authorize
The wallet signs the exact Permit2 witness. If the token lacks a usable allowance path, RouteOS surfaces the required preliminary approval.
- 06
Simulate
The complete account-state operation is simulated and checked against sponsor balance, gas and policy limits.
- 07
Settle
The RouteOS sponsor broadcasts the bound transaction, pays network gas and tracks the receipt until confirmation.
04 / Admission
Token discovery and eligibility
RouteOS does not treat every ERC-20 as safely executable. The connected wallet’s tokens can be shown automatically, but a token becomes selectable only when its current route passes admission checks.
Contract
Deployed bytecode and readable ERC-20 name, symbol and decimals.
Market
A WETH pool on an approved venue with deployed pool code.
Liquidity
At least $250,000 in reported pool liquidity during public beta.
Pool age
At least 24 hours old during public beta.
Route
A current executable route to WETH/native ETH with usable output and slippage protection.
Simulation
A final account-state simulation must pass immediately before sponsorship.
05 / Economics
Fees and beta limits
RouteOS charges from the routed ETH output, because the user is using the product precisely when they may not hold native ETH.
- Network gas for the sponsored final operation is included; it is not added as a separate wallet payment.
- The quote shows gross route output, RouteOS fee, and expected recipient ETH before authorization.
- An input must cover the $1-equivalent minimum fee and still leave positive recipient output.
- The public-beta ceiling is $1,000 equivalent per operation.
- A token’s dynamic ceiling is the lower of $1,000 or 0.25% of its qualifying pool liquidity.
07 / Relayer
Self-funded sponsorship
RouteOS operates the sponsor that broadcasts the final mainnet transaction and pays its network gas. The sponsor wallet and fee collector are separate operational roles.
Sponsor wallet
Holds operational ETH, submits approved operations and is constrained by reserve, per-operation gas and daily-budget policy.
Relay router
Enforces the signed token, amount, recipient, route hash, deadline, fixed execution target and output floors onchain.
Fee collector
Receives only the service revenue produced by the exact server-built route; it is not the wallet funding the transaction.
08 / Onchain settlement
Atomic final execution
The relay router pulls only the signed amount through Permit2, grants the route target a temporary allowance, executes the signed calls, validates recipient and fee floors, clears the temporary allowance and refunds residual input where applicable.
09 / After submission
Receipts, balance refresh and recovery
Once broadcast, RouteOS records the operation and follows its transaction receipt. The interface should move through submitting, pending, confirmed or failed states, then refresh token and native balances after confirmation.
- Quotes expire and cannot be reused after their deadline.
- Signed intents are bound to the connected source wallet.
- Refreshing the page does not create a second operation; persisted operations can be reconciled from their stored state.
- A pending operation can be recovered by its wallet and operation record, then matched to the eventual transaction receipt.
10 / Planned product
Portfolio Sweep
SoonPortfolio Sweep is designed to convert several eligible token positions into native ETH. It remains locked because different tokens can require different allowance states and wallet confirmations. RouteOS will not fund a partially completed multi-token flow that could strand value or force users through an unclear sequence of signatures.
The public release requires deterministic per-token authorization, a safe cancellation boundary, full-batch simulation, atomic or explicitly recoverable settlement, and clear receipt reporting.
11 / Deployments
Contracts and settlement addresses
Production addresses are published here so wallet prompts and explorer activity can be checked against the RouteOS deployment.
- RouteOS Relay Router
0x296E…1653↗- Permit2
0x0000…8BA3↗- Fee collector
0x837f…1478↗
12 / Reference
Network reference
- Network
- Robinhood Chain
- Chain ID
4663- Native currency
- ETH
- Settlement asset
- Native ETH; WETH may be used inside the route
- Explorer
- robinhoodchain.blockscout.com ↗
- RouteOS release
- Public beta
RouteOS is an independent product and is not affiliated with or endorsed by Robinhood. Public-beta policies and eligibility thresholds may change as execution data is collected.
