⬡ full understanding · the private note, both sides of the glass

the privacy lens

one note contract, notelab11111, live on the public jungle4 rehearsal chain — read by two very different people. The stranger sees everything the chain will ever say. The owner holds the only key that opens a note. Same bytes, different worlds — and the border between them is not a promise, it is arithmetic.

○PUBLIC ●PRIVATE ◐PRIVATE AFTER M5 ◉NEVER HIDDEN

the three flows · status read live

the comb speaks the estate's canon: nectar (sent, not yet seen) → honey (in a block) → capped (irreversible — the wax seal). Click a cell: each lands on the official monitor at the exact action, deep-link verified.

the plumbing · folded, never hidden

reading the sponsor actions…
unfold anyway — nothing is hidden, only folded 
…

the sponsor law: the machine pays, the member never does. Every transaction here was carried by a sponsor's CPU and RAM — that is plumbing, not privacy. Folded for the same reason you don't read the water bill to learn someone's name.

the ledger · every action, every field, chipped

reading notelab11111's public history…
the wall: which note did the transfer spend? ●PRIVATE
The chain holds the nullifier 8f412716… and the commitment 33df36ad… in different tables with no public link between them. Not "we won't tell you" — the information is not there to tell. Only the owner's key can name the spent note.
this row exists to show you the wall, not to climb it
what M5 changes: when the payment statement governs (SPEC-PRIVACY-1 §m5 — membership + conservation, Poseidon tree, PLONK proof), the ◐PRIVATE AFTER M5 fields stop being readable in the row: the value will live only inside the note. The audit skeleton — the ◉NEVER HIDDEN rows — stays exactly as visible as it is right now.

your key · the only door

every commitment row carries a public view tag — four bytes that mean nothing to anyone except the key that made them. Paste your view key and the lens derives each row's tag and unlocks which note is yours, from whom, and its balance. Add the note secret and it proves the note and names the nullifier that spent it. The key never leaves this page: there is no server, and the derivation runs in your browser.

the live notes …

reading the commitment set…

the two rehearsal notes above stay locked to everyone — including us: their keys were random per run and never recorded, on purpose. A member's key never leaves their device. That is not a missing feature; that is the privacy working.

hold a key of your own: mint a demo note in this page — the same arithmetic the chain's rehearsal used (commitment = SHA3-256(secret‖amount), view tag = SHA3-256(viewkey‖commitment), nullifier = SHA3-256(secret‖"null-v1") — contracts/privacy/m3.js, mirrored exactly) — then unlock it below and watch the stranger's view and the owner's view split apart. The demo never touches the chain; the arithmetic is identical.

what the owner sees that the chain never will

which note is yours ●PRIVATE view-tag match
from whom it came ●PRIVATE your records + your key
its balance (after M5) ◐PRIVATE AFTER M5 lives in the note
which nullifier spent it ●PRIVATE provable only by the owner
selective disclosure ●PRIVATE owner→auditor, off-chain, by design

the disclosure law (SPEC-PRIVACY-1 §m3): the owner can prove their own history to an auditor they choose — disclosure by the key-holder, never de-privacy by the system. The chain never sees the disclosure.