{"id":23642,"date":"2017-06-14T21:55:07","date_gmt":"2017-06-14T21:55:07","guid":{"rendered":"http:\/\/ci027cfe7a600726c3"},"modified":"2017-06-14T21:55:07","modified_gmt":"2017-06-14T21:55:07","slug":"bitmain-responds-uasf-another-hard-fork-announcement","status":"publish","type":"post","link":"https:\/\/bitcoinmagazine.com\/technical\/bitmain-responds-uasf-another-hard-fork-announcement","title":{"rendered":"Bitmain Responds to UASF With Another Bitcoin Hard Fork Announcement"},"content":{"rendered":"
<\/div>
<\/figure>\n

Major Bitcoin mining hardware<\/a> producer Bitmain<\/a> today announced<\/a> that it may launch a \u201chard fork\u201d in August. Labeled a \u201ccontingency plan,\u201d the announcement is a response to the upcoming user activated soft fork<\/a> (UASF), as defined by Bitcoin Improvement Proposal 148<\/a> (BIP148) \u2014 and the wipe-out risk<\/a> that comes along with it.<\/p>\n

After an initial 8 megabyte proposal<\/a>, Bitcoin Classic<\/a>, the Hong Kong roundtable consensus<\/a>, Bitcoin Unlimited<\/a>, and SegWit2x<\/a>, this marks the sixth time the Chinese mining giant has announced support for a hard fork in the space of two years.<\/p>\n

Here\u2019s what their latest proposal looks like.<\/p>\n

Hard Forks, Coin-Splits and Altcoins<\/h3>\n

On August 1st, a segment of the Bitcoin community will activate the BIP148 UASF. These users and miners will only accept Bitcoin blocks that signal support for Segregated Witness<\/a> (SegWit), the protocol upgrade proposed by the Bitcoin Core<\/a> development team. If, at that point, a majority of miners (by hash power) does not<\/em> signal support for SegWit through BIP148, Bitcoin\u2019s blockchain and currency could split in two: a coin-split.<\/p>\n

Now, with Bitmain\u2019s hard fork announcement, it seems there could be a third part to the split \u2026 sort of.<\/p>\n

Bitmain refers to its announced hard fork as a \u201cUAHF\u201d or User Activated Hard<\/em> Fork. While perhaps a clever play on UASF, this is not a very accurate term because the \u201ccontingency plan\u201d will actually be very explicitly activated by Bitmain \u2014 and Bitmain alone.<\/p>\n

Moreover, use of the term \u201chard fork\u201d is questionable in this context as well. Originally<\/a>, at least, the term referred to a change to the Bitcoin protocol that makes previously invalid blocks or transactions valid. But for it to be a change to the Bitcoin <\/em>protocol, it arguably at the very least requires the Bitcoin ecosystem to follow these new rules. Under Bitmain\u2019s own stated condition this wouldn\u2019t be the case, at least not to the full extent. <\/p>\n

Rather, the \u201cUAHF\u201d will only be launched in response to a successful<\/em> BIP148 UASF. It is thus more or less assumed that not everyone will adopt the new rules, which indeed seems likely. Technically, at least, Bitmain\u2019s \u201chard fork\u201d would be better described as the creation of an entirely new coin that shares a common history with Bitcoin.<\/p>\n

For purposes of this article, Bitmain\u2019s version of Bitcoin will be called \u201cBitmain\u2019s Bitcoin.\u201d<\/p>\n

Bitmain\u2019s Bitcoin<\/h3>\n

So what. specifically, will Bitmain\u2019s Bitcoin look like?<\/p>\n

Bitmain announced it will create Bitmain\u2019s Bitcoin exactly 12 hours and 20 minutes after the UASF activation, though this is configurable. At that specific point in time, under Bitmain\u2019s new rules, a block must<\/em> be included in the blockchain that\u2019s bigger than one megabyte. This will automatically \u201csplit\u201d the chain \u2014 or create a new chain depending on how you look at it. All existing full Bitcoin nodes would reject this block and ignore this chain, and would continue to follow the chain adhering to Bitcoin\u2019s current consensus rules. <\/p>\n

From that point on, Bitmain will first mine on Bitmain\u2019s Bitcoin chain privately for three days. After these three days, Bitmain will \u201cofficially\u201d launch Bitmain\u2019s Bitcoin to the public if three circumstances are met. <\/p>\n

First off, the BIP148 UASF must have been successful enough to have gained significant hash rate. Second, there must be strong market demand for Bitmain\u2019s Bitcoin. And third, the non-BIP148 side of the split must not be doing great, comparatively.<\/p>\n

Then, if launched, Bitmain\u2019s Bitcoin will accept bigger blocks. The statement mentions an initial limit of up to 8 megabytes, though this is slightly ambiguous as the same blog post mentions there will be \u201cno hard-coded consensus rule\u201d at all. The hardware manufacturer does add that miners should impose a \u201csoft limit\u201d of less than 2 megabytes, which is really more like a recommendation. Additionally, Bitmain writes that there will be a new protocol limit on \u201csigops,\u201d which, in short, should counter some potential attack vectors<\/a> on bigger blocks that could otherwise significantly slow down propagation times. <\/p>\n

For the longer term, Bitmain lays out a \u201cfuture roadmap\u201d that includes a version of Segregated Witness<\/a>, Extension Blocks<\/a>, Bitcoin NG<\/a>, Lumino<\/a>, Schnorr signatures<\/a>, Weak Blocks<\/a>, and Bitcoin Unlimited<\/a>-inspired base block size increases up to almost 17 megabytes in two years. Overall, this \u201cfuture roadmap\u201d part of the announcement does not seem very concrete yet, however. <\/p>\n

What This Means for You, and What This Means for Bitcoin <\/h3>\n

The good news is that anyone who holds bitcoins (meaning: their private keys) at the time of a split will receive coins on both (or all) sides of the chain. In other words, you will get free “Bitmain bitcoins”, which you can keep, sell or spend as long as someone is willing to accept them as payment. Bitmain will even implement replay protection on Bitmain\u2019s Bitcoin, which means that there should be no risk of accidentally spending the same (copied) coin on both chains.<\/p>\n

From a broader Bitcoin and scaling perspective, the chances of BIP148\u2019s success may have actually increased, due to this announcement. If Bitmain follows through on their blog post, it means the company will take hash power that could have otherwise frustrated the UASF \u201coff the table,\u201d to mine on Bitmain\u2019s Bitcoin chain. As a result, there is a greater chance that BIP148 miners will claim the longest chain versus non-BIP148 miners, avoiding a coin-split on the original blockchain. Additionally, Bitmain\u2019s blog post seems to have angered some Bitcoin users that were so far undecided, further increasing support for BIP148.<\/p>\n

The other scaling proposal in the running is SegWit2x, which is also supported by Bitmain. SegWit2x code should, according to its timeline<\/a>, be up and running before August 1st. If that deadline is met, it may or may not prevent a coin-split in the first place, depending on its compatibility with the BIP148 UASF. But since this proposal has been mostly developed in private, the status of this project \u2014 as well as its (in)compatibility with Bitmain\u2019s \u201ccontingency plan\u201d \u2014 remains largely unclear.<\/p>\n

And of course, in the end, it’s possible that neither BIP148, nor SegWit2x, nor Bitmain’s Bitcoin will gain much traction. Status quo could prevail, in which case not much would change at all.<\/p>\n","protected":false},"excerpt":{"rendered":"

Bitmain today announced that it may launch a \u201chard fork\u201d in response to the upcoming BIP148 user activated soft fork (UASF).<\/p>\n","protected":false},"author":2509,"featured_media":23643,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[35],"tags":[1687,197,1964,705,1079,2259,2341],"class_list":["post-23642","post","type-post","status-publish","format-standard","has-post-thumbnail","category-technical","tag-bips","tag-bitmain","tag-hard-fork","tag-scaling","tag-segwit","tag-softfork","tag-uasf"],"author_data":{"id":2509,"name":"Aaron van Wirdum","nicename":"aaron-van-wirdum","avatar_url":"https:\/\/bitcoinmagazine.com\/wp-content\/uploads\/2024\/12\/aaron-van-wirdum-96x96.jpg"},"featured_image_url":"https:\/\/bitcoinmagazine.com\/wp-content\/uploads\/2024\/11\/bitmain-responds-to-uasf-with-another-bitcoin-hard-fork-announcement.jpg","_links":{"self":[{"href":"https:\/\/bitcoinmagazine.com\/wp-json\/wp\/v2\/posts\/23642","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/bitcoinmagazine.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/bitcoinmagazine.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/bitcoinmagazine.com\/wp-json\/wp\/v2\/users\/2509"}],"replies":[{"embeddable":true,"href":"https:\/\/bitcoinmagazine.com\/wp-json\/wp\/v2\/comments?post=23642"}],"version-history":[{"count":0,"href":"https:\/\/bitcoinmagazine.com\/wp-json\/wp\/v2\/posts\/23642\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/bitcoinmagazine.com\/wp-json\/wp\/v2\/media\/23643"}],"wp:attachment":[{"href":"https:\/\/bitcoinmagazine.com\/wp-json\/wp\/v2\/media?parent=23642"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/bitcoinmagazine.com\/wp-json\/wp\/v2\/categories?post=23642"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/bitcoinmagazine.com\/wp-json\/wp\/v2\/tags?post=23642"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}