LearnBitcoin

Glossary

Bitcoin Knots

Node software built from Bitcoin Core's code with extra relay filters. Releases before May 9, 2026 follow Bitcoin's main chain; later releases follow a chain that split off in August 2026.

Bitcoin Knots is node software built from Bitcoin Core's code. Its lead maintainer is Luke Dashjr. Work done in Bitcoin Core is merged into Knots for each release, and Knots adds changes of its own on top.

Relay filters

Many of those changes are about relay policy: which unconfirmed transactions a node keeps in its mempool and passes on to peers. Knots adds settings for this, and its defaults filter out many transactions that carry arbitrary data. For example, by default it does not relay a transaction that carries data inside an inscription envelope, and it limits OP_RETURN outputs to 83 bytes.

Relay filters do not decide which blocks a node accepts. That is up to consensus rules, covered next.

Consensus: before and after May 2026

Knots releases up to and including 29.3.knots20260507 (May 8, 2026) do not include BIP-110. Nodes running them follow the same chain as Bitcoin Core nodes.

The next release, 29.3.knots20260508, came out on May 9, 2026 and applies BIP-110, the Reduced Data Temporary Softfork, once the user confirms. BIP-110 proposed a one-year soft fork that would cap most data pushes at 256 bytes and make invalid any Tapscript that executes OP_IF. Every Knots release since then includes it.

Under BIP-110, blocks starting at height 961,632 had to signal support for it. Block 961,632, mined on August 8, 2026, did not. Nodes running these Knots releases rejected it and every block built on it, which meant rejecting Bitcoin's main chain, and they split off onto a chain of their own that stalled. BIP-110 was marked Closed that month.

Knots 29.4.1, released September 2, 2026, is a hard fork for that split-off chain. Its release notes date the split to August 8. It replaces Bitcoin's proof of work with a different algorithm, BLAKE2b, and turns on BIP-110's data limits at the switch. Older software cannot follow the new blocks. The page those release notes link to gives block 961,640, on August 30, 2026, as the first BLAKE2b block. The latest Knots release as of October 2026, 29.4.2, follows the same BLAKE2b chain.

In bitnodes.io's snapshot of October 9, 2026, the split shows up in the block heights nodes report. Nodes on Knots releases up to May 8, 2026 almost all report the main chain's height. Those on 29.3.knots20260508 or 29.4 are nearly all stuck at 961,639, where the split-off chain stalled before the switch. Nodes on 29.4.1 or 29.4.2 report heights on the BLAKE2b chain.

For the debate over data in Bitcoin transactions that led to BIP-110, see Inscriptions.

Key takeaways

  • Built from Bitcoin Core's code, with its own relay settings and defaults that filter out many data-carrying transactions
  • Releases up to May 8, 2026 do not include BIP-110 and follow the same chain as Bitcoin Core
  • Releases from May 9, 2026 on enforce BIP-110; nodes running them left Bitcoin's main chain on August 8, 2026, and Knots 29.4.1 (September 2, 2026) is a hard fork that gives that chain a BLAKE2b proof of work

Corrected

  • Was: The entry said Bitcoin Knots is consensus-compatible with Bitcoin Core, so a Knots node sees the same chain and accepts the same blocks, and that the two differ only in relay policy.

    Now: Knots releases up to 29.3.knots20260507 (May 8, 2026, UTC) follow the same chain as Core. Releases from 29.3.knots20260508 (May 9, 2026, UTC) on enforce BIP-110, a temporary limit on data in transactions, and nodes running them rejected the main chain's blocks from August 8, 2026 and split off. Knots 29.4.1, released September 2, 2026, is a hard fork that gives that chain a BLAKE2b proof of work. Details

Sources (16)

Related terms (10)

Published . Revised . One correction logged for this page.

Edit this page on GitHub