Primary records before talking points.

Follow the question into its evidence

Guides, comparisons and downloadable worksheets connect these sources to the argument they support. Metanet.fyi explains the application layer; its recovery checklist develops continuity work.

• Bitcoin whitepaper · sections 5, 6 and 8 · documented. The original network, incentive and verification model. It does not document later BSV institutions.
• SV Node Safe Mode · documented. Documents protective detection and operator intervention for SV Node. Not a deployment or convergence test.
• Network Access Rules · Part III · documented. Published Association directive powers and event categories. Read the operative text for scope and conditions.
• SV Node alert system · documented. Documents signed information and directive messages. Message authentication is not a judgment on the merits, and documentation is not a deployment audit.
• BIP 50 · March 2013 chain fork post-mortem · documented. Records software incompatibility, coordinated downgrade and movement of mining hashpower, disruption and a double spend.
• BRC-187 · stewardship opinion · interpretation. Ty Everett’s authored stewardship framework. BSV.place is maintained by Project Babbage; this is a related author’s position, not independent corroboration or a deployed governance specification.
• BRC-100 · wallet to application interface · documented. The interface specification; implementation, policy and workflow outcomes need their own evidence. No new compatibility test is implied by this guide.
• TypeScript stack security policy · documented. Project-specific reporting policy. A policy is not an audit, a promised bounty, or evidence that this compatibility incident matches an advisory.
• NIST FIPS 186-5 · Digital Signature Standard · documented. Signature verification addresses authenticity and integrity under key assumptions. It cannot establish that a sensor measured the world correctly.
• RFC 9162 · Certificate Transparency v2 · documented. A concrete non-blockchain transparency design; not a drop-in IoT system. Inclusion, consistency, retention and monitoring are distinct responsibilities.