Co-authored-by: Sina Mahmoodi <itz.s1na@gmail.com>

The struct logger (or opcode tracer) was missing the return data field even
if this was explicitly enabled by user via `"enableReturnData": true` in the config.
This PR fixes this issue.
Co-authored-by: Sina Mahmoodi <itz.s1na@gmail.com>

* internal/ethapi: testBackend reuse the same db
Signed-off-by: jsvisa <delweng@gmail.com>

* internal/ethapi: implment GetTransaction
Signed-off-by: jsvisa <delweng@gmail.com>

* internal/ethapi: implement GetReceipts
Signed-off-by: jsvisa <delweng@gmail.com>

* internal/ethapi: insert receipts and setup txlookup
Signed-off-by: jsvisa <delweng@gmail.com>

* internal/ethapi: add simple success tx receipt test
Signed-off-by: jsvisa <delweng@gmail.com>

* internal/ethapi: add case create contract
Signed-off-by: jsvisa <delweng@gmail.com>

* internal/ethapi: add contract call receipt
Signed-off-by: jsvisa <delweng@gmail.com>

* internal/ethapi: add tx notfound
Signed-off-by: jsvisa <delweng@gmail.com>

* internal/ethapi: add dynamic fee testcase

* internal/ethapi: add accessList receipt

* internal/ethapi: no need to insert receipt chain, no error

* internal/ethapi: use HeaderByHash instead

* internal/ethapi: add one more case

---------
Signed-off-by: jsvisa <delweng@gmail.com>

internal/ethapi: fast exit if tx notfound

graphql: fix race in test

* eth: rm redundant type from array, slice, or map

* miner: rm redundant type from array, slice, or map

fix function name in comment
Signed-off-by: cui fliter <imcusg@gmail.com>

This prevents an issue where the node would attempt to contact the bootstrap
nodes even if they weren't contained in the netrestrict list.

This change adds the ability to perform reads from freezer without size limitation. This can be useful in cases where callers are certain that out-of-memory will not happen (e.g. reading only a few elements). 

The previous API was designed to behave both optimally and secure while servicing a request from a peer, whereas this change should _not_ be used when an untrusted peer can influence the query size. 

This simplifies the code that initializes the discovery a bit, and
adds new flags for enabling/disabling discv4 and discv5 separately.

---------
Co-authored-by: Felix Lange <fjl@twurst.com>

This change makes the StateDB track the state key value diff of a block transition.
We already tracked current account and storage values for the purpose of updating
the state snapshot. With this PR, we now also track the original (pre-transition) values
of accounts and storage slots.

Fixes an issue where waitgroups were used erroneously, which could lead to waitgroup being added to while wait was already invoked. 

Implements [EIP 5656](https://eips.ethereum.org/EIPS/eip-5656), MCOPY instruction, and enables it for Cancun. 

---------
Co-authored-by: Martin Holst Swende <martin@swende.se>

Back before #27178 , we spun up a number of ethash verifiers to verify headers. So we also had tests to ensure that we were indeed able to abort verification even if we had multiple workers running.

With PR #27178, we removed the parallelism in verification, and these tests are now failing, since we now just sequentially fire away the results as fast as possible on one routine.

This change removes the (sometimes failing) tests

This PR adds metrics for p2p dialing, which gives us visibility into the quality of the dial 
candidates  returned by our discovery methods.

This change adds back the 'geth --dev' mode of operation, using a cl-mocker. 

---------
Co-authored-by: Martin Holst Swende <martin@swende.se>
Co-authored-by: rjl493456442 <garyrong0905@gmail.com>
Co-authored-by: lightclient <14004106+lightclient@users.noreply.github.com>

Co-authored-by: Martin Holst Swende <martin@swende.se>

core (blockchain_test): add chain.Stop() to tests

This removes text parsing in leveldb metrics collection code. All metrics
can now be accessed through the stats API provided by leveldb.

We also add new gauge-typed metrics that count the number of tables at each level.

---------
Co-authored-by: Exca-DK <Exca-DK@users.noreply.github.com>
Co-authored-by: Gary Rong <garyrong0905@gmail.com>
Co-authored-by: Felix Lange <fjl@twurst.com>

The clean trie cache is persisted periodically, therefore Geth can
quickly warmup the cache in next restart.

However it will reduce the robustness of system. The assumption is
held in Geth that if the parent trie node is present, then the entire
sub-trie associated with the parent are all prensent.

Imagine the scenario that Geth rewinds itself to a past block and
restart, but Geth finds the root node of "future state" in clean
cache then regard this state is present in disk, while is not in fact.

Another example is offline pruning tool. Whenever an offline pruning
is performed, the clean cache file has to be removed to aviod hitting
the root node of "deleted states" in clean cache.

All in all, compare with the minor performance gain, system robustness
is something we care more.

* core/state, light, les: make signature of ContractCode hash-independent

* push current state for feedback

* les: fix unit test

* core, les, light: fix les unittests

* core/state, trie, les, light: fix state iterator

* core, les: address comments

* les: fix lint

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

* params, trie: add verkle fork management + upgrade go-verkle

* remove the two verkle files

* core, eth, params: add missing function

* Gary's feedback

* remove trie/utils/verkle.go

* add verkle block override

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

* eth: send big transactions by announce/retrieve only

* Update eth/handler.go
Co-authored-by: Martin Holst Swende <martin@swende.se>

* eth: remove superfluous bracket

* eth: add whitespace

---------
Co-authored-by: Martin Holst Swende <martin@swende.se>

* trie, core/state: revert error removal in (*state.Trie).Commit

* Gary's nitpick :)
Co-Authored-By: rjl493456442 <garyrong0905@gmail.com>

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

This error will never happen, but if it ever does happen, we will at least see it.

* core/vm: move TSTORE,TLOAD to correct opcode nums

* core/vm: cleanup

error message should not be capitalized / consistency

Signed-off-by: jsvisa <delweng@gmail.com>