THE COMMONKIT EVIDENCE DESK / SOCIAL MONEY
Follow the gear.
Check the money.
A smooth return. A disputed return.
Inspect both outcomes from public testnet receipts.
01 / CHOOSE A RECORDED FLOW
Two paths. Every payment accounted for.
Select a flow to run its checks.
Booking #10 · zero damage · treasury proposal #15
- Borrower refund
- 0.01 NEAR
- DAO usage fee
- 0.001 NEAR
Historical amounts to verify,
not current wallet balances.
LIVE VERIFICATION / NORMAL RETURN
Connecting to public RPC…
No checks have passed yet. Reading fresh data…
Finalized block: waiting for RPC
PASS = evidence matches · FAIL = mismatch · UNVERIFIED = evidence unavailable.
Saved snapshots never substitute for a live result. Each flow is checked separately. Historical receipts are read one at a time to reduce archive rate limits; checks can take a minute or longer.
THE CASE FILE
Evidence, decisions and payments.
Loading the recorded case file…
Evidence, one check at a time.
21 READ-ONLY CHECKS02 / CURRENT LIBRARY TOTALS
The books must balance.
Recomputed from every booking, credit and pending transfer at the same finalized block. These are whole-library totals; later borrowing can change them without changing either recorded rehearsal.
Principal only. Retained storage, proposal bonds and gas are separate.
Current ledger not verified yet.
NEW EVIDENCE / BOOKING #13 · 12 NOVEMBER
Small screen.
Real reservation.
A 390 × 844 Chrome review on the public Vercel demo, followed by a real Meteor approval. Inspect the exact 0.111 testnet NEAR reservation and the booking returned by the contract.
Reservation proof only. Completed return and dispute settlement are the separate bookings #10 and #11 above.
The screenshot and browser records document the mobile-width review and signature initiation. Final UI confirmation was observed at 1280 × 609. No physical phone was used; RPC cannot attest a browser’s viewport.
Not checked yet. Run six fresh, read-only checks. No wallet needed.
The receipt must match every signed field and all child outcomes. Booking terms and whole-library accounting are read at one finalized block. Later booking activity can change current status and totals.
Reproduce: npm run verify:testnet -- --flow mobile
03 / REPRODUCE THE CHECKS
Same checks.
Your terminal.
From the CommonKit repository, with Node.js 24. Built-in Node APIs only: no wallet, keys or dependency installation needed.
The default command checks both completed flows and the mobile reservation. Add a flow option to inspect just one.
# Both completed flows + mobile reservation
npm run verify:testnet
# Selected flow
npm run verify:testnet -- --flow normal
# Machine-readable report for both flows
npm run --silent verify:testnet -- --jsonExit 0: all checks pass · 1: mismatch · 2: incomplete/unavailable.
04 / KEEP THE EVIDENCE IN CONTEXT
Recorded checkpoints.
Captured on 9 November through Meteor on the public Vercel demo. These saved checkpoints explain intermediate balances; the results above come from fresh RPC reads.
What the evidence proves and its limits
Checks rely on public RPC responses, not independently verified light-client proofs. The code hash pins the recorded deployment; it is not a reproducible-build attestation or a security audit.
Both council accounts are controlled by the demo operator. Two distinct account approvals do not establish independent human governance. Synthetic evidence hashes bind files to calls but cannot prove physical custody or damage.
Normal return is accepted by the custodian. Two council votes authorize the DAO fee withdrawal; the first vote must not execute that withdrawal.
Withdrawals consume account credits. Receipts prove the recorded transfers, not a general per-booking withdrawal mechanism. Read the shared verification source ↗