17 Commits (9b93564e213ac33e2647ef94a8d8758ec5f0a1af)

Author	SHA1	Message	Date
Martin Holst Swende	526c3f6b9e	core/state/snapshot: fix benchmarks (#23804)	3 years ago
Melvin Junhee Woo	d2e1b17f18	snapshot, trie: fixed typos, mostly in snapshot pkg (#22133)	4 years ago
gary rong	26d271dfbb	core/state/snapshot: implement storage iterator (#20971) ... * core/state/snapshot: implement storage iterator * core/state/snapshot, tests: implement helper function * core/state/snapshot: fix storage issue If an account is deleted in the tx_1 but recreated in the tx_2, the it can happen that in this diff layer, both destructedSet and storageData records this account. In this case, the storage iterator should be able to iterate the slots belong to new account but disable further iteration in deeper layers(belong to old account) * core/state/snapshot: address peter and martin's comment * core/state: address comments * core/state/snapshot: fix test	5 years ago
gary rong	b9df7ecdc3	all: seperate consensus error and evm internal error (#20830) ... * all: seperate consensus error and evm internal error There are actually two types of error will be returned when a tranaction/message call is executed: (a) consensus error (b) evm internal error. The former should be converted to a consensus issue, e.g. The sender doesn't enough asset to purchase the gas it specifies. The latter is allowed since evm itself is a blackbox and internal error is allowed to happen. This PR emphasizes the difference by introducing a executionResult structure. The evm error is embedded inside. So if any error returned, it indicates consensus issue happens. And also this PR improve the `EstimateGas` API to return the concrete revert reason if the transaction always fails * all: polish * accounts/abi/bind/backends: add tests * accounts/abi/bind/backends, internal: cleanup error message * all: address comments * core: fix lint * accounts, core, eth, internal: address comments * accounts, internal: resolve revert reason if possible * accounts, internal: address comments	5 years ago
Péter Szilágyi	fab0ee3bfa	core/state/snapshot: fix various iteration issues due to destruct set	5 years ago
Péter Szilágyi	a4cf279494	core/state: extend snapshotter to handle account resurrections	5 years ago
Péter Szilágyi	06d4470b41	core: fix broken tests due to API changes + linter	5 years ago
Péter Szilágyi	6ddb92a089	core/state/snapshot: full featured account iteration	5 years ago
Péter Szilágyi	e567675473	core/state/snapshot: move iterator out into its own files	5 years ago
Martin Holst Swende	7e38996301	core/state/snapshot: implement snapshot layer iteration	5 years ago
Martin Holst Swende	3ad4335acc	core/state/snapshot: node behavioural difference on bloom content	5 years ago
Péter Szilágyi	fd39f722a3	core: journal the snapshot inside leveldb, not a flat file	5 years ago
Péter Szilágyi	351a5903b0	core/rawdb, core/state/snapshot: runtime snapshot generation	5 years ago
Péter Szilágyi	d754091a87	core/state/snapshot: unlink snapshots from blocks, quad->linear cleanup	5 years ago
Martin Holst Swende	cdf3f016df	snapshot: iteration and buffering optimizations	5 years ago
Péter Szilágyi	d7d81d7c12	core/state/snapshot: extract and split cap method, cover corners	5 years ago
Martin Holst Swende	e146fbe4e7	core/state: lazy sorting, snapshot invalidation	5 years ago