HORMUZ.MEME  /  DOCS  /  LIQUIDITY OPERATIONS POLICY

Liquidity Operations Policy

LP-wallet rules, anti-manipulation commitments, no-wash-trading policy.

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

Draft for owner + counsel review — not legal advice. Operational rules governing the LP wallet, market-making bounds, and anti-manipulation commitments. See DISCLAIMER.md.

DEX Screener flags pools with suspicious patterns. CMC explicitly polices artificial trading. CEX listing teams ask whether a project wash-trades. This document is the project's affirmative, public-facing answer.

Companion docs: LIQUIDITY-PLAN.md, LIQUIDITY-CHECKLIST.md, TREASURY-DISTRIBUTION-POLICY.md, CIRCULATING-SUPPLY-ATTESTATION.md, LISTING-DATA-ROOM.md. (MM diligence is tracked separately in an internal operating document, not public; available to counsel, auditors, market makers, and listing venues under appropriate review.)

Gate: G0-D. Status: draft.


1. LP wallet rules

Rule Reason
The LP wallet is a separate hot wallet, never the Ledger treasury. Limits blast radius if a launch-time hot key is compromised; matches LIQUIDITY-CHECKLIST.md.
The LP wallet receives only the HORMUZ and USDC required for the approved pool seeding, and only at the time of seeding. Prevents pre-launch leakage and front-running.
LP wallet address is published at the time of pool creation, in DEPLOYMENTS.md and at hormuz.meme/docs/tokenomics.html. Reviewers can trace it.
LP wallet does not perform any swap, sandwich, or arbitrage on the HORMUZ/USDC pair. Removes any wash-trade implication.
LP-position NFT remains in the LP wallet (or, if locked, in the lock contract). It is never transferred to a personal hot wallet. Reviewer-auditable.
Removal of liquidity (full or partial) is a documented decision, logged in this file's §6 and announced publicly with the on-chain transaction hash. Reviewers can distinguish operational rebalances from rugs.

2. Initial liquidity gate (owner-set, internal)

The dollar value of initial USDC depth and the corresponding HORMUZ amount are an internal decision, owner-set, recorded in LIQUIDITY-CHECKLIST.md Manual Confirmation block at the time of G4 approval. This document does not publish a fixed threshold:

Internal floor for routine consideration: "depth that supports a credible early-trader experience without immediate slippage-related rejection by aggregators or wallet trackers". The figure itself stays in the checklist, not here.

3. Anti-sniper measures

Measure Mechanic
Tight-range initial position The first liquidity is concentrated around the seed price for the first ~100 blocks to absorb the inevitable sniper auction at a known price. A wider, full-range position is added immediately after.
No on-chain whitelist or blacklist Contract has none; no anti-sniper "modifier" exists. The pool is permissionless.
Public pre-announcement window The pool block range is communicated to the community within a 15-minute window (not an exact block) so retail is not outrun by silence.
No buyback of sniper bags The project will not buy back from any wallet that accumulated supply at launch. This is non-negotiable; buybacks of that kind read as supply manipulation.
LP-lock decision The project decides at G4 whether the LP-position NFT is locked via a reputable lock service (e.g., UNCX) for a stated period. If unlocked, the rationale is documented here.

4. Market-maker bounds

When and only when an MM is engaged under G10, the following are contractual minimums. These are enforceable in writing, not aspirational.

Term Required
Engagement model Vested-token model preferred. Loan model only with explicit collateral and recall conditions; subject to extra counsel review.
Wash-trading clause Explicit prohibition. Breach is a termination event with token recall.
Self-dealing clause MM may not market-make against an unlisted personal position in HORMUZ.
Transparency Monthly written report listing aggregate volume facilitated, average spread, and any incidents. Stored in LISTING-DATA-ROOM.md §6.
Conflict disclosure MM declares any other HORMUZ-related engagement (LP, treasury advisory, paid promotion) at signing and at each monthly report.
Counsel red-line The contract is reviewed by project counsel before signing.
Acceptable venues MM is bound to specific named venues; cannot self-extend coverage.
Exit Either party can exit with a stated notice period; token recall is mechanical, not discretionary.

If a candidate MM will not accept these clauses, that candidate is dropped.

5. Anti-manipulation commitments

The project commits, in writing on this page, that it will not:

  1. Wash-trade HORMUZ — including via a single party trading on both sides of the pool, via off-chain "trading clubs", or via paid volume providers.
  2. Pay any KOL, influencer, or partner per-trade, per-volume, or per-price-target.
  3. Distribute HORMUZ to wallets without prior, recorded consent (no spam airdrops).
  4. Run an undisclosed buyback program.
  5. Coordinate buy-pressure ahead of any aggregator submission or CEX conversation.
  6. Lend treasury tokens to anyone under undisclosed terms.
  7. Mark any pool action as "burn" that is not, in fact, a burn (i.e., not a transfer to 0x000…dead or a _burn call).

Any breach is a documented incident in §6 and is disclosed to active CEX counterparties within 48 hours.

6. Operations log

Every pool-touching action goes here. Append-only.

Date Action Address(es) Amount(s) Tx hash Rationale
2026-06-13 G4-MICRO-LIVE seed LP 0x7991…d2bB → pool 0x20c4…8674 ~1,499 USDC + ~1,498,995 HORMUZ see DEPLOYMENTS.md Initial micro-pool
pending G4-DEEPEN Treasury → LP HORMUZ 0x8a5D…0f7F0x7991…d2bB TBD (checklist) Deepen per runbook 05
pending G4-DEEPEN Increase LP on same pool LP → pool 0x20c4…8674 TBD USDC + HORMUZ Deepen per runbook 05

7. Status

Field Value
Gate G0-D
Authored 2026-06-08
LP wallet 0x799140699e802Ac48624bd90A84afe14cfCFd2bB (live)
MM engaged none
Status DRAFT — G4-MICRO-LIVE executed; G4-DEEPEN pending owner amounts

Last updated: 2026-07-15. This page mirrors the public-safe operating doc tracked at LIQUIDITY-OPERATIONS-POLICY.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.