This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
Block-authoring side of authoring-version should be a set not a value #571
Comments
gavofyork
changed the title
gavofyork
added
J0-enhancement
lamafab
pushed a commit
to lamafab/substrate
that referenced
this issue
Jun 16, 2020
* Update to latest Substrate master (paritytech#570) * Bump substrate/version (paritytech#557) * Bump version and Substrate (paritytech#560) * Bump version and Substrate * Bump version and Substrate * Bump versions * bump substrate to release specific v0.6.15 * Update lock * Prepare Polkadot update for Substrate runtime interface 2.0 (paritytech#563) * Prepare Polkadot update for Substrate runtime interface 2.0 * bump substrate to release specific v0.6.15 * Switch to `polkadot-master` * Version bump * Master backports * Bump runtime * Fix tests * Fix tests * Another fix.
liuchengxu
pushed a commit
to chainx-org/substrate
that referenced
this issue
Aug 23, 2021
* reduce lagging finality backoff to a maximum of 10 slots * disable lagging finality backoff
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
At present, it is assumed that the block-authoring logic supports only a single authoring version. This is not correct since it can reasonably switch its logic depending on the specific runtime. Rather the block authoring logic should be able to state a set of different authoring versions that it can support. This version declaration is independent of the basic runtime version declaration, unlike at present where the two are shared.
The text was updated successfully, but these errors were encountered: