multiple vmtrace compatibility issues

[banteg]

Describe the bug

these are findings from a brief comparison with erigon. note that erigon's tracing routines are not free from bugs either.

• op is missing
• idx is missing
• mem values are missing
• used should track the remaining gas, currently it's equal to cost in reth
• push on stack currently uses full words, while in other clients you'd see 0xc0ffeebabe rather than 0x000000000000000000000000000000000000000000000000000000c0ffeebabe
• code has an extra zero word at the end for some reason

Steps to reproduce

trace_replayTransaction with reth and erigon and diff the output

Node logs

No response

Platform(s)

Linux (x86)

What version/commit are you on?

0.1.0-alpha.4

What database version are you on?

No response

If you've built Reth from source, provide the full command you used

No response

Code of Conduct

• I agree to follow the Code of Conduct

[mattsse]

there are like 0 docs for all these things so not surprising that things are missing.

The missing fields weren't part of the original OE impl.

what does idx represent here? "idx": "168-2" the last value appears to be the instruction idx, not sure what the leading value is

[github-actions]

This issue is stale because it has been open for 14 days with no activity.

[onbjerg]

@mattsse Is this resolved via the linked PRs? Going through it seems like it?

[mattsse]

closing this, if there are still issues we track them separately once they get reported