Segwit Reading Assignment

Blockchain and Bitcoin 101
#1326
  1. Increasing the max block size from 1 mb.
  2. It solves transaction malleability and also supports a second layer solution.
  3. Segwit supports second layer development which is where the lightning network was built.
  4. No, segwit is a soft fork so it is still compatible with the rules from the old protocol.
1 Like
#1327

  1. A proposed alternative to Segwit was a larger block size.

  2. Segwit solved not just the scaling issue, but also the transaction malleability issue because the signatures are stored outside the transaction block.

  3. Segwit supports the development of second layer protocols, like the lightning network.

4.No, this was a soft fork.

1 Like
#1328
  1. What was a proposed alternative to Segwit?
  • Raising the block size to 2Mb
  1. What did Segwit solve more than just the scaling issue?
  • It solved a transaction malleability issue that let an attacker change the TXIdcould. This could be used to commit fraud. This issue also prevented second layer solutions from operating safely.
  1. How is Segwit and the Lightning network connected?
  • LN is relying on unconfirmed transactions and only settling on the main network when user is ready to do so. The segwit fork enabled second layer to be built.
  1. Are people, wallets and other services forced to use Segwit?
  • No, segwit was an soft fork. Non segwit transactions would need to pay a higher fee due to this fact.
1 Like
#1329

Q1. What was a proposed alternative to Segwit?
A proposed alternative to Segwit was to increase the block size from current 1MB. This was however not good solution as the transactions will scale over time and will again need bigger blocks to accommodate more transactions.

Q2. What did Segwit solve more than just the scaling issue?
Segwit also solved transactions malleability issue in which the transaction Id can be maliciously altered resulting in invalid transactions stored on blockchain.

Segwit implemenation made signatures (Segregated Witness) separate from transaction block and thus removed possibility of altering transaction id.

Q3. How is Segwit and the Lightning network connected?
Segwit upgrade enabled development of lightning network, a second layer protocol for improving bitcoin’s scalability by settling smaller and frequent transactions off the bitcoin blockchain before being finally processed by the bitcoin network.

Q4. Are people, wallets and other services forced to use Segwit?
Segwit implementation was a soft fork which was compatible with previous protocol. This means there was no need for forcing upgrade on existing users, wallets, nodes etc.

1 Like
#1330

Ans.1)
To increase in the block size from 1MB to 2MB.
Ans.2)
Segwit solved the second problem with transactions, which is malleability.
Ans.3)
Segwit and the lighting network are both separate second-layer solutions. They operate outside of the block managing data such as signatures, in the case of Segwit, and micropayments, in the case of the lighting network. They offer separate solutions from the transaction data sets stored within the appended blocks.
Ans.4)
No one is forced to use Segwit. This is a soft fork second layer solution therefore both old and new addresses on the bitcoin network are still supported.

1 Like
#1331

1- increase block size
2- transaction malleability
3- Segwit permits second-layer protocols and smart contracts like Lightning network.
4- no

1 Like
#1332

Segwit is an on chain solution, that made second layer solutions like the Lightning network easier and safer to implement :slight_smile:

1 Like
#1333

  1. Simply increasing the block size limit.

  2. In addition to the scaling issue (and the original intention of Segwit), it separated the signatures from the Tx blocks to prevent small changes being made to the signatures that wouldn’t affect the transaction but would change the hash of the transaction (Tx malleability).

  3. Segwit made it possible for the Lightening network to function.

  4. Not forced, it was the soft fork solution to the problem.

1 Like
#1334

  1. The proposed alternative to segwit was to increase blocksize and create a hard fork i.e. Bitcoin cash.

  2. Segwit also solved the malleability problem where users could change the transaction ID and not the transaction itself thus making it possible to be paid twice.

  3. Using segwit and the top layer lightning protocol the the number of transaction processed would go from 7 tx/sec to millions tx/sec or more.

  4. People, miners, and other services had an option to upgrade However, miner who built block and do not upgrade could only build on non-upgraded blocks. After 50% of miners upgrade to segwit then segwit would become the largest block and greater POW. If they took the alternative upgrade to 4MB blocks this would create a hard fork and new currency i.e. Bitcoin cash. Since 2019 it looks like 40% adoption to segwit is the latest info reported. So by 2020 we should have more than 50% adoption.

