When Five TPS Becomes a Sacred Bull
How They Shrank Bitcoin, Then Pretended It Was a Feat
Keywords
BTC Core; non-scaling ideology; five TPS; hardware regression; protocol stagnation; miner-dominated network; arXiv:2506.14197; propagation topology; digital cash; anti-progressSubscribe
1. Opening Section – The Farce Introduced
A system conceived for global digital cash should have expanded with the world that built it. That is the expectation any rational mind would hold: that as processors quickened, as bandwidth widened, and as storage fell in cost to triviality, the machinery of a ledger designed to handle human economic activity would rise in tandem. Yet the custodians of BTC Core have performed a curious inversion. They have taken a design that needed nothing but time and natural hardware progress to grow, and they have stuffed it into a rigid sarcophagus of five transactions per second. From this coffin, they offer theological proclamations about “safety” and “purity,” as though stagnation were an achievement, as though engineering could be measured by how small a system can be made before it collapses.
There is a priestly quality to their declarations. They whisper about decentralisation as though numbers obey scripture rather than physics, insisting that the world must adapt to the smallest and weakest computers, not the other way around. It is a cult of miniaturisation, a doctrine of intentional limitation, a creed that worships regression as if shrinking a system makes it more profound. The farce lies in the contradiction: the original protocol, left alone, would have spread its wings simply by riding the curve of normal technological advancement, but the modern custodians have clipped those wings and declared the mutilation progress.
The central absurdity is therefore unavoidable. A protocol that would have grown automatically with every generational leap in silicon has been frozen for ideological reasons, not technical ones. The world’s computing infrastructure improved; BTC Core chose to act as though it had deteriorated. The world built vast data centres; BTC Core demanded Raspberry Pis. The world moved forward; BTC Core moved inward, downward, backward, every step defended with missionary zeal. What should have been the straightforward maturation of a global monetary mechanism has instead become a monument to voluntary deterioration, a system that performs less over time while congratulating itself for the achievement.
They have dressed decline as virtue. They have mistaken deliberate weakness for strength. And they have done so with the unshakeable confidence of a priesthood convinced that their creed, however irrational, must be upheld even at the expense of function.
2. Historical Baseline – What the Original Bitcoin Actually Allowed
In the early era of Bitcoin, the promise was straightforward and rooted in the engineering facts of its day: a peer-to-peer ledger built atop hardware whose capabilities improved nearly automatically, and a network whose throughput could expand if nothing critical blocked it. In that environment, every advance in processor speed, every gain in network bandwidth, every drop in storage cost carried with it the latent potential of increased transaction capacity. The original protocol did not demand radical rewrites to scale; it required only the passage of time, the inertia of hardware improvement, and sensible network propagation.
Hardware Trends & Doubling Logic
Moore’s law, improvements in network latency and bandwidth, falling cost per bit, and more efficient peer-to-peer communication—they all conspired to create a natural upward trajectory for any system that did not place artificial caps on growth. If one begins with a modest transactions-per-second (TPS) baseline—say 5 TPS—then allowing the hardware and network environment to evolve should, in principle, lead to roughly doubling capacity in a fixed interval such as 18 months. After 18 months: ~10 TPS; after 36 months: ~20 TPS; after 54 months: ~40 TPS; after 72 months: ~80 TPS; and so on. The mathematics of doubling are plain. The original Bitcoin design, unshackled by artificial ceilings, would therefore have been on a clear path of growth.
Block Propagation & Network Reality
Propagation latency and peer-topology were also central in the original system. Blocks had to traverse the network swiftly enough to keep forks rare, miners synchronized, and users confident. The original protocol permitted blocks of moderate size and interval (10 minutes, 1 MB initially) and counted on the gradual improvement of network infrastructure to handle larger or more frequent blocks if required. In other words: the system was built for evolution, not self-imposed stagnation.
The recent paper titled “The Redundancy of Full Nodes in Bitcoin: A Network-Theoretic Demonstration of Miner-Centric Propagation Topologies” (arXiv:2506.14197) makes a striking contribution to the historical baseline and network anatomy. The authors demonstrate, via graph-theoretic analysis, that home-hosted full nodes in the BTC network are essentially peripheral to the transaction-to-block inclusion path; instead, a densely interconnected miner clique dominates propagation topology. (export.arxiv.org) This means that although the original ideal was full nodes participating meaningfully, the network—by its structural dynamics—gravitated toward a centralised propagation core.
Why This Matters
This matters because when one looks back at what the original system allowed, one sees far more potential than what the present system permits. The combination of improving hardware, improving network connectivity, and growing adoption all pointed toward significantly higher TPS and larger blocks (or more frequent ones) if the protocol simply remained flexible. Instead, the current system ratifies near-stalemate throughput. The historical baseline shows that growth wasn’t only possible—it was practically built in. Yet the present engineers choose a path of deliberate non-growth.
Thus the original Bitcoin actually allowed a trajectory of scaling rooted in hardware improvement and network evolution, but the custodians of the system have opted to stand still. The network topology analysis (via arXiv:2506.14197) underlines how full-node empowerment was always more myth than reality in practice, which further corrodes the rationale of the “keep it small” argument. In short, the baseline was legacy-capable; the present is self-limited.
3. The Doubling Problem – What Five TPS Would Have Become
Five transactions per second is not a destination; it is a starting pistol. Treated correctly, it is the opening note in a geometric progression, not a ceiling chiselled into stone by a committee of frightened caretakers. Take the most mundane assumption: a doubling of sustainable throughput roughly every eighteen months, driven by nothing heroic, just routine improvements in bandwidth, latency, processing, and memory. Begin at 5 TPS. After eighteen months, 10 TPS. After three years, 20 TPS. After four and a half years, 40 TPS. At the six-year mark, 80 TPS. Seven and a half years: 160 TPS. Nine years: 320 TPS. One more cycle and the figure stares down 640 TPS. At that point, the system would be in the territory where whole industries could sit atop it without even straining.
This is the picture produced not by fevered optimism but by dull arithmetic. No protocol revolution, no tortured “layer-two” contortions, no cultish blog posts declaring that physics must bow to ideology. Simply the admission that as the rest of computing becomes faster and cheaper, a network designed to ride that curve should expand in lockstep. Had the original design been left unmolested—had the code not been shackled by artificial limits—the natural consequence of technological doubling would have carried throughput far beyond the current, arbitrarily constricted figures that BTC Core treats as sacred.
The most damning point is that “doing nothing” in terms of artificial throttling would have surpassed present performance. The act of freezing capacity is not neutral. It is not caution. It is not prudence. It is an intervention. To keep a system at 5 TPS in a world where everything it runs on has improved several-fold requires active resistance to growth. It requires committees, narratives, and a steady stream of moralising about why more capacity would somehow be corrupting.
When the numbers are written plainly—5, 10, 20, 40, 80, 160, 320 and onward—the charade is exposed. The protocol did not fail to scale; its custodians refused to let it. The limit is not technical but ideological, a self-imposed famine in the middle of a banquet of available computing power.
4. The Regression Fetish – Why BTC Core Worships Small Hardware
BTC Core has elevated a single, brittle idea into religious law: the network must be shaped to accommodate the weakest, most impotent hardware imaginable. Not contemporary machines, not commercially deployed servers, not the infrastructure that powers global communications—no. The system must bend to the constraints of the smallest, slowest, least capable device that a self-appointed guardian class believes “ought” to be able to run a node. And from this decree flows the rest of the dogma.
This is not engineering; this is asceticism masquerading as design. When a movement worships tiny machines, it inevitably begins amputating everything that threatens their continued involvement. Throughput becomes a heresy. Bandwidth becomes a threat. Storage becomes a moral failing. Computational growth—normally the lifeblood of any digital system—is framed as a danger requiring vigilance and suppression.
Thus the inversion takes hold. In every other technological domain, hardware scales upward to meet the demands of software. Nobody designs modern communication protocols around dial-up modems. Nobody builds cloud systems squeezed to the limits of recycled smartphones. Progress does not apologise to obsolete hardware; obsolete hardware either adapts or dies.
But in BTC Core’s universe, this logic is flipped. Instead of letting the network grow with the world, they carve the network down to the size of outdated consumer devices. What should expand is shrunk. What should evolve is ossified. They choose to shape the protocol around machines that time itself has tried to retire. The priority is not capability but a theatrical form of inclusivity: the symbolic gesture that “anyone” can run a node, provided “anyone” is defined narrowly as a hobbyist with a fondness for underpowered boards and ideological literature.
The result is deliberate anti-progress. The chain is strangled to fit obsolete hardware, not because the world demands it, but because the priesthood has mistaken technological minimalism for moral purity. In this worldview, the fact that a decade-old device can keep pace is not a warning sign of catastrophic underuse of modern infrastructure—it is the very point. Throughput becomes a casualty of nostalgia, crippled so that yesterday’s machines are not left behind. This is not caution; it is sabotage dressed as egalitarian virtue.
5. The False Decentralisation Argument – A Theatre of Miniature Nodes
The central dogma of BTC Core is recited with the reverence of a catechism: “Anyone can run a node, therefore the system is decentralised.” It is a comforting line for people who enjoy the romance of participating in history from the safety of their living rooms. They are told that their tiny box on a shelf is a guardian of consensus, a sentinel of monetary integrity, an equal among equals. The only requirement for this supposed political power is that the protocol be throttled so viciously that even an underfed board with a USB drive can keep up. Hence the crusade for small blocks, low throughput, and the eternal five-TPS purgatory. The sacraments of this church are minimal hardware and artificial scarcity.
Then comes the network graph, and with it, the unflattering light of mathematics. The paper The Redundancy of Full Nodes in Bitcoin: A Network-Theoretic Demonstration of Miner-Centric Propagation Topologies makes the obvious unforgivable: it demonstrates that home-hosted full nodes do not sit in the centre of anything. They are not hubs; they are not arteries; they are not even minor capillaries. They are decorative capes flapping on the shoulders of spectators. By applying complex network analysis, eigenvalue centrality, and simulations across the BTC and BSV networks, the paper shows that block and transaction propagation are dominated by a densely interconnected clique of miners, while full nodes are relegated to the periphery, structurally excluded from transaction-to-block inclusion paths. (arXiv)
In other words, the people promised sovereignty are not in the room where decisions happen. The topology itself refutes the fairy tale. The graph does not care about Reddit slogans or conference sermons; it shows edges, degrees, paths. And those paths overwhelmingly run through miner infrastructure, not through the hobbyist nodes that BTC Core claims to be defending by clamping throughput. Full nodes can download, validate, and chatter amongst themselves, but they do not shape the propagation backbone. They are, in operational terms, redundant to the process they were told they command.
This shreds the central justification for small blocks and microscopic throughput. If the network’s real propagation core is miner-centric, then deforming the protocol to suit the limitations of consumer toys does not protect decentralisation; it merely lowers the ceiling for everyone while preserving the de facto hierarchy already in place. The small-block restriction has no technical foundation in the actual topology. The graph shows a scale-free, small-world structure where a miner clique forms the spine of consensus propagation, rendering the “every Raspberry Pi is sovereign” story an elaborate piece of theatre. (arXiv)
The rhetoric claims that keeping blocks tiny and throughput anaemic is necessary so that “anyone” can influence the system by running a full node. The topology proves that “anyone” is politely confined to the balcony, watching the miners handle the real work. This is not decentralisation; it is a pageant of decentralisation. The small-hardware fetish does not democratise power; it ritualises powerlessness and wraps it in sentimental language. The protocol has been crippled in honour of spectators who never held the influence they were promised.
6. The Ideological Machinery – How Non-Scaling Became a Religion
What began as a set of engineering parameters has been elevated, through years of repetition and insecurity, into a doctrine of moral purity. BTC Core has cultivated a worldview in which the refusal to scale is not merely a technical preference but a sign of spiritual rectitude. The block size limit, once a pragmatic placeholder, has been refashioned into a commandment; throughput has become a test of virtue; stagnation, a sacrament. What any sane engineer would treat as improvable design constraints are now defended as if they were fragments of divine revelation.
This is how a movement replaces engineering with creed. “Safety” becomes the catch-all catechism, invoked whenever someone suggests the heresy that a global monetary system might need more than five transactions per second. “Purity” becomes the codeword for paralysis, used to quarantine any discussion of scaling behind a wall of imagined threats. And “decentralisation,” stripped of any grounding in the network topology that actually exists, becomes a talisman waved at critics to ward off the need for adult responsibility.
The transformation is as methodical as it is absurd. First, the engineering decision is frozen. Next, the frozen decision is moralised. Then the moralisation is used to smother dissent. A technical ceiling becomes a moral ceiling. A throughput cap becomes a character trait. The refusal to scale becomes a symbol of wisdom, restraint, enlightenment—anything but what it actually is: an inability or unwillingness to embrace the system’s intended global role.
And here lies the contradiction so grotesque it borders on the comic. BTC Core evangelists proclaim global adoption, universal usage, a planet-wide economic infrastructure. They speak with prophetic tone about billions of users. They place themselves at the centre of technological destiny. Yet they engineer a system whose capacity is microscopic, fragile, and intrinsically hostile to anything resembling real-world demand. They sell the vision of a global network while building the plumbing for a village.
This inversion—this grand ideological contortion—is the hallmark of a movement that long ago replaced ambition with asceticism. Scaling is framed as corruption. Capacity is framed as danger. Economic activity is framed as a threat to the system. The religion demands that the network remain small, predictable, and conveniently manageable for the guardians who have appointed themselves its moral custodians.
Thus non-scaling becomes a test of loyalty. To question the sacred ceiling is to expose oneself as reckless. To advocate for normal technological evolution is to announce one’s impurity. The community is shaped by sermons of scarcity, homilies about fragility, and a lingering suspicion that any increase in throughput is an assault on virtue.
This is not how functional systems grow. It is how dogmas entrench themselves. The tragedy is that what should have been a straightforward engineering discipline has been contorted into a symbolic identity—one that treats global adoption as marketing copy while treating the capacity required for global adoption as blasphemy.
7. The Economic Consequences – Fees, Congestion, and Self-Inflicted Irrelevance
A system designed for digital cash cannot survive long under the theology of deliberate scarcity. Yet BTC Core has constructed an economy in which scarcity is not the accidental result of demand but the engineered outcome of doctrinal limitation. By enforcing microscopic throughput, the network manufactures congestion; by manufacturing congestion, it manufactures fees; by manufacturing fees, it manufactures exclusion. This is not a side-effect—it is the predictable economic signature of a system that has rejected its own purpose.
When block space is capped at a level suited to hobbyist laptops and nostalgic hardware, the first victims are micro-transactions. The smallest payments—the ones that form the foundation of digital cash systems—are priced out of existence. A system that once promised the fluidity of pennies and fractions of pennies now demands that users treat every transaction as a strategic decision, an event to be rationed, a burden to be justified. The trivial and everyday become economically impossible. The casual becomes a luxury. The very category of “digital cash” evaporates under fee pressure, leaving only high-value transfers that can tolerate absurd friction.
Congestion is not accidental; it is the inevitable outcome of sealing a system in a five-TPS coffin while publicly fantasising about global adoption. Demand outstrips capacity, queues form, fees spike, and the ordinary user is left standing outside the gates, priced out by a limit that exists solely to comfort an ideological minority. What begins as a technical ceiling ends as a social filter. Those with means continue to participate; those without are quietly expelled.
This stagnation destroys utility. It suffocates the ecosystems that would have flourished atop abundant, inexpensive transactions: micro-payments, streaming commerce, machine-to-machine settlement, high-frequency gaming, IoT economies, and the vast texture of interactions that only become viable when transaction costs approach zero. All of it collapses under manufactured scarcity. A system that could have served billions instead retrenches into a boutique settlement layer, arrogant enough to call the retreat strategy.
The economic consequences reveal how thoroughly the original purpose has been abandoned. The protocol becomes a showroom piece, admired for its purity while being too delicate to use. Fees become the gatekeepers of participation. Congestion becomes a feature. Exclusion becomes an unintended declaration of priorities. The message is unmistakable: ordinary users are dispensable if their inclusion threatens the ideological comfort of stagnation.
Thus the digital cash system becomes a museum exhibit. Instead of a universal medium for everyday exchange, it becomes a playground for speculation, fee bidding, and artificially scarce transaction space. The irony is brutal: the network that promised economic inclusion engineered its own irrelevance by mistaking scarcity for sophistication.
8. The Network Consequences – A System Starved of Data
A network designed to carry economic activity cannot survive on starvation rations. Yet BTC Core has institutionalised scarcity so aggressively that the system exists in a state of permanent malnutrition. Artificially minimal throughput ensures that the chain never ingests enough data to develop resilience, never grows enough to evolve its economic structures, and never accumulates the richness of real-world usage that hardens a network against failure. A system deprived of data is a system deprived of life.
In a healthy digital cash architecture, growth is organic. Transactions flow. Markets form. Enterprises experiment. Business models attempt, succeed, or fail. Developers build services that assume continuous availability of cheap, abundant on-chain actions. The ledger becomes an environment for innovation. But a chain locked to five transactions per second cannot host this process. It cannot accommodate experimentation at scale. It cannot handle the complexity of real demand. It cannot serve as the substrate for anything except cautious, rationed usage. Every industry that would have tested it, stretched it, and strengthened it simply moves on.
Enterprises do not bet their infrastructure on a system that gasps under trivial load. No serious business architect sits down and says, “Our payment flows should compete for scarce block space against a global population.” The economics alone make adoption irrational. The technical constraints make it impossible. Businesses depend on predictable, abundant throughput—conditions BTC Core intentionally rejects. The result is a network that remains forever at the proof-of-concept stage, a decade-old prototype sealed behind glass.
The brittleness is structural. When a blockchain is denied throughput, it is denied the opportunity to develop the distributed robustness that comes from high transaction volume. It remains fragile, untested, and shallow. And because the chain cannot process meaningful economic activity, users are pushed into off-chain workarounds—solutions that require trust, custodians, coordination, and liquidity games. These off-chain systems are not supplements. They are crutches for a protocol too constrained to walk unaided.
Lightning, channel networks, state pools, custodial hubs—each one is a monument to the failure of the base layer. They exist because the base layer cannot scale. They are necessary only because the throughput ceiling remains ideologically enforced. And each layer of workaround introduces fragility, centralisation, and failure modes that the base protocol never required. A system that could have thrived on simplicity instead becomes a tower of kludges, a labyrinth of compensations for a wound that was never technical—it was self-inflicted.
The starvation of throughput therefore leads to the starvation of progress. Developers limit ambition because the chain cannot support ambitious designs. Markets remain stunted because the chain cannot support real-world demand. Enterprises stay away because the chain cannot support enterprise-grade volume. Instead of being a foundation, BTC Core becomes an artefact: brittle, delicate, and dependent on external scaffolding to do what the protocol itself should have done naturally.
This is the network consequence of ideological non-scaling: a system too fragile to rely on, too constrained to build on, and too deliberately weakened to ever fulfil its intended role. A global digital cash system reduced to a skeletal ledger, not by incapacity but by the persistent, doctrinal refusal to let it breathe.
9. The Off-Chain Escape Fantasy – LN as a Symptom of Failure
Lightning did not emerge from brilliance. It emerged from desperation. It is the architectural equivalent of punching a hole in the wall because the door has been welded shut. When a system restricts itself to five transactions per second—a volume so microscopic it cannot even serve a mid-sized retailer—some kind of workaround becomes inevitable. And so LN was born, not as a triumph of layered design, but as a frantic bypass graft for a protocol whose arteries were intentionally constricted.
Lightning exists because the base layer cannot do its job. It is a network built atop the admission of failure: the failure to scale, the failure to support volume, the failure to behave like a digital cash system. Every LN channel is a confession. Every routed payment is testimony. The very existence of LN declares, silently but unmistakably, that the underlying ledger was crippled on purpose.
Its dependence on liquidity routing exposes this with particular cruelty. A payment cannot simply be broadcast; it must navigate a maze of channels, each one requiring sufficient inbound and outbound liquidity. This transforms the concept of permissionless digital cash into a game of resource management, trust, and pathfinding. Payments fail not because of double spends or network issues but because someone, somewhere, does not have enough liquidity configured in the correct direction. The problem does not lie with cryptography. It lies with the artificial bottleneck that forced users into an under-engineered maze.
And the topology reveals its own indictment. Lightning relies on hub-like structures, central points of liquidity gravity, and entities willing to lock capital into channels. The trustlessness is partial at best; the architecture inherently favours well-capitalised routing nodes whose reliability becomes a de facto requirement. This is not the egalitarian universe promised by the ideology of “anyone can run a node.” It is a structure where liquidity and central hubs dominate, because the base layer cannot process the activity directly.
Lightning is not a scaling solution. It is an escape hatch. Its entire existence is predicated on the suffocation of the base network. If blocks were allowed to grow with hardware, if throughput were permitted to rise naturally, if the system behaved like the digital cash mechanism it was designed to be, LN would have no purpose. It would remain a theoretical curiosity, not a mandatory lifeboat for users trying to sail around a self-created reef.
Even the rhetoric surrounding LN reveals its origins in failure. It is marketed as innovation, but every justification traces back to the same root: the base chain is intentionally throttled. Instead of fixing the root cause—arbitrary constraints designed to satisfy ideological purity—users are pushed into a labyrinth that solves none of the underlying issues and introduces a gallery of new ones.
Lightning is not the future. Lightning is the admission that BTC Core burned the path to the future and called the ashes decentralisation.
10. The Psychological Component – Why Regression Is Defended
A movement does not cling to regression by accident. It requires a psychology—a shared emotional architecture—that sanctifies decline and repackages fear as wisdom. BTC Core’s refusal to scale is not sustained by technical argument but by cultural temperament, one shaped by anxieties about responsibility, a fetish for minimalism, and a collective need to justify stagnation as an elevated form of insight.
The fear of scaling is the first pillar. Scaling introduces real-world consequences. It demands reliability, throughput, resilience, and engineering maturity. It exposes the system to scrutiny beyond hobbyist circles. To scale is to grow up, and to grow up is to face the possibility of failure in full public view. For a culture that has built its identity on the illusion of immaculate correctness, this prospect is intolerable. Better to shrink the system than confront the demands of expansion. Better to define ambition as danger than to risk revealing inadequacy.
Beneath this lies an aversion to responsibility. A global digital cash system carries obligations—to users, to commerce, to stability, to the implementation of a design capable of bearing actual economic weight. Responsibility requires discipline and competence. It requires acknowledging that engineering choices affect millions. But by limiting throughput, by constructing a system that can barely serve a small town, the community protects itself from the burden of stewardship. Regression becomes a sanctuary. If the network never scales, it never has to be accountable.
Minimalism fills the vacuum left by this avoidance. Instead of being a design principle, it evolves into a fetish: the worship of the smallest possible form, the fewest possible functions, the narrowest possible bandwidth. Minimalism becomes a lifestyle masquerading as technical principle, a way to turn constraints into aesthetic preferences. A system constrained by fear can be rebranded as a system refined by art. Every missing feature is framed as elegance. Every limitation becomes an intentional stroke of purity. The chain is not small because it failed to grow; it is small because smallness is a virtue.
Then comes the ritual self-congratulation. Scarcity is transformed into a badge of honour. A chain that processes almost nothing is praised for being “disciplined.” Fees that exclude ordinary users are framed as “market efficiency.” Congestion is spun as “success.” Every symptom of deterioration is repainted as evidence of maturity. The community trains itself to applaud decline and treat any suggestion of improvement as naïve, dangerous, or heretical.
This is how a community convinces itself that decay is sophistication. It builds a worldview in which failure is recast as restraint, and stagnation as insight. A culture afraid of growth elevates its fear into doctrine. A protocol that cannot scale becomes a monument to the perceived nobility of staying small. And sincerity, the belief that a digital cash system should process transactions rather than restrict them, becomes a mark of the uninitiated.
The psychology of regression is therefore not an accidental by-product; it is the sustaining force behind BTC Core’s entire ideological posture. Fear became caution. Caution became dogma. Dogma became identity. And identity became the barricade behind which stagnation is defended at all costs.
11. The Miner Reality – What the Propagation Paper Actually Shows
Strip away the sermons and look at the graph. That is what the propagation paper does, and that is why every hymn to “full-node sovereignty” collapses the moment its findings are taken seriously. The study of the BTC network’s topology does not bother with romantic slogans or nostalgic blog posts. It measures nodes, edges, centrality, and paths. It asks a simple question: who actually matters when a transaction becomes a block? The answer is unambiguous. Miners do. Full nodes do not. (arXiv)
The paper, The Redundancy of Full Nodes in Bitcoin: A Network-Theoretic Demonstration of Miner-Centric Propagation Topologies, examines BTC and BSV using complex network theory. It models the network as a graph, computes eigenvalue centrality and related metrics, and simulates transaction and block propagation under realistic conditions. The result is not a matter of opinion. The propagation graph is dominated by a densely connected miner clique. Home-hosted full nodes sit on the periphery, structurally excluded from all transaction-to-block inclusion paths. They are, to put it bluntly, irrelevant to the process they are told they control. (arXiv)
This alone detonates the myth of “full-node sovereignty.” Sovereignty would require that these nodes occupy central positions in the graph, that their presence or absence materially affect how transactions spread and blocks are accepted. Instead, the analysis shows they are dangling leaves, not structural beams. You can prune them away and the propagation spine—built out of miner infrastructure and a handful of high-degree intermediaries—does not notice. The rhetoric casts them as judges; the mathematics exposes them as spectators.
The contradiction between rhetoric and reality is total. BTC Core’s ideological machinery justifies tiny blocks and microscopic throughput on the grounds that “anyone” must be able to run a full node, and that these full nodes are the ultimate arbiters of consensus. Yet the propagation topology demonstrates that home-based full nodes are neither critical nor operationally relevant to consensus propagation. (arXiv) The system’s real power structure resides in miner networks and their tightly coupled peers, not in the army of hobbyist devices kept on ideological life support.
Once that is understood, the small-block crusade stands exposed. It is not preserving a citizen legislature of full nodes; there is no such legislature. It is not empowering the edge of the network; the edge has no influence to empower. What remains is the spectacle of decorative nodes—lanterns hung on the outside of a building whose internal wiring is entirely elsewhere—while the protocol is strangled to preserve the illusion that these lanterns are the source of light.
Network-graph analysis leaves no room for the fairy tale. Miners dominate propagation; full nodes are structurally redundant. A system designed for global digital cash has been throttled to suit hardware that does not matter, in defence of a political myth that does not survive contact with its own topology.
12. The Final Exposure – Non-Scaling as Technological Sabotage
At the end of the analysis, when every excuse has been stripped away and every slogan has been reduced to dust, the shape of the truth is unmistakable: BTC Core’s refusal to scale is not a protective measure. It is sabotage. Not accidental, not incidental, not the cautious prudence of prudent stewards—but the deliberate act of constraining a system that was built for far more than its current custodians will allow.
Limiting block size is the first instrument of this sabotage. The cap is not a safety net; it is a garrotte. It ensures that no matter how much hardware improves, no matter how cheap bandwidth becomes, no matter how much demand exists for digital cash, the network remains throttled. It is the equivalent of fitting a growing child with a steel corset and tightening it with every passing year. The system cannot breathe because it is not allowed to. The cap does not protect the network from danger; it protects the ideology from reality.
Refusing natural growth is the second mechanism. Every technological discipline on the planet assumes that systems grow alongside the hardware they run on. Databases expand. Networks accelerate. Protocols evolve. But BTC Core engineers have chosen an inverse philosophy: the world grows, and the protocol retreats. The world improves, and the protocol contracts. The natural arc of progress bends upward, and the protocol is forced downward by decree. This is not stability. It is self-inflicted attrition.
Preventing computational expansion completes the triad. Bitcoin’s original design allowed miners to invest in performance, increase capacity, and compete on the basis of efficiency. That pathway—organic, market-driven, technologically sensible—has been barricaded. Instead of competition in performance, the network is frozen at the limits of obsolete consumer hardware. The computational arms that should have risen to support global usage are amputated. The miner ecosystem is forced to operate at a fraction of its potential, forbidden from using the scale and efficiency that modern infrastructure already offers.
The consequence is a system defined by self-shrinking impotence. It cannot meet demand because it rejects demand. It cannot scale because it rejects scale. It cannot function as digital cash because its custodians have repurposed it into a symbolic artefact whose value lies not in what it does but in what it refuses to do. The network is not protected—it is neutered. The protocol is not hardened—it is embalmed.
This is technological sabotage in its purest form: the conscious decision to deny a system its natural trajectory of growth, not because growth is unsafe, but because growth threatens the ideology of those who claim guardianship over it. They have turned a dynamic protocol into a static idol, and then declared the resulting fragility a form of perfection. In the end, the only thing BTC Core has truly scaled is its capacity to equate decline with virtue.
13. Closing Section – The Monument to Smallness
There is no polite way to conclude a dissection of deliberate impotence. A digital cash system that refuses to carry transactions is not a system. It is a contradiction wearing the mask of legitimacy. Five transactions per second, defended as “engineering,” is not engineering at all—it is theological nonsense, a creed forged out of insecurity and repeated until the repetition itself becomes proof. Nothing in computing, nothing in economics, nothing in common sense justifies shrinking a global ledger to the scale of a pocket calculator and declaring the outcome enlightened.
Regression has been rebranded as greatness. The guardians of BTC Core have inverted the axis of progress so completely that diminishment is hailed as sophistication, obstruction as wisdom, paralysis as purity. They speak as if the world must contort itself to fit their chosen limits, as if the ambitions of billions should bow before the insecurities of a subculture that fears what scaling would reveal. But the numbers remain indifferent to their narratives. Five TPS is not a philosophy. It is not a design goal. It is not a virtue. It is a measurable admission of failure.
When the arithmetic is laid bare—when doubling curves show what could have been, when topology exposes the irrelevance of full-node theatrics, when data and economic reality unmask the consequences—the ideology collapses. What remains is a monument to smallness. A deliberate retreat from capability. A shrine built to honour the least a digital cash system can do while still pretending to exist.
The tragedy is not technical. The technology was ready, the hardware abundant, the network capable. The tragedy is psychological. Fear masqueraded as philosophy; limitation masqueraded as safety; decline masqueraded as insight. And so the system that could have become a global medium of exchange has been willingly constricted into a fragile curiosity, defended not because it works, but because admitting the need for growth would demand the courage to pursue it.
This is the unavoidable conclusion: BTC Core has not preserved Bitcoin. It has preserved its own fear of what Bitcoin could have become. The monument they have built is not to digital cash, not to engineering, not to progress, but to the quiet and self-congratulatory art of staying small.