This swap · capturing
7.40 bp
Captures 24 ticks of drift. Charged a share of what it picks off.
$0.00
Why this fee
Signed drift against the cached reference
+24
ticks · 1 tick = 1 bp
drift simulated · this swap pays 0 WETH in fees
Same block, same pool
This swap · capturing
7.40 bp
Captures 24 ticks of drift. Charged a share of what it picks off.
Opposite direction
2.60 bp
Moves away from the reference, captures nothing, quoted at the floor.
Spread of 4.80 bp between two swaps a volatility-driven hook would quote identically. Both figures above are computed from the drift the hook itself reports. test/integration/DynamicPricing.t.sol pins the property on chain: in one block, against one reference, the swap capturing the drift is quoted strictly higher than the swap adding to it.
drift simulated — pool not read yet
Execution path
1 hop · v4 singleton
Both ticks are read from the deployed hook's own state. Their difference, signed by the direction of this swap, is the entire input to the fee above.
Hook events, this pool
preview, not fetched
These are the real event signatures from IAssayEvents.sol, populated with the quote above — a preview of what this swap would emit, not a log fetched from the chain. Every SwapAssayed event the pool has actually emitted is read from the chain and listed on the markets page. sender is the router, never the trader.