Polkadot Coretime — Invulnerable Collator Set Adjustment
Dear community,
This referendum seeks to adjust the invulnerable collator set of Polkadot Coretime.
The main objective is to make the invulnerable set better aligned with the risk profile and importance of the respective System Chain, while also keeping the assignment process efficient and consistent across the programme.
The curators also considered the historical assignment of slots across the System Chains. Where possible, the revised assignments favour operators with longer tenure and a demonstrated record of providing reliable service. At the same time, the changes are intended to help even the field for operators who have shown capability and interest in supporting additional System Chains.
Finally, this referendum adjusts the number of permissionless collator slots to ensure that permissionless collators do not outweigh the intended invulnerable set.
To support this, the curators applied a tiering model where each System Chain is categorised from Tier 1 to Tier 3, based on its perceived importance and risk profile. Under this model, Polkadot Coretime is categorised as a Tier-2 chain, with 4 funded community invulnerable collators.
For Polkadot Coretime, the proposed configuration is:
- Tier: Tier 2
- Community-funded invulnerable collators: 4
- Permissionless collator slots: 2
This referendum performs the following changes.
Collators being added
- Chris-Staking —
14fbxKv81FF9wxyidiD4jrYokbF428KJBrB5DsgipQp6Yrmm - MegaTron / Eric —
13oz8fEwz7TmpoAnozbHAfCG2L5uWdVmDq7cjY5Aw2CBW5Cj - HYPERSPEED —
15cu9qomrRvnqkvnSMhPPkBp9359QDbGBy1bVo3tseozxhj
Collators being removed
- MathCrypto —
112FKz5UNxjXqe3Wowe73a8FHnR5B4R9qi2pbMaXJczGNJsx - Previous invulnerable —
1k4vuCxwbNcHfsNdQ3MgTGixwvrT7wbLc2XiZj68Gru6bLM - openbitlab —
12iho9gjSMvF9smJjnihmn9j9Qqr3S1LFD97e8Lkcw4R6Yeb - Stakeworld —
13Jpq4n3PXXaSAbJTMmFD78mXAzs8PzgUUQd5ve8saw7HQS5
Collators retained
The following community invulnerable is already in place and remains part of the final Coretime set:
- STKD —
173Wc3mSdXa9ja9nv7C1z6GQHEBK4HZ9U4NGhHnvmTfJaJb
Final community invulnerable set
- STKD —
173Wc3mSdXa9ja9nv7C1z6GQHEBK4HZ9U4NGhHnvmTfJaJb - Chris-Staking —
14fbxKv81FF9wxyidiD4jrYokbF428KJBrB5DsgipQp6Yrmm - MegaTron / Eric —
13oz8fEwz7TmpoAnozbHAfCG2L5uWdVmDq7cjY5Aw2CBW5Cj - HYPERSPEED —
15cu9qomrRvnqkvnSMhPPkBp9359QDbGBy1bVo3tseozxhj
Best Regards,
Will | Paradox | ParaNodes.io
Comments (1)
Proposal Passed
Looking at the five proposals together, I’m a bit concerned about the level of concentration.
Across these 5 System Chains, we have 30 funded collator slots, but only 22 unique operators. 8 operators hold 2 slots each, meaning they account for 16/30 slots (53.3%).
If we look only at the three Tier-1 System Chains (Asset Hub, Bridge Hub and People), 7 operators hold 14 out of 24 slots (58.3%).
I understand the argument for rewarding operators with a proven track record. Reliability obviously matters for System Chains.
But at some point, repeatedly allocating multiple funded slots to the same operators also creates concentration and makes it harder for new operators to enter the programme.
I think it would be worth discussing whether we should have some kind of limit per operator, or at least a clearer mechanism to balance operational experience with decentralisation and diversity of operators.
Otherwise, we risk creating a system where the same small group keeps rotating between the different System Chains.
Polkassembly is now a read-only archive. Commenting is disabled.