SOCIAL MONEY / THE JUDGE'S TOUR
One community camera. Two possible returns.
Follow the money in 60 seconds.Vercel + Meteor · 9–12 November · no wallet needed
01 / A LIBRARY OWNED BY ITS COMMUNITY
A campus club lends its camera. Who collected it? Did it come back damaged? Who gets the bond? The borrower, custodian and council each have a distinct job.
Read both recorded outcomes ↗
02 / MOBILE REVIEW · BOOKING #13
Booking #13 began with a 390 × 844 Chrome review on Vercel and a real Meteor approval. Its finalized reservation is publicly verifiable. The next chapters follow completed bookings #10 and #11.
Mobile-width review and signature initiation; later confirmation at desktop width. No physical phone test.
03 / NORMAL RETURN · BOOKING #10
The custodian accepts the return with zero damage. The borrower withdraws the full bond. Two votes on treasury #15 pay the usage fee back to the community, where the DAO can decide how to use it.
Check the 8 normal-return transactions ↗Booking closed · 8 recorded transactions
04 / DISPUTE · BOOKING #11, PROPOSAL #16
The custodian reports damage. A council member proposes a 0.003 NEAR deduction. The first approval cannot release escrow: the policy requires both council accounts.
Read the dispute case file ↗Booking disputed · proposal pending · zero credits
05 / SECOND APPROVAL → DAO EXECUTION
The second approval lets Sputnik call the library contract. Proposal #16 creates credits; treasury #17 and the borrower’s withdrawal actually move the funds. The verifier checks child receipts, too.
Check the 11 dispute transactions ↗Credits → separate withdrawals → final receipts
06 / DON'T TAKE OUR WORD FOR IT
Verify both completed flows and the separate mobile reservation. Fresh public reads check bookings, proposal votes, final receipts and the accounting invariant.
Read the recorded proof ↗Then run fresh public checks ↗
No login or wallet. Recorded proof stays readable during RPC outages; it is not a fresh PASS.
Fresh results appear only on the verification page. Later demos can change whole-library totals.
Illustrated replay of recorded evidence, not a live transaction or real-time execution. Choose Play to begin, or read each chapter below.
WHAT THIS PROVES
The two completed flows contain 19 real NEAR testnet transactions. Booking #13 adds a separate mobile-initiated reservation from the public Vercel demo. The owner approved Meteor prompts. One operator controls the demo's two council accounts. Evidence fixtures are synthetic; a hash does not prove physical condition. The prototype is not audited.