OZONE CHAIN / WHITEPAPER V3.0A clearer view of the network ↗
HOME / WHITEPAPER
OZONE CHAIN (OZONE) / VERSION 3.0 / OCTOBER 2026

The 5-Layer Blockchain.
Read the whitepaper.

An EVM-compatible public blockchain built with the Cosmos SDK and secured by CometBFT consensus. Read the complete source text below, or download the original PDF.

About this online edition

This HTML edition reflows the supplied whitepaper v3.0 for online reading. The PDF remains the original layout reference. Figures, application statuses and resource names in the source text reflect the October 2026 edition, rather than live network values.

Website updates: SpinZone is now displayed as OSpin; the project has confirmed Real Zone as live. The current GitHub is OA-Technology-Inc, and articles are available in the local Ozone Journal. These updates do not silently alter the original whitepaper text.

SOURCE PDF · PAGE 3

Abstract

ABSTRACT A public blockchain built in five layers Ozone Chain is a public 5-layer blockchain. Its five layers (Network, Consensus, Application, Execution and Applications) combine the Cosmos SDK, CometBFT consensus and the Ethereum Virtual Machine (EVM). Applications get single-block finality and low fees, while developers keep using Solidity, MetaMask and the standard Ethereum toolchain.

OZONE is the network's native coin. It pays transaction fees, secures the chain through delegated staking and carries voting power in on-chain governance. OZONE has a fixed maximum supply of 50,000,000, an initial supply of 50,000 at launch, and a supply that can only shrink through burning.

This paper describes the network's architecture, consensus and governance, the OZONE token model, the application ecosystem and the roadmap from mainnet genesis on 1 July 2025.

At a glance

50,000,000 Maximum OZONE supply 1 block Finality, ~4.8 s block time 74 Active validators 8.16M Transactions since genesis 1.63M Addresses 5 live Applications of 25 planned On-chain figures from ozonescan.com, 20–21 October 2026. Validators counted across the latest 2,000 blocks.

View this section in the original PDF ↗
SOURCE PDF · PAGE 4

01 · Introduction

Introduction Most applications must choose between Ethereum's developer ecosystem and the speed and cost of newer chains. Ozone Chain removes that trade-off by running the EVM on a Cosmos SDK chain with CometBFT finality.

1.1 The problem

Slow finality On many chains a payment is only safe after several confirmations, too slow for checkout, gaming and trading.

Unpredictable fees Congestion on large networks makes small payments and frequent in-app actions uneconomic.

Costly migration Chains with their own virtual machine force teams to rewrite contracts, rebuild tooling and retrain developers.

1.2 Ozone Chain's approach

1 Instant finality. A block is final the moment it is committed, with no reorganisations.

2 Low, stable fees paid in OZONE.

3 Full EVM compatibility. Existing Solidity contracts, wallets and developer tools work without changes.

4 Public governance. OZONE stakers decide network upgrades and parameters on-chain.

5 One ecosystem, one coin. Wallets, payments, commerce, media and publicinfrastructure applications all settle in OZONE.

View this section in the original PDF ↗
SOURCE PDF · PAGE 5

02 · Network overview

Mainnet configuration from whitepaper v3.0
ParameterValue
NetworkOzone Mainnet
FrameworkCosmos SDK
ConsensusCometBFT · delegated Proof-of-Stake
ExecutionEVM
Coin / decimalsOZONE / 18
Chain ID10121 (0x2789)
Genesis1 July 2025
RPChttps://chain.ozonescan.com
Explorerhttps://ozonescan.com

Network overview Ozone Chain mainnet has run continuously since genesis on 1 July 2025.

Network type Public, permissionless 5-layer blockchain Framework Cosmos SDK Consensus CometBFT, delegated Proof-of-Stake Finality Single block (instant) Execution Ethereum Virtual Machine Native coin OZONE (18 decimals) Chain ID 10121 (0x2789) Mainnet genesis 1 July 2025 Average block time ~4.8 seconds (October 2026) Nodes 100+ (validators and full nodes) Active validators 74 (latest 2,000 blocks, 21 October 2026) Public RPC https://chain.ozonescan.com Exchanges LBank, KoinBX (India, FIU-IND registered) Website ozonechain.com Mainnet explorer ozonescan.com Testnet explorer testnet.ozonescan.com

