Skip to content
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

test if parathread registered on Kusama can produce blocks with polkadot-0.9.16 #61

Closed
brenzi opened this issue Jan 13, 2022 · 4 comments
Assignees

Comments

@brenzi
Copy link
Collaborator

brenzi commented Jan 13, 2022

After upgrading our collator: #60

We need to test if our wasm and state which we had registered on Kusama is compatible with the current relay-chain and collator

We had registered our parathread here (July 13th 2021):
https://kusama.subscan.io/extrinsic/8325343-2

genesis head: 000000000000000000000000000000000000000000000000000000000000000000e3eff20b9989c0270f7e42bc3aad5179cbeecd7a3279735ca414f70afc3dc08703170a2e7597b7b7e3d84c05391d139a62b157e78786d8c082f29dcf4c11131400

matches Current info on Kusama:

currentCodeHash(2015): 0xf552ca431b8004c7012c20340282eb81f300d38bb41bf3f244bdabdee3c991fd
heads(2015): 0x000000000000000000000000000000000000000000000000000000000000000000e3eff20b9989c0270f7e42bc3aad5179cbeecd7a3279735ca414f70afc3dc08703170...
@brenzi brenzi mentioned this issue Jan 13, 2022
1 task
@brenzi
Copy link
Collaborator Author

brenzi commented Jan 13, 2022

Here the original files that were deployed
shell-kusama-deployed-20210713.zip

Based in polkadot 0.9.7

paritytech/substrate?branch=polkadot-v0.9.7#9c572625f6557dfdb19f47474369a0327d51dfbc

@brenzi
Copy link
Collaborator Author

brenzi commented Jan 14, 2022

the collator master still has the same genesis hard-coded. that's good 😅

@brenzi
Copy link
Collaborator Author

brenzi commented Jan 14, 2022

tried to launch the parachain as follows with collator 6765e9b:

  1. launch relaychain node ../polkadot-launch/dist/cli.js polkadot-launch/launch-rococo-local.json
  2. register paraid 2015 and parathread with the files attached above
  3. upgrade parathread to parachain
  4. run one collator ./target/release/integritee-collator --collator --chain shell-rococo --rpc-cors all --name integritee-rococo-collator-1 -- --execution wasm --chain rococo-local-raw.json
  5. inject first of five authority keys

The parachain won't produce blocks, but no error msg:

2022-01-14 09:03:54 [Relaychain] ✨ Imported #174 (0xf7a2…938f)    
2022-01-14 09:03:54 [Parachain] Starting collation. relay_parent=0xf7a2a2371b65c82f9ac355bda7548eb980f9c5cfdbb2873ddfa3b6d2dbfe938f at=0x724c168d8e86b78b831c641e2cc822b8d1bf99fa0b4b28fe59985cd6fd580215
2022-01-14 09:03:56 [Parachain] 💤 Idle (0 peers), best: #0 (0x724c…0215), finalized #0 (0x724c…0215), ⬇ 0 ⬆ 0    
2022-01-14 09:03:56 [Relaychain] 💤 Idle (3 peers), best: #174 (0xf7a2…938f), finalized #171 (0xaf4c…1e2d), ⬇ 1.7kiB/s ⬆ 1.4kiB/s    
2022-01-14 09:04:00 [Relaychain] ✨ Imported #175 (0xb689…b1a5)    
2022-01-14 09:04:00 [Parachain] Starting collation. relay_parent=0xb689719e01f63979d95f29ca4743b82feb7fb1ea8f42b92f5a3e725340dbb1a5 at=0x724c168d8e86b78b831c641e2cc822b8d1bf99fa0b4b28fe59985cd6fd580215
2022-01-14 09:04:01 [Parachain] 💤 Idle (0 peers), best: #0 (0x724c…0215), finalized #0 (0x724c…0215), ⬇ 0 ⬆ 0    
2022-01-14 09:04:01 [Relaychain] 💤 Idle (3 peers), best: #175 (0xb689…b1a5), finalized #172 (0x3be4…8bc2), ⬇ 1.4kiB/s ⬆ 1.0kiB/s    
2022-01-14 09:04:06 [Relaychain] ✨ Imported #176 (0xdbf5…6780)    
2022-01-14 09:04:06 [Parachain] Starting collation. relay_parent=0xdbf587996c129fc73d279e38d3852c00e5f83dbda8a6e1d5bbf0f5e194506780 at=0x724c168d8e86b78b831c641e2cc822b8d1bf99fa0b4b28fe59985cd6fd580215
2022-01-14 09:04:06 [Parachain] 💤 Idle (0 peers), best: #0 (0x724c…0215), finalized #0 (0x724c…0215), ⬇ 0 ⬆ 0    
2022-01-14 09:04:06 [Relaychain] 💤 Idle (3 peers), best: #176 (0xdbf5…6780), finalized #173 (0x449f…dc2f), ⬇ 1.8kiB/s ⬆ 1.5kiB/s    
2022-01-14 09:04:11 [Parachain] 💤 Idle (0 peers), best: #0 (0x724c…0215), finalized #0 (0x724c…0215), ⬇ 0 ⬆ 0    
2022-01-14 09:04:11 [Relaychain] 💤 Idle (3 peers), best: #176 (0xdbf5…6780), finalized #174 (0xf7a2…938f), ⬇ 1.0kiB/s ⬆ 0.9kiB/s    
2022-01-14 09:04:12 [Relaychain] ✨ Imported #177 (0x46da…c57c)    
2022-01-14 09:04:12 [Parachain] Starting collation. relay_parent=0x46da57aa3b609cbb8097ac333f8d253429091691f7b3b2e44dc23b51ad8fc57c at=0x724c168d8e86b78b831c641e2cc822b8d1bf99fa0b4b28fe59985cd6fd580215
2022-01-14 09:04:16 [Parachain] 💤 Idle (0 peers), best: #0 (0x724c…0215), finalized #0 (0x724c…0215), ⬇ 0 ⬆ 0    
2022-01-14 09:04:16 [Relaychain] 💤 Idle (3 peers), best: #177 (0x46da…c57c), finalized #175 (0xb689…b1a5), ⬇ 1.7kiB/s ⬆ 1.3kiB/s    

@clangenb
Copy link
Contributor

clangenb commented Jan 16, 2022

I could successfully produce parachain blocks without any issues against polkadot-v0.9.13. I used your procedure and files from above except for a small change in your collator command:

./target/release/integritee-collator --collator --chain shell-rococo --rpc-cors all --name integritee-rococo-collator-1 --force-authoring --rpc-port 9936 -- --execution wasm --chain rococo-local-raw.json

Changes to your command:

  • added --force-authoring
  • added --rpc-port 9936 otherwise, there is a port-conflict with the relay-chains, which makes it tedious to inject the aura-key because the parachain rpc-port is random then. Is there any chance you accidentally injected the keys into the relay chain?

@brenzi brenzi changed the title test if parathread registered on Kusama can produce blocks with polkadot-0.9.13 test if parathread registered on Kusama can produce blocks with polkadot-0.9.16 Feb 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants