Shinzo Testnet Is Live. We Built the First Trustless Read Layer Blockchains Were Supposed to Have.

We've spent a lot of posts here making one argument. Blockchains are trustless to write and trust-dependent to read. The chain cryptographically verifies every state transition, then your app reads that state from Alchemy, Infura, or The Graph and takes their word for it. And the money only moves one way. $2.12 billion was paid for blockchain data in 2025, and none of it reached the validators or ecosystems that generated the data.

We're a product-led team, so we'll let the work speak first. The Shinzo testnet is live, generating verifiable Ethereum data. Here's what we built and how it works.

What Shinzo Is

Shinzo is a trustless read layer that lives where the data is born.

Every other data provider is a stack. An RPC node serves raw blockchain data, and a separate indexer reads from that RPC and structures it. Two layers, two operators, two places you have to trust. Shinzo collapses both into one service that runs at the source. The validator's own infrastructure generates structured, verifiable data directly, with no RPC hop and no downstream indexer rebuilding what the chain already knows.

The data carries cryptographic proof of where it came from. Any node can serve it, and any client can verify it. The middlemen charging rent on data they never produced are a thing of the past.

The Roles: Generators, Hosts, and Builders

Shinzo has its own vocabulary, and it's worth getting straight up front, because the roles are what separate the network from an indexer.

A Generator is a validator of a chain running the Shinzo client. As it validates, it generates verifiable data from the chain it's already securing. There's no separate operator and no RPC in between. The validator that generates the data is the one that serves it.

A Host is an entity that stores that data and runs View transformations on it. Hosts pull raw data from Generators, shape it into the Views applications query, and serve those Views. A Host doesn't run a node or generate the data. It makes the data useful.

A Builder is anyone consuming Shinzo data to power a project, and they have two ways to get it. Most Builders query Hosts for the Views their project needs. For the specialized cases, private Views or the very latest data straight from the source, a Builder can run a Direct client and pull from Generators directly.

How It Works: From Block to App

A block finalizes on the chain. A Generator validating that block reads it and writes structured data (blocks, transactions, logs, access lists) as it goes, then signs a BlockSignature: a Merkle root, the full list of content identifiers, and a secp256k1 signature. That signature is the proof of delivery everything downstream builds on.

Hosts receive that data from Generators over a peer-to-peer network, with no request and no RPC in between. Each Host runs its View transformations and serves the results over GraphQL, with access enforced per View so it can keep data open or gate it by identity. The data stays content-addressed the whole way, so its identifier is a hash of its contents and any tampering breaks the link. The database moving and verifying it is DefraDB, and the engine running the transformations is LensVM, both open source and built for exactly this.

When a query arrives, the network gateway sends it to several Hosts serving that View, compares what comes back, and returns a result tagged with how much they agreed. You're not trusting one Host to be honest. You're watching independent Hosts converge on the same answer.

ShinzoHub ties it together. Views get registered there, Generators and Hosts prove their identity, and query revenue settles each epoch. It's the accounting backbone, kept off the data path so the data stays fast.

A New Page for Ecosystems

We've made the revenue case at length in recent posts, so we won't rerun the numbers here. What matters is what's now possible.

For the first time, an ecosystem can cut the trusted indexers and RPC providers out of its data layer. Not route around them, not negotiate better terms with them, but stop depending on them. The validators already securing the chain become the ones generating its data, and the value that used to leak out to middlemen stays inside the ecosystem.

That's a healthier ecosystem from the validators up. Validators earn from the data they were already producing for free, which means less pressure to sell the token just to cover the cost of validating. A validator with revenue is one that can hold. Hosts turn that data into something builders can use and earn for serving it. Builders get verifiable data without a gatekeeper deciding their rate limit. This is new value flowing in, not old value reshuffled.

The trusted read layer was a compromise the last generation of infrastructure forced on everyone. It doesn't have to be the deal anymore.

What's Live, What's Next

The Shinzo testnet is live today, generating verifiable Ethereum data. The full stack is open source under MIT at github.com/shinzonetwork.

We're starting with Ethereum, not stopping there. From here we expand EVM-first, then to every chain worth serving, publish the whitepaper, and work with the community toward mainnet. Want your chain next? Vote for it at shinzo.network/chains, and if you're up for it, contribute to our Gen Client integrations to get it live faster. The architecture doesn't privilege any one chain. It privileges provenance. Data produced by a chain settles value back to that chain, wherever the chain sits in a stack and wherever the data is ultimately consumed.

Who This Is For

If you validate a chain, you're already doing the expensive part. Become a Generator and let the trustless read layer finally pay you for it.

If you want to run a Host, you store and serve verified data and earn from queries without running a node or generating the data yourself.

If you're building an app, you get verifiable GraphQL with no API keys, no rate limits, and no monthly invoice that scales with your own success. Query Hosts for the Views you need, or run a Direct client to Generators when you want private Views or the freshest data.

And if you steward an ecosystem, Shinzo returns its verifiable read-layer revenue without a single change to how validators are rewarded.

The technology to build a trustless read layer already existed. We stopped writing about it as a someday and shipped a testnet. Come build.

Join the community building the trustless read layer blockchains deserve.
Docs · GitHub · X · Telegram · Discord