INT. THE BALCONY — OPENING NIGHT
mutis in 60 seconds, or in 5 minutes.
The Council guide. No install. Each step says what you should see. If you see something else, it's a bug: please tell us in our thread on the Tari™ community forum.
Have a judge pass?
Track A · 60 seconds, no wallet
- A1On a computer, open the home page and drop any file. Keep Opens once. Press Copy link.Your file and its stored noise side by side, and a link whose part after
#is the key. - A2Open the link on your phone. Press Open it.The file.
- A3Reload the page on the phone.“This secret already made its exit.” Under it, the exit receipt: it goes on the public record at our next checkpoint.
- A4Optional: home page → Try to read it → Download the stored bytes.A file we locked within the hour, exactly as our disk holds it: noise.
Track B · 5 minutes, the Tari™ part
Two devices. The phone is the recipient; the computer is everyone else.
- B1On your phone, open the home page → Open my locker → Make my drop link. When asked to save your key, tap Later. On the computer, do the same (Open my locker → Make my drop link → Later): by B3 its locker will hold the testnet grant it sends from.A locker opens in a few seconds, with no email: your drop link, a 12-emoji safety code and an
otl_esm_…Tari address. - B2On the computer, open that short link and drop a photo.The same 12 emoji, “Location and camera data removed”, then Delivered in about a minute. The phone's inbox shows it under Left in your drop.
- B3On the computer: drop a file → Send it to a Tari address instead → paste the phone's address (copy it on the phone and send it to yourself in any messenger) → Send.Sent, On the Ootle ✓ and What the chain sees: amount hidden, owner hidden, memo encrypted, fee public. Above Send, a line says whether this send goes from your browser's wallet or through our relay; if it's the relay, wait a minute or two and it changes. After the send, a line under Sent says which way it went.
- B4On the phone: Inbox.A delivery that only the phone's keys could find; the scan line shows how many outputs it checked. Open it: your file.
- B5On the phone: See what a view key sees.Deliveries and amounts, and 0 files readable with this key. A view key sees arrivals; it can't spend and can't open the files locked to this locker.
- B6On either device: Get more room → the smallest pack → Pay with demo tTARIPay tTARI from this browser.Waiting → Seen on chain → Amount proven → Seen by our wallet → Exists on chain → Added within about a minute. Our demo wallet pays our own invoice: a real stealth transaction with play money.Your browser pays our invoice from the testnet grant our sponsor wallet sent its wallet when the locker opened: a real stealth transaction with play money, built and signed on your device.
- B7On the computer: Verify → the file from B3.An inclusion proof, a root that matches the SealLog component on the Ootle, and the exit receipt from A3. Until our next checkpoint, at most away, each one says it is “not on the record yet”.
If something's off
Tari features paused? The testnet is being reset; Track A still works. A step fails twice? Wait a minute and retry once, then tell us in the forum thread with the step number.
What each step shows
- Stealth outputs: B2, B3 and B6 move value with the amount and owner hidden.
- Encrypted memos: B2 and B3 carry a file's key sealed to one locker; only that locker's keys open it.
- View keys separate from files: B5 sees arrivals but opens nothing.
- Payments checked against chain state: B6 is credited only after the official Tari library proves its amount and a Tari-run indexer shows it on the chain.B6 is credited only after a Tari-run indexer confirms the payment exists on the chain; the amount is the one our wallet reads.
- No server-side keys: A1 to A4. Our server holds ciphertext; the key stays in the link.
The full map and every observer: Where Tari comes in · Who sees what
Live evidence
Our own test transactions, never a user's. They come from /evidence.json, refreshed every hour; older ones are archived in the repository
- Network
- Official Tari library
- ootle-wasm , SHA-256
- Test deliveries (a file key sealed to our own test locker)
- Test payments (our demo wallet paying our own invoice)
Run your own
File sharing needs Python's standard library and a web server. The Tari features also need a walletd on the Ootle testnet and Node for the payment checker. Self-host guide
How it was made
Built with AI coding agents under the author's direction. The design, threat model and crypto choices were reviewed by the author; the verification evidence is linked above. This deployment runs commit 9e7bc34c44a9f33243cd1149a3c4f4f219fe7007.