Current blocks and transactions are publicly inspectable.
AdoptionSourced answer
Where are the users?
“There are repositories and transaction totals, but no meaningful retained users.”
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.
Short answer
The short answer
BSV has live infrastructure, applications, wallets, and inspectable transactions. Those facts establish availability, not broad adoption. A credible adoption case needs defined active users, retention cohorts, successful workflows, economic activity, time windows, bot treatment, and independently checkable methods. Until that exists, say exactly what can be verified and keep the broader claim unresolved.
Mechanism and practical meaning
Capability is the beginning of the adoption case
Public wallet interfaces, code and transaction inspection make concrete work possible: a user-authorized action, a payment or a retained proof. The evidence inventory distinguishes those inspection surfaces from a tested workflow and a measured user cohort. We have not established broad retained-user adoption from the sources reviewed for this site; that is a scoped evidence gap, not a claim that no such data can exist.
| Signal | What this review establishes | Missing step |
|---|---|---|
| Standards and code | Published inspection surfaces | Versioned implementation test |
| Public user report | Attributed experience | Independent reproduction and resolution |
| Transactions | Activity on the rail | People, purpose and successful tasks |
| Retention | No complete independent measure established here | Defined cohort, time window and method |
What is true
The objection's strongest ground
- Code, standards, live applications, transactions, users, retained users, and sustainable businesses are different evidence levels.
- Automated or low-value transactions can inflate volume without corresponding human adoption.
- The ecosystem lacks a single independent public dashboard with cross-project retained-user methodology.
What remains unresolved
Do not claim more than the evidence
- Private product analytics may exist but cannot be treated as public proof without methods and auditable aggregates.
- This site does not infer user counts from block transactions or repository activity.
Inspect it yourself
What to inspect next
- Ask each project to define an active user, successful workflow, retention window, bot policy, and economic activity.
- Reproduce a live flow and distinguish availability from frequency of real use.
- Use chain data for transactions and fees, then obtain separate product data for people and outcomes.
Open to better evidence
What would change this answer?
Methodologically sound, repeatable retention and economic-use data would strengthen the adoption case. Continued inability to produce it keeps this objection unresolved even if tooling improves.
Evidence behind the answer
What the cited sources establish
Public repositories and demo catalogs provide a current application inspection surface.
Source desk
Read the underlying material
LiveWhatsOnChain explorerCurrent block and transaction inspection surface; explorer availability and interpretation remain third-party dependencies.WhatsOnChain · Source access 2026-10-05CodeBSV Blockchain GitHub organizationCurrent repository inventory and maintenance history; activity is not the same as production use.BSV Association contributors · Source access 2026-10-05ReferenceBSV Hub demo catalogMaintainer-curated catalog with repository and status claims. Recheck every live URL, repository, and usage claim.BSV Association · Source access 2026-10-05