Consensys / linea-tracer

Part of the Linea stack responsible for extracting data from the execution of an EVM client in order to construct large matrices called execution traces.

https://linea.build

Other

24 stars 20 forks source link

Tracing issues list #865

Open OlivierBBB opened 1 month ago

OlivierBBB commented 1 month ago

Main point

This issue is about understanding with pinpoint accuracy the exact chronology of events in Besu. Details matter tremendously to the tracer as we would like to rely less and less on "hand modified snapshots".

CREATE related

[x] #866
[x] #867
[x] #887

CALL related

[x] #868
[x] #869
[x] #885

Generalities

Memory operations

[x] #913

Stack updates

[x] #872
[x] #883

What has already taken place at ... ?

[x] #870
[x] #875

Misc

[x] #882
[x] #871

OlivierBBB commented 1 month ago

Our reason for asking is that:

866 and #867: for failure condition and empty init code we would like to take snapshots of the updated creator and createe accounts when the TraceContextReEntry hook is activated. This only makes sense if we actually enter a new context in those "trivial" cases
If not "re-entry" takes place we must hook somewhere else ... maybe post execution of the current OpCode ... or even PreExecution of the next OpCode ... ?

non-fungible-nelson commented 2 weeks ago

Hi @OlivierBBB - there are a bunch of issues opened / questions answered above. I want to make sure I am appropriately tracking next steps, what are they as of now?

CC: @lu-pinto

macfarla commented 2 weeks ago

ref https://github.com/hyperledger/besu/issues/7301