Network activity

14,641,529 Blocks produced 8,160,233 Total transactions 1,627,112 Addresses 11.3k–18k Daily transactions

0.01 Gwei

Gas price Source: ozonescan.com, 20 October 2026. Daily range covers the previous 30 days.

View this section in the original PDF ↗
SOURCE PDF · PAGES 6, 7

03 · The 5-Layer Architecture

The 5-Layer Architecture Each layer has one job, and each can be upgraded without disturbing the others: Network moves data, Consensus orders and finalises it, Application keeps the state, Execution runs smart contracts, and Applications serve users.

USERS AND DEVELOPERS FIGURE 1 LAYER 5 Applications dApps, wallets (MetaMask), ecosystem utilities and the ozonescan.com explorer LAYER 4 Execution · EVM Solidity smart contracts, Ethereum JSON-RPC, 0x addresses, Hardhat and Remix tooling LAYER 3 Application · Cosmos SDK Modules for bank (OZONE transfers), staking, distribution, slashing and governance LAYER 2 Consensus · CometBFT Delegated Proof-of-Stake validators, BFT voting, finality in one block LAYER 1 Network · P2P Peer-to-peer gossip between validator and full nodes over TCP/IP VALIDATORS AND FULL NODES 100+ NODES

Instant finality

Committed blocks are final; no reorganisations.

Ethereum tooling

Solidity, MetaMask and JSON- RPC work unchanged.

Modular upgrades

Each layer evolves through onchain governance.

The five layers in detail

3.1 · LAYER 1

Network Validator and full nodes exchange transactions and blocks over a peer-topeer gossip protocol. Any party can run a full node and verify the whole chain independently, without trusting a third party.

3.2 · LAYER 2

Consensus (CometBFT) CometBFT is a Byzantine Fault Tolerant engine. Validators propose and vote on each block in rounds; a block commits once validators holding more than twothirds of voting power sign it. A committed block is final and cannot be reorganised.

3.3 · LAYER 3

Application (Cosmos SDK) The state machine is built with the Cosmos SDK, a modular framework used by many production blockchains.

Its modules run OZONE transfers (bank), staking, reward distribution, slashing and on-chain governance.

3.4 · LAYER 4

Execution (EVM) An EVM module executes Ethereum smart contracts inside the Cosmos SDK application. Solidity contracts deploy unchanged through the standard JSON- RPC interface; MetaMask, Hardhat and Remix work out of the box with familiar 0x addresses.

3.5 · LAYER 5

Applications Where users meet the chain: wallets, payment apps, games, marketplaces, enterprise tools and the ozonescan.com explorer. Every application settles in OZONE and inherits the security and finality of the four layers beneath it.

3.6 · FEES

Paid in OZONE Every transaction pays a gas fee in OZONE. Fees go to validators and delegators through the distribution module, rewarding the operators who secure the network. Current gas price:

0.01 Gwei.

View this section in the original PDF ↗
SOURCE PDF · PAGE 8

04 · Consensus, validators and staking

Consensus, validators and staking Ozone Chain is secured by validators who stake OZONE and can lose part of that stake if they misbehave.

4.1 Validators

Ozone Chain is a public network: anyone who meets the minimum self-bond of OZONE can run a validator. More than 100 nodes, validators and full nodes together, run the network.

Voting power equals a validator's own stake plus OZONE delegated to it.

100+ Nodes running the network 74 Validators in the latest 2,000 blocks 5.9% Share of the most active validator 47% Share of the ten most active Block production measured on ozonescan.com, 21 October 2026. No single operator or small group controls the chain.

4.2 Delegation

Holders who do not run a node can delegate OZONE to a validator.

Delegated coins stay owned by the delegator; they add to the validator's voting power and earn a share of its fees, minus commission.

4.3 Rewards

Validators and delegators earn the transaction fees paid on Ozone Chain, in OZONE, in proportion to their stake and uptime. Fees are distributed automatically every block.

4.4 Slashing

Double-signing: a share of stake is slashed and the validator is removed.

Extended downtime: a smaller share is slashed and the validator is jailed.

Penalties also apply to delegations.

4.5 Unbonding

Staked OZONE is released after an unbonding period. During this period the coins earn no rewards and can still be slashed for earlier misbehaviour.

View this section in the original PDF ↗
SOURCE PDF · PAGE 9

