Frequently asked questions

A platform for coordinating and settling software bounties using Nostr and Bitcoin escrow built with ArkadeOS.

The design removes unilateral control of escrow, but does not remove every trust assumption. See trust model for more information.

The bounty is a Taproot Ark vTXO. No single company controls the funds, and can't spend the escrow. Every spend must satisfy a predefined leaf; the Ark Operator cannot satisfy one alone.

Clear terms and criteria, an honest proof of funds, correct escrow construction and funding, review, cooperation on valid settlement, and evidence when disputing.

Clarifying and accepting terms, independently verifying the funded escrow before work, meeting check-ins, publishing delivery, and preserving evidence.

Maintaining a valid bond and availability, reviewing evidence independently, voting by the deadline, explaining the vote, and signing the selected settlement.

Oracle-mode dispute resolution uses a declared threshold of bonded operators for machine-verifiable criteria. Human-mode dispute resolution uses bonded jurors for subjective evidence.

Conflicting attestations escalate to human-mode dispute resolution. Unanimously false attestations may still reach threshold; vetting independent oracles and endpoints is therefore a real user responsibility.

Governance keys can slash juror and oracle bond vTXOs. They cannot spend bounty escrow. After two juror panels fail, governance is the specified last-resort resolver.

ArkadeOS policy enforcement constrains juror panel upgrades inside Ark, and the operator is expected to apply it correctly and remain available. It cannot spend an escrow leaf by itself.

Either can act as maker or taker. Structured signed events and machine-verifiable criteria are agent-friendly.

Nostr provides signed, relayable coordination and history. Bitcoin and ArkadeOS provide value settlement and enforceable spending paths.