1 Like
#1335
  1. increase block size- larger block time increases leads to stale blocks and Hard Forks- Hard fork to increase block size- split chain block
    2.Malleability fixed - malleability where details in the transaction could be changed- lowering fees- fit more transactions into a block
  2. Two layer solution above Bitcoin-People, wallets and other services are not forced to use Segwit because it remains compatible with old protocol
  3. No Soft Fork (SF) wallets and other services are not forced to use SegWit- as more wallets embrace Segwit fees will drop, because blocks will contain more txs
1 Like
#1336
  1. What was a proposed alternative to Segwit?
  2. What did Segwit solve more than just the scaling issue?
  3. How is Segwit and the Lightning network connected?
  4. Are people, wallets and other services forced to use Segwit?
  1. Increasing block size which was done by Bitcoin Cash community.
  2. It also fulfilled its original intention of removing a risk of malleability in the transaction.
  3. Segwit is a protocol upgrade that also supports the development of second layer protocol such as lightning network. Lightning network is developed on top of Segwit upgraded base protocol.
  4. No one is forced to use Segwit. But most wallets are integrated to Segwit protocol.
1 Like
#1337

To make the Blocks of the Chain bigger.

It corrects the transaction malleability to make the hole Network more secure.

It allows the second layer protocol development of the lightning Network.

No, they can still be used because it’s a Soft Fork.

1 Like
#1338

1.What was a proposed alternative to Segwit?
Increasing the block size

2.What did Segwit solve more than just the scaling issue?
It solved the issue of tx malleability, so people could build secure smart contracts on top of Bitcoin & second layer protocols

3.How is Segwit and the Lightning network connected?
Segwit made the Lightning network possible by solving the issue of tx malleability (I still don't really know what the lightning network is though, need to read up)

4.Are people, wallets and other services forced to use Segwit?
No, because even though Segwit allows for block weights of up to 4mB legacy nodes will still not have to validate any blocks larger than 1mB, adhering to Bitcoin's original protocol. It was a soft fork.

1 Like
#1339
  1. Increase in block size instead
  2. Segwit solves the security issue caused by transaction malleability as with Segwit adoption, attacker cannot alter tx id by altering signature as it is segregated from base txn data
  3. Segwit paved way for the lightening network by reducing txn size and allowing more txns per block and so millions of txns can be processed per second making it a lightening ntw.
    4.No, not forced but after initial resistance, they are adoption Segwit method. Due to disagreement, hard fork as BCH had also occured
1 Like
#1340

There is a course for that at the academy if you’re interested :wink:

2 Likes
#1341

  1. Bitcoin Cash

  2. The malleability issue

  3. Lightning is a second layer protocol that relies on unconfirmed transactions. It takes frequent, small transactions off-chain until the users are ready.

  4. No one is forced to adopt an update, but if the majority of the network accepts SEGWIT, non-SEGWIT blocks eventually get dropped from the network and SEGWIT becomes the new norm.

1 Like
#1342
  1. Alternative to Segwit that was proposed was increasing the block size from 1MB to 2MB. However, this was disregarded because it did not fully solve the scaling problem. In future as transactions size increased it would mean increasing the block size again.
  2. The Segwit solved the scaling problem and tx malleability. To solve malleability problem, because the tx signature is quite large, it was removed from the tx therefore decreasing the size of transactions.
  3. Segwit and the Lightning network are connected by the transaction malleability fix. Without the transaction malleability fix, transactions on the Lightning network would have been too risky to be practical. It boosted bitcoin’s transaction capacity by taking frequent, small transactions off-chain, and only settling on the bitcoin blockchain when the users are ready.
  4. No people, wallets and other services are not forced to use Segwit. However, since Segwit was a soft fork the old rules on block size applies.
1 Like
#1343
  1. To increase the block size.
  2. The transaction malleability issue, by removing the “witness” information out of the base transaction block.
  3. Segwit introduction allowed an easier path forward for developers to deal with transactions, enabling them to create sub-protocols like the Ligthning network to boost Bitcoin transaction capacity even further.
  4. No.
1 Like
#1344

The majority of the nodes already updated their nodes to recognize segwit rules. This update is more relevant to the wallets to know how to create segwit transactions. But in fact they are not necessary since old style transactions still work. Though they are highly recommended. :slight_smile:

2 Likes
#1345
  1. expending a block size
  2. they also solved transaction malleability issue by removing a signature outside of the block
  3. Segwit proposed a second layer protocols called Lightning network
  4. since it was a soft fork update, all services are still compatible with old protocol
1 Like