Loading...
Loading...
How the Internet Solved the Value Transfer Problem
Unlike deep dives that examine successful regenerative organisations, diagnoses analyse sectors where architectural constraints shape participant behaviour. The advertising-funded internet is not a failure—it is a rational response to a real infrastructure gap.
When the internet was designed, it could transfer data but not value. This was not an oversight—the architects were solving a different problem. But this architectural absence created a constraint that shaped everything that followed. How do you build services when you cannot charge for them?
Advertising emerged as compensatory architecture: a solution to a real and binding problem. The current internet economy is not a market failure or a moral failure. It is the rational response to an infrastructure gap. Understanding this matters because different diagnoses suggest different interventions.
“Advertising was dominant because the system could not clear value directly. This is a constrained equilibrium, not a moral failing.”
Core thesis of this diagnosis
HTTP could transfer data but not value. This absence at the protocol level created a path dependency that shaped business models across the entire economy.
The internet could move information anywhere in the world for near-zero cost. But it had no protocol for moving value. Every payment required external infrastructure: banks, credit cards, payment processors.
Payment processors have minimum fees (typically $0.30 + percentage). This makes micropayments uneconomic. You cannot charge $0.01 to read an article when the transaction cost exceeds the price.
Advertising solved the problem. Third parties (advertisers) pay for user access. This is not extraction but exchange: users receive services; advertisers receive attention. The architecture was rational given the constraint.
The advertising model became locked in through network effects and path dependence. But lock-in is not inevitability. The constraint could theoretically be addressed at the infrastructure level.
This diagnosis is structural, not moral. Platforms that adopted advertising were solving a real problem. The advertising model enabled services that billions of people use daily for communication, information, and connection. This has genuine value.
The question this diagnosis addresses is not “who is to blame?” but rather: what architectural conditions would enable different equilibria? If the constraint is infrastructural, the solution may also be infrastructural.
Claims about “attention extraction” or “user harm” are contested and beyond the scope of this structural analysis. We focus on architecture, not outcomes.
Given the architectural constraint, internet services have a limited set of viable business models. Each has trade-offs.
Third parties pay for user access. Services are free at point of use.
Users pay recurring fees. Aligns platform with user value.
Basic service free; premium features paid. Hybrid model.
Pay per use. Would enable granular exchange. Currently not viable due to transaction costs.
Applying IRSA’s Regenerative Capital Architecture framework to understand the structural dynamics.
In regenerative systems, Delta decouples value creation from extraction. In advertising-funded services, user value and platform revenue are mediated by advertisers. This creates structural coupling, not decoupling.
In regenerative systems, Lambda aligns participant incentives with system health. In three-party markets (user-platform-advertiser), alignment is indirect and can diverge.
The internet lacks foundational infrastructure that would enable alternative equilibria.
No protocol-level way to transfer value in small amounts. Every transaction requires external payment infrastructure.
Implication: Micropayments uneconomic; subscription or advertising are the only viable models at scale.
No user-controlled identity layer. Users must create accounts with each platform, managed by that platform.
Implication: Reputation and social connections are not portable; creates switching costs.
No standards for how content is ranked or recommended. Ranking algorithms are proprietary.
Implication: Users cannot evaluate or choose ranking approaches; platform controls information diet.
Limited ability to move data between platforms. Export exists but import is typically blocked.
Implication: Investment in one platform cannot be transferred; increases lock-in over time.
Early internet had interoperable protocols (email, RSS). Modern platforms are largely closed systems.
Implication: Network effects concentrate in platforms rather than protocols; winner-take-most dynamics.
If the constraint is infrastructural, the solution may also be infrastructural. These are potential architectural interventions—not recommendations, but possibilities.
Protocol-level ability to transfer value in any amount, with near-zero transaction costs. This would enable micropayments as a viable business model.
Would enable: Direct exchange between users and service providers
User-controlled identity that works across platforms. Users own their credentials and can authorise platforms to verify them.
Would enable: Reduced lock-in; reputation portability
Social connections as user-controlled data that can be accessed by any authorised platform. Follow relationships work across services.
Would enable: Competition on service quality rather than lock-in
Users select or design their own ranking algorithms. Platforms provide data; users choose how to sort it.
Would enable: User control over information presentation
“The internet should be understood not as a failed public sphere, but as a pre-constitutional meaning system operating under architectural constraints.”
This diagnosis contributes to regenerative systems theory by demonstrating:
Full paper: structural failure of digital markets
Another case of architectural absence
Example of alternative architecture in finance
Alternative capital architecture theory
Explore regenerative organisations globally
If you’re working on protocols, identity systems, or value transfer infrastructure that addresses these architectural constraints, we’d be interested to connect.
Get in Touch