Teranode source and a public Teratestnet runner are available for inspection.
Scale & economicsSourced answer
Is BSV scaling real, or a datacenter marketing claim?
“Teranode throughput is vendor hype. Large blocks centralize operators, and cheap fees reflect missing demand.”
Answer with conditions · 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 deliberately moves heavy validation and storage toward specialized block producers while expecting most applications to use headers, Merkle proofs, and services. Teranode source and a public testnet runner now make implementation more inspectable. A vendor or testnet benchmark still does not establish sustained mainnet throughput, economically useful demand, competitive block production, or reproducibility on disclosed hardware.
Mechanism and practical meaning
Specialization and lightweight verification have distinct benefits
Specialized block production can move heavy work away from ordinary application users, while relevant proofs let clients inspect what they need. This architecture is useful if service cost, availability and verification remain acceptable for the task. Its existence does not establish competitive production or economical demand.
Keep code, measured capacity, production use, operator diversity and total cost as separate records. A promotional daily transaction target is neither an independently reproduced benchmark nor evidence of customers. No new throughput test or current beneficial-control estimate was produced for this revision.
| Claim | Required record |
|---|---|
| Measured capacity | Revision, hardware, workload, duration, latency and failures |
| Production use | Dated network window and useful workflow attribution |
| Operator diversity | Observed producers, attribution limits and supported control evidence |
| Economics | Full cost per successful task and continuing service incentives |
What is true
The objection's strongest ground
- Larger blocks increase bandwidth, propagation, validation, and archival requirements somewhere in the system.
- SPV reduces the verification burden for many clients; it does not make block production free or guarantee competitive mining.
- A large historical block, a peak benchmark, a sustained production rate, low fees, and useful demand are different measurements.
What remains unresolved
Do not claim more than the evidence
- This site does not treat Association-published throughput as independent reproduction.
- Public source does not by itself establish production readiness, fault tolerance, or total operating cost.
Inspect it yourself
What to inspect next
- Record code revision, topology, hardware, workload, transaction mix, duration, latency, error rate, cost, and failure recovery for every benchmark.
- Compare current mainnet blocks, fee distribution, transaction mix, stale blocks, and producer distribution.
- Reproduce the test outside the maintainer's environment and publish raw results, including failures.
Open to better evidence
What would change this answer?
Independent sustained tests, transparent cost curves, production deployment, and broader operators would strengthen the claim. Unreproducible benchmarks or worsening concentration would weaken it.
Evidence behind the answer
What the cited sources establish
SPV is part of both the original paper and current BRC verification model.
Source desk
Read the underlying material
CodeTeranode source repositoryCurrent public implementation. Source availability does not validate throughput or production-readiness claims by itself.BSV Association contributors · Source access 2026-10-05CodeTeranode Teratestnet runnerPublic instructions and tooling for running the test network; inspect hardware and workload before comparing results.BSV Association contributors · Source access 2026-10-05PrimaryBitcoin: A Peer-to-Peer Electronic Cash SystemThe original paper; read its proof-of-work, incentives, privacy, and SPV claims in their own terms.Satoshi Nakamoto · Source access 2026-10-05PrimaryBRC-67 — Simplified Payment VerificationApplication-side criteria for verifying transaction inclusion and ancestry with proofs.BRC contributors · Source access 2026-10-05LiveWhatsOnChain explorerCurrent block and transaction inspection surface; explorer availability and interpretation remain third-party dependencies.WhatsOnChain · Source access 2026-10-05