Skip to content

Privacy

Shielded balance

A shielded balance would let you fund participation from a pool where deposits and orders are not linked to your wallet. That mode is not available: nothing on this page is enabled, and no deposit can be made.

Unavailable on this network

No verified shielded-pool protocol is deployed on Robinhood Chain (4663).

Exact dependencies

What is blocking it

  1. A deployed, audited shielded pool with an on-chain verifier for chain 4663 (none found in the official registries or explorers as of 2026-09-21).
  2. A relayer network for that pool, with fee disclosure and proof-bound authorisation.
  3. Circuit support for launch-scoped nullifiers, amount binding and claim commitments (see docs/THREAT_MODEL.md).
  4. An independent security review of the MaroPad adapter integration itself, separate from any upstream audit.

MaroPad does not write its own cryptography and does not present an upstream audit as an audit of its integration. A shielded adapter ships only after those dependencies exist on chain 4663 and the adapter itself has been reviewed.

When available

What the design commits to

  • Commitments and Merkle-root handling of the underlying pool; proofs generated client-side.
  • Nullifiers scoped per launch, so one identity cannot exceed the cap by splitting orders, and launches are not linkable to each other.
  • Proofs bound to the amount, the launch, the claim commitment and the authorised action; replay protection across chains, pools and launches.
  • Relayer authorisation inside the proof, with the relayer fee disclosed before signing.
  • Private claims by default, with an explicit opt-in to a disclosed destination.
  • Encrypted recovery export: what you must keep to recover funds is spelled out before the first deposit.

Transparent participation

What is available now

Launches accept orders through the transparent adapter. It enforces the per-wallet cap on chain and gives no privacy. Before you participate, the form states exactly what is public. The cap applies per wallet address, per launch. the launch sums every order under the same wallet, across ticks and submissions, and rejects any order that would exceed the cap.

Chain observersSee your wallet address, limit price, amount, timing, allocation and refund. All of it is public and permanent.
Frontend hostSees the pages you load and the API calls your browser makes (rate limiting only; no analytics, no session replay).
RPC providerSees the read requests your browser makes through the relay, and your wallet sees the transactions it broadcasts.
IndexerStores the public order events; nothing that is not already on chain.
OperatorSees the same public data as everyone else. Settlement is computed on chain; the operator cannot alter it.
Other participantsSee the same public data as everyone else, including the live demand per price tick.

Explore launches