[Parachain Onboarding | Slot Request] ParaId: 2101

[robhyrk]

Parachain Name

Battery Station

ParaID

2101

Parachain Manager Account

dDyymrYQMxP5ksYCLXQjv9oAYiQdJFE9Ampgv8cYxc4qXpTNH

Upload your Genesis Header - Do not submit a compressed file.

battery_station_on_paseo_sans_highest_slot_seen_genesis_state.json

Upload your Validation Code (genesis runtime Wasm) - Do not submit a compressed file.

battery_station_on_paseo_sans_highest_slot_seen_genesis_wasm.json

🔗 zboto Link

[robhyrk]

FYI we had an issue with Battery Station being offline for an extended period and it seems we were de-registered because of it. Hoping to get back up and running. Let me know if you require any additional info, thanks!

[robhyrk]

@al3mart is there anything required from our end to help push this request forward? Thank you :)

[al3mart]

Hey @robhyrk let me get you onboarding moving.

[al3mart]

New artifacts have been registered and a core has been assigned. Please do be mindful of procuring some coretime in the coretime sales and configuring your coretime auto renewals so that you don't loose the assignment and block production never stops.

We did put together some very simple guidelines for this that you might find useful: https://paseo.site/coretime

[robhyrk]

@al3mart sorry for the delay in getting back. Did our core time simply expire then? I thought it had something to do with our testnet chain being offline. FYI we had been registered as a Parathread so not sure if that's a different assignment in terms of purchasing coretime

[robhyrk]

[robhyrk]

might be an issue with the config just not sure who's end it might be on. in the block explorer I can see that BSR is stuck on this block: 3,017,203

[al3mart]

Hey @robhyrk your chain has coretime assigned to it. I think it would be helpful if you could verify that the state registered for your chain in paras.heads is correct.