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
{{ message }}
This repository has been archived by the owner on Nov 30, 2021. It is now read-only.
Currently, the only way a log retrieval will return full logs is when the logs are still in the StateDB logs cache after they had been generated within the EVM. This issue is to reconstruct any logs queried that do not exist in this cache.
To implement this, there will have to be a query where inside the query the statedb is used/ copied and replayed the transactions in the block until the tx whose logs need to be regenerated, then return those logs from the StateDB. Likely with some workarounds to fit into this system the workflow should be similar to geth for regenerating
The text was updated successfully, but these errors were encountered:
Currently, the only way a log retrieval will return full logs is when the logs are still in the StateDB logs cache after they had been generated within the EVM. This issue is to reconstruct any logs queried that do not exist in this cache.
The query will use this function within StateDB: https://github.com/ChainSafe/ethermint/blob/3ac6359e1403730fdf6a9807d04fbb29f567ed99/x/evm/types/statedb.go#L291 to retrieve logs.
To implement this, there will have to be a query where inside the query the statedb is used/ copied and replayed the transactions in the block until the tx whose logs need to be regenerated, then return those logs from the StateDB. Likely with some workarounds to fit into this system the workflow should be similar to geth for regenerating
The text was updated successfully, but these errors were encountered: