-
Notifications
You must be signed in to change notification settings - Fork 835
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
Async backing enablement checklist #3226
Comments
FYI @rphmeier in case you want to add other things or you know if some of this stuff was already tested/checked. |
This issue has been mentioned on Polkadot Forum. There might be relevant details there: https://forum.polkadot.network/t/async-backing-development-updates/6176/1 |
Verified this, by running zombienets with asset hub parachains from polkadot 1.1.0 and polkadot 1.3.0 |
Done, westend parachains, from 1.8.0 release the with async backing changes, got upgrade while async backing was disable on relay chain. They correctly produced blocks at 12s rate. |
Checked westend block times with async backing enabled things looked good, blocked times averages are around 6.7, but that's expected because one of the validator is kagome which does not seem to back things. |
Ran subp2p-explorer for polkadot network, it discovered just 2/3 out of the all authorities, from them it seems 13(7%) are still running software that is not compatible with async-backing.
|
Really, how is that possible? |
I used the tool from here: https://github.com/paritytech/data/issues/30, as far as I can tell subp2p-explorer can't connect to those nodes to query their version. I'll let @lexnv tell you why our tool can't connect to all of the nodes. |
Known polkadot nodes that run a version behind the desired >=1.7, total number 23(8%) out of 286 discovered by subp2p-explorer.
|
This issue has been mentioned on Polkadot Forum. There might be relevant details there: https://forum.polkadot.network/t/async-backing-development-updates/6176/8 |
This issue has been mentioned on Polkadot Forum. There might be relevant details there: https://forum.polkadot.network/t/polkadot-digest-12-apr-2024/7404/1 |
Kusama async backing enabled with the enactment of https://kusama.subsquare.io/fellowship/referenda/70. ![]() The only side effect of enablement is that system parachains will see occasionally the following error: The error is harmless it is just the collator trying to build a block sooner than its parent being included and the parachain runtime rightly rejecting it. The error will go away once all system parachains get migrated to async backing with: polkadot-fellows/runtimes#266 Full stack
|
Indeed, it will go away sooner when collators upgrade to include #3630 |
Async backing has been enabled with https://polkadot.subsquare.io/referenda/688 on polkadot, closing the issue. |
The purpose of this ticket is to collate together all the needed things to be able to safely enable async backing on kusama and polkadot, in chronological order.
Kusama enablement
Polkadot enablement
Other items
The text was updated successfully, but these errors were encountered: