Why Your BIP-110 Knots Node Stops Working

BIP 110 Knots Node

Share this article

If you run a Bitcoin Knots node with BIP-110 enforcement switched on, you may have noticed something odd: your node hasn’t added new blocks, and you’re way behind the block height shown on public sites like Mempool.space.

The node shows peers, reports itself as healthy, and may even say it is fully synced. But the block height hasn’t moved in months, so what gives? Did your node get bricked?

No!

Nothing is broken with your hardware.

Your node is doing exactly what it was told to do. It is sitting on a branch of the chain that almost nobody is mining, and it will stay there until you change which rules it follows.

Why Your Knots Node Stopped?

BIP-110 (the Reduced Data Temporary Softfork, or RDTS) was designed as a user-activated soft fork. Its rules required “mandatory signalling” to begin at block height 961,632 (around 8 August 2026). From that block through block 963,647, any block that did not signal support in version bit 4 was invalid under the proposal.

Nodes enforcing BIP-110 therefore rejected non-signalling blocks. The rest of the network, running ordinary Bitcoin Core or Knots without RDTS, kept accepting them. Only a small share of hashrate (a community note on Knots’ own announcement put it at about 2.5%) mined blocks that satisfied BIP-110, so the two sides split at 961,632.

The enforcing branch found just two blocks, at heights 961,632 and 961,633, and then stalled. Meanwhile, the main chain carried on at normal speed. An enforcing node has no way to accept those blocks, so it waits for a successor that never comes. As Start9’s guidance put it, a stalled node looks exactly like a healthy one: it keeps running, keeps showing peers, and simply stops receiving blocks.

Later, Knots 29.4.x added a separate hard fork to a BLAKE2b proof-of-work at height 961,640. That is a different matter from the stall described here.

We won’t get into moving to an alternative chain; this is for operators who want to leave the BIP-110 branch, return to the main chain, and continue using Bitcoin or Lightning as they did before their node fell out of sync.

Which Block Height Are You Stuck At?

Most affected nodes are frozen at block 961,633. Operators on Start9 and Umbrel forums reported exactly this: a tip that stayed at 961633 while public explorers showed higher blocks.

The two hashes at the split are:

HeightMain chain (AntPool)BIP-110 branch
961,63200000000000000000000d1e01392faa65ceeaed307f0a3159144b84146ff24ba0000000000000000000169eb6f811ddbd0daf343af7b62180cdb13e7c78dbc16
961,633(main chain continues)0000000000000000000139eda19858a84b2ed80cb6056ba8449f0792d13d0968

I checked the main-chain hash against a block explorer and the BIP-110 hashes against a published list of stale blocks, rather than relying only on the instructions below. Do the same with your own explorer before running any commands.

To see which side you are on, run getblockhash 961632 on your node. If it returns the hash ending in ...0169eb6f...bc16, you are on the BIP-110 branch. If it returns the one ending in ...d1e01392...24ba, you are already on the main chain.

What “Fixing” It Means

You will often hear that you need to “reset to the block where the chain split.” In practice, there are two parts:

  1. Run a Knots build that doesn’t enforce RDTS. The last matching release without it is v29.3.knots20260507, which can use your existing data directory. Builds from v29.3.knots20260508 onward include the enforcement.
  2. If the node stays put, mark the first BIP-110 block invalid. Invalidating block 961,632 on the BIP-110 branch also invalidates its child at 961,633. You don’t need two commands, and you don’t download the chain again.

Most people only need step 1.

Before You Start

  • Pruned nodes: stop here. Guides for Start9 and Umbrel warn pruned operators not to proceed. Pruned data can make an in-place switch impossible, and Knots’ own notes say a pruned node that followed invalid blocks may need to re-sync from scratch.
  • Stop everything that depends on the node, including Lightning, Electrum servers, explorers, mining and watchtowers. A Lightning node watching a chain that is being rewritten underneath it is the thing to avoid. Don’t send or receive funds until everything is synced again.
  • Back up your wallet and your Lightning channel backup.
  • Don’t reindex first. A normal switch keeps your existing blocks and chainstate. Use a reindex only as a last resort, as described below.

Fix on Umbrel

  1. Stop your Lightning Node app and anything else that depends on Bitcoin Knots (Mempool, Forktower and similar).
  2. Open Bitcoin Knots → Settings → Bitcoin Knots Version.
  3. Select v29.3.knots20260507, save, and let the app restart. Any build earlier than v29.3.knots20260508 works, but one operator reported that choosing the 0508 build triggers a “Consensus rules change” pop-up that can’t be dismissed.
  4. Wait. The node may look as if nothing changed, because it will still show the BIP-110 tip at first. Leave it for a few hours while it finds the main-chain tip.
  5. If it stays on the BIP-110 block, open the umbrelOS terminal and run:
sudo docker exec bitcoin-knots_app_1 bitcoin-cli -rpcport=9332 invalidateblock 0000000000000000000169eb6f811ddbd0daf343af7b62180cdb13e7c78dbc16

