Polkadot System Parachains Collator Bounty #32 Top-Up Proposal - Jan/2025

Medium Spender
4d ago
4 Comments
Deciding
Content
AI Summary
Reply
Up
Share
Request
21.5KDOT
Status
Decision28d
Confirmation4d
Attempts
0
Tally
100%Aye
0%Nay
Aye
6.6MDOT
Nay
1.2DOT
  • 0.0%
  • 0.0%
  • 0.0%

Threshold

Support0.09%
1.32MDOT
Issuance
1.53BDOT
Votes
Nested
Flattened
Calls
Call
Metadata
Timeline3
Votes Bubble
Statistics
Comments

Hopefully this conversation about invulnerable slots can be continued and not dismissed because this is relevant to the future of Polkadot public execution layers, specially the ones that will expect high transactionality and that expect a revamp in the short term future i.e. Plaza/AssetHub/PolkadotHub. We view this a necessary conversation to have specially if Plaza/AssetHub/PolkadotHub goes live which it’s expected to gather high transactionality and applications right off the bat. For Plaza/AssetHub/PolkadotHub the number of concentrated invulnerable collators within single entities (including Parity) should be reconsidered and even planned for a complete removal likely in favor of 100% permissionless collators (or at least as close to 100% we can move to). This should be kept within the realm of possibilities, discussed and planned in advance, hopefully with a gradual test on Kusama first.

For now we will vote AYE on this Polkadot referendum to maintain the operations on Polkadot uninterrupted but we will move the big discussion about this topic to Kusama and the Polkadot forum so hopefully we hear your participation over there.
https://forum.polkadot.network/t/discontinuation-or-minimization-of-invulnerable-collators-on-system-chainsplaza-assethub-polkadothub/11502

Reply
Up