There are inspectable code and demo surfaces against which bounded capability claims can be tested.
Trust & reputationSourced answer
How should a serious person respond to the “scam” or “cult” label?
“BSV is a cult, a grift, or an affinity scam built to keep bagholders loyal.”
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
Do not answer contempt with demands for loyalty. Translate the label into testable questions: What was promised? What works now? Who benefits? What is the user's risk? Which claims failed? Can the user leave? Evidence cannot prove that every participant is sincere, but a product can avoid manipulative patterns by making bounded claims, exposing dependencies, and offering a low-risk test path.
Mechanism and practical meaning
Follow a promise through to its outcome
For a claim that a wallet works with an app, the useful record is the promised behavior, exact versions, reported failure, maintainer response and successful retest if one exists. The October compatibility case gives a concrete example with the outcome still unverified. A functioning product would not, by itself, answer a separate report of deception or harm. Address that report on its own evidence and acknowledge our own conduct where relevant.
What is true
The objection's strongest ground
- BSV advocacy has often mixed technical claims with identity, faction, or price narratives.
- People can reasonably treat repeated overclaiming, missing proof, and hidden dependencies as trust warnings.
- Working code is relevant evidence but does not answer whether marketing, financing, or investment conduct was lawful or fair.
What remains unresolved
Do not claim more than the evidence
- This site cannot certify the integrity of every BSV project, promoter, founder, or transaction.
- The absence of a proven accusation is not proof that a product is safe; users still need ordinary diligence.
Inspect it yourself
What to inspect next
- Convert the accusation into a ledger of exact promises, dates, responsible parties, evidence, and outcomes.
- Test the smallest product flow without buying a large balance, accepting an identity claim, or joining a community.
- Check licenses, custody, data export, fees, funding, corrections, and the operator's ability to change terms.
Open to better evidence
What would change this answer?
Repeated material misrepresentation, hidden conflicts, or inability to demonstrate promised utility would justify a harsher assessment. Consistent delivery, transparent gaps, and independently verified use would improve it.
Evidence behind the answer
What the cited sources establish
Source desk
Read the underlying material
CodeBSV TypeScript stackCurrent monorepo for SDK, wallet, overlay, messaging, middleware, helpers, infrastructure, documentation, and conformance vectors.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