Skip to content

Remove ignored hookData arg from initializePool call (#64)#94

Open
impetus82 wants to merge 1 commit into
Uniswap:mainfrom
impetus82:fix/initializepool-remove-hookdata-64
Open

Remove ignored hookData arg from initializePool call (#64)#94
impetus82 wants to merge 1 commit into
Uniswap:mainfrom
impetus82:fix/initializepool-remove-hookdata-64

Conversation

@impetus82

Copy link
Copy Markdown

Summary

Fixes #64. IPoolInitializer_v4.initializePool(PoolKey, uint160) takes two arguments, but script/01_CreatePoolAndAddLiquidity.s.sol encoded the initializePool call with a third hookData argument. Because abi.encodeWithSelector is variadic, the extra hookData (always new bytes(0) here) was silently appended to the calldata and ignored by the two-argument function — dead, misleading code that contradicts the interface and would confuse anyone setting a non-empty hookData expecting it to reach the pool.

Drop the trailing hookData argument so the encoded call matches the interface. hookData is still used correctly for the liquidity mint below.

(Note: the issue links the pre-rename path 01_CreatePoolAndMintLiquidity.s.sol; the file is now 01_CreatePoolAndAddLiquidity.s.sol.)

Closes #64

🤖 Generated with Claude Code

)

IPoolInitializer_v4.initializePool takes (PoolKey, uint160). The deploy script
passed a third `hookData` argument that is silently ABI-appended and ignored,
contradicting the interface and misleading developers who set a non-empty
hookData expecting it to reach the pool. Drop the trailing argument.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Clean up hookData on initializePool

1 participant