Listing Data Room

The canonical source for everything submitted to a listing surface — token facts, links, copy, logos, proofs. Anyone preparing a submission pulls from this file. Nothing here is private; this file is safe to commit. Private materials (audit engagement letters, legal memos, KYC docs, market-maker contracts) are tracked by reference, never pasted.

Companion docs: LISTING-READINESS.md, PLATFORM-LISTING-TRACKER.md.

Update rule: any field that becomes stale must be marked <stale: reason> and a fresh value written below. Never overwrite history silently.

1. Token Facts (verbatim from chain)

Supply schedule

• 1,000,000,000 HORMUZ minted once at deployment to the treasury wallet.
• No further mint capacity exists in the contract.
• No vesting contract is in place at this time; if vesting is later introduced for marketing / community / liquidity allocations, link the vesting contract here and explain the change.
• The current attested circulating supply is 1,500,000 HORMUZ at Base block 48584505: total supply minus E1 treasury 998,499,900 minus E2 deployer 100. The live LP wallet is included in circulation.
• Circulating supply must be re-attested on-chain within 24 hours of a listing submission and recorded as a static snapshot with reproducible inputs.

2. Official Links

Social handles must be identical across networks (@hormuz-style) and registered before any listing submission. Track:

3. Logo Assets

Visual assets used in submissions. The final icon is non-geopolitical and transparent, is generated from the committed raster master at brand/logo/hormuz-mark-master.png, and is live at the stable URLs below. Production bytes were reverified on 2026-07-15 and must still be checked again immediately before each later submission.

Logo rules:

• 1:1 aspect ratio, fully transparent background.
• No drop shadows. No gradient backgrounds outside the mark.
• No exchange logos or third-party marks composited in.
• Visual matches the site header at hormuz.meme.

4. Descriptions (Copy)

These are the only approved descriptions for submission. Do not improvise on a platform form. Compliance: must not imply yield, profit, redemption, peg, rebate, inflation protection, or risk-free status. See MARKETING-RULES.md and DISCLAIMER.md.

One-line description (≤ 140 chars)

HORMUZ is a fixed-supply ERC-20 meme token on Base. No mint, no tax, no admin. Not a stablecoin. No yield, peg, or redemption.

Short description (≤ 300 chars)

HORMUZ is a fixed-supply (1,000,000,000) ERC-20 meme token on Base mainnet. The contract is immutable: no mint, no transfer tax, no pause, no blacklist, no admin keys. HORMUZ is not a stablecoin and has no peg, redemption right, reserve claim, or yield mechanism.

Standard description (≤ 1000 chars)

HORMUZ is a meme token deployed on Base mainnet as a standard, immutable ERC-20. Total supply is fixed at 1,000,000,000 HORMUZ, minted once at deployment with no further mint capacity. The contract has no transfer tax, no pause function, no blacklist, no admin keys, and no upgrade path. Holders can burn their own tokens.

HORMUZ is not a stablecoin. There is no $1 peg, no reserve, no redemption right, no yield, no rebate, no inflation protection, and no guarantee of price or FDV. Trading HORMUZ is speculative and may result in total loss. Buyers are responsible for understanding their local regulations.

The official website is https://hormuz.meme and the contract is verified on BaseScan at 0xf912a4A0c374a33f192d0657719cE107194573F1.

Long description (1–2 paragraphs over the standard description)

Add platform-specific context (e.g., "available on Uniswap V3 HORMUZ/USDC pool on Base") only after the underlying fact is true and verifiable. Do not draft this in advance.

5. Required Submissions Materials by Platform

What each platform asks for, sourced from this data room. Cross-reference PLATFORM-LISTING-TRACKER.md for the official link.

Uniswap default-token-list PR

• Token-list JSON entry (chainId 8453, checksummed address, name, symbol, decimals 18, logoURI pointing to the 256×256 PNG hosted at a stable URL).
• 256×256 PNG.
• PR description: short description, BaseScan link, pool URL, volume snapshot, audit link (if any), tokenomics blurb.

DEX Screener Enhanced Token Info

• Logo (256×256 PNG).
• Short description.
• Website, X, Telegram, GitHub URLs.
• Contract address + BaseScan link.
• Wallet signature from deployer or admin address proving control. Treasury is on a Ledger; signing message will be performed at submission time, not earlier.

CoinGecko request

• 200×200 PNG logo (transparent).
• Contract address, chain (Base).
• Original description (use the standard description above).
• Total supply (1,000,000,000) + circulating supply snapshot with proof.
• Official website.
• Whitepaper URL or equivalent (a one-page "what is HORMUZ" doc is acceptable).
• Socials (must be live and active).
• Exchange/pair link (Uniswap V3 HORMUZ/USDC on Base).

