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
one thing to consider is parity-style traces only contain calls and no logs. so this would only by possible with geth-style logs by catching LOG0...LOG4opcodes.
one thing to consider is parity-style traces only contain calls and no logs. so this would only by possible with geth-style logs by catching LOG0...LOG4opcodes.
Could probably fill in logs by finding LOG* opcodes and tracing it back to raw topics/data
Overview
Foundry is able to include events in the logs... so should we!
NOTE: This may only be possible in the geth style logs.
Specification
See image ! But make fit in . Use your favorite ape crayon colors (pick a new color for the event name but use the input color for the inputs)
Dependencies
Might need to add support in
evm-trace
first: ApeWorX/evm-trace#9The text was updated successfully, but these errors were encountered: