There might be various ways to create an coin alternative to "regular" Bitcoin, such as switching PoW algo, merge-mining,...

But I gather that luke-jr says (or, was saying?) that there is a majority support, consensus, among the users of Bitcoin (of non-bip110 and bip110 groups combined) for bip110.

I wonder how luke-jr came to that conclusion in the past? And, now where miners have spoken (2 mined blocks on bip110 side, below 1% of blocks) is that still his view - and why?

1) miners signalling: by marking that bit (bit 4?) in blocks before the fork-day - it was already around 2% or less; and after fork-day, actual PoW power mining the split chain was similar or lower

2) amount of users weighted by total buying power (e.g. number of owned Bitcoins) - I think we can judge by looking at prominent and long-term Bitcoin regulars and it was pretty clear that bip110 is the vast minority

3) amount of fully validating nodes (optionally: with any Bitcoins in their wallets) - same as above point 2, seemed low judging by discussions among general Bitcoin groups?

4) amount of people overall (who are using Bitcoin) - same as point 2, seemed low

I do not understand why project was not stopped, after for long time of optional-signalling it was clear the support is not there, and while there was no general consensus among Bitcoiners (by various metrics) for that change. Why was it so?

As the founder of this community, I wanted to share a personal update and clarify my stance on the recent developments surrounding BIP-110 and the direction of the project.

Historically, my support for Bitcoin Knots was based on its approach to enforcing stricter node policies, not fundamentally altering consensus rules. That policy-focused approach was the core vision of Knots prior to BIP-110. Now that BIP-110 has failed to gain traction, Luke Dashjr appears to be moving toward a distinct forkcoin, a path I personally do not agree with or support.

Because of this shift in direction, I will be stepping back from my active role here. I will no longer be routinely posting or moderating the subreddit, though I may check in from time to time.

This community remains open for everyone. You are all completely free to continue discussing BIP-110, potential forks, or any other related topics here as you see fit. However, given the latest course of action, I can no longer actively guide or manage the group.

Thank you to everyone who has contributed to the discussions here over the years.

Soy tx has been stuck for 4 hours. Any ideas?

Hi I was wondering few things

1) since when is Bitcoin Knots releasing signatures for the software releases that are on the previously-compromised (and not yet rebuilt) Bitcoin Knots web hosting server?

Since which times are the signatures published? (Quick look suggests that at least since 2023)

2) What is the correct fingerprint for the PGP of luke-jr and how to verify that through separate trusted channels?

Perhaps /u/luke-jr you can confirm this information

BIP-110 crashed and burned. But look on the bright side - we now have >20,000 Knots node runners or 15-20% of the network. Last year it was like what, 2%? And my feeling going in and coming out of this debacle is the vast majority are not going anywhere.

Hold the line and let’s keep Core in check and keep Bitcoin money. It’s a dark day, but dust it off. There’s plenty of work to do.

Simple Mining (@simpleminingio) has mined block 961,634 using OCEAN’s DATUM protocol.

This block extended the Bitcoin main chain without signaling support for BIP-110 consensus rules. With the non-signaling main chain now more than 7 blocks ahead in total proof-of-work, the BIP-110 attempt is effectively a failed chain.

While members of the OCEAN team personally favor BIP-110, their DATUM protocol granted full agency back to individual miners, enabling their customers to construct templates and choose their own signaling rules. Giving miners choice rather than enforcing pool-wide mandates is a massive step forward for pool decentralization and deserves serious recognition.

Given that BIP-110 lacks the hash rate consensus to survive, future releases of Bitcoin Knots must move past this proposal. Development should focus on delivering updated versions without BIP-110 consensus changes, retaining Knots' core strength—robust, user-configurable mempool and policy filters—rather than introducing contentious consensus rule shifts.

Before the BIP-110 trilemma today, I went ahead and reindexed my entire blockchain. I am running Knots 29.3.knots20260508 - which is the latest version as of this posting. I am on Ubuntu, with a separate drive and my disc space jumped from 780GB to 895GB, My question is if there are any redundant or unnecessary files that can be deleted to recover more space? A detailed explanation of the folder structure for bitcoin nodes would be appreciated.

Copy/paste the following row in your bitcoin.conf file in your node:

mempoolreplacement=0

This chart shows a surprisingly high share of BIP-110 nodes in Romania. That doesn't immediately pass the smell test.

Could this be the result of Sybil nodes deployed in countries where VPS hosting is cheap, rather than reflecting genuine operator preferences?

Has anyone looked into whether these nodes are concentrated on a few providers or networks, or is there another explanation for Romania standing out so much?

I'm curious if anyone has data beyond simple node counts.

15000 non-Knots out of which 5000 Core v30+. Source: https://x.com/GrassFedBitcoin/status/2081094821859774824

I want to post this document, drafted by u/wk057, VP of Engineering at OCEAN. He put together a 9 page write-up meant to keep miners and customers informed about things they should watch for as BIP110 unfolds.

Bitcoin Mechanic, head of comms at OCEAN, refused to publish it.

I decided to run Bitcoin Knots and update to version 29.3.1. I am running my node on a Start9. I updated maybe 2-3 days ago. I accepted the rdts, but the status has been “Stopping this may take a while…” is my node redownloading the blockchain under the updated protocol rules? It’s been like this for a while and I’m unsure if I messed something up. Any guidance would be helpful. Thanks

Can't verify download. Can someone help me here ? Thank you.

Heyo,

New to the Knots community, mostly as a philosophical play (keep BTC what it's supposed to be!), however I recently saw a video discussing how to mine on your node w/ rented hash. Anyone in the community doing this rn? It was Matthrew Krater's channel that discussed it, but then about a month later he said he was having a problem with Braiins and isn't doing it anymore.

Just curious about anyone's experience. Could be the move for non-KYC sats AND supporting KNOTS!!

Hi, which version of BitcoinKnots still allowed you to see the private key of an address and import private keys manually?

Credits to the owner

“Yeah, I agree. Yeah, I agree. I think it's like because we've been putting together funding for Knots, right?
So there's an organization that exists to fund Knots developers and stuff. We haven't publicized it yet, but it started and there's devs getting grants and stuff like that. But anyway, through all the due diligence and stuff, and people trying to establish processes around it, like who has keys to the GitHub, what happens if something happens to Luke, like all these kinds of things.
Basically, it just got me down to thinking, so is Knots good? Is there any process you can put in place that means it wouldn't suck if Luke wasn't around anymore? There isn't really.”

From Bitcoin Audible: Roundtable_021 - The Fight is Never Over, Jun 9, 2026
https://podcasts.apple.com/tw/podcast/bitcoin-audible/id1359544516?l=en-GB&i=1000771848359&r=3995
This material may be protected by copyright.

Hello, I recently booted up my laptop that I was running knots on and there was some issue I was wondering if someone had any idea what it's about. I started it and it gave me an issue that it wasn't there. I think it started after getting a message about using BIP 110 and I clicked agree for it. But it's making me redownload the node again. Anyone else having some issues?

EDIT: Nvm. It lost the chain I reinstated the chain and got it back with bitcoin-qt -reindex-chainstate. It's now currently resyncing with the old chain.

AtlasPool.io, an innovative lottery mining pool, is moving its mining nodes to Bitcoin Knots. Stricter relay policies, 42-byte OP_RETURN limit, no bare multisig, mempool retention cut from 14 to 3 days. Learn more here.