In Cycle X do we need to call renew as well? or it can be automatically switched from parachain slot to a coretime cycle?
The renewal price in X+1 (for keeping the core in X+2) equals to the last core sold out in Cycle X right? and in X+2 we need to pay 3% extra in order to keep the core in X+3?
(1) no you should only need to call renew in X + 1.
(2) Almost the price for renew in X+1 is already determined in X, so based on the sellout price of X-1.
This is not correct. When you lease ends in cycle X, you will have the core until end of cycle X. So, you basically get some free coretime. However, with the start of cycle X you will need to renew your core to still have it in X + 1.
Indeed. Sorry about that, @bkchr is right. What brings the confusion is that your lease disappears from storage one cycle earlier. That is why the cycle where your lease vanishes in the UI is not the one where you need to renew, but the one after.
I updated the article accordingly. Thanks @bkchr for the correction!
Moonriver renewed for the first time (last week) and while it is currently assigned core 11, it looks like in the next cycle, it will be assigned core 35. If we renewed core 11, why will is it switching? Is this something that will happen every time or does this have something to do with switching from the old model to the new?
You can renew your core during the entire last cycle you have a core on. However during the first part (Interlude) you can renew without competition; after that if anyone buys all cores before you, then it can buy yours as well. This Interlude is 50_400 blocks (of the coretime chain) in length. This value is not measured in Timeslices.
*This chart is a simplification, only for illustration purposes of the different phases. Price discovery works differently than what’s shown here.
Yes, when you renew you get a new core assigned for the next period. This will always be the behavior. I can see here that you guys renewed your core, and that you are also allowed to renew on the next cycle:
Bumping this to list teams that must renew their cores on Kusama in the next 15 days if they want to continue producing blocks.
Team
ParaID
Core Number
DAO IPCI
2222
38
Genshiro
2024
12
Robonomics
2048
41
t1rn
3334
28
InvArch
2125
45
Please do re-check if your team is listed here and also if your team is not listed here. On this thread there’s information on what to do to renew, but do let me know if anything!
It actually makes a lot of sense that they didn’t renew their current core, as the renewal price, as shown on the UI, is much higher compared to their new core.
Also, to mitigate these types of renewal issues, we recently published a proposal that would address this problem by notifying when to renew or warning when Coretime isn’t allocated and a parachain is about to stop. Coretime Notifications | Polkassembly
Yes, I believe this is the case. Otherwise, people could buy up cores and renew indefinitely without actually using them blocking anyone else from purchase.
For a long time, we have been focused on developing the RegionX parachain, which implements a Coretime marketplace and other related functionality. We have been adding many features to the frontend; however, we are now in a state to perform a cleanup. We recently also started to migrate to an improved design.
Feedback is highly appreciated, and you can send it to my Telegram (handle: Szegoo). We are aware of some minor UX issues, and they are on our to-do list, but we are currently unaware of any more critical ones, so we would greatly appreciate your feedback.
Does anyone know when the auto-renewal feature is supposed to be ready? I know we’ll have to do something on the parachain side but I think there’s a Polkadot SDK dependency or something…
There’s a couple of fixes that need to happen before enabling coretime auto renewals, but AFAIK, it’s e okay to expect that this will be available after next upgrade (NET late December).
See runtimes#490 for more details on the incoming upgrades.