/ 04 /Transcending the Original Vision

The 2017 Green Paper described a hosting marketplace — a place where people who provided hosting and compute (either with their own hardware, or with HoloPorts purchased in our crowdfunding campaign), would earn HoloFuel. Publishers, those who needed hosting and/or compute, would spend HoloFuel. HoloFuel would be stable, asset-backed, useful — a utility currency for a specific economic context.

That vision was sound. The opportunity was real, and the architectural approach was right. It also barely scraped the surface of what was both possible — and now more necessary than ever. The 2017 paper half-saw this itself, noting that if HoloFuel were ever used as a more general-purpose currency, hosting would become a smaller part of the economy, making room for asset-backed currencies for energy, food, and transport. What was an aside then is the argument now.

The accounting infrastructure built to make distributed hosting work — mutual credit, countersigned transactions, proof-of-service validation, smart agreements — is not specific to hosting. It’s general-purpose economic coordination infrastructure. What else can you do with an accounting engine that can run on any device, denominate any unit of value, settle without a trusted intermediary, and costs a fraction of a cent per transaction?

The answer is: most of the things the current financial infrastructure does badly or doesn’t do at all.

Consider what launching a project-specific token actually requires in 2026: legal analysis in every jurisdiction. Exchange negotiations. Liquidity provision and ongoing market-making. Tokenomics management. Governance of the token itself, separate from governance of whatever you were actually trying to build. A community of speculators whose investment thesis may actively conflict with the community of people using the service. And the background noise of people measuring your project’s health through token price, regardless of whether token price reflects anything real. That cumulative overhead has effectively crushed new economy currency products and projects worldwide.

This overhead isn’t incidental. The trading pair model enforces token issuance as the price of participation. This model selected for tokenising everything, whether or not it served the project.

Mutual credit currency offers a different path. Rather than each project issuing its own token and carrying the overhead that comes with it, projects can denominate their activity in a shared currency whose supply tracks real economic activity rather than speculative demand. HoloFuel — the mutual credit currency we described in the original Green Paper — is the working instance of that model. A project building on Holochain can adopt HoloFuel as its native currency — pricing its services and letting its community transact in it — without issuing a token of its own. The project participates in a token economy without having to set up and run one.

This matters most for the projects the current system has failed most thoroughly — regenerative finance initiatives trying to denominate ecological value without speculating on it; community currency projects wanting local exchange with global interoperability; mutual aid networks needing accounting without extraction; cooperative enterprises that want to share value with participants rather than speculators; and impact organisations where capital should flow toward outcomes rather than toward whoever generates the most trading volume.

Many of these projects have been built without tokens precisely because the token infrastructure was built for speculation — and since they don’t want that erosive force driving their community, ecosystem, or project, they’ve been largely undercapitalised as a result.

And then there’s AI — the use case the 2017 Green Paper design didn’t anticipate, but our architecture is already built to serve.

One breach of a centralised AI stack reaches everything behind it. That is the property this architecture removes. Holochain has no single ledger where every application’s data accumulates — each application runs its own network with its own membrane, and the contents of private entries never leave the agent’s own device. What an application publishes is visible to that network’s peers, which is what makes validation possible. But there is no layer above it where everything aggregates, and no central infrastructure to breach.

Each entity — individual, organisation, or community — can run AI agents on its own Holochain application DNA, with its own validation rules and data boundaries, its own security posture calibrated to what it’s actually protecting. You don’t build Fort Knox for a village post office. You don’t need the same security economy for internal comms AI as you do for financial operations AI. Agent-centric architecture means each function sets its own posture, because there’s no single network imposing a single model on everyone.

The practical stack mapping that we explore in the following section is straightforward. Holochain agents can run local AI models — trained on or tuned to the entity’s own data, communicating with other agents peer-to-peer through the same cryptographic mutual accountability that governs every other Holochain interaction. Our accounting software can handle the microtransaction economics when relevant: agent-to-agent service payments at fractions of a cent, that conventional payment rails can’t cost-effectively process. A clearinghouse layer between sovereign networks can settle cross-network exchanges without requiring any single network to surrender its autonomy. HoloFuel can denominate value. This is the work Holo Ventures — the commercial entity we’ve restructured to deliver it — is now pursuing.

An identity wallet on agent-centric architecture — where the agent holds its own credentials and discloses only what each interaction requires — delivers the portability and selective disclosure the EU’s digital identity wallet promises citizens, without creating the thing that makes the centralised version dangerous: a single issuer positioned to observe every use, breachable in one incident, and compellable to hand over what it holds.

Agent-centric architecture produces data provenance as a natural byproduct of how it works. Every action signed to a source chain, every interaction countersigned, data lineage cryptographically verifiable without retrofitting anything. The regulatory requirements described in Section 2 aren’t problems for this infrastructure. They’re descriptions of what it already does.

This is not a position paper on AI. We have no interest in telling anyone what models to run. What it points to is the infrastructure layer that makes any AI deployment structurally resistant to the things that keep security professionals awake at night. What the regulatory environment is now confirming is that the architecture was right before the regulations existed.