- The proposed alternative to Segwit was the increase of block size (which eventually lead to Bitcoin Cash Fork
- Segwit and lightning both have as aim to reduce network load on the Bitcoin network. Segwit achieves this by reducing data in the transaction (therefore allowing more transactions in the block) and lightning network achieves this by taking small transactions off-chain
- Both run on the bitcoin network and have the same objective
- No. Adoption has been gradual. Those that have not adopted and effectively went with the block size upgrade effectively became part of the Bitcoin cash hardfork (split of network)
- to make block larger than 1mB for more tx. 2.that you cant change signatur and faster confirmt tx. .3 So you can have 2nd layer solution on btc block. 4. no but if not you have slower tx vertifikation.
1- Bitcoin Cash which increases the size of the blocks
2- Fixed transaction malleability by removing the signature information outside of the base transaction block
3- SegWit allowed for the support of second layer development such as the lightning network
4- SegWit is a soft fork, though they are not forced to use it, it is better for the overall network if they get onboard
-
Increasing the block size
-
It fixed the transaction malleability. The signatures are removed so that a modification them has no impact on transactions id.
-
Segwit makes it possible to execute off-chain transactions and append to the block chain when users are ready.
-
No, it’s optional.
1. What was a proposed alternative to Segwit?
Increasing the block size limit
2. What did Segwit solve more than just the scaling issue?
TX malleability. The signatures are stored separately from the TX so modification of them couldn’t affect the hash of the TXID
3. How is Segwit and the Lightning network connected?
TX malleability meant that second layer protocols with unconfirmed transactions were very risky. By fixing the TX malleability issue these second layer protocols are much less risky to use. The Lightening network takes some small transactions off chain settling them on the blockchain at a different time, allowing more TXs to occur in a shorter space of time.
4. Are people, wallets and other services forced to use Segwit?
No, the chain can still work without it.
I said people were not forced to use segwit, but somehow fooled, because segwit changed commands used in the the script. What do i mean with this ?
Basically the locking script has been changed from
OP_DUP OP_HASH160 <pubKeyHash> OP_EQUALVERIFY OP_CHECKSIG
to
0 <pubKeyHash>
As far as i understand this right now is that the locking script (or also called unlocking or redeem)
is executed to check if a UTXO can be spend or not.
The change caused that old nodes did not lock anymore at all.
But, to be honest i don’t want to investigate further on this for now (as long as i do not understand the bitcoin script correctly and can say what exactly it does).
— My answers —
-
Increasing the block size.
-
The transaction malleability issue.
-
Lightning network wouldn’t be possible without fixing the malleability issue as it requires the transaction IDs to not being altered. By fixing the malleability bug, segwit makes also the lightning network possible.
-
No, as segwit is a soft fork. However, the weight of the transactions executed from a legacy wallet is higher and therefore it’s more expensive in terms of fees.
-What was a proposed alternative to Segwit?
The proposed alternative was to increase the block size.
-What did Segwit solve more than just the scaling issue?
TX Malleability. It also allowed for a second layer- the Lightning Network.
-How is Segwit and the Lightning network connected?
Second layer protocols, such as the Lightning Network are supported by implementation of SegWit.
-Are people, wallets and other services forced to use Segwit?
No. They can still follow the old protocols.
Yes, but this is only to unlock utxo’s to spend from segwit adresses etcetera. There are many ways to lock bitcoins to a public key. You can even make your own type of locking script. But the bitcoin core implementation doesn’t support non standard scripts anymore. The opcodes are still the same, but you basically lock coins in another (allowed) way. Many people still use old addresses. So everyone is free to use whatever address type or run a non segwit node. But there are so many advantages to use Segwit adresses. For example the fee’s are much lower.
What do you mean by this ?
Does it still mean that you define the locking script by your own (and the bitcoin core client only uses specific scripts and other wallet-clients may send their own scripts) or is it explicitely defined which scripts are allowed to be used so that every node can verify if this is an allowed script ?
- What was a proposed alternative to Segwit?
Increasing the block size.
- What did Segwit solve more than just the scaling issue?
It provided a second layer solution that was within the risk tolerance for transactions
- How is Segwit and the Lightning network connected?
Segwit in a sence birthed the lightning network. It allows for a programmable second tier that is within the transaction risk tolerance and block size.
- Are people, wallets and other services forced to use Segwit?
Negative it’s a soft fork so its backwards compatible.
Ok but seagwith is soft fork so miners don t have a choice and you re forced by common sense .but i understand why mine answer should be from other perspective thx
uto, 26. svi 2020. u 18:46 Fabrice Manzo via Ivan on Tech Forum <[email protected]> napisao je:
- What was a proposed alternative to Segwit?
Increase block size. (to 2mB)?
- What did Segwit solve more than just the scaling issue?
The Malleability problem.
Lowering TX fees.
Made it possible to build second layer protocols like lightening network.
- How is Segwit and the Lightning network connected?
See above.
- Are people, wallets and other services forced to use Segwit?
No.
- What was a proposed alternative to Segwit?
Increasing the block size
-
What did Segwit solve more than just the scaling issue?
It fixes the malleability issue where details in the transaction could be changed, changing the transaction id. It removed the signature from the block allowing more room to fit more transactions into a block causing fees to lower.
-
How is Segwit and the Lightning network connected?
Fixing the block size and malleability issues so transactions could be safer which allowed the lightening network to be built on segwit so transactions to be taken off the blockchain until they were ready to be confirmed.
- Are people, wallets and other services forced to use Segwit?
No because it is a soft fork which means it is not a required update.
- Increasing the block size to 2MB
- It increased security by addressing the transaction malleability issue. The increased security was achieved by removing the signatures from the block which meant that tampering with the signature of an unconfirmed transaction no longer changes the hash of the trx ID as the signature is now outside the block and has no longer any influence on the transaction ID.
- By removing the signature from the block, a security issue was resolved that impaired the safe development of transactions on 2nd layer protocols such as the lightning network
- No, Segwit is a soft fork and as such participants can decide freely if they want to adopt this change or not. Adoption has increased steadily since its introduction and hopefully everyone will end up adopting this change and help to improve scalability and more security on the Bitcoin network.
- The proposed alternative to Segwit was to increase the size of blocks from 1MB to 2MB through a hard fork
- In addition to the scalablity benefits, Segwit prevents transaction malleability attacks - the ability of someone to change the way a signature appears in a transaction, resulting a completely new Transaction ID
- Segwit facilitates scalability but is not a comprehensive solution to the problem. It also supports the development of second layer protocols such as the Lightening network, which further enhances scalability by shifting small micro transactions off-chain and using the the blockchain on a periodic basis primarily for settlement purposes.
- The segwit upgrade is optional - while no one is forced to use it, it is compatible with previous protocols (it was a soft fork) so non-segwit transactions can still be mined into a block. Adoption is incentivized through a number of efficiency gains.
-
The proposted alternative was to increase the block size to 2MB, a part of the community has adopted this solution and therefore Bitcoin Cash has come out.
-
Segwit has solved the block size limit so that by removing signature from the block structure more transactions could now fit in the block and also solving the malleability issue meaning that users could not alter the transaction ID anymore, while signatures and script are stored separately now.
-
Segwit supports the development of second layer protocols such lightning network. This allows to futher boost bitcoin’s transaction capacity.
-
They are not forced to use Segwit, but many have already adopted Segwit support.
- Increase block size.
- Transaction malleability.
- Possibility of second layer protocols .(Base of Lightning Network)
- No, it is a soft fork.
To increase the blocksize
Transaction malleability
Segwit supports layer 2 Protocols development of Lightning network
No, People can decide for themself.
-
Implementing a larger block size limit was a proposed alternative to Segwit.
-
Not only did Segwit solve the scaling issue, but it also solved the problem of transaction malleability by removing the signature/witness information.
-
Segwit and the Lightning network are connected in that the lightning network will soon boost bitcoin’s transaction capacity by taking certain transactions off of the chain. Segwit actually supported the development of the Lightning network.
-
People, wallets, and other services are not forced to use Segwit; however, Segwit will gradually be used more often in transactions, causing bitcoin fees to drop.