Official Go implementation of the Ethereum protocol

You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

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>		4 weeks ago
..
beacon	core/state: move state log mechanism to a separate layer (#30569)	4 weeks ago
clique	core/state: move state log mechanism to a separate layer (#30569)	4 weeks ago
ethash	core/state: move state log mechanism to a separate layer (#30569)	4 weeks ago
misc	core/state: move state log mechanism to a separate layer (#30569)	4 weeks ago
consensus.go	core/state: move state log mechanism to a separate layer (#30569)	4 weeks ago
errors.go	consensus/beacon: check that only the latest pow block is valid ttd block (#25187)	2 years ago