Bitcoin.org Denounces Segwit2x Supporters Vows To Call Them Out

Bitcoin.org announced it was “denouncing” the Segwit2x hard fork and companies involved or who support the project. The website plans to publish a banner on every page of the website explaining “risks of using services” that are associated with the November 2MB fork and development team to investors of Bitcoin.

On October 6, the two anonymous owners of the website Bitcoin.org, ‘Theymos’ and ‘Cobra Bitcoin,’ stated they would soon be posting a warning on every page about the risks of Segwit2x and every company involved with the fork will also be mentioned.

“On 2017-10-11 at noon (UTC), Bitcoin.org is planning to publish a banner on every page of the site warning users about the risks of using services that will default to the so-called Segwit2x1 (S2X) contentious hard fork,” explains the site’s warning message. “S2X companies will be called out by name.”

“To ensure that we only warn users against companies that will actually put user deposits at risk, we urge all companies to publicly clarify their stance before the above date, either by a highly-visible public statement or by commenting on Bitcoin.org issue #1835 (or by doing both).”

In particular, Bitcoin.org noted that they need to know three key points are followed by companies supporting Segwit2x:

  1. The company will not under any circumstances list “Segwit2x” as “BTC” and/or “Bitcoin”. Note that Bitcoin is not ruled by miners, and miner actions cannot be used as a justification to redefine Bitcoin.
  2. The company will not by default do anything that would deprive users of their bitcoins (by eg. using S2X software without addressing replay attacks2, selling user bitcoins automatically, crediting BTC deposits only as S2X deposits, etc.). Providing access to S2X-coins is acceptable, however.
  3. The company will continue to provide normal service to Bitcoin (ie. non-S2X) users.

The press release further listed current companies that are supporting the Segwit2x hard fork:

  • 1Hash (China)
  • Abra (United States)
  • ANX (Hong Kong)
  • Bitangel.com /Chandler Guo (China)
  • BitClub Network (Hong Kong)
  • Bitcoin.com (St. Kitts & Nevis)
  • Bitex (Argentina)
  • bitFlyer (Japan)
  • Bitfury (United States)
  • Bitmain (China)
  • BitPay (United States)
  • BitPesa (Kenya)
  • BitOasis (United Arab Emirates)
  • Bitso (Mexico)
  • Bixin.com (China)
  • Blockchain (UK)
  • Bloq (United States)
  • BTC.com (China)
  • BTCC (China)
  • BTC.TOP (China)
  • BTER.com (China)
  • Circle (United States)
  • Civic (United States)
  • Coinbase (United States)
  • Coins.ph (Phillipines)
  • CryptoFacilities (UK)
  • Decentral (Canada)
  • Digital Currency Group (United States)
  • Filament (United States)
  • Genesis Global Trading (United States)
  • Genesis Mining (Hong Kong)
  • GoCoin (Isle of Man)
  • Grayscale Investments (United States)
  • Jaxx (Canada)
  • Korbit (South Korea)
  • Luno (Singapore)
  • MONI (Finland)
  • Netki (United States)
  • OB1 (United States)
  • Purse (United States)
  • Ripio (Argentina)
  • Safello (Sweden)
  • SFOX (United States)
  • ShapeShift (Switzerland)
  • SurBTC (Chile)
  • Unocoin (India)
  • Veem (United States)
  • ViaBTC (China)
  • Xapo (United States)
  • Yours (United States)

Bitcoin.org also cleared the air about SegWit stating the new hard fork has nothing to do with the technology. They additionally added that SegWit2x’s replay protection requires manual steps to prevent loss of BTC and that users who adopt the S2X currency may face loss of BTC.

  1. “SegWit2x” has nothing to do with SegWit. SegWit is already activated, and was supported by an entirely different set of people.
  2. S2X claims to have replay protection, but their version requires extra manual steps in order to prevent loss of BTC. If you use S2X software without careful engineering, you are likely to lose any associated BTC.

Want an edge in the crypto markets? Subscribe to our free newsletter. Follow Coinivore on Facebook, at Twitter and Steemit.

New to Bitcoin? Check out these tools to get started.

Leave a Reply

1 comment