From: Rusty Russell <rusty@rustcorp.com.au>
To: "Bitcoin Dev" <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] Increasing regularity of block times?
Date: Fri, 31 Oct 2014 09:48:34 +1030 [thread overview]
Message-ID: <874mul9met.fsf@rustcorp.com.au> (raw)
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.
next reply other threads:[~2014-10-30 23:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 23:18 Rusty Russell [this message]
2014-10-30 23:34 ` [Bitcoin-development] Increasing regularity of block times? Jeff Garzik
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=874mul9met.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=bitcoin-development@lists.sourceforge.net \
/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