But, segwit didn't originate as a method by which to scale the bitcoin network.
While doubling Bitcoin's block size would (probably) decrease average fees and / or confirmation times, the recent activation of
SegWit did already decrease both quite a bit.
Unfortunately,
SegWit did not get the necessary support from miners which led the «User - Activated Soft Fork» or UASF, a fork that aimed to compel miners into signaling approval for SegWit, by rejecting blocks that did not contain this signal.
So,
SegWit does not increase the block size limit, but it does enable a greater number of transactions within the 1 MB blocks.
But more importantly,
SegWit does not fundamentally understand — let alone appreciate — that the true value of bitcoin lies in the relationship between use and demand, said Dr. Craig Wright, chief scientist for nChain.
While Charles claimed he was happy to see progress made on the eventual activation of Segregated Witness (SegWit) via the activation of BIP 91, he also added, «SegWit doesn't go far enough.»
I crunched the numbers for the potential benefit that miners can get from AsicBoost, and I think SegWit doesn't change that much.
«SegWit doesn't solve the problem we have right now which is an urgent need for on - chain scaling,» said Yours CEO Ryan X. Charles, who supports Bitcoin Cash's technical roadmap.
Not exact matches
The problem is that some developers are now saying
SegWit can
do the same thing, and are backing away from the scheduled implementation in November.
Yang is an operator of one of the newer mining pools, but has already generated complaints for his favored stance - that
SegWit has little to
do with scaling and that all the main devs should be fired.
And that version of Bitcoin
does not have a
Segwit.
Bitcoin didn't even show all his
SegWit benefits (internal) and it already has upcoming news.
«I
do believe having
SegWit activate on Litecoin will help make that possible on Bitcoin too.
Since
SegWit isn't looking like a sure thing, have you looked into implementing payment channels as a centralized service similarly to what they are
doing with the Yours Network?
If more than 50 % of the operators and miners don't convert to the new BIP 91 software, there is a chance that
Segwit couldn't go through as planned.
Bitcoin ABC has contained within its release a dynamic difficulty adjustment,
does not include
SegWit, and increases the block size to 8 MB.
Bitcoin Cash has a block size of 8 MB compared to 1 MB for bitcoin and
does not have
segwit.
Although
SegWit adoption has since brought them back to normal levels, the damage was
done: many retailers ditched Bitcoin in favor of Bitcoin Cash or other alts.
Pictured above is the new option for choosing the address type on Ledger Bitcoin Wallet IMPORTANT: If you
do not wish to use
SegWit, or if you are not sure about anything, just click on the LEGACY button and you'll access and manage your accounts as it was before.
When computing a
SegWit signature, the previous transactions
do not need to be processed by the device, and each input is only processed once during the signature process, leading up to a 60 % time optimization in the signature process.
If wishing to upgrade, Ledger users can recreate the same account naming and structure on the
SegWit branch and move funds from the legacy branch to the
SegWit branch by
doing a normal bitcoin transaction.
As previously reiterated, the pool
does not think
SegWit properly addresses network capacity, which they explain «is now the most urgent issue for [b] itcoin.»
For new users of Bitcoin,
SegWit may seem like a meaningless buzzword that
does not hold any value.
While the upgrade
does enable a greater number of transactions in bitcoin's blocks,
SegWit's initial intention was to fix a bug in the bitcoin code called transaction malleability.
While Bitfinex and Coinbase announced recently they are adopting
SegWit, Coinsquare
does not have any plans to follow suit just yet.
That said, it is probably wise not to send huge amounts of bitcoin to
SegWit addresses straight away, and instead wait at least a couple of hours or maybe days to
do so.
And, the incompatibility between (covert use of) AsicBoost and Segregated Witness could explain why Wu was supportive of extension blocks, a recent proposal that appears to have little (if any) benefit over
SegWit... except that extension blocks don't break covert use of AsicBoost.
If things had gone differently, users, mining pools, and companies running the BIP 148 nodes would have started rejecting blocks that
did not signal support for
SegWit yesterday.
Jeff Garzik, the former Bitcoin Core contributor — who would soon after found his own development company Bloq —
did not consider
SegWit a sufficient short - term scaling solution.
Vertcoin developer and project manager «etang600» emphasized, however, that this had nothing to
do with
SegWit itself — only with how they implemented it.
That means that implementing the system on the bitcoin network would require a soft fork to add new codes to the script, just as other proposals such as
SegWit would
do.
While the development aspect of the
SegWit rollout process appears to be nearly over, there still is work to be
done on figuring out how this change will be activated in a timely manner.
«We
do plan to support
SegWit.
«For example, remote procedure calls could request
SegWit transactions, while at the same time rejecting these transactions because they didn't expect to get them.»
Although
SegWit adoption has since brought them back to normal levels, the damage was
done: many retailers ditched Bitcoin in favor of Bitcoin Cash or other alts.
If some users don't like
SegWit, for example, they can choose not to upgrade.
«
SegWit as a soft fork is about as safe as the CSV soft fork was — and you don't hear anyone complain about that.»
And while
SegWit looks to enable a bright future for bitcoin, it doesn't exactly bring an end to the debate and politics that have mired the community for years.
And they
do not support
SegWit.
Until
SegWit, LN, and Confidential Transactions, I didn't see a need for Litecoin to come out to help test features before they are on Bitcoin.
Specifically, they will reject any Bitcoin blocks that
do not signal support for Segregated Witness (
SegWit), the centerpiece of Bitcoin Core's scaling roadmap.
Bitflyer CEO Yuzo Kano, for instance, said he didn't know if
SegWit would be «sufficient» to fix the «block size issue» stating that he is «pro bigger blocks» because he believes it would make bitcoin more user friendly.
Despite all the recent hype, though, it's hard to say if
SegWit will ever activate on litecoin, even if it's close to
doing so.
«I think Bitcoin Core is making the right trade - off to
do SegWit as a soft fork,» Lee said.
When
SegWit was initially implemented on August 1, the blockchain
did undergo a hard fork (totally separate from the fork that was supposed to occur in November).
One minute the community thinks
SegWit is about to activate, the next it doesn't seem so clear.
When
SegWit finally activated last week, the code change didn't immediately make its benefits possible.
«The Bitcoin Core team believes
doing a hard fork at the present time is needlessly risky, and is instead pursuing
SegWit via a soft fork for a similar sized potential gain in throughput.»
But it doesn't stop there, because according to one expert,
SegWit's technical changes could also pave the way for legal issues.
He noted that DLC
does not require any changes to bitcoin, but it (like many others in the space) will work better when a coding optimization known as
SegWit is activated on bitcoin - if it ever is.