Published: August 2022
This article examines the relationship between a monetary asset being a store of value vs being a medium of exchange.
Specifically, it focuses on the scaling method of the Bitcoin network as its main example, but also takes a broad look at the history of trade-offs in the cryptocurrency space as well to see why a layered approach makes the most sense.
The primary goal of this article is to examine the topic of how bitcoin has evolved as a medium of exchange, and more broadly to analyze the order in which new monetary assets can be accepted as a store of value and a medium of exchange.
As a big part of that, I’ll include an analysis of the Lightning network, which is a small but fast-growing payments layer that is interwoven into the Bitcoin network.
Chart Source: Arcane Research, The State of Lightning Volume 2
Here are the sections of this article:
- Summary Points
- Store of Value vs Medium of Exchange
- Bitcoin and Lightning: Scaling in Layers
- How the Lightning Network Works
- Lightning Network Critiques
- Concluding Thoughts
This article is long, so I’ll summarize the main points up front here, and then spend the rest of the article diving into the details.
-A truly decentralized and permissionless payment network requires its own underlying self-custodial digital bearer asset. If instead it runs on top of the fiat currency system or relies on external custodial arrangements at its foundation, then it is neither decentralized nor permissionless.
-In order to create a truly new digital bearer asset that is useful for payments in the long run, it must also be an attractive store of value, so that a meaningful percentage of the population begins to persistently hold it as some percentage of their liquid net worth and be willing to accept it for goods and services.
-In other words, in order to create a decentralized version of Visa, beneath that you must first create a decentralized version of Fedwire, and along with that you must first create a decentralized version of digital gold. It’s hard to envision any other path succeeding.
-Bitcoin started with a smart design from the beginning. It created an underlying digital gold and settlement network, with a credible degree of decentralization, auditability, scarcity, and immutability that no other network currently rivals. On top of that foundation, Lightning as a payment network is being developed, and has reached a critical mass of liquidity and usability.
-Many cryptocurrencies that followed in Bitcoin’s wake put the cart before the horse. They optimized for throughput and speed on their base layer, at the cost of weaker decentralization, auditability, scarcity, and/or immutability of the underlying bearer asset. As such, they failed to gain structural adoption as money and rendered their high throughput irrelevant, especially since they were brought into existence in the shadow of Bitcoin’s larger network effect.
-Volatility is inevitable along the path of monetization. A new money cannot go from zero to trillions without upward volatility by definition, and with upward volatility comes speculators, leverage, and periods of downward volatility. The first couple decades of monetization for the network as it undergoes open price discovery to reach the bulk of its total addressable market should be different than the “steady state” of the network after it reaches the bulk of its total addressable market, assuming it is successful in doing so.
-Taxes on cryptocurrency transactions, as well as the lower supply inflation rate of bitcoins compared to fiat currencies, results in Gresham’s law being applicable here. Most people in developed countries have an incentive to spend their fiat and hoard their bitcoin like an investment, at least in this stage of the monetization process. The exception is for the subset of people who specifically need Bitcoin/Lightning’s permissionless nature for one reason or another, or for whom the majority of their liquid net worth is in it.
-People in developing countries, with higher inflation and weaker payment and banking systems in general, have more of a natural incentive to use Lightning as a medium of exchange earlier on its monetization process. Indeed, adoption rates are rather promising in many of those regions. This isn’t surprising, considering that more people in developing countries have smart phones than bank accounts, in aggregate.
-An overview of how the Lightning network works in a basic sense, and why channel-based transaction systems make more sense than broadcast transaction systems for individual payments.
-A look at other use-cases for the Lightning network, including its usage as a fast settlement system to move dollars and other fiat currencies around globally, through the core bitcoin liquidity of the network.
-A response to various criticisms of the Lightning network, including an explanation of why comparing its small size to various larger DeFi projects is a category error, and an analysis of its scaling potential.
-Concluding thoughts on the regulatory and enforcement hurdles governments face now that open-source peer-to-peer payments technology exists.
Store of Value vs Medium of Exchange
Humans in tiny groups don’t need money; they can organize resources among themselves manually, and credit between known individuals is easy to keep track of.
However, groups that reach the Dunbar number or larger usually start identifying and making use of some form of money, which gives them a more liquid, divisible, friction-minimized, and widely-accepted accounting unit for storing and exchanging value with people they don’t know.
What makes good money? And how does a new money get adopted by users? I catalogued the history of this question from multiple points of view in my article, “What is Money, Anyway?”
The short answer from thousands of years of history across multiple continents, is that commodity money that is adopted organically needs to have a reasonably high stock-to-flow ratio, and needs sufficient divisibility, portability, durability, fungibility, and verifiability, while being desirable to hold for some reason.
When different commodity monies come in contact with each other, often due to contact between cultures with varying levels of technology, the money that is harder to produce (i.e. able to maintain a persistently higher stock-to-flow ratio even in the face of improving human technology) wins out. Money in a society generally consolidates towards one or two, rather than many of them coexisting together indefinitely. Precious metals, and specifically gold, won the commodity money competition over thousands of years.
Ledger-only systems, referring to paper and bank currency systems with flexible money supplies that are backed by nothing and have no cost to produce, have been tried a number of times in history. Each of those fiat currencies inevitably failed over a long enough timeline. The temptation by central policymakers to produce more, especially in times of crisis, is always there. To assume that such a system can last forever without a breakdown or reset of some sort, is to assume that there will be an unbroken chain of competent and selfless centralized operators of that monetary system.
However, with the development of telecommunications technology and global bank ledgers, fiat currencies eventually offered an actual improvement in long-range transaction and verification speeds compared to precious metals, which along with the taxation or sometimes outright banning of precious metals and other monies, is part of what lead to their widespread adoption for the first time in history. Precious metals as bearer assets were not divisible or portable enough to keep up with global commerce at the speed of telecommunications channels, and thus had to be abstracted with pegs, claims, and counterparty risk. Due to this speed mismatch and subsequent abstraction, policymakers managed to drop precious metals away from the process altogether, other than keeping them as opaque sovereign reserves, and were able to create a ledger-only system around the entire world that is currently in its sixth decade of operation.
The dollar has a lower stock-to-flow ratio than gold, but does have a higher average stock-to-flow ratio than most other commodities, and has the property that it can be sent around the world relatively quickly, while most of its scarcer competition (e.g. gold) is both slow and taxed. The dollar is not something you particularly want to store value in for decades, but it clearly has its use-cases in terms of payments and near-term savings due to how the global financial system has been engineered.
I do, however, think that this fiat system that has been in place since the 1970s is becoming more unstable over time, and will end up undergoing some type of longer-run devaluation and realignment to clear excess debt out of the system. That process has already been in place for over a decade in the US and I expect it to continue both here and elsewhere in the world:
Chart Source: St. Louis Fed
And when we look globally, there are dozens of countries with current or recent inflation rates over 25%, and/or that have had currency resets or hyperinflations within our lifetimes.
The Bitcoin network introduces payment and settlement speeds that are faster than fiat currencies, but its units also have a higher stock-to-flow ratio than gold, and can be used self-custodially and peer-to-peer through the decentralized network.
However, it’s new and volatile, poorly understood, and certainly not without risk, and so bitcoins often get criticized for being too volatile to be used as a medium of exchange. And outside of niche circumstances, bitcoins are indeed only lightly used as media of exchange in their current early stage of monetization.
A number of cryptocurrencies market themselves as faster competitors to the Bitcoin network, and thus supposedly better-suited as a medium of exchange. Putting aside smart contract platforms and proof-of-stake coins for the moment (I’ve covered those elsewhere), we can do a cursory look through some of the notable proof-of-work monies that have sprung up in the wake of the Bitcoin network.
I think it’s natural for the market to explore multiple wrong answers to see in practice what the right answers are, and part of what allows me to analyze these concepts is the historical track record of why and how various projects failed to accrue value.
Litecoin was invented in 2011 based on the design of Bitcoin but with a few changes regarding how it is mined and how long its block times are, and marketed as “silver to bitcoin’s gold”. Specifically, it uses faster 2.5 minute block times compared to Bitcoin’s 10 minute block times. It hit big highs in 2013, and then hit much bigger highs in 2017, at which point the creator sold his position at the top of the market. In 2021 during the altcoin season, Litecoin managed to roughly match those 2017 highs but wasn’t able to gain traction to go up multiples from those highs. After a very long stretch of being in the top ten coins by market capitalization, it’s starting to stagnate and fall down the market cap rankings of cryptocurrencies, and is no longer in the top ten.
As one of the oldest coins that continues to operate as designed, Litecoin’s price chart denominated in bitcoin is a quintessential example of how most coins persistently degrade over time in bitcoin-denominated terms after experiencing their initial price spike:
Dogecoin, created as a joke in 2013 based on the design of Litecoin, managed to hit notably higher highs in 2017, and then had a massive meme spike in 2021 thanks to pumping by Elon Musk, followed by a 90%+ crash. It has 1 minute block times and no supply cap. Numerous other dog-themed meme coins have come along in its wake, each having a brief spike before crashing. These are joke coins that nonetheless tricked a lot of retail investors into buying them at the top. A number of crypto exchanges unfortunately marketed them aggressively to retail investors right at the top in order to make a quick buck, and therefore contributed to a bubble that sucked a lot of people in for major capital losses.
Monero, created in 2014 as a privacy-themed coin, has been unable to decisively surpass its 2017 highs and has fallen very deep in the cryptocurrency market capitalization rankings. Monero uses some interesting privacy mechanisms, but relies on indirect proofs to audit the supply, which means there’s a nonzero chance of there being an undetected inflation bug at any given time. Monero has 2 minute block times, and the way it is designed does not currently allow for a Lightning-like payment channel network to exist on top of it. I would like to see more privacy development within the Bitcoin ecosystem, to make privacy techniques more automatic and easier to use.
Bitcoin’s hard forks, like Bitcoin Cash “BCH” and Bitcoin Satoshi Vision “BSV” have fared worse. Some went away, while others such as these two survive in a weakened state. What they have in common is that they increase block sizes so that more transactions can be packaged into each block. Both of them have gone down significantly in bitcoin-denominated terms. Bitcoin Cash, which was forked from the primary Bitcoin network in 2017, hasn’t yet been able to touch its 2017 highs in dollar terms. Bitcoin Satoshi Vision, forked from Bitcoin Cash in 2018, has been in a choppy sideways pattern since inception, is currently below the price that it split at, and has been the subject of 51% attacks due to its low hash rate. If about 1% of bitcoin miners want to do a 51% attack on either of these chains, they can do so, since bitcoin’s hash rate is orders of magnitude higher and they all share the same hashing algorithm.
The main problem of having faster block times and/or larger block sizes, is that if the network is heavily used, the bandwidth and storage requirements for running a full node become rather high, which makes it hard for the typical user to run a full node to audit the network, and by extension that makes the rules of the network less credibly immutable since the number of full nodes is tiny. Going too fast can also create problems with stability.
When we look at the adoption pattern of the Bitcoin network and some of its failed forks and competitors, we can quickly see a basic problem that many of these forks/competitors encountered and why they failed. They tried to make a broad medium of exchange out of something that was not a store of value, and without the government power of fiat. And this was in addition to the fact that they had the big problem of existing in the shadow of Bitcoin’s far more dominant network effect.
They even went so far as to sacrifice their decentralization and immutability and auditability (which is a big piece of what could potentially make something like bitcoins a store of value) in order to advance their goal of being a medium of exchange. This path, however, leads to failure and irrelevance.
In other words, in order to invent a successful decentralized peer-to-peer Visa-type network (fast transaction layer), one must first invent an underlying decentralized peer-to-peer Fedwire-type network (settlement layer), along with a reason why the underlying unit should be held for the long-term compared to other assets (digital gold).
The Long Road to Monetization
The fascinating thing about watching the Cambrian explosion of new private monies or “cryptocurrencies” since 2009, based on Satoshi Nakamoto’s creation of the Bitcoin network, is that it represents a new test for economic theories on the topic of what makes good money vs what does not.
Everybody has a theory on what makes some monies better than others, but in the long arc of time, it’s the market that decides. Even for government-controlled currencies, the international market decides between them. Any cryptocurrency can have success in the intermediate term, but the real test is which ones, if any, can stick around and gain structural adoption over the course of many years and decades through bull markets and bear markets alike.
So far, the Bitcoin network has gotten through four huge bull/bear cycles (2011, 2013, 2017, 2021 bull cycles) while gaining value and users in an exponentially compounding way. Each bull cycle reached a level of scale that was significantly larger than the prior bull cycle in terms of market capitalization and the number of users.
Now, it is legal tender in a few regions of the world, and a number of large institutions hold it on their balance sheets in various ways.
Simple “bubbles” don’t survive through several 70%+ drawdowns over a period lasting thirteen years and counting; it looks more like Metcalfe’s law of network adoption at this point. That doesn’t mean it is without risks, but it means it should be studied and understood rather than dismissed, to see what it is about this network that allows it to keep growing through resistance.
Chart Source: YCharts
And most notably, bitcoin did this without any central organization promoting it. The inventor disappeared by 2011, and then even his follow-up lead developer and a number of other early developers left in the ensuing years as part of various technical disputes involving the block size. It has been a rather decentralized, open-source, self-sustaining network of rolling participation ever since.
Out of the other thousands of cryptocurrencies, the vast majority fail to successfully get through one cycle. They have a big bubble spike during a bull market, and then crash, and then never recover those bubble highs again. Founders, insiders, and others who bought super early can have spectacular gains on the back of the investors who came in late, but their coins don’t lead to structural adoption and growth. Only a small handful of them have made it through two or three cycles of higher dollar-denominated network value.
Store of Value Precedes Mass Medium of Exchange
For the Bitcoin network, usage as a niche censorship-resistant medium of exchange came first, followed by it being used as broader store of value, which became a much larger use-case. From there, the more it is used as a store of value and the better its scaling solutions become, the more it can be widely used as a mass medium of exchange.
Let’s consider adoption patterns. Suppose you owned some bitcoins and other cryptos sometime in the 2011-2017 range, when all of those various blockchain monies and forks were in the heat of their competition against the Bitcoin network as a medium of exchange, and being marketed as such.
Before the launch of the Lightning network, if you were a person with easy access to banking and payment services and were not de-platformed from anything in particular, why would you spend bitcoins on anything? If the number of dollars keeps increasing every year, but bitcoins have a hard supply cap at 21 million coins, why would you want to give your bitcoins to others? Unless you’ve been holding bitcoin so long that it has become a meaningful share of your net worth, or you actively work in the industry and potentially even get paid in bitcoin, you probably wouldn’t.
This problem is then magnified by the fact that bitcoins have ten minute average confirmation times, bitcoin cash coins have ten minute average confirmation times, and even litecoins and dogecoins which are meant to be faster have 2.5 minute and 1 minute average confirmation times respectively, which is still too slow for convenient in-person transactions. The process is longer if you want to wait for a number of confirmation times to reduce the probability that the transaction will be reversed. These are crappy things to buy coffee with in that form. It’s like trying to buy coffee with a wire transfer. No thanks. That’s what Mastercard is for.
There are circumstances where the Bitcoin network’s base layer payment options are ideal as a medium of exchange, but to try to force it in a situation where it is not ideal, doesn’t make sense. As I described in my “What is Money, Anyway?” article, bitcoin base layer payments are tank-like censorship-resistant payments. Owning bitcoin represents the stored-up ability to make censorship-resistant global payments in the future, and/or to portably bring wealth around the world even by just memorizing twelve words or holding a private key somewhere on your physical person or in your digital files.
This transaction problem is then further compounded by the fact that every cryptocurrency transaction is a taxable event. Governments don’t want other monies to compete with theirs if they can help it, and so they view your bitcoins as commodities, and if you exchange them for something, you’ve now locked in a capital gain that is taxable. Assuming you don’t want to break tax laws, you technically need to keep track of every bitcoin/crypto transaction that you do for tax season.
Furthermore, the number of people that have any meaningful amount of their net worth in bitcoin or other coins remains very low. What is the immediate incentive for a merchant to accept bitcoin or other coins, unless they happen to serve a niche industry where the percentage of bitcoin or crypto users in their customer base is higher than normal?
I’ve described this merchant acceptance problem in prior research pieces when talking about the credit card oligopoly. There are four meaningful card networks in the US, which also extend globally: Visa, Mastercard, American Express, and Discover. These have been around for decades. Merchants accept them as payment because that’s what all of their customers have in their wallets. Customers have them in their wallets because merchants widely accept them. These networks’ flywheels were bootstrapped decades ago.
It would be nearly impossible to create a fifth credit card in the US. You’d have to convince merchants to accept it despite users not yet having it, and you’d have to convince users to get one even though merchants don’t accept it yet. It’s really hard to bootstrap from nothing and compete with existing network effects.
Bitcoins and various cryptocurrencies encountered the same problem. Some places accepted them as a novelty, and some people wanted to spend them here or there, but for the most part the topic of cryptocurrencies as everyday payments was a dud during that whole 2011-2017 era, just like trying to launch a fifth credit card would be, except slower and more taxable.
The primary users of bitcoin for medium of exchange purposes in those early years were people who were de-platformed in various ways. Cypherpunks were naturally attracted to bitcoin’s censorship-resistant payments. Wikileaks turned to accepting bitcoins when they were de-platformed from PayPal in 2010. A subset of early users bought drugs on the internet with bitcoins until those centralized marketplaces were shut down. Human rights advocates began using bitcoin in authoritarian regimes with low banking access or vulnerability to arbitrary bank freezes. These use-cases weren’t for efficiency; they were for peer-to-peer censorship resistance.
For mass medium of exchange usage, meaning far beyond niche censorship-resistant use-cases, a new money likely needs to become a store of value first, if it is to arise organically rather than through government decree. And the payment experience needs to compete with various near-instant fiat payment methods. A lot of people need to each have a lot of the money, and then start asking merchants, “why don’t you accept this yet?”
As it gets big enough or becomes perceived as offering better payment solutions than legacy systems, a number of jurisdictions can even remove the per-transaction tax on it.
Where Most Cryptocurrencies Went Wrong
Since store of value usage precedes mass medium of exchange usage, the fatal flaw of Litecoin, Dogecoin, Bitcoin Cash, Bitcoin Satoshi Vision, and most of these types of attempts at medium of exchange cryptocurrencies, is that they put the cart before the horse.
As previously described, these types of projects wanted to sacrifice some degree of stability or decentralization or immutability or auditability in order to optimize themselves as higher-throughput media of exchange, even though hardly anyone was using them as a store of value yet, with negligible adoption. They were basically just building fintech payments companies with tiny teams of people, and expecting to compete with Visa, despite having way worse user experience, way slower speeds, and way less transaction throughput.
And yet, if we steelman their position, it’s somewhat understandable why some of them tried to do that: Satoshi Nakamoto described his original design as a peer-to-peer e-cash system, and what exactly “cash” is can have a few different meanings. In 2010, Satoshi briefly wrote about how the network could gradually scale in terms of block size over time, even though he was also the one who put the block size limit into the code. After he left, however, some people wanted to scale too much and too early, and without broad consensus to do such a contentious hard fork. By jamming hard forks through and going in their own direction away from the Bitcoin network, users of these other protocols had to go through the difficult experience of seeing how powerful the widely-distributed network of node users had became, and how pushing unwanted updates to them is impossible.
I think too many people in those early years interpreted “e-cash” to mean quick-and-easy payments for everyday goods using the base layer, when a better way to think of cash today is as a private censorship-resistant final settlement transaction method. Physical cash, after all, is not necessarily the easiest payment type, or a medium of exchange that we need to use for everything, but it’s the most private and the hardest to prevent from occurring.
Therefore, when we think of “e-cash”, we likely shouldn’t think of it as optimizing for speed and efficiency right on the base layer for every transaction that we do, but rather we should think of it as optimizing for those same things that physical cash is great for: private and censorship-resistant final settlement payments that can be used when it makes sense to do so.
Plus, bitcoin was already well-optimized for early adopters that actually wanted to use it as a private medium of exchange online at the time. Some of them viewed privacy as a fundamental human right, and were aware of oppressive regimes where this type of technology could be useful to protect people. Others were dealing with real-world constraints of other means of payment, such as Roya Mahboob who used it to pay women and girls in Afghanistan where access to bank accounts by females is more restricted. Bitcoin was also used very early by people using online black markets as well, in a similar way that criminals were early adopters of pagers as a technology (which doesn’t make the technology itself bad).
There were various niches of people where bitcoin was indeed an ideal medium of exchange from the beginning, and bitcoin scaled well enough for those niches. Satoshi picked his variables very carefully to ensure that cypherpunks like him had a working anonymous censorship-resistant peer-to-peer medium of exchange online to start with. So, it was and still is a very useful e-cash.
These types of people could and would wait 30 minutes for an online transaction to process with a few confirmations. They could and would run their own node. They could and would use private techniques to acquire and dispose of their coins. This was a utility network with a mild monetary premium. It offered money that a relatively small group of people at the time would desire to use, and was recognized for its value by users and speculators. Like almost every commodity that gets adopted as money, it had utility first, and gained a monetary premium second as a result of that utility. The utility was that it provided access to a tank-like medium of exchange network that could exchange value globally without centralized intermediaries to stop it, and with a better combination of monetary immutability, censorship-resistance, and liquidity than the countless imitators that followed in its wake.
After enough time had passed, this fluctuating monetary premium of bitcoin’s price attracted speculators and investors that had no intention of using it for a medium of exchange any time soon, similar to why many people buy gold. A subset of Austrian economists, for example, began recognizing bitcoins as being interesting monetary goods; specifically the finitude of the coin supply at 21 million stood out to some of them. When it became more broadly understood how immutable the Bitcoin network’s ruleset was and how its security and liquidity and decentralization dwarfed any other proof-of-work cryptocurrencies, many people began considering it to be hard money. A number of human rights activists began to recognize it as an ideal anti-authoritarian technology for its censorship-resistant aspects, and using it as such.
The mistake of the Litecoin bulls and the Bitcoin Cash bulls and so forth was that they wanted to scale too early to a bigger group of people, before there was a market for it, and even at the cost of weaker decentralization. Bitcoin’s base layer is enough for tens of millions of people to use it on an occasional basis, for when its specific properties are ideal.
The Bitcoin network on the base layer is like the 60-ton armored tank of payment and savings systems: holding and transferring value globally in a censorship-resistant manner. A tank is ideal if you need to get from point A to point B through hostile terrain, and blast through anything in your path. It’s not ideal for commuting to work in. Trying to force base-layer Bitcoin transactions to be used as a daily of medium of exchange by the general public is like trying to make commuting in tanks catch on. It’s not going to, because that’s not what it’s designed for. And to try to make it scale to everyone for all payments on that base layer makes it lose most of the properties that make it useful for what it does best. It would take over a terabyte of data storage per day to create a base layer system capable of supporting tens of thousands of transactions per second.
The earliest analysis of the Bitcoin network, by Hal Finney and others, predicted that the network would likely evolve towards a layered approach.
Bitcoin vs Dollars Example
There are over 100 million people in the world who are estimated to own bitcoin as of this past year. That’s 1-2% of global population depending on the exact number, since the number is reliant on exchange data, surveys, and other opaque assessments. In some countries, however, the adoption percentage seems to be in the low double digits.
However, most of that is pretty shallow. We can quantify adoption by both breadth and depth. Breadth would refer to how many people have a nonzero amount of bitcoin. Depth would refer to how much of their liquid money they have in bitcoin.
What I mean by this, for example, is that someone having $264.34 USD worth of bitcoin sitting in a semi-dormant crypto exchange account is not “adopting” bitcoin to any economically significant degree.
As a thought experiment, imagine a world where people hold bitcoins and/or dollars as liquid money.
And furthermore, let’s assume (bear with me) that bitcoin continues to increase in dollar price over the long run, albeit with plenty of volatility along the way, as a result of bitcoin’s much lower rate of new unit creation compared to the rate of new dollar creation, and more people learning about bitcoin and wanting to hold a nonzero amount of it. So if someone buys a bit of bitcoin, then even without further purchases it will probably become a somewhat bigger share of their liquid money over many years if this thesis is correct.
Now, suppose that only 1% of people own bitcoin, and 99% do not. And suppose that those that do own bitcoin, they have just 3% of their liquid money in it on average. Total bitcoin adoption is therefore 0.03% compared to 99.97% cash in that system. Bitcoin adoption in that context is negligible. There’s little reason for merchants to accept it other than out of novelty or if they specifically cater to cypherpunks.
If 10% of people own bitcoin and have an average of 5% of their liquid money in it, then that is 0.5% total adoption compared to 99.5% cash. Still a rounding error, but nonetheless a niche market with millions of people.
If 30% of people own bitcoin and have 10% of their liquid money in it, then that is 3% total adoption compared to 97% cash. That’s a vocal minority, representing a lot of niche purchasing power.
If 50% of people own bitcoin and have 20% of their liquid money in it, then that is 10% of total adoption compared to 90% cash. That is a huge market.
If 70% of people own bitcoin and have 30% of their liquid money in it, then that is 21% of total adoption compared to 79% cash. That’s enormous.
In order for many people to want to spend bitcoin, it’s more likely that they would have bought some long ago, and perhaps kept buying, took the time to learn how to custody it themselves rather than hold it on an exchange, and after years of price appreciation it’s a decent chunk of their liquid monetary value. They either want to sell some for cash to buy something, or even easier, just buy something with it directly.
Of course in reality, it is bumpier than that. Some early adopters in this scenario will reach very high levels of their net worth in bitcoin, and they become a wealthy cohort to cater to by niche merchants early on. So mass merchant adoption might take a while but of course there would be early merchants that want to cater to that early group, or that sell products that many bitcoin holders would specifically would want to buy.
Think of Developing Countries First
If the numbers in the example above seem extreme (“how could bitcoin possibly reach a 20%+ share of the dollar market?”), then re-run them for a developing country instead.
Replace the US with Nigeria, and the dollar with naira, in the above example. Nigeria has among the highest bitcoin adoption levels in the world, despite the fact that their government has cut off the fiat bank onramps to bitcoin/crypto exchanges to try to protect the naira.
When a currency looks like this, people can and will try to find others to use, even through resistance:
Developing countries with higher average inflation and weaker payment systems are where bitcoins, via the Lightning network, can actually scale quickly as a medium of exchange. Because for many of them, it could indeed solve an everyday payments problem pretty early on in its monetization process.
That’s why there is often a huge mismatch in perceptions about bitcoin between privileged commentators and actual users, and especially for the many people in developing countries that lack access to reliable financial services. It’s for reasons like this that Elizabeth Stark of Lightning Labs describes her mission as bringing “bitcoin to billions, not just billionaires”, to emphasize that the network can be used for a lot more than just a digital conception of gold; it can be used as an empowerment tool for people around the world.
To the extent that the Bitcoin network continues monetizing and growing, it’s not because it eats the US dollar or the Swiss franc first. Instead, it’s offering an alternative to periphery currencies with high inflation, weak property rights, and/or bad payment systems first, and then it moves inward from there. Bitcoin is already bigger than the broad money supply of many developing countries, and is accepted at more points around the world than many developing country currencies (which are generally only accepted within their issuing country or at a small number of specific exchange points internationally). Bitcoin merchant acceptance doesn’t have the density of any specific currency within that currency’s issuing country of course, but it has a wider international reach than most currencies.
The bigger the Bitcoin network gets, and over a longer period of time, the more rational it becomes for merchants to accept it. The more merchants that accept it, the stronger the network becomes, because then bitcoins don’t need to be converted back into fiat currency on one of a handful of centralized bank-connected exchanges for people that want to make use of them. In this sense, wide merchant acceptance is a form of censorship-resistance. When thinking about this, think of merchants in developing countries more-so than just merchants in developed countries.
And over time, a number of companies have been created that allow a merchant to easily accept it, and then either hold the bitcoins or exchange them for fiat currency immediately so they don’t deal with the bitcoins directly. The technical friction for accepting bitcoins as payment keeps decreasing.
The Lesson of Gresham’s Law
Gresham’s law is the principle that “bad money drives out good”. If people have a good money and a bad money, they would rather spend the bad money and keep the good money. Ironically then, the bad money is what tends to circulate with high velocity while the good money is hoarded with low velocity.
This trend revealed itself multiple times under bimetallic standards. When gold and silver were fixed relative to each other by government decree, but this “fix” was slightly off the global supply/demand ratio balance which could change over time, then one of the metals would start to disappear from circulation.
The United States began with a bimetallic standard in which the dollar was defined in terms of both gold or silver at weights and fineness such that gold and silver were set in value to each other at a ratio of 15 to 1. Because world markets valued them at a 15½ to 1 ratio, much of the gold left the country and silver was the de facto standard.
In 1834, the gold content of the dollar was reduced to make the ratio 16 to 1. As a result, silver left the country and gold became the de facto standard.
There are a couple processes for how that happens.
The first process is simply that the better (undervalued) money gets hoarded, and so it stays in the country but gets removed from everyday circulation. People will not usually part with what they perceive as being undervalued.
The second process is that international entities can observe this and arbitrage it. For example, if the global ratio of gold to silver is 15.5 to 1, but Americans have it fixed by government decree at 15 to 1 (slightly undervaluing gold vs silver), then a European entity can keep selling silver to the Americans and buying gold from the Americans. As years or decades pass, there will be a lot less gold in the United States, and a significant amount of silver instead.
The US broad money supply has grown at more than a 7% annualized rate since 1970. Most developed countries have a similar rate to that, and emerging markets tend to have a much higher rate on average.
Chart: St. Louis Fed
Meanwhile, the bitcoin supply is growing at less than 1.8% per year, which will fall to below 0.9% in a couple years, and to around 0.4% four years after that. The Bitcoin network is programmed to asymptotically approach 21 million bitcoins in total by halving its supply inflation rate every four years until it has 0% supply inflation. And unlike most other blockchain monies, the wide node network helps ensure that no centralizing force can change this distribution pattern, and it has the dominant network effect among proof-of-work blockchain monies which makes it more protected against 51% censorship or transaction-reversal attacks.
Chart Source: Coindesk
It’s natural for people to want to hoard something like gold or bitcoin, and spend their dollars, pounds, yen, euros, yuan, pesos, naira, and rupees. Money that depreciates in value tends to circulate, while scarce money that tends to appreciate in value gets hoarded, with much lower spending velocity.
This becomes especially true if a jurisdiction treats the harder money like property and taxes each transaction, which most jurisdictions do. If you try to use things like gold or bitcoins as media of exchange, each transaction is a taxable event compared to your initial cost basis when you originally bought that asset. The incentive therefore is to hoard the taxable gold or the taxable bitcoin, with their lower levels of supply inflation, and spend the non-taxable fiat currency on consumption, unless someone has a strong desire for bitcoin’s censorship-resistant payments properties.
For example, bitcoins have been used as a medium of exchange by girls in Afghanistan, by Russian political opposition when their bank accounts get frozen, by Nigerian merchants and protesters, by people getting capital out of China, by people getting their money out of Venezuela, Iran, Palestine, and elsewhere, by under-banked people in El Salvador, and more. It’s also used in developed markets for some natively-online services, such as Substack or buying VPNs, and many others. And yes, in the early years for people to buy drugs online and occasionally for things like ransomware attacks.
I’ve met a number of these human rights advocates in person. One of the most powerful moments was hearing Ire Aderinokun, co-founder of Nigeria’s Feminist Coalition, speak in Norway’s parliament building earlier this year about how when they protested police violence in Nigeria, they had their bank accounts frozen and resorted to using bitcoins instead, for their self-custodial and censorship-resistant properties. I was familiar with that story from the news, but it’s always more interesting and clear to hear first-hand accounts of it from them in person.
In this sense, although Gresham’s law originally applied to fixed exchange rates, I think it applies more broadly any time there is transactional friction of some sort, including a tax. The weaker, lower-friction currency will be spent first, unless there is a strong practical reason to do otherwise, meaning a use-case that specifically needs bitcoin’s unique properties.
So, a self-custodied store of value and payment system like the Bitcoin network is great for many people, but its exact usage pattern depends on context. It’ll tend to be adopted as a medium of exchange by people who need it, a lot more quickly than people who don’t really need it.
The Volatile Process of Monetization
An asset cannot monetize without volatility. By definition, an asset can’t go from being worth zero, to having a market capitalization of a million dollars, to a billion dollars, to a trillion dollars, to several trillions of dollars, without upward volatility. That upward price move due to user adoption is volatility.
With that being the case, any upward volatility of this magnitude will attract speculators, leverage, and surges of demand, and these speculators eventually get caught up and forced to sell for one reason or another, resulting in periods of sharp downward volatility.
When bitcoin was held by 0.001% of people, it was extremely volatile and risky, since the future was very unknowable and a few individuals could massively affect the price with buy/sell decisions. When it became held by 0.1% of people, its volatility and risk went down somewhat, but still remained high. Now that it’s likely owned in some way by over 1% of people, the risk and volatility keeps reducing over time, although still are both at a significant level. If it gets to a stage where it is held by 10% or more of people, then the volatility and risk would be further reduced.
So, early adopters mainly buy it because they analyze the qualities and consider it to be a useful network to have access to. They’re willing to accept the volatility for the long run potential upside and self-custodial peer-to-peer access that it provides. As more people come in, the asset becomes increasingly monetized.
Some people ask, “What happens once the network runs out of new buyers? Doesn’t that make it a Ponzi scheme?”
I addressed the Ponzi scheme comparison in this article, and showed why it didn’t fit the characteristics of one. But more broadly, one must ask, “at what point would someone want to permanently exchange their self-custodial scarce money (bitcoin) that has a 1.8% annual supply inflation rate that is exponentially shrinking, for a soft money (fiat currency) that typically has a 7% annual supply inflation rate or higher?”
The answer for many people, is never, as long as the Bitcoin network is still working.
Instead, they want to hold and accumulate bitcoins until enough merchants accept them, at which point they could spend some of them, especially if there is enough critical mass for them to become legal tender in more jurisdictions by that point. To the extent that they earn more income in the future, they’d prefer to continue to save at least some of that income in something that has a fixed supply, rather than other things like fiat currency that have unlimited supply and are growing by new supply far more quickly.
In other words, if successful, the network becomes a self-sustaining global economy of people wanting to save in it, and then spend it, and earn more of it, save more of it, and then spend it. Like, well… money.
That’s why this meme has been one of the longest-running ones in the ecosystem:
When understood that way, risk analysis regarding the Bitcoin network should focus on questions like, “What events could potentially derail its monetization process? What events could make the majority of users want or need to sell their bitcoin, stop viewing it as good long-term savings, and instead hold something else? What threats could censor the network, disable the network, or otherwise disrupt its ability to serve as a tank-like medium of exchange and self-custodial portable savings?” Those are the right questions to ask, in my view.
Bitcoin and Lightning: Scaling in Layers
With the invention of Bitcoin, Satoshi Nakamoto put together a number of existing technologies and added some of his own touches to make a rather profound innovation.
For one, the network serves as a decentralized transfer agent and registrar. Proof-of-work miners process transactions (without relying on circular logic like proof-of-stake systems), and the network of nodes enforce the rules of the network. The result of this is the ability to quickly and globally transfer value without the permission of any centralized third party, as long as no individual entity or coordinating group of entities can persistently control the majority of mining capacity on the network and use that majority to censor it.
Secondly, due to the large number of validating nodes run by individual users, the network offers a credibly immutable set of 21 million units (each divisible into 100 million sub-units commonly referred to as “sats”), because there is no central authority that can change the number of coins on the network. Unlike most forms of software, updates cannot be “pushed” to users by developers; they can only be accepted voluntarily. The result of this is a rather interesting (albeit currently volatile) type of money.
Trade-Offs, and No Free Lunch
It’s often said that a blockchain is basically just an inefficient database. Users in this sense are willing to accept inefficiency to ensure decentralization. They have to broadcast every change to the network, and keep track of broadcasts from elsewhere in the network.
A blockchain, especially the truly decentralized variety, is a database that is small and tight enough that thousands of entities around the world can store it on their local devices and constantly update it peer-to-peer using an established set of rules. Each node provides validation to ensure that a new block is following the rules of the protocol, and they will only accept and propagate a new block to other nodes if the new block follows the rules. A very large number of user-run nodes helps ensure that the ruleset is immutable, whereas if there are only a handful of nodes, then it only takes a small quorum of people to rewrite the rules of the network.
Plus, the easier a node is to run, the more auditable the network is for a regular user. More specifically, nodes simply give each user financial self-sovereignty to privately verify their own transactions rather than rely on any trusted third party.
A fully-centralized database has fewer limitations, because it doesn’t need to be small and tight. A large service provider can have an utterly massive database contained in a server farm. That can make things run very efficiently, but unlike with a blockchain, outside entities can’t directly audit it for content and changes, and have no way to stop the owners of that centralized database from doing whatever they want with it.
So, every blockchain network that claims to improve something compared to the Bitcoin network on its base layer, makes multiple trade-offs to do so.
-In order to increase the number of transactions that can occur over a span of time on the base layer, either the block size or the block speed needs to be increased. However, this increases the bandwidth and storage requirements of running a node, and if those variables are pushed too far, it puts it out of the reach of a normal person. And in particular, if the requirements to run a node grow faster than the rate of technological growth in terms of bandwidth and storage, it leads to a shrinking node set over time, which centralizes the network. Trying to scale the network to perform as many transactions as Visa, basically just turns the network into Visa, which is a centralized entity.
-In order to increase privacy, some degree of auditability needs to be sacrificed. One of the key things about the Bitcoin network is that any node can you tell you the exact bitcoin supply, and has the entire history of transactions and the full state of the ledger. That’s not possible to the same degree in a privacy-based system. In addition, if a privacy-based system doesn’t have a serious network effect, privacy is not necessarily as perfect as advertised because the anonymity set is very small and is therefore somewhat trackable. Privacy is in large part a function of liquidity, and if liquidity is lacking in various privacy-focused ecosystems, then their privacy potential is limited.
-In order to increase code expressivity (e.g. to execute complex smart contracts right on the base layer), a network must also increases the bandwidth and storage requirements of full nodes, which makes running a full node harder and thus centralizes the network over time as previously-described. In addition, it increases the complexity and number of possible attack surfaces. Lastly, it makes the network a means to an end rather than an end in and of itself, which means that many users will go towards whatever smart contract blockchains are cheapest.
-In order to replace proof-of-work with proof-of-stake, it requires accepting a circular validation process. In a proof-of-stake system, the coinholders are determined by the state of the ledger, and the state of the ledger is determined by the coinholders, which is a perpetual motion machine based on circular logic, and that therefore doesn’t have high fault tolerance. It is nearly costless to make an infinite number of copies of the blockchain with different transaction histories, and if the network goes offline, there is no way other than governance decisions and centralized checkpoints to determine which ledger is the “real” one. It would be like a corporation serving as its own transfer agent and registrar for its shares, which is inherently circular. A proof-of-work system uses energy as that external arbiter of truth, which is what makes it non-circular, and is what makes it a true timechain rather than merely a blockchain.
Bitcoin has been successful in large part due to its widely-distributed node network, and the associated concept of “monetary self sovereignty”. Anyone with an old laptop or Raspberry Pi and basic internet connection can run a node, and verify the whole system from genesis. Decades from now that will still be the case. The requirements to run a node increase more slowly than the technological increases in bandwidth and storage, which means that a node gets easier and more accessible to run over time. As a result, Bitcoin is inherently designed to get more decentralized over time, in contrast to most other cryptocurrencies that inherently get more centralized over time.
If developers want to change something about the Bitcoin network, their changes cannot be forced onto users’ nodes. The ruleset of Bitcoin is determined by the network of existing nodes. Any changes to the Bitcoin network in practice must be backwards compatible upgrades, which node-users can voluntarily upgrade into over time if they want to, while still being compatible with older nodes. Unless they can gain tremendous agreement from the users, any attempted upgrades that are not backwards compatible with the existing node network, are merely hard forks- they create separate new coins like Bitcoin Cash that lack a network effect and lack serious security.
Trying to do a hard fork from the Bitcoin network is like copying all of the data from Wikipedia (it’s actually not that much) and hosting it on your own website, and then getting very little traffic because you don’t have the millions of backlinks that point to the real Wikipedia, or the volunteer army of people that constantly update the real Wikipedia. Your split version of Wikipedia would be inherently worse than the real one from the moment you copy it.
If nodes had much more requirements to run, then only large entities could run a node, and the set of nodes would be much smaller. A consortium of miners, exchanges, custodians, and other large entities could agree to make changes to the network. And if that’s the case, then immutability and decentralization are lost for the network. In particular, the 21 million finite supply could be changed, and the censorship-resistant properties would be threatened.
What gives bitcoin its “hardness” as money is the immutability of its ruleset, enforced by the vast node network of individual users. There’s basically no way to make backward-incompatible changes, unless there is very strong consensus to do so (e.g. for something like the eventual 2038 problem). Some soft-fork upgrades like Segwit and Taproot make incremental improvements, are backwards compatible, and node users can voluntarily upgrade over time if they want to use those new features.
This software self-sovereignty and monetary immutability seems to have been lost on other cryptocurrency designers. Based on some of his actions and writings, even Satoshi Nakamoto himself may not have fully grasped the near-immutability of his own network, and instead it’s a property of the network that may have emerged and become realized over time, during and especially after his departure from the project. It’s certainly something I had to experience and research a number of times before I understood it.
Adam Back, whose 1990s development regarding proof-of-work was cited by Satoshi Nakamoto in the Bitcoin white paper, had this to say about it:
There’s something unusual about Bitcoin.
So, in 2013 I spent about 4 months of my spare time trying to find any way to appreciably improve Bitcoin, you know across scalability, decentralization, privacy, fungibility, making it easier for people to mine on small devices, a bunch of metrics that I considered to be metrics of improvement. And so I looked at lots of different changing parameters, changing design, changing network, changing cryptography, and you know I came up with lots of different ideas, some of which have been proposed by other people since.
But, basically to my surprise, it seemed that almost anything you did that arguably improved it in one way, made it worse in multiple other ways. It made it more complicated, used more bandwidth, made some other aspect of the system objectively worse.
And so I came to think about it that Bitcoin kind of exists in a narrow pocket of design space. You know, the design space of all possible designs is an enormous search space, right, and counterintuitively it seems you can’t significantly improve it.
And bear in mind I come from a background where I have a PhD in distributed systems, and spent most of my career working on large scale internet systems for startups and big companies, security protocols, and that sort of thing, so I feel like I have a reasonable chance if anybody does of incrementally improving something of this nature. And basically I gave it a shot and concluded, “Wow there is literally, basically nothing. Literally everything you do makes it worse.” Which was not what I was expecting.
So if every improvement makes an unacceptable trade-off, how can it get bigger? With only a few tens of millions of payments possible per month, how can Bitcoin potentially scale to a billion users?
The answer is layers. Every successful financial system uses a layered approach, with each layer being optimal for a certain purpose.
If one layer is attempting to be used for all purposes, it makes too many sacrifices to be useful for almost anything in the long run. But if each layer of the system is optimized according to certain variables to serve a specific purpose (throughput, security, speed, privacy, etc) then the full network stack can optimize for multiple use-cases simultaneously without making unacceptable trade-offs.
For example, in the US we have Fedwire as a gross settlement system between banks. It currently does under 20 million transactions per month (~200 million per year), but settles over $80 trillion in value per month (nearly $1 quadrillion per year) because the average transaction size is massive, and each of these settlements represents a batch of many smaller payment transactions.
Source: FRB Services
We as consumers don’t directly use that system. Instead, we use payment methods like credit cards, debit cards, PayPal, electronic checks, and so forth, and our banks record those transactions on their ledger and then settle with each other later. Each Fedwire transaction represents a batch of tons of smaller transactions from higher layers.
In other words, there is the underlying core settlement system, and then layers on top of it for more throughput, capable of settling billions of transactions per month.
Bitcoin’s ecosystem has evolved in a similar way, except in an open and peer-to-peer manner.
Bitcoin’s base layer has the capacity to process up to maybe 400,000 transactions per day, although each transaction can have multiple outputs, resulting in up to 1 million or more individual payments per day. That’s a few tens of millions of payments per month, or a few hundred million payments per year, which is around the same ballpark that Fedwire currently handles.
Chart Source: Coin Metrics
From there, layers can be built on top of it to give it more throughput or more capabilities.
For example, the Liquid network is a federation of dozens of entities that wraps bitcoins in tokens called L-BTC, and from that point, L-BTC is faster to move around, has somewhat better privacy, and can support smart contracts including various other types of security tokens that run on top of it. A large number of L-BTC transactions can therefore be contained within two BTC transactions (one to peg in, and one to peg out). The trade-off is that the user has to trust the federation, which is more decentralized than trusting a single entity, but less decentralized than trusting Bitcoin’s raw base layer. The majority of the Liquid’s functionary federation entities would need to collude against the system, in order to violate user trust.
As another example, and the focus of the rest of this article, the Lightning network is a series of 2-of-2 multi-signature smart contracts that run on top of the Bitcoin base layer. These channels are peer-to-peer, and can support many transactions over time for each base layer transaction. The trade-off is that the channel must be kept online to protect the funds and receive payments. Additionally, the network has taken a few years to build up to usable levels of channel liquidity.
And from there, custodians can operate in layers above that for people that want them. Exchanges, payment apps, banks, chaumian mints, and so forth can all provide services to users that are willing to trust them with a portion of their funds. This can scale bitcoin usage to any arbitrary level, including by connecting with the Lightning network. Each node on the Lightning network doesn’t necessarily need to be one person; it could be a custodian with thousands or millions of users.
In that sense, each user interacts with the network in the layer(s) that makes the most sense for their specific needs.
How the Lightning Network Works
The Lightning network consists of a series of smart contract channels that run on top of the bitcoin base layer.
And if you think about it, individual consumer payments make a lot more sense with channels, rather than being broadcast out to everyone. If we do an in-person physical cash transaction, it’s directly peer-to-peer. We don’t shout our transaction to the whole world. Lightning replicates that cash concept on top of the Bitcoin base layer.
The result is a much faster, more scalable, cheaper, and more private global payment system, albeit with some trade-offs and limitations compared to directly using base layer transactions.
Channel-based payments for the Bitcoin network have been explored since the early innings of the network. The white paper on the Lightning network was written in 2015, and the first implementations of it for use with real bitcoin came out by early 2018. Developers purposely restricted their software’s channel size early on, to grow cautiously and test things out safely in those early years (specifically to avoid the common problem of user funds being exploited, which we often see in DeFi).
The network has been functioning and growing ever since, and by late 2020 the network reached a level of liquidity, usability, and critical mass that became quite interesting to me from a macroeconomic perspective.
The Limitation of Broadcast Networks
Using a broadcast network to buy coffee on your way to work each day is a terrible idea. A blockchain is meant to be an immutable public ledger. Do I really need to broadcast my coffee transactions to tens of thousands of nodes around the world, to be held in a distributed database for the foreseeable future?
What if I want to buy something more personally or politically sensitive than coffee? Shouldn’t I use peer-to-peer payment channels for that instead?
Imagine, for example, if every email that was sent on the internet had to be copied to everybody’s server and stored there, rather than just to the recipient. That would be grossly inefficient. And yet, that’s how various high-throughput blockchains try to work regarding money.
Instead, I can open a channel on top of the broadcast network, pay for things that only me and the merchant know about (subject to some privacy caveats that will be mentioned later), and then close the channel, with no immutable public record of those individual payments having occurred.
Any network that tries to scale transaction throughput on the broadcast-oriented base layer by radically increasing the block size and/or block speed makes no sense. The node requirements become absurdly high, which turns the network into a centralized Visa-like enterprise-scale database with just a handful of massive nodes. Changes can be made to the fundamental rules of the system at any time with the agreement of a handful of major node-running enterprises, and thus all future aspects of the system including the supply of coins or who to censor the transactions for, becomes changeable. Privacy becomes very hard; various entities could track your net worth and payment history, which is bad enough in a benign environment and terrible in an authoritarian environment, which is where half the world lives.
Additionally, a channel transaction will generally be faster than a broadcast transaction, since it inherently requires propagation time to go through a broadcast network, even among the blockchains with the fastest block times.
That’s why every blockchain that attempts to scale transaction throughput too much on the base layer is inherently flawed. Bitcoin Cash, Bitcoin Satoshi Vision, Litecoin, Dogecoin, and other coins like this all sacrifice too much and become too centralized, in order to do something that doesn’t make technical sense in terms of scalability or privacy. In the long arc of time, they offer nothing of value.
The only way scaling makes sense, and avoids sacrificing decentralization, is to use a layered approach. Users can then pick their own solution, the layer(s) that make sense for them, depending on their specific needs.
Want to transfer a sizable amount of value permissionlessly, or hold coins for a long time in self-custodial cold storage with the highest-possible security and immutability? Use the Bitcoin network base layer.
Want to make a lot of instant, cheap, private, permissionless payments using a self-custodial solution, albeit with occasional on-chain transactions to open or close a channel? Use the Lightning network self-custodially. Various technologies including various mobile applications and Blockstream’s Greenlight make this increasingly easy to do, by abstracting most of the technical details away from the user while still having the user retaining their own private keys. Or if they want to be hands-on, they can be.
Want to make super easy permissioned payments for free, and potentially get other perks, but at the expense of giving up custody? Use a custodial service like Cash App, which itself uses the other two layers. And maybe in the future there will be more private custodian solutions in the Bitcoin network ecosystem, like federated chaumian mints that make use of blind signatures. Federated custody options will potentially be more available, which spreads out custodial risk.
Each layer builds upon the lower layer, without reducing the qualities of that lower layer. A broadcast network on the base layer, a channel network on the middle layer, and a custodian ecosystem on the upper layer, gives each type of user whatever they are looking for. If growing pains become apparent, there are other scaling technologies that may come into play in the future as well, to further increase the number of people that can interact self-custodially with the system.
Bitcoin came into existence in a unique way, and is purposely hard to change, which is what makes it a decentralized digital commodity rather than a centralized digital equity. Instead of trying to create something separate, developers have the ability to build on top of it.
Lightning Network 101 Explanation
Suppose you and your friends are spending a long evening at a bar.
Rather than get your payment method for every round of drinks, it’s preferable to open a tab with the bartender, and then settle that tab at the end of the night. If the bartender doesn’t know you, you can offer your credit card information ahead of time so that they can charge it later that night.
In a manner of speaking, you and the bartender open a payment channel with each other. There is a moment of friction when setting up the tab and a second moment of friction when closing the tab, but between those moments, there is no payment friction for individual rounds of drinks because you just need to tell the bartender, “another round of drinks please” and it happens.
That’s how the Lightning network works, conceptually. I can open a channel with someone else, with a base layer bitcoin transaction. This channel is a 2-of-2 multi-signature channel, meaning that we both have to agree on it, and it’s designed so that either one of us can unilaterally close the channel if we need or want to (although it’s preferable that we do a cooperative close). While the channel is open, we can transact any number of times, as long as we have sufficient liquidity in the channel, until one or both of us want to close the channel with another base layer bitcoin transaction.
Unlike a bar tab, however, a Lightning channel is not based on trust or debt. Payments within the channel are updated instantly, and the ongoing tab can be enforced by either party closing the channel and reconciling with the base layer, with each side receiving their current balance. There is no debt, no promise to pay later, from one person to another. It’s like instantly transmitting money to the bartender’s account through the channel every time you ask for another round of drinks.
Now, suppose that we take this a step further. Alice has a tab with the bartender at a bar, and another person, Bob, also has a tab open with the same bartender. If Bob wants to buy Alice a drink, he can tell the bartender to give Alice a drink and put it on his tab. Alternatively, if Bob forgot his wallet and needs money to get home, Alice can tell the bartender to give Bob $30 and put it on her tab. Alice can pay Bob through the bartender, despite the fact that Alice and Bob know nothing about each other and have no payment channel open with each other.
The Lightning network does that too, but without debt or trust. The following is an example diagram. If user A wants to send a payment to user Q, she can do it by routing the payment from A to C to F to K to L to Q. Each node in the middle might charge a tiny routing fee, like a fraction of a penny since it’s easy to automate. She doesn’t need to set up a channel directly with user Q.
Image Source: Kjerish, via Wikipedia
Because it uses onion routing technology, the nodes in the middle don’t necessarily know where the payment originated from or where it is going for its final destination. Node K is told “route this payment from F to L” without being told more than it needs to know.
The end result of this network of channels, is that one base layer transaction gives you access to a large number of individual payments to various separate entities, and thus the Bitcoin network can be scaled rather significantly.
Imagine a global system with a massive number of interconnected nodes. Anyone can enter the network with a new node and start creating channels. Alternatively, many custodial services also give their account-holders access to the network through their nodes and channels.
Here’s a visualization of the public Lightning network at the moment. It’s a growing network of interconnected nodes connected by payment channels, with those bigger dots representing particularly well-connected nodes:
And here’s a zoomed-in shot of the bottom left area to show a random sample of the shape of connections that is typical throughout the network:
Since the network is pretty efficient, transaction fees are often the equivalent of a penny or less.
There is no hard limit to how big the network can get over time, and how many transactions per second the network can handle, other than the fact that opening and closing channels result in base layer transactions. The Lightning network, if it gets to a size of having millions of open channels in the future, can theoretically handle an almost unlimited number of peer-to-peer transactions per second, but in it’s current form there is an upper limit of tens of millions of new channels that could be opened per year (depending on what percentage of base layer transactions are channel-openings). Future developments could allow more participants to share a channel, and thus could substantially raise the effective scaling ceiling.
Although it has some constraints, especially in this early development phase, this type of network makes lot of sense from a payments perspective. Peer-to-peer channels are better than broadcast networks for small individual transactions. They’re fast, cheap, and relatively private.
Plus, the network is capable of doing micropayments that are much smaller than what Visa and Mastercard can do. With Lightning, you can send payments worth a fraction of a penny. This opens up new use-cases that aren’t possible with credit cards, for example, such as machine-to-machine payments, the streaming of micro-payments, or the usage of micro-payments as a spam-prevention technique.
All of this is global and permissionless. Users can just do it, without asking the permission of a bank or other central entity. In order to prevent it, governments need to actively tell their citizens that it’s illegal to use certain types of free open source software, and then figure out how to actually enforce that.
Liquidity Advantages and Limitations
Liquidity is the biggest limitation of a network that relies on individual routing channels.
If there are only hundreds of participants, then it could be pretty hard to find a route that connects any two arbitrary nodes and has enough liquidity on each channel in the path to pass the payment through. A lot of attempted payment routes will fail. The funds won’t be lost, but the transaction will fail to initiate. The network will be limited, and the user experience will be poor.
Once there are tens of thousands, hundreds of thousands, or millions of participants, and with larger average channel balances, then routing a payment from any arbitrary point to any other arbitrary point on the network becomes exponentially easier and more reliable. There is a very large number of possible paths between most points on the network.
In the Lightning network, the larger the payment that you want to send, the harder it will be to find a set of channel paths that collectively have enough liquidity to handle that payment. For example, it’s pretty easy to send the equivalent of $25 between two points on the network, because your software merely needs to find a set of interconnected nodes that end up each having at least $25 worth of liquidity in the direction that you want. However, it’s harder to send the equivalent of $2,500 to many destinations, because there are fewer channels with that much liquidity, and instead your payment may need to be sent in parallel through multiple paths, and so there needs to be a large number of possible paths between your node and the target node. Additionally, the target node itself may simply not have enough total inbound liquidity to receive a payment of that size.
The more channels that exist, and the bigger the channels are, the more reliable it becomes to route larger payments.
Due to this dynamic, the Lightning network isn’t a light switch that could just be turned on and work perfectly from day one. It had to be painstakingly built, channel by channel, over years. The early users were high-conviction developers and early adopters working their way through a difficult-to-use network, and only after they spent years working on it, did it become relevant for a typical user who just wants cheap and fast payments. In the beginning, they limited channel sizes in the software for user safety. Think of them as slowly hacking raw paths through the jungle with machetes, so that one day roads may be built there for civilization.
Furthermore, tools had to be built along the way to make it easier for node operators to manage liquidity optimally. Those have gotten better but it’s still a work in progress.
Notably, the quality of liquidity can be even more important than the amount of liquidity in a channel network. There are measurements like the “Bos score” for example that rank nodes based on not just their size, but also their age, uptime, proximity to other high-quality nodes, and other measures of reliability. As Elizabeth Stark has described it, it’s like a combination of Google page rank and a Moody’s credit rating.
Many critics said the network would not work, and once it was implemented, many people for the first couple of years said it was a dud. Most of them, however, did not understand the way in which it grows. The Lightning network is like one of those giant freight trains with miles of cars behind it; it takes a ton of work to get up to speed from a standstill, but then it’s practically unstoppable once it gets going with tremendous momentum.
As the Lightning network becomes more usable, the companies building implementations or applications for it can raise more capital from interested investors. For example, Lightning Labs raised a $70 million series B round in 2022 to continue building Lightning network infrastructure, and Zebedee raised $35 million (including from game giant Square Enix) to continue building solutions for games to incorporate Lightning micro-payments. There have been hundreds of millions in total capital raised over the past few years for wallets, apps, infrastructure, and more.
Then, entities with a large number of users can connect to it. Bitfinex and River Financial integrated Lightning for their users in 2019. Bull Bitcoin and Okcoin integrated Lightning for their users in 2021. Cash App and Kraken integrated Lightning for their users in 2022. Tens of millions of people now technically have access to the Lightning network if they want it. A lot of merchant software accepts it now too.
At the start of 2021, I noticed that the network was starting to reach critical mass of liquidity and usability. Lightning was becoming truly usable, meaning that payment routing was becoming more reliable. The initial capacity of the network was bootstrap liquidity, and wasn’t efficiently allocated. For a while, the network looked from the outside like it wasn’t growing, when in reality, that liquidity was slowly spreading out to become more usable and efficient. And then, boom, liquidity and payments started to take off, and some really good mobile apps came to market.
Chart Source: Look Into Bitcoin
Implementations and Apps
No company controls the Lightning network. It’s an open source set of participants.
The basic foundation of the network is an agreed-upon minimal protocol, which makers of Lightning node software adhere to if they want to operate with each other and the network as a whole. These standards are kind of like basic email standards or basic internet standards for various applications to communicate with.
Lightning node software is referred to as a Lightning implementation. Lightning Labs, Blockstream, ACINQ, and Block Inc are the businesses developing the four main Lightning implementations that various developers make use of, but there are others out there as well.
If you want to be hands-on, you can choose which implementation to use, customize an implementation, or even build your own implementation from scratch. There is no gatekeeper that stops anyone from building their own lightning implementation and using it to interface with the rest of the network; it’s an open protocol.
From there, many companies can incorporate these Lightning implementations into easy-to-use apps. An end-user won’t directly use a Lightning implementation; they will use a mobile app that allows them to connect with the network and obscure most of the technical details from them, including the details of the Lightning implementation under the hood.
Some apps can be custodial, meaning you are trusting a company with your money. Cash App and Strike are examples of this. This comes with certain amounts of regulatory compliance in various jurisdictions.
Other apps can be self-custodial, meaning you have full control over your own coins, and are just using their open source software and connecting with highly-liquid nodes. Muun and Breez are examples of this.
When the initial network implementations were launched, few merchants accepted Lightning payments.
Over time, it became easier. BTCPay Server, OpenNode, and IBEX, for example, allow merchants to easily accept Lightning payments.
When El Salvador made bitcoin legal tender, large companies like McDonald’s and Starbucks were able to quickly integrate Lightning payments using third-party software.
NCR Corporation and other point-of-sale companies have expressed interest in becoming interoperable with the Lightning network. Square is a large point-of-sale software and equipment provider for small and medium-sized businesses, and their parent company Block Inc is one of the most pro-bitcoin companies around. Their Cash App already integrates with Lightning and they have multiple bitcoin-focused development units.
Over the next several years, I think it will be increasingly common to have Lightning as a payment method. Some merchants will convert to dollars immediately upon sale (which is easily implemented by many point-of-sale software providers), while some will choose to directly accept bitcoins over the network and keep them.
For a couple years now, there has been an increase in interest for using the Lightning network to transfer dollars or other currencies.
The idea is that bitcoin is an increasingly liquid asset that trades in most large currencies. Someone can exchange dollars for bitcoin, send bitcoin over the Lightning network to another custodian in some other country, and then exchange back into dollars, all within a couple seconds. This allows someone to use the payments aspect of Lightning quite separately from using bitcoin the volatile asset.
This can be done with other currencies as well. Someone can exchange pound sterling for bitcoin, send the bitcoin over the Lightning network, and then exchange that bitcoin for euros within seconds.
This is a very cheap and fast way to send global payments, and businesses like Strike and Bottlepay have been making use of the network for these types of purposes. That fiat-to-bitcoin-to-fiat method can eliminate tax issues associated with Lightning payments for the end user, while making use of the fact that Lightning is more cost-efficient than most payment networks such as Visa and Mastercard.
Due to the November 2021 Bitcoin soft fork upgrade called Taproot, the Bitcoin network and in particular the Lightning network can now theoretically be used to send other types of assets using something called the Taro protocol. The Taro protocol was announced in April 2022 by Lightning Labs, the coding is in progress, and the protocol is in the process of being peer-reviewed by the community.
For example, when this is active, a USD collateralized stablecoin asset can be issued, which can then be sent nearly instantly and nearly for free across the Lightning network. This means that a user can pay for things nearly instantly and nearly for free, in an asset with less volatility and that doesn’t trigger taxable events for the end user.
Imagine Alice and Bob have a Lightning-USD (L-USD) channel with $100 of capacity, balanced such that they both have $50 worth of inbound liquidity, and Carol and Dave have a L-USD channel with $100 of capacity, balanced such that they both have $50 worth of inbound liquidity.
If Bob only has a BTC channel with Carol, Alice can still send $10 of L-USD to Bob, who charges a small routing fee in BTC and forwards $10 of BTC to Carol, who charges a small routing fee in L-USD and forwards $10 of L-USD to Dave, the final destination. Taro interoperates with the existing BTC-only Lightning Network as-is, only requiring the first hop and the second-to-last hop to have L-USD liquidity.
This structure taps into the network effects and liquidity of today’s Lightning Network to route any number of assets, avoiding the need to bootstrap an entirely new network for new assets, and ensuring that bitcoin underpins all transactions on the network. It also incentivizes the growth of BTC liquidity within the Lightning Network to serve a broader multi-asset Lightning Network.
Importantly, the core of the network remains focused on bitcoin channel liquidity, whereas specific Taro assets would generally be on the network periphery. This avoids fracturing overall network liquidity, since ultimately it’s all moving through bitcoin channels for most of its path through the core of the network. In other words, instead of having dollar channels alongside bitcoin channels throughout the whole network (which would fracture the liquidity of the network), the dollar channels would be primarily limited to the edges of the network while the bitcoin channels that continue to grow in number will remain the primary channels for routing payments through, including those dollar payments.
From a macro perspective, that ability to route dollar and other fiat payments through bitcoin-native channels, and thus avoid fracturing network liquidity, is a huge feature. There is a lot of demand in developing countries for dollars. Stablecoins, either on Lightning or on other blockchains, can address that demand whether or not a given country’s banking system is able to offer dollar exposure to their customers or not. This type of technology reduces the practical difference between “onshore” and “offshore” dollars, at least as long as regulators from major economic hubs allow for their custodians to operate in some form.
As Elizabeth Stark, CEO of Lightning Labs described to me:
With Taro, the world’s currencies can be routed through bitcoin, making bitcoin the global routing asset and rendering “cross-border” payments obsolete.
Indeed, the European Central Bank published a report this month that examined the Bitcoin/Lightning stack among several potential methods for global cross-border payments, and took the network pretty seriously in their analysis.
Various point-of-sale technology providers can eventually integrate this as well, so stablecoins can be used to pay for things over the Lightning network, in addition to bitcoins.
Paolo Ardoino of Bitfinex provided a good summary on the technical limitations of incorporating super fast payments on a broadcast network, and why stablecoins on Lightning should ideally be a great improvement on this.
A user could have either a custodial or self-custodial mobile wallet, where they hold bitcoins and stablecoins in one app, and use them to pay for things as desired. I think Alyse Killeen, a venture capitalist focused on bitcoins startups, summarized it well:
Instant [stablecoins] on Lightning makes Bitcoin & Lightning the ultimate censorship resistant, opt-in payment network, as Bitcoin/LN can now “bank” all households, including those that don’t have the wealth to tolerate BTC’s volatility over the short term.
With various multi-signature implementations, time locks, and other programmable surfaces, there are plenty of novel ways to move money around, and use the network for various purposes.
Other Potential Use-Cases
Back in 2021, a company called Impervious released an API that allows people to make applications that run over the Lightning network.
Basically, in addition to sending value instantly and cheaply, the Lightning network can be used to send non-monetary information. This has potential use-cases for social media messages, video calls, file sharing, identity verification, content monetization, social networks, and other applications. Here in 2022, Impervious is working on a browser that brings a lot of this together in one place. Some critics disagree with the approach of embedding this type of information into Lightning payments, but as with most things, the market will be the arbiter of what is useful and what is not.
Lightning can also be used for spam resistance. Proof-of-work money was developed by Adam Back in the 1990s in the form of Hashcash, as an anti-spam technique. There are some analysts now pointing towards Lightning as potentially being an effective way to reduce online spam. There are social networks and websites where commenting requires one sat (0.00000001 bitcoins), and where users tip each other with sats. This impedes the economics of spammy social media bots, because each account and post comes with a micro-price.
With a browser plugin, many websites could implement something like this if the network grows larger.
Similarly, Strike CEO Jack Mallers implemented a micro-cost for people that want to send emails to him.
With the full stack of Bitcoin, Lightning, and things like Taro, it’s hard to predict what this network could be used for a decade from now. Some things will likely flourish, and others will be duds. It’s a programmable set of building blocks for money and information, that moves instantly, permissionlessly, and nearly for free. It’s not controlled by any one company, but rather is open source and can be built upon by any number of companies.
Sometimes this openness creates frictions between competing visions for how the network is best used or how to agree on a set of open protocols, but it also gives it a lot of power and flexibility.
Back when the iPhone was introduced in 2007, few people thought, “wow this could really disrupt the taxi industry a decade from now.” A few technologies had converged by that the point to where everyday people could have a pocket supercomputer with a big touchscreen and a high-bandwidth mobile internet connection, and this served as a set of building blocks that could exponentially eat into many other industries, including allowing Uber to come along and change how we move across cities. All manner of individual hardware electronic devices became mostly-obsolete as they became applications on a smart phone.
I view the Bitcoin/Lightning stack as being similar. The network is still tiny and has a lot of development work still to do, and nothing is for certain. But to me it looks like a powerful monetary network with a ton of upside potential over the next decade.
Lightning Network Critiques
Lightning has faced a number of criticisms, mainly from proponents of other blockchains. For many of them, the success of Lightning network could imply the irrelevance of their own project.
There is still a ton of development work to do on the Lightning network, and so some criticisms are fair, and the network does have limitations. The network is on its fifth year in operational terms, with only the past two years really being at a critical mass of highly-usable liquidity.
But after years of research into the space, I view Lightning as very promising, and generally underestimated. It requires looking out for the next several years to really see the potential.
So, here are my responses to some of the common criticisms of the network that I have seen.
Criticism 1) It’s Small and Trivial
The Lightning network is growing quickly, but still has under 5,000 bitcoins on it in public channels. Depending on bitcoin’s price at a given time, that represents only hundreds of millions of dollars at most. Due to high velocity, quite a lot of transaction volume is being done relative to that tiny amount, but ultimately it’s tiny compared to the global payments industry.
Arcane Research published a great analysis of the Lightning network’s current scale back in April 2022:
Chart Source: Arcane Research, The State of Lightning Volume 2
This small size is often compared by detractors to various DeFi applications. For example, Wrapped Bitcoin on Ethereum has over 230,000 bitcoin custodially. Lightning therefore looks very small, outmatched, and even trivial by comparison. However, that comparison is a category error.
The overall market for actual crypto medium-of-exchange payments, in bitcoin or otherwise, is still very small. Widespread use of bitcoin as a medium of exchange should not be expected until later in its monetization process, as discussed earlier, especially in developed markets where every transaction is a taxable event and people have access to much more established payment systems.
DeFi, on the other hand, is mainly used for trading and leveraging. Many of these various blockchains and Defi protocols have strong crypto VC incentives to issue a coin, market it and pump up the price and exposure, and then get fast exit liquidity on retail investors.
Chainalysis found back in that DeFi is mainly used by institutional-sized traders.
Chart Source: Chainalysis
It makes more sense to compare the amount of Wrapped Bitcoin (which is held by a centralized custodian) to the amount of bitcoin on centralized exchanges. There are more bitcoins wrapped on Ethereum DeFi than there are on either Kraken or Gemini, for example, but less than there are on Coinbase or Binance or Bitfinex. That’s a more appropriate comparison; Ethereum is basically the fourth largest bitcoin exchange and leveraging service, and trading+leveraging is a much larger bitcoin market than bitcoin merchant payments at this point in time.
Lightning, on the other hand, has no separate coin. Nobody is getting super rich quickly off of Lightning. There is no huge set of marketing incentives to get people on Lightning. It’s a rather boring payments network, frankly. It has a very low speculation-to-utility ratio, meaning that it’s almost all utility. I personally consider it to be rather exciting, but that’s because of the utility that it offers and the elegant way in which it works.
Additionally, Lightning developers purposely limited payment and channel sizes in the early years, to reduce the potential for people to lose significant amounts of money from potential bugs or exploits in its nascent state. The goal of developers was never to grow quickly all costs; the goal since the beginning was to build responsibly for the long run.
Lightning’s growth, including through a bear market, it is mainly due to organic utility and need for it, rather than primarily for speculation, trading, leveraging, or for any sort of pump-and-dump VC-funded incentivization scheme that relies on using retail investors as exit liquidity. There could be some catalysts such as Taro (e.g. dollar stablecoins on Lightning) that end up accelerating the network’s growth at some point, but either way, it’s a growing network that is there for people who want to transact using the Bitcoin network.
Criticism 2) It’s Too Centralized
The Lightning network can be challenging to use at a deep level, especially if you’re intending to be a high-volume routing node. Your node has to be on all of the time, you tie up a lot of capital, and it can be tricky to balance your liquidity.
As a result, the network naturally developed many super-nodes that serve as hubs for network traffic, since they have significant capital and spend a lot of time building and maintaining liquid channels. Some people refer to this as a hub-and-spoke model, which is not quite true in this context. This seeming-centralization is often used as a criticism of Lightning, but that criticism is misplaced.
For a hypothetical example, suppose you only have one or two fiber optic internet service providers in your area, and that those two companies are the only possible ways that you can access the internet. That’s a major centralization problem; you’re completely at the whim of those one or two companies to let you use the internet, and you have no recourse otherwise unless you move. You’re limited to the one or two hubs that serve your area in a monopoly or duopoly fashion.
Now instead, suppose hypothetically that there are hundreds or thousands of different satellite-based internet providers that you could choose to use. In this thought experiment, they each can connect you to the global internet wherever you are in the world, via a fleet of orbiting satellites. This removes any sort of centralization problem; you can pick any of them from around the world, and they are nearly countless in number. You’re not limited to a specific hub linked to your location; you can pick from the entire global set of hubs, and you can even pick more than one hub simultaneously for additional redundancy.
In the Lightning network, there are all sorts of super nodes that you can connect with for routing liquidity, and they are based in various jurisdictions or can operate privately. Since it’s all software, it scales rather significantly.
Additionally, you can avoid directly connecting with any of the super nodes if you don’t want to, and instead connect directly peer-to-peer with other small nodes (including internationally), who are themselves connected to any number of other peer nodes or super nodes. There are online groups, such as Plebnet with 6,000+ members, that focus on building channels with each other and supporting each other. This is what makes it not really a hub-and-spoke model, even if there are many particularly well-connected super nodes throughout the system.
Importantly, entities in Lightning are not enforcing the immutability of the money supply or enforcing other consensus rules; they’re merely routing individual payments.
If certain super-nodes are perceived as problematic in terms of privacy or in terms of censoring transactions, users can build channels around them. John Gilmore’s well-known quote, “The Net interprets censorship as damage and routes around it” applies here. That optionality is the key to decentralization. The Lightning network involves an evolving set of nodes and channels, with old channels being removed and new channels being built as needed by its various participants. Market forces dictate where the liquidity goes.
This was how the Internet looked back in 2005:
Source: Opte Project, via Wikipedia
And here’s that zoomed-in snapshot of part of the Lightning network that I showed earlier, which shows how similar its structure is to the Internet, except that Lightning is more decentralized because any individual node can directly connect to many other nodes, in addition to routing payments through super-nodes if they want.
Alexander Leishman recently described it well:
The Lightning Network has no shared global state, which is one of the reasons it is by far the most robust and censorship resistant Layer 2. In fact, there is no singular Lightning Network. There are many private LN nodes and subnets you can’t see.
Criticism 3) It’s Easy to Replicate
Lightning need not be unique to Bitcoin. Much like how the Bitcoin network can incorporate potentially useful technology that is developed on other blockchains, certain other blockchains can potentially incorporate Lightning-like technology on their stack.
In fact, some Lightning-like networks do exist on some other blockchains, but they are tiny compared to what exists on the Bitcoin network.
This is because as previously described, Lightning relies on liquidity. Liquidity (in the form of a large number of well-funded channels) is one of the key limitations for it to work smoothly. When the network was first launched on the Bitcoin network, it wasn’t highly usable. There were very few nodes and channels, and it was hard to find a payment route to send payments through, or to get inbound liquidity so that other people can send payments to you. A lot of payments would fail and need to be re-attempted. It was a work in progress, basically in alpha development.
However, it gradually built up more and more channels for years, which made it increasingly reliable to send and receive payments. Liquidity is a major network effect variable; it’s why certain stock and commodity exchanges remain the primary stock and commodity exchanges for decades or even centuries. People go to where liquidity is, and that creates more liquidity, which brings more people, and that creates more liquidity. Lightning has a self-reinforcing network effect that is extremely hard to replicate, and it’s growing month by month.
This is why I consider the Lightning network to be like one of those mile-long freight trains. It’s hard to get it started and to accelerate it. But once it’s going, its momentum is huge. The Lightning network took years of channel building and cautious development to reach a critical mass of liquidity and true usability, and it did so in large part because it was built on Bitcoin which has the biggest combination of liquidity, scale, and decentralization of any cryptocurrency.
Lightning is a network effect built on top of a network effect, and both reinforce each other.
Criticism 4) It’s Not Private Enough
The Lightning network generally offers better privacy than the Bitcoin base layer, especially for the sender, but it’s not a perfectly private network.
As previously mentioned, the network makes use of onion routing, so that each node along the payment path only knows the directions that apply to them, rather than the full set of directions for where the payment originated and where its final destination is. It’s a series of directions, but each participant only has a small subset of the total directions.
For example, using this diagram again, if I am sending a payment from A to Q, through nodes C, F, K, and L, those nodes don’t necessarily know that Q is the final destination and that A was the initial sender. Node K, for example, is just being told to receive payment from F and send payment to L, in exchange for a tiny fee.
Image Source: Kjerish, via Wikipedia
An entity that is trying to spy on transactions can set up multiple Lightning nodes all around the network, and serve as a payment router. Usually, an individual node doesn’t know the original source or destination of a payment; only the node where it came from and where they are sending it to. However, if an entity has enough nodes across the network, they might be able to get a good idea of where certain payments are coming from and going to. So, not every payment absolutely guarantees perfectly privacy, although the sender usually has good privacy in practice.
Knowledgeable users have significant ways to maximize their privacy, both on the Bitcoin network’s base layer and on the Lightning network, but these do take some know-how.
There is still development happening in this early stage of the network to expand privacy options for users and to make privacy more natural. This includes specific developments to make it harder for surveillance nodes to gain useful information about payments, and specific developments to increase the privacy of the recipient. The Human Rights Foundation has a bitcoin development fund that among other things, provides financing for various privacy developments.
With the recent OFAC sanctioning of the Tornado Cash privacy tool on Ethereum, there has been an increase in industry awareness around privacy and its implications vs various policymakers that would prefer to limit privacy wherever possible. The 2021 Infrastructure Investment and Jobs Act included new reporting requirements for digital asset brokers, which is broad enough to potentially include Lightning node operators. This is a complex legal issue, because Lightning node operators can and often do route payments without knowing the source or destination of the payment, similar to how internet routers don’t know the contents of the encrypted bits they are routing.
Similar to what occurred in the 1990s with the dawn of the consumer internet and end-to-end encryption, there could be a growing friction in the 2020s between anti-privacy regulators and innovative new technologies that make privacy increasingly possible.
Criticism 5) We Have Other Payment Solutions
Most people living in the US or Europe or Japan do not have problems making payments or getting bank accounts on a regular basis. They may wonder why Lightning is relevant at all.
However, a significant portion of the world is unbanked, while a free open source software app that makes use of the Lightning network can give them payments capability. A large portion of the developing world suffers from persistent double-digit inflation, and most people in developing countries have experienced major currency devaluations/resets in their lifetimes, which eradicates savings.
Additionally, approximately half the world lives in countries that are classified as authoritarian or semi-authoraritan. They face arbitrary bank account freezes for basic things like protesting or speaking too freely. Technology like the Bitcoin/Lightning stack is an asymmetric technology for them.
Even in relatively free countries, individual people, companies, or industries can be de-platformed from the common payment networks despite not doing anything illegal. The Bitcoin/Lightning stack is therefore a backup option, open to all.
When imagining the potential addressable market of the Lightning network or similar solutions, we need to think globally, rather than just about our own comfortable lives. People who suffer from high inflation, corrupt banking systems, de-platforming, and other monetary problems, are the more natural prospective users of peer-to-peer money that can’t be debased or frozen by a centralized third party. They’re more likely to get on the Bitcoin/Lightning network compared to any given person in a developed country.
Sure, some bad actors can make use of that technology as well, but that’s like saying that bad actors can make use of the Internet. Of course they can; it’s an open set of protocols. Any powerful piece of technology can be used by good or bad people. However, the number of people that need improvements in this area for legitimate purposes is orders of magnitude larger in number than prospective criminals.
It’s not shocking, then, that 19 out of 20 of Chainalysis’ top countries by cryptocurrency adoption, are developing countries. In many of these countries, there is much higher penetration of smart phones than bank accounts:
Even in developed countries, Lightning can make payments cheaper, and can be used for micro payments or machine-to-machine payments more seamlessly than the current fiat payment methods can.
Criticism 6) It Has a Scaling Ceiling for Self-Custodial Users
Lightning greatly increases the transaction volume that is possible on the Bitcoin network. However, opening and closing a Lightning channel still requires an on-chain transaction, which means that in its current form, the Bitcoin/Lightning stack still can’t scale to billions of people using it self-custodially.
Specifically, there are block space limits to how many people can use it fully self-custodially on a regular basis, unless certain base layer forks allow for more throughput.
For any network, there are inescapable technical trade-offs. To ensure the widespread auditability and immutability of the base layer, there are some constraints that are hard to overcome.
I view many other blockchain designers as trying to over-engineer their systems. Any solution needs to have product-market fit. Not everybody wants a fully self-custodial experience. Some people want the convenience of using a custodial service of some sort. Bitcoin/Lightning gives optionality to people around the world, but people can see fit to use whichever portion of the stack that they want.
To quantify it, the Bitcoin/Lightning stack can be semi-regularly used by tens of millions of people self-custodially (or more than that over time if many of them are just holding it in cold storage). Custodial services can scale that to higher numbers. For example, all of the tens of millions of accounts on Cash App technically have access to the Lightning network, through nodes and channels operated by Cash App. The same is true for people on Strike, River, and similar types of apps.
At the current time, the Bitcoin network is being criticized by some opponents for low fees and thus supposedly low long-term censorship resistance as the block subsidy winds down (meaning there is not overwhelming demand for its block space at the current time, which if that state were to persist indefinitely could eventually result in a low cost to control over half of the mining share), while it is simultaneously being criticized for not being able to scale self-custodially to everyone in the world (meaning its block space is not nearly big enough to fulfill such enormous potential demand). These are mostly mutually exclusive concerns.
If the combination of the Bitcoin/Lightning stack eventually reaches severe growing pains against the number of people that want to interact with it fully self-custodially (a good thing), then there are additional areas of development that can increase its scaling potential, via ways to allow more users to share a given channel, which are beyond the technical scope of this article.
On the other hand, if the network doesn’t grow much and its block space does not increase in value (a bad thing), then its scaling limitations are a non-issue.
At the current time, the Bitcoin/Lightning stack provides tremendous scaling potential compared to the number of people that currently use the network. The network doesn’t need to overbuild for market conditions that don’t exist yet, although of course it’s good for developers to be thinking about long-term scaling options.
As the saying goes, “necessity is the mother of invention”, and if/when the network encounters persistently high base layer fees, tons of base layer transactions being used to open lightning channels, and an inability to onboard all of the users that want to onboard to the network self-custodially, then that would spark more interest in developing further scaling solutions, including the possibility of new broad-consensus soft forks and other changes.
For thousands of years, commerce and money moved at the same speed: the speed of foot, horses, and ships. People’s ability to do transactions, and the bearer assets they transacted with (mainly gold and silver), had no inherent difference in terms of speed.
With the invention of the telegraph, and then the telephone and undersea cables throughout the 1800s, the speed of commerce increased to nearly the speed of light. People could transact across continents by updating each others’ bank ledgers over telecommunication systems.
However, gold and silver as bearer assets, still moved slowly, and thus had to be increasingly abstracted in order to keep up.
Prior to this, gold and silver were already sometimes abstracted with paper claims due to divisibility limitations, but once telecommunications technology was invented, their slow speed made it even more necessary to abstract them. Eventually, governments dropped gold and silver backing from their bank ledger and physical paper abstractions entirely. Basically, the difference in speed between commerce and bearer asset money gave governments a huge opportunity for custodial arbitrage.
The invention of the Bitcoin network, and especially the Lightning network that makes use of it, however, re-created a way for bearer assets to move at the speed of telecommunications, just like commerce does. People now have the option to store and send liquid value globally, peer-to-peer, without relying on claims or IOUs, by instead relying on decentralized code-enforced rules that immediately put the funds in the custody of the recipient.
The Bitcoin/Lightning stack is a decentralized ledger that also has peer-to-peer payment channels interwoven on top of it. It’s programmable money in a decentralized cloud, connected to the real world via its proof-of-work consensus.
It’s hard to say exactly where this leads. Peer-to-peer global transfers of liquid value is a Pandora’s box that has now been opened. Certain governments do not want it open, and pass various laws against it, but here it is, with free open source software. It’s much harder for governments to enforce payment rules on millions of individual persons, than on just thousands of highly-regulated banking institutions. If people don’t need to go through banks to transact inside or outside of their local area, that opens a new set of possibilities.
There’s a race now between public and private developers.
On one hand, things like the Bitcoin/Lightning stack are racing ahead with stateless monetary assets and cheap and instant payment channels. Since it’s open source, developers around the world can work on various parts of it to any extent they want. Combined with how finite of an asset bitcoins are, this is leading to substantial adoption and development, even as the price fluctuates wildly based on leverage and big investors and all sorts of reasons. Individuals, startups, and even some large corporations contribute development efforts to it.
On the other hand, governments are working towards central bank digital currencies. Some of them, like China, got a head start and already have implementations in the field. Most other governments, however, are way behind, and are only in the research phase for how they might want to go about constructing a digital currency.
While governments are slower than the open source private sector and have a less attractive set of incentives (maintaining an inflationary system, maintaining seigniorage with the system, enhancing surveillance and control capabilities on the users of the system, and so forth), they do have the power of taxation and regulation over their open source private sector competition.
However, this power of taxation and regulation is limited by their rule of law, the will of the people, and their desire to encourage innovation-focused businesses to remain in their jurisdiction rather than go elsewhere in the global marketplace.
At the end of the day, blockchains are information. Users are merely updating an open source distributed public ledger amongst themselves, and can simply memorize a twelve-word seed phrase to interact with it. To outright ban the individual use of open source blockchain software, is basically to ban a form of speech and information. This is somewhat possible in authoritarian regimes (although underground usage of it continues) but is more challenging to do in a country with property rights and freedom of speech and expression, with democratic representation. Governments have to get rather authoritarian if they want to nearly-completely deter the use of such open and decentralized technology and then maintain that deterrence perpetually.
Instead, the main ways that policymakers can control the industry are via on-ramps, taxation, and regulation. They can block fiat bank connections to digital asset exchanges, or regulate their usage with strict KYC AML compliance checks in and out of large digital asset exchanges combined with blockchain surveillance to track addresses. They can make it hard to serve as a custodian for digital assets, or make it hard for users to withdraw coins from custodians. There are ways around this, but all of these are frictions and control points for large pools of capital.
In problematic jurisdictions like Turkey with massive inflation or Russia with authoritarianism, they are more prone to say that it’s illegal for merchants to accept bitcoin or other digital assets as payment for goods and services and force people to try to use their fiat currency instead. But to the extent that they can even enforce such rules, they do so at the risk of cutting off their population from the rest of the world, using ever-stronger means of controlling information and open source software, and deterring innovation from happening within their jurisdiction.
In a number of countries with a failing currency, it is illegal to have and use cash dollars. And yet cash dollars are often accepted by merchants anyway. It’s very hard to enforce a cash dollar ban when people have trouble using the local currency due to high inflation or transaction censorship. Similarly, it’s rather hard to enforce a perpetual ban on open source software and peer-to-peer digital transactions; the number of enforcement points is huge and developers keep adapting it to make it easier and more private to use.
I continue to view the digitization of money as a key theme for the 2020s decade and beyond, both in bottom-up ways (e.g. bitcoins) and in top-down ways (e.g. central bank digital currencies), and am interested to see the directions that it goes in.
The Bitcoin/Lightning stack in particular continues to be very promising as a monetary network in my view, with ongoing signs of user adoption and development, along with high levels of decentralization. It’s not without risks and challenges, but it’s certainly something to keep an eye on.
Special thanks to Elizabeth Stark of Lightning Labs for answering so many research questions; this piece wouldn’t be possible without her.
And additional thanks to Steve Lee of Block Inc for sharing useful resources on the current state of Lightning privacy research, Dario Sneidermanis of Muun for answering questions about Muun and UX and scaling when I met him in Oslo, Alexander Leishman of River Financial for answering questions about liquidity, Roy Sheinfeld of Breez for publishing great research regarding the network, Kevin Rooke for interviewing a large number of Lightning experts on his podcast, Obi Nwosu of Fedi for educating me on the concept of federated Chaumian mints, Alex Bosworth of Lightning Labs for his social media posts about liquidity, Pablo Fernandez of Swan Bitcoin for being a valuable technical resource on various Lightning-related topics, the authors of Mastering the Lightning Network (Andreas Antonopolous, Olaoluwa Osuntokun, and Rene Pickhardt) for providing technical education about the network, the team at Arcane Research for putting out detailed reports on the state of the network, Alyse Killen for suggesting that I add a summary/abstract at the beginning of my ridiculously long articles, and of course all of the developers and financiers in the ecosystem for building the network out and providing articles or documents to learn from.