Orochi Network

on
CoinYQ Dossier

One billion in the diagram, seven hundred million in the contracts

Orochi asks users to trust proofs instead of databases, yet its token story creates its own verification problem. The published allocation begins at one billion ON; the current Ethereum and BSC contracts expose 600 million and 100 million. The missing reconciliation is where product ambition, chain mechanics and governance promises meet.

A proof project meets an accounting gap

The one-billion allocation and the 700 million base units are not rival versions of the same number. One describes intended distribution; the other records tokens actually instantiated by two current contracts.

The address change matters because the December 2025 TGE article points to superseded contracts. CoinGecko and Orochi's repository now identify the live Ethereum and BNB deployments, so readers following the origin story must not mistake an announcement for the current asset.

Until the project locates the remaining 300 million and publishes a reserve-aware cross-chain ledger, a holder cannot tell whether the gap represents unissued inventory, another issuance path or future dilution.

The database proves state while retaining permissions

zkDatabase is an offchain document database with owners, groups and other-user permissions. Its SDK exposes insert, update, query, history and Merkle operations, while an API key authenticates use of the hosted service.

A zero-knowledge proof can attest to a property or transformation without revealing every underlying field. That protects confidentiality only within the stated circuit and data assumptions; it does not prove an input was truthful before entry.

This is a delivered developer surface, but it combines cryptographic verification with service accounts and permission administrators. “Verifiable” describes what a proof covers, not the absence of operators.

zkMemory is a component rather than a universal machine

zkMemory reduces memory correctness to constrained READ and WRITE operations: a read must match the latest write, and writes must respect configured regions. Rust packages and source code make the component inspectable.

Builders can choose layouts, word sizes, instruction sets and proof engines. This flexibility helps construct zkVMs, but each custom machine still needs its own circuit review, benchmarks and security assumptions.

The wider ZK-data-rollup architecture recursively composes proofs of data processing. Official architecture claims are useful design evidence; production throughput, decentralization and failure behavior require live measurements the reviewed material did not provide.

A one-shot mint is simple; distribution is not

Ethereum ON could mint 600 million only once to the owner, and BSC ON used the same shape for 100 million. Once supply was nonzero the mint path closed; the base contracts have no proxy upgrade, pause or blacklist.

Distribution happens through vesting, treasury and airdrop contracts. The launch plan placed 30% in network incentives and 21.55% in ecosystem reserve, while Foundation, marketing/liquidity, team, investors and airdrop control the rest.

Airdrop rules also differed by cohort: the largest 6,000 wallets vest monthly for 12 months; others face a one-month cliff. A fixed token contract does not prevent scheduled unlocks or discretionary treasury sales.

The bridge adds the controls the base token lacks

The 2026 bridge design wraps Ethereum ON into wON and uses Chainlink CCIP pools. BSC locks/releases its 100-million base supply. Ethereum CCIP minting consumes a local counter capped at 100 million; burns replenish that headroom. This is neither a lifetime issuance cap nor a cap on total wON. Depositing native Ethereum ON mints reserve-backed wON without applying that constant.

wON is upgradeable, pausable and role controlled. The design assigns upgrades to a 48-hour timelock but permits operational multisig roles around pause, pool custody and mint/burn, so holder safety depends on keys and Chainlink messaging as well as Solidity.

The state file dated June 23, 2026 reports redeployment and wiring work, but still lists a small live round trip as the next step and contains pending replacement-address fields. These are dated repository statements, not an independently replayed deployment or a September operational verdict. They leave route availability to be established separately.

The token promises roles without transferring the institution

Official copy assigns ON to validators, storage providers, ZK sequencers and fee payers. Reviewed sources did not show a live validator roster, observed fee market or binding token-vote executor, so these remain described utilities rather than universal present rights.

Orochi Network Pte. Ltd. operates services under terms that reserve accounts, content and service control. A later Orochi Foundation announcement describes an independent nonprofit supporting grants and governance, but a token balance does not transfer its assets or corporate powers.

The strongest story is narrower than the slogan: software for proving database and memory operations exists, while reviewed records leave supply reconciliation and binding governance unresolved. The June 2026 bridge record also stops short of establishing current route availability. A holder owns transferable units and implemented access—not guaranteed yield, equity or completion.

How the project changed

  1. 2022-04
    Orochimaru repository opens

    The official organization created its full-node/MPC and VRF codebase.

  2. 2023-02
    zkDatabase repository opens

    The verifiable database became a distinct public software project.

  3. 2024-03-26
    Dashboard terms take effect

    Orochi published service rules separate from token rights.

  4. 2025-10-20
    One-billion allocation published

    Official token article described utilities and seven allocation buckets.

  5. 2025-12-18
    TGE eligibility portal announced

    Airdrop rules and now-superseded contract addresses were published.

  6. 2026-06
    CCIP deployment state is published

    The repository records completed wiring checks and leaves a small live round trip as the next step.

Evidence and primary sources

Last evidence review: 2026-09-05

What is Orochi Network?

Orochi Network began with a promise that data could remain private while its transformations became verifiable. That promise produced real developer tools: zkDatabase combines document permissions with proof generation, and zkMemory checks that reads follow the latest valid writes. ON is the token intended to pay and coordinate the broader validator, storage and sequencing network, but those future roles should not be confused with the software already delivered.

