Re: [Bitcoin-development] Upcoming network event: block v2 lock-in

2013-03-23 Thread Gregory Maxwell
On Sat, Mar 23, 2013 at 10:47 AM, Jeff Garzik wrote: > On Sat, Mar 23, 2013 at 1:43 PM, Luke-Jr 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

Re: [Bitcoin-development] Upcoming network event: block v2 lock-in

2013-03-23 Thread Luke-Jr
On Saturday, March 23, 2013 6:21:32 PM Jeff Garzik wrote: > On Sat, Mar 23, 2013 at 1:51 PM, Luke-Jr 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

Re: [Bitcoin-development] Upcoming network event: block v2 lock-in

2013-03-23 Thread Jeff Garzik
On Sat, Mar 23, 2013 at 1:51 PM, Luke-Jr 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 im

Re: [Bitcoin-development] Upcoming network event: block v2 lock-in

2013-03-23 Thread Jeff Garzik
On Sat, Mar 23, 2013 at 1:09 PM, Luke-Jr wrote: > I don't think anyone is mining using bitcoind 0.7 or later? slush, BTC Guild, ozcoin too I think, several others. -- Jeff Garzik exMULTI, Inc. jgar...@exmulti.com -- Ev

Re: [Bitcoin-development] Upcoming network event: block v2 lock-in

2013-03-23 Thread Luke-Jr
On Saturday, March 23, 2013 5:47:46 PM Jeff Garzik wrote: > On Sat, Mar 23, 2013 at 1:43 PM, Luke-Jr wrote: > > On Saturday, March 23, 2013 5:28:55 PM Jeff Garzik wrote: > >> On Sat, Mar 23, 2013 at 1:09 PM, Luke-Jr wrote: > >> > I don't think anyone is mining using bitcoind 0.7 or later? > >> >

Re: [Bitcoin-development] Upcoming network event: block v2 lock-in

2013-03-23 Thread Jeff Garzik
On Sat, Mar 23, 2013 at 1:43 PM, Luke-Jr wrote: > On Saturday, March 23, 2013 5:28:55 PM Jeff Garzik wrote: >> On Sat, Mar 23, 2013 at 1:09 PM, Luke-Jr wrote: >> > I don't think anyone is mining using bitcoind 0.7 or later? >> >> slush, BTC Guild, ozcoin too I think, several others. > > Not for p

Re: [Bitcoin-development] Upcoming network event: block v2 lock-in

2013-03-23 Thread Luke-Jr
On Saturday, March 23, 2013 5:28:55 PM Jeff Garzik wrote: > On Sat, Mar 23, 2013 at 1:09 PM, Luke-Jr wrote: > > I don't think anyone is mining using bitcoind 0.7 or later? > > slush, BTC Guild, ozcoin too I think, several others. Not for producing coinbases (where BIP 34 is implemented). --

Re: [Bitcoin-development] Upcoming network event: block v2 lock-in

2013-03-23 Thread Luke-Jr
On Saturday, March 23, 2013 4:16:19 PM Jeff Garzik wrote: > Users should not be impacted. Some ancient miners will produce > newly-invalid blocks (v1), that will get ignored. The easy solution > is to mine using a recent bitcoind (0.7 or later). If you are a miner > and need help upgrading to v2

[Bitcoin-development] Upcoming network event: block v2 lock-in

2013-03-23 Thread Jeff Garzik
Once a supermajority (95%) of mining reaches block version 2, nVersion==1 blocks will be rejected. This event seems likely to occur in the next week. Version 2 block specification: https://en.bitcoin.it/wiki/BIP_0034 Watching for the event: http://blockorigin.pfoe.be/top.php The text is at the