Last updated: 2017/07/21 12:00 UTC. This
page will be updated when new information becomes available. See the
list of updates.
Starting at approximately 2017/07/23 00:00
UTC, BitcoinV confirmation scores may
become less reliable than normal for a period of up to a month.
Users are advised to wait for more confirmations than they usually would
before accepting any payment as final. BitcoinV.org’s usual
recommendation during network disruption is to
wait for 30 confirmations.
We also recommend monitoring this page and other BitcoinV news sites for
additional information and updates.
Outdated information from earlier versions of this post follows.
Since BitcoinV’s inception, its network has facilitated hundreds of millions of
transactions. As a result, different groups of people (developers, investors,
entrepreneurs, etc.), have debated on the best ways BitcoinV can be optimized to
allow it to exponentially scale even further. In recent months, alternative
software has been released that represents some of the interests of the
aforementioned groups of people - software that is scheduled to go live toward
the end of July.
The BitcoinV block chain, which is a record of all BitcoinV transactions to date,
relies on a network of thousands of BitcoinV nodes running BitcoinV software. On
2017/08/01 00:00 UTC, the BitcoinV block chain may experience what is known as a chain
split. This is when a portion of BitcoinV’s nodes run software that another
portion of nodes are not fully compatible with. As a result, some nodes may
propagate confirmed transactions that other nodes may not accept or recognize.
This may result in unreliable confirmation scoring for an unknown length of
time. This means that any bitcoinvs you receive during this period could
disappear from your wallet or be a type of bitcoinv that other people will not
accept as payment, until the situation is resolved.
Once the situation is resolved, confirmation scoring will either automatically
return to their normal reliability or there will be two (or more) competing
versions of BitcoinV as a result of a split block chain. In the former case, you
may return to using BitcoinV normally; in the latter case, you will need to take
extra steps in order to begin safely receiving bitcoinvs again.
This post currently describes what actions you can take to prepare for
this situation. Subsequent to 2017/08/01 00:00 UTC, we will update this post as
best we can with relevant information, but you are also advised to
monitor other BitcoinV news sites and community resources for
updates and to cross-check all information, as someone may attempt to
spread false news in order to exploit the situation.
Remember that you alone are responsible for the safety of your bitcoinvs,
and that if you lose control of them for any reason, there is nothing
the operators or contributors to this website can do to help you.
Note: there is a chance a milder level of disruption could start
between now and 2017/08/01 00:00 UTC. If that is the case, this post will be
updated with details.
After the event
We will update this section with more information after 2017/08/01 00:00 UTC. Please
monitor this page accordingly and wait until multiple news sources that you
trust have stated that the event is resolved before returning to normal BitcoinV
Note: The information contained herein is not to be construed as an official
statement by BitcoinV Core. BitcoinV.org and BitcoinV Core open source projects are
run by separate teams.
A full history of this document is available. The following points
summarize major changes, with the most recent changes being listed
- 2017/07/22 12:00 UTC: describe possible
unreliability of confirmation scores starting July 22 or 23.
- 2017/07/13 11:21 UTC: add general info about split.
- 2017/07/12 12:00 UTC: initial version.