The container name can differ between umbrelOS versions. If the command can’t find it, run sudo docker ps and use the name of your Bitcoin Knots container.

  1. If Knots still won’t start cleanly or advance, go to Advanced → custom bitcoin.conf overrides, add reindex=1 and restart. As soon as the reindex finishes, remove reindex=1 and restart again. If you leave it in, the node rebuilds everything on every start.
  2. Start your Lightning app only when Knots is fully caught up.

Fix on StartOS 0.4

This is the simplest case, because both Knots flavours are listed in the Start9 marketplace.

  1. Stop Lightning and any other services that depend on Bitcoin Knots.
  2. Stop Bitcoin Knots (RDTS).
  3. Refresh the marketplace and install Bitcoin Knots (pre-RDTS). It uses the same package and your existing data.
  4. Start it and wait for it to sync. If it finds stored invalid-chain verdicts, it clears them and shows a Chain Verdicts Reset notification. If it finds none, you won’t see one, which is fine.
  5. If it doesn’t start cleanly or advance, use Actions → Reindex Blockchain.
  6. Don’t run the manual invalidate command on StartOS unless it reports a problem.

Fix on StartOS 0.3.5.1

Start9’s community recommendation is to update to StartOS 0.4.0.x first and then follow the steps above. Read Start9’s upgrade guide before you do, and take a backup.

If you won’t update the OS, you can sideload a pre-RDTS package from the community (Retropex, not an official Start9 release):

  1. Back up through System → Create Backup and don’t uninstall Bitcoin Knots.
  2. Download bitcoind.s9pk from the v29.3.knots20260507 release and check that its SHA-256 matches 3a57a796c5f211d810b44ee9e948ca84ac985fcca5af586f1ae1272c2f23f1dc.
  3. Stop all dependent services and Knots.
  4. Go to System → Sideload Service and upload it as an update to the existing service.
  5. Open Knots, choose Configure, save and start it.
  6. If it doesn’t resume sync, connect with ssh start9@your-server-name.local and run:
sudo docker exec bitcoind.embassy bitcoin-cli getblockhash 961632
sudo docker exec bitcoind.embassy bitcoin-cli invalidateblock 0000000000000000000169eb6f811ddbd0daf343af7b62180cdb13e7c78dbc16

Run the second command only if the first returned the BIP-110 hash.

How to Check It Worked

Wait for your peers to send the main chain, then run these on your platform (use the prefix from the sections above):

bitcoin-cli getblockhash 961632
bitcoin-cli getblockchaininfo
bitcoin-cli getbestblockhash

You should see:

  • getblockhash 961632 returns 00000000000000000000d1e01392faa65ceeaed307f0a3159144b84146ff24ba. If it still returns the ...bc16 hash, you are on the wrong branch.
  • blocks equals headers, and initialblockdownload is false.
  • Your tip matches a public explorer. Compare getbestblockhash with the latest block on mempool.space or another explorer, and check that the height is moving again.
  • Dependent services catch up. Wait for each index and your Lightning service to report that they are fully synced before you use them.

If you used invalidateblock, bip110.org’s guide suggests clearing that temporary mark only after the node is fully synced, by running the same command with reconsiderblock and the same hash. After that, run getblockhash 961632 again and confirm it still shows the main-chain hash. This step is optional, and if you’re unsure, leave it alone.

If It Still Isn’t Working

  • The node says it’s synced, but nothing moves. Compare the block hash at 961,632 with the table above. It is the most reliable test.
  • Stuck after a downgrade. Some operators needed reconsiderblock on the last block in their queue, or a one-time reindex.
  • Forktower or a watchtower is complaining. Once everything follows the same chain, you can uninstall Forktower.
  • You are on Knots 29.4.x. That version follows a different hard fork at height 961,640 and is not the same situation as this one.

A Note on Choosing a Side

If you’re a node operator who wants to follow the main chain, or so-called legacy chain, then the above applies to you. Others who want to commit to the BIP-110 nodes on purpose can keep their Knots version at the latest 29.4 and point their node to the Blake2B chain, a completely separate chain forked into another network, with its own asset XBT.

What matters is that you choose deliberately, or you’re simply wasting resources running a node that does nothing. A node stuck on a minority branch isn’t validating the chain most of the network uses, so you can’t run wallets and services on your own node and would need to link to a third-party node to broadcast transactions.

Defeating the purpose of running a node in the first place.

Disclaimer: This article should not be taken as, and is not intended to provide any investment advice. It is for educational and entertainment purposes only. As of the time posting, the writers may or may not have holdings in some of the coins or tokens they cover. Please conduct your own thorough research before investing in any cryptocurrency, as all investments contain risk. All opinions expressed in these articles are my own and are in no way a reflection of the opinions of The Bitcoin Manual

Leave a Reply

Related articles

You may also be interested in

HD Aezeed Wallet Explained

What Is An HD Aezeed Wallet?

Since there is no Bitcoin University that can give you a crash course in using the technology, and most of us figure it out via

ERA wallet explained

What Is the ERA Wallet?

Hardware wallets have come under a lot of scrutiny over the last year, and rightly so; what was once seen as the gold standard for

Cookie policy
We use our own and third party cookies to allow us to understand how the site is used and to support our marketing campaigns.