In hindsight, wasn’t Taproot a hostile fork? 1. Over 5 years later, hardly anyone uses it, except spammers. No major product market fit yet. 2. It was a “nice to have”, wasn’t a response to a threat (debatably like segwit was). 3. It ratcheted up the spam problem, which creates another problem now with another possible fork. If you supported Taproot, then what did you get wrong, such that you supported a hostile fork? Do you apologize? Before you get to anything else, it thinks it’s important that you ask yourself those two questions, then reflect on the answers.

Replies (27)

Default avatar
Jacob 1 month ago
AFAIK no one suspected Taproot to create this problem. This is from Luke in a debate. The problem was the city current core devs stopped fighting spam. But this should be a lesson of more careful development.
The consequence now is we have a modest amount of chain growth. Hardly worth bunching panties over. The biggest threat facing Bitcoin is a sustain spam attack on the utxo set that quickly increases the ram requirement to a point past 16gb. The retarded JPEGs guard against this ironically.
Op return limits are not a rule they are a setting. 110 is a rule change and it puts bitcoin at an existential risk for state capture.
Spam in the form of a larger witness data transaction means there is less room for dozens of small utxo spam transactions and it cost some modest growth in hard drive required to host a node. Under 110 the cost of attacking the chain with small utxo bloating transactions drops dramatically but worse the time it would take to bloat the utxo set accelerates to an unsustainable level. After activation it would cost around 160 million to spam the chain to the point where in 6 months no nodes with 16gb of ram or less could stay synced. This is a threat. Currently it would cost 10x to do this and it would take an extremely long time because the degenerates like their retarded JPEGs enough to pay 5 grand to put them on chain. TLDR we are being guarded by retards.
They take up blocks making a pure utxo attack more expensive and take way more time to pull off. The ram requirements growing too fast will centralize bitcoin. The hard disk space growing slightly faster will not.
Because the utxo growth only reduces in a post 110 world if you assume spammers don’t use p2sh to continue their trade or that a state actor doesn’t step in to purposefully spam the chain. The fact is spammers keep block space in demand. Monetary users don’t, which leaves us vulnerable to a utxo attack that could happen so quickly all pleb nodes become useless
Then We would have less utxo and hard drive bloat…and almost no demand for blocks which makes a dedicated attack almost a certainty. They don’t have to kill Bitcoin they just have to make it impractical to run a node on consumer hardware. If no one is running nodes except in data centers Bitcoin is captured.
I honestly don’t know, haven’t gamed it out. What I do know is something sold as an emergency fix when there is no emergency and also sold wrapped in morality about csam is how the Feds work. 110 is dishonest and should be rejected. I don’t know if people pushing hard for it are compromised or if they just don’t see the threat. I do think Luke is compromised by his feelings that Bitcoin should not go against the state. He is against privacy tech. I find him disturbing to say the least.
Bob Social, 's avatar
Bob Social, 1 month ago
Core must be ultra-conservative, btc is fine, change nothing until (we) the users and businesses are screaming for it🤔 when ...
JackTheMimic's avatar
JackTheMimic 1 month ago
So, to be clear you're saying it's bad that they make invalid arbitrary sig data so they can never spend their coins? Are Satoshi's coins sitting in over 22,000 different addresses bad? You have to keep those in the UTXO set too.
Bob Social, 's avatar
Bob Social, 1 month ago
when no one is demanding it loudly, it doesn’t belong in the core🔍❗️😯 (*) Stability first, (*) innovation earns its way in, (*) TO PROTECT BTC => core isn’t a playground for "too many ideas" (= it will divide us, this is what bankers want😑😓) => core is the last line of protecting the code and trust👀. (1) Every unnecessary change is an attack on reliability. (2) If the ecosystem isn’t begging for it, don’t touch the core. (3!) Why increasing the possibility to break something good, when we the users (MOST) aren't asking for it?
I mean anything that currently is allowed but would be restricted post activation. Post activation people can use the old and less utxo efficient method of P2sh wrapping to embed data. “Honest” spammers who just want their pictures on chain could choose this method and if they continued doing their spam at similar volume the chain would suffer utxo bloat in excess of the current norm. The issue I see is that in the absence of spam the lack of demand for block space makes a dedicated utxo attack feasible. Even if the attacker bloated the utxo over 2 years it would severely damage node runners. People are complaining about a couple hundred in drive upgrades because of v30…you think they are going to spend thousands for a 32gig machine?
Default avatar
Jacob 1 month ago
Spam is definately an issue. Not now but two years ago main chain was almost dead for economic transaction and full of spam/scam. Im not sure we need bit110 but a reverse to v29.0 with spamfilters would go a long way.
The spam filters that did nothing because miners ignored them? Please be serious for fucks sake.