-
What was a proposed alternative to Segwit?
Make the blocks size bigger to let the block be filled with more transactions -
What did Segwit solve more than just the scaling issue?
The transacction malleability for most and set the layer like lightning. -
How is Segwit and the Lightning network connected?
Segwit makes second layer possible -
Are people, wallets and other services forced to use Segwit?
No. Old transactions can be used as well.
Assignment on Segwit
- What was a proposed alternative to Segwit?
A hardfork of increasing block size to 2mb, which Bitcoin Cash adopts. - What did Segwit solve more than just the scaling issue?
Segwit also fixed transaction malleability, which allows develop to update on signature and script. It also enables MAST, Schnorr signatures, and TumbleBit possible to be develop on bitcoin mainnet - How is Segwit and the Lightning network connected?
Segwit makes second layer possible. So sidechain like lightning network and liquid network can be made in Bitcoin - Are people, wallets and other services forced to use Segwit?
Not forced, it is a softfork so old addresses and transactions can be used normally.
**What was a proposed alternative to Segwit?**
increasing the actual size of the blocks.
What did Segwit solve more than just the scaling issue?
TX malleability and the ability of someone to alter a sig.
**How is Segwit and the Lightning network connected?**
Lightening network takes frequent, small transactions off-chain, w/ this second layer protocol
Are people, wallets and other services forced to use Segwit?
No not forced. In fact btc cash created a hard fork because of the resistance to move to a change in the structure.
You can also still use old style transactions on Bitcoin
1. What was a proposed alternative to Segwit?
- Increase the block size. The solution of increasing the block size led to the BTC cash hard fork.
2. What did Segwit solve more than just the scaling issue? - Segwit actually borned as a solution for TX malleability, the solution it fit as well the block size issue.
3. How is Segwit and the Lightning network connected?
3.Segwit allow the second layer solution making lightning network possible.
4. Are people, wallets and other services forced to use Segwit? - No they are not force to, at the time of the assignment even big platform such Coinbase weren’t prepared. By now I don’t really know if anyone is still storing is ID into the transaction.
- an increase to block size 1mB -> 2mB
- security issue called TX malleability
- The implementation of the Lightning network was possible because of the Segwit update.
- No, everyone can update when they wish.
Those who opposed Segwit and had proposed alternate which was to increase the BTC block size.
By removing Signature from the transaction ID from block itself, it creating more secure 2nd layer capability.
Adoption of Segwit upgrade has secured BTC protocol malleability problem to the point that Lighting network has a potential of building on top of BTC network.
Since Segwit is part of upgrade all wallets and other such services must upgrade aswell or users will be forced to use other service to use new features and pay less in fees.
- SegWit2x
- Transaction malleablity: the possibility of altering the transaction ID before the original transaction was confirmed
- SegWit makes the development of 2nd layer solutions like Lighting Network possible. Preventing transaction malleability is necessary to maintain authenticity of lighting network transactions.
- No one is forced to use SegWit, but, just like any network effect, the more that use it, the more will adopt it.
Segwit is not forced. You can still create old style transactions on Bitcoin and get away with it You will pay more for the fees since Segwit transactions take up less space in a block
Segwit2x was a different thing and it happened later after Segwit was already activated. I forgot exactly what was it about.
The other alternative was to just increase the block size
- The alternative was to increase the block size (bitcoin Cash)
- Beyond the scaling problem, SegWit resolved the transaction malleability issue by removing the signature from the transaction hash.
- SegWit allows for more functionality, including second layer (layer 2) solutions such as lightning network which is a side change that settles transaction on the block chain once the transactions/users are ready.
- It is not mandatory to use SegWit and adoption has clearly taken time, but it is backwards compatible therefore all transaction are fine (Segwit and non-SegWit transactions)
-
What was a proposed alternative to Segwit?
-block size increase like a hard fork update (eg:bitcoin cash) -
What did Segwit solve more than just the scaling issue?
-transaction malleability via deployment of lightning network and decrease in transaction fees -
How is Segwit and the Lightning network connected?
-help to avoid transaction malleability via segregation of digital signatures and 2nd layer protocol with lightning network -
Are people, wallets and other services forced to use Segwit?
- they are not forced but like soft update ,giving immense opportunity to try or prefer the pros of incorporating segwit support since original transaction ID is kept unique and not altered.
-
A larger block size was a proposed alternative to segwit.
-
Segwit additionally solves the transaction malleability issue.
-
Segwit allows for second layer protocols like the Lightning network, which boosts bitcoin’s transaction capacity by taking frequent, small transactions off-chain.
-
No, it is a soft fork.
-
The proposed alternative to Segwit was to simply hard fork and increase the block size limit. Bitcoin Cash wanted to increase it to 4 MB
-
More than just the scaling issue, Segwit solved the security issue of Transaction Malleability.
-
Segwit made second layer solutions like the Lightning Network possible.
-
No one is forced to use Segwit, it was a soft fork.
- What was a proposed alternative to Segwit?
A. Increasing the block size from 1mb to 2mb which would lead to a
hard fork. - What did Segwit solve more than just the scaling issue?
A. It solved the transaction malleability issue by placing the signature
outside of the transaction block. - How is Segwit and the Lightning network connected?
A. The proposed solution the BTC network came up with allowed for second
layer protocols such as the Lightning network to be implemented that relied
on unconfirmed transactions that were less risky and easier to design. - Are people, wallets and other services forced to use Segwit?
A. No, but the advantages to its adoption is beneficial to all users. With the
conversion by basically all major players the use by most if not all is essentially
inevitable.
1 - Increase the size of block
2 - Fixed transaction maleability
3 -Segwit supports a second layer. Which enabled the lightning network
4 - No, because they are compatible with old protocol
- What was a proposed alternative to Segwit?
Answer:
Increase block size from 1MB to 4MB.
- What did Segwit solve more than just the scaling issue?
Answer:
SegWit fixed the transaction malleability problem.
- How is Segwit and the Lightning network connected?
Answer:
Segwit supports the development of second layer protocols, such as the lightning network.
- Are people, wallets and other services forced to use Segwit?
Answer:
No, it is a soft fork
-
People proposed to simply increase the block size limit, instead of utilizing Segwit
-
Segwit’s main purpose besides simply handling scaling, is to deal with the Transaction Malleability exploit.
-
Segwit technology enables second layer transactions by lowering the risk involved with unconfirmed transactions. I also surmise that Segwit’s development created the technological concept that Lightning utilizes.
-
Not all nodes are required to use Segwit, as it is a Soft Fork. I do not understand how this works outside of that fact, and could use further explanation.
-
Alternative would be increase in block size (ie: Bitcoin Cash) which uses 8MB blocks, but also a little less secure than BTC blockchain.
-
It also solved transaction “Malleability” and enabled second layer protocols.
-
They are connected because Segwit enables 2nd layer protocols to be used. In this case, the “Lightning Network.”
-
They are not forced to use Segwit. It is a soft fork. However, if they do implement Segwit, their BTC transactions will process faster and with less transaction fees.
- bitcoin cash, which increased block size
- transaction malleability
- the lightning network is built on Segwit
- No. Wallets slowly added Segwit