From: Jeff Garzik <jgarzik@bitpay•com>
To: Rusty Russell <rusty@rustcorp•com.au>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Increasing regularity of block times?
Date: Thu, 30 Oct 2014 19:34:12 -0400 [thread overview]
Message-ID: <CAJHLa0OKAq+AdJQF_1Mf3sje-266x_fUm6C+3x9R85agmZ5B9A@mail.gmail.com> (raw)
In-Reply-To: <874mul9met.fsf@rustcorp.com.au>
That's what we do for testnet today: https://en.bitcoin.it/wiki/Testnet
If no block is found for 20 minutes, one minimum-diff block may be mined.
On Thu, Oct 30, 2014 at 7:18 PM, Rusty Russell <rusty@rustcorp•com.au> wrote:
> Hi all,
>
> I've been toying with an algorithm to place a ceiling on
> confirmation latency by allowing weaker blocks after a certain time.
> Hope this isn't noise, but thought someone must have considered this
> before, or know of flaws in the scheme?
>
> Gory details:
> http://rustyrussell.github.io/pettycoin/2014/10/30/More-Regular-Block-Times.html
>
> Thanks,
> Rusty.
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
next prev parent reply other threads:[~2014-10-30 23:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 23:18 Rusty Russell
2014-10-30 23:34 ` Jeff Garzik [this message]
2014-10-30 23:34 ` Gregory Maxwell
2014-10-31 3:31 ` Rusty Russell
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=CAJHLa0OKAq+AdJQF_1Mf3sje-266x_fUm6C+3x9R85agmZ5B9A@mail.gmail.com \
--to=jgarzik@bitpay$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=rusty@rustcorp$(echo .)com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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