go-ethereum

Commit Graph

Author	SHA1	Message	Date
Karol Chojnowski	3c7336b0e9	core/state: invoke OnCodeChange-hook on selfdestruct (#30686 ) This change invokes the OnCodeChange hook when selfdestruct operation is performed, and a contract is removed. This is an event which can be consumed by tracers.	2 weeks ago
Martin HS	e56bbd77a4	core/state: small fix in hooked statedb (#30732 ) fixes a very tiny bug	3 weeks ago
Martin HS	459bb4a647	core/state: move state log mechanism to a separate layer (#30569 ) This PR moves the logging/tracing-facilities out of `*state.StateDB`, in to a wrapping struct which implements `vm.StateDB` instead. In most places, it is a pretty straight-forward change: - First, hoisting the invocations from state objects up to the statedb. - Then making the mutation-methods simply return the previous value, so that the external logging layer could log everything. Some internal code uses the direct object-accessors to mutate the state, particularly in testing and in setting up state overrides, which means that these changes are unobservable for the hooked layer. Thus, configuring the overrides are not necessarily part of the API we want to publish. The trickiest part about the layering is that when the selfdestructs are finally deleted during `Finalise`, there's the possibility that someone sent some ether to it, which is burnt at that point, and thus needs to be logged. The hooked layer reaches into the inner layer to figure out these events. In package `vm`, the conversion from `state.StateDB + hooks` into a hooked `vm.StateDB` is performed where needed. --------- Co-authored-by: Gary Rong <garyrong0905@gmail.com>	1 month ago

Author

SHA1

Message

Date

Karol Chojnowski

3c7336b0e9

core/state: invoke OnCodeChange-hook on selfdestruct (#30686 )

This change invokes the OnCodeChange hook when selfdestruct operation is performed, and a contract is removed. This is an event which can be consumed by tracers.

2 weeks ago

Martin HS

e56bbd77a4

core/state: small fix in hooked statedb (#30732 )

fixes a very tiny bug

3 weeks ago

Martin HS

459bb4a647

core/state: move state log mechanism to a separate layer (#30569 )

This PR moves the logging/tracing-facilities out of `*state.StateDB`,
in to a wrapping struct which implements `vm.StateDB` instead.

In most places, it is a pretty straight-forward change: 
- First, hoisting the invocations from state objects up to the statedb. 
- Then making the mutation-methods simply return the previous value, so
that the external logging layer could log everything.

Some internal code uses the direct object-accessors to mutate the state,
particularly in testing and in setting up state overrides, which means
that these changes are unobservable for the hooked layer. Thus, configuring
the overrides are not necessarily part of the API we want to publish.

The trickiest part about the layering is that when the selfdestructs are
finally deleted during `Finalise`, there's the possibility that someone
sent some ether to it, which is burnt at that point, and thus needs to
be logged. The hooked layer reaches into the inner layer to figure out
these events.

In package `vm`, the conversion from `state.StateDB + hooks` into a
hooked `vm.StateDB` is performed where needed.

---------

Co-authored-by: Gary Rong <garyrong0905@gmail.com>

1 month ago

3 Commits (66d8185aad6f3dde13fdeb95e985bafd6e2e0167)