-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Some chain CLI & API #11
Conversation
bcfc217
to
1515efb
Compare
1515efb
to
cb35547
Compare
return err | ||
} | ||
|
||
// TODO: anything else to do here? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should import the block into our local chainstore.
Theres also the consideration of "should we do the expensive verification pass for blocks we create locally?"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we do the expensive verification pass for blocks we create locally
i assume that we run this validation on all incoming blocks, running this validation here seems to make sense (we'll probably create blocks less often that receive)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, it will happen less frequently, but i guess what i'm wondering is whether we should skip it in this case, in order to start mining the next block on top of it more quickly
Move GenerateWinningPoStSectorChallenge to Verifier
Compute seal ticket internally, remove node ticket fn
Based on #9 (Merge after that one)
Some things for #10