Capability is not adoption

Proof and adoption-status inventory.

Each record names something you can inspect, what it demonstrates, and what it cannot establish on its own. “Live” and “open source” do not automatically mean safe, widely used, independent, or commercially successful.

Field note · proof and preservationA Merkle Proof Is a Receipt, Not a Backup

What Bitcoin proves about transaction inclusion, order, and integrity—and what builders must still preserve, index, explain, and make portable.

Read the full argument →

Workflow evidence: the state of the record

Source availability was checked October 5, 2026. No new wallet connection, transaction, compatibility or recovery test was performed. The records make that boundary explicit.

Documented paths and reported outcomes
WorkflowState and observed resultVersions, permissions and costNext evidence
Wallet-mediated quickstart

Checked 2026-10-05

Documented path · not independently tested

Public endpoint returned HTTP 200. No wallet workflow was run.

Expected: A wallet-mediated operation with an inspectable result.

Not recorded for a completed run

Use the current quickstart’s supported environment, wallet and funding requirements; not verified here.

Inspect the actual wallet request before approval; no request was submitted in this review.

Cost: Not measured

Record exact versions, prerequisites, prompts, cost, result and failures in a clean environment.
Metanet Academy Builder Lab

Checked 2026-10-05

Published learning path · not independently completed

Public endpoint returned HTTP 200. Completion time and success were not measured.

Expected: One explained architecture or diagnostic outcome.

Current page; no software run pinned

Read the path before installing or connecting anything; clean-run prerequisites unverified.

No wallet permissions or spending authorized by this evidence record.

Cost: Not measured

Have an unfamiliar builder record the first completed task, terms, blockers and elapsed time.
Zanaadu mobile posting

Checked 2026-10-05

User report and maintainer acknowledgment · repair unverified

User reported failure October 4; maintainer acknowledged an overly restrictive change. No successful current retest recorded.

Expected: Supported posting workflow completes.

Exact app and wallet versions not established in this record

The reporter’s existing mobile workflow; no new reproduction performed.

Unexpected signing restriction reported; no security bypass is proposed.

Cost: Not measured

Identify the repair release and retest the original task. Record any remaining failure.

Use the versioned compatibility matrix and case study →

legal record

Public source availability rechecked 2026-10-05 · Documentation or inspection surface; no new independent workflow test. Original assessment scope retained below.

COPA v Wright official record ↗

What it proves

  • The court's published findings and stated reasons are directly inspectable.

What it does not prove

  • Whether an unrelated protocol or application claim works.

Independent inspection path

  1. Read the official summary and approved judgment.
  2. Match every quoted legal claim to the record and scope.
governance record

Public source availability rechecked 2026-10-05 · Documentation or inspection surface; no new independent workflow test. Original assessment scope retained below.

Network Access Rules and enforcement surface ↗

What it proves

  • The Association publishes an explicit node-governance agreement.
  • Part III describes possible freeze, reassignment, peer, and block directives.

What it does not prove

  • That every directive is fair, enforceable, public, or correctly executed.
  • That courts or key holders cannot err.

Independent inspection path

  1. Read all five parts and current effective dates.
  2. Compare current node and alert behavior with the text.
  3. Request a complete directive history.
standard

Public source availability rechecked 2026-10-05 · Documentation or inspection surface; no new independent workflow test. Original assessment scope retained below.

Public BRC specification corpus ↗

What it proves

  • Wallet, identity, payment, proof, and overlay interfaces are publicly versioned and inspectable.

What it does not prove

  • Independent implementation, conformance, production security, or adoption.

Independent inspection path

  1. Read the exact BRC and its version history.
  2. Find implementation and test coverage.
  3. Check independent compatibility.
code

Public source availability rechecked 2026-10-05 · Documentation or inspection surface; no new independent workflow test. Original assessment scope retained below.

Current BSV TypeScript implementation stack ↗

What it proves

  • SDK, wallet, overlay, messaging, middleware, helper, and infrastructure source is inspectable in a current monorepo.
  • The repository publishes build, test, and conformance entry points.

What it does not prove

  • Production security of every deployment.
  • Users, retention, commercial demand, or cross-language parity.

Independent inspection path

  1. Pin a commit.
  2. Install, build, test, and run conformance.
  3. Inspect each package license and release status.
code

Public source availability rechecked 2026-10-05 · Documentation or inspection surface; no new independent workflow test. Original assessment scope retained below.

Language-neutral conformance vectors ↗

What it proves

  • A shared vector format, coverage record, runners, and parity material exist.

What it does not prove

  • Complete coverage of BRC-100.
  • Multiple independent wallets pass every vector.

Independent inspection path

  1. Read COVERAGE.md and PARITY_MATRIX.json.
  2. Run the structural and TypeScript dispatchers.
  3. Publish missing and failing vectors.
code

Public source availability rechecked 2026-10-05 · Documentation or inspection surface; no new independent workflow test. Original assessment scope retained below.

Teranode source and public testnet runner ↗

What it proves

  • Teranode is publicly inspectable software rather than only a future architecture claim.
  • A public Teratestnet runner exists.

What it does not prove

  • Any headline throughput under independent conditions.
  • Sustained mainnet demand, production safety, cost, or operator diversity.

Independent inspection path

  1. Pin source and runner revisions.
  2. Publish hardware, topology, workload, duration, latency, errors, and cost.
  3. Reproduce outside the maintainer environment.
live flow

Public source availability rechecked 2026-10-05 · Documentation or inspection surface; no new independent workflow test. Original assessment scope retained below.

Wallet-mediated application quickstart ↗

What it proves

  • A documented path exists for a builder to exercise wallet-mediated operations.

What it does not prove

  • Independent reproduction, production readiness, retained users, or wallet neutrality.

Independent inspection path

  1. Start from a clean environment.
  2. Record prerequisites, permissions, version, cost, result, and failure.
  3. Inspect the resulting source and transaction or proof.
live flow

Public source availability rechecked 2026-10-05 · Documentation or inspection surface; no new independent workflow test. Original assessment scope retained below.

Metanet Academy Builder Lab ↗

What it proves

  • An ungated architecture and diagnostic learning path is live.

What it does not prove

  • That unaffiliated builders complete it successfully or adopt the stack.

Independent inspection path

  1. Complete the path without maintainer help.
  2. Record unclear terms, broken steps, and time to outcome.
network data

Public source availability rechecked 2026-10-05 · Documentation or inspection surface; no new independent workflow test. Original assessment scope retained below.

Live block and transaction inspection ↗

What it proves

  • Current blocks and transactions can be inspected through a third-party explorer.

What it does not prove

  • Human user counts, economic necessity, producer independence, or explorer correctness.

Independent inspection path

  1. Cross-check material data with another source or node.
  2. Separate transaction counts from users and outcomes.
live flow

Public source availability rechecked 2026-10-05 · Documentation or inspection surface; no new independent workflow test. Original assessment scope retained below.

Official BSV demo catalog ↗

What it proves

  • The Association publishes a discovery catalog linking demos and repositories.

What it does not prove

  • Independent status, complete working flows, users, retention, or sustainable businesses.

Independent inspection path

  1. Open every live URL.
  2. Inspect the repository and last meaningful activity.
  3. Complete the user flow.
  4. Record a dated independent status.