Start at GitHub
Explore the OA Technology organisation and its public Validator repository. Confirm current instructions and software versions before operating a node.
THE OZONE DEVELOPER CENTRE
Your Ethereum workflow.
A new place to build.
Connect your wallet, verify the network and bring your Solidity workflow to Ozone Chain. Start with the settings below, then explore the code and technical foundations.
01 / CONNECT TO OZONE
Configure once.
Build with familiar tools.
Ozone Chain exposes an Ethereum JSON-RPC interface for Solidity contracts and familiar 0x addresses. Select a network, review its settings and approve the network request in your wallet.
Adding a network changes wallet configuration; it does not transfer funds or deploy a contract.
EVM COMPATIBLE
Open block explorer ↗02 / START WITH A CONNECTION CHECK
Know your network.
Then write the transaction.
Keep connection checks separate from signing. A read-only RPC request helps confirm the chain before you deploy or move assets.
- 01
Choose your environment
Use testnet for experiments and mainnet for production transactions. Mainnet gas is paid in OZONE; testnet uses tOZONE.
- 02
Add the network
Select Mainnet or Testnet in the panel above. Use Add to wallet, or copy the RPC, chain ID, symbol and explorer into your wallet’s manual network settings.
- 03
Verify, fund and deploy
Confirm the chain ID in your tool and wallet. You need the selected network’s native coin for gas. Configure Hardhat or Remix with the matching RPC and chain ID before deployment.
READ-ONLY / MAINNET
Check the chain ID
curl https://chain.ozonescan.com -H 'Content-Type: application/json' --data '{"jsonrpc":"2.0","id":1,
"method":"eth_chainId","params":[]}'Expected chain ID0x2789 · 10121
This request reads network information. It does not connect a wallet, request a signature or transfer funds.
Testnet funding
A confirmed project faucet is not yet listed here. Obtain tOZONE through a verified project channel before testing deployment. Never enter a recovery phrase into a faucet or support form.
Official community channels ↗03 / OPEN THE RIGHT RESOURCE
Code, context
and independent verification.
Project repositories and upstream documentation serve different roles. Use the project source for Ozone-specific material and framework references for the underlying stack.
Understand the stack
Read the documentation maintained by Cosmos SDK, CometBFT and Ethereum. These references explain the components, rather than a complete Ozone deployment procedure.
Inspect what you deploy
Review transactions on the mainnet explorer and inspect published source-verification information in the verified-contract directory.
04 / BEFORE MAINNET
Build with care.
Verify the details.
Network compatibility does not make an application secure. Review your own contracts and operational practices before users depend on them.
- Confirm the chain ID, RPC and destination addresses.
- Test contract permissions, failure cases and gas requirements.
- Keep signing keys and recovery phrases out of source control.
- Review external dependencies and disclose application-specific risks.
Network settings and compatibility statements follow whitepaper v3.0, section 11 (October 2026). Use current project sources to confirm any operational changes.