From: Jeff Garzik <jgarzik@exmulti.com>
To: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] Upcoming network event: block v2 lock-in
Date: Sat, 23 Mar 2013 12:16:19 -0400 [thread overview]
Message-ID: <CA+8xBpcwLUt=RBYynbQDwY2Bv1keCPy0pdXP4+8CG-wqvrxOCA@mail.gmail.com> (raw)
Once a supermajority (95%) of mining reaches block version 2,
nVersion==1 blocks will be rejected. This event seems likely to occur
in the next week.
Version 2 block specification: https://en.bitcoin.it/wiki/BIP_0034
Watching for the event: http://blockorigin.pfoe.be/top.php The text
is at the bottom:
"We are currently at 100 out of the latest 1000 blocks on version 1
(10.00%) and 899 out of the latest 1000 blocks on version 2 (89.90%)"
Users should not be impacted. Some ancient miners will produce
newly-invalid blocks (v1), that will get ignored. The easy solution
is to mine using a recent bitcoind (0.7 or later). If you are a miner
and need help upgrading to v2, ping us on #bitcoin-dev or
bitcoin-development@lists.sourceforge.net.
--
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com
next reply other threads:[~2013-03-23 16:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-23 16:16 Jeff Garzik [this message]
2013-03-23 17:09 ` [Bitcoin-development] Upcoming network event: block v2 lock-in Luke-Jr
2013-03-23 17:28 ` Jeff Garzik
2013-03-23 17:43 ` Luke-Jr
2013-03-23 17:47 ` Jeff Garzik
2013-03-23 17:51 ` Luke-Jr
2013-03-23 18:21 ` Jeff Garzik
2013-03-23 18:27 ` Luke-Jr
2013-03-23 19:18 ` Gregory Maxwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+8xBpcwLUt=RBYynbQDwY2Bv1keCPy0pdXP4+8CG-wqvrxOCA@mail.gmail.com' \
--to=jgarzik@exmulti.com \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox