ScarcityMan 🚀 BIP-110

@Bongo_King1 I sympathize with those who are concerned about spam on bitcoin, but I’d invite you to look around and see that you’re in an echo chamber that makes a minority fork (which doesn’t solve the issue) feel like the majority.

Lets get ahead of this. "But it doesn't stop spam." We're not talking about all exploits and steganography. We're talking about limiting the designated pathway for it. "You can just filter at the node level." Not when the very ability to do so is under constant threat of being removed, and also this does nothing whatsoever to stop our archival nodes from carrying it FOREVER. "It's rushed." Then help us find issues. The code is only a few dozen lines: bitcoinknots.org/learn/bip110-c…. You probably know people who can help. "It doesn't do enough." Why would that mean we DON'T activate it? Isn't that an argument for just continuing to work on the problem after activation? "Bitcoin isn't under existential threat." I don't know which was the degree of temperature that matters most, but the frog is boiling. If you're looking for a single event to signal the threat, you won't see it until it's too late to act. "Your node doesn't matter. Only 'economic nodes' matter." Then bitcoin is dead. I'll wear black and cry at the funeral. Will you?

@TronMonGone @SteveSimple @mattkratter @LynAldenContact @Kestrel_23 @ScarcityMan Knots is about to fork off with less support than bcash. Do you think anyone will hang around using an old version knots on bitcoin when this fails? Or that Luke will maintain it if the chain splits? There are way too many unknowns to even think about.

Hard to say. For this fork, I’d have to agree that something is indeed killing me by a thousand cuts, rather than just a background nuisance held in check by the block size limit and fee market. Defining the scale of the problem, in other words. Second I’d have to see what methods of fighting back actually work without breaking much, and weigh those methods relative to my perception of the threat (existential or nuisance or somewhere in between). Can it solve the problem or just move it somewhere else? I’d make sure I’m not putting effort into something that is more performative than functional. And what commitment am I getting into? Can one fork mostly solve the issue, or am I starting a never-ending whack-a-mole process against the problem, while the problem evolves around my attempts, and each attempt comes with potential technical trade-offs such as potentially affecting the prospects of LN Symmetry (a monetary improvement) and so forth? And *precisely* how small do I want to make the spam bucket that doesn’t contribute much to UTXO bloat (op return) while preserving the other spam methods that do? Who knows- the burden of evidence and specifics are on the proponents. Third I’d make sure not to damage the movement with sensationalist marketing. Self-appointed main characters don’t last long in the bitcoin space. “Pass my fork or Bitcoin dies” is unlikely to win, and may set back the movement. The sensationalist marketing and scale of infighting is what led a podcast host to ask me about it, for me to answer, for others to respond to me, and for me to respond to them with a more public position against this specific fork at this specific time. I’d have otherwise remained publicly indifferent at this time (since it’s a young fork and doesn’t mitigate a whole lot). Wasn’t it @giacomozucco who said that the knots movement was growing until this fork killed it, (his words, not mine)? Something like that. You know how many forks are looking to solve problems in bitcoin and have been seeking consensus for years? Welcome to the party. Fourth, I’d weigh it against other development considerations in terms of time-resources spent. How does this compare to making Lightning better via LN Symmetry? How does this compare to preventing some potentially serious exploits via Consensus Cleanup? Etc. Fifth I’d weigh it against other threats. How about governments trying to ID-verify everything at the operating system level? The attack on net privacy is about 100x a bigger concern to me than this. It’s a gift for them to have half the bitcoin space fighting over a contentious fork that just mildly rearranges the buckets for where spam goes (and for which some aspects I might even be in favor of) rather than defending against all the ways that Bitcoin’s privacy and usability can and is being attacked. I want to see a flourishing ecosystem of coinjoins, smooth lightning UX, Chaumian ecash, Ark, and whatever else people can build to improvement payments and route around censorship and ubiquitous surveillance. Best thing an enemy can do is get you to focus on paper cuts while they’re swinging their machete.