From: Aaron Voisine <voisine@gmail•com>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Block Size Increase
Date: Fri, 8 May 2015 13:17:09 -0700 [thread overview]
Message-ID: <CACq0ZD6Jt2=yw=A8+bgonb3Jb2h2fgEt8aVWNeNvsOpzZr9qrQ@mail.gmail.com> (raw)
In-Reply-To: <1551544.DzLxgCKLBq@coldstorage>
[-- Attachment #1: Type: text/plain, Size: 1386 bytes --]
As the author of a popular SPV wallet, I wanted to weigh in, in support of
the Gavin's 20Mb block proposal.
The best argument I've heard against raising the limit is that we need fee
pressure. I agree that fee pressure is the right way to economize on
scarce resources. Placing hard limits on block size however is an
incredibly disruptive way to go about this, and will severely negatively
impact users' experience.
When users pay too low a fee, they should:
1) See immediate failure as they do now with fees that fail to propagate.
2) If the fee lower than it should be but not terminal, they should see
degraded performance, long delays in confirmation, but eventual success.
This will encourage them to pay higher fees in future.
The worst of all worlds would be to have transactions propagate, hang in
limbo for days, and then fail. This is the most important scenario to
avoid. Increasing the 1Mb block size limit I think is the simplest way to
avoid this least desirable scenario for the immediate future.
We can play around with improved transaction selection for blocks and
encourage miners to adopt it to discourage low fees and create fee
pressure. These could involve hybrid priority/fee selection so low fee
transactions see degraded performance instead of failure. This would be the
conservative low risk approach.
Aaron Voisine
co-founder and CEO
breadwallet.com
[-- Attachment #2: Type: text/html, Size: 1978 bytes --]
next prev parent reply other threads:[~2015-05-08 20:17 UTC|newest]
Thread overview: 116+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 22:12 Matt Corallo
2015-05-06 22:30 ` slush
2015-05-06 23:06 ` Eric Lombrozo
2015-05-06 22:44 ` Tier Nolan
2015-05-06 23:12 ` Matt Corallo
2015-05-06 23:33 ` Tier Nolan
2015-05-06 23:41 ` Matt Corallo
2015-05-07 2:16 ` Peter Todd
2015-05-06 23:11 ` Matt Whitlock
2015-05-06 23:13 ` Matt Corallo
2015-05-07 0:00 ` Tom Harding
2015-05-07 0:07 ` Bryan Bishop
2015-05-07 0:37 ` Gregory Maxwell
2015-05-07 1:49 ` Peter Todd
2015-05-07 3:03 ` Justus Ranvier
2015-05-08 11:02 ` Thomas Zander
2015-05-08 20:17 ` Aaron Voisine [this message]
2015-05-07 3:47 ` Pieter Wuille
2015-05-07 9:25 ` Mike Hearn
2015-05-07 10:12 ` Peter Todd
2015-05-07 10:42 ` Btc Drak
2015-05-07 10:52 ` Jorge Timón
2015-05-07 11:15 ` Andrew
2015-05-07 11:29 ` Mike Hearn
2015-05-07 12:26 ` Jorge Timón
2015-05-07 14:05 ` Mike Hearn
2015-05-07 14:18 ` Bryan Bishop
2015-05-07 14:22 ` Peter Todd
2015-05-07 14:40 ` Peter Todd
2015-05-07 14:52 ` Gavin Andresen
2015-05-07 14:56 ` Peter Todd
2015-05-07 15:04 ` Alex Morcos
2015-05-07 15:09 ` Jeff Garzik
2015-05-07 15:12 ` Mike Hearn
2015-05-07 15:17 ` Jeff Garzik
2015-05-07 15:29 ` Mike Hearn
2015-05-07 15:35 ` Jeff Garzik
2015-05-07 16:18 ` Justus Ranvier
2015-05-07 16:21 ` Jorge Timón
2015-05-07 17:29 ` Peter Todd
2015-05-07 19:37 ` Mike Hearn
2015-05-07 19:44 ` Jérémie Dubois-Lacoste
2015-05-07 20:20 ` Jérémie Dubois-Lacoste
2015-05-07 15:58 ` Matthew Mitchell
2015-05-07 16:47 ` Matthew Mitchell
2015-05-07 17:26 ` Matt Corallo
[not found] ` <CABsx9T2vAQyZODRE9apu0R1n=LybssQcuTYD7P3mAQH_Fv6QCQ@mail.gmail.com>
2015-05-07 17:40 ` [Bitcoin-development] Fwd: " Gavin Andresen
2015-05-07 17:43 ` [Bitcoin-development] " Mike Hearn
2015-05-07 18:03 ` Btc Drak
2015-05-07 18:06 ` Mike Hearn
2015-05-07 18:21 ` Ross Nicoll
2015-05-07 18:40 ` Gavin Costin
2015-05-07 18:46 ` Btc Drak
2015-05-07 19:31 ` Bernard Rihn
2015-05-07 19:31 ` Alan Reiner
2015-05-07 19:54 ` Jeff Garzik
2015-05-07 19:59 ` Justus Ranvier
2015-05-08 1:40 ` Tom Harding
2015-05-08 2:09 ` Jeff Garzik
2015-05-08 5:13 ` Tom Harding
2015-05-08 9:43 ` Mike Hearn
2015-05-08 15:23 ` Alan Reiner
2015-05-08 14:59 ` Alan Reiner
2015-05-08 15:49 ` Jeff Garzik
2015-05-13 10:37 ` Oliver Egginger
2015-05-13 11:25 ` Angel Leon
2015-05-08 17:17 ` Andrew
2015-05-08 17:51 ` Alan Reiner
[not found] ` <CADZB0_bK+YsK8sN-di2pynvjsq5VjSvnEu0-cCGhPqFunyVm7Q@mail.gmail.com>
2015-05-09 12:02 ` Andrew
2015-05-09 12:53 ` Justus Ranvier
2015-05-09 18:33 ` Andrew
2015-05-08 1:51 ` Joel Joonatan Kaartinen
2015-05-08 3:41 ` Peter Todd
2015-05-07 18:38 ` Chris Wardell
2015-05-07 18:55 ` Alex Mizrahi
2015-05-07 18:59 ` Ross Nicoll
2015-05-07 19:03 ` Matt Corallo
2015-05-07 19:13 ` Jeff Garzik
2015-05-07 19:34 ` Mike Hearn
2015-05-07 21:29 ` Matt Corallo
2015-05-07 23:05 ` 21E14
2015-05-07 15:33 ` Jorge Timón
2015-05-07 16:11 ` Mike Hearn
2015-05-07 16:47 ` Jorge Timón
2015-05-07 16:59 ` Gavin Andresen
2015-05-07 17:42 ` Peter Todd
2015-05-07 18:05 ` Jorge Timón
2015-05-07 19:57 ` Btc Drak
2015-05-07 15:39 ` Btc Drak
2015-05-07 13:02 ` Peter Todd
2015-05-07 19:14 ` Matt Corallo
2015-05-07 11:55 ` Dave Hudson
2015-05-07 13:40 ` Jorge Timón
2015-05-08 4:46 ` Tom Harding
2015-05-07 14:04 ` Jeff Garzik
2015-05-07 14:32 ` Peter Todd
2015-05-07 14:38 ` Justus Ranvier
2015-05-07 14:49 ` Peter Todd
2015-05-07 15:13 ` Justus Ranvier
2015-05-07 15:25 ` Peter Todd
2015-05-07 15:04 ` Jeff Garzik
2015-05-07 15:16 ` Justus Ranvier
2015-05-07 15:27 ` Jeff Garzik
2015-05-07 15:33 ` Justus Ranvier
2015-05-07 15:47 ` Jeff Garzik
2015-05-07 15:50 ` Justus Ranvier
2015-05-07 11:20 ` Wladimir J. van der Laan
2015-05-07 11:30 ` Eric Lombrozo
2015-05-07 15:56 ` Jeff Garzik
2015-05-07 16:13 ` Mike Hearn
2015-05-07 16:54 John Bodeen
2015-05-08 20:38 Raystonn .
2015-05-08 20:40 ` Mark Friedenbach
2015-05-08 20:51 Raystonn
2015-05-08 20:55 ` Mark Friedenbach
2015-05-08 21:01 Raystonn
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='CACq0ZD6Jt2=yw=A8+bgonb3Jb2h2fgEt8aVWNeNvsOpzZr9qrQ@mail.gmail.com' \
--to=voisine@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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