CoinMarketCap request

• 200×200 PNG logo (transparent).
• Same description as CoinGecko, but rewritten in different words (do not copy-paste — both reviewers check).
• Contract, supply schedule (with on-chain proof for self-reported supply), socials, exchange/pair, BaseScan link.

Trust Wallet assets PR

• Folder: blockchains/base/assets/0xf912a4A0c374a33f192d0657719cE107194573F1/.
• logo.png — 256×256 PNG, lowercase extension.
• info.json:

{
  "name": "HORMUZ",
  "symbol": "HORMUZ",
  "type": "BASE",
  "decimals": 18,
  "website": "https://hormuz.meme",
  "description": "<short description>",
  "explorer": "https://basescan.org/address/0xf912a4A0c374a33f192d0657719cE107194573F1",
  "status": "active",
  "id": "0xf912a4A0c374a33f192d0657719cE107194573F1",
  "links": [
    { "name": "twitter", "url": "<paste>" },
    { "name": "telegram", "url": "<paste>" },
    { "name": "github", "url": "<paste>" }
  ]
}

• PR description: contract, BaseScan link, volume snapshot, holder count snapshot.

Tier-1 CEX (Kraken / Coinbase / Binance / Binance.US / Crypto.com)

• Whitepaper or one-pager.
• Audit report (full + summary).
• Legal memo summary (full memo held by counsel; only the summary travels with the application).
• Tokenomics doc with on-chain proof (treasury balance, vesting if any, circulating supply).
• Team KYC packet (held by counsel; the application notes that KYC is available on request).
• Corporate documents (certificate of incorporation, etc., if applicable).
• Market-maker contact (Kraken specifically requires this).
• Marketing plan covering the listing window.
• Volume + holder snapshots from the most recent 30 / 60 / 90 days.

Tier-2 CEX (Gate.io / Bybit)

• Same as Tier-1 plus the platform's specific KYC/AML attestation.

5c. Paste-ready submission packet (staged 2026-06-13 — submit only per each gate)

These are completed, paste-ready answers built from §1, §2, and §4. Staging ≠ submitting. Each block carries its own gate; do not file before the gate is met (CoinGecko/CMC = ~7d organic trading + a pre-submission sanctions re-screen per the counsel conditions). All copy obeys MARKETING-RULES.md: no yield/peg/redemption, no depth claim, no §10 geopolitical framing.

Pool-aware standard description (now true — pool is live)

HORMUZ is a meme token on Base mainnet, deployed as a standard, immutable ERC-20. Total supply is fixed at 1,000,000,000 HORMUZ, minted once at deployment with no further mint capacity. The contract has no transfer tax, no pause, no blacklist, no admin keys, and no upgrade path; holders can burn their own tokens. HORMUZ is tradable on a Uniswap V3 HORMUZ/USDC pool on Base.

HORMUZ is not a stablecoin. There is no $1 peg, no reserve, no redemption right, no yield, no rebate, no inflation protection, and no guarantee of price or FDV. Trading HORMUZ is speculative and may result in total loss. Buyers are responsible for understanding their local regulations.

Official website: https://hormuz.meme. Contract verified on BaseScan: 0xf912a4A0c374a33f192d0657719cE107194573F1.

CoinGecko request — field-by-field (gate: ~7d organic trading)

CoinMarketCap request — reworded description (do NOT reuse CG prose)

HORMUZ is a community meme asset issued on the Base network as a plain ERC-20. Its 1,000,000,000-token supply was created in full at launch and cannot be expanded — the deployed contract is non-upgradeable, with no tax on transfers, no freeze or blacklist controls, and no privileged owner functions. Any holder may permanently destroy their own balance.

It carries no monetary guarantees of any kind: HORMUZ is not pegged to a dollar or any asset, holds no reserves, confers no claim, redemption, or yield, and offers no protection against loss. It trades on a Uniswap V3 HORMUZ/USDC market on Base. Participation is purely speculative and can result in losing the entire amount spent. Holders are responsible for their own jurisdiction's rules.

Site: https://hormuz.meme · Contract (verified): 0xf912a4A0c374a33f192d0657719cE107194573F1

CMC also wants: contract, supply schedule with on-chain proof (§1 + attestation), socials, the Uniswap pair link above, and the BaseScan link.

DEX Screener Enhanced Token Info — field block (gate: pair indexed + owner payment)

