orochi-network-primary-sources-2026-04-27

Orochi Network primary-source snapshot

Last reviewed: 2026-04-27 UTC

Project status snapshot

• Official site: https://www.orochi.network/
• Docs root: https://docs.orochi.network/
• GitHub org: https://github.com/orochi-network
• Current docs hub page: https://docs.orochi.network/orochi-network/

What the official materials say

1) Homepage / current framing

• URL: https://www.orochi.network/
• Key takeaways:
  • The site currently frames Orochi as “The World First Verifiable Data Infrastructure” and says it addresses scalability, privacy, and data-integrity challenges in blockchain systems
  • The homepage description explicitly extends the target surface beyond classic crypto use cases into AI/ML models, RWAs, enterprise finance, stablecoins, and zk applications
  • This broad framing is a clue that Orochi is trying to become general-purpose data-integrity middleware rather than only an oracle or database product

2) “What is Orochi Network?” docs page

• URL: https://docs.orochi.network/orochi-network/
• Key takeaways:
  • The main docs describe Orochi as a verifiable data infrastructure using ZKPs, FHE, and TEEs to guarantee data integrity and privacy
  • The page highlights two central components: the Verifiable Data Pipeline and ZK-data-rollups
  • The docs explicitly say Orochi aims to replace trust assumptions around third-party data handling with cryptographic proofs, which is the best high-level categorization signal

3) Verifiable Data Pipeline page

• URL: https://docs.orochi.network/verifiable-data-pipeline/
• Key takeaways:
  • Orochi says the Verifiable Data Pipeline is meant to replace traditional oracle systems
  • The system recursively proves each stage of sampling, processing, lookup, and transformation so that end-to-end data handling remains cryptographically verifiable
  • This is the strongest page for understanding Orochi as data-processing middleware rather than merely storage or chain infrastructure

4) zkDatabase docs

• URL: https://docs.orochi.network/zkDatabase/getting-started/
• Key takeaways:
  • The docs present zkDatabase as a “provable NoSQL database” with an SDK (zkdb), API keys, and a hosted GraphQL endpoint
  • This is high-signal because it reveals an actual developer product surface with installation instructions and service access rather than only a conceptual architecture
  • The existence of a concrete database product makes Orochi more legible as a data/control-plane vendor

5) Research section

• URLs:
  • https://docs.orochi.network/category/research/
  • https://docs.orochi.network/research/poseidon-hash/
• Key takeaways:
  • Orochi maintains research-oriented technical pages, including cryptography explainers like Poseidon hash for ZK applications
  • These pages are not a canonical protocol whitepaper, but they show the team is trying to ground parts of the stack in technical educational material and not only in marketing copy
  • The research pages also suggest the docs corpus itself is intended to serve as a substantial technical source of truth

6) Public repos / runtime lineage

• URLs:
  • https://github.com/orochi-network
  • https://raw.githubusercontent.com/orochi-network/orochimaru/main/README.md
  • https://raw.githubusercontent.com/orochi-network/orochi-docs/master/README.md
• Key takeaways:
  • The public repos expose components like Orochimaru (a Rust full-node client), smart contracts, observer tooling, docs, and older computation-layer surfaces
  • The Orochimaru README says Orochi is “not a blockchain” but a distributed network for MPC and ZKP proving, which is a meaningful architectural clue
  • The older docs README still frames Orochi as a computation layer for gaming with products like Orand, Orosign, and zkWASM/zkEVM-related surfaces, showing that the project’s narrative and product framing have evolved over time

Whitepaper / technical-doc status

• No single canonical Orochi Network whitepaper or litepaper surfaced in this pass.
• The strongest current source of truth is the official docs corpus, especially the main network page, the Verifiable Data Pipeline page, and zkDatabase docs.
• The repos and older docs are important because they reveal architecture lineage and product-surface drift that the current homepage smooths over.

Research notes

• Best current category for the library: verifiable data infrastructure / verifiable data pipeline / zk data-and-computation middleware.
• The key insight is that Orochi is more informative when treated as a multi-product stack with both current and legacy narratives, rather than as a single-product protocol.
• This makes Orochi a good long-tail catalog target because the docs+repo pairing exposes the real product surface more clearly than the homepage alone.