Breakup RPCBlock into LookupBlock & RangeSyncBlock#8860
Conversation
eserilev
left a comment
There was a problem hiding this comment.
This looks great. Really makes things much clearer imo
I just had a few questions about a few test functions
|
This pull request has merge conflicts. Could you please resolve them @ethDreamer? 🙏 |
|
Some required checks have failed. Could you please take a look @ethDreamer? 🙏 |
b1802d2 to
1787638
Compare
pawanjay176
left a comment
There was a problem hiding this comment.
This is great. I just have minor nits.
I initially thought that RangeSyncBlock should be just SyncBlock because block_lookup uses it too. But I just learnt that block lookups processes blocks and columns separately even for parent lookups.
Would like to get a ✅ from @dapplion as well to make sure this is in line with his plans for gloas lookups as well
| /// verification. i.e. this block has all the required data to get verified and imported into fork choice. | ||
| /// | ||
| /// 2. `BlockOnly`: This is a post-deneb block that requires blobs to be considered fully available. | ||
| pub struct LookupBlock<E: EthSpec> { |
There was a problem hiding this comment.
Can we add docs to it specifying that its only a wrapper over a signed beacon block? Its useful when reviewing sync code
pawanjay176
left a comment
There was a problem hiding this comment.
LGTM. I know that Lion is on board with the idea so gonna go ahead and merge so that we can build other sync PRs on this
Merge Queue Status
This pull request spent 29 minutes 12 seconds in the queue, including 27 minutes 44 seconds running CI. Required conditions to merge
|
This should make sync and the DA checker much more clear.