ECOSYSTEM FUNDING INTELLIGENCE PHASE 01 · MVP
← All projects
Libraries & tooling

issues.cash

Issues.cash connects open-source issue work to BCH bounties, helping maintainers fund specific engineering outcomes.

Activity unverified
Flipstarter / FundMe

Project overview & BCH-1 report · combines linked funding rounds, commitments and results. Each campaign retains its own proposal review; funding success does not establish delivery.

RECORDED FUNDED AMOUNT36.00 BCH
CAMPAIGNS LINKED2

Recorded campaigns only; historical coverage has not been established as complete. The BCH and historical USD figures cover linked records, not lifetime project funding.

FUNDING AT HISTORICAL BCH PRICES

≈ $20,615.04

1 of 1 recorded funded campaigns priced at their own dates. 0 use archive dates rather than confirmed funding dates. Daily reference prices, not actual USD proceeds or today’s value.

Project brief
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]

Milestones
PROMISES & EVIDENCE12 milestones

What has been promised?

Extracted commitments and source-reported achievements. A passed target date or funded campaign does not establish delivery.

issues.cash

FundMe · 36 BCH · Atlas recorded
[5]
6 / 11 reported or verified complete55%

Tracked-item counts do not measure full scope coverage or the relative value of each outcome.

5 items not yet assessed. Missing evidence review does not establish non-delivery.

Included in score · eligible 2026-07-20

Campaign 1afe01a371065e6f · 2026-01-20

Autonomous summary

6 of 11 tracked items complete (reported, verified or explicitly presumed); 5 unassessed. These are raw counts, not economic weights or proof of full scope coverage. Eligible for this dated assessment; unknown scope is not a failed commitment.

01

GitHub repository integration

Reported complete

The public README documents this implemented repository/bounty capability. Classified as source-reported delivery; no wallet transaction or independent end-to-end test was performed. [5][6]

Source target: 45–60 days after funding
02

GitLab repository integration

Reported complete

The public README documents this implemented repository/bounty capability. Classified as source-reported delivery; no wallet transaction or independent end-to-end test was performed. [5][6]

Source target: 45–60 days after funding
03

Create, fund and cancel bounties

Reported complete

The public README documents this implemented repository/bounty capability. Classified as source-reported delivery; no wallet transaction or independent end-to-end test was performed. [5][6]

Source target: 45–60 days after funding
04

Bounty funding verification

Reported complete

The public README documents this implemented repository/bounty capability. Classified as source-reported delivery; no wallet transaction or independent end-to-end test was performed. [5][6]

Source target: 45–60 days after funding
05

Automatic settlement on merge

Reported complete

The public README documents this implemented repository/bounty capability. Classified as source-reported delivery; no wallet transaction or independent end-to-end test was performed. [5][6]

Source target: 45–60 days after funding
06

Expiry and automatic refund

Status unknown

The README describes expiry and direct maintainer reclaim, which does not fully reconcile the campaign’s automatic-refund wording. Partial implementation evidence remains open for acceptance. [5][6]

Source target: 45–60 days after funding
07

Public bounty list and statistics

Reported complete

The public README documents this implemented repository/bounty capability. Classified as source-reported delivery; no wallet transaction or independent end-to-end test was performed. [5][6]

Source target: 45–60 days after funding
08

One year of oracle hosting

Status unknown

A one-year service obligation runs from January 2026 into January 2027. It is not yet due for final closeout; current repository/service existence does not prove the entire future period. No retrospective failure is assigned. [5][7]

Source target: 1 year of service
09

One year of maintenance and security updates

Status unknown

A one-year service obligation runs from January 2026 into January 2027. It is not yet due for final closeout; current repository/service existence does not prove the entire future period. No retrospective failure is assigned. [5][7]

Source target: 1 year of service
10

Publish fee model and founding-contributor exemptions

Status unknown

The campaign update changes zero commission to 1.5%, with lifetime zero-fee credit per 3 BCH contribution. Preserve this amendment; benefit fulfillment is not yet reconciled. [7]

Source target: No date stated
11

Deliver the two premium BLISS tickets

