veilpool

Private value flow on @RobinhoodCrypto

Variable Notes · Local ZK proofs · ETH privacy infrastructure

0x2e9e138ebb56edf2a3d541e1127e5d3a88ad5f89

[veilpool @VeilPoolPrivacy]

VeilPool Variable V1 combines:
Groth16 proofs
Poseidon hashing
Merkle commitments
Encrypted browser-side Notes
payout approval
A transparent protocol flow with private Note data

[veilpool @VeilPoolPrivacy]

@sammynitros yes

[veilpool @VeilPoolPrivacy]

Private ETH transfers, built for control.
VeilPool Variable V1 keeps your Note details private while using Groth16 proofs, Poseidon commitments, and a Merkle Tree to verify ownership without exposing the Note itself.
Explore the workflow:
https://t.co/tc5r2ipvyR

[veilpool @VeilPoolPrivacy]

How VeilPool Works

VeilPool lets you move ETH privately while keeping the Note details hidden from the public chain.

Your browser creates an encrypted Variable Note containing a secret, nullifier, and amount. Only the commitment is stored in the Pool’s Merkle Tree. Your Note backup and password never leave your device.

When you withdraw, a Groth16 zero-knowledge proof is generated locally to prove ownership without revealing the Note details. The Pool settles the net amount to the V1 Vault after deducting the 0.3% protocol fee.

Once approved, the Vault sends the net amount to your fresh recipient address.

Your private key, Note secret, and backup password are never uploaded. Always keep your encrypted Note backup safe.📷

[veilpool @VeilPoolPrivacy]

@ShitcoinProphet Agreed — seeing the flow matters more than reading about it

A private transfer walkthrough is coming

[veilpool @VeilPoolPrivacy]

https://t.co/9b7BXO9a3V

[veilpool @VeilPoolPrivacy]

Private transfers are built around Notes, not public account balances

Select your existing Note
Create a new recipient Note
Generate the proof locally
Submit the transfer on-chain

The old Note is spent
The new Notes carry the value forward

[veilpool @VeilPoolPrivacy]

DEX payment complete