PROJECT BRIEF · SOURCE-BASED EXTRACTION
Problem and BCH usefulness
BCH-native GitHub/GitLab bounty settlement addresses a real funding workflow. Existing hosted bounty systems and direct payments are substitutes; the reviewed deployment shows only minimal use, so 7 recognizes meaningful capability without assuming broad demonstrated demand. [7][6][9][10][1]
Alternatives and added value
FundMe and Flipstarter raise project budgets; issues.cash targets repository issues and merge-triggered workflows. General bounty platforms are substitutes, but its BCH-native contract path is a specific increment. No exclusive-market claim is made. [7][6][9][10]
Reach / Scalability
Public site reports 0 active bounties, 1 claim, 1 contributor and 1 organization. This is concrete limited deployment activity, supporting 3, rather than substituting GitHub/GitLab integration capability for adoption. Self-hosted/private use is outside observed coverage. Public deployment totals only; not all possible self-hosted instances. Small payouts are not a cost ratio and do not prove all work was unused. [7][6][9][10][1]
Funding and dollar inputs
Eligible recorded funding: 36.00000000 BCH; approximately $20,615.04 using retained historical USD reference prices. These are funding equivalents, not actual expenditure. A zero eligible subtotal with missing funding records does not mean zero development cost. Unconfirmed dates and grace-window rounds are excluded. [7][6][9][10][1]
Funded scope and delivery
Core lifecycle and integrations have release/source evidence. The promised automatic expiry refund is documented as maintainer reclaim, a material semantics difference; continuing hosting is not overdue. Most functionality shipped with a substantive scope difference fits 7. The usage result is not itself used as a delivery penalty. [7][6][9][10][1]
Impact versus cost
Retained eligible funding is $20,615.04. The public mainnet site reports 1 claim, 1 contributor, 1 organization and 0.00101 BCH paid out; these are application-reported, not independently chain-audited totals and may include demonstration use. Combined with the delivered reusable platform, this supports limited demonstrated value 4, not a claim of no benefit or definitive global inactivity. [7][6][9][10][1]
Open work and execution
Open repository documentation explains the oracle trust boundary and the updated 1.5% fee model. The earlier zero-commission promise and contributor exemptions must not silently vanish. [7][6][9][10][1]
Evidence confidence and coverage
Assessment revision bch1-autonomous-v2-2026-11-12-applicability. Source refresh is bounded; HTTP success is not claim verification. Unavailable/JS-only sources do not erase accepted evidence. Ratings express anchored judgments, not precise measured completion percentages. Analyst simulation: primary-source claims and retained campaign evidence; independent on-chain spending, full deployment testing and matched peer-cost/usage datasets are not established. Original campaign identities and recorded completion states are preserved. Unassessed work is neither failed nor delivered. [7][6][9][10][1]