With parachains now transitioning from the slot auction model to the Coretime model, there must be a simple way to track lease expiry and act upon it by renewing Coretime to ensure that the parachain’s operations do not stop.
Without this, we risk some parachains not renewing on time due to a lack of information or encountering mistakes during the renewal process.
However, the Coretime and lease expiry data should be tracked not only by the parachain teams but also by their users, who might be less technical. It is important for users to be able to track this in a clear and transparent way so they can act if they see that the parachain team is not handling the transition and procurement process.
These are the main reasons why we consider having a clear dashboard that allows for this data to be tracked and acted upon to be important for the ecosystem.
With Corehub parachain dashboard, our goal is to facilitate the transition to the new Coretime model for existing parachain teams. Additionally, once transitioned, we aim to simplify the ‘maintenance’ of these projects by offering tools to monitor Coretime expiry and provide a straightforward way to enable renewal.
This is the main purpose of the Corehub parachain dashboard.
However, Given that RegionX already offers a user-friendly UI for Coretime procurement, management, and consumption tracking, we also decided to add a UI for parachain ID reservation and registration as the final steps of the deployment process on Polkadot. This way, the Corehub UI covers the final steps of parachain deployment.
With this, we can also simplify and ease the deployment process for parachains on Polkadot.
The full proposal can be found here: https://docs.google.com/document/d/1q-xzS2O3b5WdqiE9sguHd0q5JQYTL1s56M-m7qC3pmY/edit?usp=sharing
Threshold