HTTP did not specify what websites should contain. It specified how information should be requested, transmitted, and received. Every website — news, commerce, science, government, social media — runs on the same base protocol. HTTP does not care about the content. It cares about the structure of exchange.
\(\infty_0\) is the HTTP of exchange. It does not specify what tokens represent, what consensus mechanism governs them, what incentive structure rewards participation, or what governance model controls issuance. It specifies how any transfer is structured as a causal node, how exchange is recorded permanently on the bilateral ledger, how verification is achieved without a central authority, and how security is guaranteed by \(\tau\) irreversibility rather than computational hardness.
Everything is already a label on \(\infty_0\). The protocol makes that label transferable, verifiable, and permanent. Any thing — currency, property, identity, vote, reputation, carbon credit, intellectual property, physical object, biological sample, moment of time — can be tokenised as a label on \(\infty_0\) and exchanged through the protocol. Exchange means any transfer of anything between any parties — not just financial value. Contracts, provenance records, identity credentials, agreements, data, rights — all exchange.
The \(\infty_0\) protocol provides four primitives. Everything built on top — whether a currency, a contract system, a provenance registry, an identity layer, or anything else — uses some combination of these four. None are specific to any particular token type, purpose, or governance model.
The \(\infty_0\) protocol deliberately leaves the following to individual token systems. This is what makes it a protocol rather than a currency.
| Parameter | Protocol position | Examples of what can be built |
|---|---|---|
| Token semantics | Any | Currency, property deed, vote, identity, carbon credit, time, reputation, physical object, biological sample, intellectual property |
| Consensus mechanism | Any expressible as validator proportion | Koide 2/3, simple majority, unanimous, proof of stake, delegated, quadratic voting |
| Issuance model | Any | Fixed supply, algorithmic, commons-governed, demand-driven, time-locked, event-triggered |
| Governance structure | Any | Commons, DAO, corporation, government, cooperative, individual, smart contract |
| Incentive design | Any | UBI, proof of work, proof of contribution, staking, burning, demurrage, subsidy |
| Privacy level | Any tier from fully public to fully private | Public ledger, selective disclosure, zero-knowledge, fully private with audit key |
| Transfer rules | Any | Free transfer, restricted, time-locked, conditional, non-transferable, expiring |
| Accumulation rules | Any | Uncapped, ceiling, demurrage, progressive, pooled |
Because \(\infty_0\) is a protocol not a currency, the token can represent any asset for which a unique causal identity, permanent provenance, and verified transfer are valuable. This is a much broader class than financial assets.
A house, a car, a piece of land, a machine — any physical object can be tokenised as a label on \(\infty_0\). The token's causal provenance is the object's ownership history. Transfer of the token is transfer of ownership. The bilateral ledger is the land registry, the title deed, the vehicle logbook — permanent, unforgeable, universally readable.
A birth certificate, a qualification, a professional licence, a security clearance — any credential can be a token on \(\infty_0\). The token's causal ancestry is the credential's issuance history. The zero-knowledge proof layer allows the credential to be verified without revealing its contents. You prove you have a medical licence without revealing your patient records.
A vote, a patent, a copyright, a carbon credit, a fishing quota, a spectrum licence — any right can be tokenised. The token encodes the right's scope, duration, and transferability. The bilateral ledger records every exercise and transfer of the right permanently. Rights cannot be exercised twice — the causal ledger makes double-use physically impossible.
A specific \(\tau\) position can itself be a token — a moment of time with a unique identity, transferable, tradeable, permanently recorded. Time-based contracts, time-locked agreements, scheduled transfers, expiring rights — all expressible as \(\tau\)-anchored tokens on the \(\infty_0\) protocol.
A genetic sequence, a cell line, a physical sample — any unique biological or physical object can be tokenised. The token's causal provenance is the sample's chain of custody. Consent, attribution, and benefit-sharing for biological resources become enforceable through the token's governance layer.
The most powerful deployment pattern for \(\infty_0\) tokens is piggybacking on constitution certificates — attaching token payloads to the compliance certificates that bilateral mesh deployments already carry. Every registered deployment already has a certificate on the bilateral chain. Attaching a token to that certificate costs nothing additional in infrastructure — the certificate node already exists, the chain already records it, the validators already confirm it.
Piggybacking enables broad token distribution without a separate distribution infrastructure. Every entity that registers with the commons — every researcher, every commercial deployer, every institution that files a ringfence — automatically has a certificate and therefore automatically has the infrastructure to carry tokens. The distribution network is the compliance network. Universal basic \(\infty_0\) allocation becomes a natural extension of universal commons membership.
The token payload on a certificate can carry: economic value (currency), governance rights (voting weight), access rights (ringfence permissions), identity credentials (commons membership tier), and any other right or value the commons chooses to attach. The certificate is the bilateral object. Its egress face is the compliance record. Its ingress face is the rights and value payload. Both faces are permanent. Both are on the same causal node.
The \(\infty_0\) protocol is designed to be substrate-independent and purpose-independent. The bilateral chain is the reference implementation — the native substrate, the most secure, the most aligned with the protocol's principles. But \(\infty_0\) tokens can be issued and transferred on any substrate that implements the four protocol primitives: unique \(\tau\)-anchored identity, permanent causal provenance, consensus-validated transfer, and \(\tau\)-irreversibility security.
A scientific community uses it to record experimental data with permanent provenance. A government issues identity credentials on it. A cooperative manages shared resources through it. A hospital tracks patient consent. A community that prefers Ethereum can implement the \(\infty_0\) primitives as Ethereum smart contracts — accepting a reduction in security (Ethereum's computational hardness rather than \(\tau\) irreversibility) in exchange for access to the existing Ethereum ecosystem. A government that wants a permissioned ledger can implement \(\infty_0\) on a private chain with its own validators. A cooperative that wants a simple shared database can implement a lightweight \(\infty_0\) compatible record. The purpose does not constrain the protocol. The protocol bridges all implementations — tokens issued on one substrate are recognisable and verifiable by any other \(\infty_0\)-compatible system.
This is the HTTP analogy made precise. HTTP runs over TCP/IP, but also over other transport layers. \(\infty_0\) runs on the bilateral chain, but also on other ledger technologies. The protocol is the standard. The substrate is the choice of the implementing community.
All existing digital exchange systems — currencies, contract platforms, provenance registries, identity systems — are secured by computational hardness. A bilateral mesh quantum computer — operating from \(0\) rather than toward \(0\) — dissolves these assumptions. When that capability exists, every token on every existing system is potentially forgeable, double-spendable, and repudiable.
\(\infty_0\) tokens on the bilateral chain are not. Their security derives from \(\tau\) irreversibility — the becoming-time axiom. The token exists at a specific \(\tau\) position. That position cannot be forged because \(\tau\) never repeats. The transfer history is permanent because \(\tau\) never decreases. A bilateral mesh quantum computer cannot make time run backwards. The security is prior to computation — it will hold against any computing system, quantum or otherwise, for as long as time remains irreversible.
Tokens on non-bilateral substrates — Ethereum, Bitcoin, permissioned chains — inherit that substrate's security. The \(\infty_0\) protocol does not guarantee the security of non-bilateral implementations. It provides a migration path: as the bilateral chain becomes available, tokens can be migrated from computationally-secured substrates to \(\tau\)-secured ones. The protocol is forward-compatible with its own most secure implementation.
On the status of this paper. The \(\infty_0\) protocol is a design proposal for a base-layer value exchange protocol extending from the Bilateral Constitution's certificate and causal ledger architecture. The four protocol primitives — unique \(\tau\)-anchored identity, permanent causal provenance, consensus-validated transfer, and \(\tau\)-irreversibility security — follow directly from the bilateral chain architecture established in the constitution. The claim that \(\infty_0\) can tokenise any asset for which unique causal identity and permanent provenance are valuable is a general claim about the scope of the protocol, not a specific technical claim requiring verification. The \(\tau\)-irreversibility security guarantee is the genuinely novel element — it is the only existing proposal for a digital asset security mechanism that is prior to computational hardness and therefore resistant to a bilateral mesh quantum computer. Implementation is future work. The architecture is here. Framework: A Philosophy of Time, Space and Gravity — Dunstan Low.