STOCKYZK
Solana
What you own, held as hashes.
Every note below is a commitment sitting in the public set on Solana. The chain stores the hash. The opening — which asset it is, and the one-time key that owns it — never leaves this browser.
Commit an asset to the set.
The transaction publishes one 32-byte hash in a memo. It does not name the asset, and it is not readable back to you: the leaf commits to a secret asset salt and a fresh one-time key that has never held anything else.
What the chain will see
This exact hash, and nothing else.
The fee (about 0.000005 SOL) is paid by your connected wallet. That wallet is the only public link, and it never appears inside the commitment.
Prove you own it. Not what else you own.
Pick a commitment, take the verifier's challenge, and sign it with that note's one-time key. The result is checked against the set as it stands on Solana right now — the verifier learns this one asset is yours, and nothing more.
Proof blob
Hand this to the verifier. It contains the opening for one asset only.
Hand ownership over, quietly.
The sender spends the old commitment and appends a new one. The chain sees a one-time key it has never seen before retire, and a fresh hash appear. Neither wallet is named.
Receiving side
Generate a ticket and send it to whoever is handing you the asset.
Delivery note
After a transfer, send this to the recipient so they can open their new commitment. Paste it below to claim one.
Check a claim against the chain.
Paste a proof blob. This page rebuilds the set from the registry's public memo history over a Solana RPC and runs verifyOwnership on it — no wallet needed.
To be plain about it: there is no on-chain program here. Any client rebuilds the set from public Solana memo history using fixed rules, so enforcement comes from open verification — anyone can replay the history and get the same answer — not from a contract rejecting bad transactions.