From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net,
	Gavin Andresen <gavinandresen@gmail.com>
Date: Sun, 17 Mar 2013 15:29:37 +0000
User-Agent: KMail/1.13.7 (Linux/3.7.3-gentoo; KDE/4.9.5; x86_64; ; )
References: <CABsx9T050Zia=5Xy4fRh_RtjOQzAVi-UPKmhYCuKbdZTF3U7dA@mail.gmail.com>
	<51452473.1040301@gmail.com>
	<CALxyHsXqoCPSc43ty-A6FLw6Z1+MVA9LjbrOOMG6tef4N8Qobg@mail.gmail.com>
In-Reply-To: <CALxyHsXqoCPSc43ty-A6FLw6Z1+MVA9LjbrOOMG6tef4N8Qobg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Message-Id: <201303171529.39725.luke@dashjr.org>
Subject: Re: [Bitcoin-development] 0.8.1 plan
Precedence: list

On Sunday, March 17, 2013 2:20:14 AM Frank F wrote:
> Well, he did make the bitcoin.org/may15.html page already. It would be
> crazy to change that now.

OTOH, the page's recommended config isn't really too ideal. While the new lock 
limit should be good for up to 2 block deep reorgs, I doubt merchants/miners 
want to get stuck if someone pulls off a 3-block deep reorg. Since we usually 
consider 6 blocks to be "confirmed beyond impossibility of reversal", a limit 
of at least 292692 should probably be recommended. Additionally, I suspect 
set_lg_max may need bumping upward - but I'm not quite sure how to calculate 
the correct value there.

Why does the example config do set_lg_dir? That will screw things up should 
the client be using some other directory for any reason..

Also, please add a note that 0.4.x, 0.5.x, 0.6.x, and 0.7.x will be receiving 
backports in their next stable releases sometime before May 15.

Luke