go-ethereum

Author	SHA1	Message	Date
rjl493456442	59f7b289c3	cmd, core, eth, graphql, trie: no persisted clean trie cache file (#27525 ) 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.	1 year ago
rjl493456442	dea1fb3cfc	all: cleanup tests (#25641 ) Follow-up to PR #25523 to cleanup all relevant tests.	2 years ago
rjl493456442	d10c280309	all: move genesis initialization to blockchain (#25523 ) * all: move genesis initialization to blockchain * core: add one more check * core: fix tests	2 years ago
Martin Holst Swende	1988b47e02	tests/fuzzzers. eth/protocols/snap: add snap protocol fuzzers (#23957 )	3 years ago