HORMUZ.MEME  /  COMPLIANCE
Compliance & Affiliation Notice

HORMUZ is not affiliated with any party named in the 2026 Strait-of-Hormuz news cycle.

This page is a public, contemporaneous statement of what HORMUZ is, and, more importantly, the entities, schemes, and narratives HORMUZ has no affiliation with. It is published so that exchange, wallet, and aggregator compliance reviewers can verify the project's position against active 2026 sanctions and adverse-media context at the same time as they encounter the project.

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 before reliable completion of the required score-80 fuzzy-name pre-screen. That timing is a logged process exception. DropsTab was submitted 2026-07-15 after a fresh venue-specific OFAC screen. Both requests remain pending and are not approved; submitting them does not establish sanctions, platform, or other compliance clearance. Other free forms are partially submitted: the seven remaining forms require restoration and are not submitted. Centralized exchanges (CEX): none submitted. Official X: @hormuzians.

01

HORMUZ is not affiliated with any of the following.

The list below is explicit and binding. If a third party publishes claims to the contrary, that party is misrepresenting HORMUZ.

HORMUZ has not received, transmitted, processed, facilitated, or accepted any payment from, to, or on behalf of any of the entities or schemes listed above. HORMUZ has no business model, revenue model, or operational role that involves any of them. The HORMUZ contract has no transfer tax, no admin function, no upgrade path, and cannot route value to any party other than the parties to a peer-to-peer transfer.

02

Why this notice exists.

The HORMUZ name is a geographic reference to the Strait of Hormuz, a maritime chokepoint between Iran and the Arabian Peninsula. In the 2026 news cycle, the same geographic term has been used in connection with: an OFAC alert on Iranian demands for Strait-of-Hormuz passage payments; the U.S. Treasury's designation of the Persian Gulf Strait Authority; the EU Council's May 22, 2026 extension of sanctions targeting parties impeding Strait-of-Hormuz transit; the OFAC June 2, 2026 designation of four Iranian crypto exchanges; FinCEN's IRGC front-company alert; and a parallel impersonation scam in which fraudsters posing as Iranian officials demand cryptocurrency from shipping companies.

None of those items involve HORMUZ-the-project. This notice exists so that the absence of involvement is documented in a public, contemporaneous form alongside the project itself, and is unambiguous to a compliance reviewer reading the site for the first time.

The first internal screening run, dated 2026-06-08, classified the project status as REVIEW. A second pass on 2026-06-09, live interactive screening at the OFAC SDN and UN SC portals, escalated the classification to REVIEW-HIGH after the OFAC name search for "HORMUZ" surfaced 15 Iran-context vessel and entity matches at fuzzy threshold 80. At the address level, the contract, treasury, and deployer all returned zero matches on the OFAC SDN and UN SC interactive searches. On 2026-06-12, external U.S. crypto counsel adjudicated the full screening record and issued a written sanctions & adverse-media opinion concluding there is no OFAC nexus between HORMUZ and any sanctioned person, entity, or jurisdiction; the name-level collision is reputational / adverse-media exposure only, not a sanctions nexus attributable to HORMUZ-the-token. The classification moved to CLEAR-WITH-CONDITIONS, clearing pool launch and public marketing on Base subject to the binding conditions listed above. The opinion does not extend to centralized-exchange compliance, MiCA, or securities classification; those remain separate analyses, and exchange / aggregator submissions remain subject to their own requirements and a pre-submission re-screen. The UK Sanctions List portal was in service outage at the time of the interactive pass and the EU FSF database requires authenticated access; both are scheduled for the next quarterly re-screen and before any UK / EEA-facing distribution.

03

Verifiable on-chain records.

Token contract (Base mainnet)
0xf912a4A0c374a33f192d0657719cE107194573F1, verified on BaseScan
Treasury (HORMUZ Treasury Controller, hardware cold wallet)
0x8a5D41A03c40034Ec02a5e72450802b998F10f7F, 998,499,900 HORMUZ at Base block: 48,584,505
Deployer
0xBabc8aB5847F2e4960F995b92dA6A0812F9Ba54c
Chain
Base mainnet (chainId 8453)
Standard
ERC-20, fixed supply 1,000,000,000 HORMUZ, 18 decimals, immutable
Uniswap pool
0x20c497699faf52e25f79d8a66b315d1f264e8674, Uniswap V3 HORMUZ/USDC 1%, live
Market-data and listing status
GeckoTerminal and DexTools live; DEX Screener unconfirmed. CoinCodex submitted 2026-07-14 and DropsTab submitted 2026-07-15; both are pending review and not approved. Other free forms are partially submitted: seven require restoration and remain unsubmitted. Centralized exchanges (CEX): none submitted.
04

Operational commitments.

05

Reporting impersonation.

Anyone observing an account, message, smart-contract clone, or domain that misrepresents HORMUZ as participating in the Strait-of-Hormuz toll scheme or the impersonation scam should report it to compliance@hormuz.meme and to the relevant platform.

HORMUZ does not contact shipping companies. HORMUZ does not request transit fees. HORMUZ does not request seed phrases or private keys. Any message claiming otherwise is fraudulent.

06

Internal references.

Last updated: 2026-07-14. This notice will be re-issued with each material change to the project's status, counsel adjudication, or compliance posture. Return to home.