Circulating Supply Attestation

Current public attestation — not legal advice. Methodology and latest snapshot for self-reported circulating supply. Auditable on-chain by any third party. See DISCLAIMER.md.

CoinGecko, CoinMarketCap, Trust Wallet, and CEX listing teams routinely cross-check a project's self-reported circulating supply against the on-chain reality. CMC explicitly acts against misleading supply data. This document defines the method HORMUZ uses, so any reviewer can re-derive the number on the same inputs.

Companion docs: TREASURY-DISTRIBUTION-POLICY.md, LIQUIDITY-OPERATIONS-POLICY.md, DEPLOYMENTS.md, LISTING-DATA-ROOM.md.

Gate: G0-C. Status: Attested as of Base block 50930325.

1. Definitions

• Total supply = the totalSupply() view on the HORMUZ contract at the snapshot block.
• Excluded address = any wallet on the explicit list in §3 below. Each excluded address's balance is subtracted from total supply to compute circulating supply.
• Project-reported circulating supply = totalSupply() − Σ balances of excluded addresses, at the snapshot block.
• Snapshot block = a specific Base mainnet block number, recorded in the data room alongside the resulting circulating supply value.

Only addresses on the published exclusion list are subtracted. No off-chain exclusions or rounded balances are used. This is not an independently audited measure of public free float. The formula includes the separately disclosed LP / operations-wallet balance, including tokens outside the pool. An aggregator may classify controlled wallets differently; moving tokens between controlled wallets does not by itself establish circulation.

2. Method

1. Pick a Base mainnet block number, ideally the head block at the time of attestation.
2. Read totalSupply() at that block from the HORMUZ contract.
3. Read balanceOf for treasury, deployer and LP / operations wallet at that same block. Subtract only the treasury and deployer; disclose the operations balance separately.
4. Compute circulating = totalSupply − Σ excluded balances.
5. Record (block, totalSupply, list of excluded balances, circulating) in LISTING-DATA-ROOM.md §6, with the BaseScan link to the contract page for that block.
6. Publish the same numbers at https://hormuz.meme/docs/circulating-supply-attestation.html.

The balance treatment changes only by documented change to this file (G0-C re-approval). The list is the authoritative source — nothing else.

3. Balance-treatment list (current)

At snapshot block 50930325, excluded balances are E1 998,499,900 plus E2 100, for an excluded total of 998,500,000 HORMUZ. The LP / operations wallet and tokens committed to the live pool are included. The wallet holds 92,889.298733656228758671 HORMUZ at the same block; its inclusion does not mean those tokens are independently held public free float. Therefore:

1,000,000,000 − 998,499,900 − 100 = 1,500,000 HORMUZ circulating.

4. Re-verification recipe

A reviewer can independently verify this attestation at the exact snapshot block through the official Base mainnet JSON-RPC. Base block 50930325 is JSON-RPC block tag 0x3092295. The public endpoint below requires no API key, but Base documents it as rate-limited and unsuitable for production traffic. This recipe intentionally does not use BaseScan's retired V1 endpoints. Etherscan/BaseScan V2 requests for Base (chainid=8453) require an Etherscan API key; no explorer API is needed for these direct RPC calls.

Direct Base JSON-RPC at block 50930325

Read totalSupply():

curl -sS https://mainnet.base.org \
  -H 'content-type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0xf912a4A0c374a33f192d0657719cE107194573F1","data":"0x18160ddd"},"0x3092295"]}'

Read the E1 treasury balanceOf(address):

curl -sS https://mainnet.base.org \
  -H 'content-type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0xf912a4A0c374a33f192d0657719cE107194573F1","data":"0x70a082310000000000000000000000008a5d41a03c40034ec02a5e72450802b998f10f7f"},"0x3092295"]}'

Read the E2 deployer balanceOf(address):

curl -sS https://mainnet.base.org \
  -H 'content-type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0xf912a4A0c374a33f192d0657719cE107194573F1","data":"0x70a08231000000000000000000000000babc8ab5847f2e4960f995b92da6a0812f9ba54c"},"0x3092295"]}'

The total, treasury and deployer reads were independently verified on 2026-09-05 at block 50930325 through Base mainnet RPC endpoints; the same pinned observation also read the operations wallet. Their ABI-encoded uint256 results decode to 1000000000000000000000000000, 998499900000000000000000000, and 100000000000000000000 raw units respectively. Divide each by 10^18, then subtract the two excluded balances: 1,000,000,000 − 998,499,900 − 100 = 1,500,000 HORMUZ.

Read the separately disclosed E3 LP / operations balanceOf(address) at the same block:

curl -sS https://mainnet.base.org \
  -H 'content-type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0xf912a4A0c374a33f192d0657719cE107194573F1","data":"0x70a08231000000000000000000000000799140699e802ac48624bd90a84afe14cfcfd2bb"},"0x3092295"]}'

Its observed result is 92889298733656228758671 raw units, or 92,889.298733656228758671 HORMUZ. This fourth read is a disclosure, not another subtraction from the existing project-reported formula. Supply less all three known controlled-wallet balances would be 1,407,110.701266343771241329 HORMUZ; that alternative is also not an independently audited free-float measure.

A reviewer reproducing the project-reported number subtracts E1 and E2, then separately discloses E3. Different aggregator exclusions can produce a different number and should be reconciled explicitly.

5. Update cadence

The attestation history lives in LISTING-DATA-ROOM.md §6 and at https://hormuz.meme/docs/circulating-supply-attestation.html.

6. Status