Segwit Reading Assignment

[LuchoXIV]

1. It was proposed that an increased block size would solve Bitcoin’s long term scaling issues. This alternative, was, in fact used in Bitcoin Cash’s hard fork, but it wasn’t as widely accepted as the Segwit update.

2. Segwit solved the transaction malleability issue, thus adding more security to the network.

3. Segwit makes second layer protocols like Lightning Network possible, by making it safer to use unconfirmed transactions and making future projects easier to design.

4. As with any soft fork, the nodes are not forced to accept the updated code, as the stricter rules still work on the older parts of the network.

[Bryan]

1. What was a proposed alternative to Segwit?

To increase the maximum block size.

2. What did Segwit solve more than just the scaling issue?

The transaction malleability issue where a signature or signatures could be changed in a block, keeping the transaction inputs and outputs the same, thus generating a new tx_id or hash for the block.

3. How is Segwit and the Lightning network connected?

Another big step forward made possible by SegWit is that it supports the development of second layer protocols, such as the lightning network. The malleability fix made any feature that relied on unconfirmed transactions less risky and easier to design.

The lightning network will further boost bitcoin’s transaction capacity by taking frequent, small transactions off-chain, only settling on the bitcoin blockchain when the users are ready

4. Are people, wallets and other services forced to use Segwit?

No it was a soft fork.

[FreeBird81]

1. Bitcoin Cash

2. It solved Tx Malleability

3. The lightening network will boost bitcoins transaction capacity by taking frequent, small Tx off chain and only settling on the bitcoin blockchain when users are ready.

4. No it was a soft fork.

[LuizCyriloA]

1 Increate the block size
2 The Transaction Malleability
3 Segwit handles second layer protocol (lightning network)
4 No

[kryptoJr]

• 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?

1. The alternative to segwit was increasing the block size limit to 2mb.

2. Segwit also solved the transaction malleability issue of being able to change the transaction id.

3. Segwit is connected through lighting network because it fixed the malleability issue. Second layer protocols were able to be implemented with less risk.

4. No. It was only a soft fork. However most at moving forward with it.

[charlesleonp]

1. The alternative was to increase the block size.

2, Segwit also solved the transaction malleability issue.

3. SegWit supports the development of the Lightning network, which is a second layer protocol. As SegWit provides a fix to transaction malleability it has made features that relied on unconfirmed transactions less risky and easier to design.

4. Those that remain with the Bitcoin protocol adopted SegWit. Others that adopted a larger block size caused a fork. One of the results was the development of bitcoin cash.

[Brett82]

1. A proposed alternative to segwit was to increase the block size.

2. Segwit also solved TX malleability.

3. Segwit supports the development of 2nd layer protocols such as the lightening network which boosts Bitcoins TX capacity.

4. No one is forced to use Segwit.

[Craft]

1. What was a proposed alternative to Segwit?
Increased centralization, larger nodes for signatures. Furthermore, increased block sizes and a new metric known as block weight.

2. What did Segwit solve more than just the scaling issue?
Segregated Witness [SegWit] can be described as a solution for transaction malleability. However, if the data structure is to large and/ or is not uniform; it will be rejected from the network.

3. How is Segwit and the Lightning network connected?
Software a a Service [Saas], in order to accelerate transactions. Additionally a second layer of protocols is introduced. ,

4. Are people, wallets and other services forced to use Segwit?
Negative, SegWit is however a protocol upgrade and is furthermore described as soft fork.

[Mako]

1. Increasing the Block size to 2 MB (and this was adopted by Bitcoin Cash)

2. It solved the transaction malleability which means that slight changes to other than transaction data like cannot affect the transaction ID.

3. They are connected as it Segwith fixes the transaction malleability and has improved on the problem of block size by moving the signature (witness data) out of the block. The lightning network on the other hand further improves by removing small frequent transaction from the block chain and doing a final settlement when either party drops the channel.
   So in effect the connection is both are improvements to solve the transaction block limit of 1 MB and improve the confirmation speeds.

4. No, they are not. However support for Segwit is slowly being incorporated into wallets and other nodes are upgrading. Both are still within 1 MB size block limit.

[Fetih]

