getPoolCoinByHash function not working ?

[AbhinavMV]

Requirement

i want to use a node call to get pool key information like currency0, currency1, fee, tickSpacing, hook information using pool id hash

Problem

the method getPoolCoinByHash provided on the hook contract on base chain (0xd61A675F8a0c67A73DC3B54FB7318B4D91409040) does not work ❌

Steps to reproduce

• this is valid poolHash on zora 0x93e1d72304ac86343afdb5ad346ce2d1cd9fae8d05e518a3f50259f1cb803932 , it was initialized in the transaction https://basescan.org/tx/0xa0030e458d4bf4ca161499215737fc9c1f729474aa61366ae5e5e5072e97c931#eventlog#92
• this method requires bytes23 input, converting the poolIdHash to bytes23 gives 0x93e1d72304ac86343afdb5ad346ce2d1cd9fae8d05e518
• And when i call the function with this input it returns the zero address https://basescan.org/address/0xd61A675F8a0c67A73DC3B54FB7318B4D91409040#readContract

Some Findings

• Since Zora uses hooks to integrate with unsiwapv4, the poolKeys function on uniswapV4 state view contract does not work

  /// @notice Mapping of pool keys to coins.
 mapping(bytes32 => IZoraV4CoinHook.PoolCoin) internal poolCoins;

    /// @inheritdoc IZoraV4CoinHook
 function getPoolCoinByHash(bytes23 poolKeyHash) external view returns (IZoraV4CoinHook.PoolCoin memory) {
        return poolCoins[poolKeyHash];
 }

• i checked the code on BaseZoraV4CoinHook.sol, in above code taken from the contract if you see, the key of the map (poolCoins) is of type bytes32 but in the function the input is of bytes23, is that a typo or something ? (Have little knowledge about solidity, so sorry if this dumb question 😅)

Could someone please help understand what i am doing wrong ? 🤔

[iainnash]

Hi! Good catch, we fixed this bug in future versions of the protocol. The parameter was supposed to be bytes32 but there was a typo in earlier versions of coins we made.

For old tokens try using the getPoolCoin with all the parameters to make the hash -- that should work.
I can also draft an example of reading the storage slot directly but it is a little bit more complicated than the first approach.

[AbhinavMV]

For old tokens try using the getPoolCoin with all the parameters to make the hash -- that should work.

my requirement is to use the hash to get all parameters (currency0, currency1, tickSpacing) so this method won't work, so looks like there is no way to do this with current version :/

[iainnash]

There is off chain — maybe it can be added to the sdk?

…

On Thu, Aug 7, 2025 at 01:30 Abhinav MV ***@***.***> wrote: *AbhinavMV* left a comment (ourzora/zora-protocol#526) <#526 (comment)> For old tokens try using the getPoolCoin with all the parameters to make the hash -- that should work. my requirement is to use the hash to get all parameters (currency0, currency1, tickSpacing) so this method won't work, so looks like there is no way to do this with current version :/ — Reply to this email directly, view it on GitHub <#526 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGMCOHTQBNDP2PX2TIKNOT3MLP7TAVCNFSM6AAAAACDD7IR2WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCNRSGU2DMMJVGI> . You are receiving this because you commented.Message ID: ***@***.***>

[iainnash]

You can use the poolKey tuple to do this lookup on the zora hook from the zora initialized event in the receipt you shared at
https://basescan.org/tx/0xa0030e458d4bf4ca161499215737fc9c1f729474aa61366ae5e5e5072e97c931#eventlog#130

You can then call the getPoolCoin function with that data.

[iainnash]

Re-open the issue if this doesn't work.