Bridging

Robinhood Chain is an Ethereum Layer 2, so moving value on and off it is a different problem than it is on a sovereign chain. Tuck supports three routes, and picking the right one is mostly a question of destination and how long you are willing to wait.

Whichever route you use, the privacy pattern is the same: Tuck privately sends ETH from your shielded balance to a bridge temporary wallet, and that wallet — not your main wallet — interacts with the bridge. The bridge operator never sees your holdings, and observers cannot link the deposit back to you.

Bridge Routes

| Route | Destination | Time | Trust model | | --- | --- | --- | --- | | Canonical Arbitrum bridge | Ethereum L1 | ~7 days (withdraw) | Rollup security, no third party | | Omnichain (LayerZero / Stargate) | Any supported EVM chain | Minutes | Bridge protocol + liquidity | | NEAR Intents | ZCash | Minutes to hours | Intent solver + liquidity |

Deposits into Robinhood Chain from Ethereum are fast on every route — a canonical deposit confirms in minutes. It is the withdrawal direction where the rollup challenge window applies.

Ethereum Canonical Bridge

Robinhood Chain is built on the Arbitrum Orbit stack and settles to Ethereum, so it inherits the canonical Arbitrum bridge. This is the only route with no third-party trust assumption: your withdrawal is secured by the rollup's fraud-proof system, not by a bridge operator's solvency.

The tradeoff is the challenge window. Withdrawing from an optimistic rollup to L1 requires waiting roughly 7 days for the challenge period to elapse, after which you submit a claim transaction on Ethereum to release the funds. Tuck tracks the pending withdrawal and notifies you when it becomes claimable; the claim itself is an Ethereum L1 transaction and costs L1 gas, which is typically far more than anything you pay on Robinhood Chain.

Use the canonical bridge for large amounts, long time horizons, or whenever you would rather not add a bridge protocol to your trust surface.

Fast Omnichain Routes

Robinhood Chain supports LayerZero and Stargate for omnichain transfers of supported assets, and Chainlink CCIP for contract-level messaging. These routes settle in minutes instead of days because a liquidity provider fronts the funds on the destination chain and reconciles later.

That speed is the whole point, and so is the tradeoff: you are trusting the bridge protocol and its liquidity, not the rollup's fraud proofs. Tuck shows the route, the protocol, and the fee breakdown before you confirm. For anything you would consider a meaningful position, prefer the canonical bridge.

ZCash Bridging

Tuck bridges ETH to ZCash through NEAR Intents, a cross-chain intent protocol. This is the route to use when you want to leave the EVM entirely: ZCash offers native privacy at the protocol level, so shielded ZEC is protected by consensus rather than by a wallet architecture.

Getting a Quote

When you initiate a bridge, Tuck fetches a real-time quote from NEAR Intents. The quote shows the exchange rate between ETH and ZEC, the amount of ZEC you'll receive, and all bridge fees. Quotes are valid for a limited time (typically 24 hours) to protect against market volatility. Rates fluctuate with market conditions and available liquidity, so the final amount might vary slightly from the quote.

Bridge Fees

Multiple fees apply: the Tuck Shield withdrawal fee for the private send from your shielded balance, Robinhood Chain gas for the forwarding transaction, and NEAR Intents bridge plus cross-chain swap fees. All are included in the quote, and the displayed ZEC amount is what you'll actually receive after all deductions — there are no additional hidden charges.

Minimum and Maximum Amounts

The minimum bridge amount is 0.0004 ETH. The maximum depends on available liquidity in the solver network. For large amounts, split into several smaller bridges to reduce slippage, executing them sequentially and waiting for each to complete.

Executing the Bridge

Once you approve the quote, Tuck handles the workflow automatically. The private send from your shielded balance completes first (this takes time for zero-knowledge proof generation and confirmation). Tuck then forwards the ETH from the bridge temporary wallet to the deposit address and registers the bridge request.

NEAR Intents validates the deposit, executes the cross-chain swap, and sends ZEC to your specified address. This can take a while depending on solver availability and ZCash confirmation times.

Monitoring Progress

Tuck continuously monitors bridge status by polling the NEAR Intents API. The transaction history shows real-time updates through each stage: pending deposit, processing, and complete. You can close the wallet and come back later — Tuck keeps tracking automatically.

When the bridge completes, Tuck displays the final ZCash transaction hash and a link to a ZCash block explorer, so you can confirm the ZEC arrived.

Bridge Failures and Refunds

Incomplete Deposits

If the ETH deposit fails or is incomplete (insufficient amount, network issues), the bridge refunds it. Refunds are sent back to the bridge temporary wallet address used for the bridge.

Refund processing can take time — NEAR Intents typically attempts refunds within a day of detecting a failed bridge. Once the refund arrives at the temporary wallet, it becomes eligible for the full wallet cleanup flow and the Shield All ETH flow, either of which recovers it back to your shielded balance.

Bridge Timeouts

If a bridge doesn't complete in a reasonable time, Tuck marks it as timed out. This doesn't mean your funds are lost — it means the process is taking longer than expected. You can keep waiting, or contact the bridge's support.

The timeout is only a local status update in Tuck. The underlying quote may still be valid, so a bridge showing a timeout can still complete successfully.

Getting Help

If a bridge fails and you don't receive a refund, or the bridge seems stuck, contact the bridge operator's support. They can look up your bridge using the Robinhood Chain transaction hash that Tuck displays in the transaction details.

Keep that hash handy — it's the proof that you sent ETH to the deposit address, and it's what support needs to trace the transfer. You can verify it yourself on Blockscout.

Privacy Considerations

Bridging is where privacy leaks. Everything Tuck does on Robinhood Chain keeps your activity unlinkable, but a bridge is by definition a correlated pair of events on two chains: an amount leaves here and a matching amount appears there, close together in time. The bridge temporary wallet breaks the link to your main wallet, not the link between the two sides of the bridge itself. Round-number amounts and immediate follow-up transfers make that correlation trivial.

For ZCash specifically: NEAR Intents currently supports transparent ZCash addresses (t-addresses), which start with "t1" and are 35 characters long. These are visible on the ZCash blockchain — anyone can see the balance and transaction history, much like Bitcoin. Make sure you have a ZCash wallet that can receive to a t-address (Zashi, for example).

After receiving, shield the ZEC to a z-address to get ZCash's native privacy, which hides amounts and the transaction graph through zero-knowledge proofs. Receiving to a t-address and leaving it there gives you none of the protection you bridged for.