- To increase the size of the blocks.
- It solved the issue of transaction malleability.
- Segwit made second layer solutions possible.
- Old addresses and transactions can still be used.
1 Like
- Increase in block size.
- SegWit solved the issue of malleability, by taking out the signature from the input of the tx, other people couldn’t change the hash of the transaction, therefore the tx id, and still keep the contents of the tx. By taking the signature out of the tx, they also dodged a bullet, by not making a hard fork, and splitting the BTC chain.
3.SegWit, by fixing the malleability, they made any feature that relied on UTXOs less risky.
The lightning network is a second layer of protocol that will boost BTC transaction capacity by taking small transactions off-chain.
4.No, because they made a soft fork.
1 Like
- Larger block sizes
- Segwit allows for the development of second-layer protocols, and smarter smart-contracts
- Segwit allows transactions to be moved off-chain, to be settled and added to the blockchain once the users are ready.
- No.
1 Like
But how did it enable that? Couldn’t this be done just as well on old style transactions?
2 Likes
It does this by removing signatures from transactions. Therefore the signature is no longer factored into he hash, making transaction malleability no longer possible. It also prevented the need for a hard fork.
1 Like
- Large block size
- Fixed txid maleability by separating sign of content tx
- Due segwit was possible to develop Lightning
- No its voluntary, incentivized by lesser fees i think
1 Like
-
By simply Increasing block size.
-
Transaction Malleability. The ability for someone to change information in a transaction ID but not information in the content itself.
-
Segwit allows for developers to create second layer protocols. Thus, the lightning network can run on top of bitcoin and boost transaction capacity.
-
No.
1 Like
- What was a proposed alternative to Segwit?
SegWit (short for Segregated Witness) is a protocol upgrade that changes the way data is stored. SegWit introduced a new concept called “block weight.” This is a squeeze of the block size by eliminating intermediate signatures for each transactions stored in the block. The signature data is capped at 4MB, while the block size limit for the base transactions remains at 1MB. This means that the SegWit upgrade is compatible with the previous protocol, and avoids the need for a hard fork.
However, as alternative to this idea, a simple solution initially appeared to be an increase in block size. Yet that idea turned out to be not simple at all. First, there was no clear agreement as to how much it should be increased by. Some proposals advocated for [2MB], and one wanted to go as high as [32MB] - What did Segwit solve more than just the scaling issue?
While the upgrade enabled a greater number of transactions in [bitcoin’s blocks], SegWit’s initial intention was to fix a bug in the bitcoin code called “transaction malleability”. This flaw allowed anyone to change small details that modified the transaction id (and the subsequent hash) but not the content. While not a critical problem for bitcoin, it prevented the development of more complex features such as second-layer protocols and smart contracts.
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.
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.
3. How are Segwit and the Lightning network connected?
SegWit supports the development of second layer protocols, such as the lightning network. The lightning network further boosts 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?
Not everyone in the bitcoin community agrees that SegWit is the solution bitcoin has been waiting for. Some believe that it is a case of “kicking the can down the road,” and at best a temporary fix. Yet people were never forced to to adhere to the new protocol rules. Those that did not accept those changes branched out and created new crypto. Thus as a result of a resistance to SegWit was one of the factors behind the development of bitcoin cash, a fork of the bitcoin network which chose to implement a larger block size limit rather than rely on a new transaction structure.
As more wallets embraced the upgrade, the percentage of transactions that used the SegWit structure increased, and bitcoin fees dropped as blocks contained a greater number of transactions a result of SegWit.
1 Like
-
Alternatively, it was proposed that one should increase the maximum block size above 1MB, We can see this with Bitcoin Cash (BCH) and its maximum block size of 8MB.
-
SegWit also helped prevent the issue of transaction malleability by removing the digital signature that is inputted in the transaction data structure. By removing this digital signature, the weight of the transaction is massively reduced also allowing more transactions to fit per block, solving the full block issue.
-
SegWit made second layer solutions possible. This solution/ protocol is known as the Lightning network, which speeds up transactions and resolves bitcoins scalability problem.
-
No as SegWit is a soft fork update opposed to a hardfork update, although it does make more sense to pursue the SegWit update.
1 Like
how come the blockchain allow some transaction to run outside segwit without forcing them to go to another fork?
Since hard fork make valid a previous invalid block
soft fork make invalid a previous valid block, how can you still run the old style transaction and still be valid?
cheers
1 Like
1 increase block size
2 malleability
3 SegWit supports the development of second layer protocols, such as the lightning network.
4 no
1 Like
- Increasing the block size limit to include more transactions.
- Transaction malleability, anyone was allowed to make a small change to the signature and alter the TX ID without altering the details.
- SegWit allowed for second layer protocols that rely on unconfirmed transactions.
- SegWit is a soft fork and so you can choose to adopt it.
1 Like
1.)
The proposal was larger blocks, but that was not implemented in Bitcoin. But a part of the community / miner disagreed. This led to the Bitcoin Cash hard fork in July 2017.
2.)
Segwit solved the problem with “transaction malleability” vulnerability
3.)
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.
4.)
No it is optional, you can still use the old Bitcoin legacy addresses.
1 Like
- What was a proposed alternative to Segwit?
Block Size increase, which would lead to a hard fork. - What did Segwit solve more than just the scaling issue?
Segwit helps also for second layer solutions and fix transaction malleability. - How is Segwit and the Lightning network connected?
Lightning Network is this second layer Protocol.
That allows small off chain transactions. - Are people, wallets and other services forced to use Segwit? No, its a soft fork update.
1 Like
-
What was a proposed alternative to Segwit?
increasing the block size -
What did Segwit solve more than just the scaling issue?
the transaction malleability issue -
How is Segwit and the Lightning network connected?
Segwit supports layer two protocols, which the lightning network runs on -
Are people, wallets and other services forced to use Segwit?
No, the old blocks can still be processed
1 Like
What was a proposed alternative to Segwit?
Increase block size.
What did Segwit solve more than just the scaling issue?
Transaction Malleability including providing a supporting a second layer solution.
How is Segwit and the Lightning network connected?
Segwit created the second layer solution (Lightning Network).
Are people, wallets and other services forced to use Segwit?
This was a Soft fork so the previous addresses and wallets are valid.
1 Like
-
What was a proposed alternative to Segwit?
Increasing size block -
What did Segwit solve more than just the scaling issue?
As the signature isn’t part of the Hash the issue of Transaction malleability is solved.
-
How is Segwit and the Lightning network connected?
Segwit makes second layer possible -
Are people, wallets and other services forced to use Segwit?
no it’s a soft work , a % of nodes are using the old version of the network
1 Like
-
What was a proposed alternative to Segwit?
The alternative was increasing the blocksize. -
What did Segwit solve more than just the scaling issue?
It also fixed transaction malleability. -
How is Segwit and the Lightning network connected?
Segwit enables further developments such as the lightning network. -
Are people, wallets and other services forced to use Segwit?
No, segwit started as a softfork.
1 Like
- What was a proposed alternative to Segwit?
Increase the size of the block, from 1 MB to 2MB. - What did Segwit solve more than just the scaling issue?
By separating the signatures from the data block, it eliminated transaction Malleability. - How is Segwit and the Lightning network connected? Segwit allows the lightning network by separating the Witness data.
- Are people, wallets and other services forced to use Segwit?
No, legacy nodes are still able to process SegWit Blocks.
1 Like
#1implement a larger block size limit rather than rely on a new transaction structure.
#2 separating data to scale down time layers singther using different transaction
#3lighting network allows nodes to be connected p2p on bitcoin blockchain using a cross platform no exchange necessary
#4no one is forced to us segwit it is a soft fork update making more spaces on blockchain use case.
1 Like