CIPHER / PRIVACY LAB

Watch it encode.
Choose what to reveal.

A moving model of encrypted notes and selective disclosure.
Follow the crawler. Watch readable data become ciphertext.

SWARM cipher-crawlerNODES 420STAGE SHIELDLOCAL VISUALIZATION
01 SHIELDInto the pool / illustrative flow
CRAWLER LOG
› initialize local model
WORKFLOW
VISIBILITYPUBLIC INPUTDeposits can be visible.
CRAWLER.JS / VISUALIZATION
Animation logic · no cryptographic execution
Drag over the network to shift the viewpoint. Select a stage to follow the crawler.Open wallet simulation ↗
ZK proofs / planned verification modelView keys / scoped disclosureRelayers / proposed fee routing


What the chain sees
One wallet.
Three different views.
The same sample records, viewed by the public, the owner, or a scoped auditor. Switch perspectives.
PUBLIC EXPLORER / SAMPLE RECORDSDETAILS REDACTED
ACTIVITYAMOUNTCOUNTERPARTYDATE


Shield. Send. Unshield.
The wallet, on your terms.
Interactive simulation. Balances and actions below are local examples; no assets move onchain.
SIMULATED PUBLIC BALANCE12.400 SOL
Outside the shielded pool
SIMULATED SHIELDED BALANCE0.000 SOL
Owner view · local simulation
Into the pool.
Simulate moving SOL from a public balance into a shielded balance.
cipher://simulation — ready
Choose an action. No transaction signatures are requested.
Local simulation only. Wallet connection requests your public address; it does not connect these balances to real holdings.


How the proposed protocol works
Three moves. Less exposure.
01 / SHIELD
Into the pool.
Deposit SOL or a supported SPL token. The intended protocol creates a private note controlled by your keys. Deposits themselves may remain visible.
02 / PROVE
Math, not exposure.
Zero-knowledge proofs would verify valid spends and prevent double-spending without disclosing the protected transfer details.
03 / UNSHIELD
Out, when you choose.
Withdraw to an address. A relayer could submit the transaction and pay gas, reducing a direct fee-payment link to your main wallet.


View keys / Read-only access
Private by default.
Shared by choice.
The planned view-key feature would let an accountant or auditor read a defined scope, without permission to move funds. Choose a date range and which information to share.
Once someone has seen information, you cannot make them forget it. Narrow the scope before sharing.
The key generator below creates a local sample token, not a cryptographic view key.
Scoped access
cvk-sample · ████████████████
Can read: chosen fields. Can spend: never.


$CIPHER / Proposed token model
The token behind the pool.
The proposed unshielding fee funds relayers and token buybacks. Governance would choose which tokens gain support.
UNSHIELD FEE0.15%
Proposed fee when leaving the pool.
TO RELAYERS50%
Half the fee supports transaction submission.
BUYBACK & BURN50%
Half the fee would buy and burn $CIPHER.
GOVERNANCE1 : 1
Proposed one-token, one-vote model.
Proposed design, not deployed token mechanics. No verified token contract or trading link is published here.


Know the limits
Privacy needs honest boundaries.
The pool matters.
A small pool provides less cover. Actual protection depends on usage, protocol design and the available anonymity set.
Metadata can connect.
Timing and recognizable amounts can reveal relationships even when some transaction data is protected.
Review comes first.
CIPHER has no deployed privacy protocol. Circuits, contracts and key handling would need independent review.
Keys need care.
A real private-note system may make recovery impossible if keys are lost. View keys can expose what you choose to share.
Frequently asked
Before you shield.
Is the protocol live?
No. This site illustrates the product flow. Shield, Send and Unshield are simulations; no deposits or transfers are submitted.
Are the simulated amounts my wallet balance?
No. They are local sample balances and remain separate from a connected wallet’s real assets.
Do view keys let someone spend?
The proposed view-key design is read-only. Sample keys here only control which sample fields the auditor view displays.
Which tokens would be supported?
The initial design targets SOL, with additional SPL tokens proposed through governance after protocol implementation and review.
Some things are yours.
Explore privacy with boundaries you can understand.
Explore CIPHER ↗


Connect your wallet.
Connect Phantom or Solflare to share your public address. CIPHER never asks for your recovery phrase. Shield, Send and Unshield below remain simulations.
On mobile, open this site in your wallet’s browser. Need a wallet? Get Phantom ↗ · Get Solflare ↗