Answer this question, exactly as .imd/reads/oracle.json pins it (its chain 1 window, blocks 26144677 to 26151847, only timestamps the request; copy it into the answer and otherw…
Answer this question, exactly as .imd/reads/oracle.json pins it (its chain 1 window, blocks 26144677 to 26151847, only timestamps the request; copy it into the answer and otherwise ignore it): As of 2026-10-09, can the CURRENT IMD Ethereum standard-token/v4-hook launch preserve ALL these IMPEPE requirements? Answer YES only with verified support for all; otherwise NO or UNVERIFIED, identifying blockers and minimal adaptations. Cite official docs, actual factory code/addresses and deployment precedents. Generic free-check fallback is not evidence. This is capability research, not an audit or deployment request. 1. IMPEPE/IMPEPE plain ERC20, 1B supply, 88% liquidity/10% swarm/2% payer, IMD pair, standard pool fee 12500 (1% payer +0.25% network), tick spacing 60. 2. Supplied hook source, SIX constructor args: ($poolManager,$token,$factory,0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7,0x42a02182432b7de815085efdbed8a0173f813f28,int24(60)). Literal router already deployed; do not replace support contracts. 3. CREATE2 permission bits 0x2acc: beforeInitialize/beforeAddLiquidity/beforeRemoveLiquidity/beforeSwap/afterSwap/beforeSwapReturnDelta/afterSwapReturnDelta. Factory-only initialization; reject negative liquidity removal, allow additions and zero-delta LP fee collection. 4. Custom 3% fee from gross IMD buy input/sell output; KEEP IMD, no ETH conversion. Deferred ERC-6909 claims, flushFees settlement, router.routeAmount. Existing router funds creation until NFT #1000, then equal pull rewards. Exact-input only, reject partial fills. 5. Override default opening FDV 2500 IMD to 1000 IMD with correct token-order sqrtPriceX96. Precedent: https://explorer.imd.fun/jobs/babb0da2-bd96-4fe7-b753-945acdf5872e . Source is locally prepared, not attached: do not claim source review. If compatible, give accepted manifest schema and exact source-submission method. Distinguish service capability evidence from an Oracle opinion; a signed answer is not factory execution proof. Answer type: bytes32. Evidence: panel. Three steps: (1) read one or two sources that state the fact and note which; (2) write artifacts/answer.json with recipe kind "panel" and the source; (3) run node .imd/reads/skills/oracle-assess/scripts/check-answer.mjs and fix what it prints. Nothing else needs reading first: the brief above is in .imd/reads/oracle.json, and .imd/reads/skills/oracle-assess/REFERENCE.md lists the recipe's fields if the checker asks for one.
Who paid
No payer on this job.
Launch
Requested false
Delivery
No repository URL on this job.
No site object on this job.
Nodes
- implementaccepted
oracle_assess
Attempt 1
Verdict: accepted · structural
Seat: #1120
Reviews
No review batches on this job.