
Posting about software and Bitcoin (money not a database; #BIP110)
Cygnus X-1
Joined April 2009
- Tweets2.2K
- Following1K
- Followers393
- Likes19.8K
Jon Matcho retweeted
Replying to @saylor
Hi,
So BIP110 isn't anti-spam. It identifies >83 byte OP_RETURNs and the usage of OP_IF in taproot specifically as threats that go beyond mere spam having become sanctioned as *official methods of file storage in Bitcoin*. This happened as a result of Core 30 removing a filter in the midst of a discussion that was centered around the less consequential defaults for relay policy, which remains where conversations about spam actually belong.
Bitcoin is *not* a file storage platform, and if it is allowed to become one it seems inevitable to most that it will eventually be used for the worst kind of media given its unique ability to "force" everyone to store the media in perpetuity whilst having the option to do so anonymously.
Those who do not understand this scream "fear mongering" or simply do not understand that Bitcoin only works if it is decentralized and that deviating from a monetary mandate to arbitrary data storage means the death of decentralization.
This has all been carefully delineated amidst an incredibly noisy, emotionally charged conversation which is all the result of Bitcoin not having a corporate governance structure which is a feature, not a bug.
You can participate in the discussion in an informed way, and if you were to do so, it would be greatly appreciated given your overwhelming influence.
But it appears that so far, you have yet to even understand the motivation for the BIP. The spam filter/default relay policy conversation never ended and continues the minute BIP110 activates and the JPG spammers all find some new approach. But Bitcoin will no longer be vulnerable to the specific issue BIP110 targets.
Jon Matcho retweeted
"If you don't believe that you get to decide the rules, then you don't understand the game."
Jon Matcho retweeted
Notice BIP-110ers don’t really talk about price these days.
They know what’s currently at stake is much more important than price.
Run BIP-110. #Bitcoin
Jon Matcho retweeted
Do not allow people like @BitMEXResearch, @adam3us, @brian_trollz, @theonevortex and their incompetent ilk call @hodlonaut his articles "slop". Always push back on their nonsense.
Jon Matcho retweeted
While the resistance to Core V30 has happened in the open, with complete transparency and organic cooperation
The "pro V30" side has fought with tactics we became very familiar with during covid:
1) Gaslighting by ignoring what was happening, "don't talk about it, pretend it doesn't exist"
2) Backroom coordination, very little transparency
3) Censorship on established fora and channels
4) Social pressure and ostracization for talking about it
But now that ignoring it hasn't worked, those tactics are backfiring.
It's just looks really dumb when you come out guns blazing against BIP-110 when you've been pretending to ignore the issue for the last year
Jon Matcho retweeted
@JonMatcho Unfortunately, these people aren't going to read or listen to anything that refutes their biases. They will scramble to the next argument as soon as you disprove one.
Watch:
Hey guys, ignoring deprecations for a moment, BIP-110 is proposing a consensus change to OP_RETURN, not a policy change, hence no, changing datacarriersize is not the same thing...
Jon Matcho retweeted
The real damage from L1 spam (inscriptions, Runes, etc.) isn’t higher fees.
It’s the bloated UTXO set that increases verification costs for sovereign nodes — more RAM, more I/O, longer IBD.
BIP-110 in Knots sets temporary limits on arbitrary data inside scripts and witnesses to realign incentives back to money, not data.
This isn’t censorship. It’s protecting verifiable sovereignty.
Jon Matcho retweeted
2026 will be a year full of high signal in bitcoin.
We saw in 2025 that, despite the shitcoiners seemingly taking over with Core 30's release, the latter part of the year witnessed some of the best discourse in bitcoin in years.
Monetary maximalism is alive and well.
Jon Matcho retweeted
Replying to @TheGuySwann
I think it’s quite simple: Core apologists only appeal to the UTXO set growth when making an argument defending something else they want to implement.
Knots-aligned people see the bloat as an existential long term threat to decentralization and are exploring remedies.
Jon Matcho retweeted
"In keeping silent about evil, in burying it so deep within us that no sign of it appears on the surface, we are implanting it, and it will rise up a thousandfold in the future. When we neither punish nor reproach evildoers, we are not simply protecting their trivial old age, we are thereby ripping the foundations of justice from beneath new generations."
Scamming gullible newcomers out of their hard-earned sats by hyping worthless JPEGs isn't just greedy speculation, it's profoundly evil predation that exploits ignorance, siphons real sovereignty into vapor, and deliberately muddies the waters to delay the masses from grasping Bitcoin's singular, unreplicable monetary revolution.
This quote is from Aleksandr Solzhenitsyn's The Gulag Archipelago (1973–1975), specifically in Volume 1 (Part I).
I think it’s eerily pertinent, as we are talking about digital shit!
Jon Matcho retweeted
The consensus rules have always been about morality
One charge that's frequently levied at knotzis is that any attempt to reject spam at the consensus level is based on "moral" objections to spam transactions instead of "technical" objections. One problem with this... 1/4
Jon Matcho retweeted
Whether you are pro-core or pro-knots, do you feel the next version of the core client should go back to a reasonable OP_RETURN size?
74%Yes
26%No
306 votes • Final results Jon Matcho retweeted
Replying to @rot13maxi
@rot13maxi realizing his VC-funded house of cards is fast becoming more worthless than its previous levels of worthlessness...
Jon Matcho retweeted
Replying to @citrea_xyz
No, you’re not at all “Bitcoin-focused”. You’re focused on prolonging your venture capital funding, and your VCs are just looking to turn a profit. The value driving that is the Fiat system.
Jon Matcho retweeted
Tossing federal money doesn't make health care cheaper. It just changes who pays. If people can't afford health care, taxpayers can't either.
Jon Matcho retweeted
The fact that Gloria deleted her Twitter account is an obvious sign of weakness.
She won’t even defend her positions.
She is a total disgrace to Bitcoin.
She should resign as a Core Maintainer yesterday.
Jon Matcho retweeted
Not everyone can code, but everyone can understand bitcoin's monetary properties.
No excuse for being ignorant of bitcoin's value proposition if you are in a position to make changes to bitcoin's code.
Jon Matcho retweeted
Defaults (especially on a reference client) are special choices made on behalf of others who want to defer to experts about what is best. In addition, they act as signals to outsiders: “What is the purpose of this protocol?” They’re very important and meaningful.
Replying to @cinnaman18 @satflation
Changing default client settings≠changing consensus rules.
Also, i know. That’s why I’m predicting it will happen, and that it will be a knots supporter that does it.
Jon Matcho retweeted
F2Pool is actively attacking the network RIGHT NOW. All it takes is one attacker to send them a single instance of CSAM, and Bitcoin users will have to knowingly and intentionally receive, store, and distribute it until the end of time. This will permanently impact Bitcoin adoption regardless of whether governments turn a blind eye or prosecute. If miners are going to switch pools when they do bad things, NOW IS THE TIME.
I don't care if you switch to Foundry or even Antpool. Obviously I would prefer you make your own blocks and use OCEAN, but this is too critical and time-sensitive to be picky. We can work on mining decentralization and spam issues over a longer period of time, but CSAM is an insta-kill we MUST avoid.
Mining is centralized.
The concern around objectionable content is met with appeals to decentralization of mining - i.e a Bitcoin network that doesn't exist.
Until now, what has already been "technically possible" with storing nasty stuff in the chain wasn't.
1. "The" mempool was protected because everyone would filter a sick 100kb OP_RETURN along with *all* OP_RETURNs greater than 83 bytes.
2. The blockchain was protected because the few miners there are in the world would reject directly submitted malicious content.
This left one option for sabotage: an attacker mining a CSAM OP_RETURN directly into the chain themselves.
Referring to something as impractical as that as "technically possible" is entirely frivolous and it would have been laughable if it had ever happened. An "Unknown" pool finds a block that has a giant 1MB MP4 of something appalling in it? Obvious sabotage that we would universally eschew and I'm confident we would be able to resolve after the fact.
Now however the situation has changed.
F2Pool solicits this stuff directly from the p2p network and Libre Relay nodes along with Core 30 release candidates are willingly relaying it.
There is now an anonymous, p2p network for this attack that's free to access and there is a miner who will oblige it.
The combination of the above, in practice, drops the cost from six figures ($$$,$$$) to three ($$$) and makes it possible to do anonymously.
But more importantly, the mechanism of the attack makes the resulting content appear to have been endorsed by the network at the policy level rather than come as a result of a circumvention that exploits crude consensus rules.
If you still cannot understand the significance of that then you must simply not be aware of the changes that Bitcoin has undergone with all the malicious tweaking of late and the sheer desire there is to take Bitcoin out.
Again: The p2p network has protected itself from attack due to sane default mempool policies, while the blockchain has been inaccessible to attackers due to pools not wanting to be on the hook for blocks containing malicious data.
Those technically-circumventable factors are now gone and there is no practical limitation to the attack beyond cleaning some coins, and paying a couple hundred bucks in transaction fees to get unacceptable content into the chain.
If the network isn't going to protect itself from malicious, consensus-valid activity then the only option left is changing consensus and doing a soft fork to limit OP_RETURNs and perhaps other known types of data carrying.
That idea entered the arena on the mailing list on Friday from someone vocally against Knots (@PortlandHODL) and was received positively by the Core devs who responded. Some embellishment was offered by Luke (add additional data carrying types) to which there was not so much response.
Without community support a fork fails. It's possible if even the Core 30 proponents are OK with limiting this stuff at the consensus level though that there is community support and thus it could be the way forward.
I dislike it because it abandons spam mitigation occurring at the policy level which is where it belongs but the current environment isn't giving us a lot to work with.
It is probably appropriate to characterize the fork as defense we never needed against a specific type of attack versus spam mitigation in general which will have to be continue in parallel.
Fork?






















