Disputes & DAO

The host says who came. A guest who disagrees can dispute it, and a DAO council decides.

Court onFor deposit events created from now on

Council: nearvent-court.sputnik-dao.near · NearBlocks. Each event keeps the rules it was created with, so earlier events stay without a court.

How a dispute works

1
The host publishes who came
After the event, from the door check-ins. Nothing is paid yet.
Guest marked as checked in at the door
2
Not on the list? Dispute it
For 12 hours any guest can dispute one record: “I came” or “they didn’t”. It locks one deposit.
You’re not on the host’s list: I Came, Open a Dispute
3
The council decides
Our bot opens a vote in the DAO with a link to the door log. 3 council votes decide, within 7 days after the window.
Dispute waiting for the council, with the door check-in log
4
Anyone settles
Payouts follow the final list. Nobody votes if nobody disputes.
Payout ready to withdraw

Who gets what

The councilThe guest who disputed
AgreesGets the deposit back, plus the payout if they came
DisagreesLoses the deposit: half to the treasury, half to the guests who came
Doesn’t decide in timeGets the deposit back; the host’s list stands
Cancels the eventEveryone gets their deposit back, dispute deposits too

An optimistic oracle

True unless challenged
The host’s list is a claim. If nobody disputes it within 12 hours, it is final.
finalize → Submitted · challenge window 12 h · settle
The court is on-chain
The escrow takes a verdict only from the event’s own DAO, through an approved proposal. Not from us, not from the host.
Sputnik DAO v2 · FunctionCall resolve_dispute / void_event
The evidence can’t change
The door log only grows and freezes when the list is published. Every DAO proposal carries its hash.
/api/checkin?log=1 · door log sha256 in the proposal
A bot does the paperwork
Our keeper opens the votes and settles after the deadline. Anyone can do the same by hand.
keeper · add_proposal · settle (permissionless)

Safeguards

  • A lost dispute costs a deposit, so spam isn’t free.
  • One “they didn’t come” claim per guest per event.
  • Registration closes at the start: the host can’t add friends after seeing who came.
  • Each event copies the rules when it is created. The owner can’t change a running event.
  • The court DAO and the treasury can’t host events.
  • A host bond can be switched on for new events: it pays the guests who win a dispute. It is off now.

A DAO can host too

Any Sputnik DAO (*.sputnik-dao.near) can host events. Its council runs Manage and the door, and publishing or cancelling become DAO proposals. The deposits stay in the escrow and go to the guests who came.

FAQ

Who is on the council?+
The members of the court DAO. 3 votes decide, and every vote is public in the DAO.
Does every event have a court?+
Deposit events created while the court is on. Tickets and free events don’t need one.
What if the council never votes?+
7 days after the window, open disputes expire: the list stands and every dispute deposit comes back.
Can I dispute from MetaMask?+
Yes, with one signature through NEAR Intents. You need one deposit of USDC in your NEAR Intents balance.
Can the council take the money?+
No. It can only say who came or cancel the event. The escrow pays the guests.

Methods and money rules: Smart Contract.

NextReputation
Loading component…