Status unknown

Campaign update offers two premium event tickets to qualifying top contributors. Acceptance/delivery evidence was not recovered. [7]

Source target: No date stated

issues.cash

FundMe · Funding confirmation pending · Atlas recorded
[4]
0 / 1 reported or verified complete0%

Tracked-item counts do not measure full scope coverage or the relative value of each outcome.

1 items not yet assessed. Missing evidence review does not establish non-delivery.

Funding date unconfirmed — excluded from score

Campaign 77f2043f6a40bec0 · 2026-01-15

Autonomous summary

0 of 1 tracked items complete (reported, verified or explicitly presumed); 1 unassessed. These are raw counts, not economic weights or proof of full scope coverage. Funding/date reconciliation is unresolved; excluded from scoring.

01

Original bounty-platform proposal

Status unknown

First funding attempt did not reach its goal; the same scope was relaunched in campaign 93. [4]

Source target: No date stated
Open research
OPEN RESEARCH

What still needs checking

  • Resolve automatic-refund versus maintainer-reclaim acceptance.
  • Verify contributor fee exemptions/rewards and the continuing service period.
  • Independent human review remains required. No current retrieval failure is evidence of historical non-delivery.
EVIDENCE LEDGER

Sources & provenance

Profile revision 5 · updated 2026-11-11 · Initial research snapshot

  1. issues.cash live platform ↗Primary source · inspected 2026-11-11

    Reopened for the locked 12 November methodology. Response SHA256 00019db962135e2094dee4aa0c3dd7d06657c91d89dc1162ebd94767c0a44c17; source extract preserved in the cohort audit. Creator statements and source code are not independent deployment or financial verification.

  2. dlbnco/issues.cash GitHub repository ↗Primary source · inspected 2026-09-22

    GitHub API 2026-09-22; last push 2026-05-11, commit history through PR #40.

  3. issues.cash FundMe campaign ↗Archived campaign · inspected 2026-09-22

    Atlas-archived; 35.99999 BCH recorded, success, 2026-01-20.

  4. issues.cash ↗Archived campaign · inspected 2026-09-26

    Campaign text and funding reviewed from the bundled Atlas snapshot; not a fresh retrieval of the campaign page. Funding is not delivery evidence.

  5. issues.cash ↗Archived campaign · inspected 2026-09-26

    Campaign text and funding reviewed from the bundled Atlas snapshot; not a fresh retrieval of the campaign page. Funding is not delivery evidence.

  6. issues.cash · README ↗Primary source · inspected 2026-11-11

    Reopened for the locked 12 November methodology. Response SHA256 281be7871db868e8e200c017f8c5e8c70627d1a0d55ec2a863970ea12ab0e38c; source extract preserved in the cohort audit. Creator statements and source code are not independent deployment or financial verification.

  7. issues.cash · FundMe 93 ↗Primary source · inspected 2026-11-11

    Reopened for the locked 12 November methodology. Response SHA256 9e923f0d45df50ba7c4bf756e77f188616722f8903a5153cdbcc556f78f23cd6; source extract preserved in the cohort audit. Creator statements and source code are not independent deployment or financial verification.

  8. Retained funding receipt · issues.cash ↗Primary source · inspected 2026-10-29

    Retained Atlas recovery/chain observation, not freshly refetched in this audit. Funding date uses claim/block timestamp, not archive discovery. Snapshot retained in the audit evidence; public explorer is the receipt reference.

  9. issues.cash · release history ↗Primary source · inspected 2026-11-11

    Reopened for the locked 12 November methodology. Response SHA256 a8530690b7d8d6395152a6c3b7c955e4d79695746da673c3c74cd1fe8666ec59; source extract preserved in the cohort audit. Creator statements and source code are not independent deployment or financial verification.

  10. issues.cash · official project page ↗Primary source · inspected 2026-11-11

    Reopened for the locked 12 November methodology. Response SHA256 00019db962135e2094dee4aa0c3dd7d06657c91d89dc1162ebd94767c0a44c17; source extract preserved in the cohort audit. Creator statements and source code are not independent deployment or financial verification.