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
Attempting to use util/getLogs to get the logs of an event with a tuple in it's ABI will always yield no logs due to the wrong topic string being inferred from the ABI.
Attempting to use
util/getLogs
to get the logs of an event with a tuple in it's ABI will always yield no logs due to the wrong topic string being inferred from the ABI.Example code:
This is due to a bug in the following internal function
This function yields an incorrect topic string for ABIs with tuples in their signature.
expected:
0x40cdf7952f1870062f22e699acb978b97d3f41f739aa8b64d3b74c3f10654f83
actual:
0x49fa5e352a6e224cc24f6a14d90e9573aad1b2f8e0233e04d69baa5596af1371
See 'MatchConfirmed' event here: https://arbiscan.io/address/0xa40Ad3916237fa0FE11A500241fFA6eAc59CBD6A#events
The text was updated successfully, but these errors were encountered: