Open app

Whitepaper v0.1 · Draft

A compliant shielded pool with holder rewards

Abstract

Public blockchains expose every balance and payment to anyone with a block explorer. Zhield Cash is a shielded pool on Robinhood Chain that breaks the on-chain link between deposits and withdrawals using zero-knowledge proofs, while letting users prove their funds come from an approved set. Holders of $ZHIELD earn NVIDIA stock (NVDA) every hour.

Version
0.1 draft
Date
Oct 2026
Reading time
3 min
Sections
7
Chain
Robinhood
Proofs
Groth16
Supply
1B fixed

1.Problem

Once someone knows one of your addresses, they can see your salary, savings and every purchase. Earlier mixers solved this but also served stolen funds, which led to sanctions and delistings. Users need privacy that does not make them look like criminals.

2.Design

A deposit stores a commitment as a leaf in an incremental Merkle tree:

C = Poseidon(nullifier, secret)
(1)

To withdraw, the user proves in zero knowledge that:

  1. (a)they know nullifier and secret for some leaf in the tree,
  2. (b)that leaf is also in the current association-set root,
  3. (c)the public nullifierHash is unused, so the note cannot be spent twice.

The proof reveals none of: which leaf, when it was deposited, or the depositor's address.

3.Compliance

Following the Privacy Pools model, an association-set provider screens each deposit against public sanctions lists and known exploit addresses. Approved deposits enter a second Merkle root, and withdrawals must prove membership in it. Rejected deposits can only exit to their source through ragequit. The owner can replace the provider, but a new one takes effect only 7 days after it is proposed.

4.Rewards

The RewardsVault holds NVIDIA • Robinhood Token (NVDA), funded by the team; the 0.20% shield fee on each withdrawal also goes to the vault. Every hour, each wallet holding at least 3,000,000 $ZHIELD earns a fixed dollar amount r of NVDA, at that hour's price:

reward_i,h = [balance_i,h ≥ 3,000,000] × r / price_NVDA,h
(2)

Contracts, such as the launch curve and liquidity pools, do not earn. A publisher posts a Merkle root of every holder's cumulative total each hour, and the vault caps how much each root can add. Holders claim for themselves, to their wallet or to a fresh address, so claiming does not have to link the holding wallet to the spending wallet.

5.Tokenomics

Total supply is 1,000,000,000 ZHIELD, with no mint function after deploy.

1B$ZHIELD
AllocationShareTokens
Fair-launch liquidityLP locked 12 months60%600,000,000
Rewards boostStreamed over 12 months15%150,000,000
Treasury3-of-5 multisig10%100,000,000
Team3-month cliff, 12-month vest10%100,000,000
Security & bug bountyReleased per milestone5%50,000,000
Figure 1.Allocation of the fixed $ZHIELD supply by share, token count and terms.

6.Security

  • Circuits and contracts tested end to end on a local chain, with an in-house review, before mainnet.
  • A public trusted-setup ceremony is planned after launch.
  • Per-pool deposit caps until the pools have run cleanly.
  • Admin cannot move user funds.

7.Risks

Disclosure

Contracts and circuits may contain bugs. Small pools give weak privacy. Rewards depend on volume and can be zero. Laws on privacy tools differ by country, and users are responsible for following theirs. $ZHIELD is a utility token, not a share in any company.