Q1. What was a proposed alternative to Segwit?
A. Rather than changing the transaction structure within a block to make it ‘weigh’ less, the alternative was to increase the block size limit, which was implemented in the hardfork that created Bitcoin Cash.
Q2. What did Segwit solve more than just the scaling issue?
A. Aside from solving Bitcoin’s scaling problem, the initial purpose of Segwit was to address ‘transaction malleability’, where the recipient of a transaction could easily alter the digital signature of a transaction and therefore the hash ID without changing the basic transaction data. By removing the signatures from each block, the Segwit update addressed such fraudulent activitiy.
Q3. How is Segwit and the Lightning network connected?
A. The ‘lightning network’ is Bitcoin’s attempt to build a second layer on the basic blockchain for additional protocols and smart contracts. Segwit aided the development of the lightning network by separating signatures from transaction data, making unconfirmed transactions easier and less risky and thereby improving security for the implementation of smart contracts.
Q4. Are people, wallets and other services forced to use Segwit?
A. The Segwit update was a backwards-compatible softfork. Blocks can still contain signatures in the old way and implementation has been slow but the incentives for wallets using Segwit Support are high.