Upgrade Coretime system chain to 1.6.0 and 100 cores

13aY...tTp6

Whitelisted Caller

6d ago

Executed

Content

AI Summary

Description

There are two changes proposed here:

A runtime upgrade of Coretime system chain to 1.6.0.
Increasing the number of cores from 66 to 100.

The runtime upgrade is meant to fix the current Coretime situation on Polkadot. It does this by the following:

We configure a minimum price of 10 DOT, to prevent prices to drop to unreasonable low values, which cause the system to take forever to recover in case demand picks up.
Renewals are now no longer completely decoupled from the market, but will be adjusted to cost at least the end price of the current sale. Immediate effect will be that renewals will be adjusted to the minimum price too.

Details are outlined in https://github.com/polkadot-fellows/RFCs/pull/149.

Some fellowship members had a call with all parachain teams describing changes of RFC-149 in detail and from what I know they were on board and want the coretime issue get fixed.

The enactment block of the proposal was chosen to be https://polkadot.subscan.io/block/26803000.
Note however, that both changes will take place in the next sale period after the enactment, which is around July 25/26.

Build

opengov-cli build-upgrade --network polkadot --only --coretime "1.6.0"
# modify the build call to 0x630004000100b50f04082f0000060202eb4353e21a0600a428020800095b5a86cc8055e729b7b8660f2f551d8bfe6712b24d2e637a0624444addcc8d2e32128c00
opengov-cli submit-referendum \
    --proposal "0x630004000100b50f04082f0000060202eb4353e21a0600a428020800095b5a86cc8055e729b7b8660f2f551d8bfe6712b24d2e637a0624444addcc8d2e32128c00" \
    --network "polkadot" --track whitelistedcaller --at 26803000

Edited

Status

Decision28d

Confirmation

10mins

Attempts

Tally

100%Aye

76.4%Threshold

0%Nay

Aye

≈149.6MDOT

Nay

40,017DOT

0.0%
0.0%
Threshold
0.0%

Support

8.10%

≈128.03MDOT

Issuance

≈1.58BDOT

Votes

Nested

Flattened

Actions

Check how referenda works here.

Call

Metadata

Timeline6

Votes Bubble

Statistics

Comments

15aS...xNK3

It would appear based on the RFC pull request that this does more than simply, "increases the number of cores from 66 to 100". Can that be clarified in the proposal text? Were critical ecosystem partners consulted about the potential impacts of these changes?

13zn...P5ju

Dear Proposer,

Thank you for your proposal. Our first vote on this proposal is AYE.

The Whitelisted Caller track requires 60% quorum according to our voting policy v0.2, and any referendum in which the majority of members vote abstain receives an abstain vote. This proposal has received eight aye and zero nay votes from ten available members. Below is a summary of our members' comments:

The majority of voters expressed strong support for the referendum, indicating that they believed it would benefit Polkadot and its parachains. Many participants conveyed their enthusiasm with simple affirmations or enthusiastic comments, emphasizing the lack of reasons to oppose the measure. Overall, the sentiment was overwhelmingly positive, with all voters casting their votes in favor of the proposal, reflecting a unified belief in its potential advantages.

The full discussion can be found in our internal voting.

Please feel free to contact us through the links below for further discussion.

Kind regards,
Permanence DAO
Decentralized Voices Cohort IV Delegate

📅 Book Office Hours
💬 Public Telegram
🌐️ Web
🐦 Twitter
🗳️ Delegate