video1.0<iframe src="https://www.loom.com/embed/4a40fa663c9d425da94f9ee9726d0fb9" frameborder="0" width="1280" height="960" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>9601280Loomhttps://www.loom.com9601280https://cdn.loom.com/sessions/thumbnails/4a40fa663c9d425da94f9ee9726d0fb9-7375b47856e9e269.gif235.266This Loom explains Standby, a mechanism to protect future Uniswap V4 execution capacity without reserving liquidity. It defines supporting capacity S and obligation O, maintaining an invariant that supporting capacity must always be at least as large as the obligation while normal pool use continues. The example starts with 80,000 USDC supporting capacity and no obligation, then admits a 50,000 USDC capacity commitment, leaving supporting capacity at 80,000 with a 50,000 entitlement. A 15,000 USDC request reduces supporting capacity to 65,000 while keeping the 50,000 obligation valid, but a further 20,000 request would drop supporting capacity to 45,000 and is rejected since it would break the commitment. The beneficiary later executes the protected 50,000 capacity along the actual Uniswap V4 path, and the pool manager delivers exactly 50,000 USDC.