From: Gavin Andresen <gavinandresen@gmail•com>
To: Peter Todd <pete@petertodd•org>
Cc: bitcoin-development@lists•sourceforge.net
Subject: [Bitcoin-development] Blocksize and off-chain transactions
Date: Wed, 13 Mar 2013 13:01:43 -0400 [thread overview]
Message-ID: <CABsx9T0xOpNpFG4bo7wjcMV8a_xtw_jrRx_fiSutX08yfP8P7Q@mail.gmail.com> (raw)
> The very statement that we're willing to increase the blocksize as our
> solution to increased transaction volume rather go down the path of
> off-chain transactions is incredibly controversial.
I really don't understand this either/or mentality.
OF COURSE we're going to raise the block size limit. Limiting the main
blockchain to single-digit transactions-per-second is not an option,
the vision FOREVER has been to scale it up.
And OF COURSE there will be off-chain transactions-- at the very
least, we need them for "instantly confirmed" transactions.
But lets table that whole discussion until 0.8.1 is out the door.
--
--
Gavin Andresen
next reply other threads:[~2013-03-13 17:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 17:01 Gavin Andresen [this message]
2013-03-13 17:48 ` Peter Todd
2013-03-13 18:01 ` Michael Gronager
2013-03-13 18:08 ` Luke-Jr
2013-03-13 18:28 ` Pieter Wuille
2013-03-13 19:29 ` Roy Badami
2013-03-13 19:43 ` Stephen Pair
2013-03-13 20:14 ` Michael Gronager
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=CABsx9T0xOpNpFG4bo7wjcMV8a_xtw_jrRx_fiSutX08yfP8P7Q@mail.gmail.com \
--to=gavinandresen@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=pete@petertodd$(echo .)org \
/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