05 · On-chain governance

On-chain governance Changes to Ozone Chain's parameters and software are decided by OZONE stakers through on-chain votes, operating as a DAO.

What the DAO decides

Network parameters Chain software upgrades Monthly allocation releases Spending from community funds

How a proposal moves

1 Proposal Any OZONE holder submits a proposal with a deposit.

2 Deposit period The proposal enters voting once it reaches the minimum deposit.

3 Voting period Staked OZONE votes Yes, No, No with veto or Abstain; delegators vote directly or inherit their validator's vote.

4 Tally A proposal passes when it meets quorum and the passing threshold.

5 Execution Parameter changes apply automatically; upgrades activate at the block height named in the proposal.

DAO

The majority of staked OZONE and of validator nodes is held by the community, not the founding team. Because voting power comes from staked OZONE, the public that secures the network is the public that steers it.

View this section in the original PDF ↗
SOURCE PDF · PAGES 10, 11

06 · OZONE token

Maximum-supply allocation
AllocationShareOZONERelease
Ecosystem rewards95%47,500,000Through NFTWall
Team2%1,000,000Monthly over 120 months; DAO-approved
Liquidity1%500,000Monthly over 120 months; DAO-approved
Research & development1%500,000Monthly over 120 months; DAO-approved
Server infrastructure1%500,000Monthly over 120 months; DAO-approved
Total100%50,000,000

OZONE token OZONE has a hard cap of 50,000,000 coins; 95% is reserved for ecosystem rewards and only 2% goes to the team.

6.1 Utility

Gas

Pays for every transaction and contract call.

Staking

Validators and delegators stake it to secure the network.

Governance

Staked OZONE is voting power in proposals.

Payments

Ecosystem applications accept and settle in it.

6.2 Supply

50,000,000 Maximum supply, can never increase 50,000 Initial supply at launch Deflationary Supply only shrinks through burning

6.3 Distribution

Allocation Share OZONERelease Ecosystem Rewards 95% 47,500,000Through the NFTWall program Team 2% 1,000,000Monthly over 10 years, DAO-approved Liquidity 1% 500,000Monthly over 10 years, DAO-approved Research & Development 1% 500,000Monthly over 10 years, DAO-approved Server Infrastructure 1% 500,000Monthly over 10 years, DAO-approved Total 100% 50,000,000

6.4 Treasury and release schedule

95% Ecosystem Rewards Held in a treasury contract and distributed to participants through the NFTWall program (nftwall.io).

5% Team, Liquidity, R&D, Server Released in monthly instalments over 10 years (120 months). Each release is approved by the DAO.

Every allocation has its own wallet, published on ozonechain.com and trackable on ozonescan.com, so the community controls how fast coins reach the market.

6.5 Burning

OZONE is burned by sending it to an unspendable address. Burned coins leave supply permanently; every burn is an on-chain transaction anyone can verify, and the cumulative burned amount is reported live.

BURN ADDRESS 0x000000000000000000000000000000000000dEaD

6.6 Supply transparency

Supply figures are calculated from on-chain balances and published through public endpoints used by ozonechain.com and by market-data providers such as CoinMarketCap and CoinGecko.

Endpoint Returns ozonechain.com/api/max-supply Maximum supply ozonechain.com/api/total-supplyMaximum supply minus burned ozonechain.com/api/circulating-supplyTotal supply minus treasury and locked wallets ozonechain.com/api/burned Cumulative burned OZONE Circulating supply = 50,000,000 − Burned − Treasury − Locked allocations

View this section in the original PDF ↗
SOURCE PDF · PAGES 12, 13

07 · Ecosystem

Ecosystem Twenty-five applications are planned on Ozone Chain: five are live today and twenty are in active development. Each uses OZONE for payments or fees, tying real usage to the coin.

Live today

Ozone Chain LIVE Core network The 5-layer EVM blockchain. OZONE pays gas, secures staking and carries governance votes.

ozonechain.com NFTWall LIVE NFT marketplace and ecosystem rewards Mint, buy and trade NFTs on Ozone Chain. Distributes OZONE ecosystem rewards to participants.

nftwall.io Meta Predict LIVE Prediction game · Android Players predict whether Bitcoin's price goes up or down in 60-second rounds, using OZONE.

