HORMUZ.MEME  /  DOCS  /  CIRCULATING SUPPLY ATTESTATION

Circulating Supply Attestation

Method document a reviewer can use to independently reproduce HORMUZ's circulating-supply number on-chain.

Network
Base mainnet · chainId 8453
G0-A status
CLEAR-WITH-CONDITIONS
Circulating supply
1,500,000 HORMUZ at Base block 48584505
Uniswap V3 live pool
HORMUZ/USDC · 0x20c497699faf52e25f79d8a66b315d1f264e8674 · first swap 2026-06-13
GeckoTerminal
live as of 2026-07-14
DEX Screener
unconfirmed as of 2026-07-14 — Previously indexed; the pair API returned no pair on the observation date.
DexTools
live as of 2026-07-14
CoinCodex
submitted 2026-07-14 · pending · not approved
DropsTab
submitted 2026-07-15 · pending · not approved
Coinranking
submitted 2026-07-15 · pending · not approved
CoinCheckup
submitted 2026-07-15 · pending · not approved
Other free forms
partially submitted · submitted requests: DropsTab, Coinranking, CoinCheckup · staged values retained: none · restore required: CoinLore, LiveCoinWatch, CoinCarp, TokenInsight, Blockspot
Centralized exchanges (CEX)
none submitted
Official X
@hormuzians
Held-private ops docs
Not public
Last updated
2026-07-15

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 48584505.


1. Definitions

Only addresses on the published exclusion list are subtracted. No off-chain exclusions, no hand-waved estimates, no rounded numbers.

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. For each address marked excluded in the balance-treatment list (§3), read its balanceOf at that block.
  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)

# Address Role Excluded? Source
E1 0x8a5D41A03c40034Ec02a5e72450802b998F10f7F Treasury (Ledger cold wallet) Yes; balance at block 48584505: 998,499,900 HORMUZ DEPLOYMENTS.md, TREASURY-DISTRIBUTION-POLICY.md
E2 0xBabc8aB5847F2e4960F995b92dA6A0812F9Ba54c Deployer wallet Yes; balance at block 48584505: 100 HORMUZ DEPLOYMENTS.md
E3 0x799140699e802Ac48624bd90A84afe14cfCFd2bB LP wallet; holds the live Uniswap V3 position No. Included in circulating supply while the pool is live. DEPLOYMENTS.md, LIQUIDITY-OPERATIONS-POLICY.md
E4 MM wallet Excluded for the vested portion not yet released; included for the released portion n/a until G10 Internal operating document, not public. Available to counsel, auditors, market makers, and listing venues under appropriate review.
E5 Burn address (0x000…dead) Subtracted from total supply via the standard "burned supply" calculation — already excluded from totalSupply() if burn-on-transfer is used; for HORMUZ, holders self-burn and the burned tokens reduce totalSupply directly implicitly handled contract source

At snapshot block 48584505, excluded balances are E1 998,499,900 plus E2 100, for an excluded total of 998,500,000 HORMUZ. The LP wallet and tokens committed to the live pool are included. 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 48584505 is JSON-RPC block tag 0x2e55739. 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 48584505

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"},"0x2e55739"]}'

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"},"0x2e55739"]}'

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"},"0x2e55739"]}'

These exact calls were re-run successfully against https://mainnet.base.org on 2026-07-14. 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.

A spreadsheet or scratch script that ingests total supply plus the E1 and E2 balances and subtracts both balances is sufficient. Any reviewer who arrives at a different number must reconcile against the exclusion list — there is no other source of truth.

5. Update cadence

Trigger Action
Any treasury movement (per TREASURY-DISTRIBUTION-POLICY.md §5) Re-attest within 24 hours
Any MM tranche release Re-attest within 24 hours
Any addition or removal from the exclusion list Re-attest immediately
Monthly hygiene Re-attest on the first business day of each month
Pre-CEX submission Re-attest within 24 hours of submission

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

6. Status

Field Value
Gate G0-C
Authored 2026-06-08
Latest snapshot block 48584505 (Base) — 2026-07-13T15:59:18.798Z
Latest circulating supply 1,500,000 HORMUZ (totalSupply 1,000,000,000 − E1 treasury 998,499,900 − E2 deployer 100)
Re-run npm run attest:circulating
Status ATTESTED (pre-aggregator submit)

Last updated: 2026-07-15. This page mirrors the public-safe operating doc tracked at CIRCULATING-SUPPLY-ATTESTATION.md in the project's repository. Internal operating docs (budgets, counsel scopes, CEX submission tactics, entity planning, MM diligence, launch-day playbook) are not published here; they are available to counsel, auditors, market makers, and listing venues under appropriate review.