From: 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: Fri, 12 Jun 2015 09:37:17 +0100 [thread overview]
Message-ID: <CAE-z3OXMp6494BXeD0FcKPSriHHr+F6grH=tdhk45Ni1+FQ6ZQ@mail.gmail.com> (raw)
In-Reply-To: <20150612004058.GA14749@muck>
[-- Attachment #1: Type: text/plain, Size: 502 bytes --]
Once the 75% threshold is reached, miners who haven't updated are at risk
of mining on invalid blocks.
If someone produces a version 3 block that violates the new rules, then
miners who haven't upgraded will end up wasting mining power building on
that block.
This could be used as an expensive way to attack miners who haven't
upgraded. It is low risk of happening, since creating an invalid version 3
block costs 25BTC in hashing power and the miner who does it ends up
creating an invalid block.
[-- Attachment #2: Type: text/html, Size: 575 bytes --]
next prev parent reply other threads:[~2015-06-12 8:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-12 0:40 Peter Todd
2015-06-12 8:37 ` Tier Nolan [this message]
2015-06-13 13:01 ` Pieter Wuille
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='CAE-z3OXMp6494BXeD0FcKPSriHHr+F6grH=tdhk45Ni1+FQ6ZQ@mail.gmail.com' \
--to=tier.nolan@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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