Cosmos-sdk: Simulation transaction number

[rigelrozanski]

It may be useful to build out a simulation transaction number index and start referring to it throughout logging etc. Beyond communication, this could be useful for future simulation features such as isolating out transaction subsets which can still produce errors etc.

[cwgoes]

As in a monotonically increasing index? What would you want the tooling to do exactly?

[rigelrozanski]

yes, an index which increases with each transaction independent of block height

This is intended to be used with few other ideas for the simulation:

• run _up-to_ a transaction on-top a particular state
• re-run user-specified a transaction on-top a particular state (eg. run tx 100, 150, & 199 on the state formed from running the simulation to height 10)

This type of functionality could be further advanced isolate out specific transactions which when played together reproduce the bug.

For all of these types of more advanced functionality, having a transaction index could be useful.

[jackzampolin]

Looks like @fedekunze 's recent sim improvements covered this. Closing this issue.

[fedekunze]

Not entirely, we still need to assign a number to the operation itself. Should be fairly simple to implement tho