<p>According to <a href="https://www.uasf.co/" rel="nofollow noreferrer">UASF Working Group</a></p>
<blockquote>
<h2>What do users need to do to enforce BIP148?</h2>
<p>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.</p>
<p>Users aware of the risks and who want to commit should use clients that enforce BIP148. Users that run full nodes would upgrade to one that enforces BIP148, or run their node behind an upgraded border node. Users of light clients (like mobile wallets) should check with each vendor to see their support for BIP148. We plan on documenting any public responses from wallets regarding BIP148 support.</p>
</blockquote>
<p>This web-page describes the mechanism for any User Activated Soft Fork (UASF)</p>

CC BY-SA 4.0
2018-08-17T15:11:28.707Z
2018-08-17T15:11:28.707Z
2020-06-16T11:10:03.350Z
RedGrittyBrick
<p>I'm not sure about UASF/BIP-148 but should I do something for the activation? Will bitcoin core dev release new version? I do support segwit by the way.</p>

<p>My bitcoind servers are used as a provider of utxo info and accepting signed transaction to broadcast. The wallet and mining feature are not used.</p>

<bip148-uasf>
I run bitcoin core. What should I prepare by August 1st?
zono
# I run bitcoin core. What should I prepare by August 1st?

(Asked by: username_0 on 2017-05-31)

I'm not sure about UASF/BIP-148 but should I do something for the activation? Will bitcoin core dev release new version? I do support segwit by the way.

My bitcoind servers are used as a provider of utxo info and accepting signed transaction to broadcast. The wallet and mining feature are not used.

**Tags:** bip148-uasf


---

## 1 answers

### Answer by username_1 on 2018-08-17. Score: 1

According to [UASF Working Group](https://www.uasf.co/)

> ## What do users need to do to 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.
>
> Users aware of the risks and who want to commit should use clients that enforce BIP148. Users that run full nodes would upgrade to one that enforces BIP148, or run their node behind an upgraded border node. Users of light clients (like mobile wallets) should check with each vendor to see their support for BIP148. We plan on documenting any public responses from wallets regarding BIP148 support.

This web-page describes the mechanism for any User Activated Soft Fork (UASF)


---

