

If this does not occur, node software supporting BIP148 should not be run after August 1st as it will cause a chain split leading to the abandonment of BIP148. What are the various scenarios that could happen from BIP148?īIP148 requires support from the economic majority, particularly exchanges and wallets.
#Bip65 reference miner update
#Bip65 reference miner upgrade
Users that run full nodes would upgrade to one that enforces BIP148, or run their node behind an upgraded border node. Users aware of the risks and who want to commit should use clients that enforce BIP148. It is recommended that users do not update unless an economic majority commits to updating and users are aware of the risks and mitigations of a failed UASF deployment. What do users need to do to enforce BIP148? For more information on the benefits of SegWit, please visit:. BIP148 is designed to motivate miners to signal for SegWit so that it is activated in a way that even users who are not running BIP148 will get the benefits of the activation of SegWit. A vast majority of the nodes currently deployed are aware of the BIP9 signalling for SegWit. In 2012, P2SH was activated by UASF with a simple flag day.īIP148 was created to avoid having to force most users to upgrade their software. In general, the block signalling mechanism is only supposed to be a coordination method that makes accelerated activation possible. For this reason, the shortened route to SegWit activation is to require blocks to signal for SegWit activation. A new “SegWit UASF” deployment would require all nodes to upgrade again which will take considerable time. However, almost 80% of the network has already upgraded to SegWit capable node software, in anticipation of miner triggered activation. This is not the standard for UASF because normally nodes would just begin enforcement on a given “flag day”. To be clear, BIP148 is a soft fork that requires miners to activate the existing SegWit deployment. What are companies saying about BIP148? CompanyĪdd your business here by creating a pull request (must include public announcement link) Why BIP148 and not a direct flag day UASF for Segwit? Miners must also check blocks prior to their own and ensure that they also signal for SegWit, and only build on those blocks. Link for reference: /programs/bitcoin/files/charts/segwit.html. This will cause all SegWit ready nodes, which make up over 80% of the network, to activate and begin enforcement. What is BIP148?īIP148 is a UASF that is designed to cause the existing SegWit MASF deployment to cause activation in all existing SegWit capable node software (which currently is 80% of the network nodes).įrom August 1st, 2017, miners are required to signal readiness for SegWit by creating blocks with the version bit 1. Overall, if everyone cooperates, this method is very convenient and has been used to successfully activate multiple soft forks in the past such as BIP65 CLTV and BIP112 CSV. The other tradeoff is that the method allows a small number of hash power to veto activation of the soft fork for everyone on the network. For example, this was the case with BIP66, when hashpower indicated they had upgraded when in fact more than 50% had not. If they do not, it can cause various invalid chains on the network. This method is a tradeoff, because it puts trust in the hash power actually enforcing the new rules. This allows for a faster activation time for the soft fork, leaving full nodes to upgrade at their leisure. It’s a mechanism by which miners trigger activation of soft forks when a majority signals the readiness to upgrade. MASF stands for Miner Activated Soft Fork. The UASF concept was combined with SegWit activation in the BIP148 proposal which can be found here: /bitcoin/bips/blob/master/diawiki. In the past, a UASF was successfully carried out to activate the P2SH soft fork (BIP16). A UASF requires a lot of industry support and coordination, which is good practice for eventual hard forks which requires even more industry coordination.

It’s a mechanism where the activation time of a soft fork occurs on a specified date enforced by full nodes, a concept sometimes referred to as the economic majority. UASF stands for User Activated Soft Fork.
