Bounty

A signed offer of bitcoin for work under declared terms. A bounty can be in the following states

  • open = published but not funded,
  • in progress = funded and work has started,
  • claimed = completed (taker has been paid), or
  • in dispute = maker and taker do not agree on payout

Maker creates the bounty

The maker publishes an addressable Nostr event with a stable bounty ID, description, amount, deadline, check-ins, refund address, status, and dispute-resolution choice. Oracle-mode bounties also name the oracle set, threshold, endpoint, and structured criteria.

Proof of funds

At the time of bounty creation, the maker references a maker-controlled commitment vTXO. It is a proof of funds, not the bounty escrow. Taker's client warns if funds move or if one outpoint backs several current bounties.

Clarify and accept

Potential takers ask questions in the public thread and negotiate amount and criteria. Takers will sign individual acceptance Nostr events, signaling they are ready to start working. The maker will construct the final escrow by including information from one acceptance event, ultimately choosing which taker to collaborate with.