ck CommonKitNEAR TESTNET

THE CAMERA STORY / RECORDED EVIDENCE

One shared camera.
Two ways home.

A campus club lends its camera. It comes back clean—or someone reports damage. Follow who decides and where the bond goes.

Illustrative community camera kit
Illustrative equipment · controlled testnet demonstration

0.111 NEAR attached to each reservation

0.010 refundable bond + 0.001 usage fee

0.100 retained storage, separate from principal

Testnet funds only. Gas and DAO proposal bonds are additional and separate.

BOOKING #10 · 8 RECORDED TRANSACTIONS

Clean return.
Full bond back.

The custodian accepts the camera’s return. No damage deduction is made.

Borrower received
0.010 NEAR
Community DAO received
0.001 NEAR

Recorded testnet payouts · not current balances

  1. Custodian accepts the returnZero damage. The full bond becomes borrower credit.
  2. Withdrawals move the moneyThe borrower withdraws their credit. Treasury proposal #15 needs both council votes to pay the DAO.

Final snapshot: · block 276879750

Inspect all 8 recorded transactions
  1. Borrower reserved equipment and attached 0.111 NEAR ↗borrower.commonkit-mw7dph80.testnet · reserve
  2. Custodian acknowledged pickup and evidence ↗custodian.commonkit-mw7dph80.testnet · pickup
  3. Borrower requested return with evidence ↗borrower.commonkit-mw7dph80.testnet · request_return
  4. Custodian accepted the matching return evidence ↗custodian.commonkit-mw7dph80.testnet · accept_return
  5. Borrower withdrew the full bond ↗borrower.commonkit-mw7dph80.testnet · withdraw
  6. Council proposed withdrawing the DAO fee credit ↗custodian.commonkit-mw7dph80.testnet · add_proposal
  7. Custodian council account cast the first treasury vote ↗custodian.commonkit-mw7dph80.testnet · act_proposal
  8. Second council account cast the final treasury vote ↗commonkit-mw7dph80.testnet · act_proposal
Run fresh normal-return checks ↗

BOOKING #11 · 11 RECORDED TRANSACTIONS

Damage disputed.
A council decision.

The custodian records a claim. The council decides the deduction using two approvals.

Borrower received
0.007 NEAR
Community DAO received
0.004 NEAR

Recorded testnet payouts · not current balances

  1. Both council accounts approveProposal #16 allocates 0.003 NEAR for damage. Credits are created; payment is a separate step.
  2. Withdrawals move the moneyThe borrower withdraws their credit. Treasury proposal #17 needs both council votes to pay the DAO.

Final snapshot: · block 276886320

Inspect all 11 recorded transactions
  1. Borrower reserved equipment and attached 0.111 NEAR ↗borrower.commonkit-mw7dph80.testnet · reserve
  2. Custodian acknowledged pickup and evidence ↗custodian.commonkit-mw7dph80.testnet · pickup
  3. Borrower requested return with evidence ↗borrower.commonkit-mw7dph80.testnet · request_return
  4. Custodian reported a dispute ↗custodian.commonkit-mw7dph80.testnet · dispute
  5. Council proposed the 0.003 NEAR damage decision ↗custodian.commonkit-mw7dph80.testnet · add_proposal
  6. Council member 2 cast the first settlement vote ↗custodian.commonkit-mw7dph80.testnet · act_proposal
  7. Council member 1 cast the second settlement vote ↗commonkit-mw7dph80.testnet · act_proposal
  8. Council proposed withdrawing the DAO credit ↗commonkit-mw7dph80.testnet · add_proposal
  9. Council member 1 cast the first treasury vote ↗commonkit-mw7dph80.testnet · act_proposal
  10. Council member 2 cast the second treasury vote ↗custodian.commonkit-mw7dph80.testnet · act_proposal
  11. Borrower withdrew their available credit ↗borrower.commonkit-mw7dph80.testnet · withdraw
Run fresh dispute checks ↗

THE MOMENT THAT MATTERS / BOOKING #11

One vote cannot
release the bond.

A proposal is not a payment. Neither is the first approval. The saved checkpoints show exactly where authority changes the outcome.

  1. 1 / 2 approvals0.011 NEAR stays escrowed

    Booking disputed. Proposal pending. Zero borrower or DAO credits.

    One-vote snapshot ↗First-vote transaction ↗
  2. 2 / 2 approvalsCredits: 0.007 + 0.004 NEAR

    0.007 for the borrower. 0.003 damage plus the 0.001 usage fee for the DAO. These are credits, not yet payouts.

    Settlement snapshot ↗Second-vote transaction ↗
  3. Separate withdrawalsBoth payments completed

    Borrower withdrawal and treasury proposal #17 execute the payouts. The final snapshot records both available credits at zero.

    Final snapshot ↗Recheck actual transfer receipts ↗

WHY THE COMMUNITY USES IT

The fee goes back
to the shared treasury.

Each completed borrowing cycle pays a usage fee to the community DAO. It can support upkeep and future equipment purchases through the DAO’s own decisions. This demo proves the fee withdrawal, not a real purchase or an operating community.

What the demonstration does—and does not—prove

The 19 transactions are real NEAR testnet actions approved through Meteor on the public Vercel demo. One operator controls both council accounts. The damage evidence is synthetic; its hash does not prove physical condition. There is no independent community pilot or audit claimed.

Booking #13 is separate: a real Meteor reservation initiated at 390 × 844 Chrome width, with later desktop confirmation. It is not a physical-phone test or a completed return. Inspect the mobile proof ↗