Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

CheckInherentError can now report when something would be valid #1204

Merged
merged 3 commits into from
Dec 4, 2018

Conversation

rphmeier
Copy link
Contributor

@rphmeier rphmeier commented Dec 4, 2018

This enables consensus proposers to finish proposing only when check_inherents(block_with_inherents) returns Ok.

In srml-timestamp, the set inherent will automatically be set forward to the next valid time, but proposers should not broadcast their block until waiting until a time specified by CheckInherentError::ValidAfterTimestamp.

The check_inherents generated by the macro will choose the highest ValidAtTimestamp variant returned by submodules.

@rphmeier rphmeier added the A0-please_review Pull request needs code review. label Dec 4, 2018
@bkchr bkchr self-requested a review December 4, 2018 08:18
@bkchr bkchr added A8-looksgood and removed A0-please_review Pull request needs code review. labels Dec 4, 2018
@bkchr bkchr merged commit 3d549e9 into master Dec 4, 2018
@bkchr bkchr deleted the rh-inherents-valid-after branch December 4, 2018 08:19
lamafab pushed a commit to lamafab/substrate that referenced this pull request Jun 16, 2020
* Rename Fixed128 to FixedI128.

* Bump cargo, merge paritytech#6236 fixes

Co-authored-by: Shawn Tabrizi <[email protected]>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants