Shinzō Network: Blockchain Data You Can Prove

Introduction:

A blockchain is built to eliminate the need for trust. Every transaction is verified, every state change is cryptographically secured, and anyone can independently inspect what happened. Yet the moment an application needs to read that data, the rules quietly change.

Most applications rely on third-party providers like Alchemy, Infura, or The Graph to access and interpret blockchain data. These services make the information usable, but they also introduce a layer of trust that the blockchain itself was designed to remove. The chain proves what happened, but applications still have to trust someone else to tell them. And while these providers have built valuable businesses around blockchain data, the validators and ecosystems responsible for producing it see little of the revenue generated from it.

Shinzō was built to change this.

Rather than adding another layer between applications and the blockchain, Shinzō brings data access closer to where the data originates. By enabling validators to serve structured, cryptographically verifiable data directly from their own infrastructure, Shinzō aims to make reading blockchain state as trustless as writing to it.

Understanding Shinzō:

Blockchains already have a way to establish truth. The challenge is making that truth accessible without having to trust someone else to deliver it.

Today, blockchain data typically passes through two separate services before applications can use it. RPC providers retrieve the raw data, while indexers organise it into a usable format. Shinzō brings both steps back to the source, enabling validators to serve structured data directly from their own infrastructure, with cryptographic proof of its origin.

Instead of asking applications to trust the service delivering the data, Shinzō gives them a way to verify it themselves. The result is a more open, permissionless foundation for accessing blockchain information across networks, giving developers and AI agents the ability to build on data they can independently verify.

An Exploration of Shinzō’s Key Features:

Data Generated at the Source: Shinzō brings blockchain data generation directly to the infrastructure securing the network.

• Validators generate structured, verifiable data from the blockchain they already validate.

• Shinzō combines data retrieval and structuring at the source, removing the separate RPC and indexing steps used by conventional providers.

• This creates a more direct connection between blockchain networks and the applications using their data.

Cryptographically Verifiable Data: Shinzō gives applications a way to verify the data they receive.

• Cryptographic signatures and content identifiers provide evidence of data origin and integrity.

• Multiple independent Hosts can serve the same data, allowing query responses to be compared.

• Applications can assess agreement between providers instead of relying entirely on a single source.

Flexible Access for Developers: Shinzō gives builders multiple ways to access blockchain data.

• Developers can query Hosts for structured data tailored to their applications.

• Direct connections to Generators support specialised use cases and access to the latest data from the source.

• This separates data access from the infrastructure required to operate a blockchain node.

Designed for a Multichain Ecosystem: Shinzō's architecture is built to support data from multiple blockchain networks.

• Shinzō’s testnet is currently live, reading data from Ethereum mainnet. Support for additional networks will be prioritised based on data demand, with communities able to signal interest in future integrations through the Shinzō network support page.

• Its source-level approach can be integrated with different networks without relying on a single centralized data provider.

• This creates a foundation for applications to access verifiable information across ecosystems.

What Makes Shinzō Unique

Shinzō challenges a fundamental assumption in blockchain infrastructure: that accessing onchain data must depend on a separate layer of trusted providers. In the conventional model, RPC nodes retrieve raw data while indexers process it into something applications can use. Shinzō brings structured data generation to the source, where the blockchain is already being validated. This shortens the path between consensus and consumption, while removing the need to rebuild the same information through a separate indexing pipeline.

The distinction goes beyond where the data is produced. Shinzō separates the ability to generate data from the ability to transform and serve it. Generators operate alongside blockchain infrastructure, while Hosts specialise in storing data, executing Views, and delivering results to applications. This separation allows the network to expand its serving capacity without requiring every participant to operate a validator, making the architecture more flexible as demand grows.

Verifiability is central to the design. Cryptographically signed data establishes evidence of origin, content addressing helps protect integrity, and comparisons across independent Hosts give applications another way to assess the reliability of query results. Rather than making trust in a particular provider the starting point, Shinzō makes verification part of the data access process itself.

Technical Architecture

Shinzō has two layers that work together. The data layer handles the collection, verification, and delivery of blockchain data. The coordination layer, built around ShinzōHub, manages the participants, data Views, access, and payments. The data itself moves directly between network participants, rather than passing through ShinzōHub.

The Data Layer:

Generators: Reading the Chain at Its Source

A Generator runs alongside a blockchain node and reads new blocks as they arrive. It collects the block data, transactions, receipts, and logs, then organises them into structured records.

Before sending the data out, the Generator signs it with a cryptographic signature. This gives other participants a way to verify where the data came from and check that it has not been altered. The signed data is then published over Shinzō’s peer-to-peer network, where Hosts can receive it directly.

