Author

Topic: UAHF: A contingency plan against UASF (BIP148) (Read 577 times)

hero member
Activity: 574
Merit: 500
User Activated Hard Fork, but who wants a hard fork?

At this point....everyone.
Yes, I'm sure it's the "silent majority", the one which is exclusive to r/btc and doesn't show up in any polls.

I mean with some people it's hard to tell when all they tell you is "I'd prefer not to have BU/Emergent Consensus".   Wink


You do realize UASF is really just a hard fork, and one without miner support, right?
hero member
Activity: 574
Merit: 500
ClaimWithMe - the most paying faucet of all times!
User Activated Hard Fork, but who wants a hard fork?

At this point....everyone.
Yes, I'm sure it's the "silent majority", the one which is exclusive to r/btc and doesn't show up in any polls.

I mean with some people it's hard to tell when all they tell you is "I'd prefer not to have BU/Emergent Consensus".   Wink
sr. member
Activity: 314
Merit: 251
Where does Wu think he's going to sell his new JihanCoins?  To the PBOC?
legendary
Activity: 1708
Merit: 1036
User Activated Hard Fork? But who wants a hard fork?

Just the clowns at Bitmain. It's not a UAHF by the way, it's a MAHF. And apart from the usual handful of shills this proposal is a laughingstock and will be ignored.

The real question is why they are putting it forth. BIP148 support seemed weak until now based on public evidence as regards the all-important mining pools. I'm betting that some major pools are privately telling Bitmain they are sick of being pushed around by Jihan Wu and they are planning to support BIP148. We'll see if I'm right, but otherwise I can't make sense of this announcement.
hero member
Activity: 574
Merit: 500
User Activated Hard Fork, but who wants a hard fork?

At this point....everyone.
jr. member
Activity: 57
Merit: 10
User Activated Hard Fork? But who wants a hard fork?

Edit: which users
hero member
Activity: 574
Merit: 500
https://blog.bitmain.com/en/uahf-contingency-plan-uasf-bip148/

Fresh post from Bitmain. Essentially, NY agreement is full go ahead.
Jump to: