How SEALED works.

How it works

Private route, step by step

• Quote. We ask the partner network for a live quote to your destination network and asset. Independent exchanges answer; the best rate wins, and the number of exchanges quoting is shown next to it.
• Order. On "Seal it" the partner creates the order and returns a one-time deposit wallet on Robinhood Chain itself, valid for one hour.
• Send. You sign one plain ETH transfer on Robinhood Chain (4663) to that deposit wallet. No bridge, no contract call, no approval.
• Clear. The partner picks the best exchange from a network of 40+ and delivers to the address you chose. The exchange sits between your deposit and the destination, breaking the on-chain link.
• Track. Your transfer reports by tx hash; the partner order is polled every 30 s until it is delivered, refunded, or expired.

What the partner sees

The deposit wallet it issued, the transfer that funds it, and your destination address. Screening runs on the deposit before anything moves. SEALED sends no personal data to the partner.

What SEALED stores

Per order: the partner id, the Robinhood tx hash, the sending address, amounts, status, timestamps. Lookup is by an unguessable id only. There is no per-wallet history endpoint by design.

Routes

• A · Private. Robinhood → partner deposit wallet on 4663 → screened exchange → destination network (EVM or not: BTC, SOL, XMR, TRON and more).
• B · Standard. Robinhood → screened partner → destination. Same engine, limited to familiar EVM chains and framed for speed rather than unlink. Works today.
• C · Arrive on Robinhood coming. Any chain → partner → Robinhood Chain. Same mechanism reversed; v1 is docs only.

Fees

• Standard: same as private — everything is inside the quoted rate. The "route spread" line shows the full cost in USD before you sign.
• Private: everything is inside the quoted rate — the "route spread" line shows the full cost in USD before you sign. No fee outside the quote.
• Gas: one transaction on Robinhood Chain, estimated live in the quote.

Limits

• Partner min and max per quote (live).
• proposed per-order cap of $60,000 equivalent, printed as a warning on the quote.
• Geo-block and Tor rules on /compliance.

Refunds

Refunds are executed by the partner network, not by SEALED. If a deposit is flagged by screening, cannot fill, or expires, the partner returns funds along the path they came from, tracked on this order id. SEALED cannot move or redirect a refund; there is nothing of ours on the money path.

Risks

• Unaudited software. SEALED itself is not audited. It writes no contracts, but the routing logic could have bugs.
• Floating rate. The private rate is floating between quote and clearing; the delivered amount can differ slightly from the quote. Standard bridge legs carry a 0.5% slippage tolerance.
• Partner delays. Screening can hold a deposit. XMR routes are slower by design.
• Address reuse. A reused destination address is a link. The seal cannot fix that.
• Timing. Amount + timing correlations exist. Do not expect a mixer's anonymity set; expect a clean unlink of one hop.

API

• GET /api/chains every destination network and asset the partner receives, with an evm flag (Standard shows EVM only).
• GET /api/tokens?chain=4663 token list per chain.
• POST /api/quote standard: { fromToken, fromAmount, fromAddress, toChain, toToken, toAddress } · private: { fromAmount, toNetworkId, toAssetId }.
• POST /api/order create private order (returns the tx to sign) or record a standard tx.
• GET /api/order/:id tracking view. PATCH attaches the signed tx hash.
• POST /api/quote { mode, fromAmount, toNetworkId, toAssetId } · same shape both tabs.