The token now presents its own verification puzzle. Official allocation totals one billion ON, while current base contracts instantiate 600 million on Ethereum and 100 million on BNB Smart Chain. The exact current addresses are recorded in the facts and sources; older TGE addresses were superseded. Until Orochi accounts for the remaining 300 million and bridge reserves, allocation, issued supply and wrapped supply must be kept separate.

What problem does Orochi Network solve?

Orochi tries to make offchain data transformations checkable without publishing the underlying private data. zkDatabase attaches ownership, group and other permissions to documents and can generate proofs over stored state; zkMemory constrains reads to the last valid write inside a customizable proof machine.

Its larger “verifiable data infrastructure” adds ZK data rollups, storage, validators and sequencers. The official token page describes staking, storage leasing, fees and validator rewards, but the reviewed sources did not expose a current validator set, mainnet consensus statistics or a binding governance executor. Those utilities should therefore be read as project-described network design, not all as observed production flows.

How does Orochi Network work?

The verified Ethereum token at 0x33f6BE84becfF45ea6aA2952d7eF890B44bFB59d minted 600,000,000 ON once to its owner and cannot call mint again after totalSupply becomes nonzero. The BSC contract at 0x0e4F6209eD984b21EDEA43acE6e09559eD051D48 used the same one-shot pattern for 100,000,000 ON; its ownership is now renounced according to the project bridge state. Neither base token is a proxy or exposes pause/blacklist.

The 2026 CCIP repository adds upgradeable wON, lock/release and burn/mint pools, pause roles, a 48-hour upgrade timelock and multisig handoff. Its 100-million limit applies to the local CCIP mint-headroom counter, not total wON supply: depositing Ethereum ON to wrap it against reserves is not capped by that constant. The state file dated June 23, 2026 reports wiring checks and leaves a small live round trip as the next step. That dated repository record does not establish September route availability.

Key facts

  • Current CoinGecko contracts: Ethereum 0x33f6BE84becfF45ea6aA2952d7eF890B44bFB59d; BSC 0x0e4F6209eD984b21EDEA43acE6e09559eD051D48.
  • Ethereum ON totalSupply is 600,000,000 and Blockscout showed 568 holders at review.
  • BSC ON was designed for a one-time 100,000,000 mint; the project bridge state records owner() as zero.
  • Both base tokens are non-proxy ERC-20 contracts with a one-shot owner mint and no pause or blacklist surface.
  • Official allocation claims a 1,000,000,000 ON total: 30% network incentives, 21.55% ecosystem reserve, 15% foundation, 11.65% marketing/liquidity, 10% team, 8% investors, 3.8% airdrop.
  • The reviewed current base contracts account for 700 million aggregate nominal units; the remaining 300 million and global supply reconciliation were not established.
  • A December 2025 TGE article published earlier ETH/BSC addresses, different from the current CoinGecko and repository addresses.
  • Top 6,000 airdrop wallets were assigned 12-month monthly vesting; other wallets a one-month cliff. XORO conversion was described as 10 XORO for 1 ON.
  • zkDatabase has SDK/API-key workflows plus document, collection, ownership and permission operations.
  • zkMemory is an open-source Rust toolkit for proving memory consistency and lets builders customize machine layout, word size, instructions and proof engine.
  • The ON utility page describes validator staking, distributed-storage leasing, ZK-sequencer rewards and transaction fees; live economic usage was not fully evidenced.
  • The CCIP code gives wON role-controlled pause/mint/burn and a 48-hour upgrade timelock. The 100-million limit caps CCIP mint headroom, not total wON supply or reserve-backed native ON deposits.
  • The June 23, 2026 bridge STATE record reports wiring checks and lists a small bidirectional live test as next; this is not a fresh determination of September bridge availability.
  • Holding ON gives ERC-20 transfer rights and access only where applications implement it; it does not convey equity, Foundation assets, IP, guaranteed yield or a legal claim on Orochi Network Pte. Ltd.

Official links

Categories

Related coins

Frequently asked questions

Which ON token is this?

The current CoinGecko asset maps Ethereum 0x33f6BE84becfF45ea6aA2952d7eF890B44bFB59d and BSC 0x0e4F6209eD984b21EDEA43acE6e09559eD051D48; older TGE announcement addresses are historical and must not be substituted.

Is total supply one billion?

That is the official allocation headline. Reviewed current base contracts show 600 million Ethereum plus 100 million BSC; the remaining 300 million/global reconciliation was not demonstrated.

Can the base token mint forever?

No. Each published base contract has a one-shot mint guarded by nonzero totalSupply. Ownership controls that first call, and both supplies are already minted.

Does ON run a live proof-of-stake chain?

The docs describe validator staking and sequencers, but reviewed evidence did not establish a current permissionless validator set or production consensus metrics.

What is already usable?

zkDatabase documentation exposes SDK and dashboard workflows, while zkMemory is installable open-source Rust code. Product availability and decentralized network maturity are separate questions.

Is the bridge live?

The project’s June 2026 state said wiring checks passed and a small two-way live test was still pending. Current route availability needs fresh verification before use.

Does staking guarantee yield?

No. The utility page describes incentives, but no fixed legal or protocol yield right follows from merely holding ON.

Do holders govern the company or Foundation?

No such right was established. Token governance language does not equal equity, board control, IP ownership or a claim on treasury assets.

External trackers

Choose a tracking site for Orochi Network: