Installing BIP110 - February 2026
Installing BIP110 on Ubuntu 24.04 from source
Intro
This article is intended for those people already running Bitcoin Knots or Bitcoin Core on Ubuntu who want to build from scratch and run BIP110.
You can watch this YouTube video to follow along with this process.
https://youtu.be/YYGnaBWTC0g
You can find more information about BIP110 on this website.
https://bip110.org/
These instructions take you through deploying the first official release of BIP110 (v0.1) on Bitcoin Knots. This is a drop-in replacement for Bitcoin Knots and Bitcoin Core v29.x.
Prep Work
If you have an existing node installation, first stop it. Then move it, ready for the new BIP110 version to be downloaded.
mv bitcoin bitcoin.oldNext, we need to clone the BIP110 repository.
git clone -b v29.3.knots20260210+bip110-v0.4.1 --depth 1 https://github.com/dathonohm/bitcoin.gitLet’s verify that the code has not been tampered with.
cd bitcoin
git verify-tag `git describe`You might get a warning like “gpg: Can’t check signature: No public key”. Let’s see if there is a publicly registered key for that hash.
gpg --keyserver keyserver.ubuntu.com --recv-keys "2B97F03293744D70F6BBA82F2E3A66FF67F98B4F"
git verify-tag `git describe`This time, you should see a “Good signature from Dathom Ohm”. You will get a warning that the key is not certified - but we can’t do this unless we actually meet Dathom, or someone we trust who has met Dathom, to 100% confirm it really is him.
Time to get building.
The less code you use, the less likely you are to be affected by vulnerabilities and bugs. I don’t use the Bitcoin wallet built into the node software or Tor, so I disable both.
I solo mine with ckpool-solo, and it is more efficient with ZMQ enabled, so I enable ZMQ support.
Lastly, I want the node to be as fast as possible, so I enable all host CPU optimisations. Paste all of this in one go. It checks what is available and configures the build environment.
cmake -B build \
-DENABLE_WALLET=OFF \
-DWITH_ZMQ=ON \
-DENABLE_TOR_SUBPROCESS=OFF \
-DCMAKE_CXX_FLAGS_RELWITHDEBINFO="-O2 -g0 -march=native"And now we get to build it! This can take a long time. On my machine, it takes 12 minutes.
cmake --build build -j 4Optionally, you can run the test below to verify it starts up correctly. Hit CTRL-C when done.
./build/bin/bitcoindYou want to see the first line mentions that it is running a version with BIP110. This is what mine looked like.
2026-02-06T00:31:55Z Bitcoin Knots version v29.2.knots20251110+bip110-v0.1 (release build)And then start your Bitcoin node as you did previously. I use systemctl, but I won’t cover that off here.
You can then run the command below to confirm that your node is advertising support for BIP110. Note that this command will not work until your node has finished starting up, which might take 30s to 60s.
bitcoin-cli getnetworkinfo | grep subversionYou should see bip110 in the output. This is what mine looks like:
"subversion": "/Satoshi:29.2.0/Knots:20251110+bip110-v0.1/UASF-BIP110:0.1/",Final Thoughts
You can monitor the BIP110 rollout on this website. At the time of writing, there were already 1,305 BIP110 nodes.https://thebitcoinportal.com/nodes/bip110


You think there’s any validity to the argument. Knots vs Core. Since knots will not have the bloatware of core, it will not over time collect the same amount of information, making it marginally slower and lower in odds of finding a block? Also factoring in how many blocks are being found by foundry USA, sec pool etc… if over 50% of network complicit, and using core, could it be a disadvantage?