Compare Bitcoin node implementations
Compare the latest published Bitcoin Roots and Bitcoin Core releases, with Roots-only operator features first. Bitcoin Knots remains a separately versioned comparison column.
Versions reviewed
Latest published releases checked on 6 November 2026:
- Bitcoin Roots: v32.1-roots.1
- Bitcoin Core: v32.1
- Bitcoin Knots: v29.4.3.knots20260508
Bitcoin Roots v32.1-roots.1 starts directly from Bitcoin Core v32.1. Selected policy, wallet and operator features have historical Knots lineage; Knots is not the direct Roots base or a dependency. Each table column describes the release named in its heading, rather than mixing historical and current versions.
Comparison
Scroll horizontally to compare all three projects.
| Feature | Bitcoin Roots v32.1-roots.1 | Bitcoin Knots v29.4.3.knots20260508 | Bitcoin Core v32.1 |
|---|---|---|---|
| Roots-only features | |||
| Advanced privacy-aware coin control | Included: wallet-reported effective value, reuse, grouping, locks and spendability; stale selections are cleared | Standard coin-control dialog; no Roots advanced wallet-facts view | Standard coin-control dialog; no Roots advanced wallet-facts view |
| Address-specific spending-key export (exportaddresskey RPC) | Included for the selected local-key wallet, including supported multisig, Miniscript, Taproot and MuSig2 keys | No exportaddresskey RPC | No exportaddresskey RPC |
| Explicit startup gate for key-disclosure RPCs (--allow-dangerous-rpc) | exportaddresskey, listdescriptors, gethdkeys and derivehdkey are disabled by default; only an explicit command-line opt-in enables them | No equivalent startup gate; normal wallet authorization still applies | No equivalent startup gate; normal wallet authorization still applies |
| Effective local-policy reporting (getmempoolinfo.policy) | Included: initialized admission settings, units and enforcement gates, alongside native v32 mempool fields | Mempool information RPC; no Roots policy object | Native v32 mempool information; no Roots policy object |
| Transaction and mining policy | |||
| Embedded-data relay controls (-datacarrier, -datacarriersize) | Included; defaults to an 83-byte aggregate budget, recognized input/witness counting and one OP_RETURN output | Included | Included |
| Configurable embedded-data cost (-datacarriercost) | Included from the Knots lineage | Included | Not included in v32.1 |
| Extended replacement policy modes (-mempoolreplacement) | Included from the Knots lineage | Included | Native full-RBF policy; no -mempoolreplacement mode selector |
| Coin-age and maturity relay filters (-minrelaycoinblocks, -minrelaymaturity) | Included from the Knots lineage | Included | Not included in v32.1 |
| Sub-dust effective-fee penalty (-subdustfeepenalty) | Included from the Knots lineage | Included | Not included in v32.1 |
| Bare multisig policy toggle (-permitbaremultisig) | Included | Included | Included |
| Mining weight and minimum-fee controls (-blockmaxweight, -blockmintxfee) | Included | Included | Included |
| Coin-age priority mining reserve (-blockprioritysize) | Included from the Knots lineage | Included | Not included in v32.1 |
| Project and consensus | |||
| Role and lineage | Bitcoin Core v32.1 plus a reviewable Roots patch carrying selected Knots-lineage behavior | A separate Core-derived implementation on its own 29.x release line | The current upstream reference implementation and the direct v32.1 Roots base |
| Bitcoin Core-compatible consensus | Yes. Required for every Roots release. | No. The reviewed v29.4.3 release carries additional consensus rules | Yes. Reference behavior. |
| RDTS / BIP-110 enforcement | Excluded | Included in the reviewed v29.4.3 release | Not included |
| Project-specific consensus changes | Excluded | Includes BLAKE2b proof-of-work, RDTS and extended coinbase maturity; see the release notes | Not included |
| Network resources and operator tools | |||
| Compact-block extra-transaction count bound (-blockreconstructionextratxn) | Included | Included | Included |
| Compact-block reconstruction memory bound (-blockreconstructionextratxnsize) | Included: 10 decimal MB of charged transaction storage by default, alongside the count bound | Included | Not included in v32.1 |
| Orphan-transaction resource limits | Native v32 orphanage bounds; no -maxorphantx count option | Configurable transaction-count cap (-maxorphantx) | Native v32 orphanage bounds; no -maxorphantx count option |
| Upload target and peer permissions (-maxuploadtarget, -whitebind, -whitelist) | Included | Included | Included |
| Collected mempool samples (getmempoolstats RPC) | Not available in v32.1-roots.1 | Included | No getmempoolstats RPC |
| Monotonic process-uptime reporting | Included through the native Core v32.1 base | Included | Included natively in v32.1 |
| RAM, cache and index defaults | Native Core v32.1 defaults are preserved | Knots 29.x defaults and resource controls | Native v32.1 resource defaults |
| GUI peer-health view | Bounded live peer table and current-connection details, with stale state cleared | Included, with additional Knots monitoring surfaces | Standard peer table and details |
| Wallet and desktop | |||
| Descriptor wallet and basic GUI coin control | Included through the Core base | Included | Included |
| Per-send Replace-By-Fee choice | Included; follows the wallet default and confirms the transaction's effective signaling | Included in the send dialog | No per-send RBF checkbox in the v32.1 Qt send dialog |
| Wallet storage | Descriptor wallets using SQLite | Descriptor wallets; legacy-wallet support depends on the build | Descriptor wallets using SQLite |
| Private-key sweeping | Included as sweepprivkeys RPC and a Qt dialog, with a non-broadcast preview and explicit final broadcast | Included as sweepprivkeys RPC and a GUI dialog | Not included in v32.1 |
| QR receive-request image export | Included | Included | Included |
| Windows taskbar synchronization progress | Included when the Windows GUI build enables taskbar progress | Included | Not included in v32.1 |
| Selected build and dependency portability | Qt 6.2 or newer; native v32 HTTP, IPC and external-signer interfaces | Qt 5.11.3 or Qt 6.2 or newer, selected at build time | Qt 6.2 or newer; native HTTP, IPC and external-signer interfaces |
“Roots-only” means the described interface or workflow is present in the reviewed Roots release and absent from both other reviewed releases. Additional controls shared with Knots follow, then the consensus, resource and wallet comparisons. Shared names do not imply identical defaults or behavior; consult each version's built-in help for accepted settings. The Roots feature catalogue and effective-policy contract describe the current Roots boundaries.
Wallet scope
Private-key sweeping and advanced privacy-aware coin control are shipped in v32.1-roots.1. Sweeping uses a transient WIF key, scans supported confirmed P2PKH/P2WPKH outputs, and defaults to a non-broadcast preview. It does not scan Taproot outputs. Advanced coin control exposes wallet facts and clears stale selections; these manual tools do not add CoinJoin, payjoin or an anonymity score.
Address-specific key export is a separate workflow. exportaddresskey, listdescriptors, gethdkeys and derivehdkey require the explicit startup command-line option --allow-dangerous-rpc; normal wallet authorization and unlock requirements still apply. Read the current wallet manual for supported scripts, permissions and key-disclosure consequences.
Current-version differences
Core v32.1 already provides monotonic uptime and the native v32 wallet, mempool, resource and build foundations inherited by Roots. These are shared features. Conversely, getmempoolstats is not available in Roots v32.1-roots.1, and the old -maxorphantx count option is absent from both v32.1 columns. The table keeps these differences explicit instead of carrying forward v29 claims.
Sources
The comparison uses these primary release and source references:
- Roots: v32.1-roots.1 release, released source, feature catalogue, effective-policy schema and wallet manual.
- Core: official downloads, v32.1 release, released source, policy options, Qt send dialog and GUI dependency requirements.
- Knots: official downloads, v29.4.3 release notes, released source, policy options, coin-control view and Qt version selection.
Which project may fit?
Bitcoin Core
The appropriate baseline for operators who want the reference implementation, its standard policy defaults, and the smallest number of project-specific differences.
Bitcoin Roots
Intended for operators who want Bitcoin Core-compatible consensus together with the advanced wallet tools, explicit key-disclosure permissions and effective-policy reporting shown above, alongside selected conservative Knots-lineage policy and operator controls.
Bitcoin Knots
An alternative implementation with additional policy and configuration choices. The reviewed v29.4.3.knots20260508 release includes BLAKE2b proof-of-work, RDTS and extended coinbase-maturity rules, and does not follow Bitcoin Core v32.1 consensus. Review its linked release notes before choosing the network rules to run.
Frequently asked questions
Is Bitcoin Roots a new cryptocurrency?
No. Bitcoin Roots is full-node software intended to follow the Bitcoin network and Bitcoin Core-compatible consensus. It does not introduce a new token.
Is Bitcoin Roots a network fork?
Bitcoin Roots is a source-code fork built directly on Bitcoin Core, with selected behavior retained from the Bitcoin Knots lineage. Its stated purpose is not to create a competing Bitcoin chain.
Does stricter policy change Bitcoin consensus?
No. Mempool and transaction relay policy govern unconfirmed transactions handled by the local node. They do not determine whether a block is valid.
Can a transaction rejected by Bitcoin Roots appear in a valid block?
Yes. A miner may include a consensus-valid transaction that Bitcoin Roots did not accept into its local mempool. Bitcoin Roots must accept the block if the block satisfies Bitcoin consensus rules.
Why preserve features from Bitcoin Knots?
Bitcoin Knots developed useful controls for transaction relay policy, resource use, privacy, and node operation. Bitcoin Roots preserves selected features where they remain compatible with its consensus commitment.
Why does Bitcoin Roots reject RDTS/BIP-110?
Bitcoin Roots does not consider subjective transaction policy a sufficient basis for changing Bitcoin consensus rules. It keeps conservative filtering at the node-policy layer while following Bitcoin Core-compatible block validity.
Does Bitcoin Roots guarantee “no spam”?
No. “Spam” is not an objective consensus category. Bitcoin Roots can apply conservative local relay and mempool policy, but it must still accept consensus-valid blocks.