209 похожих чатов

Could someone briefly summarise the main reasons why Segwit was

such a bad idea?

2 ответов

11 просмотров

1. SegWit took 5000 lines of code for nonsense reasons (to make it a Soft-Fork), when it could probably take like 500 lines and 10x less complexity by just doing a simple, clean hard-fork 2. SegWit was offered as a bait-and-switch type of trap (called a "compromise" back then) with the promise of increasing blocksize to 2MB as long as SegWit goes in. Guess what happened. SegWit went in, broke BTC with insane complexity and 2MB never happened.

3. Because of being a soft-fork, SegWit "lies" to the network that nothing changed, while in reality everything changes. You can still run a pre-segwit Core client from early 2017 and it should theoretically work and the client will perceive as if nothing changed at all, thinking that it can use the network properly. But it cannot. In reality, new changes were introduced in an insidious manner, where the upgraded network keeps lying to any old clients that they can use it. 3a. Because of the above, incredible mess was created where old clients can still theoretically use the network, but in a much less efficient manner (they can only see 1MB of blocksize, not whole ~3.5 MB or whatever), increasing the complexity, problems and fees for the network even more. So basically SegWit opened a whole new attack surface against BTC network. An example of such attack is the Taproot NFT exploits.

Похожие вопросы

Обсуждают сегодня

Карта сайта