- What was a proposed alternative to Segwit?
- What did Segwit solve more than just the scaling issue?
- How is Segwit and the Lightning network connected?
- Are people, wallets and other services forced to use Segwit?
A.1. The proposed alternative to Segwit was BitcoinCash. BitcoinCash meant to implement larger block size limit of 8MB in contrast to 4MB solution presented by Segwit. Both attempts aimed to scale Bitcoin adoption by facilitating high-volume transactions quickly.
A.2. Segwit presented a solution that ended up solving two different issues (1) block size scalability and (2) transaction malleability.
Block size scalability became of concern as Tx fees increased and latency issues got worse given the growing demand for Bitcoin Blockchain use i.e. increasing adoption. The issues faced by the limit block size of 1MB were two folded—longer propagation time leading to increasing Stale Blocks.
Transaction malleability was a flaw in the Bitcoin code which allowed users to change the Tx Hash/Tx ID. This would in turn allow users to take advantage by lying that they did not receive a specific payment when in fact they did receive the money. Unfortunately the network was not able to verify the claim because a change has been made in the Tx Hash and there was no record of that attempt.
The Segwit solution was then able to increase the block size limit to 4MB by removing the signature data and store it outside the block.
Quick question: Although, changing Tx signatures did not affect the Tx content, what is the convenience of allowing signatures to be modified? Many thanks.
A.3. Segwit and the Lightning network connect through the second layer solution by facilitating micropayments through faster Tx at reduced costs. This propelled development on other features such as MAST, Schnorr signatures and TumbleBit.
A.4. Miners, Nodes, Wallets and other Bitcoin related products and services are not forced to use Segwit. They can opt to BitcoinCash. Despite the new Tx structure “Witness”, Segwit solutions have been updated by Trezor, Ledger, Electrum, Kraken and beyond. Segwit sought a softfork implementation rather then hardfork as means to keep the community together; by the writing of this assignment BTC marketcap, ₿18,653,637 vs BCH marketcap, ₿179,432. This means that BTC adoption continues growing exponentially in comparison to BCH, although BCH limit block size, 8MB in contrast to BTC limit block size, 4MB.