- What was a proposed alternative to Segwit? Bitcoin Cash to increase block size
- What did Segwit solve more than just the scaling issue? it solved Tx Malleability by removing sig from hash.
- How is Segwit and the Lightning network connected? SegWit allowed for Lightning network to be built ontop as a layer 2 solution, LN also further boosts btc tx capacity by taking frequent small tx off chain.
- Are people, wallets and other services forced to use Segwit? no
- Increase to the block size
- makes it compatible with previous protocols avoiding need for hard fork and supports development of second layer protocol.
- 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.No as it’s a soft fork
Reading Assignment: Segwit
An increase in block size.
By removing the signature from the transaction data structure, Segwit also solved the transaction malleability issue.
The lightning network makes use of unconfirmed transactions. By removing the transaction malleability issue second layer protocols, like the lightning network, are easier to develop and can operate with more confidence in the unconfirmed transactions they are referencing.
EDIT: Both seek to increase the number of transactions the network can process, Segwit by reducing the size of transaction data and lightning network by moving small, frequent transactions off-chain.
No. Because the change was introduced as a soft fork wallets can still use the legacy implementation.
- What was a proposed alternative to Segwit?
- Increased blocksize from 1mb to 2mb
- What did Segwit solve more than just the scaling issue?
- Segwit also solves Transaction Malleability
- How is Segwit and the Lightning network connected?
- Segwit removes uncertainty by eliminating transaction malleability, which allow 2nd layer solution like LN to build on.
- Are people, wallets and other services forced to use Segwit?
- Segwit is a softfork therefore not enforceable.
[quote=“filip, post:1, topic:8408, full:true”]
It’s time for a reading assignment about Segwit. Read through the following article https://www.coindesk.com/information/what-is-segwit, and answer the following questions.
- What was a proposed alternative to Segwit?
- it was to increase block size , bitcoin cash is an example of an alterntive.
- What did Segwit solve more than just the scaling issue?
- it solves the transection malleability.
- How is Segwit and the Lightning network connected?
because of segwit update it provided layer two solutions which made lightening network possible. - Are people, wallets and other services forced to use Segwit?
- no segwit is a soft fork its still compatible with old rule set .
What change in segwit enabled second layer protocols?
- To increase block size limit.
- Malleability - changing sign script and transaction id after transaction was created
- Segwit is necessary for Lightning network, because it relies on transaction ids.
- They are not, but they will save money if they do.
1.block size increase
2.fixed the malleability issue by removing the signature out of transaction block
3.Segwit made second layer solutions possible like the Lightning network
4.no,it’s a soft fork and thus compatible with the old protocol
-
What was a proposed alternative to Segwit?
Increasing the block size which meant increasing the Megabytes which in turn is a hardfork. -
What did Segwit solve more than just the scaling issue?
solves the TX malleability. -
How is Segwit and the Lightning network connected?
Segwit allows the development of second layer protocols which the Lightning network was created from. -
Are people, wallets and other services forced to use Segwit?
No, services and wallets can still use old protocols
- What was a proposed alternative to Segwit?
It was also proposed to increase the block size of Bitcoin. Bitcoin Cash was a hard fork from Bitcoin that increased the 1 mB size of every block.
- What did Segwit solve more than just the scaling issue?
Transaction malleability. The signature can be changed without changing the hash of the transaction.
- How is Segwit and the Lightning network connected?
Segwit, by solving the transaction malleability issue, allowed the lightning network and other second layer solutions to be possible. This is because the malleability fix made any feature that relied on unconfirmed transactions less risky and easier to design.
- Are people, wallets and other services forced to use Segwit?
No, and that is the reason it was not a hard fork, but a soft fork. Wallets can still create transactions that are compatible with the previous rules (signature inside the transaction and with a limit of 1 mB). With segwit the same limitation of 1 mB for the block applies, but the transaction and the rest of the data cannot overpass 4 mB.
-
The proposed alternative to Segwit was to increase the size of the block from 1MB to 2MB which would lead to the hardfork.
-
It also solved the transaction malleability by storing the signature IDs outside the base transaction block so the more transactions would fit in the same size of the block.
-
Segwit made lightning network possible.
-
No, all the old transactions and addresses known as soft fork can still be used.
- An Increase in block size
- prevented second layer solutions
- made 2nd layer solutions
- no its a soft fork, its optional for now
Your answer seems to contradict with the second answer. Did segwit prevent second layer solutions?
1.What was a proposed alternative to Segwit?
To increase the block size to 2MB.
2.What did Segwit solve more than just the scaling issue?
It solved the tx malleability issue.
3.How is Segwit and the Lightning network connected?
After the release of Segwit it openned space to support second layer protocols and Lightning is one of them.
4.Are people, wallets and other services forced to use Segwit?
No. They have a choice. They can hard fork to solve the issue if they prefer.
They can also still use old style tx on Bitcoin as well
- Increasing the block size above 1mb which would create more centralisation
- SegWit solved Transaction Malleability whilst reducing the TX fees
- SegWit enabled Lightning network (second layer protocol) - combined, the transactions per second increased from 7 to millions per second which is more efficient as BTC achieves mainstream adoption
- Segwit is still compatible with the previous protocol so people, wallets and other services are not forced to use it. Old nodes on the network still exist that do not implement SegWit
- What was a proposed alternative to Segwit?
2mb blocks
- What did Segwit solve more than just the scaling issue?
transaction malleability
- How is Segwit and the Lightning network connected?
Segwit made unconfirmed transactions less risky and lightning payments easier to design
- Are people, wallets and other services forced to use Segwit?
no, it was done a a soft fork, so is compatible with previous protocol
1.Implementing a bigger block size.
2. It also solved the tx malleability issue.
3. Via Second Layer
4. No
- Alternate was Block size of 4 Mb, which was later on remained 1 mb for transaction and signatures are moved to Second layer to increase speed.
- The block size was not increased to 4 Mb which can result in hardfork, and it remained a soft fork which resulted in no change on user wallet side except the Public key address format.
- Both are second layer solution to scale bitcoin transaction.
- No as it was a soft fork.
More importantly than the address format it solved the tx malleability issue.
Segwit is an on chain solution that made second layer solutions like Lightning safer and easier to implement.