Better tracking of primitive origin #412
Description
Imagine you have an app that is monitoring two chains:
- main chain A
- other chain B
You want to create an application where, when a primitive gets triggered, you look up additional information. The question is, when you do the lookup, how do you know where the primitive came from?
Right now, we only track scheduledTxHash which gives you the transaction hash which triggered the primitive. Although you can get any data you need just from the transaction hash, it would be more convenient if you could also get other information about its origin.
Notably, one thing we can't get from just scheduledTxHash easy is the log index, (for EVM) which could be situationally useful (as noted by #415) because it allows you to create primary keys on tables that index log events (you can't use the EVM tx hash only, as one tx can emit multiple events). As a workaround for this, you can use the Paima tx hash as a primary key (it works, but not ideal)
This could also help for timers as well to know what triggered a timer