Current public evidence summary: 2026-09-06. The canonical distribution profile is used to reconcile these facts; a date records observation rather than a promise that values cannot change. Exact original July records are preserved in a dated archive, not silently discarded.
Dated public snapshot — 2026-09-05
- Contract:
0xf912a4A0c374a33f192d0657719cE107194573F1, Base mainnet, chain ID 8453, ERC-20, 18 decimals, verified source. - Supply: 1,000,000,000 total/max supply. Project-reported circulating supply is 1,500,000 HORMUZ at Base block 50,930,325, observed
2026-09-05T23:13:17.671Z. - Method: total supply minus treasury
998,499,900minus deployer100. LP / operations wallet0x799140699e802Ac48624bd90A84afe14cfCFd2bBholds 92889.298733656228758671 HORMUZ and is included in this formula. This is not an independently audited measure of public free float. Aggregators may apply different exclusions; moving tokens between controlled wallets does not establish circulation. - Pool: Uniswap V3 HORMUZ/USDC 1% is live at
0x20c497699faf52e25f79d8a66b315d1f264e8674; native Base USDC is0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913. The factory lookup and pool tokens agree with these addresses. - Official X: @hormuzians. Other social accounts must stay blank unless independently verified. Contact: hello@hormuz.meme.
Official links and logo evidence
- Website, project facts JSON, public docs, tokenomics, supply methodology.
- Verified contract source, token balances.
- Stable original logo assets: 200px PNG, 256px PNG, 400px PNG, 512px PNG. All derive from the approved master; do not substitute a new mark. Verify live bytes immediately before a submission.
- Compliance notice, Legal & Risk, official X, contact hello@hormuz.meme.
No Telegram, Discord, Farcaster, public GitHub repository, origin jurisdiction or submitter role is asserted without evidence. Account creation, terms acceptance, signatures and payment remain human actions.
Description
HORMUZ is an ERC-20 culture token on Base built around internet-native satire, original alien characters and public-record commentary. The official website provides a character studio, project documentation and links to on-chain records. The token contract was deployed on Base mainnet on June 8, 2026. One billion HORMUZ were minted at deployment. The contract has no post-deployment mint function, transfer tax, blacklist, pause control or upgrade mechanism. Holders can burn tokens, which can reduce total supply. The HORMUZ/USDC Uniswap V3 pool was created on June 13, 2026 using native Base USDC and a 1% fee tier. Public records distinguish the token address, pool, treasury, deployer and LP/operations wallet. Project-reported circulating supply excludes the treasury and deployer balances but includes the disclosed operations balance; it is not an independently audited free-float measure. GeckoTerminal reported zero 24-hour volume at the September 5 observation. Thin liquidity can cause substantial slippage, and market values are snapshots rather than promises. HORMUZ has no redemption rights, reserve backing, promised return or guaranteed price. The project is not affiliated with any government, military, shipping authority or named third-party organization. Official accounts are linked from hormuz.meme; no Telegram, Discord or Farcaster account has been verified for this packet. Listing applications are distinguished from approved listings, and unconfirmed platforms are not presented as available markets.
Verified coverage and limitations
Observed 2026-09-05. API indexing, a visible chart, a project application and exchange approval are different facts.
| Surface | Verified observation | Public evidence / next action |
|---|---|---|
| Uniswap V3 Base | Live HORMUZ/USDC pool, 1% fee. Thin liquidity; pool existence is not a successful new swap transaction. | Pool; verify the contract before interacting. |
| GeckoTerminal | API indexed: the API returned the exact Base pool; the public chart page returned 404 and web contract search found no result in the final check. Provider snapshot: $0 24h volume and approximately $3,228.35 reserves. These are observations, not executable depth or guaranteed prices. | Pool API and API record. |
| DexTools | Live: exact Base HORMUZ/USDC pair and visible chart verified in the browser. Provider displayed 16 historical trades, 11 holders and $0 24h volume. Holder count is provider-reported, not independently reconciled. Inconsistent price/title values are excluded. | Exact pair. |
| DexPaprika | Indexed: exact Base pool returned by API. Price, project website and logo metadata were unavailable. | Pool API; indexing does not establish complete metadata or a functioning price chart. |
| DEX Screener | Unconfirmed coverage: pair, token and contract-search queries returned no matching result. No specific indexing cause has been established. | Pair API and expected pair URL; a constructed URL is not proof that a chart exists. |
Do not claim a listing is live from HTTP 200 alone. Check the exact chain, token and pool returned. No artificial trades, paid boosts or engagement manipulation are authorized to create indexing signals.
Documented applications and human follow-up
| Platform | Historical submission evidence | Current state at reconciliation | Human action |
|---|---|---|---|
| CoinCodex | Submitted 2026-07-14, documented in the campaign handoff. | Current review unknown; not approved means no approval evidence, not rejection. | Check the project email thread and official CoinCodex support path for a dated outcome. |
| DropsTab | Submitted 2026-07-15, documented receipt. | Current review unknown; not approved means no approval evidence. | Check the receipt/email and official DropsTab listing/support path. |
| Coinranking | Submitted 2026-07-15, documented Airtable confirmation and owner logo upload. | Current review unknown; not approved means no approval evidence. | Check the receipt/email and official Coinranking support path. |
| CoinCheckup | Submitted 2026-07-15, owner final-submit confirmation. The historical confirmation mentioned three working days; that is not current review evidence. | Current review unknown; not approved means no approval evidence. | Check the receipt/email and official CoinCheckup support path. |
| LiveCoinWatch | Submitted 2026-09-06; the saved application later displayed an official success state. The final click was not witnessed. | Current review and publication unknown; not approved means no approval evidence. | Preserve the observed confirmation and do not submit a duplicate. |
| Blockspot | Submitted 2026-09-06; the official form displayed “Coin submitted!” | Current review and publication unknown; not approved means no approval evidence. | Await editorial review and do not submit a duplicate. |
| Base ecosystem | Submitted 2026-09-06; the Coinbase-owned form confirmed the response was recorded. | Current review and directory publication unknown; no endorsement is claimed. | Await review and do not submit a duplicate. |
| Remaining free forms | Three owner-completion routes remain: CoinLore, CoinCarp and TokenInsight. | These three are not submitted. | Recheck current official forms, complete a fresh venue-specific screen, and perform required human account/CAPTCHA/legal steps individually. |
| Centralized exchanges (CEX) | None submitted in the documented record. | No application or approval is claimed. | Current eligibility, legal requirements, contacts and economics require separate review. Do not pay or make commitments from this page. |
A submission receipt does not prove review, publication, approval or endorsement. The documented record now contains seven applications: CoinCodex, DropsTab, Coinranking, CoinCheckup, LiveCoinWatch, Blockspot and Base ecosystem. Later forms retain their own current requirements and fresh venue-specific screening; a previous screen or application does not authorize a duplicate or different submission.
Compliance and risk controls remain in force
The recorded G0-A classification is Clear-with-conditions, from the counsel record dated 2026-06-12. The scope and conditions are preserved in Sanctions & Adverse-Media Name Screening and the public compliance notice. The September 6 operations pass refreshed the official interactive OFAC screen: 19 name-level results, including HORMUZ SAFE, and zero exact matches for the token, treasury, deployer or operations-wallet addresses. This is not a new legal opinion or counsel adjudication. The CoinCodex application was submitted before reliable completion of the required score-80 fuzzy-name pre-screen; the process exception remains disclosed. New platform requests retain their own eligibility and pre-submission screening requirements.
No independent security audit or liquidity-lock proof is claimed. HORMUZ has no guaranteed price, redemption right, reserve backing or promised return. Thin liquidity and total loss are material risks. Read the Legal & Risk notice.
Historical screening runs — recorded evidence
The rows below reproduce dated process history. They are not fresh September screens and do not override the preserved counsel conditions. The complete screening record retains findings F1–F14 and their later adjudication.
| Run date | Surfaces checked | Result | Notes |
|---|---|---|---|
| 2026-06-08 | OFAC SDN / Consolidated / Treasury press releases; UK Sanctions List; EU Consolidated Sanctions List; UN Security Council Consolidated List; FinCEN advisories; adverse-media indices | Review | Findings F1–F9 logged in SANCTIONS-NAME-SCREENING.md §6. Name-level adverse-media exposure is elevated due to active 2026 OFAC / EU / FinCEN action on Strait-of-Hormuz crypto tolls and a parallel impersonation scam in the press. Address-level negative search (indexed, not interactive). Owner + counsel adjudication required before any G6 / G9 / G11 / G13 / G14 submission. Manual interactive SDN/UK/EU/UN searches still required pre-submission. |
| 2026-06-09 | Interactive sanctions-portal screens: OFAC SDN Search (sanctionssearch.ofac.treas.gov), UN SC Consolidated List Search (search.sanctions.un.org), UK Sanctions List Search (search-uk-sanctions-list.service.gov.uk, in outage), EU FSF (webgate.ec.europa.eu/fsd/fsf, owner-only via EU Login). |
Review-high (escalated from REVIEW) | New findings F10–F14 in SANCTIONS-NAME-SCREENING.md §6.2. Contract / treasury / deployer addresses returned 0 matches on OFAC SDN and UN SC interactive searches, partially discharging the §6 follow-up item 2. Name "HORMUZ" at fuzzy threshold 80 on OFAC SDN returned 15 Iran-context vessel/entity matches (HORMUZ 2; IRAN HORMUZ 12 / 14 / 22 / 25; HORMOZ; HORMOZ OIL REFINING; HORMOZ UREA FERTILIZER; IRAN HORMOZ 12 / 14; PERSIA HORMOZ SHIP REPAIR YARD; PERSIA HORMOZ SHIP REPAIRS; PERSIA HORMOZ SHIPYARD; HOMA vessel + entity), confirming F1's name collision at the interactive level — basis for the REVIEW-HIGH escalation. UK portal returned service-outage page; retry required at next G0-A re-screen. EU FSF requires EU Login; route via counsel during G2 or grep public XML feed. Capture transcripts saved locally to screenshots/sanctions-private/ (gitignored — owner-reviewable). Blocker (unchanged through this row): no pool, liquidity, aggregator submission, wallet submission, or exchange submission may proceed until UK + EU checks captured, commercial wallet screening (Chainalysis / TRM / Elliptic) run, and counsel adjudicates whether REVIEW-HIGH can be cleared, mitigated, or requires rebrand. |
| 2026-06-12 | Counsel adjudication of the 2026-06-08 + 2026-06-09 screening record (no new portal pass; review of F1–F14, operator attestations §1, and address-level OFAC SDN + UN SC results). | Clear-with-conditions (counsel-adjudicated; was REVIEW-HIGH) | Anderson PC written memorandum dated 2026-06-12, matter ref HORMUZ-G0A-2026-06 (full memo held with counsel; authorized summary in SANCTIONS-NAME-SCREENING.md §6.3). Counsel finds no OFAC nexus between HORMUZ and any sanctioned person/entity/jurisdiction; F11–F14 address screens clean; F10 name collision is reputational/adverse-media only, not a sanctions nexus. Cleared scope: pool launch + public marketing on Base, subject to five conditions (marketing-rule compliance; keep compliance page current; quarterly + pre-submission re-screen; geo-restrict sanctioned jurisdictions; maintain non-affiliation list). NOT cleared: CEX/aggregator/wallet submissions (own requirements + pre-submission re-screen), MiCA, securities classification (G2 separate). Findings F1–F14 preserved. Provenance: logged per owner's representation of counsel's written memo. |
| 2026-07-13 | Pre-aggregator bulk OFAC SDN XML download (treasury.gov/ofac/downloads/sdn.xml, ~28.7 MB). Searched contract, treasury, deployer, pool addresses + HORMUZ/HORMOZ name strings. |
BULK CLEAN on addresses; name hits unchanged class | Address hits: 0 for 0xf912…73F1, 0x8a5D…0f7F, 0xBabc…a54c, 0x20c4…8674. Name substring hits remain (HORMUZ/HORMOZ Iran-context entities) — same reputational class as F10, not a new address nexus. Still required before CG/CMC submit: interactive OFAC SDN Search UI at https://sanctionssearch.ofac.treas.gov (counsel condition 3). Logged for G6/G7 prep in EXCHANGE-EXPANSION.md. |
| 2026-07-14 | Operational interactive OFAC SDN Search for contract, treasury, deployer, pool, LP wallet, and project name. | Address-clean; name-threshold control incomplete | All five address searches returned 0. The name field visibly showed 80 before Search, but the postback reset it to 100 and returned only the five score-100 vessel matches, not the 15-result score-80 set recorded on 2026-06-09. Treat this as an attempted control, not a reusable or reliably completed score-80 run. CoinCodex had already been submitted and is logged as a process exception; a fresh, threshold-evidenced name-and-address screen remains mandatory before every later aggregator/CEX request. See SANCTIONS-NAME-SCREENING.md §6.4 and marketing/outbound/SUBMIT-HANDOFF-2026-07-14.md. |
| 2026-09-06 | Official OFAC interactive name-and-address screen during the operations pass. | Address-clean; name-level collision remains | The screen returned 19 name matches, including HORMUZ SAFE, and zero exact address matches for the token contract, treasury, deployer, or operations wallet. This operational refresh is not a new legal opinion or counsel adjudication. Each later venue request retains its own eligibility and fresh-screening requirements. |
Attestation history
| Observation | Total supply | Treasury excluded | Deployer excluded | Reported circulating |
|---|---|---|---|---|
Historical 2026-07-13T15:59:18.798Z, block identifier 48584505 |
1,000,000,000 | 998,499,900 | 100 | 1,500,000 |
Current 2026-09-05T23:13:17.671Z, Base block 50930325 |
1,000,000,000 | 998,499,900 | 100 | 1,500,000 |
The September observation separately records the included LP / operations balance; unchanged headline balances do not make the two observations interchangeable.
Historical records
The full prior data room is preserved at historical data room. Historical application timeframes and market values must not be relabeled current.