The node

FAQ

Running a node, staying on the Bitcoin chain, and how the software is checked. Commons-level FAQ.

Will I stay in consensus with the Bitcoin network?

This node is written to Bitcoin’s consensus rules and binds consensus-critical functions to the Orange Paper. A passing Z3 check means the spec-lock prover and Z3 accepted that function’s contract. Compatibility is checked in layers — property tests, libFuzzer, golden vectors, and a differential against Core / libbitcoinkernel. No signed log covers the chain from genesis to the tip.

How does this help decentralize Bitcoin?

Bitcoin’s network currently relies on one dominant implementation. A serious second full node with independent consensus coverage makes the network more resilient. BLVM provides the shared formal spec that makes safe alternatives practical without each team reverse-engineering consensus rules from C++.

What if there is a bug in my node?

Treat it like any other full node: review the software before you put real funds on it. Spec-lock runs in CI; the test suite includes property tests, fuzzing, golden vectors, and a Core differential. Report security issues to security@thebitcoincommons.org. Coordinated releases for consensus bugs still go through the published governance process.

Is this a fork of Bitcoin?

No. BTCDecoded does not fork Bitcoin’s blockchain, change its consensus rules, or introduce a new coin. The Orange Paper is the written specification. The goal is a second full node on the existing Bitcoin network.

Do I need technical knowledge to run a node?

Not necessarily. Current packages are on the Install page (GitHub Releases, with checksums). Marketplace installs for Start9, Umbrel, myNode, and Parmanode are coming. Building from source is documented separately for developers.

How does governance work?

Bitcoin Commons governance is published and tiered. Who can merge, which signature thresholds apply, and how long review windows last are in a public repository. Phase 1 is current. Enforcement is off and the keys are test keys. If you disagree with a rule you fork that repository, not the chain.

How can I fund the project?

Through Plebly (plebly.fund): on-chain escrow, not a custodial tip jar. Fund a listed Commons proposal, or donate to Commons directly.

Where do I get support?

The Support form for Intelligence billing, keys, and checkout, and for node questions that are not a security report. Security issues go to security@thebitcoincommons.org. Node docs: docs.btcdecoded.org/blvm.