metapredict.io PromoZone LIVE Promotions and shopping Converts Promo NFTs into shopping coupons redeemable at participating online and offline merchants.

promozone.io SpinZone LIVE Gaming A live game application in the Ozone Chain ecosystem.

Meta Ludo LIVE Gaming A Ludo board game in the Ozone Chain ecosystem.

In active development

Twenty applications across four categories, each built to settle in OZONE.

WALLETS, PAYMENTS AND TRADING

Like Wallet Self-custody wallet for multiple crypto assets OzoPay Crypto payments that integrate with merchant platforms ODEX Decentralised exchange with liquidity pools and automated market making OzoneX Crypto exchange with trading fees paid in OZONE Wild Card Crypto card for ATM withdrawals and purchases

COMMERCE AND TRAVEL

FlyZone Flight booking paid in OZONE, with rewards OzoStay Accommodation booking paid in OZONE, with rewards Real Zone Real-estate brokerage platform settling in OZONE Secured Trade Trading-protection plans purchased with OZONE Cash Gain Crowdfunding platform for community projects

SOCIAL, MEDIA AND GAMING

Open Style Decentralised social media application MetaTube Decentralised video-sharing platform Cloud Connect Video conferencing platform Battle 11 Game application

ENTERPRISE AND PUBLIC

INFRASTRUCTURE

O Ledger Retail and online billing with tamper-proof records QROZ QR-code product authentication against counterfeits ONID Self-sovereign digital identity for education, health and financial records Votom Blockchain voting for private and public elections OzoSpace Platform for creators of space-technology ideas Crypto Academy Blockchain education and courses

View this section in the original PDF ↗
SOURCE PDF · PAGE 14

08 · Roadmap

Roadmap The roadmap starts at mainnet genesis on 1 July 2025 and runs in phases, not dates.

A phase is complete when every application in it is live; an application can launch early if it is ready.

1 Foundation LIVE Genesis 1 July 2025 · ozonescan.com · EVM and MetaMask · validator network · LBank and KoinBX Live apps: NFTWall · Meta Predict · SpinZone · Meta Ludo · PromoZone 2 Transparency and listings Supply API · verified treasury and allocation wallets · CoinMarketCap and CoinGecko update · audit · whitepaper v3 3 Wallets, payments and trading Like Wallet · OzoPay · ODEX · OzoneX · Wild Card 4 Commerce and travel FlyZone · OzoStay · Real Zone · Secured Trade · Cash Gain 5 Social, media and gaming Open Style · MetaTube · Cloud Connect · Battle 11 6 Enterprise and public infrastructure O Ledger · QROZ · ONID · Votom · OzoSpace · Crypto Academy 7 Scale and decentralisation Larger validator set · broader community governance · cross-chain interoperability

View this section in the original PDF ↗
SOURCE PDF · PAGE 15

09–10 · Security and risk factors

Security

Security rests on BFT consensus, economic penalties, independent audits and public verifiability.

Consensus safety

Safe while less than one-third of voting power is faulty. Committed blocks are final.

Economic security

Validators and delegators stake their own OZONE; slashing makes attacks costly.

Smart-contract audits

NFTWall contracts are audited by SolidProof, with periodic third-party reviews.

Verified contracts

Treasury and core contracts are sourceverified on ozonescan.com.

Open verification

Every block, balance, burn and release is public; anyone can run a full node.

Key management

Users hold their own keys; applications are non-custodial by default.

Risk factors

Technology. Bugs, consensus failures or outages could interrupt the chain.

Upstream software. Defects in Cosmos SDK, CometBFT or EVM components may affect the network until patched.

Smart contracts. Applications run their own contracts, which may hold vulnerabilities even after audit.

Validator concentration. Concentrated voting power raises collusion and outage risk.

Market and liquidity. OZONE trades on few exchanges; price can be volatile and liquidity thin.

Regulation. Digital-asset laws differ by country and may restrict access in some regions.

Key management. Lost or stolen private keys cannot be recovered by the network.

Execution. Roadmap applications may launch later, change scope or not launch.

View this section in the original PDF ↗
SOURCE PDF · PAGE 16

11 · Developers and community

