Closed F3Joule closed 2 years ago
{
manager: 5GjP491LcTa71ZhTBbwp3Eda3xauBX8ESunEsQq3KCQPaz4r
periodBegin: 28
periodCount: 3
lastLease: 28
leaseCount: 1
}
For what I see, you should be onboarded again in the next batch. These onboarding/offboardings are automated by the assigned_slots pallet.
In the meantime I could suggest running rococo_local on your side and keep on testing in there.
You completed the Cumulus Tutorial for your parachain and tested locally?
rococo-local
.Team Name
Dappforce
Parachain Name
Subsocial
ParaID
3015
This para ID does NOT conflict with another Rococo para ID?
Is this a request for a long term slot?
Short term, we don't have a matching para ID in use on Polkadot or Kusama.
Upload your Genesis Head (genesis state)
para-3015-rococo-genesis.txt
Upload your Validation Code (genesis runtime Wasm)
para-3015-rococo-wasm.txt
(Optional) Upload your Chain Specification
No response
Anything else we should know?
We need a few more days to finish our testing. Then we'll get long-term slot. But for now we please for prolongation.
Register your Rococo parachain details for
polakdot-js/apps