Borrow the camera.
Follow the money.

The story, in text

Shared gear needs shared responsibility. A campus club lends its camera. If it comes back damaged, who decides what happens to the deposit?

Meet CommonKit: equipment borrowing and community dispute settlement on NEAR testnet.

A borrower reserves the camera with a refundable bond. The custodian records pickup and inspects the return. For a clean return, the full bond becomes borrower credit. Separate withdrawals pay the borrower and the community treasury.

For a disputed return, funds stay locked while the Sputnik DAO considers the damage claim. Evidence hashes help match files; they do not prove what physically happened. One council vote leaves the principal escrowed. The second authorizes the allocation. Withdrawals then transfer the money.

Now, let's open the real app.

No wallet is needed to explore. Start here explains the borrower, custodian and council roles. Choose either recorded outcome, or browse the camera and review the fee, bond and retained storage before connecting Meteor.

Here is the normal return: booking ten. The borrower withdrew point zero one NEAR, and the DAO withdrew the point zero zero one fee.

Booking eleven shows the dispute. One vote kept point zero one one NEAR locked. After two approvals, the borrower withdrew point zero zero seven, and the DAO withdrew point zero zero four.

Open the public verifier to check execution and payment receipts. Our latest read passed fifty-four checks, including a separate mobile-width reservation.

This is a testnet prototype with synthetic evidence and one operator controlling the demo council accounts. Explore both flows at commonkit-testnet dot vercel dot app.

AI illustrations from the supplied Gemini Notebook film, ElevenLabs narration and real public-app capture. Media provenance and credits ↗