TLDR: The PDP team has developed a publicly available tool for inspecting parachains and enabling coretime auto-renewal. Simply paste an RPC URL, and the tool will advise on which addresses to fund and prepare all necessary XCM calls.
Try it out now: https://deploypolkadot.xyz/coretime-auto-renewal
Example 1 (Bifrost)
Example 2 (Mythos)
In addition to other exciting features available exclusively to our PDP beta testers (apply to join the next testing cohort!), we’re expanding our public tools, starting with the “Coretime Auto-renewal Guide” page.
Why is this Important?
Every parachain relies on securing a core, and it’s crucial to maintain ownership of a core each cycle. The auto-renewal feature acts like a subscription, ensuring that your core is secured as long as your sovereign account is sufficiently funded. This approach eliminates the risk of losing your core at the start of a cycle. While we plan to support the ecosystem in unforeseen situations by developing new tools for such cases, starting with robust coretime management is key.
How to Enable Auto-renewal?
The interactive guide outlines three major steps to activate this feature:
- Fund the Sovereign Accounts: Ensure the sovereign accounts on the Relay and Coretime chains have enough funds to cover XCM transaction fees and future renewals.
- Set Up an HRMP Channel: Establish an HRMP channel between your parachain and the Coretime chain. The guide will prepare an encoded XCM call for this, which you can review on Polkadot.js or PAPI Console.
- Enable Coretime Auto-renewal: The tool will also prepare the final XCM call required for auto-renewal.
Please note that both XCM calls must be executed from your parachain’s origin. Depending on your parachain’s authorization method, whether using the Sudo pallet or Governance, you may need to wrap the call in a sudo statement or proceed with Governance authorization.
You can find more detailed information in the documentation.
Please let us know what you think.
Happy renewals!