Finance:SegWit2x

From HandWiki
Revision as of 00:03, 3 December 2022 by SpringEdit (talk | contribs) (linkage)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

SegWit2x was a proposed hard fork of the cryptocurrency Bitcoin. The fork was slated to occur on 16 November 2017, but was cancelled due to lack of consensus. The fork would have increased the block size to 2 megabytes. Segregated Witness has been previously activated on the Bitcoin chain from which SegWit2x would have forked.

Details

The implementation of Segregated Witness in August 2017 was the first half of the so-called "New York Agreement" in which those who wanted to increase effective block size by SegWit compromised with those who wanted to increase block size by a hard fork to a larger block size.[1] The second half of SegWit2X involves a hard fork in November 2017 to increase the blocksize to 2 megabytes.[2] Some companies that originally supported the New York Agreement backed-out, including F2Pool, Bitwala and Wayniloans.[3]

Controversy

A major issue of contention was the choice by the SegWit2x developer[4] not to implement mandatory replay protection.[5][6] Opt-in replay protection means that the Segwit2x chain will still accept transactions intended for the original chain, in addition to replay-protected transactions only valid on Segwit2x. Users sending transactions on the Bitcoin chain, or who failed to send replay-protected Segwit2x transactions, would have been vulnerable to having their transactions replayed to the other chain, resulting in accidental loss of funds. This absence of strong replay protection has created considerable controversy in the bitcoin community.[7]

Cancellation

On November 8, 2017 the developers of SegWit2x announced that the planned hard fork had been canceled, due to a lack of sufficient consensus.[8][9]

Network Failure

Although the stated reason for the cancellation of the hardfork was "lack of consensus",[10] several bugs in the codebase would have prevented the fork from occurring.[11] The official fork was planned to occur at block height 494,784, however the actual code stalled waiting for block height 494,783 due to an off-by-one coding error.[12]

The hash rate of miners signaling in favor of Segwit2x subsequently dropped to below 10%[13] and all nodes running the SegWit2x software have permanently stalled on block 494,782.[14]

See also

References

  1. ↑ Haywood, Matthew (16 August 2017). "Segwit2x, 'The New York Agreement'". bravenewcoin.com. https://bravenewcoin.com/news/segwit2x-the-new-york-agreement/. Retrieved 6 October 2017. 
  2. ↑ Hertig, Alyssa (12 July 2017). "Explainer: What Is SegWit2x and What Does It Mean for Bitcoin?". CoinDesk. https://www.coindesk.com/explainer-what-is-segwit2x-and-what-does-it-mean-for-bitcoin/. Retrieved 6 October 2017. 
  3. ↑ tendencialglobal (18 September 2017). "Segwit2X loses support between mining groups and blockchain companies". cryptocurrency. Steemit. https://steemit.com/cryptocurrency/@tendenciaglobal/segwit2x-loses-support-between-mining-groups-and-blockchain-companies. Retrieved 7 October 2017. 
  4. ↑ "List of Segwit2x contributors". https://github.com/segwit2x/segwit2x.github.io/graphs/contributors. Retrieved 10 December 2017. 
  5. ↑ "segwit2x-announce should mention how to safely opt-out of changes #10". https://github.com/segwit2x/segwit2x.github.io/issues/10. Retrieved 10 December 2017. 
  6. ↑ Song, Jimmy (4 October 2017). "How Segwit2x Replay Protection Works". bitcointechtalk.com. https://bitcointechtalk.com/how-segwit2x-replay-protection-works-1a5e41767103. Retrieved 6 October 2017. 
  7. ↑ van Wirdum, Aaron (22 September 2017). "SegWit2X and the Case for Strong Replay Protection (And Why It's Controversial)". Bitcoin Magazine. https://bitcoinmagazine.com/articles/segwit2x-and-case-strong-replay-protection-and-why-its-controversial/. Retrieved 6 October 2017. 
  8. ↑ Hertig, Alyssa (8 November 2017). "2x Called Off: Bitcoin Hard Fork Suspended for Lack of Consensus". CoinDesk. https://www.coindesk.com/2x-called-off-bitcoin-hard-fork-suspended-lack-consensus/. Retrieved 8 November 2017. 
  9. ↑ Vigna, Paul (8 November 2017). "Bitcoin Dodges Split That Threatened Its Surging Price". The Wall Street Journal. https://www.wsj.com/articles/bitcoin-dodges-split-that-threatened-its-surging-price-1510172701/. Retrieved 8 November 2017. 
  10. ↑ "Segwit2x Final Steps". 8 November 2017. https://lists.linuxfoundation.org/pipermail/bitcoin-segwit2x/2017-November/000685.html. Retrieved 1 December 2017. 
  11. ↑ Song, Jimmy (20 November 2017). "Segwit2x Bugs Explained". https://bitcointechtalk.com/segwit2x-bugs-explained-8e0c286124bc. Retrieved 1 December 2017. 
  12. ↑ Akolkar, Bhushan (18 November 2017). "Amidst Doubts, the SegWit2x Hard Fork Fails to Get Activated". https://www.coinspeaker.com/2017/11/18/amidst-doubts-segwit2x-hard-fork-fails-get-activated/. Retrieved 10 December 2017. 
  13. ↑ "Bitcoin Proposal Support by Block (historical) Summary". https://coin.dance/blocks/proposals. Retrieved 10 December 2017. 
  14. ↑ "Network Snapshot of Satoshi:1.14.5 Nodes". https://bitnodes.earn.com/nodes/?q=Satoshi:1.14.5. Retrieved 10 December 2017. 




Retrieved from "https://handwiki.org/wiki/index.php?title=Finance:SegWit2x&oldid=2445977"