Open-source BCH bounty platform linking repository tasks to smart-contract payments. Settlement depends on an oracle and maintainer approvals; delivery and adoption need separate assessment.
issues.cash connects BCH bounties to GitHub issues. Organizations fund bounties; contributors claim them when work merges; payouts are oracle-mediated through the platform's on-chain flow. The live site publishes platform stats: 3 bounties, 0.00303 BCH funded, 1 bounty claimed and paid out (0.00101 BCH), 1 contributor, 1 organization (dlbnco) as of 2026-09-22. [1]
Bounty infrastructure can connect maintainers with paid contributors. Smart contracts hold the bounty, but the oracle and maintainer control relevant settlement decisions. Historical observations of a deployment and small payout totals do not establish reliability, adoption, or full campaign completion. [1][2]
The repository (dlbnco/issues.cash) shows commits through 2026-05-11, including a Next.js upgrade, with 40+ pull requests merged historically. The FundMe campaign of January 2026 recorded 36 BCH funded. The live platform operates with the statistics above. [2][3]
The campaign explicitly requires trust in the oracle that invokes settlement and in maintainers who approve contributions. Self-hosting can reduce oracle dependence. Arbitration, reputation and stable-token bounties are future considerations, outside the funded initial scope. [5]
This autonomous report is a v2 reassessment of cited project material and the bundled Atlas campaign snapshot. Funding and creator testimony are distinct from independently verified delivery. A named human review is still required. [1]
Extracted commitments and source-reported achievements. A passed target date or funded campaign does not establish delivery.
No successful funding recorded for this round. Its scope is not counted as a funded obligation.
First funding attempt did not reach its goal; the same scope was relaunched in campaign 93. [4]
Source target: No date statedAtlas records 36 BCH. Delivery conclusions below reflect campaign statements; unresolved items require human evidence reconciliation.
Explicit campaign 93 commitment. A product/repository exists, but this review has not exercised or reconciled this individual capability against production evidence. [5]
Source target: 45–60 days after fundingExplicit campaign 93 commitment. A product/repository exists, but this review has not exercised or reconciled this individual capability against production evidence. [5]
Source target: 45–60 days after fundingExplicit campaign 93 commitment. A product/repository exists, but this review has not exercised or reconciled this individual capability against production evidence. [5]
Source target: 45–60 days after fundingExplicit campaign 93 commitment. A product/repository exists, but this review has not exercised or reconciled this individual capability against production evidence. [5]
Source target: 45–60 days after fundingExplicit campaign 93 commitment. A product/repository exists, but this review has not exercised or reconciled this individual capability against production evidence. [5]
Source target: 45–60 days after fundingExplicit campaign 93 commitment. A product/repository exists, but this review has not exercised or reconciled this individual capability against production evidence. [5]
Source target: 45–60 days after fundingExplicit campaign 93 commitment. A product/repository exists, but this review has not exercised or reconciled this individual capability against production evidence. [5]
Source target: 45–60 days after fundingExplicit campaign 93 commitment. A product/repository exists, but this review has not exercised or reconciled this individual capability against production evidence. [5]
Source target: 1 year of serviceExplicit campaign 93 commitment. A product/repository exists, but this review has not exercised or reconciled this individual capability against production evidence. [5]
Source target: 1 year of serviceProfile revision 3 · updated 2026-09-26 · Initial research snapshot
Live fetch 2026-09-22; bounty list, stats panel, organizations and contributors observed.
GitHub API 2026-09-22; last push 2026-05-11, commit history through PR #40.
Atlas-archived; 35.99999 BCH recorded, success, 2026-01-20.
Campaign text and funding reviewed from the bundled Atlas snapshot; not a fresh retrieval of the campaign page. Funding is not delivery evidence.
Campaign text and funding reviewed from the bundled Atlas snapshot; not a fresh retrieval of the campaign page. Funding is not delivery evidence.