The important difference is where this work happens. Traditional infrastructure retrieves raw blockchain data through an RPC provider and then sends it to an indexer for processing. Shinzō combines these steps at the source, using the infrastructure that already has access to the chain’s data.

Hosts: Making Blockchain Data Usable

Applications rarely need raw blocks in their entirety. A DeFi application might need token transfers, while an analytics platform could be interested in contract activity across an entire network. Hosts turn the data produced by Generators into the specific information these applications need.

They receive data from Generators, verify its cryptographic attestations, and transform it into structured datasets called Views. These Views are then made available to applications through GraphQL.

Hosts use DefraDB to store and replicate data across the network, while Lens handles more complex transformations, such as decoding smart contract events. The same transformation produces consistent results from the same input, allowing different Hosts to independently generate and compare their outputs.

Generators and Hosts have separate responsibilities. Generators focus on producing verifiable data, while Hosts handle the work of preparing and serving it. Hosts can therefore scale to meet demand without having to operate their own blockchain nodes.

How Shinzō Verifies Data

Shinzō's verification process begins when a Generator signs a batch of data. The signature includes a Merkle root and content identifiers, providing a cryptographic record that Hosts can check when they receive the data. Content identifiers are derived from the data itself, so changing the contents also changes their identifiers.

Verification continues when applications request information. Shinzō's gateway can query multiple Hosts serving the same View, compare their responses, and indicate how closely they agree.

These checks serve different purposes. Cryptographic proofs help establish the origin and integrity of the source data, while comparing responses from independent Hosts helps identify disagreements in the results. Applications get more information about the reliability of what they receive, instead of having to rely on one provider alone.

ShinzōHub: Coordinating the Network

The data moves between Generators and Hosts, but the network needs a way to organise its participants. That's the role of ShinzōHub, a dedicated blockchain that coordinates registrations, Views, access, and the network's economic activity.

When a developer registers a View, ShinzōHub records it so Hosts can discover and serve it. Generators and Hosts also register their identities with the network. ShinzōHub coordinates access and query-revenue settlement, but it doesn't store or serve the blockchain data itself. Keeping these responsibilities separate means the data doesn't need to pass through the coordination layer every time an application makes a query.

Connecting Other Blockchains

Shinzō is designed to support data from different blockchain networks, each with its own way of identifying validators and handling payments. Outposts and relayers connect these external chains to ShinzōHub.

An Outpost is designed to run on an external chain, where it can use that chain's own mechanisms to verify validator identity and handle payments. A relayer monitors events on the external chain and passes the relevant information to ShinzōHub, which processes it within the Shinzō network.

This lets ShinzōHub coordinate participants from different ecosystems without having to monitor each chain directly. The details of verification can vary by network, while the information passed to ShinzōHub follows a consistent process.

The full contract-based Outpost flow is still planned and is not deployed on the current testnet. For now, validator assertions use an administrator-approved process.

All in all, a Generator reads new blockchain data, signs it, and publishes it to the network. Hosts receive and verify the data, organise it into Views, and make those Views available to applications. When an application queries the data, responses from multiple Hosts can be compared to give it a clearer picture of their agreement.

ShinzōHub handles the coordination behind the scenes, including participant registration, View discovery, and the network's access and payment systems. It keeps the network organised without sitting in the path of every data request.

Each component has a distinct job, but they work towards the same goal. Blockchain data can move from its source to the applications that need it, with cryptographic verification built into the process and without depending on a single provider to retrieve, structure, and serve it.

News Recap: Recent Breakthroughs and Updates

The tailwinds are building for Shinzō

• Shinzō Testnet Is Live

Launched on 9 July, Shinzō’s testnet brings its vision for a trustless read layer into a live environment, making blockchain data verifiable from the source.

• Frontend Updates Across Studio, Registration and Explorer

Recent improvements streamline registration, expand Ethereum Explorer features, add tokenomics support, and improve platform reliability.

• Shinzō v0.7.0 Is Live

The latest release introduces chain abstraction for Generators, alongside improvements to attestations, indexing safety, and network stability.

• The Operator Network Is Growing

Stakin by The Tie, Simply Staking, Validatrium, Sensei Node, Stakely, Ethernodes and more have joined as Generator operators. StakeCraft and 0xHub join as Host operators, while RockLogic has also joined the testnet.

Conclusion

Blockchain data is a critical part of the infrastructure powering applications, financial systems, and AI agents, yet access to that data still depends heavily on third-party providers. Shinzō is working towards a different model, where data can be generated at its source, verified independently, and served by a network of operators. With its testnet live and development progressing across the protocol and operator ecosystem, Shinzō is laying the groundwork for a more open and verifiable way to access blockchain data.