The BSV Hub publishes a catalog of demos and onboarding projects with repository and status claims.
Why have so many funded BSV projects disappeared?
“Accelerators and ecosystem patrons funded projects that vanished. The ecosystem burns money and rebrands the failures.”
Open evidence question · Updated 2026-10-05 · Next review 2026-11-05
By BSV.place / Project Babbage. Editorial review; source access dates below. No independent product retest is implied.
The short answer
No one should defend every funded project. A grant, accelerator place, press release, repository, demo, maintained product, retained user base, and sustainable business are different statuses. The current BSV Hub and GitHub organizations provide discovery surfaces, but their labels need independent verification. A durable inventory should name owner, funding disclosure, last verified date, live proof, maintainer, license, and shutdown state.
Preserve a project’s outputs and its actual status
Use a dated record for each selected project: announced, inspectable, reported in use, independently tested, sunset or unknown. An active repository is a maintenance signal, not proof of sustainability. A failure is not by itself evidence of fraud. Public funding relationships should be attributed to their actual documents.
The proof inventory gives bounded inspection records; it is not a complete funding-to-outcome ledger. Historical application records may survive a frontend, but claims about recovered content still require a scope and completeness check. Retain shutdown notices and export instructions instead of making old promises disappear.
The objection's strongest ground
- A demo or repository does not establish a maintained service, users, or sustainable business.
- Official catalogs are useful for discovery but have an incentive to present projects favorably.
- Failure becomes harder to learn from when status, funding, ownership, and shutdown reasons are not recorded.
Do not claim more than the evidence
- This site does not yet have an audited historical ledger of every BSV-funded project.
- A closed project is not automatically fraud or waste; experiments can fail honestly and still produce reusable work.
What to inspect next
- Check the live URL, repository activity, releases, issue response, named maintainers, and a complete user flow.
- Record funding source when documented, current legal owner, status date, and evidence for the status label.
- Preserve shutdown notices, source, export instructions, and lessons instead of silently deleting listings.
What would change this answer?
A transparent inventory showing maintained projects, repeat use, accountable funding, and honest sunsets would improve the record. Repeated promotion without verifiable delivery would worsen it.
What the cited sources establish
GitHub organizations expose current repository and maintenance evidence.
Repository activity is one status signal, not proof of users or sustainability.