{"id":37186,"date":"2017-06-04T08:41:49","date_gmt":"2017-06-04T05:41:49","guid":{"rendered":"https:\/\/forklog.com\/en\/?p=37186"},"modified":"2025-08-29T13:38:47","modified_gmt":"2025-08-29T10:38:47","slug":"what-is-a-user-activated-soft-fork-uasf","status":"publish","type":"post","link":"https:\/\/forklog.com\/en\/what-is-a-user-activated-soft-fork-uasf\/","title":{"rendered":"What is a user-activated soft fork (UASF)?"},"content":{"rendered":"
\n
\n

1<\/span><\/p>\n

What is a user-activated soft fork (UASF)?<\/strong><\/p>\n

The acronym UASF stands for User Activated Soft Fork. A UASF is a mechanism by which a soft fork is enforced on a specified date, set by the network\u2019s full nodes. The concept requires substantial industry support and coordination, hence it is also described as the economic majority model.<\/div>\n<\/div>\n
\n

2<\/span><\/p>\n

What is a soft fork?<\/strong><\/p>\n

There are two main types of code modification: soft forks and hard forks. The former is a \u201csoft\u201d change; the latter a \u201chard\u201d one. With a soft fork, the change of rules does not require all clients (software) to upgrade to remain compatible with the new rules. If nodes in the network do not adopt the new rules, they can still interoperate with nodes that do. ForkLog has covered this in more detail previously.<\/div>\n<\/div>\n
\n

3<\/span><\/p>\n

How does UASF differ from other activation methods?<\/strong><\/p>\n

The key difference is that significant code changes are usually activated via MASF (Miner Activated Soft Fork), a mechanism in which a majority of miners signal readiness for the upgrade.<\/div>\n<\/div>\n
\n

4<\/span><\/p>\n

How is UASF related to Segregated Witness?<\/strong><\/p>\n

In March 2017 the user-activated soft fork concept was combined with activating Segregated Witness<\/a> (SegWit), a Bitcoin protocol upgrade aimed at optimising block capacity. It lays the groundwork for future scaling solutions. The proposal is known as BIP 148<\/a>.<\/div>\n<\/div>\n
\n

5<\/span><\/p>\n

Why was this combination needed?<\/strong><\/p>\n

The SegWit soft fork (BIP 9), included in the Bitcoin Core codebase, faced a hurdle: it could be locked in and activated only with 95% of miners\u2019 hash power signalling support. Owing to competing visions for Bitcoin\u2019s development, a portion of miners with substantial hash power successfully blocked activation. At the same time, a large part of the industry \u2014 including payment processors, wallet providers and miners \u2014 believed activating SegWit was the correct course.<\/div>\n<\/div>\n
\n

6<\/span><\/p>\n

How does BIP 148 work?<\/strong><\/p>\n

\n

BIP 148 can be described as a non-standard UASF: it is intended to trigger SegWit activation in existing software but, beyond full-node operators\u2019 efforts, also requires miners\u2019 participation. The unusual aspect is that nodes typically begin enforcement on a pre-set flag day. However, more than 80% of the network had already upgraded node software, signalling support for SegWit.<\/p>\n

From 1 August 2017, miners must signal readiness for SegWit by creating blocks with version bit 1. This will cause all SegWit-active nodes to begin enforcing the protocol.<\/p>\n<\/div>\n<\/div>\n

\n

7<\/span><\/p>\n

What would happen to the Bitcoin network if BIP 148 is rejected?<\/strong><\/p>\n

As noted above, BIP 148 requires support from the economic majority, especially exchanges and wallets. Otherwise, node software with BIP 148 support should not be run after 1 August, as this would lead to a chain split, resulting in BIP 148 being abandoned. At the same time, there are strong economic incentives for nodes to interoperate and remain in consensus to prevent a split.<\/div>\n<\/div>\n
\n

8<\/span><\/p>\n

What would happen to the Bitcoin network if BIP 148 activates?<\/strong><\/p>\n

If the economic majority as of 1 August signals support for BIP 148, miners will have strong incentives to adopt it. Otherwise, the economic majority will reject their blocks, and miners would in effect be producing an altcoin not recognised by users or exchanges.<\/div>\n<\/div>\n
\n

9<\/span><\/p>\n

What other scenarios are possible?<\/strong><\/p>\n

\n

\u2022 If miners activate SegWit before 1 August, BIP 148 will not apply. All users will remain on the same chain, regardless of the client they use.<\/p>\n

\u2022 If miners do not activate SegWit, a chain split may occur, with different users seeing different sets of transactions.<\/p>\n

\u2022 If a majority of miners adopts BIP 148, any split will be temporary; eventually all clients will see one chain, and SegWit will be activated for all SegWit-compatible clients (Bitcoin Core 0.13.1 and above).<\/p>\n

\u2022 If a majority of miners does not adopt BIP 148, users who accept BIP 148 and those who do not will diverge.<\/p>\n

\u2022 If a majority of miners starts supporting BIP 148 after 1 August, the chain not following BIP 148 rules may later be reorganised, while the BIP 148 chain gains more support and becomes dominant. In that case, users running a BIP 148 client can be confident, but users on legacy clients may face a \u201crewrite of history\u201d and ultimately lose all funds.<\/p>\n<\/div>\n<\/div>\n

\n

10<\/span><\/p>\n

Which companies support UASF BIP 148?<\/strong><\/p>\n

\n

Data as of 1 June 2017<\/em><\/p>\n

Miners: Bitfury, Bitcoin India, LightningASIC, Slush Pool.<\/p>\n

Wallets: Electrum (ready), Samourai Wallet, Coinkite, Coinomi, GreenAddress, Ledger Wallet, Trezor (ready), Mycelium.<\/p>\n

Exchanges and financial services: Abra, Bitfinex, Vaultoro, Prasos, Bylls, MojBitcoin, Bittylicious, Satoshi Counter.<\/p>\n

Other companies and services: Bitcoin Embassy, BitCoinReminder, BitKong, Bitrefill, Microsoft, Stampery, Walltime.<\/p>\n<\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

1 What is a user-activated soft fork (UASF)? The acronym UASF stands for User Activated Soft Fork\u2014a mechanism by which full nodes set a date to enforce new rules, relying on broad industry support, the so-called economic majority. 2 What is a soft fork? There are two main types of code change: soft forks and hard forks; with a soft fork, non-upgraded nodes can still interoperate with upgraded ones.<\/p>\n","protected":false},"author":1,"featured_media":37187,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"select":"1","news_style_id":"1","cryptorium_level":"2","_short_excerpt_text":"","creation_source":"human_written","_metatest_mainpost_news_update":false,"footnotes":""},"categories":[2113],"tags":[2115,18,459,1134],"class_list":["post-37186","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cryptorium","tag-101-technical-foundations","tag-bitcoin","tag-softfork","tag-technical-updates"],"aioseo_notices":[],"amp_enabled":true,"views":"34","promo_type":"1","layout_type":"1","short_excerpt":"","is_update":"","_links":{"self":[{"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/posts\/37186","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/comments?post=37186"}],"version-history":[{"count":1,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/posts\/37186\/revisions"}],"predecessor-version":[{"id":37188,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/posts\/37186\/revisions\/37188"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/media\/37187"}],"wp:attachment":[{"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/media?parent=37186"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/categories?post=37186"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/tags?post=37186"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}