You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 26, 2024. It is now read-only.
The web3_sha3 RPC method is supposed to accept a hex-encoded string for the data to hash. So for instance, to get the Keccak hash of Move(string,string,string,uint256,uint256,address,uint256,address) (for a Solidity event topic), the call should be:
This call returns the expected value of 0x1241ca91bf224e988427ae79840cc9e3a02fa0579a3bd3fffc1f5c363192a873 for me with a real geth instance (version 1.10.8) as well as the old ganache-cli (version 6.12.2).
However, with the new ganache in development, I get 0xfb003308ec3db2d4f5b4afd507e20a6405153cdacffdee04022877e29465e778. I do get the correct result if I pass in the string directly, i.e.
From what I can see in the code this is kind of "intended". However, isn't this a bug, as ganache should follow the RPC spec and be consistent with the behaviour of other clients (like geth)?
The text was updated successfully, but these errors were encountered:
The
web3_sha3
RPC method is supposed to accept a hex-encoded string for the data to hash. So for instance, to get the Keccak hash ofMove(string,string,string,uint256,uint256,address,uint256,address)
(for a Solidity event topic), the call should be:This call returns the expected value of
0x1241ca91bf224e988427ae79840cc9e3a02fa0579a3bd3fffc1f5c363192a873
for me with a real geth instance (version 1.10.8) as well as the oldganache-cli
(version 6.12.2).However, with the new
ganache
in development, I get0xfb003308ec3db2d4f5b4afd507e20a6405153cdacffdee04022877e29465e778
. I do get the correct result if I pass in the string directly, i.e.From what I can see in the code this is kind of "intended". However, isn't this a bug, as
ganache
should follow the RPC spec and be consistent with the behaviour of other clients (like geth)?The text was updated successfully, but these errors were encountered: