Skip to content

Your node. Your policy. Bitcoin consensus.

Bitcoin Roots is a Bitcoin Core-based full node that preserves selected conservative policy and operator controls from Bitcoin Knots.

It follows Bitcoin Core-compatible consensus and does not enforce RDTS/BIP-110.

THE PLAN ₿ FOUNDATION PRESENTS

Connected to the trunk. Conservative in policy. Neutral in consensus.

Independently verify Bitcoin

Your node receives the network’s data, checks it independently, and applies your choices before confirmation.

  1. 01

    Connect

    Join Bitcoin’s peer-to-peer network and receive blocks and transactions directly from other nodes.

  2. 02

    Verify

    Independently validate every block according to Bitcoin consensus rules.

  3. 03

    Configure

    Choose the relay, mempool, privacy, and resource policies applied by your node.

  4. 04

    Stay compatible

    Follow the Bitcoin chain while keeping local policy under your control.

From Knots, without leaving Bitcoin

Bitcoin Roots preserves selected policy features and operator controls from Bitcoin Knots while remaining compatible with Bitcoin Core consensus.

The repository records 29.3.knots20260507 as its Knots lineage reference, not as an exact Git parent. Bitcoin Roots does not adopt RDTS/BIP-110 consensus rules.

Bitcoin Roots is a source-code fork. It is not a separate cryptocurrency, proof-of-work network, or competing Bitcoin chain.

Read our principles

Know exactly where policy ends

Bitcoin Roots separates the shared rules that keep Bitcoin nodes in agreement from the local choices each operator makes about unconfirmed transactions.

Shared boundary

Consensus is shared

Bitcoin Roots applies Bitcoin Core-compatible block-validity rules and follows the Bitcoin chain.

A transaction rejected by local mempool or relay policy may still be valid under Bitcoin consensus. If a valid block contains that transaction, Bitcoin Roots accepts the block.

Operator boundary

Policy is local

Your node decides which unconfirmed transactions it accepts into its mempool and relays to peers.

Bitcoin Roots provides conservative, configurable policy options without turning those preferences into new consensus rules.

Read the transaction relay policy

Why Bitcoin Roots?

Bitcoin Core is the reference implementation and the upstream development trunk.

Bitcoin Roots builds on that foundation while preserving selected controls for operators who want stricter transaction relay, explicit resource limits, and greater visibility into node behaviour.

Suitable Bitcoin Core developments are reviewed and incorporated into Bitcoin Roots releases. Project-specific differences should remain limited, documented, and testable.

Compare Bitcoin Roots

Bitcoin Roots is intended for operators who want:

  • Bitcoin Core-compatible consensus
  • Conservative, configurable mempool policy
  • Explicit resource and network controls
  • Independent validation
  • Transparent differences from upstream
  • No RDTS/BIP-110 consensus enforcement

From source to a running node

Follow the platform guide, choose resource limits deliberately, and keep the complete reference available when you need it.

Choose your platform
  1. 1. Build
    Choose your system

    Follow the repository instructions for Linux, macOS, Windows, or BSD.

  2. 2. Configure
    Set deliberate limits

    Review the available memory, storage, network, privacy, relay, and mempool settings before changing the defaults.

  3. 3. Verify
    Run your node

    Connect to the Bitcoin network, independently validate the chain, and apply your chosen policy to unconfirmed transactions.

Documentation stays with the source

The website renders the Markdown documentation maintained in the repository. The code, documentation, and review history can therefore evolve together.

Browse all documentation

Open development for security-critical software

Bitcoin Roots is developed in public. Changes can be inspected, tested, and discussed through the project repository.

Consensus compatibility is a release requirement. Differences in relay, mempool, privacy, and resource policy should be explicit and documented.

Testing and code review are essential. Contributions from node operators, reviewers, developers, and documentation writers are welcome.

Run the node. Read the diff. Keep the choice yours.

Bitcoin Roots gives node operators conservative policy controls without asking them to leave Bitcoin consensus.

Bitcoin Roots is released under the MIT License.