Mainnet and testnet settings
SettingMainnetTestnet
Network nameOzone MainnetOzone Testnet
RPChttps://chain.ozonescan.comhttps://rpc-testnet.ozonescan.com
Chain ID10121 (0x2789)10120 (0x2788)
Currency symbolOZONEtOZONE
Explorerhttps://ozonescan.comhttps://testnet.ozonescan.com

Developers and community Ozone Chain is listed on Chainlist, so any EVM wallet or tool connects with the settings below.

Setting Mainnet Testnet Network name Ozone Mainnet Ozone Testnet RPC URL https://chain.ozonescan.comhttps://rpctestnet.ozonescan.com Chain ID 10121 (0x2789) 10120 (0x2788) Currency symbol OZONE tOZONE Block explorer ozonescan.com testnet.ozonescan.com

Add Ozone Chain to MetaMask

1 Open MetaMask and choose Add network 2 Select Add a network manually 3 Enter the mainnet settings above 4 Save and switch to Ozone Mainnet

Developer resources

GitHub github.com/ozoneofficial Blog medium.com/@ozonechain Chainlist chainlist.org/chain/10121

Community

X @ozonechain Telegram t.me/ozonechainofficial Discord discord.gg/ReJnPSkgF2 YouTube @ozonechainofficial Facebook /ozonechain Instagram @ozonechain

View this section in the original PDF ↗
SOURCE PDF · PAGE 17

12 · Company and legal disclaimer

Company and legal disclaimer

12.1 Company

Company Ozone Automation Technologies Inc.

Jurisdiction Panama Registration number 155765694 Founder and CEO Emmanuel Dzeko Website ozonechain.com Mainnet explorer ozonescan.com Testnet explorer testnet.ozonescan.com Ecosystem websites nftwall.io · metapredict.io · promozone.io

12.2 Disclaimer

This whitepaper is for information only. It is not an offer to sell, or a solicitation to buy, any security, investment or financial product, and it is not financial, legal or tax advice.

OZONE is a utility coin used for network fees, staking and governance on Ozone Chain. Nothing in this document promises any price, income, yield or return. The value of OZONE can fall as well as rise, and holders can lose all of their value.

Statements about future plans, applications and timelines are forward-looking. They reflect current intentions and may change or not happen. Blockchain technology carries technical, regulatory and market risks.

Each reader is responsible for complying with the laws of their own jurisdiction, including tax and any restrictions on acquiring or using digital assets. OZONE is not intended for persons in jurisdictions where its use is prohibited. Users hold their own keys and are solely responsible for their wallets and on-chain actions.

This document may be updated. The latest version is published on ozonechain.com.

View this section in the original PDF ↗
SOURCE PDF · PAGE 18

Glossary, references and document history

Glossary

5-Layer Architecture Ozone Chain's five layers: Network, Consensus, Application, Execution, Applications Delegation Assigning staked OZONE to a validator without giving up ownership BFT Byzantine Fault Tolerance: consensus that stays correct even if some participants are malicious EVM Ethereum Virtual Machine, the runtime that executes smart contracts Block A batch of transactions added to the chain at once Finality The point after which a transaction cannot be reversed Burn Sending coins to an unspendable address, removing them from supply permanently

Gas

The fee, paid in OZONE, for processing a transaction Circulating supply Coins available on the market, excluding treasury, locked and burned coins Genesis The first block of Ozone Chain mainnet, produced on 1 July 2025 CometBFT The consensus engine that orders and finalises Ozone Chain blocks Slashing Removing part of a validator's stake as a penalty for misbehaviour Cosmos SDK The modular framework used to build Ozone Chain's state machine Treasury The contract that holds Ecosystem Rewards and distributes them through the NFTWall program

DAO

The community of OZONE stakers who decide proposals on-chain Unbonding period The waiting time before unstaked OZONE becomes transferable Delegated Proof-of-Stake Holders delegate stake to validators who produce blocks Validator A node operator that proposes and signs blocks

References

1. Cosmos SDK documentation · docs.cosmos.network 2. CometBFT documentation · docs.cometbft.com 3. Ethereum Virtual Machine · ethereum.org/developers/docs/evm 4. Ozone Chain explorer · ozonescan.com 5. Network registry · chainlist.org/chain/10121

Document history

Version 3.0 October 2026 Full rewrite from mainnet genesis: 5-Layer Architecture, official tokenomics, current ecosystem and phase roadmap. Supersedes all earlier versions.

View this section in the original PDF ↗