-
Notifications
You must be signed in to change notification settings - Fork 8
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
unbrick parachain #77
Comments
closes #65 part of #77 * re-genesis all chain specs (Kusama will be reset, westend will be torn down in favor of a fresh rococo deployment) * de-clutter spec generation. added a few improvements from encointer too * bump version to 1.5.13 * this PR shall build the basis of the to-be-reset genesis config for Kusama tested * [x] rococo-local-with-shell and upgrade to full runtime * [x] kusama-local-with-shell (need to wait 60min before producing blocks!!) runtime upgrade only takes seconds after that * [x] launch without relay `--chain integritee-kusama` * paraid correct for parachainInfo.parachainId = 2015 * sudo key correct * sudo balance 10 TEER
trying to reproduce #84, but I can't: repeating test starting with collator 1.4.12 and polkadot-0.9.17 relay binaries:
check parachain genesis hash: 0x54f9c063093854f597aaa6b6acfc16bee59394667693bac3c5e6e22c68a0e9b4 runtime should be V2 (on Kusama, it actually was V0 before we upgraded to V2 #75 ) now, like on Kusama, we upgrade our runtime to V3 (edit: this we didn't do on Kusama! it was at V2 when doing forceSetCurrentHead!):
wait a few blocks until it is applied and reload js/apps brick chain: set sudo balance to 10 -> reaped check genesis hash: 0x54f9c063093854f597aaa6b6acfc16bee59394667693bac3c5e6e22c68a0e9b4 use release binary 1.5.13 (which is guaranteed to produce different genesis from 1.4.12)
now edit the spec and set
new-head.state:
relay: sudo forceSetCurrentHead(2015, new-head.state) para should stall now. wait 1min and no new block should be produced now, start a new collator on fresh genesis:
this node started collating, but no blocks could be produced (why?) So I started another node based on the old collator binary but the new spec:
and it started producing blocks. after a few blocks, kill that stepping stone again and restart it with the 1.5.13 binary
now, open js/apps to port 9947 check balances. Alice should have her funds back. now we are at a comparable state to our Kusama para now. sudo is fixed. runtime is V3 state matches the new head: 0x104ef43d943c58bb485a586668a381240763ed9 so, let's try a simple setBalance sudo again: reload js/apps
works like a charm let's send a filtered extrinsic:
yields all good here. why not on Kusama? |
insight from #84 (comment)
|
reproduced: #84 (comment) |
tracking issue
iku-collator-04
(bootnode) andiku-cullator-05
with new genesis spec and purge parachain for these nodes only and inject keys. keep identities the same for bootnode configtest with rococo local
using new launch config here: 183484a
~/bin/polkadot-v0.9.17
~/bin/integritee-collator-1.4.12
node ../polkadot-launch/dist/cli.js polkadot-launch/launch-rococo-local-with-shell-rococo-1.4.12.json
until setup completefirst, brick the parachain:
now, sudo is dead and Bob can't rescue Alice because of the extrinsic filter in place
prepare new head
now, edit the spec to make sure it will be different.
on the relaychain, SetCurrentHead:
you should see
that will stall the parachain
remedy: start entirely fresh parachain collator with new spec
then, point js/apps to port 9946 and Alice will have her funds back. and block numbers start at zero again
prepare new genesis for integritee shell
As we are reverting to genesis, we need a different genesis state than last time (otherwise this SetCurrentHead won't have any effect)
This is a good occasion to solve #65 at the same time and a few other things:
#78
The text was updated successfully, but these errors were encountered: