Menu

The Inevitable.

Everything is being written on-chain. Almost nothing can read it at the moment it matters.

In one July week in 2026: Robinhood's tokenized equities passed 200,000 holders. The DTCC ran production trades of tokenized Russell 1000 stocks. Ondo put BlackRock's S&P 500 ETF on-chain. A few weeks earlier, Spain's World Cup win burned 1.16 million fan tokens in the biggest redemption event of the year.

Every one of those assets travels on rails built in the last five years. The writing side of blockchain is finished, funded, and institutional.

Now walk any of those holders up to the moment the asset should matter. The shareholder at a register. The fan at a bar in the stadium district. The member at a door. Nothing there can read what they hold. The token exists, the holder exists, and the two facts never meet.

That gap is not a missing feature. It is a missing layer.

The pattern repeats for software

The same week those assets moved, AI agents started paying for things. x402 settles the payment. MPP settles the payment. Neither verifies the caller. Whether an agent is registered, whether a principal actually delegated authority to it, whether that delegation is still valid, whether the wallet behind it has any history at all: those facts are written on-chain too, in ERC-8004 registries and ERC-7710 delegations. And at the moment of the call, the payment rail does not look.

Humans at a register, agents at an API. One gap, two costumes.

What the missing layer has to be

Blockchains made writing permanent. We make reading them verifiable. For reading to work at the moment of need, it has to be four things at once:

Private. The register learns yes or no, never the balance. Boolean, not balance.

Verifiable. A signed answer that anyone can check against a published key, offline, without asking us twice. The signature proves we issued it. The blockchain proves we were correct.

Universal. One call across 38 chains, because holders do not arrange themselves by network.

Open to software. An agent with five cents of USDC and no account gets the same signed answer as an enterprise with a key.

That is condition-based access: send a wallet and a condition, get a signed boolean. No secrets. No identity-first. No static credentials.

Why we keep writing these

Each post in this series marks the same event in a different costume: an asset went on-chain at scale, and the place it should have mattered could not read it. We are not predicting this future. We are counting it.

The tokens exist. The holders exist. The agents are already calling. What the register, the API, and the door need is one thing: a signed yes or no.

Read wallet state. Evaluate conditions. Return a signed boolean.

See the primitive underneath

Free API key. 38 chains. First attestation in under 5 minutes.

How It Works Quickstart