HORMUZ.MEME  /  TOKENOMICS
Tokenomics

Fixed supply. Immutable. On record.

Every fact on this page is verifiable on-chain at the BaseScan link in the right-hand column. There is no off-chain claim that supports a number here.

Current public snapshot

One record for reviewers.

Supply snapshot: Base block: 48,584,505, observed 2026-07-13T15:59:18.798Z. Total/max supply is 1,000,000,000 HORMUZ; treasury balance is 998,499,900; deployer balance is 100; circulating supply is 1,500,000.

Liquidity: Uniswap V3 HORMUZ/USDC 1% is live at pool 0x20c497699faf52e25f79d8a66b315d1f264e8674. As observed 2026-07-14, GeckoTerminal and DexTools are live; DEX Screener is unconfirmed.

Listings: CoinCodex was submitted 2026-07-14; review is pending; it is not approved. DropsTab was submitted 2026-07-15 after a fresh venue-specific OFAC screen; review is pending and it is not approved. Other free forms are partially submitted: DropsTab is the only submitted request; the seven remaining forms require restoration and are not submitted. Centralized exchanges (CEX): none submitted. Official X: @hormuzians.

01 · Snapshot

Token snapshot.

NameHORMUZ
SymbolHORMUZ
StandardERC-20
NetworkBase mainnet (chainId 8453)
Decimals18
Total supply1,000,000,000 HORMUZ, minted once at deployment
Mint after deployNone. The contract has no mint function reachable after deployment.
Transfer taxNone.
PauseNone.
BlacklistNone.
Admin keysNone after deployment.
Upgrade pathNone. The contract is immutable.
BurnHolders may burn their own tokens at will.
02 · Addresses

On-chain references.

Contract 0xf912a4A0c374a33f192d0657719cE107194573F1, verified on BaseScan
Treasury (HORMUZ Treasury Controller, hardware cold wallet) 0x8a5D41A03c40034Ec02a5e72450802b998F10f7F — see Float Plan for earmarks vs on-chain float
Deployer 0xBabc8aB5847F2e4960F995b92dA6A0812F9Ba54c
Deployment transaction 0x253ece7c3ddb556cabd80c602ba99e8fa48229a8d5ccedf9e4da8ea6b63e04c7
Deployed at (UTC) 2026-06-08T03:14:55.547Z
Uniswap V3 HORMUZ/USDC pool (Base, 1%) 0x20c497699faf52e25f79d8a66b315d1f264e8674, live since 2026-06-13, full range
LP wallet (separate from cold treasury) 0x799140699e802Ac48624bd90A84afe14cfCFd2bB
02b · Liquidity (micro-launch)

HORMUZ/USDC pool on Uniswap Base.

A Uniswap V3 HORMUZ/USDC pool was created on Base mainnet on 2026-06-13 as a micro-liquidity launch, enough to make HORMUZ buyable and verifiable, not exchange-ready depth.

Pool0x20c497699faf52e25f79d8a66b315d1f264e8674
Pair / fee / rangeHORMUZ / native Base USDC · 1% · full range
Initial pool reserves1,499.00 USDC + 1,498,995 HORMUZ
Realized starting price$0.001000 per HORMUZ at the 2026-06-13 launch (verified on-chain)
Implied launch FDV≈ $1,000,000 at the 2026-06-13 launch (not a guarantee of value)
Initial pool TVL≈ $2,998 at the 2026-06-13 launch
TradeUniswap (verify contract 0xf912…73F1 first)

This is a thin pool. Price can move sharply on small trades, and you could lose the full amount you spend. HORMUZ is not a stablecoin, not an investment, not financial advice. See Legal & Risk.

02c · Float plan

Float is the product.

Published earmarks (intent until the transfer tx lands): 5% LP depth · 10% community/swarm · 6.9% public CEX/bridge reserve · remainder long-term treasury. Phase 0 already floated 0.15% into Uniswap (2026-06-13). Full table, phases, and verify links: float.html.

Holding tokens in a CEX reserve wallet is not a centralized-exchange listing. No wash trading. No spam airdrops.

03 · Supply schedule and circulating

How circulating supply is computed.

Total supply is fixed at 1,000,000,000 HORMUZ. The contract has no mint capacity reachable after deployment, so total supply will only decrease, and only through holder-initiated burns.

Circulating supply at Base block 48,584,505 is total supply − treasury − deployer: 1,000,000,000 − 998,499,900 − 100 = 1,500,000 HORMUZ. The deployer balance of 100 HORMUZ is disclosed and excluded alongside the Ledger treasury balance. Any later published CEX-reserve or community-ops wallet is excluded only while the current attestation explicitly treats its balance as non-circulating.

Any party can reproduce the snapshot with the block-pinned Base JSON-RPC calls in the public circulating-supply attestation. Current balances remain independently visible on BaseScan; if a current page and on-chain state disagree, on-chain state wins.

04 · Immutability

What "immutable" means here.

The HORMUZ contract source is published and verified on BaseScan. The contract does not implement the OpenZeppelin Ownable, Pausable, AccessControl, or upgrade-proxy patterns in a way that retains administrative capability after deployment. There is no privileged role that can mint, freeze, blacklist, redirect, tax, or upgrade the contract once it is live.

The trade-off is intentional: there is no kill switch. If a material issue emerges now that liquidity exists, the contract cannot be patched. The project's audit RFP documented the intended pre-liquidity review, and the official pool is now live; any future audit finding must be evaluated against the cost and risk of a redeploy. Immutability is part of the trust story, but it also removes the option to patch this deployment.

05 · What HORMUZ is not

This is not a stablecoin or a yield product.

HORMUZ is a fixed-supply ERC-20 culture token. It does not target a fiat peg. It has no reserves. There is no redemption right against any party. There is no yield, rebate, staking reward, or inflation-protection mechanism in the contract. Anyone who represents HORMUZ as a stablecoin, an investment, a security, or a guaranteed-return product is misrepresenting it. See Legal & Risk and the binding rules in the project's MARKETING-RULES.md.

06 · Compliance posture

Compliance posture as of 2026-07-14.

HORMUZ is not affiliated with the IRGC, the Persian Gulf Strait Authority, Iranian government entities, shipping authorities, maritime passage systems, toll schemes, vessel clearance, safe-passage payments, sanctions evasion, or impersonation scams. The full affiliation notice is at Compliance & Affiliation Notice. The current status is CLEAR-WITH-CONDITIONS; a fresh venue screen is required before each submission.

Last updated: 2026-07-14. Everything above is verifiable on-chain at the BaseScan link in §02.