{"id":25636,"date":"2015-12-07T16:45:00","date_gmt":"2015-12-07T16:45:00","guid":{"rendered":"http:\/\/ci027cfe71000e2697"},"modified":"2015-12-07T16:45:00","modified_gmt":"2015-12-07T16:45:00","slug":"gavin-andresen-explains-why-he-prefers-bip-over-bip-1449506700","status":"publish","type":"post","link":"https:\/\/bitcoinmagazine.com\/technical\/gavin-andresen-explains-why-he-prefers-bip-over-bip-1449506700","title":{"rendered":"Gavin Andresen Explains Why He Prefers BIP 101 Over BIP 100"},"content":{"rendered":"
<\/div>
<\/figure>\n

There have been a few proposals to increase the maximum
blocksize<\/a>
in Bitcoin over the past year, but the two plans that are garnering the most attention right now are
Jeff Garzik<\/a>\u2019s
BIP 100<\/a>
and
Gavin Andresen<\/a>\u2019s
BIP 101<\/a>. While Andresen has already implemented his plan in
BitcoinXT<\/a>, Garzik is still working on a formal write-up and the code for BIP 100.<\/p>\n

Andresen shared his thoughts on BIP 100 via an interview on Epicenter Bitcoin<\/em><\/a>. Although he did not seem completely dismissive of the proposal, it\u2019s clear that he would prefer to go with his own idea for increasing the blocksize, which would offer more predictability in regard to where the blocksize limit will be in the future. <\/p>\n

How BIP 100 Works<\/strong><\/p>\n

When asked directly about BIP 100 by Epicenter Bitcoin<\/em>
co-host S\u00e9bastien Couture<\/a>, Andresen was quick to describe the basic way in which the concept is intended to work: <\/p>\n

\u201cJeff [Garzik]\u2019s proposal is that basically the miners get to decide what the next maximum blocksize should be. There\u2019s kind of a regular vote every — on the order of months.\u201d<\/em><\/p>\n

Andresen then discussed both BIP 100 and BIP 101 in terms of which proposal would lead to a larger increase in the blocksize limit. The Bitcoin Foundation<\/a>
chief scientist noted that Garzik\u2019s proposal does not come with an immediate increase after it has been implemented, but this does not necessarily mean that it would limit the size of blocks over the short term: <\/p>\n

\n

[Garzik] starts with the status quo, so he has no jump-up until the first miner vote. It\u2019s more cautious there. I mean, theoretically, miners could double-up — he has a maximum of 32 megabyte blocks — more quickly. So, if miners wanted to and they all voted for the maximum increase every time, we could be at 32 megabytes more quickly than BIP 101, which would probably be OK if the miners are comfortable with that and they think the network can support it, then OK, so be it.\u201d<\/em><\/p>\n<\/blockquote>\n

Is BIP 100 More Conservative?<\/strong><\/p>\n

Due to the unpredictable nature of Garzik\u2019s BIP 100 proposal, it is difficult to tell if the plan would be more or less conservative than Andresen\u2019s BIP 101. Andresen stated: <\/p>\n

\n

Depending on how you look at it, it\u2019s either less conservative or more conservative. It\u2019s probably more conservative.\u201d<\/em><\/p>\n<\/blockquote>\n

If BIP 100 were implemented, it would take a vote from the miners to increase the blocksize limit. In other words, BIP 100 does not increase the blocksize limit by default. It\u2019s also possible that miners could limit the blocksize to a size much smaller than Andresen\u2019s proposed immediate increase to 8 megabytes, which is why some individuals see this proposal as a more conservative approach. On the other hand, miners could vote to increase the maximum blocksize to 32MB in a relatively short period. It is difficult to know which approach would be more conservative without seeing how miners would react to a real-world BIP 100 implementation. <\/p>\n

BIP 101 is More Predictable<\/strong><\/p>\n

The key attribute that Andresen likes about his own plan when compared to BIP 100 is that his comes with a predictable increase in the blocksize limit. He explained the importance of this predictability during his Epicenter Bitcoin<\/em>
interview: <\/p>\n

\n

I don\u2019t like it as much as BIP 101. I don\u2019t really care what the rule is, but I really like predictable rules. I really like rules that are — I know exactly what the maximum blocksize is going to be on, you know, February 15th, 2022. With BIP 101, we know that. It\u2019s set down there in the spec. We know exactly what it\u2019s going to be, in much the same way that we know what the supply of bitcoin is going to be on that date too — pretty much. [Bitcoin founder] Satoshi [Nakamoto]\u2019s very predictable <\/em>
money supply algorithm<\/em><\/p>\n

for introducing new bitcoins is kind of what inspires me to propose that we just have this limit be very predictable so people can plan… You can do some modeling of what I think the demand for transactions is going to be. You might be able to figure out what the fees are likely to be. All those kinds of things are easier to do if you, kind of, fix this rule as opposed to letting it be miner consensus over time.\u201d<\/em><\/p>\n<\/blockquote>\n

The majority of the network hashrate is currently supporting<\/a>
Garzik\u2019s BIP 100 solution via a Coinbase<\/a>
blocksize vote on the network. Having said that, miners are not the only Bitcoin users with a say in the matter. Many bitcoin exchanges, wallet providers, and payment processors, such as Circle<\/a>
and Blockchain.info<\/a>, see value
in Andresen\u2019s BIP 101 — but not necessarily the BitcoinXT fork. Coming to consensus on this matter has proven to be next to impossible up to this point, but it\u2019s possible that we could be approaching a breaking point with all of the recent activity in the debate. <\/p>\n

Photo <\/em>
Web Summit<\/em><\/a><\/p>\n

<\/a><\/p>\n

<\/a>
\/ <\/em>
Flickr(CC)<\/em><\/a><\/p>\n

<\/a><\/p>\n

<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

There have been a few proposals to increase the maximumblocksize in Bitcoin over the past year, but the two plans that are garnering the most attention right now areJeff Garzik\u2019sBIP 100 andGavin Andresen\u2019sBIP 101. While Andresen has already implemented his plan inBitcoinXT, Garzik is still working on a formal write-up and the code for BIP […]<\/p>\n","protected":false},"author":3445,"featured_media":25637,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[35],"tags":[3595,3592,1687,1662,1694,3587,3450,86],"class_list":{"0":"post-25636","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-technical","8":"tag-bip-100","9":"tag-bip-101","10":"tag-bips","11":"tag-block-size","12":"tag-blocks","13":"tag-gavin-andersen","14":"tag-jeff-garzik","15":"tag-miners"},"author_data":{"id":3445,"name":"Kyle Torpey","nicename":"kyle-torpey","avatar_url":"https:\/\/bitcoinmagazine.com\/wp-content\/uploads\/2024\/12\/kyle-torpey-promo-image-96x96.jpg"},"featured_image_url":"https:\/\/bitcoinmagazine.com\/wp-content\/uploads\/2024\/11\/gavin-andresen-explains-why-he-prefers-bip-101-over-bip-100.jpg","_links":{"self":[{"href":"https:\/\/bitcoinmagazine.com\/wp-json\/wp\/v2\/posts\/25636","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/bitcoinmagazine.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/bitcoinmagazine.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/bitcoinmagazine.com\/wp-json\/wp\/v2\/users\/3445"}],"replies":[{"embeddable":true,"href":"https:\/\/bitcoinmagazine.com\/wp-json\/wp\/v2\/comments?post=25636"}],"version-history":[{"count":0,"href":"https:\/\/bitcoinmagazine.com\/wp-json\/wp\/v2\/posts\/25636\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/bitcoinmagazine.com\/wp-json\/wp\/v2\/media\/25637"}],"wp:attachment":[{"href":"https:\/\/bitcoinmagazine.com\/wp-json\/wp\/v2\/media?parent=25636"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/bitcoinmagazine.com\/wp-json\/wp\/v2\/categories?post=25636"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/bitcoinmagazine.com\/wp-json\/wp\/v2\/tags?post=25636"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}