Arguments worth keeping.
Start with the question you need answered. Follow the mechanism, compare alternatives, inspect the sources, or keep a worksheet for your own review. An unanswered empirical question stays unanswered.
Mining incentives and economic acceptance
Who produces, verifies and accepts a payment; how credible rejection can deter an attack; and why coordination and continued mining still matter.
Updated 2026-10-05 · Evidence scope stated insideMechanism guide · Governance and responsibilityStewardship and authority in an open system
A practical account of transferable competence, institutional correction and independent stewards, with BSV’s current authority boundaries made explicit.
Updated 2026-10-05 · Evidence scope stated insideCase study · Wallets and compatibilityWhen a conforming wallet still breaks an application
The October 4 Zanaadu exchange explains why interface checks, wallet policy, release communication and successful user workflows need separate evidence.
Updated 2026-10-05 · Evidence scope stated insideDecision guide · Applications and evidenceWhen a shared ledger helps an IoT record
A sensor example separates signatures, truth, retention, ordering and settlement, then compares database logs, transparency services and ledger anchors.
Updated 2026-10-05 · Evidence scope stated insideField note · PreservationA Merkle proof is a receipt, not a backup
Retained evidence, current accepted history, application meaning and a practical recovery manifest.
Includes recovery and settlement boundariesA connected reference library
The short answers give you a stopping point. These guides explain the reasoning. The evidence inventory separates documentation and reports from tests. Metanet.fyi explains the application model; its recovery checklist develops the operational work.
For reuse: public library JSON · machine-readable index · revision feed. Preserve source dates and conditions when taking an answer elsewhere.