The resource desk
Primary records before talking points.
A compact path into the documents, code, and live systems that can confirm—or contradict—the claims on this site.
01
Primary records
Start here for legal, historical, protocol, and governance claims.
COPA v Wright — approved judgmentOfficial High Court publication of the approved judgment and identity findings.Bitcoin: A Peer-to-Peer Electronic Cash SystemThe original paper; read its proof-of-work, incentives, privacy, and SPV claims in their own terms.BSV Network Access RulesThe published agreement governing the Association-node relationship; it is evidence of the stated rules, not independent proof of their application.Network Access Rules — Part III, Enforcement RulesDirective events, restrictions, and permitted steps including freezes, reassignment, peer controls, and block invalidation.Network Access Rules — Part IV, Dispute Resolution RulesPublished dispute path; inspect scope, forum, standing, and remedies rather than assuming an appeal mechanism.Bitcoin SV node — Open BSV LicenseOperative repository license. Version 5 conditions derived software use on BSV blockchains.
02
Standards to read
Specifications establish what is proposed. Implementations and shared tests establish what interoperates.
Bitcoin Request for Comments indexPublic specifications and proposal history; a published specification is not itself proof of independent adoption.BRC-100 — Unified wallet-to-application interfaceThe current unified interface covering wallet actions, signatures, encryption, certificates, permissions, and discovery.BRC-67 — Simplified Payment VerificationApplication-side criteria for verifying transaction inclusion and ancestry with proofs.BRC-103 — Mutual authentication and certificate exchangePeer-to-peer authentication, message signatures, and selective certificate exchange protocol.BRC-105 — HTTP service monetization frameworkSpecification for authenticated HTTP 402 pay-per-request flows; implementation and demand must be verified separately.
03
Code and conformance
Inspect implementation, tests, license, current maintenance, and known gaps.
BSV TypeScript stackCurrent monorepo for SDK, wallet, overlay, messaging, middleware, helpers, infrastructure, documentation, and conformance vectors.BSV TypeScript conformance corpusLanguage-neutral vectors and runners. Inspect current coverage and parity before calling the whole interface interoperable.Teranode source repositoryCurrent public implementation. Source availability does not validate throughput or production-readiness claims by itself.Teranode Teratestnet runnerPublic instructions and tooling for running the test network; inspect hardware and workload before comparing results.
04
Things to try
Use a real path and record versions, permissions, expected output, cost, and failures.
Project Babbage quickstartsRunnable wallet-mediated application paths. Maintainer documentation is useful for reproduction, not independent adoption proof.Metanet Academy Builder LabUngated architecture, diagnostics, and working-flow walkthroughs for builders.Use BSV ToolsBuilder-facing tool entry point; verify each linked dependency and live path independently.
05
Current-state surfaces
Useful for discovery and live inspection; recheck every unstable fact at decision time.