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 submitting a transaction that is executed by either the init or handle function in a smart contract, when events are emitted, attributes are duplicated. This happens for all event types except message. This only happens during smart contract transactions. No dup events are produced when calling blockchain modules directly via RPC or CLI.
It can be seen that the attributes have been duplicated for both our custom blockchain module (type name_bound), as well as those attributes emitted by the integration test smart contract (type wasm).
The text was updated successfully, but these errors were encountered:
It seems that with the release of wasmd v0.16.0, we're no longer seeing dup events in Provenance for our smart contracts. Unsure if this is related to our updates or wasmd updates, but it seems this is no longer an issue. Feel free to close unless you'd like to investigate further.
Problem
When submitting a transaction that is executed by either the
init
orhandle
function in a smart contract, when events are emitted, attributes are duplicated. This happens for all event types exceptmessage
. This only happens during smart contract transactions. No dup events are produced when calling blockchain modules directly via RPC or CLI.wasmd version = v0.15.1 ; See here
Example
See here as an example of the steps to demonstrate this issue.
Simply storing then instantiating the above integration test contract will produce the following output.
It can be seen that the attributes have been duplicated for both our custom blockchain module (type
name_bound
), as well as those attributes emitted by the integration test smart contract (typewasm
).The text was updated successfully, but these errors were encountered: