public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
* [Bitcoin-development] Block Size Increase
@ 2015-05-06 22:12 Matt Corallo
  2015-05-06 22:30 ` slush
                   ` (10 more replies)
  0 siblings, 11 replies; 116+ messages in thread
From: Matt Corallo @ 2015-05-06 22:12 UTC (permalink / raw)
  To: Bitcoin Dev

Recently there has been a flurry of posts by Gavin at
http://gavinandresen.svbtle.com/ which advocate strongly for increasing
the maximum block size. However, there hasnt been any discussion on this
mailing list in several years as far as I can tell.

Block size is a question to which there is no answer, but which
certainly has a LOT of technical tradeoffs to consider. I know a lot of
people here have varying levels of strong or very strong opinions about
this, and the fact that it is not being discussed in a technical
community publicly anywhere is rather disappointing.

So, at the risk of starting a flamewar, I'll provide a little bait to
get some responses and hope the discussion opens up into an honest
comparison of the tradeoffs here. Certainly a consensus in this kind of
technical community should be a basic requirement for any serious
commitment to blocksize increase.

Personally, I'm rather strongly against any commitment to a block size
increase in the near future. Long-term incentive compatibility requires
that there be some fee pressure, and that blocks be relatively
consistently full or very nearly full. What we see today are
transactions enjoying next-block confirmations with nearly zero pressure
to include any fee at all (though many do because it makes wallet code
simpler).

This allows the well-funded Bitcoin ecosystem to continue building
systems which rely on transactions moving quickly into blocks while
pretending these systems scale. Thus, instead of working on technologies
which bring Bitcoin's trustlessness to systems which scale beyond a
blockchain's necessarily slow and (compared to updating numbers in a
database) expensive settlement, the ecosystem as a whole continues to
focus on building centralized platforms and advocate for changes to
Bitcoin which allow them to maintain the status quo[1].

Matt

[1] https://twitter.com/coinbase/status/595741967759335426



^ permalink raw reply	[flat|nested] 116+ messages in thread
* Re: [Bitcoin-development] Block Size Increase
@ 2015-05-07 16:54 John Bodeen
  0 siblings, 0 replies; 116+ messages in thread
From: John Bodeen @ 2015-05-07 16:54 UTC (permalink / raw)
  To: bitcoin-development

[-- Attachment #1: Type: text/plain, Size: 333 bytes --]

If the worry about raising the block size will increase centralization,
could not one could imagine an application which rewarded decentralized
storage of block data? It could even be build aside or on top of the
existing bitcoin protocol.

See the Permacoin paper by Andrew Miller:
http://cs.umd.edu/~amiller/permacoin.pdf

Regards

[-- Attachment #2: Type: text/html, Size: 459 bytes --]

^ permalink raw reply	[flat|nested] 116+ messages in thread
* Re: [Bitcoin-development] Block Size Increase
@ 2015-05-08 20:38 Raystonn .
  2015-05-08 20:40 ` Mark Friedenbach
  0 siblings, 1 reply; 116+ messages in thread
From: Raystonn . @ 2015-05-08 20:38 UTC (permalink / raw)
  To: Aaron Voisine; +Cc: Bitcoin Development

[-- Attachment #1: Type: text/html, Size: 2601 bytes --]

^ permalink raw reply	[flat|nested] 116+ messages in thread
* Re: [Bitcoin-development] Block Size Increase
@ 2015-05-08 20:51 Raystonn
  2015-05-08 20:55 ` Mark Friedenbach
  0 siblings, 1 reply; 116+ messages in thread
From: Raystonn @ 2015-05-08 20:51 UTC (permalink / raw)
  To: Mark Friedenbach; +Cc: Bitcoin Development

Replace by fee is what I was referencing.  End-users interpret the old transaction as expired.  Hence the nomenclature.  An alternative is a new feature that operates in the reverse of time lock, expiring a transaction after a specific time.  But time is a bit unreliable in the blockchain

-Raystonn


On 8 May 2015 1:41 pm, Mark Friedenbach <mark@friedenbach.org> wrote:
>
> Transactions don't expire. But if the wallet is online, it can periodically choose to release an already created transaction with a higher fee. This requires replace-by-fee to be sufficiently deployed, however.
>
> On Fri, May 8, 2015 at 1:38 PM, Raystonn . <raystonn@hotmail.com> wrote:
>>
>> I have a proposal for wallets such as yours.  How about creating all transactions with an expiration time starting with a low fee, then replacing with new transactions that have a higher fee as time passes.  Users can pick the fee curve they desire based on the transaction priority they want to advertise to the network.  Users set the priority in the wallet, and the wallet software translates it to a specific fee curve used in the series of expiring transactions.  In this manner, transactions are never left hanging for days, and probably not even for hours.
>>
>> -Raystonn
>>
>> On 8 May 2015 1:17 pm, Aaron Voisine <voisine@gmail.com> wrote:
>>>
>>> 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
>>
>>
>> ------------------------------------------------------------------------------
>> One dashboard for servers and applications across Physical-Virtual-Cloud
>> Widest out-of-the-box monitoring support with 50+ applications
>> Performance metrics, stats and reports that give you Actionable Insights
>> Deep dive visibility with transaction tracing using APM Insight.
>> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>
>

^ permalink raw reply	[flat|nested] 116+ messages in thread
* Re: [Bitcoin-development] Block Size Increase
@ 2015-05-08 21:01 Raystonn
  0 siblings, 0 replies; 116+ messages in thread
From: Raystonn @ 2015-05-08 21:01 UTC (permalink / raw)
  To: Mark Friedenbach; +Cc: Bitcoin Development

[-- Attachment #1: Type: text/html, Size: 1672 bytes --]

^ permalink raw reply	[flat|nested] 116+ messages in thread

end of thread, other threads:[~2015-05-13 11:26 UTC | newest]

Thread overview: 116+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-05-06 22:12 [Bitcoin-development] Block Size Increase 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
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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox