public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net,
	Gavin Andresen <gavinandresen@gmail.com>
Subject: Re: [Bitcoin-development] 0.8.1 plan
Date: Sun, 17 Mar 2013 15:29:37 +0000	[thread overview]
Message-ID: <201303171529.39725.luke@dashjr.org> (raw)
In-Reply-To: <CALxyHsXqoCPSc43ty-A6FLw6Z1+MVA9LjbrOOMG6tef4N8Qobg@mail.gmail.com>

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



      parent reply	other threads:[~2013-03-17 15:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-17  1:13 [Bitcoin-development] 0.8.1 plan Gavin Andresen
2013-03-17  2:03 ` Alan Reiner
2013-03-17  2:20   ` Frank F
2013-03-17  2:31     ` Gavin Andresen
2013-03-17 15:29     ` Luke-Jr [this message]

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=201303171529.39725.luke@dashjr.org \
    --to=luke@dashjr.org \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=gavinandresen@gmail.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