SegWit is fine, SegWit discount is the problem! 4MB blocks are not original 1MB design
That’s a broad generalization…
Bitcoin launched in 2009 without an explicit block size limit.
In 2010, Satoshi Nakamoto introduced a hard limit of 1 megabyte (1MB) to the protocol.
The limit was implemented as a security measure to prevent "spam" attacks (where an attacker could flood the network with massive, invalid blocks) and to ensure that running a node remained affordable, keeping the network decentralized.
In 2017, it is true the Segwitt change effectively created a "virtual" block size increase. But the technical limit is 4 million weight units (which theoretically allows for a 4MB block if it contained only witness data), real-world blocks typically land between 1MB and 2MB, depending on the transaction types…
Bitcoin launched in 2009 without an explicit block size limit.
In 2010, Satoshi Nakamoto introduced a hard limit of 1 megabyte (1MB) to the protocol.
The limit was implemented as a security measure to prevent "spam" attacks (where an attacker could flood the network with massive, invalid blocks) and to ensure that running a node remained affordable, keeping the network decentralized.
In 2017, it is true the Segwitt change effectively created a "virtual" block size increase. But the technical limit is 4 million weight units (which theoretically allows for a 4MB block if it contained only witness data), real-world blocks typically land between 1MB and 2MB, depending on the transaction types…
2
