{"id":24039,"date":"2017-04-12T15:43:38","date_gmt":"2017-04-12T15:43:38","guid":{"rendered":"http:\/\/ci027cfe6600042697"},"modified":"2025-01-28T18:51:39","modified_gmt":"2025-01-28T18:51:39","slug":"christian-decker-network-improvements-tradeoffs-and-finding-block-size-sweet-spot","status":"publish","type":"post","link":"https:\/\/bitcoinmagazine.com\/technical\/christian-decker-network-improvements-tradeoffs-and-finding-block-size-sweet-spot","title":{"rendered":"Christian Decker on Bitcoin Network Improvements, Tradeoffs and Finding the Block Size \u201cSweet Spot\u201d"},"content":{"rendered":"
<\/div>
<\/figure>\n

At the core of Bitcoin\u2019s scaling debate has been the block<\/a> size limit. For better or worse, the majority of the discussions about scaling in the Bitcoin community have mostly been focused on this one variable.<\/p>\n

As an oversimplification of the current debate: Some would like to see an increase in block size which would enable more on-chain transactions per second; others would like to see the block size limit remain low in an effort to limit the cost of operating a full node while moving some types of payments above the base Bitcoin protocol to secondary layers such as the Lightning Network<\/a> and sidechains<\/a>.<\/p>\n

In early 2016, a research paper was released in which the relationship between increased on-chain capacity and increased costs of operating a full node were explored. The paper, titled On Scaling Decentralized Blockchains<\/em><\/a>, explained that blocks must not exceed 4 megabytes if the goal is to prevent more than 10 percent of the full nodes on the network from being overwhelmed by the demands of the network. This 4 megabyte metric is often brought up during discussions around the proper block size limit for Bitcoin.<\/p>\n

According to Christian Decker, an infrastructure tech engineer at Blockstream<\/a> and one of the co-authors of the paper, Bitcoin network communication has improved over the past few months which, the paper explained, has affected the tradeoffs.<\/p>\n

Bitcoin Magazine<\/em> reached out to Decker to gather more information related to what the Bitcoin network can handle today in terms of block sizes.<\/p>\n

Clearing Up Misconceptions Around the Study<\/strong><\/p>\n

Decker first wanted to clarify a common misconception of the research presented in the paper on scaling decentralized blockchains:<\/p>\n

\u201cOur results are not binary, in that they are not showing a threshold up to which nothing happens and going just beyond [which] bad things start to happen,\u201d Decker explained. \u201cWhat we do is show that there is a tradeoff between block size and the guarantees that confirmations<\/a> give us.\u201d<\/p>\n

According to another paper co-authored by Decker, titled<\/em>Information Propagation on the Bitcoin Network<\/em><\/a>,<\/em> an increasing block size will also increase the blockchain fork rate, which means confirmations in the current version of the blockchain become less reliable for users.<\/p>\n

\u201cWhat we can compute are upper bounds on block size, after which the system will definitely become unstable, e.g., never converge to a unique ledger state,\u201d Decker continued. \u201cHowever the tradeoff between block size, confirmation guarantees, and centralization pressure is continuous: Even small changes have an effect. We show that the tradeoff exists and that it must be taken into consideration, but the decision about what the sweet spot in this tradeoff is, is a political issue and less a technical one. If network participants are happy to have a less decentralized network in exchange for an incremental transaction rate increase, that’s their decision.\u201d<\/p>\n

While Decker said he is convinced that a moderate block size increase is possible without incurring too many negative effects, he also noted that the precedent set by such a move needs to be taken into consideration.<\/p>\n

\u201cThere are natural limits to the size that the network can support, namely our worst case thresholds, beyond which we cannot go,\u201d Decker stated. \u201cAn increase today could signal that in case of block space contention we can always just increase the block size, which is definitely not true.\u201d<\/p>\n

Improvements to the Bitcoin Network<\/strong><\/p>\n

According to Decker, the fundamental analysis provided by On Scaling Decentralized Blockchains<\/em> is still relevant, but there have been incremental improvements achieved over the past few months that have had a noticeable effect on the tradeoffs described in the paper. Decker pointed to Bitcoin Core<\/a> contributor Matt Corallo\u2019s work on the FIBRE relay network<\/a> and Compact Block Relay<\/a> as specific contributors to network communication improvements.<\/p>\n

Decker also runs BitcoinStats.com<\/a> which tracks the efficiency of information propagation around the Bitcoin network. He recently updated the site with new data<\/a> that, in his view, shows the propagation of blocks around the network is much faster than it was before Corallo\u2019s improvements were implemented.<\/p>\n

<\/figure>\n

According to Decker, a comparison of block propagation times between now and one year ago show that a 3 megabyte block today has an equivalent propagation time of a 1 megabyte block from one year ago. It took a 1 megabyte block 6.5 seconds to reach half of the network a year ago, while it takes roughly 2 seconds today. However, Decker added that size increases have increased longtail propagation time, which means it now takes longer for a block to reach every single node on the network.<\/p>\n

\u201cBoth [FIBRE] and [Compact Block Relay] employ forward error correction to reduce the amount of data to be shipped around the world and recombine blocks from multiple sources instead of relying on a single source,\u201d Decker explained. \u201cThis creates geographically distributed seeds from which the blocks are then forwarded to the remaining peers.\u201d<\/p>\n

In the past, Corallo and BTC.com\u2019s Kevin Pan have told Bitcoin Magazine<\/em><\/a> that FIBRE and Compact Block Relay have also led to a decline in the number of empty blocks<\/a> mined on the network.<\/p>\n

What Can Bitcoin Handle Today?<\/strong><\/p>\n

At this time, further analysis on what impact the implemented network improvements have had on Bitcoin\u2019s ability to handle blocks larger than 4 megabytes has not been made available. \u201cI am continually monitoring the network propagation, and need to aggregate them and re-evaluate our analysis,\u201d Decker said.<\/p>\n

\u201cWhat is safe strongly depends on the requirements of the user, the tradeoff is still valid, it just shifted slightly due to the increased efficiency,\u201d Decker added.<\/p>\n

According to Decker, extrapolating a new throughput limit based on the improvements in how efficiently data is shipped around the world may be simplistic. In other words, a threefold improvement in network communication does not necessarily mean the 4 megabytes number in the original paper would be 12 megabytes if it were written today.<\/p>\n

\u201cThese one-time efficiency increases have certainly moved the throughput limit at which bad things definitely happen upwards, but whether it is at 12 megabytes, I’m not sure,\u201d explained Decker. \u201cAs I mentioned, it’s not a binary threshold, just an upper limit, and putting a number on it just does not mean that lower values are safe.\u201d<\/p>\n

In conclusion, Decker added that there are some types of transactions that will never make sense as on-chain transactions due to the intrinsic costs involved. \u201cThere will always be use-cases which are not fit for on-chain payments.\u201d he stated. \u201cThere is also a privacy increase in using off-chain transfers, since they no longer leave a permanent trace in the blockchain.\u201d<\/p>\n

In Decker\u2019s view, off-chain protocols, such as the Lightning Network or Duplex Micropayment Channels<\/a>, are desirable for long-term scalability because they evolve much faster and do not rely on consensus from the entire ecosystem to enable.<\/p>\n

\u201cI think Segregated Witness<\/a> is both a malleability<\/a> fix, enabling these higher level protocols, and a safe block size increase, which does not set the dangerous precedent of just bumping the block size [limit] when there is block size contention,\u201d Decker stated.<\/p>\n","protected":false},"excerpt":{"rendered":"

At the core of Bitcoin\u2019s scaling debate has been the block size limit. For better or worse, the majority of the discussions about scaling in the Bitcoin community have mostly been focused on this one variable. As an oversimplification of the current debate: Some would like to see an increase in block size which would […]<\/p>\n","protected":false},"author":3445,"featured_media":24040,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[35],"tags":[1662,556,287,2604,460,3181,705],"class_list":{"0":"post-24039","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-technical","8":"tag-block-size","9":"tag-blockchain","10":"tag-blockstream","11":"tag-christian-decker","12":"tag-lightning-network","13":"tag-matt-corallo","14":"tag-scaling"},"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\/christian-decker-on-bitcoin-network-improvements.jpg","_links":{"self":[{"href":"https:\/\/bitcoinmagazine.com\/wp-json\/wp\/v2\/posts\/24039","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=24039"}],"version-history":[{"count":0,"href":"https:\/\/bitcoinmagazine.com\/wp-json\/wp\/v2\/posts\/24039\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/bitcoinmagazine.com\/wp-json\/wp\/v2\/media\/24040"}],"wp:attachment":[{"href":"https:\/\/bitcoinmagazine.com\/wp-json\/wp\/v2\/media?parent=24039"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/bitcoinmagazine.com\/wp-json\/wp\/v2\/categories?post=24039"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/bitcoinmagazine.com\/wp-json\/wp\/v2\/tags?post=24039"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}