Skip to main content

Frequently Asked Questions

General​

What is Bitcoin Knots?​

Bitcoin Knots is an enhanced derivative of Bitcoin Core, maintained by Luke Dashjr since 2011. It includes additional features, policy options, and improvements not available in Bitcoin Core while maintaining identical consensus rules (with one v29.3 exception on a scheduled activation — see the BIP-110/RDTS section below).

Is Bitcoin Knots safe to use?​

Yes. By default, Bitcoin Knots follows identical consensus rules to Bitcoin Core, ensuring full network compatibility. The differences are in local policy (what your node relays) and features (GUI, wallet, RPC). Your node currently validates the blockchain exactly the same as Core; the one caveat is the RDTS softfork shipped in v29.3, which the standard build will enforce when it activates (~September 2026) — see the BIP-110/RDTS section.

Who maintains Bitcoin Knots?​

Luke Dashjr (luke-jr), one of the earliest Bitcoin developers (involved since 2010), maintains Bitcoin Knots. He's also a Bitcoin Core contributor, author of BIP 22/23 (mining protocols), and co-founder of the Ocean mining pool.

Why is it called "Knots"?​

The name has a dual meaning:

  • Technical: References the merging/tying together of code branches and patches
  • Personal: A reference to a biblical passage significant to Dashjr's faith

The project was originally called "Bitcoin LJR" before being renamed.

As of July 2026, Bitcoin Knots runs on roughly 23% of reachable Bitcoin nodes (bitdis.org measured 22.97% of 23,874 reachable nodes on July 2, 2026; Coin Dance showed 22.7%). The share peaked at about 25% in September 2025. Adoption surged in 2024-2025, largely driven by the OP_RETURN controversy and Core v30's removal of data limits. For current figures, check the live dashboards linked in External Resources.

Knots vs Core​

What about the "40,000 lines of unreviewed code" claim?​

The ~40,000 lines figure is roughly accurate when counting insertions (~36k). The more important question is what do those lines do? Here's the breakdown (v29.2 vs Core v29.0):

CategoryInsertionsDeletionsNetRisk Level
GUI (Qt)11,44211,450~0Zero - can't affect consensus
Tests9,113821+8,292Zero - improves safety
Docs/Build~5,000~2,000~3,000Zero
Wallet1,532239+1,293Low - your keys only
RPC2,238277+1,961Low - API commands
Policy77072+698Low - relay, not consensus
Validation/Script1,256306+950Review below
Total36,43815,294~21,144

Key facts:

  • ~70% is GUI, tests, and docs (zero consensus risk)
  • ~25% is wallet, RPC, policy (affects your node only)
  • Only ~4% (~1,400 lines) is consensus-adjacent
  • 0% changes consensus rules — Knots validates identically to Core (this analysis covers v29.2; v29.3 later added the RDTS softfork — see below)

What's in the "consensus-adjacent" code?

  • bitcoinconsensus: Restored Core code removed in v28 — already reviewed
  • validation.cpp: Mostly policy options (configurable, can be disabled)
  • No changes to actual consensus rules

See Code Analysis for the full breakdown.

How is Knots different from Core?​

FeatureBitcoin CoreBitcoin Knots
Consensus RulesStandardIdentical (v29.3 adds RDTS on a scheduled activation)
Legacy WalletRemoved (v30)Maintained
OP_RETURN LimitRemoved (v30)Configurable
Inscription FilteringNoYes (default on)
Automatic Tor launchNoYes (starts Tor for you if installed)
Dark ModePartialFull support
UPnPRemovedRestored
Block Size OptionsRemovedRestored

Will Knots fork Bitcoin?​

Not by default. Out of the box, Knots follows the same consensus rules as Bitcoin Core. The differences are purely in:

  • What transactions your node relays (policy)
  • What features are available (GUI, RPC, wallet)
  • What defaults are used

Today, your Knots node validates blocks identically to Core. Since v29.3.knots20260508 there is one scheduled exception: the standard build includes the BIP-110/RDTS softfork and will enforce it when it activates (~September 2026). The build asks for your explicit confirmation, and a separate build without RDTS (29.3.knots20260507) is offered for users who don't want enforcement. If RDTS activates without broad hashrate support, enforcing nodes could diverge from non-enforcing nodes — see the BIP-110/RDTS section below.

Can I run Knots and Core on the same network?​

Yes, they're fully compatible. Knots nodes communicate seamlessly with Core nodes. With default settings, the network doesn't distinguish between them at the consensus level.

Does filtering affect the Bitcoin network?​

No. Policy is local to your node. When you filter transactions:

  • They can still propagate through other nodes
  • They can still be mined by any miner
  • Your node will still accept blocks containing them

