From: Gregory Maxwell <gmaxwell@gmail•com>
To: Jeff Garzik <jgarzik@exmulti•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Upcoming network event: block v2 lock-in
Date: Sat, 23 Mar 2013 12:18:03 -0700 [thread overview]
Message-ID: <CAAS2fgTq2xz6P1C8kk_HrWsKcJ8rsDSzF_4ceRS+ympj7K-SCA@mail.gmail.com> (raw)
In-Reply-To: <CA+8xBpfzNYqFm-zCD8L7KDiL9x+ez-pUM3B3T981D1n69t8gQQ@mail.gmail.com>
On Sat, Mar 23, 2013 at 10:47 AM, Jeff Garzik <jgarzik@exmulti•com> wrote:
> On Sat, Mar 23, 2013 at 1:43 PM, Luke-Jr <luke@dashjr•org> wrote:
>> Not for producing coinbases (where BIP 34 is implemented).
> Sure, that is largely the pool server layer. But it is misleading to
> imply that bitcoind is nowhere in the stack.
You're both right: BIP34's addition of the height is implemented in
the coinbase generator, so for almost everyone the Bitcoind version is
not very relevant for that. Rejection of invalid chains, however, is
in the Bitcoin daemon. Upgrading bitcoind alone should be sufficient
to prevent the creation of forks, though if miners would like to avoid
losing income they must update _both_ so that they don't create
invalid blocks or mine on invalid forks.
prev parent reply other threads:[~2013-03-23 19:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-23 16:16 Jeff Garzik
2013-03-23 17:09 ` 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 [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=CAAS2fgTq2xz6P1C8kk_HrWsKcJ8rsDSzF_4ceRS+ympj7K-SCA@mail.gmail.com \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jgarzik@exmulti$(echo .)com \
/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