From: Pieter Wuille <pieter.wuille@gmail.com>
To: Tier Nolan <tier.nolan@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Miners: You'll (very likely) need to upgrade your Bitcoin Core node soon to support BIP66
Date: Sat, 13 Jun 2015 15:01:12 +0200 [thread overview]
Message-ID: <CAPg+sBhNSuyctyuRvMYd9gDcjfGwxj=nhY56nSDhCtwp7rJxdw@mail.gmail.com> (raw)
In-Reply-To: <CAE-z3OXMp6494BXeD0FcKPSriHHr+F6grH=tdhk45Ni1+FQ6ZQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 290 bytes --]
On Fri, Jun 12, 2015 at 10:37 AM, Tier Nolan <tier.nolan@gmail.com> wrote:
> Once the 75% threshold is reached, miners who haven't updated are at risk
> of mining on invalid blocks.
>
Note that we've been above the 75% threshold since june 7th (before Peter's
main was sent).
--
Pieter
[-- Attachment #2: Type: text/html, Size: 685 bytes --]
prev parent reply other threads:[~2015-06-13 13:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-12 0:40 [Bitcoin-development] Miners: You'll (very likely) need to upgrade your Bitcoin Core node soon to support BIP66 Peter Todd
2015-06-12 8:37 ` Tier Nolan
2015-06-13 13:01 ` Pieter Wuille [this message]
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='CAPg+sBhNSuyctyuRvMYd9gDcjfGwxj=nhY56nSDhCtwp7rJxdw@mail.gmail.com' \
--to=pieter.wuille@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=tier.nolan@gmail.com \
/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