CODE AND TESTS ONLY; no public deployment or live-site publication.

Continue from job 80e9b1d1-bc63-4665-89e1-4bfb05777f0a and repository:

https://github.com/identity-md-launches/launch-1838-uniswap-v4-hook-code

Accepted commit: 3939f319d67dcd92eb50b057c0c13754ccb6b35c

Reconcile newer accepted work and preserve history. Deliver implementation, regression tests and the published commit, not just a design proposal.

AUTHORIZED DESIGN: ONE-WAY UNLOCK GATES

Each FDV milestone is a door that opens once for everyone and never closes. A valid instantaneous official-pool price touching or exceeding a threshold is sufficient. No sustained UNLK price, UNLK TWAP, confirmation duration, sequential waiting period or final-unlock delay is required. This supersedes those previous requirements.

A short-lived price spike may open gates. Selling immediately after a gate opens is intended behavior, even if selling lowers the price again. The requester accepts this economic consequence, including permanent full unlock after a valid $50M touch. Document it clearly; do not claim manipulation resistance.

PRESERVE THE EXISTING CUMULATIVE ACCOUNTING

E = cumulative eligible acquisitions under the existing authenticated accounting model.

S = cumulative executed official-pool sales.

Before final unlock: Q = max(0, floor(E * p / 10000) - S).

A sale q must satisfy S + q <= floor(E * p / 10000), then increase S by the actual executed sale amount.

Example: E=1000, p=20%, S=0 permits 200 sold. Afterwards S=200 and the wallet may hold 800. At 30%, total entitlement becomes 300, so only 100 MORE may be sold. Do not calculate 30% of the remaining 800. Opening gates must never reset S, restore consumed quota or credit E.

Preserve existing buy-credit maturity, authenticated payer/reward credits, deduplication, fee accounting and identity rules. Transfers, donations and liquidity operations create no quota rights. Native claims remain independent of synchronization.

UNCHANGED GATES

Initially 20%.

$100K:25%; $250K:30%; $500K:35%; $1M:40%;

$2M:45%; $3.5M:50%; $5M:55%; $7.5M:60%;

$10M:65%; $15M:70%; $20M:75%; $25M:80%;

$30M:85%; $35M:90%; $40M:95%.

At $50M: permanently bypass quota checks for ALL holders, including transfer-only recipients with E=0. Setting p=10000 alone is insufficient.

Advance directly to the highest crossed threshold. A jump across several targets opens all corresponding gates without separate transactions or waiting. Price declines never reduce rights.

VERIFIED PRICE AND EXECUTION ORDER

FDV = fixed 1-billion supply * official UNLK/IMD pool spot price * valid IMD/USD reference.

Replace temporal filtering of the UNLK price/gate progression with instantaneous price evaluation. Keep the previously implemented no-subscription IMD/USD reference and its validation separate: this authorization does not silently remove its freshness, history or external-market checks. Explain the remaining reference latency and operating gas requirements.

Use actual PoolManager state for the exact bound official PoolKey, correct currency ordering/decimals and overflow-safe math. No user-supplied price, website API, arbitrary pool, fabricated history or admin override.

Evaluate gates automatically on successful official-pool swaps using the executed post-swap price, and provide a permissionless current-state checkpoint. Preserve the highest valid threshold observed at swap boundaries, including multiple swaps in one transaction. A reverted transaction leaves no new gates, credits or sales behind.

Specify and test ordering: use the already-open gate to validate a sale; a sale cannot use its own post-swap update retroactively to justify an otherwise excessive sale. A successful earlier buy/checkpoint may open a gate usable by a later sale, including in the same transaction subject to unchanged credit maturity.

Invalid reference data must prevent NEW gate advancement only. Existing unlocked rights, within-quota trading, transfers and native claims remain available. Do not claim to detect historical price touches that the contract never observed.

PRESERVE EVERYTHING ELSE

Standard Uniswap router compatibility, 1B/18-decimal UNLOCK/UNLK, 10/87/3 allocation, official 1.25% fee, additional 0.75% IMD treasury fee, immutable beneficiary, principal protection, unrestricted transfers and native claims. No upgrades, pause, resets, exemptions or admin price/rule changes.

TEST AND DELIVER

Test the exact 1000/200/100 example, rounding, partial/full sales, additional acquisitions, price decline, repeated checkpoints, exact thresholds, multi-tier jumps, brief spikes, same-transaction buy/unlock/sell, reverted batches, maturity, invalid references and permanent final bypass for E=0 holders.

Update candidate UI explanations, ABI, deployment documentation and release artifacts; do not alter the live deployment configuration. Run full contract/frontend checks and report executed versus skipped checks.

Reassess earlier findings against this explicit economic design. Intended valid-price spike unlocking is accepted behavior, not a claimed security fix. Wrong-price attribution, broken accounting, external-reference attacks and shared-executor quota pooling remain separate findings; do not silently waive them.

Deliver GitHub commit, exact results and remaining release requirements. Request independent review; if none occurs, state pending. No claim that this code-only job updates immutable live contracts or makes deployment automatically safe. MAINNET HANDOFF IN THIS SAME TASK:

After implementing the changes, assess the exact final commit for an actual IMD mainnet UNLK/IMD launch. Verify current platform support and run a recorded-block fork rehearsal of factory deployment, companion setup, activation, standard-router buys/sells, fees, claims and milestone opening.

Deliver one consolidated GO/NO-GO report. For every remaining blocker, identify the exact failing check, required code change, platform operation or requester decision. Resolve issues within the authorized scope now; do not defer known implementation work to another paid task. Include reproducible deployment scripts and the concrete supported release steps. Do not broadcast mainnet transactions in this code-only task or present fork success as independent security approval.