1. Increasing the block size
2. The trancations malleability
3. It makes it possible
4. No, because it is a soft fork

[Cryptobearcat]

Increased block sizes

Fixed trx
malleability

Supports second layer protocols ie lightning network

Can still be used (soft fork)

[Earnst]

1. The proposed alternative to the Segwit solution was to increase the size of the block to 2MB

2. It enabled more TXs to be stored in the block as data wasn’t taken up by the inclusion of signatures, which aren’t small. And it removed the risk of TX malleability, as changing the signature would no longer affect the resulting hash the block generates.

3. These are terms used to describe proposed changes to the Bitcoin blockchain. They both resulted in faster and cheaper transactions.

4. No, not at the moment as older transactions can be used as well. It is a soft fork update, meaning it resides within a rule set that also accepts pre-Segwit rules.

[JasonM]

1. What was a proposed alternative to Segwit?
   The proposed alternative was to increase the block size from 1MB to 2MB.

2. What did Segwit solve more than just the scaling issue?
   It also solved the transaction malleability issue…this is the changing of the transaction signature to alter the transaction ID.

3. How is Segwit and the Lightning network connected?
   Segwit supports the development of second layer protocols of which lightning network is one.

4. Are people, wallets and other services forced to use Segwit?
   No one is forced to use Segwit, which is resulting in a slow uptake.

[Corneile]

1. Block Size increase
2. The transaction malleability issue, higher fees and slow speeds
3. Segwit supports second layer solutions which is the lightning network
4. No

[DNenzel]

1. Increasing the block size limit

2. Segwit solved transaction malleability and enabled second layer protocols like Lightning Network

3. The Lightning Network is a second layer Bitcoin protocol

4. No they are not forced to use segwit, it is a soft fork

[MonikaGrabowska]

1. What was a proposed alternative to Segwit?

It was to increase block size which leads to chain split - forks

2. What did Segwit solve more than just the scaling issue?

SegWit fixed transaction malleability by removing the signature information (otherwise known as the “witness” information) and storing it outside the base transaction block. With that, signatures and scripts can be changed without affecting the transaction id.

3. How is Segwit and the Lightning network connected?

SegWit supports the development of second layer protocols, such as the lightning network. The malleability fix made any feature that relied on unconfirmed transactions less risky and easier to design.

4. Are people, wallets and other services forced to use Segwit?

No, they are not force however more and more wallets implement Segwit

[MonikaGrabowska]

1. What was a proposed alternative to Segwit?

It was to increase block size which leads to chain split - forks

2. What did Segwit solve more than just the scaling issue?

SegWit fixed transaction malleability by removing the signature information (otherwise known as the “witness” information) and storing it outside the base transaction block. With that, signatures and scripts can be changed without affecting the transaction id.

3. How is Segwit and the Lightning network connected?

SegWit supports the development of second layer protocols, such as the lightning network. The malleability fix made any feature that relied on unconfirmed transactions less risky and easier to design.

4. Are people, wallets and other services forced to use Segwit?

No, they are not force however more and more wallets implement Segwit

[bigbill]

1. To increase block size
2. The transaction malleability issue
3. It supports the development of second layer protocols, such as the lightning network. The malleability fix made any feature that relied on unconfirmed transactions less risky and easier to design.
4. No, it is a soft fork

[RichJamo]

1. A proposed alternative to Segwit was simply to increase the block size limit (initially to 2mB)

2. Segwit also solved something called transaction malleability - before segwit this opened a door for scammers to get double payment, and it also made it risky to build any apps based on unconfirmed transactions

3. Segwit having solved transaction malleability means that it’s now easier and less risky to design second layer protocols like lightning on top of bitcoin

4. No, they are not forced, but adoption was slowly increasing as of 2018

[ChloeN]

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

2. What did Segwit solve more than just the scaling issue?
   Malleability (ability to change small details that modified the transaction id (and the subsequent hash) but not the content of the transaction.

3. How is Segwit and the Lightning network connected?
   When fixing the malleability, Segwit makes the Lightning network less risky when relying on unconfirmed transactions and easier to design.

4. Are people, wallets and other services forced to use Segwit?
   No