Uniswap Hooks

why is position represented with keccak256(owner+tickLower+tickUpper) when owner+tickLower+tickUpper fit inside bytes32? seems like this could work without keccak

Can we just all get along?
Somos todos macacos.
Viva la libertad carajo!

only thing I can think of is `abi.encodePacked` doesn't return a `bytes32` - it returns a dynamic `bytes` data type. keccak'ing it just makes sure the key is always a fixed size bytes32

haardik.dev | Founder @learnweb3 | lead instructor /uniswaphooks | building @openfarcaster

yeah, i cant seem to find any specific instances where it would make much difference either

also casting directly instead of keccak also saves about 40 gas it looks like

Yeah but bytes can be cast to bytes32 without keccak, so it must be something else

Also it doesnt have to be encodePacked it can be simple bit OR and bitshift left