diff options
author | Luke-Jr <luke@dashjr.org> | 2013-03-23 18:27:20 +0000 |
---|---|---|
committer | bitcoindev <bitcoindev@gnusha.org> | 2013-03-23 18:27:40 +0000 |
commit | e7da5c9c94560c1a42388d4c455d33190836bfff (patch) | |
tree | 4b91f72f8d34bfd1c74d396587d23db4a40a548a | |
parent | a2bacbbfb342c22613dd724a5a0311aefc6a2a23 (diff) | |
download | pi-bitcoindev-e7da5c9c94560c1a42388d4c455d33190836bfff.tar.gz pi-bitcoindev-e7da5c9c94560c1a42388d4c455d33190836bfff.zip |
Re: [Bitcoin-development] Upcoming network event: block v2 lock-in
-rw-r--r-- | 4c/86fb2b3e253317fe1c8bc8ddbb62533c638849 | 68 |
1 files changed, 68 insertions, 0 deletions
diff --git a/4c/86fb2b3e253317fe1c8bc8ddbb62533c638849 b/4c/86fb2b3e253317fe1c8bc8ddbb62533c638849 new file mode 100644 index 000000000..60b3a833d --- /dev/null +++ b/4c/86fb2b3e253317fe1c8bc8ddbb62533c638849 @@ -0,0 +1,68 @@ +Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] + helo=mx.sourceforge.net) + by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) + (envelope-from <luke@dashjr.org>) id 1UJTAK-0007N8-Uf + for bitcoin-development@lists.sourceforge.net; + Sat, 23 Mar 2013 18:27:40 +0000 +X-ACL-Warn: +Received: from zinan.dashjr.org ([173.242.112.54]) + by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76) + id 1UJTAJ-00067V-JH for bitcoin-development@lists.sourceforge.net; + Sat, 23 Mar 2013 18:27:40 +0000 +Received: from ishibashi.localnet (unknown [173.170.142.26]) + (Authenticated sender: luke-jr) + by zinan.dashjr.org (Postfix) with ESMTPSA id BD68627A2966; + Sat, 23 Mar 2013 18:27:31 +0000 (UTC) +From: "Luke-Jr" <luke@dashjr.org> +To: Jeff Garzik <jgarzik@exmulti.com> +Date: Sat, 23 Mar 2013 18:27:20 +0000 +User-Agent: KMail/1.13.7 (Linux/3.7.3-gentoo; KDE/4.9.5; x86_64; ; ) +References: <CA+8xBpcwLUt=RBYynbQDwY2Bv1keCPy0pdXP4+8CG-wqvrxOCA@mail.gmail.com> + <201303231751.48969.luke@dashjr.org> + <CA+8xBpdSHxbzSZenTCLrh7yfCWMLXokbdupTkjpU0V2+B1YV3w@mail.gmail.com> +In-Reply-To: <CA+8xBpdSHxbzSZenTCLrh7yfCWMLXokbdupTkjpU0V2+B1YV3w@mail.gmail.com> +X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F +X-PGP-Key-ID: BD02942421F4889F +X-PGP-Keyserver: hkp://pgp.mit.edu +MIME-Version: 1.0 +Content-Type: Text/Plain; + charset="iso-8859-1" +Content-Transfer-Encoding: 7bit +Message-Id: <201303231827.23273.luke@dashjr.org> +X-Spam-Score: -2.5 (--) +X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. + See http://spamassassin.org/tag/ for more details. + -2.5 RP_MATCHES_RCVD Envelope sender domain matches handover relay + domain +X-Headers-End: 1UJTAJ-00067V-JH +Cc: bitcoin-development@lists.sourceforge.net +Subject: Re: [Bitcoin-development] Upcoming network event: block v2 lock-in +X-BeenThere: bitcoin-development@lists.sourceforge.net +X-Mailman-Version: 2.1.9 +Precedence: list +List-Id: <bitcoin-development.lists.sourceforge.net> +List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> +List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> +List-Post: <mailto:bitcoin-development@lists.sourceforge.net> +List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> +List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> +X-List-Received-Date: Sat, 23 Mar 2013 18:27:41 -0000 + +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. + + |