public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Luke-Jr" <luke@dashjr.org>
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 18:27:20 +0000	[thread overview]
Message-ID: <201303231827.23273.luke@dashjr.org> (raw)
In-Reply-To: <CA+8xBpdSHxbzSZenTCLrh7yfCWMLXokbdupTkjpU0V2+B1YV3w@mail.gmail.com>

On Saturday, March 23, 2013 6:21:32 PM Jeff Garzik wrote:
> 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.

Transaction selection and everything else bitcoind does, is irrelevant to BIP 
34. It is incompatible with getblocktemplate for coinbase-creating software to 
produce v2 blocks without implementing BIP 34 themselves, even if the upstream 
GBT server specifies it.



  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 [Bitcoin-development] Upcoming network event: block v2 lock-in 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 [this message]
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=201303231827.23273.luke@dashjr.org \
    --to=luke@dashjr.org \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=jgarzik@exmulti.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