Introduction

There is a well-known principle in software design called the law of conservation of complexity. It states that every system has an inherent amount of complexity that cannot be eliminated, only moved around. You can hide it from the user, but then the developer must absorb it. You can simplify the developer experience, but then the user faces it. The complexity has to live somewhere. This principle has serious implications for how we think about Bitcoin scaling.

Complexity Cannot Be Destroyed

When a new Bitcoin layer is proposed, the pitch usually focuses on what it adds: faster transactions, lower fees, new capabilities. What gets less attention is the complexity it introduces. Every layer adds protocol rules, state management, communication overhead, and failure modes that did not exist before.

This complexity does not disappear because the marketing materials do not mention it. It manifests as friction, cost, and delay. Users encounter confusing edge cases. Developers struggle with integration. Operators face operational burdens that grow with the system's complexity. And all of this creates pressure to centralize.

The Path From Complexity to Centralization

The progression is predictable. A new layer is added to Bitcoin with good intentions. The added complexity creates friction that users and operators want to reduce. The most efficient way to reduce friction is to centralize operations: fewer nodes, bigger hubs, managed services. Centralization creates trusted chokepoints where a single entity or small group controls access.

This is not a conspiracy. It is the natural economic response to complexity. When something is hard to run yourself, you pay someone else to run it for you. When enough people make that choice, power concentrates. The layer that was supposed to extend Bitcoin's trustless properties has quietly recreated the trust-based model.

When the Exits Close

The centralization problem becomes critical during periods of high on-chain demand. If blocks are full and fees are elevated, users on layers cannot affordably exit to the base chain. Their ability to enforce their rights in a transaction disappears. The hub or service provider they depend on becomes their de facto custodian.

At that point, the user is in a fully trusted situation. They cannot move their bitcoin without the cooperation of the entity controlling their layer. This is functionally identical to having funds in a bank, except without the regulatory protections that banks provide.

Soft Forks and Protocol Changes Are Not Immune

This complexity trap is not limited to external layers. Soft forks and protocol-level additions follow the same pattern. Every new feature added to Bitcoin's base layer increases the protocol's complexity, which increases the barriers to running a full node, which increases centralization pressure. The conservation of complexity applies regardless of where the complexity is introduced.

Conclusion

Complexity is the silent cost of every Bitcoin scaling proposal. It cannot be eliminated, only redistributed. And its natural destination is centralization, which ultimately recreates the trust dependencies that Bitcoin was designed to remove. Recognizing this pattern is essential for evaluating any scaling approach honestly.