ORC (Ozone Request for Comments) is the official standards, proposal framework, and developer tooling suite for Ozone Chain.
Inspired by Ethereum's EIP/ERC ecosystem, ORC standardizes token interfaces, smart contract protocols, wallet interaction conventions, and developer SDKs while maintaining 100% compatibility with standard EVM technologies and the existing ERC-20 ecosystem.
This repository houses two fundamental components of the Ozone Chain developer ecosystem:
ORC Repository
│
├── 1. Specifications & Protocols
│ ├── Governance & RFC Process (process/)
│ ├── Core Standards & Roadmaps (standards/)
│ ├── Solidity Reference Implementations (contracts/)
│ ├── Formal Compliance Test Suites (test/)
│ ├── Reproducible Gas Benchmarks (benchmarks/)
│ └── Certification & Ecosystem Guidelines (certification/, docs/)
│
└── 2. Official Developer Package
└── packages/orc/
▼
@ozonechain_orc/orc (npm package: ABIs, types, constants & helpers)
The official developer package exposes canonical ABIs, TypeScript type definitions, and chain metadata for building dApps, indexers, wallets, and scripts on Ozone Chain.
npm install @ozonechain_orc/orcimport { ORC20_ABI, OZONE_CHAIN_MAINNET, ORC_STANDARD } from "@ozonechain_orc/orc";
import { createPublicClient, http } from "viem";
const client = createPublicClient({
transport: http(OZONE_CHAIN_MAINNET.rpcUrls.default.http[0]),
});
const balance = await client.readContract({
address: "0x...",
abi: ORC20_ABI,
functionName: "balanceOf",
args: ["0x..."],
});For full details, see the Package Documentation.
- Strict EVM Compatibility: ORC operates at the smart contract, application, and tooling standards layer. It does not alter Ozone Chain's EVM execution environment, consensus, or base transaction semantics.
- Preservation of Existing Assets: Existing ERC-20 tokens deployed on Ozone Chain remain fully functional. No migration or contract redeployment is required to maintain compatibility.
- Canonical Interface Parity: Core standards (such as ORC-20) maintain exact ABI, function selector, and event signature equivalence with canonical ERC standards to guarantee seamless integration with MetaMask, ethers.js, viem, wagmi, AMMs, and EVM block explorers.
- Empirical Benchmarks: Performance and gas characteristics are strictly based on reproducible measurements on the EVM; marketing claims without verifiable benchmarks are prohibited.
- Open Governance: Clear, RFC-style proposal lifecycle managed by standards editors, open-source contributors, and ecosystem working groups.
ORC/
├── process/ # Governance, lifecycle, numbering & RFC template
│ ├── ORC-1.md # Foundational process specification
│ ├── lifecycle.md # Status transition machine
│ ├── numbering.md # Identifier allocation policy
│ └── template.md # Canonical proposal template
│
├── standards/ # Finalized and active specifications
│ ├── ORC-20.md # Ozone Fungible Token Standard
│ └── ROADMAP.md # Upcoming standards pipeline
│
├── contracts/ # Smart contract interfaces & reference code
│ ├── interfaces/ # Clean, modular Solidity interfaces
│ │ ├── IORC20.sol # Core ORC-20 interface
│ │ ├── IORC20Metadata.sol # Optional token metadata interface
│ │ └── IORC20Errors.sol # Standard custom revert errors
│ └── reference/ # Production-grade reference implementations
│ └── ORC20.sol # ORC-20 reference contract
│
├── test/ # Formal compliance and test suites
│ ├── ORC20Compliance.t.sol # Automated compliance test suite
│ ├── ORC20EdgeCases.t.sol # Boundary and fuzz test suite
│ └── helpers/ # Test runners and reporting utilities
│
├── benchmarks/ # Performance measurement suite
│ ├── ORC20Benchmark.t.sol # Forge gas measurement contracts
│ └── ORC20Benchmark.md # Reproducible gas analysis methodology
│
├── certification/ # Token compliance certification & registry
│ ├── CERTIFICATION.md # Tier definitions & verification requirements
│ ├── registry.json # Registry of certified tokens
│ └── verify-compliance.sh # CLI verification script
│
├── docs/ # Ecosystem developer documentation
│ ├── introduction.md # Ecosystem vision and overview
│ ├── compatibility.md # EVM & tooling compatibility matrix
│ ├── developer-guide.md # Building and testing ORC tokens
│ ├── ecosystem-integration.md # Wallet, DEX, Explorer & Bridge integration
│ ├── certification.md # How to verify and certify your contracts
│ ├── security.md # Smart contract security guidelines
│ └── npm-release.md # Package release process & guide
│
└── packages/ # Official npm packages monorepo workspace
└── orc/ # @ozonechain_orc/orc developer SDK
├── src/ # TypeScript source code (ABIs, types, constants)
├── package.json # Package configuration & exports
├── tsconfig.json # TypeScript compiler options
└── README.md # Package documentation
| Standard | Title | Category | Status | ERC Alignment | Description |
|---|---|---|---|---|---|
| ORC-1 | ORC Process and Governance | Process | Final | EIP-1 | Defines proposal structure, lifecycle, and editorial workflow |
| ORC-20 | Ozone Fungible Token Standard | Token | Final | ERC-20 | Canonical standard for fungible assets on Ozone Chain |
| ORC-165 | Standard Interface Detection | Interface | Planned | ERC-165 | Runtime interface query mechanism |
| ORC-721 | Ozone Non-Fungible Token | Token | Planned | ERC-721 | Unique and collectible assets standard |
| ORC-1155 | Multi-Token Standard | Token | Planned | ERC-1155 | Efficient batch and hybrid token management |
| ORC-2612 | Signed Approvals (Permit) | Token | Planned | ERC-2612 | Gasless signature-based token allowances |
| ORC-4626 | Tokenized Vault Standard | Application | Planned | ERC-4626 | Standardized yield-bearing vaults |
Ecosystem tokens deployed on Ozone Chain are classified into four transparent tiers:
- ERC-20 Compatible: A contract providing standard ERC-20 ABI functions.
- ORC-20 Compatible: A contract satisfying all normative semantic requirements of ORC-20.
- ORC-20 Certified: A contract that passes 100% of the official ORC-20 Compliance Suite with reproducible on-chain test receipts.
- ORC-20 Reference Implementation: The official implementation maintained by the Ozone Chain core team in
contracts/reference/.
See Certification Guide for verification procedures.
# Clone the repository
git clone https://github.com/Ozone-chain/orc.git
cd orc
# Run compliance tests
forge test --match-contract ORC20ComplianceTest -vv
# Run gas benchmarks
forge test --match-contract ORC20BenchmarkTest --gas-report# Install dependencies
npm install
# Build @ozonechain_orc/orc TypeScript SDK
npm run build
# Run SDK unit tests
npm testAnyone in the Ozone Chain community can author an ORC proposal or contribute to developer tooling. Please review:
Smart contract and tooling security is paramount in the Ozone Chain ecosystem. If you discover a vulnerability within an ORC reference implementation, package, or standard specification, please review SECURITY.md for our disclosure process.
| Parameter | Value |
|---|---|
| Network Name | Ozone Chain Mainnet |
| RPC Endpoint | https://node1.ozonechain.io |
| Chain ID | 4000 (0xFA0) |
| Native Currency | OZO |
| Block Explorer | https://ozonescan.io |
- Ozone Chain Website: https://ozonechain.io/
- Ozone Chain Explorer: https://ozonescan.io/
- Ozone Chain GitHub: https://github.com/Ozone-chain
- NPM Package: https://www.npmjs.com/package/@ozonechain_orc/orc