In the space of just a couple of days, 'bitcoin core' ran up close to 300 nodes with its latest version. Wanna bet all these 29.1.0 nodes wont turn on v30 fast? This is a wrap. Core has been compromised for a long time. True Bitcoiners do not run core nodes. Move and keep bitcoin for money - that is its use case

Run a v30 core node? This is what the headlines could look like Mainstream media will be ready to report this immediately. Stop it now. Run a (knots) node OR run a node with any other software besides 'core' v30 - due out this Friday. Any old SSD laptop online can do this

Latest Core version now suddenly 100 nodes ahead of Knots. This is a major attack. No other explanation If you run a Knots node, spin up another :)

Bitcoin... If you controlled a central bank - Would you do nothing to stop this? Would you not use your printed paper to make sure your printer wins long term? This isn't hard

With 'core' v30 nodes online there could be child sexual abuse material on every bitcoin node. Then it's just a matter of declaring such a server illegal and bingo you head towards a centralized bank. That is not Bitcoin Get 'coreporation' Bitcoin out Run Knots and Defend your Money

Like most good things these days Bitcoin is under attack You won't hear about it on the news They haven't reached that part yet I am already and will continue to cover this topic At length! Apologies for the break in regular programming

Looking forward to the soft fork Let 'core' fans go mine whatever data sh1tcoin they feel like

A SOFTFORK enforcing OP_Return limits which is backwards compatible may be the way out - Pass it on Get Out of 'Bitcoin Core' which has gone ROGUE by enabling 100k jpegs on chain which may contain Child Sexual Abuse Material #RunKnots

We need a version that physically filters op return blocks out of the chain.

Defend Bitcoin Run A NODE RunKnots

Use Bitcoin for your financial sovereignty? Run A Node Run Knots (It's IMPORTANT)

The community is waking up. Those who care about bitcoin enough run nodes. Caring means they will notice when an update torpedos the network. Our job is to make sure this deception stays in the spotlight until core lands in the dumpster RunKnots RemoveCoreporation

We got this far by moving We must keep moving If the core is rotten #RunKnots

Let's remember: Satoshi did this (financially) for 'nothing' If 'protocol developers' are being incentivized by fiat hoarders to 'develop' then here is the obvious breakdown of Bitcoin to bitcoin CORP A centralized corp pushing bitcoin development 🚩

'X' is a censorship platform My 'reach' there -> 0 Please make people aware that they are never seeing the whole picture Opinions are removed, manipulation is rampant

Satoshi did this (financially) for 'nothing' If 'protocol developers' are being incentivised by fiat hoarders to 'develop' then here is the obvious breakdown of bitcoin to bitcoin corp The users who understand the problem Satoshi solved want bitcoin. Not bitcoin corp

OP_RETURN bloat is not necessary Bitcoin is just fine without it So I will keep campaigning I like lots of node runners I work to increase their number

Would somebody please contact Dennis Porter... And have him come on Nostr Unfortunately he is another one of those who do not understand just how much censorship is going on on 'X' and how we need free communication to move Bitcoin along. Nostr rules

The OP_RETURN war is heating up Seems to me that this could culminate in a fork which nobody wants Lukas - duczko on X wrote: My current understanding of the Core/Knots debate below 👇 Let me know what you think. CURRENT STATE 1. All nodes are blocking the data so <100kb images can’t get stuffed into the chain in easy readable form. 2. Slipstream and MARA wont accept to put illicit images on-chain via their backdoors because it’s a massive business risk for them (and the team would have moral objections too). 3. People that want to put illicit images >80 bytes on-chain are left with the only option to chop up the data in hard to read form. Thereby giving the noderunner plausible deniability and relative safety from government crackdown. 4. As a result the chain is mostly clean from easy readable large 100kb-ish images with illicit content. Yes, there is nasty stuff hidden in convoluted forms, but you have to have special software and know where it is to find it. Thereby, hosting the blockchain is not tied with legal risk. NO FILTER STATE 1. Anyone can put large illicit images >80 bytes into your node. Because you are downloading and decrypting the data in easy readable form by the node software you don’t have plausible deniability and you are exposed to significant personal legal risk. 2. Also, the chain will start getting stuffed with illicit images that everyone will have to store. Which may also become a big problem for node runners down the road, making hosting Bitcoin blockckain into a toxic waste storage operation that many noderunners may opt out of. SUMMARY Core is playing with fire. Changing from current state into a filterless state is not a trivial change as many claim but is connected with significant risk to destroy incentives for noderunners to run nodes. Risking significant decrease in people wanting to run nodes and thereby decreasing Bitcoin decentralization. NOTE An argument I often hear is “only economic node matter”. I’m not sure I agree, but let’s assume it’s true. Then it’s still true that the people running economic nodes have personal risk and if it’s a business then it’s also a team and a business risk that many economic noderunners may not be eager to take.

Luke Dashjr People need to stop trying to dress up attacks on Bitcoin as "debates". That implies there are two legitimate "sides". There is no "debate" around OP_RETURN. There is an attack, and it must be fought.