You're choosing what your node relays, not what the network allows.

BIP-110 / RDTS​

What is BIP-110 (RDTS)?​

The Reduced Data Temporary Softfork (RDTS) is a proposed temporary softfork that restricts data-carrying transactions at the consensus level. It is an official BIP, BIP-110, and Knots implements it as a modified BIP9 temporary deployment that automatically expires after roughly one year of enforcement (~52,416 blocks).

Does Knots enforce RDTS?​

Depends on which build you run. The standard v29.3.knots20260508 build enforces the RDTS deployment on its schedule — that is a property of the build, not of your configuration. What the software asks for is explicit confirmation: the GUI shows a prompt at startup (and exits if you decline), while bitcoind runs and enforces but logs a warning every hour until you add consensusrules=rdts to bitcoin.conf. If you don't want RDTS enforcement at all, run the parallel build without RDTS support (29.3.knots20260507). Full details: BIP-110 / RDTS Integration.

How would RDTS activate?​

Via miner signaling on version bit 4: activation requires 55% of blocks (1,109 of 2,016) within a difficulty period to signal support. The Knots deployment parameters also include a maximum activation height (block 965,664, roughly September 2026 per the implementation), after which the softfork activates regardless of signaling.

As of late June 2026, signaling remains minimal — around 0.31% of hashrate, mostly from the Ocean pool.

Is RDTS controversial?​

Yes. Critics — including Adam Back and Jameson Lopp — have warned that activating a softfork with minority hashrate support risks a chain split: nodes enforcing RDTS could end up following a different chain than the rest of the network. Supporters argue the upgrade fixes long-standing data-abuse vectors. If you run an RDTS-enforcing build, understand that after activation it may enforce rules the majority of the network does not.

Installation & Upgrades​

Can I use my existing Bitcoin Core data?​

Yes. Bitcoin Knots uses the same data directory format. Simply:

  1. Stop Bitcoin Core
  2. Install Bitcoin Knots
  3. Start Knots (it uses the same data automatically)

No migration needed.

How do I upgrade from Core to Knots?​

# 1. Stop Core
bitcoin-cli stop

# 2. Install Knots (download from bitcoinknots.org)

# 3. Start Knots
bitcoind  # or bitcoin-qt

Your blockchain, wallets, and settings are preserved.

Can I switch back to Core?​

Yes, with one caveat:

  • Blockchain data: Fully compatible
  • Descriptor wallets: Fully compatible
  • Legacy wallets: Core v30+ removed support

If you have legacy wallets, either:

  • Keep using Knots
  • Migrate wallets first: bitcoin-cli migratewallet
  • Export keys: bitcoin-cli dumpwallet

Do I need to re-sync the blockchain?​

No. Knots uses the same data format as Core. Your existing blockchain is fully compatible.

Where do I download Bitcoin Knots?​

Official source: bitcoinknots.org

Always verify signatures when downloading.

Policy & Filtering​

What does rejectparasites do?​

It filters CAT21 spam transactions from your mempool. This:

  • Reduces your mempool churn
  • Saves bandwidth
  • Doesn't affect what blocks you accept

Note: rejectparasites specifically targets CAT21 spam, not inscriptions or ordinals in general. Transactions can still be mined by others and your node accepts all valid blocks.

What's a good datacarriersize setting?​

SettingEffect
0Disable all OP_RETURN relay
42Restrictive (hash commitments only)
83Knots default (legacy compatibility)
100000+Effectively unlimited (Core v30 behavior)

How do I disable all filtering?​

bitcoin.conf
corepolicy=1

Or explicitly:

bitcoin.conf
rejectparasites=0
rejecttokens=0
permitbaremultisig=1
datacarriersize=100000

Does filtering reduce my fee income (if mining)?​

Potentially yes, but:

  • Luke Dashjr notes "spam-filtered blocks often have more fees anyway"
  • Ocean pool runs filtered and reports competitive revenue
  • You're choosing policy, not sacrificing consensus

What are "parasites" and "tokens"?​

  • Parasites (rejectparasites): CAT21 spam transactions
  • Tokens (rejecttokens): transactions involving non-bitcoin tokens — this covers Runes protocol transactions (OP_RETURN with OP_13) as well as OLGA-pattern data storage in P2WSH outputs

Both are "data storage" uses of Bitcoin that some consider spam.

Wallet​

Are legacy wallets deprecated?​

  • Bitcoin Core: Yes, removed in v30
  • Bitcoin Knots: No, fully supported

This is a key reason many users switched to Knots.

Can I import Core wallets into Knots?​

Yes. Both descriptor and legacy wallets are compatible.

What is sweepprivkeys?​