Name:        HORMUZ
Symbol:      HORMUZ
Chain:       Base
Contract:    0xf912a4A0c374a33f192d0657719cE107194573F1
Logo:        256×256 transparent PNG (§3)
Description: HORMUZ is a fixed-supply (1,000,000,000) immutable ERC-20 meme token on
             Base. No mint, no tax, no admin keys. Not a stablecoin — no peg,
             redemption, or yield. Trading is speculative.
Website:     https://hormuz.meme
Twitter/X:   https://x.com/hormuzians
Telegram:    <Telegram URL>
Proof pack:  https://hormuz.meme/docs/

Proof-of-control signing note. DEX Screener's update flow requires a signature from the wallet it recognizes as the token's controller — normally the deployer 0xBabc8aB5847F2e4960F995b92dA6A0812F9Ba54c. At submission DEX Screener presents its own nonce/message in the browser; the owner connects the deployer wallet and signs that message (a plain personal-sign, no transaction, no value, no token approval). If the deployer wallet is not accepted, the fallback is the treasury Ledger as majority holder. Do not pre-sign anything; the message is generated at submission time. Confirm Ledger blind-signing is off — this is a readable personal-sign, not a blind transaction.

5b. Compliance, Treasury, Supply Packet (plan v2)

Plan v2 adds five pre-launch gates (G0-A → G0-E) and a strict separation of written quotes from planning estimates. The artifacts below are referenced from every CEX submission. Until a row has a status link, the corresponding gate is not satisfied.

Sanctions & adverse-media screening runs

G4-MICRO-LIVE — pool launch — 2026-06-13

This satisfies MARKETING-RULES §9: buy/trade CTAs are now permitted on public surfaces because the pool is recorded here and in DEPLOYMENTS.md. Aggregator/CEX submissions remain gated (own requirements + pre-submission re-screen per SANCTIONS-NAME-SCREENING.md §6.3).

Circulating supply attestation snapshots

Marketing-rule incidents

6. Current Source Proof Packet

Current source evidence as of 2026-07-15. Production URLs and final-logo bytes were reverified immediately before the DropsTab submission. Market values are observations, not guarantees, and must retain their observation date.

Historical snapshot — superseded

The dated G3 and G3.1 proof blocks below are retained for provenance. Their pre-launch state is not the current project status.

G3 publication status — 2026-06-08

Pending action — logo asset. tokenlist.json references https://hormuz.meme/logo-256.png. The 256×256 transparent PNG is not yet hosted in the repo at site/logo-256.png. Listing reviewers (Uniswap default list, Trust Wallet, CoinGecko) consume that exact URL. Owner action: drop the 256×256 PNG at site/logo-256.png (and the 200×200 at site/logo-200.png for aggregator submissions).

