IMD settlement pool depth and oracle check. Context: weekly cash-settled contracts on IMD (0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7) that settle each expiry from one IMD oracle answer. Read-only research: do not trade, deploy or pay for anything. Answer each part with numbers, the block number you read at, and how you got them.

PART A - SETTLEMENT POOL DEPTH. The settlement pool is Uniswap v4 pool id 0xb07d640fd9e2eb9dc81b953c8e4fd006bdfeaf276010fb5418eb763ca15abfb3 (ETH/IMD, POOL4 hook) on PoolManager 0x000000000004444c5dc75cb358380d2e3de08a90, Ethereum mainnet.

1. Identify the hook contract, the pool fee and tick spacing, and describe exactly what the hook does on buys and on sells (sell burn, trims, any liquidity it places below or above the price). Cite the verified source or the transactions you read.
2. Read the liquidity distribution by tick. Report active liquidity at the current tick, and how much ETH and IMD sits within +/-5%, +/-10% and +/-20% of the current price. State whether the liquidity is full-range or concentrated.
3. Using that distribution, the pool fee and the hook's behaviour, compute the ETH needed to push the price up 10% and 20%, and the IMD needed to push it down 10% and 20%, in a single swap.

PART B - COST OF HOLDING A MOVED PRICE. Settlement uses the univ4-spot recipe: the median of 61 evenly spaced samples of this pool over a fixed window of about 300 blocks (one hour) ending 5 blocks before the request. 4. List the other IMD pools that arbitrage against this one (at least v4 0x4158...a704, v4 0x8a40...a128, v3 IMD/USDC 0x894d4e6d3d2abc64fc0de0e4e2ea63a93bc9c520, v3 IMD/USDT 0xf0262866f9e0588f67d1a7936726fab0a75bb1a6) with their liquidity, and how quickly arbitrage closed price gaps between them over the last 7 days (look at swaps after large trades). 5. Estimate the total cost (fees, hook burns, arbitrage losses) for one actor to keep the settlement pool at least 10% above or below fair price for 31 of the 61 samples. Give a low and high estimate and your assumptions. 6. Recommend a maximum open interest per weekly expiry, in IMD, such that a 10% manipulation is unprofitable with a 2x safety margin. Show the arithmetic.

PART C - ORACLE FEASIBILITY. Use https://imd.fun/docs/ and GET https://api.imd.fun/requests/capabilities. 7. Can a contract on Sepolia (11155111) call the Intake's requestWithFailure with an oracle body whose chainId is 1 and whose evidence is chain, reading this mainnet pool? Note the testnet_only refusal reason and what triggers it. If not, what is the best way to test end to end before mainnet? 8. The same question for a contract on Robinhood Chain (4663) asking about this Ethereum pool. Can such a contract pin a fixed {fromBlock,toBlock} Ethereum window, and what can it verify about the attested window? 9. Confirm a body with answerType uint256, evidence chain, toleranceBps 0, panelSize 5, quorum 5 and a univ4-spot median definition passes POST /requests/check (a free check; include the exact body you checked and the response). 10. Find two or three recent attested univ4-spot requests on this pool in GET https://api.imd.fun/oracle/requests and report how long each took from creation to attestation, and whether any for this pool ended disagreed or failed.

Finish with a one-paragraph verdict: is a 5,000 IMD per-expiry cap safe, too tight or too loose, and is the oracle path workable on Ethereum mainnet, Robinhood Chain and Sepolia.