Skip to content

[evm] performance: since we only create a cacheCtx whenever a precompile is called, then reverting a precompile call can just get rid of the cacheCtx and reset the writeToCommitCtxFromCacheCtx function to nil. That would be a cleaner way to revert a PrecompileCalled journal entry rather than deep copy the multistore and save it in a snapshot, but I'd have to test that implementation out. #42

[evm] performance: since we only create a cacheCtx whenever a precompile is called, then reverting a precompile call can just get rid of the cacheCtx and reset the writeToCommitCtxFromCacheCtx function to nil. That would be a cleaner way to revert a PrecompileCalled journal entry rather than deep copy the multistore and save it in a snapshot, but I'd have to test that implementation out.

[evm] performance: since we only create a cacheCtx whenever a precompile is called, then reverting a precompile call can just get rid of the cacheCtx and reset the writeToCommitCtxFromCacheCtx function to nil. That would be a cleaner way to revert a PrecompileCalled journal entry rather than deep copy the multistore and save it in a snapshot, but I'd have to test that implementation out. #42

Triggered via issue October 29, 2024 21:00
Status Success
Total duration 12s
Artifacts

gh-issues.yml

on: issues
Add GH ticket to project
3s
Add GH ticket to project
Add GH ticket to project
2s
Add GH ticket to project
Fit to window
Zoom out
Zoom in