Pending action — owner deploy. All four new files exist in the repo. The Vercel routing at vercel.json will serve them at hormuz.meme/* once the owner deploys (push to the connected branch or vercel deploy). Until then, the URLs return 404 and the in-data-room rows above will not flip to 200.

Repo health at publication time. git diff --check clean. npm run preflight 46/46 passing (1 unrelated .env warning).

G3 production deployment — 2026-06-09

Live URL probes (curl)

Compliance posture at deployment

• G0-A status: REVIEW — unchanged by this deployment. Findings F1–F8 in SANCTIONS-NAME-SCREENING.md §6 are untouched.
• Counsel adjudication: pending. Open item from §6 of the screening file is still open.
• Manual interactive sanctions-list screenshots: pending. OFAC SDN form, UKSL search, EU FSF, and UN scsanctions verifications of contract / treasury / deployer remain unrun.
• Submissions: none. No request has been filed to CoinGecko, CoinMarketCap, Trust Wallet, Kraken, Coinbase, Gate.io, Bybit, Crypto.com, Binance, Robinhood, Revolut, or Upbit. G6 / G9 / G11 / G13 / G14 remain blocked.
• Live disclaimer. Both the Access Status panel on the home page and the dedicated Compliance & Affiliation Notice at /compliance.html carry the explicit non-affiliation list (IRGC, Persian Gulf Strait Authority, Iranian government entities, shipping authorities, maritime passage systems, toll schemes, vessel clearance, safe-passage payments, sanctions evasion, impersonation scams) and the REVIEW classification.

Known follow-ups

1. Owner to replace placeholder logos at site/logo-256.png and site/logo-200.png with the final branded mark before any aggregator submission. Aggregator reviewers consume the exact logoURI URL.
2. Owner to perform manual sanctions-list screenshots of contract / treasury / deployer at the four official sanctions-list portals, attach to §7 of this file.
3. Owner to confirm Google Search Console verification + sitemap submission per the indexing kit in G3-CONTROLLED-SURFACES.md.
4. Owner to push controlled-surface updates (X / Telegram / Farcaster / Reddit / GitHub README / BaseScan profile / ENS) using the ready-to-paste content in G3-CONTROLLED-SURFACES.md.

G3.1 — public proof pack — 2026-06-09T15:01:36Z

Goal of G3.1: publish the public-safe operating docs on hormuz.meme/docs so reviewers, crawlers, and community users do not depend on private GitHub links. Held-private docs stay local + git-ignored. GitHub repo stays private.

Live URL probes (curl)

Sitemap re-verified: all 8 docs URLs present in <urlset>.

Live content spot-checks: sanctions-name-screening.html contains 19 occurrences of "REVIEW" (classification preserved) and the F1–F8 finding rows. listing-readiness.html contains the G0-A → G15 gate ladder with held-private rows redacted via the canonical phrase. listing-data-room.html mirrors this file's public-safe content.

Held-private posture (unchanged)

• The 7 held-private operating docs (AUDIT-RFP, CEX-BUDGET-QUOTE-LOG, CEX-SUBMISSION-PACKET, ENTITY-FORMATION, LAUNCH-DAY-PLAYBOOK, LEGAL-MEMO-SCOPE, MM-SHORTLIST) remain on the local working tree only. None are tracked. .gitignore was extended to enforce this — git status --short no longer lists them.
• GitHub repository remains PRIVATE.
• Held-private docs are available to counsel, auditors, market makers, and listing venues under appropriate review; nowhere else.

Compliance posture (unchanged)

• G0-A status: REVIEW. Findings F1–F8 in SANCTIONS-NAME-SCREENING.md §6 are untouched and now publicly readable at https://hormuz.meme/docs/sanctions-name-screening.html.
• No liquidity. No Uniswap pool has been created. No HORMUZ trading is live.
• No submissions. No request has been filed to CoinGecko, CoinMarketCap, Trust Wallet, Kraken, Coinbase, Gate.io, Bybit, Crypto.com, Binance, Binance.US, Robinhood, Revolut, or Upbit. G6 / G9 / G11 / G13 / G14 remain blocked.
• Counsel adjudication: pending.
• Manual interactive sanctions-list screenshots: pending (OFAC SDN form, UKSL, EU FSF, UN scsanctions).

Original metric table

Each metric must include the as-of date and the link that lets a reviewer independently verify it. Snapshots that have aged out of relevance (older than 30 days at submission time) must be refreshed before submitting.

7. Private Materials (Tracked by Reference Only)

Do not paste contents of any of the following into this file. Track only that they exist and where they are held.

Historical snapshot — superseded

Browser verification log — 2026-06-08

This browser-driven verification pass is retained as dated provenance only. Its pre-launch observations are superseded by the current proof packet above. The session was scoped to verify and archive only — no accounts, forms, wallet signatures, or submissions.

Verified directly in browser

Blocked by Chrome safety filter

The following sites are blocked at the browser layer ("This site is not allowed due to safety restrictions") and were not verified live. The URLs in PLATFORM-LISTING-TRACKER.md remain the authoritative reference; they should be opened by an owner-driven browser session before any submission.

• support.coingecko.com (listing how-to article)
• www.coingecko.com (request form)
• coinmarketcap.com (request portal)
• www.coinbase.com (listings page)
• www.kraken.com (get-listed page)
• robinhood.com (coin availability article)

CEX listing portals (Binance, Binance.US, Crypto.com, Bybit, Gate, Upbit) and Revolut docs were not attempted in this session — based on the pattern above they are expected to be blocked as well.

Open follow-ups from this session

• When the owner opens the blocked URLs above, take screenshots and attach them to a fresh dated block beneath this section.
• After Uniswap pool creation, re-open BaseScan to confirm the first swap and pool address, then refresh the "Verified directly in browser" table.
• After hormuz.meme is updated with the "Access status" section, re-verify and link the on-site row to the relevant proof for each listing.

9. Versioning

• This file's history is git-tracked. Listing reviewers may ask for the commit hash at the time of submission — provide it, do not redact past values.
• The "stale" rule (top of file): mark <stale: reason> rather than overwriting. Listing teams sometimes ask why a supply number changed.
• When a row becomes verifiable (e.g., the pool exists, CoinGecko approves), record the value, the public link, and the date. Then update the corresponding row in PLATFORM-LISTING-TRACKER.md and the "Access status" section on hormuz.meme. All three move together.