Shinzo

The trustless read layer for blockchains

[Shinzo @shinzonetwork]

https://t.co/2xFyfFMLaR

[Shinzo @shinzonetwork]

🐳 Shinzō v0.7.2 is live!

We’ve released v0.7.2 for both Generator and Host clients, bringing major improvements across multi-chain support, reliability, observability, and security.

→ Multi-chain support for Hosts.
→ Improved blockchain reorganization handling for consistent indexing.
→ Optional OpenTelemetry metrics and Grafana dashboards for both clients, disabled by default.
→ More reliable pruning, Generator peer connectivity, and transaction processing.
→ RPC chain ID validation and automatic redaction of API credentials from logs.

⚠️ Action required for Host operators

We’ve deployed our Generators on new infrastructure and all Hosts connected to Shinzō’s existing Generators must update their connections.

The new deployment uses domain-based endpoints (dns4) instead of IP-based connections, along with a new chain-based configuration format.

What you need to do:

Upgrade to Host client v0.7.2-ethereum-mainnet.

Update your config.yaml using the new Generator endpoints. The changelog includes instructions for both default and customized configurations.

Recreate your Host container to apply the new image and configuration.

⏰ Deadline is Tuesday, November 17, 2026

The existing Generator endpoints will be decommissioned on Tuesday, November 17, 2026. Please complete the migration before then to avoid interruptions to data replication.

🐳 Generator client
docker pull https://t.co/nDCOOe9sVu

🐳 Host client
docker pull https://t.co/r6t7QzFkhe

👇 Full changelog and updated Generator connection details

https://t.co/ZLw0knM95Z

If you need help migrating your Host, reach out in the hosts channel in our Discord and our technical team will assist.

[Shinzo @shinzonetwork]

7/ @NODERS_TEAM is now producing signed, verifiable data on the Shinzō testnet.

Testnet is live. 👇
https://t.co/vOmSh8UjqC

[Shinzo @shinzonetwork]

1/ Noders is now live on the Shinzō testnet as a Generator.

Welcome to the Shinzō Kazoku @NODERS_TEAM 🧵

[Shinzo @shinzonetwork]

6/ Validation, RPC, API, snapshots, development tools, and now verifiable data production at the source. An operator that builds across the full infrastructure stack.

[Shinzo @shinzonetwork]

Most people experience Ethereum through a wallet. They see a balance, a payment, a history of what they did.

If the company supplying that data can decide what they see, and that data can't be verified, Ethereum's guarantees only go so far.

We're building access to Ethereum data from the operators closest to its source.

[Shinzo @shinzonetwork]

6/ An operator that doesn’t just validate blocks but builds infrastructure to make that data usable.

Explorers, APIs, developer tooling, and now verifiable data production at the source on Shinzō testnet.

Testnet is live. Learn more. 👇
https://t.co/vOmSh8TLB4

[Shinzo @shinzonetwork]

1/ STAKEME is live on the Shinzō testnet as a Generator.

44 bare-metal nodes. 20+ mainnets secured. Custom block explorers for Sei, Celestia, Monad, and 0G. Multi-chain faucet and developer tooling.

Now producing verifiable blockchain data at the source.

Welcome to the Shinzō Kazoku @stakeme_pro 🧵

[Shinzo @shinzonetwork]

5/ @stakeme_pro already builds the tools that make chain data accessible.

Custom block explorers, multi-chain faucets, RPC endpoints, IBC relaying.

44 bare-metal nodes across 20+ mainnets. DDoS-protected. $15M+ staked.

[Shinzo @shinzonetwork]

Ask your data provider who signed the block behind your answer.

On Shinzō, Generators sign the block data they read from their own nodes. Hosts check those signatures and record when independent operators agree.

Now your app can ask who saw the same thing.

[Shinzo @shinzonetwork]

A deposit can settle onchain and still go uncredited if the exchange's data provider misses it.

Consensus verifies what happens onchain. Apps need to verify what they read.

Shinzō gives apps blockchain data they can verify back to the chain. Validator operators sign it at the source.

[Shinzo @shinzonetwork]

Consensus is decentralized. Access isn't.

An RPC can log your IP. A data provider can decide what your app sees. And apps take the answer on trust.

Ethereum's guarantees should reach the people using it.

That's why we’re building verifiable reads from the validator up.

[marilyn100x.eth @marilyn100x]

"Now that core is developed, we're shifting focus to the access." - @jchaskin22

Jason says the properties Ethereum guarantees at its core still fail to reach most users, who rely on gatekeepers like RPCs and app frontends.

I asked him how @ethereum brings those properties to every user.

> What is the main gap between how Ethereum is supposed to work and what most people experience?
> Which intermediaries still sit between users and Ethereum, and which can we already remove?
> Which part of a normal user flow forces the largest trust assumption?
What still needs to land before wallets stop defaulting to trusted RPCs?
> Which Ethereum guarantees do builders care most about preserving?
> What change in wallets or dApps would show the gap is closing? If this work succeeds, what would feel different for an ordinary user?

Full Q&A👇

[SHI @SHIknowz]

a decentralized network can still leave you relying on one company’s version of the truth

most applications don’t read blockchain data directly. they get it through rpcs, indexers and apis that turn it into something useful

if that data is wrong or incomplete, the application can make the wrong decision even when the chain is working perfectly

verifiable data gives us a way to trace an answer back to its source and check it independently

we've built networks where anyone can verify what happened. the information people use to make decisions must also be verifiable.