Open s8sato opened 1 week ago
atm one might listen to events in the order of execution since it's sequential. But in the future the order of multiple transactions can get intertwined. Proper solution would be to add transaction hash into a data event as is suggested
In some use cases they want to watch changes to a particular entity and inspect the transaction that caused the changes. Any ideas to achieve this, other than the issue title?