not âkicking the can down the roadâ, they allege, by increasing block size (hard fork), e.g. btc cash.
it supported development of second layer protocols like the lightning network, and other core improving features such as MAST, Shnorr, and TumbleBit.
Segwit paved the way for lightning network. made second layer solutions, in general, possible. Bc Segwit solved malleability concern, LN was able to operate securely and off chain, which off loads block weight to LN with less risk.
no, soft fork (network contraction). however, this is the way of the future. but does this mean there are numerous chains operating simultaneous? can a segwit block be linked to a non-segwit block? @filip
The most obvious alternative proposal to Segwit was to increase the block size i.e. 1 MB to 2MB although this was considered by some as ´kicking the can down the road´. It also would be resulted in a hardfork.
What did Segwit solve more than just the scaling issue?
The scaling issue has resulted in increased TX speeds and lower fees. However, Segwit has also resolved a serious TXs malleability bug and made possible the development of a second layer of protocols such as the lightning network
How is Segwit and the Lightning network connected? Network which will
See 2. Segwit allows for the development of the lightning network which will considerably increase transactions speed.
Are people, wallets and other services forced to use Segwit?
Wallets and smaller nodes are not required to use Segwit as it was a softfork and therefore compatible with the older protocol. However, newer wallets and larger nodes have / are implementing the change.
What did Segwit solve more than just the scaling issue?
Fixed the transaction malleability issue by removing the signature from the transactions hash, and allowed for more development for new ideas.
How is Segwit and the Lightning network connected?
By removing the signature from the transaction data, it allowed for the Lightning network to be developed, it is a second layer protocol that allows for much faster transactions.
Are people, wallets and other services forced to use Segwit?
What was a proposed alternative to Segwit?
increasing the size of the block which will lead to a hard fork
What did Segwit solve more than just the scaling issue?
it solves a bug in bitcoin code, tx malleability
How is Segwit and the Lightning network connected?
SegWit is the foundation for the Lightning Network by making it possible to be the second layer network
Are people, wallets and other services forced to use Segwit?
no itâs soft fork so the old TXs still valid and adoption of segwit is increasing since August 2017
What was a proposed alternative to Segwit?
The alternative for Segwit was to have a larger block size limit
What did Segwit solve more than just the scaling issue?
Other than the scaling issue, by removing the signature from the block it freed up a lot of space for more transactions to be stored on the block, which means that bitcoin can process a greater throughput without changing the block size.
How is Segwit and the Lightning network connected?
Lightning network is a second layer protocol that takes small transactions off-chain, only settling on the bitcoin blockchain when the users are ready.
Are people, wallets and other services forced to use Segwit?
The adoption is voluntary, only who wishes to use Segwit adhered to it.
1 the propose alternative to segwit was increasing the size fo the block grader than 1MB
2.also solve the transaction malleability and lower fees
3.Segwit support the lighting network which is the second layer of the solution
4.NO because is a soft fork but wallet and are implemented segwit support
The alternative to SegWit was the increase of the block size. That approach was taken by Bitcoin Cash for example. W.nkâŚs!
Segwit solves not only the scaling issue, but also prevent transaction malleability.
By fixing the transaction malleability, SegWit made the network and the unconfirmed transaction, in particular, less risky which allowed the development of second-layer solutions such as Lightning Network.
No one is forced to use SegWit as it is a Soft Fork, however, is recommended so all can contribute to the improvement of the network.
The alternative proposed was a larger block size, which created a fork with Bitcoin Cash
It also solved malleability, also made possible to do second layer on top of the network
Lightning network uses segwit taking smaller transactions off chain and getting them back on chain when needed
No, they are not forced to use segwit
A proposed alternative to Segwit was an increase in block size.
aside from the scaling issue, segwit also addressed transaction malleability which allowed someone to change the transaction id.
Segwit allowed for the development of second layer protocols such as lighting network, which further boosted bitcoinâs transaction capacity by taking small transactions off-chain.
No, segwit is a soft fork so people, wallets, and other devices are not forced to use the segwit protocol however more and more wallets are adding support for its clear advantages and is currently at 66% adoption as of Jan 2020.
As Bitcoin grew in popularity, transactions increasingly reached the 1MB block limit leading to higher fees and longer confirmation times. The first proposal was to simply increase the block limit, but critics felt that such an increase was the equivalent of âkicking the can down the roadâ rather than actually fixing the problem. Thus, SegWit (or Segregated Witness) was proposed.
SegWit solved two problems: the block limit and transaction malleability. However, SegWit led the way for second-layer protocols like the Lightning network, MAST, TumbleBit, and Schorr signatures.
SegWit and the Lightning network are connected in that they have the same objective: faster transactions. However, SegWit and Lightning achieve this in different ways. SegWit reduces the excess âweightâ of transactions by removing their signatures. On the other hand, Lightning takes small transactionsâknown as micropaymentsâoff the blockchain entirely.
No, no one is obligated to use SegWit. SegWit was a soft fork, thus backward compatible. The updated protocol abbreviated the locking script to distinguish SegWit from non-SegWit transactions.
1. What was a proposed alternative to Segwit?
Increasing the block size
2. What did Segwit solve more than just the scaling issue?
Tx malleability
3. How is Segwit and the Lightning network connected?
The lightning network makes unconfirmed transactions possible with segwit. All the small transactions are not on the chain but will be there when the transactions are confirmed. This will make transactions faster
4. Are people, wallets and other services forced to use Segwit?
No, they can continue on a different chain. Without the use of the update
Both of these are true in fact, but Lightning network wouldnât be possible without segwit(or at least more risky to implement) since it relies on unconfirmed transactions and these are dangerous because of the malleability problem that allows a malicious party to change the txid