Polkassembly Logo

OpenGov
This proposal was still in progress when Polkassembly was archived. The status shown here is frozen and may not reflect the final on-chain outcome.
View All Staking Admin

Polkadot Asset Hub — Invulnerable Collator Set Adjustment

inStaking Admin
23 days ago
Deciding

Dear community,

This referendum seeks to adjust the invulnerable collator set of Polkadot Asset Hub.

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 Asset Hub is categorised as a Tier-1 chain, with 8 funded community invulnerable collators.

For Polkadot Asset Hub, the proposed configuration is:

  • Tier: Tier 1
  • Community-funded invulnerable collators: 8
  • Permissionless collator slots: 4

This referendum performs the following changes.

Collators being added

  • ExtraCoin / Yaron — 12EXTrrfo9LTbK7ToB5XekXJysjoWCg3SyqgAMaFpXyXHQUF

Collators being removed

  • LuckyFriday — 15MV2nX6BEoiBz8Ua2xNta19sVBKT7kiw2MEHdu2Jd9a4VaC
  • Stake Plus — 15dikXxF1QwijxxU7wZBFmHy7HeCotHXa1LxzVu44KVKXCRC

Collators retained

The following community invulnerables are already in place and remain part of the final Asset Hub set:

  • ParaNodes — 16WWmr2Xqgy5fna35GsNHXMU7vDBM12gzHCFGibQjSmKpAN
  • STKD — 1gkGXWr2wr1CqYCKqGHRRsBhL9iCmTy7ubwVgeys4m4tJwQ
  • BESTVALIDATOR / Zurich — 14T3MFxNa4d7pyjRAdKU6tLC8sfde1HBLGNMHKCMFqjWRrrM
  • Iceberg Nodes — 14icei1ZMoG9QtKBFDk4y1eMR756q2TREuRAi2BanJ9MJVPL
  • Staker Space — 14wQoaBqk718MgNxp3qdpqHnEgmTTmTkcVnYuxMWWvYr3DXb
  • DPSTK / Dapestake — 14xSXydBVvuMMaNduDXwWcckt3BziSB8Sa7o34Jt9z2aMGxX
  • Turboflakes — 167xwLzY4z3uNBMQSdDJmPnLgPKBY1SRsvQXbyaeHcnwd4um

Final community invulnerable set

  • ParaNodes — 16WWmr2Xqgy5fna35GsNHXMU7vDBM12gzHCFGibQjSmKpAN
  • STKD — 1gkGXWr2wr1CqYCKqGHRRsBhL9iCmTy7ubwVgeys4m4tJwQ
  • BESTVALIDATOR / Zurich — 14T3MFxNa4d7pyjRAdKU6tLC8sfde1HBLGNMHKCMFqjWRrrM
  • Iceberg Nodes — 14icei1ZMoG9QtKBFDk4y1eMR756q2TREuRAi2BanJ9MJVPL
  • Staker Space — 14wQoaBqk718MgNxp3qdpqHnEgmTTmTkcVnYuxMWWvYr3DXb
  • DPSTK / Dapestake — 14xSXydBVvuMMaNduDXwWcckt3BziSB8Sa7o34Jt9z2aMGxX
  • Turboflakes — 167xwLzY4z3uNBMQSdDJmPnLgPKBY1SRsvQXbyaeHcnwd4um
  • ExtraCoin / Yaron — 12EXTrrfo9LTbK7ToB5XekXJysjoWCg3SyqgAMaFpXyXHQUF

Best Regards,
Will | Paradox | ParaNodes.io

Comments (1)

22 days ago

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.

Voting Period

Decision Period

23 / 28 days

Confirmation Period

0 / 3 hours

Help Center

Report an Issue
Feedback
Terms and Conditions
Github

Our Services

Docs
Terms of Website
Privacy Policy

Polkassembly · Archived 2026 · polkassembly.io

Terms and ConditionsTerms of Website
Privacy Policy