see detailed information on how the predictive algorithm worked
the full access list (what was accessed)
how many steps did the algorithm take (how many batches of state needed to be fetch).
the actual code that was executed probably represented as a sequence of program counters and maybe the actual opcodes that were executed in what order.
the actual state and accounts that were identified as being needed (including which ones we already had, and which ones needed to be fetchd)
maybe even fancier meta data about how each piece of state was determined to be needed.
One goal here is to be able to run this continuously against transactions in mainnet blocks to examine real world transaction access patterns and see how well the tool performs against real world transactions.
@pipermerriam Now the JSON-RPC, three execution modes and detailed information output are supported. The parameters may be different, please check the examples in README.
Here's what I'd like to be able to do with your tool.
$ ./predict old-tx 0x<tx-hash>
from/to/value/data
$ ./predict new-tx --from ... --to ... --value ... --data ...
$ ./predict execute --code --from ... --to ... --value ... --data ...
One goal here is to be able to run this continuously against transactions in mainnet blocks to examine real world transaction access patterns and see how well the tool performs against real world transactions.