Segwit Reading Assignment – Questions
1. What was a proposed alternative to Segwit?
Increasing the blockchain’s block size limit to 2 MB (i.e Bitcoin Cash), which would have been a short-term quick fix to the problem of higher fees and longer confirmation/processing times imposed on users (due to block sizes being limited to 1 MB).
2. What did Segwit solve more than just the scaling issue?
The Segwith hard fork solution was also able to solve the transaction (TX) malleability problem, whereby users on the receiving end of transactions would be able to modify a transaction ID’s hash value (altering the signature or scripsig, which, if stored within a transaction’s data structure, would impact its hash value directly). Doing so would enable them to claim never having a particular transaction, therefore potentially duping/tricking senders from sending the same transaction/payment/transfer a second time.
3. How are Segwit and the Lightning network connected?
Segwit supports the Bitcoin network’s second layer solution, which is the Lightning Network itself.
Additionally, Segwit enabled the implementation of MAST, Schnorr signatures and Tumblebit
4. Are people, wallets, and other services forced to use Segwit?
No, as it was implemented as a soft fork.