Dispute and resolve

Disputes

If maker and taker disagree about the payout during a bounty that is in progress, either party can open a dispute. The dispute resolution mode chosen by the maker at bounty creation will determine whether the dispute process happens automatically via oracle attestations or manually via juror panel voting process. The bounty’s dispute-resolution choice cannot be changed after funding.

Evidence

Both parties can present evidence and their reasoning in the first stage of the dispute resolution process. The dispute resolution mode will determine who reviews the dispute and how the evidence is processed.

Human-mode dispute resolution

Bonded jurors are selected randomly from the public juror registry for each dispute. They review the evidence manually, vote, and the threshold of juror-held keys signs either Leaf B in favour of the taker or Leaf C in favour of the maker in the escrow vTXO. Non-participation of a juror can trigger slashing of the juror bond vTXO and a re-panel.

Oracle-mode dispute resolution

Independent bonded oracles query the declared source (API endpoint) and publish positive or negative attestations based on passing or failing CI pipelines. A threshold signs the matching escrow path. If attestations conflict, the case escalates to human-mode dispute resolution.

Joining the juror registry

Jurors are incentivised with the juror reward - voting in a majority will yield a reward in Bitcoin. A new juror creates a bond vTXO, publishes registration and specialisations, stays available, and refreshes the bond as required. Deregistration removes future eligibility but not duties on an active panel. In other words jurors cannot effectively deregister until their active disputes are resolved.