5 Commits (57a65f00c9518dd29b876e72756a287d0d365012)

Author	SHA1	Message	Date
Péter Szilágyi	81bd998353	core, eth/downloader: handle spurious junk bodies from racey rollbacks (#25578) ... * eth/downloader: handle junkbodies/receipts in the beacon sync * core: check for header presence when checking for blocks	2 years ago
Marius van der Wijden	c6dcd018d2	core: eth: rpc: implement safe rpc block (#25165) ... * core: eth: rpc: implement safe rpc block * core: fix setHead, panics	2 years ago
Marius van der Wijden	e6fa102eb0	core, eth, internal, rpc: implement final block (#24282) ... * eth: core: implement finalized block * eth/catalyst: fix final block * eth/catalyst: update finalized head gauge * internal/jsre/deps: updated web3.js to allow for finalized block * eth/catalyst: make sure only one thread can call fcu * eth/catalyst: nitpicks * eth/catalyst: use plain mutex * eth: nitpicks	3 years ago
Martin Holst Swende	db03faa10d	core, eth: improve delivery speed on header requests (#23105) ... This PR reduces the amount of work we do when answering header queries, e.g. when a peer is syncing from us. For some items, e.g block bodies, when we read the rlp-data from database, we plug it directly into the response package. We didn't do that for headers, but instead read headers-rlp, decode to types.Header, and re-encode to rlp. This PR changes that to keep it in RLP-form as much as possible. When a node is syncing from us, it typically requests 192 contiguous headers. On master it has the following effect: - For headers not in ancient: 2 db lookups. One for translating hash->number (even though the request is by number), and another for reading by hash (this latter one is sometimes cached). - For headers in ancient: 1 file lookup/syscall for translating hash->number (even though the request is by number), and another for reading the header itself. After this, it also performes a hashing of the header, to ensure that the hash is what it expected. In this PR, I instead move the logic for "give me a sequence of blocks" into the lower layers, where the database can determine how and what to read from leveldb and/or ancients. There are basically four types of requests; three of them are improved this way. The fourth, by hash going backwards, is more tricky to optimize. However, since we know that the gap is 0, we can look up by the parentHash, and stlil shave off all the number->hash lookups. The gapped collection can be optimized similarly, as a follow-up, at least in three out of four cases. Co-authored-by: Felix Lange <fjl@twurst.com>	3 years ago
Marius van der Wijden	c641cff51a	core: refactored blockchain.go (#23735)	3 years ago