SOLANA 𝕏 @redact_sol
private by default Β· solana

Your wallet is a public diary.Redact it.

Every balance, every payment and every counterparty on Solana is readable by anyone, forever. REDACT moves your tokens into a shielded pool where zero-knowledge proofs check the math without showing the numbers. View keys let you prove what you choose, to whom you choose.

ZKproofs, not trust
view keysdisclose on your terms
relayersno gas link to you
a payment.
visible
a salary.
visible
a balance.
visible
a habit.
visible
what the chain sees

Same wallet. Three different views.

The public explorer sees that something happened. You see everything. Someone holding your view key sees only what you shared. Demo data below.

demo wallet

Shield. Send. Unshield.

A simulated wallet. Nothing here touches the chain, and no SOL moves.

wallet Β· not connected (demo)
public balance
12.400 SOL
shielded balance
0.000 SOL

Moves SOL from your public balance into the shielded pool.

redact://demo β€” ready
β€Ί choose an action on the left
how it works

Three moves. No trust required.

01 / SHIELD

Into the pool

Deposit SOL or a supported SPL token. You get a private note that only your keys can read. The chain sees a deposit, not what you do next.

02 / PROVE

Math, not exposure

Every private transfer carries a zero-knowledge proof: inputs equal outputs, nothing is spent twice. Validators check the proof, never the amounts.

03 / UNSHIELD

Out, anywhere

Withdraw to any address. A relayer can pay the gas, so the new address has no fee trail back to your old one.

view keys

Private by default.
Provable on demand.

Privacy isn't hiding from everyone forever. It's deciding who gets to look. A view key is read-only: it can show history, it can never move funds.

  • 01Scope it: one token, one date range, or one account.
  • 02Hand it to your accountant, an auditor or an exchange that asks.
  • 03They verify. Nobody else sees a thing.
  • !Once someone has seen data with a key, you can't un-show it. Share carefully.
view key Β· demo
rvk1Β·β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆ
scopeSOL Β· 2026-07-01 β†’ 2026-09-30
can readincoming, outgoing, balance
can spendnever
$REDACT

The token that runs the pool.

A small fee on unshielding keeps relayers paid and buys back $REDACT. Holders vote on which tokens the pool supports.

unshield fee0.15%

Charged only when you leave the pool.

to relayers50%

Pays the people who submit your transactions.

buyback & burn50%

Buys $REDACT on the market and burns it.

governance1 token
1 vote

Which SPL tokens get a shielded pool next.

limits Β· read this

What privacy can't do.

The crowd is the coverA shielded pool is only as private as it is busy. Early on, with few users, deposits and withdrawals are easier to link.
Timing leaksShielding 3.17 SOL and unshielding 3.17 SOL a minute later is easy to connect. Wait, and vary amounts.
Audits firstREDACT is pre-launch. Circuits and contracts will be audited before mainnet, and the reports published.
Your keys, your problemLose your keys and nobody can recover the notes. That's the point, and the risk.
No. A mixer pools coins and hopes. REDACT uses zero-knowledge proofs inside a shielded pool, and view keys let you show your history to anyone you choose, which mixers can't do.
No. Notes are encrypted to your keys. The team, validators and relayers see proofs and encrypted data, nothing readable.
That a valid proof wants to withdraw to some address. Not who you are, not your balance. You can also submit withdrawals yourself.
SOL first, then SPL tokens voted in by $REDACT holders.
Not yet. The contract address will be posted on 𝕏 by @redact_sol. Anything posted anywhere else is not us.