A Knots RPC that finds all funds controlled by a private key and sends them to a fresh address in your loaded wallet, in one operation. Safer than importprivkey because:

  • The swept key isn't stored in your wallet
  • Funds move to an address your wallet controls
  • Original key exposure doesn't matter after the sweep

It takes a single options object (there is no destination argument — funds always go to a new address in the loaded wallet):

bitcoin-cli sweepprivkeys '{"privkeys": ["5KJvs..."], "label": "swept coins"}'

Since v29.3, sweepprivkeys also finds segwit (p2wpkh) and taproot (p2tr) UTXOs in addition to p2pk/p2pkh, and the GUI has a matching "Sweep private key" dialog in the File menu.

What is Codex32?​

Codex32 (BIP-93) is a seed backup scheme that:

  • Uses paper and pencil (no electronics needed)
  • Supports Shamir secret sharing
  • Has error correction (detects/fixes mistakes)
  • Can be verified entirely by hand

Knots supports importing Codex32 seeds.

Mining​

Can I use Knots for mining?​

Yes. Knots includes mining enhancements:

  • Restored -blockmaxsize option
  • Transaction priority support
  • Per-call getblocktemplate parameters
  • Used by Ocean mining pool in production

Does Knots affect my hashrate?​

No. Knots doesn't modify the mining algorithm or proof-of-work. It only affects block template construction.

What mining pool uses Knots?​

Ocean, co-founded by Luke Dashjr, runs Bitcoin Knots. It's backed by Jack Dorsey and reportedly processed $500M+ in mining.

Privacy & Networking​

How do I use Tor with Knots?​

Simple way (automatic): if Tor is installed on your system, Knots will automatically launch it as a subprocess when appropriate — no configuration needed. (Knots doesn't bundle Tor itself; the command used can be overridden with the hidden -torexecute=<command> option, default tor.)

Manual way (existing Tor daemon):

bitcoin.conf
proxy=127.0.0.1:9050
listenonion=1

See Tor Integration for full details.

Is UPnP safe?​

UPnP automatically opens ports on your router. Considerations:

  • Pro: Enables inbound connections, helps network
  • Con: Exposes your node to internet
  • Risk: Depends on your threat model

Use only if you understand the implications:

bitcoin.conf
upnp=1

What is v2 transport?​

Encrypted peer-to-peer connections (BIP 324). Even on clearnet, prevents ISPs from inspecting Bitcoin protocol traffic:

bitcoin.conf
v2transport=1

GUI​

Does Knots have dark mode?​

Yes. Knots includes proper dark mode support via the qt_darkmode patch. It:

  • Follows system theme automatically
  • Works on Windows, macOS, Linux
  • Covers all dialogs and windows

See Dark Mode.

What GUI improvements does Knots have?​

  • Dark mode: Full support
  • Network monitor: Enhanced traffic graphs
  • Mempool stats: Visual mempool widget (restored from old Core)
  • Tor settings: GUI configuration for Tor
  • Policy options: GUI access to filtering settings

Troubleshooting​

My node won't sync​

See Troubleshooting Guide. Common causes:

  • No peer connections (firewall issue)
  • Insufficient disk space
  • Corrupted data (try -reindex)
  • Stale peer connections (try clearbanned)

RPC connection refused​

Ensure server=1 is in your config:

bitcoin.conf
server=1

Where are the logs?​

OSLocation
Linux~/.bitcoin/debug.log
macOS~/Library/Application Support/Bitcoin/debug.log
Windows%APPDATA%\Bitcoin\debug.log

How do I report bugs?​

Open an issue at github.com/bitcoinknots/bitcoin/issues

Include:

  • Knots version (bitcoin-cli --version)
  • OS and version
  • Relevant log entries
  • Steps to reproduce

Philosophy​

Why does Knots filter by default?​

Luke Dashjr's view is that Bitcoin is designed for monetary transactions, not data storage. Filtering:

  • Preserves block space for payments
  • Reduces UTXO bloat (especially from Stamps)
  • Is a choice — users can disable it

Is filtering "censorship"?​

No. Filtering is:

  • Local policy: Only affects your node's relay
  • Not consensus: Filtered transactions can still be mined
  • Optional: You can disable all filtering with corepolicy=1
  • Your choice: You decide what your node does

What's the OP_RETURN controversy?​

In 2025, Bitcoin Core v30 removed the 80-byte limit on OP_RETURN data. Critics (including Nick Szabo, who broke 5 years of silence) warned this:

  • Increases attack surface for data storage abuse
  • Changes Bitcoin's character from money to data layer
  • Was done without broad community consensus

Knots maintains configurable limits. See OP_RETURN Controversy.

See Also​