From: Jeff Garzik <jgarzik@exmulti•com>
To: Luke-Jr <luke@dashjr•org>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Upcoming network event: block v2 lock-in
Date: Sat, 23 Mar 2013 14:21:32 -0400 [thread overview]
Message-ID: <CA+8xBpdSHxbzSZenTCLrh7yfCWMLXokbdupTkjpU0V2+B1YV3w@mail.gmail.com> (raw)
In-Reply-To: <201303231751.48969.luke@dashjr.org>
On Sat, Mar 23, 2013 at 1:51 PM, Luke-Jr <luke@dashjr•org> wrote:
> bitcoind is nowhere in the implementation of the miner end of BIP 34.
Again, not strictly true.
bitcoind's 'getblocktemplate' RPC call used by some supplies the block
version, selects transactions for the miner, and other tasks integral
to the implementation of the miner and BIP 34.
--
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti•com
next prev parent reply other threads:[~2013-03-23 18:27 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 [this message]
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+8xBpdSHxbzSZenTCLrh7yfCWMLXokbdupTkjpU0V2+B1YV3w@mail.gmail.com \
--to=jgarzik@exmulti$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=luke@dashjr$(echo .)org \
/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