- An increase in block size to 2MB
- It also solved the transaction ID malleability problem.
- Segwit is the foundation for the Lightning network.
- Nobody is forced as Segwit is a soft fork.
- What was a proposed alternative to Segwit?
The increase the block size. - What did Segwit solve more than just the scaling issue?
Solved the TX malleability. - How is Segwit and the Lightning network connected?
Segwit made the 2nd layer solutions possible and the Lightning Network is a “Layer 2” payment protocol. - Are people, wallets and other services forced to use Segwit?
No. As of February 2018, only 14% of transactions were using the new format.
- What was a proposed alternative to Segwit?
To increase the block size.
- What did Segwit solve more than just the scaling issue?
It stops transaction malleability as well.
- How is Segwit and the Lightning network connected?
With SegWit, Bitcoin supports the development of second layer protocols such as the Lightning network.
- Are people, wallets and other services forced to use Segwit?
No.
1- block size increase
2- malleability issues
3- by not including the signature in the block, that makes unconfirmed txs safer
4- no, its an user activation soft fork
[quote=“filip, post:1, topic:8408”]
- What was a proposed alternative to Segwit?
- A proposed alternative to SegWit was increasing the current block size. However, doing this would cause the block to do a hard fork. Hence why we something like Bitcoin Cash
- What did Segwit solve more than just the scaling issue?
- SegWit fixed transaction malleability, lowering fees, and supports the development of second layer protocols such as lightening network, schnorr signatures, etc.
- How is Segwit and the Lightning network connected?
- SegWit supports development of second layer protocols, which allowed the lightening network to develop.
- Are people, wallets and other services forced to use Segwit?
- No it is a choice. SegWit is a soft fork (embedded) on the Bitcoin protocol. Some wallets support it while other do not or are trying to implement it as a choice
-
The proposed alternative was to increase the size of each block. At the end it was done causing the Hard fork, Bitcoin Cash.
-
Also solved the transaction malleability.
-
The implementation of Segwit made possible second layer protocol, like Lightning network.
-
No, the previous transactions can also be made and stored on the block. Although the advantages of Segwit lead to a natural change of wallets and services.
-
The alternative proposed to Segwit was to double the block capacity from one megabyte to two megabytes per block.
-
In addition to the scaling challenge Segwit was able to solve transaction malleability and provide greater security to transactions.
-
Segwit supports second layer protocols such as the Lightning network which provides increased speed and capacity to bitcoin transactions.
-
Those that want to use bitcoin will use Segwit as 95% of the community agreed to this new protocol. Those that prefer the solution to increase the block capacity have created hard forks, which has created other forms of bitcoin currency such as bitcoin cash.
The increase in the block size from 1MB to 2MB, what it was implemented later in the Bitcoin Cash protocol.
2.
The Malleability bug, and also allow to build a second layer for smart contracts and other solutions
3.
As the txID it is in the base layer, the Segwit allows safely to build in a second layer other functionalities.
4.
Just the ones that have been updated, the ones not updated still can transact without Segwit.
-
What was a proposed alternative to Segwit?
A hard fork in the form of an increase in block size. -
What did Segwit solve more than just the scaling issue?
It solved Transaction Malleability, meaning that any changes to a signature info would be separate from the Transaction and result in no changes to the hash of the transaction, ensuring improved security. -
How is Segwit and the Lightning network connected?
Segwit allows for layer two protocols to be implemented to the network now that the Malleability issue has been resolved and transactions are more secure. -
Are people, wallets and other services forced to use Segwit? People, wallets and other services are not forced to use Segwit, as it is a soft fork and various companies, wallets are implementing segwit in their own time.
1- Increase block size
2- Transaction malleability and the potencial to integrate second layer protocols-
3- Segwit allowed the bitcoin blockchain to have a second layer protocol- like lightning network
4-No, this was a soft fork.
Increase in block size
segwit solves for tx malleability
Supports a second layer solution
No it is a soft formk.
- Increase block size to 4mb.
- Transaction malleability, lower fees, and support for a second layer.
- Lightning network is a second layer that builds on Segwit.
- No, because Segwit is compatible with old protocol.
- Increase the block.
2)transaction malleability
3)It made lightning network possible
- No it is a softfork, old addresses can still be used
- What was a proposed alternative to Segwit?
Increased block size limit. Bitcoin Cash was created for those that wanted to go in this route instead of Segwit. - What did Segwit solve more than just the scaling issue?
Fixed transaction malleability. Altering the digital signature no longer changes the hash of the Tx and allows smart contracts/processes that rely on unconfirmed Tx to be less risky/easier to design. - How is Segwit and the Lightning network connected?
Segwit allowed for the creation of lightning network. - Are people, wallets and other services forced to use Segwit?
No, but since Segwit is a soft fork, they will be affected by it.
- Bitcoin Core with increased block size
- Transaction malleability
- Segwit allows other protocols work in another layer one of them is lightning.
- Users are not obliged but we saw a lot of adoption to Segwit
- What was a proposed alternative to Segwit?
A blocksize increase to 2MB. This requires a hardfork and was done resulting in the Bitcoin Cash fork.
- What did Segwit solve more than just the scaling issue?
Transaction malleability, making a change in the signature resulted in a change in the transaction data and thus a change in the hash.
- How is Segwit and the Lightning network connected?
Segwit solves transaction malleability which made the design of lightning easier and less risky by relying on unconfirmed transactions.
- Are people, wallets and other services forced to use Segwit?
No, it’s a soft-fork
-
A proposed alternative to segwit was to make the block size bigger.
-
One of the other problems segwit solved was the transaction malleability.
-
Segwit and lightning network is connected because it supports the development of second layer protocols.
-
No, because it is a soft fork and still has the same rules before the update.
- To increase the block size to 4MB
- The transaction malleability issue, being able to change the signature after the hash.
- Segwit allows second layer protocols like the lighting network. It in solving the malleability flaw makes it possible to to small transactions off chain.
- No, it is backward compatible. This also makes it a softfork.
-
One solution was to increase block size. But that would only be a temporary solution since capacity would eventually reach the new increased block size.
-
Segwit also solved an issue of malleability. With the scrip signature removed from the block, someone can no longer change it.
-
Lightening network is a protocol that is able to work with the Segwit update.
-
Not everyone has to use Segwit because it it a softfork.
1, An increase in block size. BCH was a result.
2, transaction malleability, lower fees & 2nd layer solutions support.
3, Segwit has made second layer solutions less risky such as lightning.
4, No. They have a choice but over time more and more are adopting its use.