Sending Funds

Sending ETH

From Shielded Pool (Private Send)

When you send ETH from your shielded balance, the Tuck Shield contract pays the recipient directly against a zero-knowledge proof. The proof reveals a nullifier and the payout, and nothing that ties either to your deposits. The recipient receives ETH with no on-chain link back to your wallet. Proof generation takes 5-20 seconds in your browser.

Fee: 0.0002 ETH base + 0.35% of withdrawal amount (deducted from your shielded balance). Minimum send: 0.00002 ETH.

From Public Shards

ETH in public shards can be sent directly to recipients, but this is less private — the recipient can see the shard address. If your send amount exceeds a single shard's balance, Tuck aggregates from multiple shards automatically.

Fee: ~0.000004 ETH per transaction, paid by the Tuck relayer and automatically reimbursed from your shielded balance. Shards can be emptied completely — Robinhood Chain has no rent or minimum-balance requirement.

From Private Shards

ETH in private shards cannot be sent directly. To use this balance, run the cleanup/consolidation workflow to shield it first. This moves the ETH into your shielded pool where it can be sent privately.

Workaround (not recommended): Export the private shard's key from Settings → View Wallets and send from another wallet. This exposes the shard on-chain.

Sending ERC-20 Tokens

From Public Shards

Tokens in public shards are sent directly to the recipient with a standard transfer call. No recipient-side setup is needed — an ERC-20 balance is a mapping entry, so the recipient does not need to pre-create anything and there is no rent to pay.

Fee: ~0.000006 ETH per transfer, paid by the Tuck relayer and automatically reimbursed from your shielded balance.

From Private Shards (Not Recommended)

You can send tokens from private shards, but this compromises privacy. The Tuck relayer pays gas upfront. After the send completes, the relayer is automatically reimbursed from your shielded balance through a Tuck Shield withdrawal (0.0002 ETH + 0.35%).

After the send: the private shard is converted to a public shard (now visible on-chain), and a new private shard is generated to replace it.

Fee: ~0.000006 ETH per transfer, paid by the relayer and reimbursed from your shielded balance.

Sending Stock Tokens

Stock Tokens transfer like any other ERC-20 — there are no allowlists or permissioned-transfer restrictions on holder-to-holder movement. Two things are worth knowing before you send:

• Amounts are ERC-8056 scaled. Enter the share count you see; Tuck converts it to a raw amount using the current uiMultiplier(). If a corporate action lands between quoting and confirming, Tuck re-reads the multiplier and re-prompts rather than sending a stale raw amount.
• Equity positions are highly identifying. An unusual position size or ticker mix is far easier to fingerprint than a round ETH amount. Prefer sending from a public shard you are willing to burn, and do not reuse it afterwards.

From DApp Wallets

DApp wallets can send both ETH and ERC-20 tokens directly. Gas is paid by the Tuck relayer and automatically reimbursed from your shielded balance.

Fee: ~0.000004 ETH for ETH sends, ~0.000006 ETH for token transfers.

Transaction Fee Handling

All send operations use Tuck's relayer system to handle gas automatically. Shard and dApp wallets sign an ERC-2771 meta-transaction; the relayer submits it and pays the ETH gas upfront, then is reimbursed from your shielded balance after the transaction completes.

The reimbursement happens through a Tuck Shield withdrawal (0.0002 ETH + 0.35%). Tuck's fee estimator shows the total cost including both network gas and reimbursement costs before you confirm the send.

Ensure your shielded balance has sufficient ETH to cover both the send amount (if applicable) and the relayer reimbursement. If your balance is insufficient, the send will fail with a clear error message.

Edge Cases

• One flow at a time: you cannot start a new send while another flow (send, swap, consolidation) is active.
• Insufficient shielded balance: if you lack shielded ETH for relayer reimbursement, the send fails with an error showing how much more you need to shield.
• Wrong network: Tuck only sends on Robinhood Chain (chain ID 4663). The same 0x address exists on every EVM chain, but a recipient who only monitors Ethereum will not see a Robinhood Chain transfer. Confirm the network with them first.
• Contract recipients: sending ERC-20 tokens to a contract that does not implement token handling will succeed on-chain and strand the tokens. Tuck warns when the recipient address has bytecode.