> Well, he did make the bitcoin.org/may15.html page already. It would be crazy
> to change that now.
Not crazy, just inconvenient, and possibly confusing.
I'm going to be pretty stubborn about the dates. I'm just not
interested in lots of discussion about what the perfect times/dates
will be, the
On Sat, Mar 16, 2013 at 9:03 PM, Alan Reiner wrote:
> On 03/16/2013 09:13 PM, Gavin Andresen wrote:
> > I chose May 15 arbitrarily; two months seems like a reasonable 'quick'
> > amount of time to give people to upgrade/workaround.
> >
>
> Maybe you should wait until after the Bitcoin Conference
On 03/16/2013 09:13 PM, Gavin Andresen wrote:
> I chose May 15 arbitrarily; two months seems like a reasonable 'quick'
> amount of time to give people to upgrade/workaround.
>
Maybe you should wait until after the Bitcoin Conference -- if something
goes wacky on May 15th but then everyone is getti
Here's the plan for the 0.8.1 release:
A new CheckBlock() rule, in effect until 15 May, that ensure only
blocks compatible with old releases are accepted into the main chain
(only blocks that touch 4,500 or fewer distinct txids are allowed).
A limit of 500k to blocks created, also in effect until
Hardware mining rigs do not need updating - they all are designed to connect
directly to a pool and it is the pool that makes all block related decisions.
All the miner, or as I prefer to call them hasher, sees is an 80 byte block
header and possibly with stratum and getblocktemplate enough othe
>> Bitcoin version 0.8.0 is safe to use for everything EXCEPT creating blocks.
>>
>> So: safe for everybody except solo miners / pool operators.
>
> And even solo miners / pool operators can use it if connected to the network
> only through a 0.7 node.
I'll go ahead and use 0.8.x since it will be
6 matches
Mail list logo
