* core/state, tests: remove account reset operation

* core/state, core/vm: implement createcontract journal event

* core/state: make createcontract not emit dirtied account, unskip tests

* core/state: add createcontract to journal fuzzing

* core/state: fix journal

* core/state: address comments

* core/state: remove useless code

---------

Co-authored-by: Gary Rong <[email protected]>

trie: Preallocate capacity for fields slice

Currently our state journal tracks each storage update to a contract, having the ability to revert those changes to the previously set value.

For the very first modification however, it behaves a bit wonky. Reverting the update doesn't actually remove the dirty-ness of the slot, rather leaves it as "change this slot to it's original value". This can cause issues down the line with for example write witnesses needing to gather an unneeded proof.

This PR modifies the storageChange journal entry to not only track the previous value of a slot, but also whether there was any previous value at all set in the current execution context. In essence, the PR changes the semantic of storageChange so it does not simply track storage changes, rather it tracks dirty storage changes, an important distinction for being able to cleanly revert the journal item.

fix useless condition

…627)

This PR fixes some flaws with the existing tests.

The randomized testing (TestSnapshotRandom) executes a series of steps which modify the state and create journal-events. Later on, we compare the forward-going-states against the backwards-unrolling-journal-states, and check that they are identical.

The "identical" check is performed using various accessors. It turned out that we failed to check some things: 
- the accesslist contents
- the transient storage contents
- the 'newContract' flag
- the dirty storage map

This change adds these new checks

* build: build all the builders to build all the builders

* build: tweak the indexes a bit to make them consistent

* build: drop trusty from PPA builds, EOL and incompatible

* build: add Ubuntu Noble PPA build target

… (#29661)

Define these on a value receiever so that nil is shown differently.

…9620)

set cap for map in a certain scenario

…514)

…ode (#29579)

Co-authored-by: Sina Mahmoodi <[email protected]>

* all: refactor so NewBlock(..) and WithBody(..) take a types.Body

* core: fixup comments, remove txs != receipts panic

* core/types: add empty withdrawls to body if len == 0

This PR removes pre-merge sync logic from the downloader. Now-irrelevant tests are removed and others have been updated.

* fix: open file used up but not closed

* feat: more same case

* feat: accept conversation

* core/rawdb, trie: improve db APIs for accessing trie nodes

* triedb/pathdb: fix

* core/state, internal/workerpool: parallelize parts of state commit

* core, internal: move workerpool into syncx

* core/state: use errgroups, commit accounts concurrently

* core: resurrect detailed commit timers to almost-accuracy

* preallocated capacity for map's certain usege of memory

* preallocated capacity for map's certain usege of memory

…ze (#29708)

…BlockRoot` (#29355)

Added a start/end system where tracer can be notified that processing of some Ethereum system calls is starting processing and also notifies it when the processing has completed.

Doing a start/end for system call will enable tracers to "route" incoming next tracing events to go to a separate bucket than other EVM calls. Those not interested by this fact can simply avoid registering the hooks.

The EVM call is going to be traced normally afterward between the signals provided by those 2 new hooks but outside of a transaction context OnTxStart/End. That something implementors of live tracers will need to be aware of (since only "trx tracers" are not concerned by ProcessBeaconRoot).

---------

Co-authored-by: Sina Mahmoodi <[email protected]>

ethdb/pebble: use GetOrRegister instead of NewRegistered when creating metrics

…29644)

* eth/gasprice: add query limit for FeeHistory to defend DDOS attack

* fix return values after cherry-pick

---------

Co-authored-by: Eric <[email protected]>

Fixes #29702

Co-authored-by: Felix Lange <[email protected]>

* core: simplify chain tests

* core, eth, cmd: use in-memory freezer for tests

* core: restore tests

…1.14.2

Add a notion of zombies to preserve empty account behavior