-
What was a proposed alternative to segwit?
The proposed alternative was to increase the block size to 4mb. -
What did Segwit solve more than just scaling issue?
The activation of other features such as MAST, which enabled more complex contracts, better security, less risks of stale blocks forming and transaction capacity boost. -
How is Segwit and the lighting network connected?
Segwit boosted development on supporting features such as enabling the lighting network. -
Are people, wallets and other services forced to use Segwit?
No, but a majority of providers were intending to implement a roll-out from 2018.
-
A increase in the block size
-
transaction malleability
-
“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.”
-
No thus: bitcoin cash
- Increasing the block size from 1MB to 2MB.
- The transaction malleability problem.
- By fixing the malleability problem, Segwit made any feature that deals with unconfirmed transactions less risky.
- No.
- What was a proposed alternative to Segwit?
Bitcash.
- What did Segwit solve more than just the scaling issue?
Transaction malleability.
- How is Segwit and the Lightning network connected?
Layer 2 solutions.
- Are people, wallets and other services forced to use Segwit?
No.
- What was a proposed alternative to Segwit?
Block size increase
- What did Segwit solve more than just the scaling issue?
It fixed a a problem with being able to change the signature and eliminating transaction id malleability.
- How is Segwit and the Lightning network connected?
Segwit planted the seed to make The Lightning Network possible.
- Are people, wallets and other services forced to use Segwit?
no they are not it was a soft fork and by 2019 40% had adapted it
-
What was a proposed alternative to Segwit?
The alternative was to increase the allowed block size to 2 MB. -
What did Segwit solve more than just the scaling issue?
It solved the malleability issue, the fact that it was possible to change the transaction ID by changing the signature without changing the transaction itself. It was solved by saving the signature outside the block. -
How is Segwit and the Lightning network connected?
Lighning is a layer 2 protocol that allows faster transactions by relying on unconfirmed transactions. Since with SegWit the block ID cannot be changed by just changing the signature (since its not part of the block and therefore the hash won’t change either) it is much safe to rely on unconfirmed transactions. -
Are people, wallets and other services forced to use Segwit?
No, they are not since it is a soft fork.
-
Increasing the block size to 2 mB
-
It solved the transaction malleability problem
3.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.
- No because it is a soft fork. You can still include signatures in your block but it’ll be less likely that your block will be selected since it has less fees and proof of work.
- It increases the block.
2.The segwit solved the transaction malleability.
-
They’re both connected that made the second layer possible.
-
No, there are other ways that can be used with transactions and nodes.
What was a proposed alternative to Segwit?
The alternative proposal to Segwit was the increase of the block size to 2MB
What did Segwit solve more than just the scaling issue?
Besides the scaling issue, Segwit solves also the problem with tx malleability by removing the tx signatures from the Block.
How is Segwit and the Lightning network connected?
SegWit enabled second layer scaling solutions, leading to the birth of the Lightning Network.
Are people, wallets and other services forced to use Segwit?
No, it was a soft fork. Besides Segwit there is also Legacy and Native SegWit(Bech32)
-
To increase the block size to 2MB -> Bitcoin Cash
-
It also solved a bug of transaction malleability, allow people to change small details of the transaction ID but not the transaction contents
-
The malleability fix in Segwit made any feature that relied on unconfirmed transactions less risky and easier to design. Second layer features could now use Bitcoin securely
-
No
- To increase the block size to 2 MB. This is what would happen with Bitcoin Cash (hardfork).
- It solved the problem of malleability. This made any feature that relied on unconfirmed transactions less risky and easier to design, which made possible the development of second layer protocols, such as the lightning network. Segwit also boosted development work on other features such as MAST (which enables more complex bitcoin smart contracts), Schnorr signatures (which would enable another transaction capacity boost) and TumbleBit (an anonymous top-layer network).
- The Lightning network was made possible by Segwit because it is a second layer protocol that relies on unconfirmed transactions. Segregating the signatures from the transactions ensured that changes to the signatures would not affect the hash of the transaction (Tx ID).
- Being a soft fork, segwit will not be forced on the network immediately, but once over 50% of the network adopts segwit the new fork will grow longer and show more PoW. This will result in the original fork dropping off and its transactions returning to the mempool. Therefore after 50% of the network updates it will be forced on the rest of the network (majority rule). Is this correct @filip?
-
What was a proposed alternative to Segwit?
Increase the transaction block from 1MB to 2MB’s.
-
What did Segwit solve more than just the scaling issue?
It solved the transaction malleability issue.
-
How is Segwit and the Lightning network connected?
The lightning network effectively creates a layer on top of bitcoin, enabling fast and cheap transactions which can net settle to the bitcoin blockchain.
-
Are people, wallets and other services forced to use Segwit?
No.
-
What was a proposed alternative to Segwit?
Increase the block size. -
What did Segwit solve more than just the scaling issue?
Solved the malleability issue. -
How is Segwit and the Lightning network connected?
Segwit’s platform allows for second layer development. Lightning network is second layer. -
Are people, wallets and other services forced to use Segwit?
No, Its optional.
- A proposed alternative to Segwit was to increase block size from 1mb to 2mb.
- Segwit solved more than just scaling issue but also solved problem with malleability transaction.
- Segwit makes the second layer solution possible.
- No, it is just a soft fork.
-
A proposed alterantive to SegWit was Block weight increase.
-
SegWit made transaction sizes smaller by removing the sig from the hash block, it boosted the development of MAST which enables more complex bitcoin smart contracts, Shchorr Signatures which anabled another transaction capacity boost, and Tumblebit which is an anonymous top layer network. It alos supports the development of the lightning network.
-
SegWit is and still is a major contributer to the lightning network as it makes it possible with the solutions SegWit provides to Bitcoin. Segwit supports the layer two solutions which is namely the “Lightning Network”.
-
People, Wallets and other services are not forced to use segwit but SegWit provides better security for verifying transaction signatures and avoids forks from forming in the blockchain.
-
Implementation of a larger block size, hence a hardfork on the network and the creation bitcoin cash network
-
The malleability fix and it also supports the development of a second layer protocols ie the lightning network
-
SegWit enable the second layer
-
No
- What was a proposed alternative to Segwit?
Increasing the block size. - What did Segwit solve more than just the scaling issue?
Transaction Malleability. - How is Segwit and the Lightning network connected?
Due to the fix of transaction malleability, the bitcoin network now supports second lay networks such as the Lightning network. - Are people, wallets and other services forced to use Segwit?
No, in fact not all wallets have transitioned yet and therefore only a percentage of the transactions use segwit. As more wallets and services include Segwit, fees are expected to drop due to the additional space for more transactions in each block.
1.) Larger block size
2.) Segwit fixed an issue in the code that could allow anyone to change info in the transaction id. Segwitt also fixed transaction malleability by removing the signature info. Allowing more to fit inside of a transaction
3.) Both working together to boost transaction captivity and enables more complex development dapps like smart contracts
4.) No
1 Increase the block size
2 Malleability issue. When the Sig is removed trx ID can’t be modified
3 Segwit makes Lightning network possible as a layer 2 solution to speed trxs
4 No adding Segwit created a soft fork
- Increasing block size.
- Solved transaction malleability.
- Solving TX malleability allowed unconfirmed TXs more secure. Lightning network takes TXs offchain and settles them on-chain when ready.
- No, because it is a softfork.