From: Gavin Andresen <gavinandresen@gmail.com>
To: Adam Back <adam@cypherspace.org>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] soft-fork block size increase (extension blocks) Re: Proposed alternatives to the 20MB stepfunction
Date: Fri, 29 May 2015 20:16:01 -0400 [thread overview]
Message-ID: <CABsx9T309r6rT+sVtOb0Qmi=PLr+CUGApmLjuXs-_NcMS4K=gg@mail.gmail.com> (raw)
In-Reply-To: <CALqxMTFoMkAmwpMmB9mbAi8rx4B_iH14t=U4XGtpzhjVYLUR+g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 626 bytes --]
RE: soft-forking an "extension block":
So... go for it, code it up. Implement it in the Bitcoin Core wallet.
Then ask the various wallet developer how long it would take them to update
their software to support something like this, and do some UI mockups of
what the experience would look like for users.
If there are two engineering solutions to a problem, one really simple, and
one complex, why would you pick the complex one?
Especially if the complex solution has all of the problems of the simple
one (20MB extension blocks are just as "dangerous" as 20MB main blocks,
yes? If not, why not?)
--
--
Gavin Andresen
[-- Attachment #2: Type: text/html, Size: 869 bytes --]
next prev parent reply other threads:[~2015-05-30 0:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-30 0:00 [Bitcoin-development] soft-fork block size increase (extension blocks) Re: Proposed alternatives to the 20MB stepfunction Adam Back
2015-05-30 0:16 ` Gavin Andresen [this message]
2015-05-30 1:36 Raystonn
2015-05-30 3:27 ` Andrew
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='CABsx9T309r6rT+sVtOb0Qmi=PLr+CUGApmLjuXs-_NcMS4K=gg@mail.gmail.com' \
--to=gavinandresen@gmail.com \
--cc=adam@cypherspace.org \
--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