Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
Alerts: BIP148/91: update with post-91 disruption risk #1698
Conversation
harding
and others
added some commits
Jul 21, 2017
|
@harding This is great, thanks for working on this - no arguments here. ;) Unless others object, this will be merged at 18:00 UTC today. |
wbnns
added
the
Merge Scheduled
label
Jul 21, 2017
wbnns
self-assigned this
Jul 21, 2017
wbnns
merged commit 1064f91
into
bitcoin-dot-org:master
Jul 21, 2017
1 check passed
Mai99k
commented on f7cade5
Jul 23, 2017
Mai99k
replied
Jul 23, 2017
|
title: "Potential network disruption" |
097589542
reviewed
Jul 23, 2017
find errors whole system fix put on constant maintenance schedule true only geniuine software hardware updates only!!!!$$$
| bannerclass: "warning" | ||
| --- | ||
| {% assign start='<span class="date">2017/08/01 00:00 UTC</span>' %} | ||
| -*Last updated: <span class="date">2017/07/13 11:21 UTC</span>. This |
harding commentedJul 21, 2017
It appears that many miners, perhaps 50% or more, "false signaled" for BIP91, meaning they set their versionbits manually without running either Core+BIP91 patch or Btc1. If they continue doing this, this means that they may build on top of BIP91-invalid blocks on or after block 477120. BIP91-compliant miners may then orphan those blocks. Spy mining aggravates this situation.
This short update describes the minimal problem and response. I've clicked the box to "allow edits from maintainers" so that @wbnns can make whatever edits he thinks are appropriate without him and I needing to argue about it.