The project
Problem
Bitcoin’s chain rules are hard to change. How the dominant client is governed is mostly informal: a small group of maintainers, little cryptographic accountability, and a high social cost if you disagree.
Hard rules on the chain, soft process above it — that gap is what this project is for.
Alternative implementations face two hard requirements. First, correctness: without a shared mathematical specification tied to code, consensus divergence is a matter of when, not if. Second, coordination: without governance you can fork and audit, informal power recentralizes around whichever client wins the narrative.
BTCDecoded targets both: an Orange Paper-grade specification with a formally verified consensus path (Z3-backed spec-lock on blvm-consensus), plus the Bitcoin Commons model: published tiers, multisig thresholds, and enforcement tooling (blvm-commons) that users and operators can review or fork. Same Bitcoin rules; clearer rules for how the software that enforces them evolves.
The commons
Built on Bitcoin Commons
Forkable governance applying Ostrom’s commons principles through cryptographic enforcement.