V4 Hook Fee Conformance

Recomputes a Uniswap v4 pool’s per-swap fee from v4-core’s own fee rules at the pinned commit a7cf038cd568801a79a9b4cf92cd5b52c95c8585 (ProtocolFeeLibrary.calculateSwapFee: protocolFee + lpFee − protocolFee·lpFee/1,000,000; Pool.sol’s protocol-fee-zero pass-through and MAX_SWAP_FEE boundary; LPFeeLibrary’s 0x400000 override flag, 0x800000 dynamic flag and MAX_LP_FEE 1,000,000) and checks each swap’s emitted fee against that recomposition. A mismatch means the declared fee story does not explain what the pool charged. The declared hook charge is accrued in integer arithmetic with every remainder reported, and LP revenue is reported separately, never netted against it. Evidence only, zero network.

Policy Mandate Export Compliance Control compliance_control Proof deferred

🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data: use synthetic or anonymised inputs only.

Protocol fee (uint24, both directions packed as v4 stores it: low 12 bits zeroForOne, bits 12–23 oneForZero; each direction ≤ 1000 pips)

Pool fee (uint24: static pips, or 0x800000 = 8388608 for a dynamic-fee pool)

Declared total fee cap in pips (optional; swap fee + hook charge is checked against it)

Declared LP-fee bounds JSON { min_pips, max_pips } (0..1000000)

Declared hook charge JSON { rate_pips, splits: [{ recipient_label, share_bps }] } (shares are reported as declared; a sum ≠ 10000 bps is flagged, never coerced)

Swaps JSON array: [{ index, zero_for_one, amount_in, emitted_fee_pips, lp_fee_override? (raw uint24 incl. the 0x400000 flag), exact_out? }]

Result

Run the AINumbers MCP tool `check_v4_hook_fee_conformance`. Task: Recompute a Uniswap v4 pool’s per-swap fee from v4-core’s own rules at pinned a7cf038cd568801a79a9b4cf92cd5b52c95c8585 (calculateSwapFee composition), validates the packed protocol fee and LP-fee bounds, decodes the 0x400000 override, and checks each emitted fee: CONFORMS, OUT_OF_BOUNDS, FEE_MISMATCH, or INDETERMINATE. Call it with arguments: {"policy_parameters":{"protocol_fee":0,"pool_fee":3000,"declared_lp_fee_bounds":{"min_pips":0,"max_pips":1000000},"declared_hook_charge":{"rate_pips":500,"splits":[{"recipient_label":"treasury","share_bps":10000}]},"swaps":[{"index":0,"zero_for_one":true,"amount_in":1000000,"emitted_fee_pips":3000}]}} Verify before trusting: call `verify_execution_hash` on mcp.ainumbers.co (https://mcp.ainumbers.co/mcp) with the parameter `claimed_hash` set to the returned `execution_hash`, passing the full artifact the run returned (the object containing `policy_parameters` + `output_payload` + `execution_hash`; equivalently `policy_parameters` + `output_payload` with `claimed_hash`), not the bare hash string, or re-run the in-page WebMCP tool `check_v4_hook_fee_conformance`. Return the ledger link https://ledger.ainumbers.co/ so a human can re-verify without contacting us. PII rule: All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only. Open the tool with the sample prefilled: https://ainumbers.co/chaingraph/art-709-v4-hook-fee-conformance.html#p=v1.H4sIAAAAAAAA_wEYAef-eyJwcm90b2NvbF9mZWUiOjAsInBvb2xfZmVlIjozMDAwLCJkZWNsYXJlZF9scF9mZWVfYm91bmRzIjp7Im1pbl9waXBzIjowLCJtYXhfcGlwcyI6MTAwMDAwMH0sImRlY2xhcmVkX2hvb2tfY2hhcmdlIjp7InJhdGVfcGlwcyI6NTAwLCJzcGxpdHMiOlt7InJlY2lwaWVudF9sYWJlbCI6InRyZWFzdXJ5Iiwic2hhcmVfYnBzIjoxMDAwMH1dfSwic3dhcHMiOlt7ImluZGV4IjowLCJ6ZXJvX2Zvcl9vbmUiOnRydWUsImFtb3VudF9pbiI6MTAwMDAwMCwiZW1pdHRlZF9mZWVfcGlwcyI6MzAwMH1dfUKmbhcYAQAA

V4 Hook Fee Conformance

Ask your agent