The Five-Per-Second Delusion: How “Hard Money” Becomes Soft IOUs
When a starved base layer meets Lightning’s wishful arithmetic, the end state isn’t freedom—it’s a cartel of liquidity providers selling paper promises.
Keywords
Bitcoin, BTC, Lightning Network, transaction throughput, fee markets, payment routing, HTLC limits, liquidity providers, custodial risk, settlement finality, IOUs, gold standard, fee externalities, network topology, capital lock-up, systemic risk
I. Thesis
The immutable arithmetic of a five-transaction-per-second base layer dictates the fate of BTC. Such a system cannot sustain universal cash use, no matter how much theological fervour is applied. Lightning, constructed as a compensatory scaffold, does not transcend this limit—it compounds it. Its architecture inherits every flaw of the underlayer and amplifies them through liquidity asymmetry, capital lockup, and routing inefficiency.
The inevitable equilibrium is consolidation. A network that begins with talk of freedom concludes with a handful of liquidity barons and custodians controlling flow. Lightning’s liquidity constraints push users toward large, well-capitalised intermediaries; these hubs internalise payments, batching them for eventual—though increasingly rare—on-chain settlement. What emerges is not digital cash, but a digital clearinghouse.
At this end state, BTC becomes what gold once was under the so-called “standard”: a fetishised reserve asset underpinning a paper economy of IOUs. The base chain serves as a museum exhibit for “sound money,” while the real economy functions on synthetic representations issued by corporate treasuries and financial platforms. These paper-BTC instruments, like their 19th-century predecessors, expand elastically, decoupled from their supposed finite base.
The final irony is that Lightning, championed as the saviour of peer-to-peer exchange, mathematically guarantees the return of intermediaries. When settlement becomes too costly to perform, trust becomes too cheap to avoid. The cryptographic spectacle remains—the hash, the keys, the slogans—but the economics revert to form. BTC ceases to be a system of digital cash and ossifies into a monument to scarcity worship, where the only thing truly decentralised is the delusion.
II. Ground Rules and Assumptions (Explicit, Conservative)
The foundation of this analysis rests on what the system demonstrably is, not on what its advocates wish it to be. The assumptions are drawn from documented, observable constraints, not speculative optimisations or hypothetical upgrades. The analysis, therefore, proceeds under conditions that the network itself defines and enforces.
Base-layer capacity: The BTC network sustains roughly five transactions per second—an arithmetic constant dictated by block size and interval. Each block, at approximately 1 MB every ten minutes, accommodates about 2,500 transactions on average. This ceiling is not a theoretical inconvenience; it is the mechanical throttle that determines all economic behaviour above it. Transaction throughput remains effectively fixed, with confirmation times and mempool clearance governed by fee bidding. When activity surges, the queue extends, and miners select only the highest-fee transactions. This creates an unavoidable economic hierarchy: those able to pay, transact; those who cannot, wait.
Settlement meaning: For purposes of economic finality, a settlement refers to an on-chain transaction—either closing a Lightning channel or transferring funds between ultimate owners. Settlement is the only point at which ownership truly changes in a verifiable, irreversible manner. Any off-chain update, however frequent or intricate, remains a provisional state subject to future settlement. Therefore, all “scaling” claims must still funnel through this narrow on-chain aperture.
Lightning primitives: The Lightning Network’s architecture is straightforward but unforgiving. Each channel is funded through an on-chain commitment transaction, forming a bilateral ledger between two participants. Transfers occur by exchanging pre-signed commitment states secured through Hash Time-Locked Contracts (HTLCs). Time-locks ensure that disputes can be resolved via the base layer, while commitment updates record temporary balances. To send funds, a node must possess outbound liquidity; to receive them, inbound liquidity. Channel unbalancing, insufficient liquidity, or CLTV/time-lock conflicts all yield payment failure. None of these limitations are theoretical—they define the network’s daily operation.
Adversarial but realistic environment: The model presumes rational actors seeking profit, not altruistic volunteers. Fee maximisation is the norm. Nodes reprice dynamically, closing unprofitable channels and hoarding liquidity when volatility increases. Churn occurs as channels age out, fail, or become economically unviable. Ordinary network outages and route failures further erode reliability. These are not catastrophic edge cases but typical operational realities observed in Lightning’s live topology.
No exotic adversaries or “black swan” interventions are invoked. The system is taken at its word—its rules, code, and demonstrated behaviour form the boundary of the analysis. Within that boundary, the economics are clear: five transactions per second anchor the network, and everything built above inherits the limits, friction, and fee-driven scarcity that flow from it.
III. Fee-Market Arithmetic on a Starved Base Layer
The mathematics of a fee-driven system operating under an artificially constrained capacity are unforgiving. With roughly five transactions per second as the upper bound, the BTC base layer cannot scale organically with demand. The scarcity of blockspace functions as a pricing mechanism — not by design of elegance, but by brute exclusion. Only those who can outbid others are permitted to settle.
Every on-chain transaction, whether an initial channel opening, a channel closure, or a rebalancing event, must compete for the same limited space. When the number of required settlements exceeds the system’s throughput capacity, the backlog extends indefinitely, and fee pressure rises exponentially. The inequality is simple but fatal:
If total settlement demand (D) > capacity (C), then fees (F) → ∞ as queue time (Tq) → ∞.
This is not theoretical modelling; it is the natural product of a fee auction in a fixed-supply environment. When channel churn increases — through node failures, unbalanced routes, or rebalancing — Lightning’s supposed efficiency disintegrates. The cost of settlement rises, pushing smaller or less sophisticated participants out of the market entirely.
As settlement becomes expensive, Lightning participants are incentivised to defer closure or avoid on-chain interaction altogether. Channels remain open long past their intended operational window, and imbalances accumulate. Those unable to absorb such costs — smaller routing nodes, hobbyists, or genuine peer-to-peer users — capitulate, leaving the system to larger intermediaries capable of batching and internal netting.
Here the reflexive feedback loop begins:
Fees rise, making direct interaction with the blockchain uneconomical for individuals.
Users migrate to custodial hubs or liquidity aggregators that promise cheaper or “instant” transfers.
These intermediaries consolidate, handling vast internal flows off-chain while representing aggregated settlement batches on-chain.
Independent users decline, further lowering the proportion of individual closings.
Blockspace becomes dominated by large custodial actors who now set effective policy and pricing power.
This dynamic does not stop; it accelerates. Each upward tick in fee volatility reinforces centralisation pressure, and each round of consolidation further marginalises end-users. The result is a market in which on-chain settlement becomes a privilege of institutions, not individuals — an inversion of the network’s original premise.
Scarcity, in this configuration, ceases to be a virtue; it becomes the mechanism of exclusion. When the system rewards custodial aggregation and penalises direct use, it ceases to function as digital cash and mutates into a closed financial oligopoly. The five-transaction bottleneck ensures that the fee market will always serve as a gatekeeper, throttling participation until the only actors remaining are those wealthy or industrial enough to pay for entry. The dream of peer-to-peer exchange collapses under the arithmetic of its own constraint.
IV. Lightning’s Structural Frictions (The Parts Marketing Omits)
The Lightning Network is often described as an elegant abstraction that “scales Bitcoin.” In truth, it scales complexity. Every aspect of its operation is bounded not by imagination but by mechanical and economic constraints that no amount of marketing can erase. These are not theoretical annoyances—they are structural ceilings built into the design itself.
A) Routing Is Constrained by Liquidity, Not Topology
Graphically, the Lightning Network appears vast and well-connected, a mesh of nodes and channels resembling a healthy decentralised topology. But this image is a mathematical deceit. The existence of a path in the graph does not imply the economic viability of that path. Routing depends not on the availability of connections but on the directional liquidity within each channel.
Every payment requires a sufficient outbound balance from sender to receiver across all intermediate hops. If even one hop along the route lacks enough inbound liquidity, the transaction fails. Thus, routing is an exercise in constrained optimisation under asymmetric liquidity conditions, not a simple traversal of edges. As channels skew in one direction—inevitable over time—available routes collapse, and the network fragments into clusters centred on liquidity-rich hubs.
B) Capital Lock-Up and Rebalancing
Lightning is not a fluid system; it is a system of frozen capital. To send, one must lock funds on-chain to open a channel; to receive, one must have liquidity in the opposite direction. This creates a paradox: a participant cannot receive without having already distributed liquidity elsewhere.
Rebalancing, the act of restoring usable channel balances, comes at a cost. It can either occur on-chain—paying base-layer fees and worsening congestion—or via circular off-chain routes, which fail frequently and consume additional liquidity. Under stress conditions, rebalancing becomes economically irrational: the cost of maintaining balance exceeds the utility of the channel itself. As liquidity accumulates in a few large nodes, smaller participants are drained of capacity and rendered inert.
C) HTLC and Timelock Ceilings
The network’s concurrency limits are not theoretical artefacts but coded boundaries. Each channel supports only a finite number of active HTLCs (Hash Time-Locked Contracts), typically around 483. Each payment in flight consumes one HTLC slot and requires a timelock delta to protect against fraud. As transaction volume increases, these slots saturate, and nodes begin rejecting new payments.
The timelock (CLTV) chain across multiple hops extends settlement delay and increases the risk of expiration under congestion. The more hops a route has, the longer its cumulative timelock—introducing measurable latency and risk of failure. Thus, large-scale transaction bursts, precisely what Lightning is marketed to handle, cause routing to degrade in speed and reliability.
D) Gossip and Path-Finding Reality
Lightning’s routing is dynamic but blind. Nodes advertise channel states via a gossip protocol, yet those states are inherently stale—balances change with every transaction, but updates are not broadcast in real time. Payment amounts are private, forcing nodes to guess viable paths using incomplete information.
Pathfinding therefore becomes a process of trial and error. Failed routes must be retried with new combinations, adding latency and uncertainty. Each additional hop increases the probability of encountering a depleted or disabled channel. In aggregate, this transforms payments into probabilistic events rather than deterministic transactions. The user experience degrades accordingly: “instant” becomes “maybe.”
E) Volatility and Liveness
Lightning’s operational fragility compounds during volatility or network stress. When the price of BTC swings sharply or when on-chain fees spike, nodes respond rationally—they close channels, raise routing fees, or temporarily disable forwarding to protect balances. Liquidity dries up at precisely the moment demand increases.
Liveness, the system’s ability to maintain operational continuity, thus becomes conditional. During congestion, Lightning’s liquidity evaporates, its routing graph fractures, and payments fail unpredictably. Large transactions, which require multiple well-funded channels, become practically impossible just when users most need reliability.
Together, these constraints define Lightning’s mechanical reality: a system that is technically clever but economically brittle. It is not the frictionless, infinitely scalable fabric described in promotional literature, but a liquidity network hemmed in by the very mathematics of its design. Each fix adds new fragility. Each layer of abstraction distances it further from the simplicity of direct, on-chain exchange. The physics of liquidity cannot be faked — and Lightning, built on scarcity, only magnifies the scarcity it claims to solve.
V. Why “Just Use Lightning” Collapses into Hubs
The mantra “just use Lightning” is repeated with the zeal of a televangelist promising salvation through slogans. Yet beneath the chant lies the most primitive economic law of networks: the more costly the settlement layer, the more power accrues to those who can afford to absorb its cost. Lightning, operating above a five-transaction-per-second base, is no exception. The consequence is mathematically certain — consolidation into hubs.
When on-chain settlement becomes rare and expensive, only agents with deep capital reserves can survive the liquidity friction. To route payments reliably, a node must maintain vast, balanced channels with multiple peers, each funded on both sides. This demands a permanent lock-up of capital, continuous liquidity management, and operational uptime indistinguishable from a financial institution. The small user cannot compete.
Capital Requirements and Economic Gravity
Every successful routing node must carry both inbound and outbound capacity — liquidity that is immobilised but must remain available. This is not investment; it is collateral. Idle capital earns no yield, so only entities with large treasuries or institutional balance sheets can bear it. As in all capital-intensive markets, the few who can afford inefficiency dominate it.
As users transact, they naturally seek reliability. A route through a large, well-funded node offers higher success probability and lower expected cost of failure. Over time, rational behaviour produces network gravity: small nodes cluster around larger ones, and traffic centralises to minimise latency, failure, and rebalancing expense. The result is a self-reinforcing topology where the “mesh” becomes a wheel, and the spokes lead to a handful of hubs.
Operational Complexity and 24/7 Constraints
Running a high-availability routing node is not a hobby; it is infrastructure. Continuous monitoring, automated liquidity rebalancing, fee optimisation, and channel management are mandatory to remain profitable. This demands professional staff, redundancy, and constant uptime. The archetype of the independent participant, transacting freely from a laptop node, dissolves in the face of economic reality. The surviving operators behave exactly like banks — capital providers offering transaction reliability in exchange for a spread.
Internal Netting and Custodial Incentives
As hub concentration grows, a second transformation occurs: internal cross-netting. Hubs with vast user bases can clear payments internally without touching the public network. A Lightning payment from one user of a hub to another becomes a simple database update — cheaper, faster, and risk-free from a liquidity standpoint. Once this model dominates, the hub effectively becomes a custodial clearinghouse, using the Lightning network only for occasional inter-hub settlements.
The number of actual, economic Lightning payments — those traversing multiple independent nodes — shrinks. Liquidity becomes captive within corporate silos. These entities batch their on-chain settlements, further reducing overall blockchain utilisation. Fees collected from users become the spread between internal ledgers and occasional base-layer redemptions. It is the same logic that transformed the gold standard into fractional reserve banking: too costly to redeem, too easy to issue claims.
The Hub-and-Spoke Convergence
The network, left to the natural selection of efficiency, converges on a hub-and-spoke model. It is not malice or design; it is arithmetic. Centralisation minimises failed routes, economises on liquidity, and spreads rebalancing costs over large transaction volumes. Independence dies not by coercion but by convenience.
The myth of peer-to-peer resilience fades into a technical museum piece — a network in name only, where all roads lead through custodians. Lightning, by its own internal logic, breeds the very institutions it was invented to displace. When transaction throughput is throttled and settlement is scarce, trust ceases to be optional. It becomes the medium of exchange.
VI. The Cost Curve That Kills “Everyday Cash”
The Lightning Network was marketed as the resurrection of digital cash — cheap, instant, and borderless. Yet when confronted with the arithmetic of its own fee structure, it collapses into precisely the opposite: a costly, fragile construct that punishes small payments and rewards intermediated volume. The economics are not a mystery; they are fatal.
Each Lightning transaction comprises multiple cost components — the base fee charged by each node in the route, a proportional fee based on the amount transmitted, and the failure-retry overhead that arises when routing attempts stall or collapse. These costs are additive, not abstract. The base fee applies per hop, meaning that every additional routing node compounds the expense. The proportional fee is typically a small percentage, but its accumulation across multiple hops transforms microtransactions into micro-taxations.
A) The Geometry of Cost Accumulation
Consider a small transaction — say, a few dollars’ worth of BTC. On a route of four hops, each with a base fee and proportional fee, the total effective cost often exceeds one percent even under ideal liquidity conditions. Under stress, that figure grows dramatically. When channels are unbalanced — the normal state of the network — routing algorithms must attempt multiple paths before finding one that succeeds. Each failure costs time and, in many cases, fee exposure through partially committed HTLCs.
Small payments therefore bear a disproportionate cost burden: they must compete for liquidity against higher-value transactions that offer nodes better return per locked satoshi. Rational routing policies naturally deprioritise low-value transfers. The network optimises itself not for inclusivity but for efficiency of yield.
B) The Feedback Loop of Failure
As channels saturate or fall out of balance, the probability of routing failure increases non-linearly. Each failed attempt triggers a new round of pathfinding and liquidity checks. Empirical analyses of Lightning’s live topology demonstrate that failure rates rise sharply for payments exceeding even modest fractions of total channel capacity — often as low as 0.01 BTC.
For small users, this manifests as unpredictability: payments that “should” succeed intermittently fail, while even successful transactions experience multi-second to minute-long delays. These are not software bugs; they are emergent from liquidity constraints and routing mechanics.
The loop is vicious. As failures mount, users gravitate toward custodial solutions with predictable performance. Custodians, in turn, batch internal transactions and act as surrogate liquidity providers, further starving the public network of balance diversity. The more users depend on them, the less resilient the network becomes — and the more justified the dependence appears.
C) The Death of Everyday Cash
Peer-to-peer cash lives or dies by marginal usability. It must make sense to send a penny as easily as a pound. In Lightning’s architecture, that economic calculus fails. A system where fees, retries, and liquidity management outweigh the transaction’s value cannot serve as daily currency. The claim of microtransaction capability is technically true and economically void.
In practice, the median user faces two choices:
Pre-custody funds with a hub, effectively trusting an intermediary for access and reliability; or
Operate independently, enduring recurrent payment failures, rebalancing costs, and mounting frustration.
Either path eliminates the defining property of cash — autonomy at negligible cost. The result is a bifurcated economy where convenience and control are mutually exclusive, and both are rationed by liquidity.
Lightning’s cost curve is not a quirk; it is a death sentence for small payments. As the marginal cost of reliability rises above the marginal value of everyday transactions, the system ceases to be currency at all. It becomes a boutique settlement network, a playground for high-value routing between custodians, and a mausoleum for the dream of peer-to-peer digital cash.
VII. Paper Claims and the Re-Invention of Custody
When direct settlement becomes a luxury, representation takes its place. The modern custodial wallet, the exchange, and the “crypto bank” do not fight Lightning’s constraints — they monetise them. By maintaining vast internal ledgers and offering instantaneous transfers within their own systems, they create an illusion of liquidity: instant, costless, and friction-free, so long as the user never tries to leave.
A) The Illusion of Instant Finality
Within a custodial environment, transactions appear miraculous. Alice sends “BTC” to Bob, and the transfer clears in milliseconds. No channels, no routing failures, no HTLC expirations. It feels like progress — until one remembers that no BTC actually moved. What changed was a database entry on the custodian’s internal ledger. The transaction’s speed derives not from cryptographic efficiency, but from centralisation. The custodian assumes the role of both counterparty and arbiter, guaranteeing that balances reconcile at its discretion.
This system works precisely because users rarely demand redemption. As long as internal transactions are cheaper and faster than true settlement, convenience becomes the narcotic that masks dependency. Each “free” transaction is underwritten by a silent assumption of trust — the custodian’s solvency, honesty, and operational integrity.
B) The Mechanics of Fractionalisation
Once transactions on the custodial layer outpace those on the base layer, fractionalisation pressure becomes irresistible. The equation is simple: if claim velocity exceeds redemption velocity, more claims can circulate than can ever be redeemed simultaneously.
This is not theoretical hand-wringing; it is the same process that transformed the gold standard into a paper economy. Gold’s physical scarcity made direct redemption slow and costly. Banks, recognising the asymmetry, issued more paper receipts than gold in reserve. So long as withdrawals remained rare, the system endured. The Lightning-anchored BTC ecosystem replicates this perfectly. A base layer throttled to five transactions per second cannot possibly redeem the aggregate of custodial balances in circulation. Redemption becomes the bottleneck; therefore, promises multiply because they can.
The incentive is structural. A custodian can create a synthetic balance with a keystroke and earn yield or transaction fees on claims that never touch the blockchain. Provided confidence persists, no user demands proof of reserve. And when confidence falters, the five-TPS constraint ensures that redemption cannot occur at scale. What was marketed as immutable scarcity becomes, in practice, an inconvertible script.
C) The Custodial Feedback Loop
As more users retreat from Lightning’s operational complexity, custodial platforms grow in dominance. Their internal ledgers become the true circulatory system of BTC commerce. On-chain transactions are reduced to periodic net-settlement events between major actors — exchanges, payment processors, and institutional treasuries. These entities batch hundreds of thousands of internal user transactions into a single blockchain entry, further abstracting the link between users and real BTC ownership.
The user, once promised self-sovereignty, ends up holding a numbered balance in a corporate database — a claim, not a coin. The irony is brutal: a technology conceived to eliminate intermediaries re-creates them, fortified by mathematics rather than law.
D) From Hard Limit to Elastic Supply
BTC’s vaunted 21-million cap applies only to the base chain. Lightning’s off-chain representations, combined with custodial ledgers, introduce de facto elasticity. There can be 21 million on paper, 21 billion in circulation, and no immediate contradiction — because redemption is neither required nor feasible. The same logic that birthed paper gold now governs paper Bitcoin.
In this architecture, scarcity is no longer a property of the asset but a function of access. The blockchain becomes a reserve ledger, a settlement network for a handful of large custodians. The rest of the world transacts in derivative claims, secure only until redemption day arrives — a day that the five-transaction bottleneck guarantees will never fully come.
BTC thus perfects the oldest cycle in finance: the migration from substance to symbol, from coin to claim, from cash to credit. What it calls “scaling” is, in fact, the resurrection of trust — the quiet return of the very intermediaries it pretended to destroy.
VIII. “Lightning Without Bitcoin”: Why Supply Becomes Elastic in Practice
The most uncomfortable truth about Lightning is also its most inevitable one: it does not require Bitcoin to function in practice. It requires belief in Bitcoin — the narrative of a scarce base asset, not the frequent redemption of that asset itself. As long as participants accept off-chain balances as equivalent to the underlying token, the system can operate indefinitely without touching the blockchain. That, in turn, makes the money supply elastic — not through code, but through confidence.
A) Off-Chain Accounting: Consensus Without Settlement
Lightning’s core mechanism is bilateral agreement. Two nodes maintain a private ledger — a channel — that reflects who owns what. Updates to that ledger are secured by pre-signed transactions, but those transactions are never broadcast unless a dispute arises. The vast majority of Lightning activity consists of these unfinalised states: accounting entries recognised by both sides but not yet recorded on the blockchain.
The moment participants decide that on-chain settlement is too costly, they simply delay it. The channel stays open, and the funds — or rather, the claims to them — continue circulating. Because Lightning transactions can be routed across multiple intermediaries, the same liquidity can underpin a far larger volume of off-chain transfers than its nominal value suggests. This is the genesis of elasticity: the velocity of claims grows while the underlying collateral remains static.
B) The Economics of Deferred Settlement
When settlement costs rise, rational actors choose to defer redemption. This behaviour mirrors fractional reserve dynamics: a system of circulating promises whose redemption base is perpetually insufficient. In Lightning, each channel is a bilateral reserve; each route, a temporary credit line. So long as participants have confidence in counterparties and can continue rolling over their obligations, the system functions. The scarcity of actual on-chain transactions becomes an advantage, not a liability — fewer settlements mean fewer fees.
But deferral comes at a price: the longer channels remain unclosed, the weaker the link between the claim and the asset. Liquidity is recycled, re-routed, and aggregated into payment flows far exceeding the collateral originally posted. Over time, what circulates are not bitcoins but synthetic derivatives of them — entries whose existence depends solely on the integrity and solvency of intermediaries.
C) Elastic Supply and the Myth of the Hard Cap
Bitcoin’s fixed supply of 21 million units is a cryptographic truth, but only on the base layer. The Lightning Network, combined with custodial intermediaries, detaches transactional volume from that limit. In economic terms, the effective money supply — the total amount of spendable claims denominated as “BTC” — can expand without bound.
A liquidity provider can create multiple overlapping channels backed by the same collateral, each circulating distinct balances among users. As long as no more than one set of claims attempts to settle simultaneously, the illusion holds. This mirrors the structure of shadow banking: rehypothecation of collateral, layered credit issuance, and a stable façade sustained by low redemption demand.
Thus, the “21 million” narrative remains pristine in rhetoric while the network quietly supports a multiple of that number in circulating claims. Marketing calls this scaling. Economics calls it leverage.
D) “Lightning Without Bitcoin”: The Terminal Irony
At sufficient abstraction, Lightning ceases to depend on Bitcoin at all. Nodes could, in theory, denominate channels in satoshis without ever anchoring them to the blockchain. As long as participants trust each other’s ledgers, the illusion of Bitcoin persists — a closed ecosystem of credit instruments bearing the logo of a coin no longer moving.
The end state is Lightning without Bitcoin: a web of synthetic balances whose value rests on faith in their equivalence to a reserve that no longer redeems. The system can grow indefinitely because it has severed itself from its foundation. Bitcoin becomes mythology; Lightning becomes the economy.
The irony is final and complete. A network born to eliminate elasticity ends by institutionalising it. The scarce digital gold becomes the collateral base for an empire of promises, and the promise of a trustless future gives way to the oldest monetary trick in history: inflation by abstraction.
IX. Systemic Risks at Scale
As Lightning evolves from experiment to infrastructure, its systemic vulnerabilities harden into inevitabilities. Every “scaling solution” built atop a throttled base layer imports a catalogue of hazards long familiar to monetary history. These risks are not speculative; they are structural — the logical consequences of operating a high-velocity credit system anchored to a glacial settlement base.
A) Custodial Concentration and Correlated Outages
The consolidation of liquidity into a handful of major custodians and routing hubs produces a brittle topology masquerading as resilience. The illusion of decentralisation depends on the presence of many nodes, but the reality is that a small number of liquidity providers carry the transactional load. When one of these central hubs experiences an outage — technical, operational, or regulatory — vast portions of the network stall.
This concentration risk mirrors that of modern banking infrastructure, where a failure at a clearing house can paralyse entire markets. In Lightning, however, recovery is slower and coordination weaker. Channels tied to the failed hub become inert until force-closed, which, under the five-TPS limit, cannot occur in aggregate. Thus, a localised failure escalates into a network-wide liquidity freeze.
B) Liquidity Crunches and Payment Blackouts
Lightning’s liquidity is static capital, not elastic credit. During periods of price volatility or mempool congestion, participants hoard liquidity, disable channels, or increase routing fees to avoid loss. The collective effect is a liquidity crunch — a period where routing capacity evaporates, payments time out, and the network effectively blackouts.
In traditional finance, central banks supply emergency liquidity to stabilise flow. Lightning has no such lender of last resort. Its liquidity creation mechanism — channel opening — requires the very base-layer access that becomes prohibitively expensive in a crisis. Thus, during stress, the system contracts precisely when expansion is needed. The architecture guarantees procyclicality: euphoria amplifies liquidity, fear annihilates it.
C) Legal and Regulatory Capture
As custodial hubs assume the dominant role, they become natural choke points for regulation. Jurisdictions will demand KYC, AML, and reporting compliance from these large intermediaries. The supposed decentralisation of Lightning provides no shield; the economic reality is a concentration of control in entities large enough to regulate.
Over time, the network morphs into a regulated financial utility. Permissioning seeps in through the side door — not through protocol change, but through the economic capture of the few who matter. What remains of the peer network becomes ornamental, a fig leaf covering the re-institutionalisation of the system.
D) Socialised Losses and Redemption Impossibility
When a major intermediary fails — whether through insolvency, fraud, or technical collapse — the losses cannot be contained. Users’ balances, being claims rather than coins, cannot be redeemed promptly through the base chain. With only five transactions per second available, mass withdrawal is arithmetically impossible.
The bottleneck transforms every large custodian failure into a systemic event. Users, unable to exit, are forced into collective loss-sharing. The very property Bitcoin was meant to abolish — the socialisation of private risk — resurfaces, re-engineered into the network’s mechanics.
E) Moral Hazard and the Rise of Yield Games
In an ecosystem where redemption is costly, slow, and statistically unlikely, prudence dies first. Custodians and liquidity providers face irresistible temptation to rehypothecate balances or offer yield products on synthetic BTC — precisely because the friction of exit discourages verification. Users, lulled by the appearance of constant liquidity, deposit ever more capital into the system, unaware that the underlying reserves may already be pledged multiple times over.
The feedback loop is well-known: opacity breeds overextension, overextension breeds fragility, and fragility ends in collapse. The five-TPS anchor ensures that when it happens, redemption will not mitigate the damage — it will merely reveal it in slow motion.
Lightning at scale becomes indistinguishable from the financial system it claimed to disrupt: centralised, leveraged, and vulnerable to contagion. The rhetoric of decentralisation dissolves under the arithmetic of throughput and liquidity. Scarcity at the base layer forces abundance of promises above it. And promises, as history proves, always break at scale.
X. Rebuttal to the Stock Slogans
The defenders of BTC and Lightning rely not on analysis but on catechism — a repertoire of slogans chanted with religious conviction, designed to substitute repetition for reason. Each slogan collapses under the weight of arithmetic. What remains, when the rhetoric is stripped away, is a network built on contradiction: a scarcity fetish dressed as a payment system.
A) “Not your keys, not your coins.”
Once a declaration of sovereignty, this slogan has degenerated into an epitaph. In a system throttled to five transactions per second, true self-custody is mathematically prohibitive for the majority of users. Every opening, every closing, every balance adjustment demands scarce on-chain space — a commodity priced far beyond the reach of the ordinary participant.
Thus, most users face a binary choice: hold their coins in cold storage and abandon transacting altogether, or surrender them to custodians who promise liquidity and ease. The former is isolation; the latter is dependency. There is no middle ground.
The irony is brutal. The slogan meant to defend ownership now describes its absence. “Not your keys, not your coins” has become a historical inscription carved over the tomb of peer-to-peer cash — a warning, not a boast.
B) “Layer 2 fixes this.”
This slogan represents the theology of denial — the belief that abstraction can overcome arithmetic. Layer 2, we are told, rescues BTC from its own limitations by shifting activity off-chain. But the fundamental bottleneck remains unchanged: every channel must open and close on-chain. Every rebalancing ultimately competes for the same constrained throughput.
Layer 2 does not fix the problem; it relocates it. It replaces the simplicity of direct transaction with the complexity of deferred settlement. It economises on some transactions while entrenching the very scarcity it pretends to bypass. The more Lightning grows, the greater its dependency on the base layer it cannot expand.
Worse, the illusion of scalability encourages complacency. By branding abstraction as innovation, BTC’s architects have built a monument to circular dependency — a system whose success guarantees its failure.
C) “Routing scales magically.”
Routing, the mechanical heart of Lightning, is treated by its evangelists as an act of faith. They speak of “mesh networks” and “instant payments” as if liquidity were infinite and topology frictionless. In reality, routing scales only until it collides with three hard ceilings: liquidity imbalance, HTLC limits, and fee accumulation.
Every hop consumes capital and introduces risk; every additional channel multiplies coordination overhead. The network cannot scale beyond the capital its participants are willing to immobilise. As liquidity concentrates into well-funded hubs, routing becomes efficient — not through decentralisation, but through centralisation. The “magic” is the disappearance of peers.
At small scale, Lightning resembles a network. At large scale, it converges on a clearinghouse. That is not scaling; it is consolidation.
These slogans — talismans for the uninformed — exist to disguise a single truth: a five-TPS foundation cannot bear a global monetary system. The rhetoric of freedom, autonomy, and peer-to-peer exchange collapses under the physics of capacity. The slogans remain only as liturgy for the faithful, recited over a protocol that has already buried the very ideals it claims to defend.
XI. The End State: A Fake Standard
When the last layers of rhetoric are stripped away, the destination is unmistakable. You do not arrive at a world of peer-to-peer digital cash. You arrive at a replica of the old financial order—reborn under a different banner, but identical in substance. The slogans of freedom remain, but the structure is the same: the public holds promises; the few hold coins.
Lightning and the five-transaction-per-second base chain are not the engines of a revolution; they are the scaffolding of a new custodial aristocracy. Square, Coinbase, and their ilk will not build systems for self-custody; they will build markets for dependency. Square will “sell BTC balances” that never touch the blockchain, internalising transactions within proprietary ledgers. These balances will settle not in satoshis but in accounting entries, redeemable—if ever—through congested, fee-choked channels back to the chain.
Corporate treasuries will warehouse UTXOs as reserves, issuing internal claims the way banks once issued gold certificates. Exchanges will clear vast volumes of “BTC” daily without a single on-chain transaction. The token will serve as collateral for an economy of abstractions—layered liabilities circulating with the speed of belief and the fragility of trust.
This is not evolution; it is regression. The decentralisation narrative becomes a marketing device, a veil stretched thin over centralised plumbing. The system’s efficiency derives not from cryptography but from the same sleight of hand that sustained paper gold: trade promises faster than they can be redeemed, and pray that nobody calls them in at once.
The difference between BTC and the fiat system it derides is therefore cosmetic. Both rely on scarcity as theatre, not as mechanism. Both are run by financial intermediaries who monetise access to the ledger. Both depend on the compliance of the herd, convinced that representation equals reality.
The result is the birth of a fake standard—a tokenised gold standard without gold, a network whose decentralisation exists only in documentation. BTC becomes not the currency of autonomy but the collateral of conformity, its scarcity guarded by those it was meant to replace.
The irony is almost too rich: a project born to eliminate middlemen culminates in their enthronement. Its revolution ends not in emancipation, but in paperwork. Peer-to-peer cash was the promise. Paper BTC is the delivery. #FakeStandard #PaperBitcoin
XII. What Would Be Required to Escape This Trap
To escape this engineered cul-de-sac, the system would need to reject nearly every superstition that currently defines BTC orthodoxy. The path to genuine digital cash is heretical precisely because it is mathematical. It requires abandoning the religion of artificial scarcity and embracing the economic law that utility is proportional to throughput. Freedom, in a monetary system, is not a function of slogans; it is a function of capacity.
A) Orders of Magnitude in Base-Layer Throughput
The first and most unyielding requirement is scale at the foundation. A system aspiring to global utility cannot operate at five transactions per second — not for a city, not for a small nation, and certainly not for the planet. To replicate the liquidity of cash, throughput must expand by several orders of magnitude. This is not an option; it is a precondition.
Only when the base layer can process millions of transactions per second does the architecture achieve the density required for peer-to-peer exchange. At that point, off-chain abstractions become conveniences, not necessities. The network ceases to be a rationed resource and becomes a public utility: universal, accessible, and economically inclusive.
B) Predictable, Low, and Stable Fees
A true cash system demands cost predictability. Volatile fee markets destroy usability because they replace certainty with auction. The fee for settlement must remain both low and stable, independent of demand shocks. This is not merely an engineering challenge; it is a structural imperative.
When the cost of participation is known and negligible, economic activity migrates on-chain rather than fleeing to custodians. The mempool becomes an accounting buffer, not an exclusion zone. The user’s right to transact ceases to be contingent on market timing.
C) Settlement Capacity for Universal Redemption
Without redemption capacity, ownership is an illusion. A genuine monetary system must allow every holder, at any time, to redeem their claim directly on the base ledger. This requires settlement capacity sufficient to absorb total demand — not in principle, but in practice.
If the ledger cannot process withdrawals, it ceases to be money and becomes a promise. The hallmark of a sound system is its indifference to redemption; it does not fear the exit because it can handle it. The current five-TPS bottleneck guarantees the opposite: a system perpetually insolvent in throughput.
D) Incentives for Competitive Provision
Monetary liberty requires competition — not in ideology, but in operation. The network must reward those who provide capacity and efficiency, not those who hoard liquidity or monopolise access. Mining and transaction processing should be competitive markets, driven by productivity and transparency. Custodial concentration must be economically irrational, not inevitable.
That means scaling horizontally, where every node that adds capacity strengthens the system rather than fragments it. The architecture must favour throughput and accountability, not narrative and scarcity theatre.
E) Reality over Rhetoric
Finally, the system must dethrone mythology. Scarcity alone does not make sound money; liquidity, verifiability, and redemption do. The obsession with limiting block size and worshipping “decentralisation” at the cost of utility is the cardinal error — a confusion of virtue with vacancy. Arithmetic is the final judge, and arithmetic is merciless.
Without these heretical conditions — industrial-scale throughput, stable fees, redeemable settlement, and incentives aligned with openness — BTC remains a monument to its own contradictions. The rhetoric will continue to outpace the reality until the network collapses under the weight of its inefficiency.
For Bitcoin to fulfil its original promise as digital cash, it must become what it was designed to be: a system that scales. Anything less is theatre — a grand illusion performed for an audience too entranced to notice that the curtain never lifts.
XIII. Conclusion
The arithmetic cannot be romanticised away. A network chained to five transactions per second is not a revolution; it is a rationing system. It guarantees custodial dominance because scarcity of settlement space transforms freedom into privilege. Lightning, though ingenious as an engineering exercise, is shackled to an economic impossibility: it promises infinite scale on a foundation that cannot grow. Clever code cannot compensate for broken math.
The result is not peer-to-peer cash but a hierarchy of credit. The “hard money” mythology dissolves into a swamp of soft claims — ledgers of promises, balances without redemption, abstractions of ownership backed by faith instead of finality. Lightning does not fix Bitcoin’s constraints; it institutionalises them, turning every channel into a deferred settlement, every user into a counterparty, and every custodian into a central bank in miniature.
When settlement is scarce, trust metastasises. It creeps into every gap the blockchain cannot fill, seeping through intermediaries who promise liquidity and deliver dependency. The new financial order looks suspiciously like the old one, its priests now fluent in cryptographic jargon instead of Latin, but preaching the same gospel of managed scarcity and deferred redemption.
The conclusion is merciless in its simplicity. Lightning is not the cure; it is the symptom. BTC is not the hard standard it claims to be; it is the paper claim built upon one. Arithmetic, not ideology, writes the epitaph: a system that cannot scale cannot free. When trust becomes the lubricant of transaction, the machinery of power reawakens. And in the ledger’s cold arithmetic, the revolution ends where it began — with the few owning the coins and the many holding the promises.
Real BitCoin, the Euler Circuit of mercantilism