From: Gavin Andresen <gavinandresen@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Difficulty adjustment / time issues
Date: Wed, 14 Sep 2011 16:28:01 -0400 [thread overview]
Message-ID: <CABsx9T2Ot2iErtr48X_QmcZFQOXGH_jWNPrG=Ck6uQXhVXS=QA@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgQOuNKWD09arSzqKxYFRv95q4xyq0Wz4ZkeKdKSWJ-=kA@mail.gmail.com>
> Perhaps better thing to do is to also delay the _forwarding_ of these
> blocks _and_ blocks that extend them, until extended one more time.
Excellent idea, that gets the incentives right.
RE: fixing the root cause with a forking change:
What do other people think? I think it is too high risk for too
little benefit and shouldn't be done until we have a really compelling
reason to introduce a forking change.
The first really compelling reason I can think of is removing the
MAX_BLOCK_SIZE limit (but does something clever to prevent the
rogue-miner-sends-you-a-valid-10Terabyte-block attack).
--
--
Gavin Andresen
next prev parent reply other threads:[~2011-09-14 20:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 15:06 [Bitcoin-development] Difficulty adjustment / time issues Gavin Andresen
2011-09-13 15:15 ` Vladimir Marchenko
2011-09-13 15:54 ` John Smith
2011-09-13 16:24 ` kjj
2011-09-14 14:45 ` Gavin Andresen
2011-09-14 15:43 ` Luke-Jr
2011-09-14 16:06 ` Christian Decker
2011-09-14 19:52 ` Aidan Thornton
2011-09-14 20:09 ` Gregory Maxwell
2011-09-14 20:28 ` Gavin Andresen [this message]
2011-09-14 21:36 ` Alex Waters
2011-09-14 21:51 ` Gregory Maxwell
2011-09-14 22:07 ` theymos
2011-09-14 23:01 ` Luke-Jr
2011-09-13 16:48 ` Luke-Jr
2011-09-14 21:45 ` theymos
2011-11-07 15:02 ` Pieter Wuille
2011-11-07 15:27 ` Luke-Jr
2011-11-07 15:43 ` Pieter Wuille
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='CABsx9T2Ot2iErtr48X_QmcZFQOXGH_jWNPrG=Ck6uQXhVXS=QA@mail.gmail.com' \
--to=gavinandresen@gmail.com \
--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