Pinned Tweet
#libertarianism is just as absurd a concept for a sustainable society as #socialism is on the other far end of the spectrum.
1
3
NNMarbas retweeted
⚠️ Rumor circulating in the XBT Bitcoin Knots mining community: There’s talk that regular Stratum pool miners on Blake2B XBT may potentially be excluded from future payouts, with the devs reportedly considering (radically) a Datum-nodes-only approach.
If true, that could mean miners who spend the next 45 days mining won't receive their payout. 😬
Nothing is confirmed but this might happen... they want this to happen.
NNMarbas retweeted
I repeat: BIP-110 has NOT been canceled. BIP-110 CANNOT be canceled. Please spread the word.
Replying to @dathon_ohm
@LukeDashjr @BTC_for_Freedom @hodlonaut @DrJackKruse it would be wonderful if some large X accounts could help spread the word. Unfortunately my following is apparently too small to be picked up by the LLMs.
NNMarbas retweeted
Luke Dashjr on what actually belongs on the Bitcoin blockchain:
"Spam is anything the person who's getting it did not solicit, did not consent to. In the context of Bitcoin, that's any data that doesn't involve, in some way, the transfer of coins from one person to another. Everything else is just clogging the network and ruining the experience for everyone else.
People who want to share JPEGs can do that. There are websites for it. There are even decentralized ways to do it, like BitTorrent.
The only reason to do it the way they're doing it — forcing it on-chain — is to intentionally push it onto people who have not consented and explicitly do not want it."
@LukeDashjr on The @_BitcoinMatrix #197
NNMarbas retweeted
Stupid people thinking spammers "running out of money" means spam on bitcoin can never be a long term problem don't understand what Fiat Money is and the true nature of the problem Bitcoin solves.
In the Fiat Money system, the supply of money is INFINITE. That means that any attacker can be supplied with an infinite amount of money long before the effects of that money in the economy cause hyperinflation.
Spammers with their infantile "Use Cases" will continue to come in waves as gullible nincompoops fund them with millions of VC dollars; you will never be rid of stupid people, bitcoin Patrician, so this problem wiil never end barring a technical solution.
There is more than enough money to permanently cripple bitcoin long before a hyperinflation event would be triggered by weaponizing the money supply against bitcoin.
Bitcoin being exposed to an attack like this CANNOT SURVIVE without a technical measure to make spam impossible.
The problem here is the complete mind blind incapability of these broken people to understand the true scope and nature of the Fiat Money problem. They're thinking in a manner that assumes the fiat money supply is finite or in some way limited.
They are not smart. AT ALL.
And finally...the fact that the money supply is infinite was the reason bitcoin was written in the first place. The Spam / Ordinals problem and the fiat money problem are two aspects of the same problem!
NNMarbas retweeted
By repeatedly adjusting default mempool policy to match what miners will accept anyway (large OP_RETURN uncapped because “they’ll just mine it via bypasses like Libre Relay, or direct APIs”), we are implicitly conceding that miner greed + economic incentives are the ultimate rule-setter, not node-enforced principles.
Meaning a (cleverly hidden) capitulation of Bitcoin as a decentralized project.
You could say that the “CENSORSHIP!” argument from Core and their supporters on the concept of nodes filtering is a roundabout way of critizing decentralization itself.
Nodes were always supposed to be the sovereign check, they decide what they accapt and relay.
When we keep loosening policy to align with whatever is the current grift “use case”, and by extension what is short term profitable for miners, it trains the entire ecosystem to treat restrictive node behavior as pointless theater.
Over time this hollows out node sovereignty: running a full node becomes more about passively observing the chain that miners + L2s + data-spammers have already decided on, rather than actively enforcing a monetary-first standard.
As a cuck bonus it also leads to higher resource costs for every honest node (bandwidth, RAM, storage) à fewer independent verifiers in practice
Decentralization starts looking like a performance act. Miners produce the blocks, a handful of relays and L2 sequencers steer the flow, and nodes just… validate after the fact.
It’s not a hard-fork capitulation (consensus rules haven’t changed), but it is a cultural, philosophical and operational one. The most profound capitulation in practice.
The philosophy flips from “Bitcoin should resist non-monetary garbage even if it costs us some short-term fee revenue” to “whatever pays miners gets standardized because resistance is futile.”
Once you accept “miners will do it anyway” as the justification for policy, you’ve already handed the character of Bitcoin over to the highest bidder. Nodes stop being the immune system and start becoming just a polite audience.
The OP_RETURN uncap looks a lot like another quiet step toward a two-tier network (miners + insiders set the tone, everyone else just watches. Keep doing this and running a node risks becoming a branding exercise instead of the actual source and guarantee of Bitcoin’s decentralization.
NNMarbas retweeted
Here is what Satoshi had to say about other use cases outside of money:
"Piling every proof-of-work quorum system in the world into one dataset doesn't scale.
Bitcoin and BitDNS can be used separately. Users shouldn't have to download all of both to use one or the other. BitDNS users may not want to download everything the next several unrelated networks decide to pile in either.
The networks need to have separate fates. BitDNS users might be completely liberal about adding any large data features since relatively few domain registrars are needed, while Bitcoin users might get increasingly tyrannical about limiting the size of the chain so it's easy for lots of users and small devices."
NNMarbas retweeted
Core devs now blocking me on X. Hilarious.
I’ve been completely on the side of core this entire time… AND I am still in support of core development AND I’d like to see the greater community align again - after more carefully understanding the process of reviewing and merging PRs this week it became clear that a mistake was made in changing the default size of the OP_RETURN - which was obviously not a consensus decision.
Even if the opinions of the NACKs were philosophical rather than technical for the most part… one argument that is very valid is that the cost of OP_RETURN storage is 4x the fee of where what some people call “garbage” has landed in witness_data - so there is literally no incentive to use a more expensive trash bin when it is less costly to litter.
The absolutely most ridiculous part of it is that they could just add back the default and it would make no difference to them really but mean the world to hundreds or maybe even thousands of other people.
I opened a PR to suggest it and it got shut down so quickly! Now they are also blocking me on X.
NNMarbas retweeted
This is how decentralized mining at @ocean_mining looks like.
Beautiful.
NNMarbas retweeted
Them: "Filters don't work. Look, we can update our spam every week."
Us: "Look, here's a filter for the spam you designed yesterday."
Them: "Not like that!"
NNMarbas retweeted
Some more signal from Dathon Ohm on GitHub. Beautifully stating the pro-BIP 444 position and laying out why the threat is so grave, and why immediate action is warranted:
NNMarbas retweeted
Some people seem to want to argue that there is already CSAM in Bitcoin's blockchain. This is false. Bitcoin today does not support images at all - only arbitrary data up to 80 bytes (or 95 in the coinbase).
Exploits like "Inscriptions" work by _misinterpreting_ script code, and _bypassing_ existing policy rules. They are not actually storing images, but merely putting gibberish code on the chain, which they later themselves (not Bitcoin) _misinterpret_ as images.
This distinction is very real and relevant. If you don't differentiate between "data that can be misinterpreted to produce CSAM" and "data that correctly interpreted displays CSAM", then literally _all data_ is CSAM, with _no exceptions at all_. This tweet would be CSAM. Google's logo would be CSAM. Your phone's operating system would be CSAM. Literally anything _can_ be misinterpreted as CSAM.
NNMarbas retweeted
Replying to @stephanlivera @kyletorpey
1. Being a long-time contributor doesn't give them the right to remove policies that users want and impose their will. Policy is a user decision, not a dev dictate.
2. Debatable things might or might not propagate, depending on the community's policies. You get to decide for yourself - the problem is when some people (like Core30) try to deny you the option.
2b. If the community as a whole ends up allowing spam through this mechanism, and it kills Bitcoin, there was never anything we could do to save it.
NNMarbas retweeted
OCEAN isn't involved in spam filtering. We leave these decisions with miners, and encourage them to do the right thing.
Knots's default policy has already for years filtered these out, and can adapt if needed.



























