The stack

Architecture

Write Bitcoin’s rules, implement them, run a node, and publish who can change the software. Orange Paper → blvm-consensus (spec-lock) → blvm-protocol → blvm-node → blvm → blvm-sdk → governance. Architecture docs.

1

blvm-spec

Mathematical Specification

Complete mathematical specification of Bitcoin consensus extracted from Bitcoin Core. Includes the 21 million supply convergence proof (Theorem 6.2.3). Orange Paper viewer on this site →

2

blvm-consensus

Formally Verified Implementation

Rust implementation of the Orange Paper functions. blvm-spec-lock binds those functions to numbered spec sections and checks them with Z3 in CI. If the code drifts from the spec, the build fails.

Spec-lock: chain selection, block subsidy (21M proof), proof-of-work, and transaction validation carry contracts discharged by Z3. This is the consensus path the node must call — it is not a claim that every runtime path is a finished theorem.

3

blvm-protocol

Protocol Abstraction

Bitcoin variant abstraction (mainnet, testnet, regtest) built on blvm-consensus. All consensus calls go through the formally verified layer.

4

blvm-node

Full Node Library

Complete Bitcoin node library using blvm-protocol and blvm-consensus. Adds storage, networking, and RPC. Optional features: Iroh QUIC transport (NAT traversal), Quinn QUIC transport, UTXO commitments (faster initial sync).

5

blvm

Binary Wrapper

Standalone binary executable that wraps blvm-node. Provides command-line interface for running a full Bitcoin node. Depends on blvm-node library.

6

blvm-sdk

Developer Toolkit

Developer toolkit for building alternative Bitcoin implementations. Provides module composition framework for declaratively assembling custom Bitcoin nodes, plus governance cryptographic primitives.

7

governance

Governance Configuration

Central source of truth for governance rules, layer hierarchy, and emergency tier system. Defines who can merge what, and when.

8

blvm-commons

Cryptographic Enforcement

GitHub App enforcing governance rules through signature verification and review periods. Uses blvm-sdk for cryptographic operations. Phase 1: Infrastructure complete, enforcement not yet activated.

All consensus decisions flow through the formally verified blvm-consensus layer.

Orange Paper → blvm-consensus (spec-lock + tests) → protocol, node, SDK, governance.