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.

Replies (93)

One way I like to think about it is: Your node allows you to control YOUR experience of using Bitcoin, but it doesn't give any control over the network. So the reason to run a node is really to verify your own transactions, not other people's. But that cuts both ways. A node run by an exchange or a miner can't determine your experience of using or verifying Bitcoin either. However all nodes agree to the consensus rules, so only changes to the consensus rules matter. Otherwise you can just run another client or an old version. And to be honest I'm on the fence about BIP 110 because I feel like a lot of the time it's either framed dishonestly or a lot of supporters don't understand it. But it's BIP 110 which is actually changing OTHER people's experience of Bitcoin, i.e consensus rules, not the other way round.
Yes. However trying to change consensus rules without broad agreement is not a good thing either even if the change itself is positive - I agree with Giacomo here. It must be very hard to change consensus. IMO we should convince people / nodes to change their relay policy back to 80 cap on op_return and to solo mine with ocean defining their own block (at a cost in terms of expected profit and loss) as decentralized mining is very important too.
Monero got rid of that shit un une instance, simply because it absolutely prioritises money use case over everything else.
Exactly. Mordinals lasted like what, two weeks, before a node update was sent out, rejecting them from being relayed by the default software. Sure, I guess you could make your own fork of the software that would relay them, but it wouldn't help because no other relay would accept it and it would never reach a miner. And even if it did reach a minor, it would not be mined because it wouldn't be accepted by the rest of the network as being valid.
Default avatar
SchwurBler 8 months ago
What would the architecture of this even look like? 10k full nodes, so 10PB of HDDs? Or all pruned nodes? Maybe 10k front ends + one full or pruned backend? Are the 10k IPs individual VMs? Is faking 10k nodes actually as trivial and cheap to pull of as you say?
On one side we have core which has been corrupted. On the other side we have wall street trying to turn Bitcoin into an inter-broker settlements asset. I feel like I've wasted over a decade of my life.
Dude haven’t you been in bitcoin for awhile? This post makes it sound like you never understood the value prop that was still very clearly explained when I started paying attention to the space. Bitcoin’s value comes from the fact that (1) it can’t be diluted. 21M. And (2) I can easily run a node to verify bitcoin sent to me and broadcast bitcoin I want to spend without any intermediary. Nothing you’ve just complained about has to do with that. And I’m not sure if you are misunderstanding op_return or what but can you explain how the recent change affects bandwidth, ram, or storage for noderunners? I know for a fact the block size limit prevents storage concerns but open to your opinion on bandwidth and ram, though I’m fairly confident the impact there is trivial.
Default avatar
SchwurBler 8 months ago
But what would be the point? The miner wastes 500k on adding a bunch of, as you say, low value nodes to the network? What would they relay? Blocks with large op_returns? Assuming BIP110 nodes are 10% of the network and the miner has added 10% to the total of relay nodes, the added nodes are basically doing what 90% of nodes were doing before. The added nodes would be even more pointless than the BIP110 nodes. I would really like to understand your angle here and if this could be a threat to Bitcoin in some way.
Oliveira's avatar
Oliveira 8 months ago
Very well said. I’ve come to believe that #Bitcoin is no longer fighting a technical battle… that’s settled; it works. It’s also not fighting a financial battle. As much as everyone hates it, the fact that the suits are here proves that battle is won too. The only important war still raging, and I believe it’s eternal, is over Bitcoin’s philosophy, its soul. That this war is currently fought so viciously is not a bug but a feature. It shows Bitcoin is still alive and well. No actor in the space, no miner, no BIP, no other authority, will lead the way here. Every node on the network is responsible for what they want Bitcoin to be. Act accordingly, whatever that means for you. The results will punish or reward our actions.
Default avatar
nicodemus 8 months ago
Solid points. Thank you for the rational thinking!
You have much to learn. 1) The supply of Bitcoin can easily be diluted with wrappers and paper claims off chain. Past cycle is evident for this. 2) The spam issue raises the bar for new participants bc it’s more difficult to do an IDB (4GB of RAM HW no longer works), you need 8-12 at minimum. The same problem is here for old participants who need to make a fresh sync of the blockchain due to critical errors, or changing hardware. 3) the Blocksize limit doesn’t prevent storage concerns, see below image for details. image
Economic incentives can become mal-incentives. Once a mal-incentive exists long enough, entire industries start depending on it. At that point fixing the problem threatens the people profiting from the distortion. The incentive system becomes self-defending. I hope you can see the irony. If you don’t, I can give you some real live examples to prove incentive can be co-opted just as easily and then be turned on its head. See Goodheart’s Law for reference. And substitute “the measures” for “miner revenue”, “security budget” or whatever made up metric you like to justify miners mining spam.
> BIP 110 which is actually changing OTHER people's experience of Bitcoin Yes, if you’re using Bitcoin as money it will actually *improve* your experience. If you’re using it for something else, it will degrade your experience. Simple as that. The question we need to answer is do we want other uses for Bitcoin besides money. My answer is a clear NO and my node reflects this answer.
1) isn’t related to OP but agree paper bitcoin = bad 2 & 3) again, blocksize limit. Are you suggesting that blocks should be smaller?
You are right ; we should continue. 20% of knots and 20% core 30 so 80 pct network running 80 capped op_return. I would have preferred consensus to have capped op_return but the conservativeness in changing consensus is very important too (and, less so but also, the simplicity of consensus rules) I disagree with changes implemented in relay policy by core. I believe it is reckless and arrogant. core has too much influence on the network through this type of changes I agree. But I am also happy that core can’t change consensus rules too easily. I also want home solo mining to increase and I believe it will and we should aim for as much as possible designing own blocks through ocean Then for BIP-110 itself I understand the motivation, the frustration etc, I am hesitating but it might be (at this stage at least) a bad precedent if it were to succeed and if does not reinforce core
Time Chain's avatar
Time Chain 8 months ago
All facts. Nodes must run the show. BIP-110 brings that back into alignment.
You’re missing the point. Models suggest that even if 99.9% of nodes run restricted policy, a toxic op_return and a motivated attacker will still find a way to embed a large file on the network. Core 30 changed everything. Prior to it was possible to limit this attack vector with stricter policy. Consensus change is the only mitigation right now. That’s why it’s more important than ever to realise the risk associated with compromised dev team. We should stop pretending consensus is effective defence against human governance. It’s good enough, but not a painkiller.
I don’t understand why core 30 changed that. Even before core 30 a motivated attacker could (one of the arguments of core for changing) and it was indeed a situation where 99.9 pct of nodes were a running restrictive relay policy. And if you believe that most nodes having a restrictive or relax relay policy does not matter you can’t be mad at core 30 for changing that. So my position is : “I wish consensus rules were different but they are the way they are and changing them is not not-costly and should be done carefully” and “I wish core did not change relay policy rule let’s continue to try to gather consensus first on this”
You suddenly think you were neutral? Let me refresh your short memory. How did spreading misinformation feel? BIP 110 is a soft fork. But you gladly amplified the false hitpeace propaganda. image So while you are saying "you are free to run anything" which is true and people can't be stopped to have their free choice and run anything, you are actively being against Knots. That is not neutral.
I never stated I was “neutral.” I asked you to explain how I am “corrupt.” Still waiting. Also, when I posted about the hard fork potential that was a looooong time before BIP110 was even proposed. At the time, everyone said there would be no fork whatsoever, because knots filters would solve spam. Looks like that was false.
And Bitcoin Knots itself has nothing to do with a hard fork. Corruption can have different direct and also indirect effects. Whether you choose not to say a word against David Bailey spammer because of his conferences to which you would like to be invited, whether you choose the side of the comrpomised Core because some of them are your friends, whether you choose not to speak about Citrea because of the investors like Jameson Lopp or Peter Thiel or others ... There is a reason of each action and there is a root cause.
You position yourself where you are with your own choice, voice and actions. Everyone positions themselves where they are. Bitcoiners have their own opinions and their own points of view. Bitcoiners felt something was not right with Core and started asking themselves Why are Core doing this? Why are Core censoring Bitcoin contributers for mentioning Citrea? Why do Core's arguments make no sense? That is why they did it and because of that 23% of the Bitcoin nodes are running Knots. So what I am saying it is that I am not making you anything. I just get the information coming from you which reveals to me your position.
DPR's avatar
DPR 8 months ago
These aren’t serious people, Walker. I muted all the BIP110 Knotzis weeks ago and haven’t looked back — not worth the time. Running core 29.2 until this whole thing blows over 🤷‍♂️
Desert Dave's avatar
Desert Dave 8 months ago
I'm not worried at all. If you don't want to see what's happening, that's okay.
indeed, forming consensus is profound. so just do that. run your node, explain why it serves your interests, and persuade others. all other behavior rightfully belongs to the category “kardashian drama”
Bitcoin Knots is stopping spam to enter my mempool. I don't relay spam. Many people use Bitcoin as money. And their number will grow. image
Filters are a quicker and more dynamic way for the nodes, including miners, to stop unwanted data. it's a tool of the whole network. If a fewminers disregard and decide that they will just mine those txs, then 1-the spammers incur in a cost, they loose the censorship resistance of the p2p network, it centralized service and pay a premium to the miners. 2-if this is considered harmful by a majority of the network, and miners are not following the gentlemans agreement, then the only choice is to force them by consensus, it's not by making their choices more widespread.
My node does not relay spam transactions. My zaps are turned on. I receive zaps and I zap people. Not sure why you need to lie about this?
Desert Dave's avatar
Desert Dave 8 months ago
Just trying to help you out. I'm not the one with platform to lose. No one gives a fuck what I think. This is not going to end well for you and other core apologists.
What I didn't see in your philosophy is the part of the truth and the part of taking informed decisions. Many Coretards do not have good understanding of Bitcoin and just trust the compromised Core devs or some influencers who spread misinformation. Their decisions are not in their own interest. They are tricked to act in the shitcoiners VCs interests. Other than that I agree.
Its up to you to consider the effect of the propaganda in the consensus formation. I do consider it.
"people who don't believe in allowing child porn on the chain are attempting to stir trouble" Lol because somehow stirring trouble is worse than supporting pedophilia
Heyla's avatar
Heyla 8 months ago
But... You are most : man, richs, withes, obsessed by money, sexists, and do "crypto sectarism" and "techno sectarism" and spam Nostr with that, it's not just a river under gain, it's a cyclone of dirty content (And you Know what ? There are no spam on the fediverse and they donc claim monaie, don't exclude poeple when they can't pays)
Young Neal: “I just want my transactions to be secure and decentralized, and am not willing to trade that off for anything.” But @walker is actively weakening #bitcoin Then you lose me, and I’m just a humble pleb mind you…you feel like one can’t speak up because of why?
some people tear down themselves via their actions and their misinformation or illogical arguments, for example the compromised Core
Don’t worry, you’re not the only one who doesn’t see what actually changed. Before that release, about 99.9% of the network - both Bitcoin Core and Knots - were running policy that effectively capped OP_RETURN at around 83 bytes or less. Data storage was not considered a supported use case. Technically possible, but clearly outside the intended design. Anyone determined to do it had to hack their way in through non-standard transactions. That mattered, because when something is possible but non-standard, the network is implicitly signaling: this isn’t what Bitcoin is for. The legal and moral hazard for node operators stayed minimal, basically zero, because these transactions were extremely rare and the ecosystem broadly agreed that Bitcoin wasn’t meant to host arbitrary data. Then the default implementation used by 95%+ of the network changed the policy. That flipped the script. Bitcoin went from being a monetary network that merely tolerated rare data embeddings to a system that is effectively agnostic about what data gets stored in transactions. Suddenly you could insert arbitrary data in a standard, non-contiguous way through the official channel. No hacks required. Just follow the default settings. That’s a profound shift. For sixteen years the norm was: Bitcoin was for monetary transactions, and anything else lived on the margins. With this change, the default stance quietly moved toward content neutrality. Bitcoin becomes not just money infrastructure, but a general-purpose data carrier. That philosophical pivot has consequences far beyond technical policy. It introduces legal exposure, moral questions for node operators, and a very different set of incentives around blockspace. Once the default policy changes at the reference client level, you can’t realistically mitigate the effect with local node policy alone. The coordination gravity of the default implementation is too strong. If the network wants to close that gap, the only durable path is tightening the rules at the consensus layer, because that’s where the highest level of network coordination actually happens.
The only “top-down authoritarian incentives” in Bitcoin are the ones created by Core maintainers (5 people) who can apparently make arbitrary code changes to the default implementation without network wide agreement. You’re asking what spam? Are you unable to define what is spam (therefore you’re retarded) or are simply new to this topic?
2 & 3) blocks don’t need to be full for Bitcoin to function as intended. So any additional storage used for non-monetary purposes is simply a burden on the network. Storage optimization should be the obvious default. UTXO bloat is different, and it impacts the network in two concrete ways. First, it increases the amount of RAM a fully validating node must keep available, since the UTXO set has to live in memory for efficient validation. Second, it lengthens the time required to complete an IBD, because every historical transaction must still be validated against that expanding state. Personally, I think blocks should be smaller, but that’s beside the point here. Block size is a physical constraint, not an optimization mechanism. It limits throughput, it doesn’t decide what should occupy that space. Even with smaller blocks, you can still end up with blocks packed full of spam. That pushes monetary transactions into the backlog and raises the cost of getting them confirmed. The constraint alone doesn’t guarantee the space is used for the purpose Bitcoin was built for. It only guarantees that competition for that space becomes more expensive. As we’ve seen, fees don’t outprice spam. image
1. 5 is better than 1 2. I didn't appreciate the change in v30 either and haven't upgraded. Doesn't make Knotzis any better or a suitable alternative. 3. Spam isn't a problem. I know this because I am not new and seen when there was issues.
Filters would have solved spam eventually if Core didn’t release v30. That’s when and why a soft fork was drafted. You’re a complete imbecile not worth replying to, but here we are because you have a lot of readers/listeners.
Do you remember the slogan “fix the filters”? The wording wasn’t random. It was a direct appeal to the maintainers to repair the broken filters that used to block most of the spam. Instead, the broken filters were left untouched and some of the ones that actually worked were removed (OP_Return). At the moment, the only filters that behave the way they were originally intended are the Knots filters, and they’re running on roughly 22% of the network. That’s the backdrop for why BIP-110 was drafted. If that basic chain of cause and effect is still unclear to you, the problem isn’t the argument. It’s your ability to follow it. Your homeschooling apparently skipped the part about adversarial thinking. Right now it’s just hot air under pressure.
This is the nirvana falacy that is so often repeated by core worshiping sycophants. You are stuck on this idea that if something isn't 100% perfect then it's completely worthless. Ok now try to follow along here, this is an analogy that you seem incapable of understanding but I'll try anyway: if you have a lock on your door but a burglar breaks in through the window, this doesn't mean the lock is useless. btw if you have an issue with being called a core worshiping sycophant you should re listen to your episodes with Lopp and Michael Tidwell from last September for two particularly egregious examples.
DPR's avatar
DPR 8 months ago
Great news is I don’t have to upgrade anytime soon and neither does anyone else. Knots isn’t convincing to me from a SDLC opsec/governance perspective, but I’m open to running another node implementation in the future if it’s up to snuff.
Not here to convince you of anything. Your v29.2 isn’t helping because since v25 the policy heuristics have been manually and quietly altered to justify the drift toward turning Bitcoin into a data dumpster like Ethereum. Your node is signaling to the network that, as far it’s concerned, this is the sanctioned, acceptable state of affairs. The only real point of division now is the OP_RETURN rate limit, which is merely the final nail in the coffin on the road to Bitcoin turning into Bithereum.
the point is, just bc it's a consensus change it doesn't have to be a HF, even though imo HFs are technically cleaner, but there are other reasons to go SF way. It's not Knots being wrong on filters, filters are in previous versions of Core and they have a reason to exist and they do the job they are supposed to do.
My point was that bitcoin should still function as intended even if blocks are full. If it doesn’t, we need smaller blocks. Look I see your point that spam is a strain on the network and I agree, but this is in an environment where fees are less than 1 sat/vbyte. It’s not surprising fees aren’t outpricing spam. Censorship of the network is a short sighted solution to a problem that was already solved in the design of the protocol with fee market & blocksize limit. If bitcoin becomes a valuable monetary network the market will solve the spam problem naturally.
Framing what you disagree with, or is not important to you, as "drama" poisons the well and basically ends any hope for an honest debate. This has been a key part of the core playbook from the start.
Can you clarify what you meant when you said: all other behavior rightfully belongs to the category “kardashian drama”? In particular what are some examples of the "other behavior" you mentioned?
> Censorship of the network is a short sighted solution to a problem that was already solved in the design of the protocol with fee market & blocksize limit. - it’s not censorship, filters enforce rate limits, not content moderation. they have always worked like that and never been called censorship until core propagandists and spam apologists started spinning that narrative - fees and Blocksize limit were only part of the spam solution, the rest was handled by policy and thanks to core, policy is now serving the opposite purpose that was originally created for
hey just FYI there are a lot of us running BIP-110 who aren't picking fights with everyone. It can still be the logical move forward even if you don't wanna run knots or associate with knots.
“Can” and “will” are two different things. I do realise a motivated enough spammer can’t be stopped with rate limits, just like a motivated enough burglar can’t be stopped with a fence and an alarm system. Still, the effects of prevention are there, even if not immediately seen. bastiat.org/en/twisatwins.html
Sure it was. If fees were higher people wouldn’t want to bear the cost of spamming on chain. They would use cheaper alternatives
↑