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.
#108 Establishing a bounty for Collators of System Parachains.
Dear community,
This proposal seeks to fund collators of the Statemine
network for the duration of 6 months
as a pilot. If passed, a Collator will receive a performance based
, fixed fiat reward of USD$300.00
per month as well a one time reimbursement
for work previously provided. The proposal document was presented to current System Collators as well as Joe (W3F) and Zoltan (Encointer) to their satisfaction.
Additionally, I am taking the opportunity to test assigning a Curator to the bounty within the same proposal as approving it. This is usually undertaken as a separate process because the bounty needs to be approved before it can be assigned a Curator. Let's see how this goes, no time would be lost due to this experiment.
The Curators are namely:
- FrankyWild (
frankywild#8573
) - Tim Jansen (
Tim Janssen (Won't DM)#8682
) - Husni (
pastaMan#9738
)
These individuals are members of the Moderation and Anti-scam teams and also have experience with bounty curation. They have also met the requirements as described within section 5.2 of the proposal.
Summary:
A System Parachain (S.C.) is defined as any Parachain which attained its lease via governance. This proposal aims to establish a framework for Collators on System Parachains to minimise censorship, maintain liveliness and incentivise efficient performance.
It attempts to achieve this by suggesting parameters for the selection, incentivisation and the ideal number of Collators on System Parachains. It is also anticipated that this framework would form a standard that would aid future System Parachains as they are deployed.
As a medium term solution, 1,873.69 KSM is requested to fund a bounty to incentivise Collators on the Statemine network for six (6) months. This would be used as a pilot test and re-evaluated before further funding is provided.
Full proposal
The full proposal can be accessed here.
Discussion
The proposal was left for open discussion for a duration of two weeks and received only one item of feedback.
Regards,
Will | Paradox
Show More
Overall 50 % of users are feeling optimistic. The financial interest proposal aims at fairly compensating Statemine collator operators through network fees for their service to Polkadot and Kusama parachains, with an element of retroactive payment due to free operation in the past year. While acknowledging existing bounties that reward infrastructure builders, there's support for a dedicated curator fund if it ensures diverse participation from around the globe without compromising security needs or over-infrastructural investment given current low usage levels of Statemine and Polkadot Kusama ecosystem....
Overall 28 % of users are feeling neutral. The IBP proposal, while aiming for sustainable unstoppable systems by rewarding validators and collators on common good chains without direct financial incentives like loans or NFTs, faces opposition when it comes to distributing rewards among those who maintain the relay-chain. Concerns about governance models suggest a need for careful consideration of system requirements before deciding on the number of necessary independent collators and addressing potential imbalances between chains with different characteristics like Kusama versus Polkadot counterparts....
Overall 21 % of users are feeling against it. The author criticizes a proposal that suggests collators should support specific validators by running their own operations at loss, arguing it stifles innovation rather than fostering charity within the network. The author also questions transparency and potential conflicts of interest in voting for such proposals while highlighting concerns over large delegates' influence on outcomes due to vested interests tied to collators like Stake Plus being affected by this proposal, which they find alarmingly biased towards certain parties with significant stakes....
AI-generated from comments
Just to be clear, I'm not against the bounty itself I would support it 100% if it had different Curators (they know who they are). It seems like the ecosystem system keeps rewarding backstabbing. Plenty of good people in the ecosystem should get a chance to contribute.
Hello, may I ask what is your specific issue with the curators?
Hey Will,
Thank you for posting the proposal. The proposal audit overview is noted below.
Please note the Audit report is reflecting only the quality of information presented in the proposal and not the Quality of the project/idea itself.
The following proposal Audit is created as a part of Proposal #67.More information about Treasury proposal template and the Audit process can be found on the link above. All templates are free for everyone to use. For any questions or feedback regarding the Audit templates use discussion link from above.
Please note that views and opinions presented in the Audit report are my personal and they do not represent general community opinion. PS. I am using Crust network as ecosystem solution for the storage. Please let me know if the files/links are unavailable.
This could be a fine short term solution but we really should try to figure a long term solution during those 6 months.
I recognise most of these collators to also be validators on Kusama, and I believe that we, as a network, have been accommodating to validators, especially with the recent introduction of the 10% minimum commission. I would assume that under the $34/KSM price point taken for the 10% min. commission argument, the collators in question are running a small profit from their validator operations.
Regarding collators, I see them as a bit of a charity project at the moment and hope that we can implement better long-term solutions. Personally, I find the idea of supporting a specific validator on Kusama by running a collator at a loss compelling. In this way, collators could be supported through the validation efforts (marketing potential for validators).
The proposal actually covers a pretty big time frame as it includes retroactive payments (12 months) as well as the 6 month future payments.
On a separate note, I would have appreciated greater transparency regarding your personal financial interest in this proposal as a collator.
I intend to vote "nay" on this proposal.
What do you mean by financial interest? To put it simply, collators on the system (former common-good) parachains are being paid solely from the network fees (which are basically zero right now) so we tried to come up with a fair way how to get rewarded for our service to the network. There are no other interests than this - and since I and others run Statemine collator for almost a year for free, there's also a request for retroactive payment included.
Interesting comment, are you aware there can be no chain without infrastructure? So it seems unfair to you to cover infra costs + a $100 monthly reward to operators for having chains to exist? FYI a Kusama 100% active validator running at 3% (before the change in minimum commission) have been running at loss for the entire last year, these very validators who allow the chain to exist and run.
Hi, neither Franky nor I run any validators on Kusama and I think neither does Husni. So I don't understand how you could recognize us as validators on Kusama.
Tim Janss... I meant to say collators ofc and not curators. Edited.
Where Validators on the relay-chain have an opportunity to earn rewards those who collate on common-good chains do not have a viable means to earn a return. If we are to develop unstoppable systems we need to think with sustainability in mind. Lending on goodwill or hope of a nomination on another service is imo not sustainable.
Within section 3 of the document you'll find references to other discussions on the topic. For the sake of not repeating all of the options and their pros/cons please read the proposal.
A general point.. It bewilders me that there is usually so much opposition to reward distribution for Validators/Collators and the like when these are the individuals who live a 24/7 on call life to ensure the chains they support operate optimally. We would support NFT systems, Translations and anything else with little resistance but when Validators ask for a commission raise or Collators ask for a reward it is treated as a matter of greed.
Whilst I agree in principal with collators for system parachains not running at a loss - I think we need to take a harder look at the number of collators actually required to provide the necessary censorship resistant characteristics we're after.
On Basilisk and HydraDX we run ~20 collators and this is somewhat higher than many others - I'm not sure that we can say e.g. Statemine needs 20 collators. I would also argue that all system parachains are not equal - 20 collators for e.g. Encointer would be crazy, whereas can easily be argued for the Bridge Hub.
We should also be mindful of # collators (and quality) needed for e.g. Kusama (ded chain) vs Polkadot - Statemint with the coming DEX and integrations with e.g. Circle, Binance, whoever could easily command a decentralised set of professional collators.
I think it's well covered in section 4.5 if you read the detailed proposal - though we didn't reflect any difference between Polkadot and Kusama and I am not sure if it's up to this proposal to judge. Anyways, the main idea is that governance will decide about the most collators that will be onboarded so makes sense for governance to also decide what are the criteria for selecting collators for the particular system chain and how many of them should be there.
These are all valid points, and number of collators might vary depending on the chain. As written in section 4.5, invulnerable and permission-less collator number (15 and 5, respectively) is a suggestion.
I take your points, they are discussed in the document and were discussed at length with the team. The views expressed in the proposal are collective.
As stated in the proposal the ideal number of collators is unknown, we however established the number 20 under general guidance from SR Labs. What is imo more important is that these persons are truly independent. We hope that the application and governance voting in approach works well to helping us solve this
I wholly agree that we may need to look at each system chain's requirement in isolation. There would be a difference between the requirements of Statemine and BridgeHub.
I however disagree that we should treat Kusama as a lesser chain due to volume. Kusama might be prone to Chaos like activity or synthetic loads. With that I would argue that there should always be a minimum likeness between the Kusama and Polkadot counterparts.
Thank you for providing a sensible response.
Voted Aye
I'm extracting some outrageous points for discussion on the main thread just to address them openly.
There were two statements made against the Curators, one issued by Vegas and another issued by Gabriel (now corrected). I am speaking in favour of these individuals; they are each hard working, honest and they have an on-chain record of service. Please put aside personal grievances and keep this factual. To Gabriel's first statement that is now corrected, neither of the Curators are Collators or Validators.
The proposal actually covers a pretty big time frame as it includes retroactive payments (12 months) as well as the 6 month future payments.
On a separate note, I would have appreciated greater transparency regarding your personal financial interest in this proposal as a collator.
The budget is imo very clear and the recipients are well identified. May I ask, what more would you like? Is the "your" referring to me personally? If so why am I singled out?
I of course was talking about collators and not the curators. I do not know these curators and thus don't have an opinion on them.
People will see the proposer to be Paradox and then they will also see a the collator ParaNodes as an affected party in the proposal. For transparency it would have been nice to make the connection there for people that are not aware.
I agree collators are important but this strikes me as an example of where treasury funds may prevent innovation and value creation.
As mentioned above: collators could for example fund their operations through validator activities. By advertising the running of a collator "for charity" one could attract more nominations on Kusama.
Stake Plus is one of the affected collators (beneficiary of this proposal) and also the biggest voter on this track by far (delegated votes with a 70,000KSM weight).
Thus a large part of the current votes are controlled by the affected parties of this proposal (70% with Stake Plus alone if we assume a turnout of 100k KSM) which is rather alarming!
I'm waiting for 3-4 days remaining to cast our vote, acting as a tie breaker in some situations of very close calls, and just simply going with the flow in the majority of cases. I was hopeful that when I started voting with this weight it would bring others into the governance. That hasn't really been the case so far. There are a few that have come out, but not nearly enough.
As is the case with most other proposals we've voted on, we'll cast our vote with 3-4 days remaining and most likely just go with the flow.
Voted Aye
As someone building on Statemine(a use-case of the Virto tech) and planning to run a collator in a poorly covered region this would be beneficial, however I'm not so sure we need this when there's already something like bounty 19 for the infrastructure builders program that from what I understand would already reward collators of the common good chains that achieve certain milestone in the professional track(I'm actually looking forward to participate in the program :))
When you put collators of the program that should be spread around the globe, plus existing ones that already have other means of financing I think we are left with a decent amount(at least for now), remember that collators don't provide security(a single collator can keep things running perfectly fine) and our current user base and the load of a network like Statemine is quite low to need massive infrastructure(dare I say, the usage of the entire Polkadot+Kusama ecosystem is so low that a few nodes in a single parachain would probably handle everything just fine ;P).
As a member of the IBP, where we already host boot and rpc nodes for all common good parachains, I would prefer to see this included in IBP. I will abstain on this one.
Voted Aye
I appreciate the invitation and suggestion of including this under the IBP. While I am sure existing collators would all appreciate receiving grants ($15k+$15k) for hardware, I think there's better value attained from the proposed model. The IBP is afaik designed to fund parties for provision of RPC and Bootnodes (Infrastructure) and not for collation on said chains.
As it relates to selection of members, existing members were selected in a permission-less manner and the proposal seeks to elect collators by means of governance (see section 4.5). Imposing members of the IBP as collators is certainly something that is not desired. Members of the IBP are free to participate and I'm sure a decentralized use-case would speak to their favour.
The proposal speaks towards the determination of the ideal number of Collators and what we are trying to achieve with the framework. You are correct that the security of the network is provided by the relay-chain and the ideal number of Collators is unknown. As I responded to lolmcshizz, we are following guidance from SR Labs and they suggested 20.
Just for general clarity, if there are 2 collators on Statemine and a block time of 12s, if one should fail then the block time increases to 24s. Stretching this to 20 collators, if one collator fails then the block time is 12.6s. There are also other considerations why 'a few' may not be desired which are again all discussed in the proposal.
Voted Aye
Please note that the bounty was approved but the curators were not assigned. To assign curators the bounty must first be funded, the funding of the bounty actually occurs per-spend-period and not immediately upon approval.
Hello,
We are in the process of validating a true need for a service to assist teams with crafting and completing successful treasury proposals, so they can focus on building. We would love to hear about your experience with this proposal. If you are willing to take a few minutes, please fill out this form about your experience with the OpenGov treasury proposal process: https://forms.gle/MwDij4adXEQd7Um79
Feel free to leave out any details that your team is not comfortable with sharing, but the more info you can provide, the better we will be able to assess the potential need for our services.
For more info, follow us on Twitter/X: https://twitter.com/OpenGovAssist
Discover similar proposals
Remove Gabe from the fellowship
See More
Fellowship Admin
Fellowship Admin
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.
Invarch failed to provide the first two, so Gabe, a founding member of the team, does not meet the ethical standards required to have a voice in the Fellowship.
TENETS (extract from the fellowship manifesto)
"Members are expected to faithfully uphold the following tenets.
Clarifications to the rules should be in agreement with these tenets. Acting in clear breach of these tenets may be considered by voters as grounds for non-promotion, demotion or, in extreme cases, exclusion from the Fellowship.
(1) Sincerely uphold the interests of Polkadot and avoid actions which clearly work against it.
(2) Respect the philosophy and principles of Polkadot.
(3) Respect the operational procedures, norms and voting conventions of the Fellowship.
(4) Respect your fellow Members and the wider community"
See More
KSM RFP #1 - Shielded Kusama Hub Transfers - $50k Total Prize!
See More
Treasurer
Treasurer
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