OZONE CHAIN / WHITEPAPER V3.0A clearer view of the network ↗
HOME / OFFICIAL IDENTITY
VERIFY THE PROJECT BEFORE YOU CONNECT

Ozone Chain.
The coin is OZONE.

Use this page to confirm the project, network and official destinations. Ozone Chain at ozonechain.com is the public EVM-compatible network described in whitepaper v3.0.

OFFICIAL DOMAINozonechain.com
NATIVE COINOZONE
MAINNET CHAIN ID10121
SIMILAR NAME / DIFFERENT PROJECT

OZONE and OZO are different.

Ozone Chain at ozonechain.com uses OZONE. The similarly named project at ozonechain.io is associated with OZO. Do not transfer supply figures, technical claims or wallet instructions between them. Check the domain, full coin symbol, chain ID and explorer together.

NETWORK IDENTIFIERS

Check the connection.

Network
Ozone Mainnet
Chain ID
10121 (0x2789)
Currency
OZONE · 18 decimals
Public RPC
https://chain.ozonescan.com

These are mainnet identifiers. Testnet has separate settings; confirm the selected network before signing.

COMPANY RECORD

Know the issuer.

Company
Ozone Automation Technologies Inc.
Mercantile Folio
155765694
Domicile
Panamá, Province of Panamá, Republic of Panama

The supplied registry certificate is dated 14 April 2025. It gives the company domicile, but does not specify a street or office address.

OFFICIAL DESTINATIONS

Start from a known address.

Bookmark the destinations you use. A matching name or logo alone is not enough to verify a service.

FIGURES NEED CONTEXT

Allocation is not circulation.

The whitepaper specifies a maximum of 50,000,000 OZONE and a historical initial supply of 50,000 OZONE. Its allocation model assigns 95% to ecosystem rewards, 2% to the team and 1% each to liquidity, research and development, and server infrastructure. These amounts are not a statement of current circulating balances.

SOURCE & VERIFICATION

Read beyond the summary.

Network specifications and allocation rules follow the October 2026 whitepaper v3.0. Current balances, validator participation and supply can change. Verify current data through the explorer and read the security assessment within its stated scope.