Proposal: Additional Funding for Kusama System Parachain Collators
Bounty #20 KSM address: F3opxRbN5ZbjJNU513biNemEwi2QDYNACcNqzU68jHWZos2
Requested allocation: 4,116.24 KSM
This proposal seeks additional funding to support the operational status and provide a bounty top-up budget for collators on Kusama's System Parachains. Collators are essential for maintaining network security, decentralization, and performance. While previous referenda have successfully provided the necessary resources for their effective operation, additional funds are required to sustain these efforts and adapt to the expanding network demands.
This proposal will focus on the operational status and the bounty top-up budget, while more detailed information can be found under the bounty page and in earlier proposals, as listed below.
Full Proposal: Kusama System Parachains Collator Bounty #20 Top-Up Proposal - Jan/2025
Previous System Chain Collator Related Referenda
The history of initiatives for Kusama System Chain collators dates back to early 2023. They have provided vital support for maintaining the network’s stability, security, and decentralization.
Thank you!
Threshold
This is a continuation of the discussion posted on the Polkadot referendum 1395. We would like to kickstart a discussion for a plan to revamp the invulnerable slots for the 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. Currently, we have a static set of invulnerable collators on all system chains or public chains plus a number of open slots for permissionless validators. These invulnerable collators spent resources and time in the beginning of these system chains and currently are rewarded by bounty 32 and with the invulnerable slots due to the lack of sufficient native fees that will help support operations and due to stability but with the advent of Plaza/AssetHub/PolkadotHub we would like to see that change to a completely permissionless or at least a permissionless maximized approach to collators. That’s why we are inviting comments on the Polkadot forum, on the Polkadot referendum 1395 and the Kusama referendum 487 about potential minimization or discontinuation to this invulnerable set. We envision this as a gradual but constant change given that most execution layers on Polkadot similar to what Plaza/AssetHub/PolkadotHub plans to be i.e. Moonbeam, Astar are quite permissionless when it comes to collators. The same applies to other competing L1s. would also like to hear ideas about changes to this bounty that will allow for that change to happen.
For now we will ABSTAIN on this Kusama referendum to maintain the operations on Kusama uninterrupted and yet open to hear ideas if there are immediate changes that can be done to this bounty in order to kickstart the change towards full permissionlessness on Kusama first. So we will move the big discussion about this topic to 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