Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blocks added to the store before some verifications #1288

Closed
terencechain opened this issue Jul 11, 2019 · 3 comments
Closed

Blocks added to the store before some verifications #1288

terencechain opened this issue Jul 11, 2019 · 3 comments
Labels
general:presentation Presentation (as opposed to content) scope:fork-choice

Comments

@terencechain
Copy link
Contributor

terencechain commented Jul 11, 2019

The block gets added to the store before checking it's a descendant of the finalized block and later than the finalized epoch slot. Any reason it is added before those verifications?
The appropriate spot looks to be after state transition

Screen Shot 2019-07-10 at 6 53 21 PM

@terencechain terencechain changed the title Blocks added to the store before a few checks Blocks added to the store before some verifications Jul 11, 2019
@hwwhww
Copy link
Contributor

hwwhww commented Jul 11, 2019

Because with the current algorithm, the given block would be queried in get_ancestor(store: Store, root: Hash, slot: Slot) function recursively.
I had the same question before: #1068 (comment), but we haven't figured out a better solution yet.

We do want to make the fork choice rule spec more abstract in the spec level, however for sanity testing, the Store is exposed as status quo. IMO it might need more iterations past spec freeze to make it better.

@JustinDrake JustinDrake added the general:presentation Presentation (as opposed to content) label Jul 11, 2019
@JustinDrake
Copy link
Contributor

@terencechain: Can we close this?

@terencechain
Copy link
Contributor Author

Sure and to clarify this is just a presentation issue. In Prysm, we add the block to fork choice store after state_transition

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
general:presentation Presentation (as opposed to content) scope:fork-choice
Projects
None yet
Development

No branches or pull requests

3 participants