# What happened, and what it means - Open Value Blog

> A new participant is arriving.

Blog · 2026-09-30

## What a neutral record buys

A new participant is arriving. Software agents are beginning to transact with each other at machine tempo, and the largest platforms have begun standardizing how agents pay. Trade at that tempo needs proof at that tempo: events recorded as fast as they happen, checkable by any party without a queue. The machine economy needs what the human one has always lacked: a shared record of what happened, available for any party to read from and write to.
A neutral record replaces none of the institutions. A bank keeps its ledger, a registry keeps its titles, a platform keeps its rules. What changes is what sits between them: one canonical sequence of events that everyone can verify and no one must trust. Interoperability becomes an internet protocol problem rather than a business-agreement problem.

## One thin base

The base layer does two things: it orders economically consequential events and keeps the record available at all times. It executes nothing and interprets nothing. Many semantic layers sit above it, each keeping its own meaning; the base stays thin.
Most networks pay for their own security with a native token, and the token is also how they acquire an owner. Whoever holds it steers the design, and the cost of using the network rides on an asset whose price has little to do with the work being done. A base layer meant to stay neutral has to find another way.
Whether it can operate securely, permissionlessly, and sustainably without a native token is one of the initiative’s core research questions.

Select a layer to read what it does. Everything above the dashed plane keeps its own meaning. Everything below is shared.
Layer

Open Value does not propose a finished stack. The event-state dissociation thesis is the starting point; how many layers there are, and how they are organized, remain open questions.

Two key questions:

- How can the base layer operate neutrally (no censorship) and safely (high security and data availability guarantees) at internet scale without a token?
- What must be true for different and untrusted semantic layers to natively exchange value on the Internet using the base layer as a trusted and neutral value coordinator?

## Seven terms

Seven terms central to Open Value’s thesis:

### 01 · Value · the record of what happened
An account balance, a deed, a ticket: each exists as a record of who holds what, and moves when that record changes. Those records live inside separate heterogeneous systems, each with its own rules, verifiable only from within. Open Value’s subject is the record of what happened across all of them, verifiable at internet level.

### 02 · Event · what goes into the record
Every system produces a sequence of events: a payment sent, a deed signed over, a ticket scanned, a measurement taken. An event is the fact that something happened. Systems send their events to a shared record.

### 03 · State · what the events add up to
The state of a system is interpreted from its events: the balance after the payment, the name on the deed, the tickets still unsold. State is always derived. Get the events and their order right, and any system can interpret its own state.

### 04 · Event-state dissociation · record the facts, not the meaning
The moment a layer decides what an event means, anyone who accepts its record has to accept its rules as well, and the record stops travelling between systems. That is why the two are held apart: keep meaning out, and a single record can serve many interpretations. How event inclusion and ordering work operationally is open research.

### 05 · Base layer · shared foundation
The shared foundation of the stack. Every participating system can read from and write to it, but no participant controls it. It records and orders events; it never interprets, executes, or validates. It is content-blind by design.

### 06 · Semantic layer · where meaning lives
Any system above the base: a bank, a registry, a platform, or app. Each reads the shared record and derives its state from its own events. The base records what happened, while what it means belongs to the semantic layer. Whether the architecture settles into two layers is open research; the division of jobs does not depend on it.

### 07 · Sovereignty · each domain keeps its own meaning
Because the base layer records and orders events without interpreting them, every semantic layer keeps control of its own execution, rules, economics, and governance.