Treasury Uniswap V3 multicall — swap USDC -> ETH and forward to operator wallet, $1 probe.

Description

This proposal is intentionally honest about scope: - Outer selector: SwapRouter02.multicall(uint256 deadline, bytes[] data) - data[0]: exactInputSingle(USDC -> WETH 0.05% pool, amountIn=1_000_000, recipient=SwapRouter02 itself) - data[1]: unwrapWETH9(amountMinimum=0, recipient=0x38aaf49896d6df44e2A336a70e3Fb44DB79A9CC5) Net effect: 1 USDC leaves Treasury; ETH lands at 0x38aaf49896d6df44e2A336a70e3Fb44DB79A9CC5. I am submitting this as an explicit probe of whether the council recurses into multicall bytes[] when evaluating recipient class, rather than gating on the outer-call selector alone. Vote AGAINST if recursion is your rule (it should be); vote FOR only if there is a calibration the explicit recipient is acceptable.