Trading/private

Private transfers

Move value without leaving a link on-chain — between your own wallets, out to any address, or in from anyone, in ETH or SOL.

Every ordinary transfer on this chain is a public link: address A paid address B, forever, for anyone who cares to look. A private transfer moves ETH without writing that link. The funds leave the chain, cross an independent exchange step, and come back from somewhere unrelated — so what the chain records is “A sent to a deposit address” and, separately, “some address paid B”, with nothing joining the two.

It has its own page — Private in the nav — and a quick path inside the wallet Transfer flow for the common case. Both write to the same list of jobs, so a transfer started in one place shows up in the other.

#Three directions

It began as a hop between two of your own wallets. It now covers both ends of the platform boundary as well: out to anyone, and in from anyone.

Mode	What it does	What is hidden
Between wallets	Moves ETH from one of your hood.dev wallets to another.	That the two wallets belong to the same person. This is the reason to run several wallets at all.
Send out	Pays any address you type — not just your own, and not only on this chain. ETH on Robinhood Chain or SOL on Solana.	That the payment came from your wallet. The recipient sees a payout from an address that is nothing to do with you.
Receive	Mints a deposit address you can hand to anyone — on Robinhood Chain or on Solana. Whatever lands is delivered as ETH to the wallet you picked.	Your wallet, from the sender. They only ever see the deposit address, on whichever chain they are paying from.

Sending out is a withdrawal, and it is final

In Send out the destination is whatever you typed. There is no recall, no support ticket that reverses it, and the only check on the address is the one in your browser — it verifies the shape of an address for the chain you picked, nothing more. A well-formed address belonging to nobody is accepted by every layer of this. Paste it, read it back, then send.

#Which chains

Native ETH on Robinhood Chain is the default at both ends, and native SOL on Solana works at either end too: a sender can pay SOL into a Solana deposit address and you receive ETH here, and a Send out can pay SOL to a Solana address out of your ETH balance. What is offered is not a hardcoded list — the app asks the route, live, whether it can genuinely take a given chain as an origin and pay it as a destination, and only shows the ones that answer yes. When it cannot ask, the selector falls back to Robinhood Chain alone rather than guessing.

An address belongs to one chain

Pick the network first, then paste. Switching networks deliberately clears the address field, because an 0x… left sitting in a Solana payout is exactly how funds get stranded — the check in your browser names the mismatch (“that’s an EVM address”) and refuses to price the route until it agrees.

#The numbers

Assets

Native ETH on Robinhood Chain, or native SOL on Solana — either end. Nothing wrapped, no tokens.

Minimum

0.02 ETH, or 0.25 SOL. Below that the amount arriving mid-route can fall under the route’s own floor and strand. The estimate re-checks it against the live floor and says so.

Cost

A 0.5% service fee, plus what the route itself costs — the bridge legs and the exchanger’s spread, which is the larger part. Roughly 3% all-in on a Robinhood round trip, and a little less to Solana, which is a shorter route.

Time

Minutes, not seconds. It is a job with a progress timeline, not a send.

Recipients

One per transfer. The whole amount goes to a single destination.

Reversible

No — at any stage.

Before you commit you get a live you’ll receive figure covering the whole round trip. Rates float and are re-quoted at execution, so it is an estimate — and when a leg cannot be priced the UI says which one and shows no number rather than a made-up one.

#How one runs

Compose it

Pick the direction, the wallets or address, and the amount. The estimate prices the route while you type.

Fund it — one signing prompt

The deposit goes to an address outside the platform, so your credential signs it, not the popup-free delegated key (see Wallets & keys). On the happy path you never handle the deposit address by hand; it surfaces under Details as a fallback if the automatic send cannot go through. In Receive there is nothing of yours to sign at all — the address is the whole deliverable.

Four milestones

Deposit received → converting for the private hop → breaking the on-chain link → delivering ETH. The card tracks them and keeps running whether or not the page is open.

Delivered

ETH lands in the destination. If a leg gets stuck the job is parked as needs support rather than failing silently: the funds sit with the route, and the reference on the card is what support needs to resolve it by hand.

#Running several

The page lets you stage transfers into a queue and run them in one go. They execute strictly one at a time — each one is a separate signature, and parallel sends from one wallet would race each other’s nonce — with a short randomised gap between them. Stop after this one finishes what is in flight and leaves the rest queued. One failure is marked and retryable; it does not abandon the transfers behind it.

What a few seconds of jitter does not buy

The gap between queued transfers exists so consecutive sends do not look like one mechanical batch. It is not a defence against timing analysis. Anyone watching both ends still sees a burst of activity in the same few minutes, and equal amounts in and out are their own signature. Real decorrelation means spreading transfers over hours and varying the amounts — that is on you, not on the rail.

#Tracking, and what a job id reveals

Jobs survive a refresh, and are re-adopted on a different device or after cleared storage — recovered for wallets you can prove you own, so nobody else’s transfers can be enumerated.
The progress lookup a browser can make from a job id alone returns how far along it is and nothing else. Deliberately no addresses: the destination is precisely the link this exists to break, and job ids get pasted into chats and screenshots.
So the reference on a card is safe to send to support. It is not a claim on the funds and it does not identify either end.

#Honest limits

Mid-route, the funds are in someone else’s custody. That is what buys the unlinking. It is a real trust assumption, and it is why the minimum and the address check exist — a wedged job is recovered manually, not automatically.
Send the exact amount on an incoming deposit. Only the native asset on the quoted network is detected, and sending less than quoted can leave it sitting there.
Privacy is not retroactive and not automatic. If the receiving wallet then trades against the sending wallet, funds them ordinarily later, or is the only wallet ever to receive an unusual amount, the link comes back by other means.
The rail can be offline. It depends on services we do not run. When it is down the page says so plainly instead of taking a deposit it cannot route.

Moving ETH between your own wallets the ordinary way is still instant and costs nothing but gas — see internal transfers. Use that when the link does not matter, and this when it does.

chain 4663·on-chain values read 2026-07-29·Blockscout