Browse documentation

Wallets & apps

Privacy and inclusion

Know what stays private, how transaction expiry works, and how to check a pending submission.

2 min read

What stays private?#

Signed transaction submissions go to BlockFerret’s private intake. They are not automatically forwarded to public mempools or read providers. Private wallet transaction bytes are not exported in independent-builder templates.

Once a transaction lands in a block, its on-chain contents are public. Privacy before inclusion does not make the resulting blockchain transaction private.

Wallet reads are different#

Balances, receipts, fee estimates, and simulations normally use public RPC providers through our proxy. Those providers can see the read request or call data, and proxy reads arrive from the server’s outbound IP. The routing guide explains provider failover and direct reads for compatible apps.

Accepted does not mean included#

A returned transaction hash confirms acceptance. The transaction still needs a valid nonce, enough balance, successful execution, space in a block, an eligible relay proposer, and a winning BlockFerret bid.

A swap can miss its deadline or no longer meet its slippage limit while waiting. The observed delivery pace on the homepage is a wait guide, not a transaction reservation or guaranteed ETA.

30-minute private queue#

Private submissions expire after 30 minutes. Expiry does not automatically broadcast them publicly. The queue is currently held in memory, so a service restart can also require resubmission.

Your wallet may still show “pending” after the private queue entry expires. That display alone does not prove a transaction is still queued or has reached a public mempool.

Check before resubmitting#

  1. Look up the transaction receipt by its hash.
  2. Check your wallet nonce and whether another transaction with that nonce landed.
  3. Review any swap deadline and slippage settings before creating a replacement.
  4. Remember that sending the transaction through another RPC can make it public.

When gas is charged#

If the transaction is never included, there is no on-chain execution gas charge. An included transaction is subject to the network’s actual execution result and gas accounting.

Search guides, concepts, and API reference.