uniswap-v4-hooks

To implement Uniswap v4 hooks securely, use audited code templates for functions like beforeSwap and afterSwap, and follow best practices for access control, router verification, and delta accounting to prevent exploits.

Common Uniswap v4 hook vulnerabilities include delta accounting errors, overflow risks, incorrect sender identification, NoOp rug pulls, and reentrancy issues that exploit incorrect access control or router verification.

Delta accounting in Uniswap v4 PoolManager hooks tracks token flow differences during execution. Secure development requires precise delta handling to ensure all balance changes settle correctly before the transaction completes.

Yes, you can create a dynamic fee hook for Uniswap v4. The Skill provides secure templates for hook functionalities and warns about potential reentrancy issues when implementing the beforeSwap function.

Router verification is needed in Uniswap v4 hooks whenever external calls trigger pool operations. Correctly identifying the sender prevents unauthorized access and protects against dangerous patterns like NoOp rug pulls.

An afterSwap hook fails access control checks if it lacks proper router verification or incorrect sender identification. Implementing secure code templates with strict access control prevents these authorization failures.