Solana × Zcash principles
Reveal less.
Prove more.
Exploring private payments for Solana, inspired by Zcash. Share what matters. Keep the rest yours.
Launching on pump.fun
$SABLE
Fair launch on pump.fun. No presale, no team allocation, no vesting.
Contract address
No contract exists yet. Any address claiming to be $SABLE before it appears on this page is not ours.
The token is a community asset. It is not equity, not a claim on any technology described here, and confers no rights. Nothing on this site is a working privacy product, and the token does not change that.
Disclosure Studio
A hands-on model of selective disclosure. Change a setting. See who learns what.
Live · in your browserReal SHA-256 via Web Crypto. No wallet, no upload, nothing leaves this tab.
1. Create a transaction
2. Choose what to disclose
Select the information you want to prove or reveal.
- Prove payment happenedShow that this transaction is valid
- Reveal amount onlyShare the amount, keep identities private
- Prove balance above 10 SOLShow you have sufficient funds
- Keep recipient hiddenHide the recipient address
- Keep memo hiddenHide the memo / note
3. Knowledge map
See what each party can learn.
Learns details No disclosure
Activity
- Change a disclosure switch or create a receipt. Every operation is logged here with its real duration.
Private by default
Your financial information stays yours.
Verifiable when needed
Prove what matters without revealing everything.
Disclose with intent
You choose what to share, and with whom.
Technology
Solana ambition. Zcash inspiration.
Our direction is private payments for the Solana ecosystem, informed by Zcash’s approach to shielded transactions. The Studio is the first step: a simple way to explore what a payment reveals, and what it could keep private.
Explore the TechnologyProtect
Explore how a payment can reveal less.
Prove
Understand proof without full disclosure.
Share
Disclose only what matters, on your terms.
Inspired by Zcash
Inspired by shielded payments and deliberate disclosure. A research direction, not a live bridge or a Zcash integration.
Threat model
What holds, and what does not.
"Zero-knowledge" describes a technique, not a guarantee. These are the specific properties this tool does and does not have.
What holds
Hidden values never leave the browser
Fields you keep private are exported as commitments only. Their values and their salts are discarded, not stored and not uploaded.
Each field is salted independently
A fresh 256-bit random salt per field, so a commitment cannot be brute-forced from a guessed value, and two identical values do not produce matching commitments.
Tampering is detectable
The checker recomputes every disclosed commitment and the fingerprint over all of them. Altering a value or a commitment fails verification.
Nothing is transmitted
Receipt creation and checking both run locally through the Web Crypto API. There is no server, no account and no telemetry.
What it does not claim
It does not prove authorship
A receipt is internally consistent, not authentic. Anyone can generate a different self-consistent receipt. Compare a fingerprint over a channel you already trust.
It is not a zero-knowledge proof
These are salted hash commitments. No circuit, no proving system, no verifier. The payment and balance switches are teaching controls, not attested claims.
Disclosure is irreversible
A value you share is public to everyone who receives the file. There is no revocation, and no later disclosure from the same commitment.
It has had no security audit
No independent cryptographic or application review. The browser and its origin must be trusted; a malicious extension can read inputs before this code sees them.
Research direction
Where this goes, in order.
Each stage depends on the one before it. Only the first has shipped.
- 01
Make disclosure legibleShipped
An interactive model of who learns what, plus a local commitment tool. Shipped, and the whole of what this site is today.
- 02
Define the threat model formallyNext
Write down the adversary, the assumptions and the properties claimed, precisely enough to be attacked on paper before anything is built.
- 03
Select a protocolNot started
Choose a proving system and a settlement design, with the custody and trust assumptions of any cross-chain route stated explicitly rather than assumed away.
- 04
Independent reviewNot started
Cryptographic and application audit by reviewers with no stake in the outcome, published in full, before anything touches real funds.
Questions
The obvious ones.
Is this a working privacy payment system?
No. It is a teaching model with a working local commitment tool. There is no wallet connection, no transaction, no bridge and no proof generation. Nothing here moves money.
Are you affiliated with Zcash or Solana?
No. Not with Zcash, the Electric Coin Company, or Solana. "Inspired by" means the design principles informed the research direction — it is not a partnership and not an integration.
Then what is the receipt actually good for?
Showing someone a specific fact about a record while withholding the rest, and letting them check that the disclosed part matches a commitment made earlier. That is a real, narrow, useful primitive. It is not proof that a payment happened.
Can I verify the claims on this page myself?
Yes, and you should. The commitment is SHA-256 over a tagged tuple of the field name, value and salt; the fingerprint is SHA-256 over all commitments. Recompute either with any SHA-256 implementation and compare.
Where does this run?
sablezero.xyz is registered and hosted on Vercel. Everything on this page runs client-side, so there is no backend to depend on and nothing to go down.
Is my sample data sent anywhere?
No. Every operation runs in your browser through the Web Crypto API. There is no server to receive it, no account and no analytics.
References
Primary sources.
The specifications and documentation this direction is read from. Linked so the claims above can be checked against them rather than taken on trust.
Zcash shielded assets
Protocol and cryptography
Solana and implementation
A more private tomorrow
What should the world know?
Explore the technology. Experiment with disclosure. See a more private future.