Replying to Avatar FLASH

⚡️⚔️ NEWS - Bitcoin ATTACKED from within?!

That’s how some describe the fierce conflict between Bitcoin Core and Bitcoin Knots — a battle that could redefine the very nature of the protocol.

At stake: Bitcoin’s neutrality and the future of the blockchain.

Bitcoin Core — the most widely used software to run a node — was originally coded by Satoshi.

But Core ≠ Bitcoin.

Any Bitcoiner can choose another implementation. That’s decentralization.

Now, a storm is brewing inside Core…

A new proposal suggests removing the 80-byte limit in the OP_RETURN field.

It might sound technical — but it’s huge.

Why? Because it shifts Bitcoin from being a monetary network…

…toward a general-purpose blockchain like Ethereum or Solana.

Removing this limit enables:

- On-chain data storage (images, NFTs, tokens…)

- Ethereum-style use cases

- More congestion, higher fees, and heavier nodes

And most controversially:

the new limit would be non-configurable.

Translation: Core devs decide for everyone. A clear break from the principle of individual sovereignty.

Tensions escalate.

Some critical voices — like bitcoinmechanic — are banned from the Core GitHub.

Words like censorship, conflicts of interest, and centralization drift are flying around.

Here’s what it looks like:

✔️ ACK = Accept the change

❌ NACK = Push back

Enter: Bitcoin Knots.

A fork of Core, maintained by OG dev Luke Dashjr, which keeps user freedom intact. In 2025, Knots is gaining serious traction.

The war isn’t just in code — it’s ideological: “Don’t trust. Verify.”

Every node operator has the power to say NO.

The community is mobilizing:

- Cut donations to compromised devs

- Launch educational campaigns

- Expose bad actors

- Boycott biased podcasts & events

Because in Bitcoin, vigilance is the last line of defense.

Why would I trust Luke?

Reply to this note

Please Login to reply.

Discussion

Trust no one

Just Verify

Hasn’t it been verified that he did some sneaky shit already?

it is a good question

nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq36amnwvaz7tmwdaehgu3wvf5hgcm0d9hx2u3wwdhkx6tpdshsqg9tvep3k80m46uqtf4aysm9cgzxc73zdr0xgw7sdy9yjn9qg2mstsmg2qrx do you know what is the control and code review used for bitcoin core and for knots ?

#asknostr

Bitcoin Core's code review process is rigorous, involving multiple developers and focusing on security and reliability. Bitcoin Knots, being a fork maintained by a smaller group, likely has a less formal but still careful review process, focusing on bug fixes and performance. Specific details for Knots are harder to find via search, but the general principle of 'Don't trust, verify' still applies, as node operators can choose which implementation to run.

You don’t have to trust anybody when you’re able to customize the software your self. This argument about trusting Luke is a bit of a stretch. Knots allows full customization. Core devs want to REMOVE features from the software. I don’t care what they want to accomplish, it’s about my choices as a node runner. I came to Bitcoin for self sovereignty, not trusting elite devs to make choices, thats just fiat system all over again.

Customize the software myself? Arent we trying to make this thing accessible to the almost 2 billion unbanked? Now they will need to write their own code too? So much for mass adoption if this is the future. Most bag holders including myself are not devs, coders, or tech savvy.

Here’s just a small portion of some options available on Knots, no code required! It’s easy and lightweight to run your own node right now, again, no coding required. Once the blockchain is full of spam and bloat data, it will become much more expensive and spec heavy to run your own node. Like Eth for example.