public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Peter R <peter_r@gmx•com>
To: Dave Hudson <dave@hashingit•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] "A Transaction Fee Market Exists Without a Block Size Limit"--new research paper suggests
Date: Wed, 5 Aug 2015 15:15:43 -0700	[thread overview]
Message-ID: <7F9283D5-5F0F-4318-BE64-A1C20A5B7606@gmx.com> (raw)
In-Reply-To: <3162BC78-EC0B-4DAA-A472-D143389DDD8A@hashingit.com>

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

Hi Dave,

Thank you for the feedback regarding my paper.  

> The paper is nicely done, but I'm concerned that there's a real problem with equation 4. The orphan rate is not just a function of time; it's also a function of the block maker's proportion of the network hash rate. Fundamentally a block maker (pool or aggregation of pools) does not orphan its own blocks.

With the benefit of hindsight, I think the paper would be stronger if it also analyzed how the model changes (or doesn't) if we assume zero propagation impedance for intra-miner communication, as you suggested (the "you don't orphan your own blocks" idea).  Note that the paper did briefly discuss miner-dependent propagation times in the second paragraph of page 9 and in note 13.  

> In a degenerate case a 100% pool has no orphaned blocks.

Agreed.  In this case there's no information to communicate (since the miner has no peers) and so the Shannon-Hartley limit doesn't apply.  My model makes no attempt to explain this case.  

> Consider that a 1% miner must assume a greater risk from orphaning than, say, a pool with 25%, or worse 40% of the hash rate.

I'd like to explore this in more detail.  Although a miner may not orphan his own block, by building on his own block he may now orphan two blocks in a row.  At some point, his solution or solutions must be communicated to his peers.  And if there's information about the transactions in his blocks to communicate, I think there's a cost associated with that.  It's an interesting problem and I'd like to continue working on it.  

> I suspect this may well change some of the conclusions as larger block makers will definitely be able to create larger blocks than their smaller counterparts.

It will be interesting to see.  I suspect that the main result that "a healthy fee market exists" will still hold (assuming of course that a single miner with >50% of the hash power isn't acting maliciously).  Whether miners with larger value of h/H have a profit advantage, I'm not sure (but that was outside the scope of the paper anyways).  

Best regards,
Peter



>> On 3 Aug 2015, at 23:40, Peter R via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
>> 
>> Dear Bitcoin-Dev Mailing list,
>> 
>> I’d like to share a research paper I’ve recently completed titled “A Transaction Fee Market Exists Without a Block Size Limit.”  In addition to presenting some useful charts such as the cost to produce large spam blocks, I think the paper convincingly demonstrates that, due to the orphaning cost, a block size limit is not necessary to ensure a functioning fee market.  
>> 
>> The paper does not argue that a block size limit is unnecessary in general, and in fact brings up questions related to mining cartels and the size of the UTXO set.   
>> 
>> It can be downloaded in PDF format here:
>> 
>> https://dl.dropboxusercontent.com/u/43331625/feemarket.pdf
>> 
>> Or viewed with a web-browser here:
>> 
>> https://www.scribd.com/doc/273443462/A-Transaction-Fee-Market-Exists-Without-a-Block-Size-Limit
>> 
>> Abstract.  This paper shows how a rational Bitcoin miner should select transactions from his node’s mempool, when creating a new block, in order to maximize his profit in the absence of a block size limit. To show this, the paper introduces the block space supply curve and the mempool demand curve.  The former describes the cost for a miner to supply block space by accounting for orphaning risk.  The latter represents the fees offered by the transactions in mempool, and is expressed versus the minimum block size required to claim a given portion of the fees.  The paper explains how the supply and demand curves from classical economics are related to the derivatives of these two curves, and proves that producing the quantity of block space indicated by their intersection point maximizes the miner’s profit.  The paper then shows that an unhealthy fee market—where miners are incentivized to produce arbitrarily large blocks—cannot exist since it requires communicating information at an arbitrarily fast rate.  The paper concludes by considering the conditions under which a rational miner would produce big, small or empty blocks, and by estimating the cost of a spam attack.  
>> 
>> Best regards,
>> Peter
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists•linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> 


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

  parent reply	other threads:[~2015-08-05 22:15 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-03 15:22 [bitcoin-dev] Eli Dourado on "governance" Gavin Andresen
     [not found] ` <1438640036.2828.0.camel@auspira.com>
2015-08-03 22:21   ` Gavin Andresen
2015-08-04  6:40     ` [bitcoin-dev] "A Transaction Fee Market Exists Without a Block Size Limit"--new research paper suggests Peter R
2015-08-04 18:41       ` Dave Hudson
2015-08-04 21:18         ` Peter Todd
2015-08-04 21:30         ` Gavin Andresen
2015-08-04 21:46           ` Peter Todd
2015-08-05  0:26             ` Milly Bitcoin
2015-08-05  0:40               ` Neil Fincham
2015-08-04 23:37           ` Dave Hudson
2015-08-05 22:15         ` Peter R [this message]
2015-08-05 22:44           ` Dave Hudson
2015-08-05 23:45             ` Tom Harding
2015-08-05  8:33       ` Benjamin
2015-08-05  9:18         ` Hector Chu
2015-08-05  9:57           ` Adam Back
2015-08-05 10:51             ` Hector Chu
2015-08-05 11:07               ` Adam Back
2015-08-05 11:35                 ` Hector Chu
2015-08-05 19:04                   ` Hector Chu
2015-08-05 10:26         ` Peter R
     [not found]       ` <CAAS2fgTzeFnmnr2ScZvf1pDUtF+M3HhF9xo0yhjVPObpqhgz0A@mail.gmail.com>
     [not found]         ` <6ED57388-6EC3-4515-BF3F-E753301537AB@gmx.com>
     [not found]           ` <CAAS2fgRoFna4i-d=hpmz-CpV35VQ=J1aEoTTT6B1oD4f15C1KA@mail.gmail.com>
     [not found]             ` <C8B38FEC-0EF2-483F-9E53-43AB937455A0@gmx.com>
     [not found]               ` <CAAS2fgQjXNTi9Y_YwLg2dR8baYZhvmEjw43ictt749zR2AOEWw@mail.gmail.com>
     [not found]                 ` <6FED5604-4A6F-4CE1-B42E-36626375D557@gmx.com>
     [not found]                   ` <CAAS2fgQ7hRRvRtD8igcZ2aWBmnqre6iM27peCFGxgC8ODb9jgw@mail.gmail.com>
     [not found]                     ` <6BA86443-7534-4AAA-92BC-EC9B1603DE5F@gmx.com>
     [not found]                       ` <CAAS2fgTTZKD9LQHpMmEH0OU=T8Ta7cCaavWzhM1yQ68-MAT8UQ@mail.gmail.com>
     [not found]                         ` <27B16AB4-0DAD-4665-BF08-7A0C0A70D8D8@gmx.com>
     [not found]                           ` <CAAS2fgRm_CSmWgr7CGmBUD0nX+V0fJ8N4TQN01Vchgip9-s6uQ@mail.gmail.com>
     [not found]                             ` <CAAS2fgT+DP+DaoCMG276uF4=Yoi-w40YyNP-RDRG7NQgOmtpGw@mail.gmail.com>
     [not found]                               ` <CAEgR2PGn_SER18sMuKPJJz5RT=1K=346eCm ph5FJQhhoLcV1zw@mail.gmail.com>
     [not found]                                 ` <CAEgR2PGn_SER18sMuKPJJz5RT=1K=346eCmph5FJQhhoLcV1zw@mail.gmail.com>
2015-08-30 20:08                                   ` Peter R
2015-08-30 21:02                                     ` Daniele Pinna
2015-08-04 14:22 ` [bitcoin-dev] Eli Dourado on "governance" Anthony Towns
2015-08-04 18:28   ` Owen
2015-08-05  3:07     ` Eric Lombrozo
2015-08-05  6:32       ` Mashuri Clark
2015-08-05 13:28       ` Mashuri Clark
2015-08-07 16:26 ` Thomas Zander

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=7F9283D5-5F0F-4318-BE64-A1C20A5B7606@gmx.com \
    --to=peter_r@gmx$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=dave@hashingit$(echo .)com \
    /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