Damus
Jah · 3w
Maybe nostr:nevent1qqs9hzs60yepgypayqrh8znt7fndvjkky7tdjxnfay5dhgplu8rv84gzyz0gkucuv7ddsu3q8szaekx6mel9twrmvhtxndd92e7rzz27kg2rjqcyqqqqqqg2s04ps
mleku profile picture
the longer a broken bone sits in the wrong alignment the more harmful it becomes later on. the damage that was caused by taproot, empowered by leveraging segwit, is severe. the nearly 2 year long running manias in shitcoinery to flood bitcoin blocks with pixel monkeys did a lot of harm to the chain, to lightning and to large settlement transfers. it's only a question of catalysts that can cause it to happen again, the spammers just get bored and have manias in random turns.

if you have a bucket, and there is one big crack up high, and a small one down below, which one is the most important to fix? the lower one. the one that will keep leaking and is easiest to fix (smaller). the big ones up high (non-consensus, mempool) are not as critical as the hole that lets those keep on getting baked into blocks (one crack segwit, and then crossing that and widening it, taproot).
2
Jah · 3w
Sorry but I am not following you... you are saying removal/redesign of sewgwit is an easy fix? I get “more important”. but bip110 will be running in one month, and meanwhile I believe this has created enough awareness for the greater problem so it can be addressed, and (hopefully) properly fixed...
Tauri | BIP-110 · 3w
You might be right but this sounds as much more serious consensus change that will require much more time and effort to gather support. Think about BIP-110 as putting a duck tape on the lower crack in the bucket instead of a fix of the higher crack. Not perfect, but good enough to give the community...