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
The naming of the storage structure affects event identifiers.
It means that if users are implementing the same interface, events provided by them can have different identifiers(and topics of this event too) in case of the different storage struct naming.
The solution for this can be: during the definition of events set the name of the trait which will emit these events. In this case, if users implement the IErc20 trait, events emitted by them will have the same identifiers.
But this solutions is not possible at the moment for 2 reasons:
We can't define events during trait definition. It is described here
Event doesn't allow to customize ident of storage struct/trait. But it can be easily integrated.
The naming of the storage structure affects event identifiers.
It means that if users are implementing the same interface, events provided by them can have different identifiers(and topics of this event too) in case of the different storage struct naming.
The solution for this can be: during the definition of events set the name of the trait which will emit these events. In this case, if users implement the IErc20 trait, events emitted by them will have the same identifiers.
But this solutions is not possible at the moment for 2 reasons:
Also it can be part of use-ink/ink#564
The text was updated successfully, but these errors were encountered: