Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

--Xevm-worldstate-update-mode=JOURNALED interfers with tracing #47

Open
FlorianHuc opened this issue Oct 4, 2024 · 0 comments
Open

Comments

@FlorianHuc
Copy link

When we enable the option --Xevm-worldstate-update-mode=JOURNALED in a node using the line-tracer plugin, the traces are modified and become invalid.

The two servers return different values for evmWorldUpdater.get(transaction.getTo().get())
in the case the JOURNALED option is enabled, we have:
0x2d8879046f1559e53eb052e949e9544bcb72f414 -> {nonce: UndoScalar{value=1, undoLog=[]}, balance:UndoScalar{value=0x0000000000000000000000000000000000000000000000000c61417e159debb7, undoLog=[UndoEntry[value=0x0000000000000000000000000000000000000000000000000c61417e159debb7, level=7847562], UndoEntry[value=0x0000000000000000000000000000000000000000000000000c6be9fa03f16bb7, level=7847604]]}, code:[not updated], storage:[not updated] }

which leads to invalid trace generation.

in the other case I have:
0x2d8879046f1559e53eb052e949e9544bcb72f414 -> {nonce: 1, balance:0x0000000000000000000000000000000000000000000000000c61417e159debb7, code:[not updated], storage:[not updated] }

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant