Members of the Fellowship Collective involved in projects flagged by the OG tracker should provide a proper explanation, return the funds to the Treasury, or face expulsion.
Back to Big Spender
Executed
Requested:
4.12K KSM
#487 Kusama System Parachains Collator Bounty #20 Top-Up Proposal - Jan/2025
Description
AI Summary
Votes Bubble
Timeline
Evaluation
On Chain Info
Stats
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.
- Referendum 108: Establishing a Bounty for Collators of System Parachains, February 2023
- Referendum 273: Bridge Hub Collator Compensation for June, July, and August, September 2023
- Referendum 275: Bridge Hub Collator Compensation for June, July, and August, September 2023
- Referendum 309: Kusama System Parachain Collators - Tips Q4/2023, November 2023
- Referendum 322: Funding of Kusama System Parachain Collators, December 2023
- Referendum 445: Bounty Top-Up of the System Parachain Collators Funding on Kusama, August 2024
Thank you!
Show More
Please Log In to comment
Users are saying...
Based on all comments and repliesOverall 66 % of users are feeling optimistic. Kus DAO has unanimously voted for approval, emphasizing their commitment to network stability, security, and scaling Parachain systems within Polkadot's ecosystem. They are actively seeking involvement through invitations on Discord or Telegram while advocating fair distribution of collator slots via a WFC system like DN for enhanced decentralization in the chain governance structure.
Overall 33 % of users are feeling neutral. A user sought clarification regarding a specific issue within the context of Polkadot Bounty, as documented in referendum #1395 on their platform. The query was subsequently addressed by another participant or moderator who provided guidance and information pertinent to resolving the question posed about this particular topic related to bounties on Polkadot's network.
AI-generated from comments
4Comments
0%
0%
50%
50%
0%
HLsP...91LP
Polkadot's system chains are controlled by a small number of operators, with just four holding 33% of the 139 system collators. These big operators run 3 invulnerable spots each (where no deposit is required and spot is guaranteed) and increase the bids in permissionless spots in order to kick new validators who want to make the ecosystem more decentralised.
https://docs.google.com/spreadsheets/d/161nT5NWLF0s1lGlOLPttuFAESkjwA6zDMG6znTEDc64/edit?usp=sharing
A WFC is needed at a protocol level in order to have a fair distribution of invulnerable collator slots and increase descentralization in the system chains with a rotating a system like DN.
GCMG...9erp
(Edited)
The same comment was posted on Polkadot Bounty and answered there:
https://polkadot.polkassembly.io/referenda/1395#2XQ1Flx2LjUCZIdEG6dg
HcEb...jJ5F
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.
EFQV...Siag
Kus DAO have voted AYE (first voting).
✅ Critical for network stability, security, and scaling system parachains.
❌ None.
💪 Get involved: 🔗 Discord Invite or Telegram Invite
💬 Join the discussion: 🔗 Discussion Thread
Discover similar proposals
#509
E5qF...tqrg
Deciding
KSM RFP #1 - Shielded Kusama Hub Transfers - $50k Total Prize!
See More
Treasurer
Treasurer
#509 KSM RFP #1 - Shielded Kusama Hub Transfers - $50k Total Prize!
E5qF...tqrg
This RFP was adapted over several weeks on AAG to turn a treasury proposal in discussion to an RFP with refined scope and oversight.
To apply for the prize pls fill out this form.
Prize Pool: $43,000
Finder’s Fee: $2,000 **
Supervisors: $5,000
Supervisors (Bounty Curators)
- Flipchan
- Byte (Erin)
- James Slusser
Excess or unused funds will be returned to the treasury by Bounty Curators.
Timeline
Monday, March 17 - AAG Discussion & this forum post! ✅
Monday, March 24 - Single-ref Bounty + Curators ✅
4 Weeks after Bounty Funding - Submission Deadline Thursday
July 31 - Project Completion (Pending Kusama Hub Launch)
Project Scope
Smart Contract Development
- A Solidity-based smart contract deployed on Kusama Hub
- ZK enabled for private deposits & withdrawals
- Compatibility with all Kusama Hub assets
User Interface
- Browser-based, mobile-ready UI hosted on IPFS
- Support for: Deposits, Withdrawals, Transfers, XCM Transfers
- Compatible with popular ecosystem wallets (Nova Wallet, Talisman, Subwallet)
Anti-correlation Attack Mitigations:
- Fixed deposit amounts (e.g. 1, 10, 100, 1000 units)
- Batch payouts for withdrawals to multiple users
Interoperability - Ability to receive assets via XCM from any Kusama-connected parachain and transfer them to Kusama Hub for use in shielded pool.
Open-Source Delivery
- All code (smart contracts and UI) published under the MIT license
- Publicly accessible repositories Project updates shared transparently via Polkassembly, Subsquare, or Polkadot Forum from Team with Milestone deliveries
- Developer & User documentation
Milestones
Milestone 1, Initial Pools & Basic UI:
$16,200 USD
1 month
- Tests - Smart contract test
- Smart contract - ZK shielded smart contract with KSM and multi asset support on Westend or Paseo
- Basic UI - A basic UI for interacting with the smart contract
Milestone 2, UI + XCM:
$9,900
1 month
- Tests - tests for all features
- User interface design - UI design
- XCM transfers - XCM transfer assets in UI
- Fixed amount transfer only - Allow fixed amount transfers in the UI
Milestone 3, Mainnet Deployment:
$16,900
1 - 1.5 months
- Contract Migration to Kusama Assethub - Migrate contract from Testnet to Kusama Hub
- Public documentation - Documentation for using Kusama shield and developer integration documentation
- Test - tests for contract
- V1 UI - User tested & something we can be proud of
** re: Finder’s Fee: this payment is set aside to incentivize a broad search for the right implementor. Finder’s Fees are paid out at time of team engagement. Teams that submit themselves can collect their own Finder’s Fee at completion of project.
See More
Deciding
