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
When indexing non-primitive, custom types in a log event, is the rust binding that is generated in the topic the abi encoded hash for the custom type? I'm looking at the Initialize log in the v4 contracts. The indexed Currency type is an address but the rust binding is declaring it a FixedBytes<32>.
I am generating the bindings using foundry with the v4 contracts as git submodule working on rev e74c9bbd42fe0fb1c20e2560e72d5c2e62fb45f1.
Component
primitives, sol-types
What version of Alloy are you on?
0.7.2
Operating System
macOS (Apple Silicon)
Describe the bug
When indexing non-primitive, custom types in a log event, is the rust binding that is generated in the topic the abi encoded hash for the custom type? I'm looking at the Initialize log in the v4 contracts. The indexed
Currency
type is anaddress
but the rust binding is declaring it aFixedBytes<32>
.I am generating the bindings using foundry with the v4 contracts as git submodule working on rev
e74c9bbd42fe0fb1c20e2560e72d5c2e62fb45f1
.generated bindings:
The text was updated successfully, but these errors were encountered: