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
We may return many events with the same type and want to return them all.
For example, if the user sends tokens to an contract, and the contract sends tokens to a 3rd party, there will be 2 bank sends with the same message type. Once upon a time (launchpad) these ended up merged together and a client app would no have access to both events. This also affects when one contract calls a sub-contract, and those other calls get hidden.
Let's investigate the current situation of event merging in the path from contract/handler to external client (over tendermint rpc). Also what is left when we search for events in tendermint.
Then we can propose possible changes to the sdk or to our internal handling of events/attributes
The text was updated successfully, but these errors were encountered:
We may return many events with the same type and want to return them all.
For example, if the user sends tokens to an contract, and the contract sends tokens to a 3rd party, there will be 2 bank sends with the same message type. Once upon a time (launchpad) these ended up merged together and a client app would no have access to both events. This also affects when one contract calls a sub-contract, and those other calls get hidden.
Let's investigate the current situation of event merging in the path from contract/handler to external client (over tendermint rpc). Also what is left when we search for events in tendermint.
Then we can propose possible changes to the sdk or to our internal handling of events/attributes
The text was updated successfully, but these errors were encountered: