-
What was a proposed alternative to Segwit?
Increasing block size to 2mb from 1mb -
What did Segwit solve more than just the scaling issue?
Transaction malleability -
How is Segwit and the Lightning network connected?
Segwit allows for the use of second layer protocols such as Lightning where micro transactions can be done much quicker offline and then added to the blockchain when the parties are ready. -
Are people, wallets and other services forced to use Segwit?
No, because it was a soft fork. However, currently the vast majority of miners, nodes and wallets support segwit.
1. What was a proposed alternative to Segwit?
- To increase the Block size from <=1 MB to <=2 MB to fit in more Tx.
2. What did Segwit solve more than just the scaling issue?
- Segwit was actually proposed to Solve Tx Malleability issue. By changing the signature within the tx was also changing the Hash ID of Tx.
3. How is Segwit and the Lightning network connected?
- Segwit supports the second layer protocol called lightning network. By resolving the malleability issue, it allowed developers to create feature called lightning network which relies on unconfirmed transactions and make the new feature less risky and easier to design
4. Are people, wallets and other services forced to use Segwit?
- They are not forced but as many services embrace the segwit change, it will allow more transaction in the block which ultimately brings down the fees and aids to other features in the roadmap e.g. lightning
- What was a proposed alternative to Segwit?
Larger block size
- What did Segwit solve more than just the scaling issue?
Solves transactions malleability
- How is Segwit and the Lightning network connected?
Segwit transaction malleability fix supports development of second layer protocols like lightning network
- Are people, wallets and other services forced to use Segwit?
No.
Segwit Answers
-
The proposed alternative was the temporary fix of raising the block size limit from 1mB to 2 mB.
-
Segwit solves both issues of blocks being full and TX malleability by removing the signature from TX and therefore reducing the size of TX and preventing the issue of changing the script signature from affecting the actual TX.
-
Segwit supports the building of second layer protocols by fixing the malleability problem making the Lighting Network possible by making unconfirmed TX easier to sign and less risky.
-
No this was a softfork update
-
What was a proposed alternative to Segwit?
A proposed alternative to Segwit was to increase the block size. -
What did Segwit solve more than just the scaling issue?
Besides scaling issues, Segwit also solved Transaction Malleability. -
How is Segwit and the Lightning network connected?
Both are connected due to The Lightning Network being a second layer solution. -
Are people, wallets and other services forced to use Segwit?
It is not a requirement to use SegWit, but it is a soft fork
Lesson 5 – Reading assignment: Segwit - questions
-
What was a proposed alternative to Segwit?
Larger block size limit -
What did Segwit solve more than just the scaling issue?
It also solved the malleability issue -
How is Segwit and the Lightning network connected?
Segwit allows the use of second layer protocols like The lightening network. It will help Segwit to boost the bitcoin transaction capacity by taking frequent small transactions off chain until the users are ready to settle the transactions on the bitcoin blockchain. -
Are people, wallets and other services forced to use Segwit?
No Segwit is a Soft Fork so all new rules in the protocol update fit into the old rule set.
-
What was a proposed alternative to Segwit?
Increasing the 1mb block size was an alternative. -
What did Segwit solve more than just the scaling issue?
Segwit solved transaction malleability. (The ability to modify the signature of a transaction.) -
How is Segwit and the Lightning network connected?
The lightning network is a layer 2 scaling solution that can send transactions for little to no fees off chain and then finalize all the data on chain eventually. -
Are people, wallets and other services forced to use Segwit?
Segwit is a soft fork so wallets and services are not forced to adapt to the new format unless they choose to.
1. What was a proposed alternative to Segwit?
Increase Blocks size
2. What did Segwit solve more than just the scaling issue?
Solver Tx malleability, and lower fees
3. How is Segwit and the Lightning network connected?
Allowed dev on second layer protocols
4. Are people, wallets and other services forced to use Segwit?
No since not all node have updated to the update
- A hard fork increasing the max block size to 2 MB.
- The transaction malleability issue.
- By solving transaction malleability, Segwit helps second-layer and smart contract protocols such as Lightning. Any feature that relies on unconfirmed transactions is less risky and easier to design under Segwit.
- No, however many people naturally began to transition to Segwit throughout the industry.
thanks, well spotted, I meant increase speed.
- What was a proposed alternative to Segwit?
-Another option was to increase the block size limit, to be able to squeeze more data into a block
- What did Segwit solve more than just the scaling issue?
-It solved the transaction malleability issue. Where you were able to go in a alter the transaction ID, in turn altering the hash output.
- How is Segwit and the Lightning network connected?
-Segwit update allow for a 2nd layer solution. The Lighting network was that 2nd solution to scale the bitcoin network. It allows for small transaction off chain.
- Are people, wallets and other services forced to use Segwit?
-No, but with segwit fees are reduce and transaction are confirm quicker. So i dont see why not.
[quote=“filip, post:1, topic:8408”]
- What was a proposed alternative to Segwit?
Block weight was proposed as an alternative to Segwit. It’s a mashup of block size with and without signature data not to exceed 4BM.
- What did Segwit solve more than just the scaling issue?
The possibility for development of second layer protocols. It also avoids the need for a hard fork. - How is Segwit and the Lightning network connected?
It takes smaller frequent transactions off the chain, and it is a second layer protocol. It also allows settling the blockchain only when users are ready. - Are people, wallets and other services forced to use Segwit?
No because it’s not a hard fork, but many people, wallets and services are starting to implement Segwit.
-
What was a proposed alternative to Segwit?
To increase block size limit. That would have created a hard fork. -
What did Segwit solve more than just the scaling issue?
It also helped to keep fees low and have low/acceptable confirmation waiting time. -
How is Segwit and the Lightning network connected?
Thanks two SegWit, 2nd layer solutions were possible. Lightning is one of these. -
Are people, wallets and other services forced to use Segwit?
No. Some of them didn’t accepted the consensus change. Other are accepting the change over time. As of today, segwit is at 40% acceptance.
What was a proposed alternative to Segwit?
to cut fees
and to cut the confirmation time
in order to increase adoption.
the question was asked: Can we increase the size of the blocks?
yret, if increasing blocks size will lead to temporary reprieve and lead to …
a hard fork, if not everyone would agree, and lead to…
Miner centralization increases, as hardware requirements to process larger size blocks
network traffic increases, and so does network hardware (memory, CPU, etc) and bandwidth issue plus, and lead to…
time to effectively propagate these larger blocks across the network will lead so increasing chances of stales blocks and soft forks
What did Segwit solve more than just the scaling issue?
Transaction Malleability - where someone can change the transaction’s hash after the transaction was confirmed and sent / propagated by resending the transaction with a modified signature - as in ScriptSig which can be changed make small changed to change the way the signature is written - and lead to increase risk hacks, Attacks and stolen money. this issue his precluded the ability for second-layer protocols and smart contracts.
How is Segwit and the Lightning network connected?
SeGwit achieved malleability by putting the signature /witness info outside the base transaction block which secured the transaction ID by insulating it from the signature - the bug was fixed
This slimmed down the data inside the block and allowed for more transaction per 1 MB block limit. Segwith added the concept of “Block weight” or a new cap of 4MB which include signature date out the transaction block and the 1MB block itself!!
SeqWit also reduced the risks of unconfirmed transactions and made it easier to design more features - enter Lightening network as well 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).
Are people, wallets and other services forced to use Segwit?
No. By Bitcoin enabling SegWit, BitCoin Cash was Forked into existence
, as they wanted to kick the can don the road and just go ahead and increase the block size limit, rather than employ a new structure.
tezor, Ledger, Electrum, Kraken did but Coinbase was slower in their work to do so, as well as Bitcoin Core bitcoin;s most popular Full node wallet.
- increasing the block size to 2mB
- the transaction malleability issue
- segwit made it possible for second layer protocols like the lightning network to be developed as it makes working with unconfirmed transactions less risky
- no, as it was a soft fork, not a hard fork
-
What was a proposed alternative to Segwit?
Increase block size to 2 mB. -
What did Segwit solve more than just the scaling issue?
The issue with the transaction malleability. With segwit the signature is not hashed and thus not included in the Tx id. -
How is Segwit and the Lightning network connected?
Segwit “frees” resources on blocks that could be used for layer 2 solutions like the Lightning network. -
Are people, wallets and other services forced to use Segwit?
No. They are not forced and that is why the adoption took time.
- Increasing the transaction block size.
- Malleable transactions.
- Solving the issue of malleable transactions as Segwit did makes implementing Lightning network possible.
- No.
1. What was a proposed alternative to Segwit?
- Another possibility to fight the full blocks was to increase the overall block size, from 1MB for example to 2 or 4 MB. Some groups of people actually implemented these alternatives and created some Bitcoin forks, like Bitcoin Cash.
2. What did Segwit solve more than just the scaling issue?
- It also fixed the issue with transaction malleability. Previously, it was possible for anyone to change the transaction ID of any transaction in the mempool, by modifying the signature, while the signature still remained valid. Some “hackers” could exploit this and fraud the less-knowledgeable BTC users, who were sending them a transaction, to send them the same amount of BTC twice.
3. How is Segwit and the Lightning network connected?
- Segwit is a big enabler for the Lightning network, as, without it, the implementation would be much harder. In the case of Lightning network, the block size is obviously irrelevant, in this case, the only issue was the transaction malleability. With solved transaction malleability, it becomes much easier to rely on the existence of a specific transaction in the mempool.
4. Are people, wallets and other services forced to use Segwit?
- Nobody is forced to use anything in the Bitcoin space, everybody has a choice. Segwit, being a softfork, was taking quite a long time until it was widely used by all the major wallet providers. It was causing quite some issues at the end of 2017 when the transaction fees were skyrocketing, as not so many wallets were using segwit then.
You also are not required to use BCH because you can use old style transactions on BTC just fine. As you mentioned other wallets didn’t implement it soon after Segwit was activated.
I’m not sure how long it took for bitcoin core to support it. I would imagine they were the first to have it implemented
- An increase in the block size
- Transaction malleability
- SegWit support the second layer solution which is the lightning network
- No because it is a soft fork