{"id":7824,"date":"2022-07-29T12:00:00","date_gmt":"2022-07-29T12:00:00","guid":{"rendered":"http:\/\/ci02a75a53b0002523"},"modified":"2022-07-29T12:00:00","modified_gmt":"2022-07-29T12:00:00","slug":"luke-dashjr-segwit-bitcoin-independence-day","status":"publish","type":"post","link":"https:\/\/bitcoinmagazine.com\/culture\/luke-dashjr-segwit-bitcoin-independence-day","title":{"rendered":"Bitcoin Independence Day: Luke Dashjr On The Lessons From SegWit That We\u2019re Forgetting"},"content":{"rendered":"
<\/div>

In a year that has been marked by pontification on what it means to be a \u201cBitcoin maximalist,\u201d<\/a> the implosion of numerous centralized \u201ccrypto\u201d projects<\/a> and the excommunication of self-interested Bitcoin influencers<\/a>, Bitcoin Independence Day is worth celebrating more than ever.<\/p>\n

The first Bitcoin Independence Day was slated for August 1, 2017, when Bitcoin users planned to deploy a software upgrade through a user-activated soft fork (UASF) via BIP148<\/a>, which they hoped would mark a community-based victory in the years-long Blocksize War by activating SegWit. This was a change to Bitcoin\u2019s transaction format that was supported by the Bitcoin community at large, but opposed by<\/a> some large mining entities and other ecosystem startups that sought instead to impose a hard fork on the protocol to increase the block size limit.<\/p>\n

The idea of celebrating the August 1 BIP148 flag day as a holiday was more or less meme\u2019d into existence<\/a> by Jan3 CEO Samson Mow, who was an outspoken advocate for the UASF. Bitcoin\u2019s mining community capitulated in the days leading up to this planned inaugural Bitcoin Independence Day, signaling their support for BIP91<\/a> after the BIP148<\/a> UASF enforcing SegWit was already deployed and inevitable. SegWit activated on the Bitcoin network on August 24, 2017<\/a>.<\/p>\n

The spirit of this original UASF rally makes the idea of Bitcoin Independence Day worth remembering, even five years later. Meanwhile, questions about how Bitcoin protocol changes should occur and the role of Bitcoin\u2019s most prominent individuals in influencing its future remain very much unresolved to this day.<\/p>\n

Looking Back At SegWit With Luke Dashjr<\/h2>\n

To reflect on those questions as part of this year\u2019s Bitcoin Independence Day, it may help to travel back to the start with someone who was there. Prominent Bitcoin Core developer Luke Dashjr was one of the first<\/a> to suggest the option of deploying SegWit as a soft fork.<\/p>\n

Dashjr maintains the spirit that was on such prominent display during the Blocksize War. Most recently, that has meant speaking out against the Speedy Trial path for Taproot activation<\/a> despite its general acceptance among much of Bitcoin\u2019s technical community, pointing out that the Speedy Trial method of activation ignored<\/a> consensus developed around the BIP8 method for activating soft forks<\/a>.<\/p>\n

\u201cWe learned some major lessons activating SegWit,\u201d Dashjr recalled while reflecting on the process in an interview for this year\u2019s Bitcoin Independence Day. \u201cUnfortunately, some developers appear to have not<\/em> learned these lessons, and attempted to repeat the same mistakes with Taproot, even going so far as to reject the community consensus around BIP8.\u201d<\/p>\n

Taproot can be seen as Bitcoin\u2019s most significant protocol upgrade since SegWit, but its activation hardly tested the resolve of the Bitcoin community as viciously. The majority of Bitcoin hash rate contributors quickly signaled their support for the popular upgrade<\/a>.<\/p>\n

A \u201cbusiness entity vs. user\u201d standoff never occurred around Taproot activation, and the really existential questions about how consensus can be achieved for changes to Bitcoin were not really answered. In fact, Dashjr pointed out that, if anything, Bitcoin may now be in a worse position to resist the influence of centralized entities, like those who supported SegWit2x<\/a>.<\/p>\n

\u201cSince 2017, the expectations for Bitcoin have grown, but unfortunately Bitcoin itself and its network has shrunk, making it much less secure and borderline centralized,\u201d he said, pointing to data<\/a> showing that the number of Bitcoin nodes has dropped from 200,000 in 2018 to fewer than 50,000 today. \u201cBut over the same time, the need<\/em> for Bitcoin has also grown considerably \u2014 I like to say \u2018too important to allow to fail\u2019 \u2014 and I think ensuring its success despite these difficulties is critical to the future of mankind.\u201d<\/p>\n

Run Your Own Node<\/h2>\n

As the bitcoin price has grown from around $4,400 in August 2017 to more than $20,000 today, it\u2019s clear that the original Bitcoin Independence Day protected the protocol\u2019s path toward mass adoption. But the recent failure of centralized custody providers like Celsius<\/a> demonstrates that genuine Bitcoin independence is not growing at the same clip as this asset adoption.<\/p>\n

\u201cIt\u2019s not enough to get people to buy bitcoins, or for the price to go up,\u201d as Dashjr put it. \u201cAll of Bitcoin\u2019s advantages \u2014 including its security from outright theft and the 21 million BTC cap \u2014 stem from the assumption that the majority of the economy are using their own full nodes to verify payments to them. Centralized verification and third-party\/custodial wallets are a bigger threat to Bitcoin than anything else.\u201d<\/p>\n

Perhaps the greatest legacy of SegWit and the Blocksize War can be in the reminder that for Bitcoin to truly realize its promise, its users must remain as fiercely independent as they proved to be in 2017.<\/p>\n

\u201cIt was an important trial in Bitcoin\u2019s history, for the community to overcome what amounted to a hostile takeover attempt from some powerful elites,\u201d Dashjr recalled. \u201cHad the UASF failed, it would have probably meant the death of Bitcoin and the concept of decentralized currency as a whole. So an annual celebration as Bitcoin Independence Day seems very fitting, and worth participating in.\u201d<\/p>\n","protected":false},"excerpt":{"rendered":"

Five years since the first Bitcoin Independence Day, have we forgotten how Bitcoin survived its most existential threat to date?<\/p>\n","protected":false},"author":2705,"featured_media":7825,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[33],"tags":[2081,422,1140,1079],"class_list":{"0":"post-7824","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-culture","8":"tag-bitcoin-independence-day","9":"tag-feature","10":"tag-luke-dashjr","11":"tag-segwit"},"author_data":{"id":2705,"name":"Peter Chawaga","nicename":"peter-chawaga","avatar_url":"https:\/\/bitcoinmagazine.com\/wp-content\/uploads\/2024\/12\/peterc-96x96.jpg"},"featured_image_url":"https:\/\/bitcoinmagazine.com\/wp-content\/uploads\/2024\/11\/luke-dashjruasf.png","_links":{"self":[{"href":"https:\/\/bitcoinmagazine.com\/wp-json\/wp\/v2\/posts\/7824","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\/2705"}],"replies":[{"embeddable":true,"href":"https:\/\/bitcoinmagazine.com\/wp-json\/wp\/v2\/comments?post=7824"}],"version-history":[{"count":0,"href":"https:\/\/bitcoinmagazine.com\/wp-json\/wp\/v2\/posts\/7824\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/bitcoinmagazine.com\/wp-json\/wp\/v2\/media\/7825"}],"wp:attachment":[{"href":"https:\/\/bitcoinmagazine.com\/wp-json\/wp\/v2\/media?parent=7824"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/bitcoinmagazine.com\/wp-json\/wp\/v2\/categories?post=7824"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/bitcoinmagazine.com\/wp-json\/wp\/v2\/tags?post=7824"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}