Back to Medium Spender
Executed
Requested:
844.65 KSM
#309 Kusama System Parachain Collators - Tips Q4/2023
Proposer:
GCMG...9erp
in Treasury
Beneficiary:(76.88 KSM)&13 more
22nd Nov '23
(Edited)
Description
AI Summary
Votes Bubble
Timeline
Evaluation
On Chain Info
Stats
Quote
Share
Copy
Dear Kusama community,
Collators on System Parachains are provided with minimal rewards for block production and small incentives in terms of transaction fees. This reduces incentives for Collators to act in a favorable manner and they may also be inclined to under-resourcing their hosts to save costs. Collators should receive funding for the provision of their services. Ultimately, this should be provided by the chain in a preferably sustainable manner. Implementation of such a system is a long-term solution. In the medium term, funding for collators can be provided by the respective Treasuries in the form of a bounty. This allows funding to be pre-allocated and independently managed.
This proposal is the final monthly operating costs payment for service providers in Q4 2023. Future cost compensation will be done under the Kusama System Parachain Collators Bounty 20 starting from January 2024.
The proposal aims to secure 844.654 KSM for Collators on the Kusama System Parachains network for services delivered for 3 months - 10-12/2023.
We encourage the Kusama community to review this proposal and provide any feedback or suggestions.
Thank you!
Show More
Please Log In to comment
Users are saying...
Based on all comments and repliesOverall 100 % of users are feeling neutral. The last compensation round on Bridge Hub only covered until August, with September being skipped for collators. A monitoring mechanism similar to Polkadot is hoped for Kusama and Polkadot networks. ChaosDAO members voted in favor without extensive discussion, emphasizing the importance of collective feedback for proposal improvement.
AI-generated from comments
3Comments
0%
0%
50%
0%
50%
CazU...g8Zd
Quote
Share
Copy
We just want to re-iterate the points made for collators on system parachains that was made on Polkadot https://polkadot.polkassembly.io/referenda/288#dna5CUc5AGtWclG1ICAU
Hopefully we get to see a similar monitoring mechanism on Kusama as well as on Polkadot. However, Kusama is the more experimental alpha network we will vote AYE on Kusama's proposal.
Hide replies
GCMG...9erp
Quote
Share
Copy
Thank you for the feedback. In response to these concerns, I will repeat the answers provided on the Polkadot system chain collator proposal that the development and funding of a monitoring solution to address these issues is indeed being considered. This is outlined in Section 6 of the upcoming Bounty proposal describing the plan to implement a system that will monitor and report on the infrastructure used by collators, thereby increasing transparency and helping to mitigate risks.
This proposal does not include development funds beyond the monthly costs associated with collating. The focus is primarily on operational expenses rather than development.
I hope this clarifies the current situation and the steps being taken to improve it. Your vigilance in these matters is greatly appreciated, as it helps us all work towards a more secure and reliable network.
GqC3...m8Jj
Voted Aye
Quote
Share
Copy
The last round of compensation only paid through August, at least on Bridge Hub, so September is being skipped - I collated for some time during that month. Perhaps once the bounty is up we can circle back to September.
I think this is fine, though I would have preferred block-weighted compensation. AYE from me, thanks for putting this together!
EjwQ...214n
Quote
Share
Copy
ChaosDAO would like to provide the following feedback from our community. We offer this feedback voluntarily in the spirit of OpenGov, in order to help teams improve their proposals so we can all build the network together.
- ChaosDAO members voted AYE without substantive discussion
ChaosDAO votes as a collective based on the results of our anonymous internal voting procedures. Our members are not required provide any feedback about why they have voted in a particular direction. Similarly, to respect our members' right to anonymity, we will not be sharing names of individuals who have chosen to voluntarily provide feedback.
Discover similar proposals
#509
E5qF...tqrg
Confirm Started
KSM RFP #1 - Shielded Kusama Hub Transfers - $50k Total Prize!
Quote
Share
Copy
See More
24th Mar '25
Treasurer
Treasurer
#509 KSM RFP #1 - Shielded Kusama Hub Transfers - $50k Total Prize!
E5qF...tqrg
24th Mar '25
Quote
Share
Copy
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
Confirm Started
#511
GUUd...xV2R
Deciding
[Whitelisted Caller] Increase max_validators to 700
Quote
Share
Copy
This referenda increases the parachain validator set size from 600 to 700. The maximum backing group size is kept to 5, so the total number of usable cores increases to 140.
See More
31st Mar '25
Whitelisted Caller
Whitelisted Caller
#511 [Whitelisted Caller] Increase max_validators to 700
GUUd...xV2R
31st Mar '25
Quote
Share
Copy
This referenda increases the parachain validator set size from 600 to 700. The maximum backing group size is kept to 5, so the total number of usable cores increases to 140.
Additionally, also update the setNDelayTranches from 257 to 299, so that the number of assignments per candidate stays constant to around ~2.33, the justification why this is the desired value for this parameter can be found in ELVES https://eprint.iacr.org/2024/961 paper and here.https://github.com/paritytech/polkadot-sdk/issues/6853#issuecomment-2540373492.
See More
Deciding