Kusama Coretime Renewal

Hey everyone!

I wanted to share that it’s time for the first teams to renew their cores on Kusama. The renewal window opened today at the Coretime chain block 284,039 and will last until the Coretime chain block 334,439.

It is important to know that all the parachains that have a running core now, still have it until the end of this region, independently of renewing or not. Renewing is executed in advance, affecting the following cycle.

Cores allowed for Renewal

The following list contains the cores eligible for renewals and important information about them. Each entry shows which core can be renewed, what paraID is currently assigned to that core (with the corresponding paraName where available), as well as what is the renewal price. Finally, it has the first timeslice at which the region of that core begins (*).

If your team is on this list, and you want to renew your core, you have to do it before Coretime chain block 334,439. Otherwise, the core will be offered in the open market, where you can still buy it (for the open market price vs the renewal price).

List

[
  {
    paraName: 'Integritee',
    paraID: 2015,
    coreIndex: '11',
    price: '5 KSM',
    regionBegin: '295,848 (in timeslice)'
  },
  {
    paraName: 'Parallel Heiko',
    paraID: 2085,
    coreIndex: '16',
    price: '5 KSM',
    regionBegin: '295,848 (in timeslice)'
  },
  {
    paraName: 'Altair',
    paraID: 2088,
    coreIndex: '18',
    price: '5 KSM',
    regionBegin: '295,848 (in timeslice)'
  },
  {
    paraName: 'Kintsugi',
    paraID: 2092,
    coreIndex: '20',
    price: '5 KSM',
    regionBegin: '295,848 (in timeslice)'
  },
  {
    paraName: 'GM',
    paraID: 2123,
    coreIndex: '30',
    price: '5 KSM',
    regionBegin: '295,848 (in timeslice)'
  },
  {
    paraName: 'Amplitude',
    paraID: 2124,
    coreIndex: '31',
    price: '5 KSM',
    regionBegin: '295,848 (in timeslice)'
  },
  {
    paraName: 'InvArch Tinkernet',
    paraID: 2125,
    coreIndex: '32',
    price: '5 KSM',
    regionBegin: '295,848 (in timeslice)'
  },
  {
    paraName: 'NA',
    paraID: 2233,
    coreIndex: '34',
    price: '5 KSM',
    regionBegin: '295,848 (in timeslice)'
  },
  {
    paraName: 'Quantum',
    paraID: 2274,
    coreIndex: '38',
    price: '5 KSM',
    regionBegin: '295,848 (in timeslice)'
  },
  {
    paraName: 'NA',
    paraID: 2275,
    coreIndex: '39',
    price: '5 KSM',
    regionBegin: '295,848 (in timeslice)'
  },
  {
    paraName: 'NA',
    paraID: 3347,
    coreIndex: '49',
    price: '5 KSM',
    regionBegin: '295,848 (in timeslice)'
  },
  {
    paraName: 'NA',
    paraID: 3348,
    coreIndex: '50',
    price: '5 KSM',
    regionBegin: '295,848 (in timeslice)'
  }
]

(*) A timeslice is a unit of time that was configured to consist of 80 blocks, and it correlates to the block height at the relay chain. In order to understand to which block height at the relay chain the timeslice corresponds, one must do timeslice * 80. So for a core which Region begins at timeslices 295,848, that correlates to block height 23,667,840 on Kusama.

How to renew your core

Any account can renew a core, it doesn’t have to be a specific account tied to the core or to the paraID. The steps to achieve this, are:

  1. Teleport KSM to the Coretime Chain. Both Lastic and RegionX have tooling available to do this.
  2. Call the broker.renew(core_index) method on the Coretime Parachain. This extrinsic requires only the core_index as a parameter, which you can find on the list above. This can be done on PolkadotJS Apps, and also again RegionX and Lastic have tooling to do this.

After a successful extrinsic execution, your core will be renewed. This renewal affects goes into effect the following cycle, not the current one.

Renewals going forward

Going forward, there are two main efforts to reduce the burden on having to renew a core on each sale cycle. Namely:

  • A coretime renewal Bot, which is closed to be finished. This can be found here.
  • Integration of a subscribe functionality on the broker pallet directly. This is being implemented here.

Last remarks

Remember that you need to renew your core before Coretime chain block 334,439 in order to make use of the renewal price. Otherwise, the core will be offered on the open market, where it must be purchased at the open market price.

Please post any questions on this thread if help is needed.

14 Likes

I truly appreciate the exceptional communication, timely updates, and detailed guidance your team has provided with the Coretime feature. The renewal process was incredibly smooth and seamless, making the entire experience really good.

Could you please add the Coretime metadata to the metadata portal? Unfortunately, neither Novasama nor Parity hosts this information, preventing the Polkadot Vault from being used with it. Adding this metadata would greatly enhance its usability and benefit all users.

5 Likes

Good catch re: the metadata, we’ll bring it up :slight_smile:

1 Like

So far we have seen renewals from Centrifuge, Interlay and Integritee :cowboy_hat_face:

https://x.com/itsbirdo_/status/1793236843703447965

2 Likes

GM – we will add the Coretime chain to https://metadata.novasama.io/ shortly - thanks for the report!

4 Likes

Hi, that branch has been merged with main so that link is now broken, you can retrieve the bot from here!

1 Like

Updated the link on the post, thanks Beto!

2 Likes

@santi also big thanks from me. Renewal was smooth. Looking forward to doing renewals with that renewal bot in the future.

Just one question: after the renewal: I see that I can renew again starting at block 300,888. How come? Should the next renew cycle only start at the beginning of cycle 2, i.e., 28 days after block 295,848?

1 Like

What you are looking at is expressed in Timeslice not in blocks (Source Code), and it shows until when you have an available core on Kusama. A unit of Timeslice is configured in itself to be 80 blocks.

So in this case, the Timeslice=300_888 equates to block height 24_071_040 on Kusama, meaning that you have a valid core for this current cycle, and for the following one. For renewing, you need to renew in the next cycle (which is your last one), to have a valid core for the one after that.

I made an updated timeline on how this would look like. You can see that now the “yellow dot” that represents until when your parachain has a core assigned, has moved to the end of c1 as you just renewed it.

3 Likes

That’s an important clarification. Coincidentally also block 295,848 of the coretime chain was authored this week and so I just figured that the number 295,848 refers to a coretime block height instead of a timeslice.

1 Like

Very coincidentally :sweat_smile: