Guest User

Untitled

a guest
Jan 26th, 2016
193
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 32.01 KB | None | 0 0
  1. Forwarded conversation
  2. Subject: [bitcoin-dev] "A Transaction Fee Market Exists Without a Block Size Limit"--new research paper suggests
  3. ------------------------
  4.  
  5. From: Peter R via bitcoin-dev <[email protected]>
  6. Date: Tue, Aug 4, 2015 at 6:40 AM
  7. To: Bitcoin Dev <[email protected]>
  8.  
  9.  
  10. Dear Bitcoin-Dev Mailing list,
  11.  
  12. 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.
  13.  
  14. 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.
  15.  
  16. It can be downloaded in PDF format here:
  17.  
  18. https://dl.dropboxusercontent.com/u/43331625/feemarket.pdf
  19.  
  20. Or viewed with a web-browser here:
  21.  
  22. https://www.scribd.com/doc/273443462/A-Transaction-Fee-Market-Exists-Without-a-Block-Size-Limit
  23.  
  24. 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.
  25.  
  26. Best regards,
  27. Peter
  28.  
  29. _______________________________________________
  30. bitcoin-dev mailing list
  31. https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
  32.  
  33.  
  34. ----------
  35. From: Gregory Maxwell <[email protected]>
  36. Date: Tue, Aug 4, 2015 at 7:42 AM
  37. To: Peter R <[email protected]>
  38.  
  39.  
  40. How could you have written at such length and complexity but ignoring
  41. the simple expident miners have of simply centeralizing their
  42. operation around larger pools to lower their costs-- an activity they
  43. previously performed, in practice, not just theory (which was walked
  44. back by handing them more efficient relay mechenisms) and which is
  45. simple, easy, and which reduces those marginal costs to 0 at the limit
  46. (e.g. all miners served off a particular host) --- after I
  47. specifically called you out on this previously? Doubly so when your
  48. analysis gives provides a framework for analyizing the profitibility
  49. of moving from one point on that income tradeoff graph to another
  50. (e.g. the lost income from failing to centeralize)....
  51. > _______________________________________________
  52. > bitcoin-dev mailing list
  53. > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
  54. >
  55.  
  56. ----------
  57. From: Peter R <[email protected]>
  58. Date: Tue, Aug 4, 2015 at 7:52 AM
  59. To: Gregory Maxwell <[email protected]>
  60.  
  61.  
  62. Hey Greg,
  63.  
  64. The paper does consider more efficient relaying mechanisms. This is what I refer to as the "propagation impedance." Figure 8 shows that the cost of spam blocks decrease considerably with faster block propagation. The first two simplifying assumptions described in the conclusion (p.13, second paragraph) speak to this further, and the first two "topics for further research" in that same paragraph relate to this as well.
  65.  
  66. Best regards,
  67. Peter
  68.  
  69. ----------
  70. From: Gregory Maxwell <[email protected]>
  71. Date: Tue, Aug 4, 2015 at 8:01 AM
  72. To: Peter R <[email protected]>
  73.  
  74.  
  75. On Tue, Aug 4, 2015 at 7:52 AM, Peter R <[email protected]> wrote:
  76. > Hey Greg,
  77. >
  78. > The paper does consider more efficient relaying mechanisms. This is what I refer to as the "propagation impedance." Figure 8 shows that the cost of spam blocks decrease considerably with faster block propagation. The first two simplifying assumptions described in the conclusion (p.13, second paragraph) speak to this further, and the first two "topics for further research" in that same paragraph relate to this as well.
  79.  
  80. I'm aware-- But "use the same pool" is a seperate modality from "use
  81. more efficient transmission"; for one because if all miners do so (or
  82. technically just a simple majority plus a preference to mine on their
  83. own blocks even if later) then I believe your model would have an
  84. impediance of zero which has very different behavior. It also already
  85. exists, e.g. doesn't require new technology. And for any point on
  86. your demand curve you assume the system is operating at, if the size
  87. of blocks can go up, I believe your model shows miners will increase
  88. income by centeralizing (because absent a limit on the supply, a lower
  89. impedance is more profitable).
  90.  
  91.  
  92. A more minor point, perhaps I'm missing it, but you don't seem to
  93. analyize the effect of R/T changing on your model. As you know, in
  94. Bitcoin unless the supply of coins is increased R/T is vanishing and
  95. will geometrically become 0.
  96.  
  97. ----------
  98. From: Gregory Maxwell <[email protected]>
  99. Date: Tue, Aug 4, 2015 at 8:37 AM
  100. To: Peter R <[email protected]>
  101.  
  102.  
  103. On Tue, Aug 4, 2015 at 8:01 AM, Gregory Maxwell <[email protected]> wrote:
  104. > On Tue, Aug 4, 2015 at 7:52 AM, Peter R <[email protected]> wrote:
  105. >> Hey Greg,
  106. >>
  107. >> The paper does consider more efficient relaying mechanisms. This is what I refer to as the "propagation impedance." Figure 8 shows that the cost of spam blocks decrease considerably with faster block propagation. The first two simplifying assumptions described in the conclusion (p.13, second paragraph) speak to this further, and the first two "topics for further research" in that same paragraph relate to this as well.
  108. >
  109. > I'm aware-- But "use the same pool" is a seperate modality from "use
  110. > more efficient transmission"; for one because if all miners do so (or
  111. > technically just a simple majority plus a preference to mine on their
  112. > own blocks even if later) then I believe your model would have an
  113. > impediance of zero which has very different behavior. It also already
  114.  
  115. It occurs to me that I'm perhaps being too understated.
  116.  
  117. "An unhealthy fee market requires a propagation time that grows
  118. asymptotically with block size slower than log Q Using physical
  119. arguments, we can show that this is not possible"
  120.  
  121. Your physical argument is incorrect on several folds. First, if we
  122. miners centralize they can achieve a growth of propagation time of 0.
  123. 0 is less than log(Q), that condition is trivially possible.
  124.  
  125. More generally your invocation of shanon-hartley is misapplied because
  126. you are ignoring the entropy of the signal. Even disregarding the
  127. miners ability to optimize communication by centralizing, no
  128. blocksize-proportional information is /necessarily/ transmitted at the
  129. time a block has been received. For example, imagine if miners only
  130. include transactions that were previously committed to by another,
  131. external, consensus system the concent of the blocks would be known in
  132. advance, and not need to be transmitted. As a more concrete example,
  133. the block relay network today communicates far less than one bit per
  134. bit of blocksize to relay a block (e.g. transmitting a 962597 byte
  135. block using 3804 bytes-- I wonder why instead you did not announce
  136. your discovery that the block relay network has beat the Shanon limit!
  137. :) --- after all, by your metric it can transmit X bits of information
  138. over a channel which has _significantly_ less than X capacity).
  139.  
  140. If miners choose transactions in a way to minimize the transmission
  141. delays there is no physical limit on how small the amount of
  142. information is, and it does not necessarily depend on the blocksize at
  143. all (see e.g. the practice of agreeing on transactions in advance--
  144. e.g. the transmitted transaction proportional data can be the constant
  145. size of 0),
  146.  
  147. ----------
  148. From: Peter R <[email protected]>
  149. Date: Tue, Aug 4, 2015 at 9:27 AM
  150. To: Gregory Maxwell <[email protected]>
  151.  
  152.  
  153. Hi Greg,
  154.  
  155. Thanks for the comments and interest in my paper.
  156.  
  157. > I'm aware-- But "use the same pool" is a seperate modality from "use
  158. > more efficient transmission"; for one because if all miners do so (or
  159. > technically just a simple majority plus a preference to mine on their
  160. > own blocks even if later) then I believe your model would have an
  161. > impediance of zero which has very different behavior. It also already
  162. > exists, e.g. doesn't require new technology. And for any point on
  163. > your demand curve you assume the system is operating at, if the size
  164. > of blocks can go up, I believe your model shows miners will increase
  165. > income by centeralizing (because absent a limit on the supply, a lower
  166. > impedance is more profitable).
  167.  
  168. I agree that lowering the propagation impedance is a profitable strategy. I also agree that if the hash power is all pointed to one "super pool" that the impedance would be zero.
  169.  
  170. > A more minor point, perhaps I'm missing it, but you don't seem to
  171. > analyize the effect of R/T changing on your model. As you know, in
  172. > Bitcoin unless the supply of coins is increased R/T is vanishing and
  173. > will geometrically become 0.
  174.  
  175. I don't, except briefly in the last paragraph of the conclusion. The paper was already quite long and I didn't want to open a can of worms about things a quarter of a century away.
  176.  
  177. > Your physical argument is incorrect on several folds. First, if we
  178. > miners centralize they can achieve a growth of propagation time of 0.
  179. > 0 is less than log(Q), that condition is trivially possible.
  180.  
  181. Good point. I'm implicitly assuming that mining isn't centralized…that information must still be communicated across the network. I thought that was sort of obvious (because that's the 51% scenario will already know about), but I agree I should have spoken to this point in more detail.
  182.  
  183. > More generally your invocation of shanon-hartley is misapplied because
  184. > you are ignoring the entropy of the signal.
  185.  
  186. The "gamma" variable represents the coding gain (the degree to which the blocks can be compressed) and "C" represents the channel capacity. So the term (gamma * C) represents the effective rate than the uncompressed block's propagate at. The actual bit rate is just C.
  187.  
  188. As long as information needs to be communicated across channels, the Shannon-Hartley theorem applies. To what extent the solutions can be compressed (what gamma value can be obtained) is an open research questions, afaik.
  189.  
  190. > I wonder why instead you did not announce
  191. > your discovery that the block relay network has beat the Shanon limit!
  192. > :) --- after all, by your metric it can transmit X bits of information
  193. > over a channel which has _significantly_ less than X capacity).
  194.  
  195. Haha, but I actually do discuss this in two places on page 9. But I agree now that you point it out that I should have explained how the relay network has a higher "gamma" value than the peer-to-peer network, and that's part of the reason why it's propagation impedance is so much lower. I will include this in the next version!
  196.  
  197. Best regards,
  198. Peter
  199.  
  200. ----------
  201. From: Gregory Maxwell <[email protected]>
  202. Date: Tue, Aug 4, 2015 at 9:43 AM
  203. To: Peter R <[email protected]>
  204.  
  205.  
  206. On Tue, Aug 4, 2015 at 9:27 AM, Peter R <[email protected]> wrote:
  207. > Good point. I'm implicitly assuming that mining isn't centralized…that information must still be communicated across the network. I thought that was sort of obvious (because that's the 51% scenario will already know about), but I agree I should have spoken to this point in more detail.
  208.  
  209. Thats orthorgonal-- in that yes, if mining is not decenteralized less
  210. infomration must be communicated (in fact it's a progression, not a
  211. threshold-- the more centeralized the network the less information
  212. will be transmitted even by a naieve system)... but even with complete
  213. decenteralization no information needs to be transmitted at the time a
  214. block is found.
  215.  
  216. > To what extent the solutions can be compressed (what gamma value can be obtained) is an open research questions, afaik.
  217.  
  218. Consider the following scheme (which, we've proposed deploying
  219. previously in varrious forms):
  220.  
  221. Miners volutarily participate in a fast consensus mechenism which
  222. commits to transactions-- it could be a merged mined blockchain (like
  223. the P2Pool chain, which commits to transactions) or something entirely
  224. different. No reward is given for participation in this scheme. In
  225. their Bitcoin blocks miners only include transactions which are at
  226. least 6 blocks deep in that chain, moreover they include all
  227. transactions which are in it, in a determinstic order.
  228.  
  229. Now when they find a block, all the participants will know exactly
  230. which transactions they included, in exactly which order. No matter
  231. how many there were. _No_ information proportal to the transaction
  232. count needs to be communicated to trasmit the block.
  233.  
  234. -
  235. ----------
  236. From: Gregory Maxwell <[email protected]>
  237. Date: Wed, Aug 5, 2015 at 8:50 PM
  238. To: Peter R <[email protected]>
  239.  
  240.  
  241. Peter, It's been over 24 hours since my last message to you-- and I'm
  242. greatly confused by the correspondance which I see you posting on
  243. reddit.
  244.  
  245. I believe in my discussion with you I conveyed a total break of your
  246. paper: I believe demonstrated that your premises were incorrect and do
  247. not support your some of your strongest conclusions.
  248.  
  249. I've been expecting you to come back with a response that you would be
  250. retracting or seriously revising your paper and its conclusions. And
  251. yet I see you continuing to communicate with the public in messages
  252. which suggest you are unaware of these considerations.
  253. (e.g. https://www.reddit.com/r/Bitcoin/comments/3fuz2s/peter_todd_against_gavin_on_the_bitcoindev/cts983w
  254. ).
  255.  
  256. I don't think Peter Todd's response to you was approiate at the
  257. time... but it would be helpful if you didn't demonstrate that he was
  258. actually correct.
  259.  
  260. ----------
  261. From: Peter R <[email protected]>
  262. Date: Wed, Aug 5, 2015 at 9:43 PM
  263. To: Gregory Maxwell <[email protected]>
  264.  
  265.  
  266. Hi Greg,
  267.  
  268. > Peter, It's been over 24 hours since my last message to you-- and I'm
  269. > greatly confused by the correspondance which I see you posting on
  270. > reddit.
  271.  
  272. Sorry for the delay. It was my last day in Annecy and we were swimming and today I was on the train to the Paris airport.
  273.  
  274. >> On Tue, Aug 4, 2015 at 9:27 AM, Peter R <[email protected]> wrote:
  275. >> Good point. I'm implicitly assuming that mining isn't centralized…that information must still >> be communicated across the network. I thought that was sort of obvious (because that's the 51% >> scenario will already know about), but I agree I should have spoken to this point in more detail.
  276. >
  277. > Thats orthorgonal-- in that yes, if mining is not decenteralized less
  278. > infomration must be communicated (in fact it's a progression, not a
  279. > threshold-- the more centeralized the network the less information
  280. > will be transmitted even by a naieve system)... but even with complete
  281. > decenteralization no information needs to be transmitted at the time a
  282. > block is found.
  283.  
  284. I'm not following your logic here. At some point information needs to be transmitted to the miner's peers. This takes a non-zero amount of time according to the Shannon-Hartley theorem. This time has a cost associated with it. What do you disagree with here?
  285.  
  286. To what extent the solutions can be compressed (what gamma value can be obtained) is an open research questions, afaik.
  287.  
  288. > Consider the following scheme (which, we've proposed deploying
  289. > previously in varrious forms):
  290. >
  291. > Miners volutarily participate in a fast consensus mechenism which
  292. > commits to transactions-- it could be a merged mined blockchain (like
  293. > the P2Pool chain, which commits to transactions) or something entirely
  294. > different. No reward is given for participation in this scheme. In
  295. > their Bitcoin blocks miners only include transactions which are at
  296. > least 6 blocks deep in that chain, moreover they include all
  297. > transactions which are in it, in a determinstic order.
  298. >
  299. > Now when they find a block, all the participants will know exactly
  300. > which transactions they included, in exactly which order. No matter
  301. > how many there were. _No_ information proportal to the transaction
  302. > count needs to be communicated to trasmit the block.
  303.  
  304. If zero information related to the transactions needs to be transmitted between peers, then the peers aren't making decisions of their own volition related to the transactions included in a block. If they're not making decisions related to transactions then they're not really "peers" in my opinion. I see this as another example of how a single entity who controls a lot of hash power can do various nasty stuff.
  305.  
  306. What is your definition of a peer? To me, a peer needs to get information from his other peers from which he makes his own independent decisions. This information takes time to communicate. If there's more transactions, there's more information to communicate. The only way this isn't true if I'm not mistaken is if there's no information to communicate related to the transactions in the block. But like I said earlier, in this case then the miner's aren't peers--they're just slaves--and the system is already centralized.
  307.  
  308. > I believe in my discussion with you I conveyed a total break of your
  309. > paper: I believe demonstrated that your premises were incorrect and do
  310. > not support your some of your strongest conclusions.
  311.  
  312. The only objection I've heard that makes sense to me is Dave Hudson's. Can you explain exactly a what point in my paper you disagree with the math, the logic, or the assumptions? How should the math change to make it correct in your opinion?
  313.  
  314. > I've been expecting you to come back with a response that you would be
  315. > retracting or seriously revising your paper and its conclusions. And
  316. > yet I see you continuing to communicate with the public in messages
  317. > which suggest you are unaware of these considerations.
  318. > (e.g. https://www.reddit.com/r/Bitcoin/comments/3fuz2s/peter_todd_against_gavin_on_the_bitcoindev/cts983w
  319. ).
  320. >
  321. > I don't think Peter Todd's response to you was approiate at the
  322. > time... but it would be helpful if you didn't demonstrate that he was
  323. > actually correct.
  324.  
  325. Dave Hudson made what I feel was a valid objection regarding the "you-don't-orphan-your-own-blocks" idea. I agree that my paper doesn't address his objection, but I believe it can be modified to do so without changing the results of the paper (that a healthy fee market exists). Peter Todd echoed something agreeing with Dave, no?
  326.  
  327. Best regards,
  328. Peter
  329.  
  330.  
  331.  
  332.  
  333.  
  334.  
  335. ----------
  336. From: Gregory Maxwell <[email protected]>
  337. Date: Wed, Aug 5, 2015 at 10:29 PM
  338. To: Peter R <[email protected]>
  339.  
  340.  
  341. On Wed, Aug 5, 2015 at 9:43 PM, Peter R <[email protected]> wrote:
  342. > I'm not following your logic here. At some point information needs to be
  343. > transmitted to the miner's peers. This takes a non-zero amount of time
  344. > according to the Shannon-Hartley theorem. This time has a cost associated
  345. > with it. What do you disagree with here?
  346.  
  347. Hm. I thought I gave a sufficiently concrete example. No information
  348. needs to be conveyed at the time a block is found (beyond the fact of
  349. the block, e.g. it's extranonce, which is all constant size); because
  350. the information can have been sent in advance, unboundadly far in
  351. advance is possible in fact.
  352.  
  353. > If zero information related to the transactions needs to be transmitted
  354. > between peers, then the peers aren't making decisions of their own volition
  355. > related to the transactions included in a block. If they're not making
  356. > decisions related to transactions then they're not really "peers" in my
  357. > opinion. I see this as another example of how a single entity who controls
  358. > a lot of hash power can do various nasty stuff.
  359.  
  360. Thats not the example I'm making.
  361.  
  362. (Though the centeralization pressure you're talking about is a
  363. consideration you should have gone into too! -- but I think it's
  364. mostly mooted by the bigger issue I'm raising)
  365.  
  366.  
  367. > What is your definition of a peer? To me, a peer needs to get information
  368. > from his other peers from which he makes his own independent decisions.
  369. > This information takes time to communicate. If there's more transactions,
  370. > there's more information to communicate. The only way this isn't true if
  371. > I'm not mistaken is if there's no information to communicate related to the
  372. > transactions in the block. But like I said earlier, in this case then the
  373. > miner's aren't peers--they're just slaves--and the system is already
  374. > centralized.
  375.  
  376. I think you're stuck thinking in a particular model and I'm not sure
  377. how to break you out of it.
  378.  
  379. For example, I'm about to communicate the whole 40 some gigabytes of
  380. the Bitcoin blockchain to you:
  381.  
  382. 00000000000000001454fdecfdb2b18cc07bf759f759ce4d8cac3301dc98f478
  383.  
  384. As you can see, I was able to do that by communicating only 32bytes--
  385. and amount that I sent you here had no real dependence on the size of
  386. the blockchain.
  387.  
  388. This was possible because our computers had already agreed on the
  389. content of the blockchain before my communication to you happened.
  390.  
  391. Yes, communication did occur-- but not at the time of my transmission,
  392. it happened arbritarily before. This is devistating for your analysis
  393. because you are working exclusively with the increased delay in
  394. transmission as a function of the blocksize as a mechenism for
  395. increasing orphaning resulting in an equlibrium profit maximizing
  396. size. Data which they sent earlier may have some costs to them, but
  397. it does not have a cost in terms of increasing their orphan rate.
  398.  
  399. In that case I used data I didn't choose (the blockchain), but this
  400. works just as well for data I did choose: I could send you a gigabyte
  401. of data right now, then later send you an extranonce to append that
  402. makes the result have a low hash.
  403.  
  404. There are many ways to use this fundimental result, and the relay
  405. network protocol currently uses it in the simplest possible way.
  406. Ultimately, it means that its possible to construct schemes where
  407. miners retain choice but transmit a constant amount of information at
  408. the time of block announcement.
  409.  
  410. ----------
  411. From: Peter R <[email protected]>
  412. Date: Wed, Aug 5, 2015 at 10:49 PM
  413. To: Gregory Maxwell <[email protected]>
  414.  
  415.  
  416. Hi Greg,
  417.  
  418. OK I think I understand what you're saying. I need to think more about it though. One point already: wouldn't this strongly affect the miner's ability to include very recent transactions in a block? A miner receives a transaction with a juicy fee, includes it, and then 1 second later solves the block. New information needs to be communicated to his peers. The more recent TXs included, the more information. Also, I can imagine how your scheme works if everyone agrees ahead of time exactly how they'll build blocks, but I don't see that it works if miner's are free to build blocks how they choose.
  419.  
  420. Off to bed...
  421.  
  422. Best regards,
  423. Peter
  424.  
  425. ----------
  426. From: Tom Harding via bitcoin-dev <[email protected]>
  427. Date: Wed, Aug 5, 2015 at 11:45 PM
  428.  
  429.  
  430. > On 8/5/2015 3:44 PM, Dave Hudson via bitcoin-dev wrote:
  431. > I do suspect that if we were to model this more accurately we might be able to infer the
  432. > "typical" propagation characteristics by measuring the deviation from the expected distribution.
  433.  
  434. The paper models propagation using a single time value that is a function of block size. Modeling the propagation distribution (which is totally separate from the poisson model of block production) would add a lot of complexity and my guess is the outcome would be little changed.
  435.  
  436.  
  437. > On 5 Aug 2015, at 15:15, Peter R <[email protected]> wrote:
  438. > Although a miner may not orphan his own block, by building on his own block he may now orphan
  439. > two blocks in a row. At some point, his solution or solutions must be communicated to his peers.
  440. >
  441. > Why complicate the analysis by assuming that a miner who finds two blocks sequentially does
  442. > not ? publish the first, or that other miners would orphan miner's first block unless both were
  443. > very quick? In general you don't consider anything beyond 1 block in the future, which seems fine.
  444.  
  445.  
  446. 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.
  447. 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).
  448.  
  449. Correcting for non-orphaning of one's own blocks could be as simple as adding a factor (1 - h/H) to equation 4, which it appears would leave hashpower as an independent variable in the results. But at worst, the discussion can be considered to apply directly only to low-hashpower miners right now.
  450.  
  451. Overall, the paper does not predict big changes to per/kb fees or spam costs for the kinds of block sizes being discussed for the immediate future (8MB). But it does conclude that these fees will rise, not fall, with bigger blocks.
  452.  
  453. Also it is welcome that this paper actually mentions the bitcoin exchange rate as a factor in relation to block size (it points out that a spam attack is much more expensive in fiat terms today than it was years ago).
  454.  
  455. ----------
  456. From: Gregory Maxwell <[email protected]>
  457. Date: Wed, Aug 5, 2015 at 11:50 PM
  458. To: Peter R <[email protected]>
  459.  
  460.  
  461. On Wed, Aug 5, 2015 at 10:49 PM, Peter R <[email protected]> wrote:
  462. > OK I think I understand what you're saying. I need to think more about it though.
  463.  
  464. Understood. Enjoy your travels. (I should have said in my last
  465. message: sorry to nag about response times, I certantly understand.)
  466.  
  467. > One point already: wouldn't this strongly affect the miner's ability to include very recent transactions in a block?
  468.  
  469. It would. Though with the high varience in block finding (e.g. 10
  470. minutes expected but 1 hour blocks happen quite a few times a week) I
  471. don't think e.g. effectively having a second or two delay would be
  472. noticed by users at all. (actually there are already a bunch of delays
  473. in transaction handling that no one seems to care about-- e.g. until
  474. fairly recently each hop added up to 200ms delay just from sleeps in
  475. the networking code; thats part of why decker's propagation numbers
  476. are so high).
  477.  
  478. > A miner receives a transaction with a juicy fee, includes it, and then 1 second later solves the block. New information needs to be communicated to his peers. The more recent TXs included, the more information.
  479.  
  480. Yes, new information needs to be conveyed in that case. At a cost;
  481. although: by using forward error correction we can make it so that the
  482. miner can convey information only proportional to the amount of
  483. missing data they're correcting, without actually knowing which data
  484. is specifically missing.. But all that gets you is a bound on how
  485. many __very__ (e.g.within seconds) new transactions a miner can
  486. profitably include... it's not relevant if the fees are fairly uniform
  487. and there is a backlog.
  488.  
  489. Speaking of backlog, if you're looking for other avenues your work
  490. didn't consider. Think about the incentives of a miner once fees are
  491. larger than subsidy (which is something that could reasonably happen
  492. in just a few years) absent a block size limit. Instead of moving the
  493. chain forward, why doesn't he instead orphan the tip, take all its
  494. transactions and add the new ones that has come in since? It's not
  495. hard to setup a situation where the chain only makes progress when a
  496. miner gets multiple blocks in a row (multiple depending on how much
  497. larger than subsidy the fees are).
  498.  
  499. > Also, I can imagine how your scheme works if everyone agrees ahead of time exactly how they'll build blocks, but I don't see that it works if miner's are free to build blocks how they choose.
  500.  
  501. I was giving a simplified example to make it easier to follow. For
  502. example, even without agreeing on anything except the past history,
  503. each miner can announce their intent to all the other miners (using
  504. hashcash to prevent DOS), the communication overhead for this depends
  505. on how efficient the communication is (e.g. just differential with the
  506. intents of other miners?) but doesn't impact orphaning... if your
  507. intent is taking a long time to communicate you have some penalty how
  508. recent a transaction you can include without a marginal orphaning cost
  509. for that transaction.
  510.  
  511. ----------
  512. From: Peter R <[email protected]>
  513. Date: Thu, Aug 6, 2015 at 7:34 AM
  514. To: Gregory Maxwell <[email protected]>
  515.  
  516.  
  517. Hi Greg,
  518.  
  519. Thank you for your response. I think you bring up some interesting points that readers should be made aware of. Transforming your concerns to the language of my paper, I think you're challenging the claim that "gamma" [the coding gain with which block solutions are transmitted] can not be infinite (cf. Section 7). Indeed, if gamma is infinite then the analysis breaks down.
  520.  
  521. I propose the following changes:
  522.  
  523. 1. I will make it more clear that the results of the paper hinge on the assumption that block solutions are propagated across channels, and that the quantity of pure information communicated per solution is proportional to the amount of information contained within the block.
  524.  
  525. 2. I will add a note [unless you ask me not to] something to the effect of "Greg Maxwell challenges the claim that the coding gain cannot be infinite…" followed by a summary of the scenario you described. I will reference "personal communication." I will also run the note by you before I make the next revision public.
  526.  
  527. 3. I will point out that if the coding gain can be made spectacularly high, that the propagation impedance in my model will become very small, and that although a fee market may strictly exist in the asymptotic sense, such a fee market may not be relevant (the phenomena in the paper would be negligible compared to the dynamics from some other effect).
  528.  
  529. 4. [UNRELATED] I also plan to address Dave Hudson's objections in my next revision (the "you don't orphan your own block" point).
  530.  
  531. Lastly, thank you for the note about what might happen when fees > rewards. I've have indeed been thinking about this. I believe it is outside the scope of the present paper, although I am doing some work on the topic. (Perhaps I'll add a bit more discussion on this topic to the present paper to get the reader thinking in this direction).
  532.  
  533. Best regards,
  534. Peter
  535.  
  536. ----------
  537. From: Gregory Maxwell <[email protected]>
  538. Date: Sat, Aug 29, 2015 at 8:32 PM
  539. To: Peter R <[email protected]>
  540.  
  541.  
  542. https://www.reddit.com/r/Bitcoin/comments/3iuz3r/on_the_nature_of_miner_advantages_in_uncapped/cujz46a
  543.  
  544. Again, I am disappointed find you posting on reddit without correcting
  545. factual statements which I know you know to be wrong.
  546.  
  547. E.g. in dpinna's paper, "PeterR has recently proven that unhealthy
  548. fee markets where a miner’s surplus continuously grows with block
  549. space are impossible. This is guarateed by the fact that while the fee
  550. demand curve is asymptotically linear for largeblock sizes (see (3)),"
  551.  
  552. You know that your "proof" of this problematic-- outright false under
  553. the discussion we had, or at least likely of little pratical relevance
  554. under reasonable, pratical assumptions. But you respond to dpinna
  555. agreeing with him and not cautioning him on relying on these
  556. assumptions.
  557.  
  558. ----------
  559.  
  560. From: Daniele Pinna <[email protected]>
  561. Subject: Your Gmaxwell exchange
  562. Date: 29 August, 2015 5:05:33 PM PDT
  563. To: Peter R <[email protected]>
  564.  
  565. Why wouldn't you forward this to me when you've known about me working on extending your work for the past two weeks...
  566.  
  567. Daniele
Advertisement
Add Comment
Please, Sign In to add comment