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.
#144 Infrastructure Maintenance Bounty Top-up request
After delivering a report showcasing the child bounties approved at the community request, we aim to request a top-up of the Infrastructure maintenance bounty, which works to aid teams that have been funded by the treasury before for the development of their ideas, to maintain infrastructure and perform continued operations to reduce the work or to resubmit the treasury proposals and time constraints associated with it, as well as model a way in which the community can achieve more agency and support in directing how on-chain treasury funds are spent. The bounty has been running for roughly a year now and has helped fund multiple infrastructure proposals, whose details can be found in the spreadsheet here.
This follow-up top-up will enable us to continue with our efforts as well.
Details of this proposal, including what we have achieved so far, our future goals, and an estimated breakdown of the requested top-up, can be found in the proposal document.
Show More
Overall 100 % of users are feeling neutral. 001723456, 8923 days ago. Teacher: In a recent study on the impacts of climate change on crop yields in the Midwest region of India during the period from 1960 to 1960. The researchers have found that the average temperature and precipitation levels were significantly lower than they are today, with an increase in rainfall variability (P < 25%), which could potentially lead to: Answer:
AI-generated from comments
Could you explain to me like i'm 10, the ROI thesis of this large instrastructure spending?
Is there for example a point where this spending moves towards a law of diminishing returns?
Is there a basic level that needs sustaining that keeps the lights on?
Given the spending to date from the treasury on infrastructure (a very broad category that also includes wallets etc) and relatively little use of said infrastructure, is there an argument to be made that this spending could be reduced in favour of other areas more directly aligned with driving on-chain adoption of the ecosystem?
Genuinely interested in your assessment.
The asking amount here is substantial (8% of the treasury)!
This comes at a time where as a community we are looking at measures to protect the treasury from depletion. A spending of this amount would blow any projections of treasury depletion out of the water.
I am grateful that this proposal forces us to address the issues of a depleting treasury with utmost urgency.
I look forward to the discussion and the results that come out of it.
In the meantime I will be voting against the proposal to offer resistance to the currently unchallenged vote (46k KSM ayed within 15 minutes). I hope this encourages more debate around treasury issues. My vote is not final.
Voted Aye
Hello there,
To those voting NAY citing a depleted Treasury, I invite you to look into two Treasury proposals that have borrowed 72,000 KSM from the Kusama Treasury and are expected to repay [some of it] back to the Treasury at the beginning of Q3 2023:
Thank you for your time.
Edit: It would also help if NAY voters could reframe the amounts requested in the current context of high inflation experienced across developed and developing economies altogether.
Edit 2: According to this comment, only 50,000KSM + interest will be refunded.
It is very alarming to me that a funding request of this dimension only has 3 comments on it after 5 days of being on-chain...
Do we just not care anymore?
Why is this not on Polkadot?
Why the 12 month period and not a shorter funding cycle?
Hi Gabriel, thanks for pushing the discussion. But I think all of your questions have been answered in the proposal document (at least that is how I read it), but let me summarise it :
-
Yes, we, as a community, should care a lot, especially when it comes to core infrastructure providers. These providers are instrumental in providing essential services such as block explorers, governance forums, applications, snapshots, and validator services. As a community, it is essential that we support and encourage their work by providing sufficient funding in a timely manner to ensure the continued functioning of these critical services.
-
The document suggests that there may be plans to propose a bounty on Polkadot in the near future, which is a positive development. Yet, it is important to mention that while Kusama and Polkadot are related, they are two distinct networks. So, it may not be the most optimal solution to fund the entire Kusama's public infrastructure with Polkadot tokens.
-
Since the beginning, the Bounty has proven to be well-performing by funding reliable public infrastructure for the Kusama ecosystem (I have cross-checked on Subsquare for every child bounty, as this is the platform the curator team seems to be using, not Polkassembly), so allocating a portion of the Treasury to Bounty pot on an early bases sounds reasonable thing to do. Furthermore, I do not understand what added benefit the treasury with the shorter funding cycle would bring (Elaboration would be super appreciated). Based on my understanding and the conversations I had, it would cause quite the opposite result. If we want a proper infrastructure, it is important that Treasury would still have to continue funding those maintenance proposals, whether it be through bounty or referenda. Yet, by moving those tokens from the Treasury pot to the Bounty pot, we are doing a better job of decreasing the number of KSM that will be burned to Society's pot at the end of every spending period (according to wiki). I strongly believe that Society should not be the ultimate recipient of those tokens. So this seems like an acceptable short-term decision until someone makes those changes.
Voted Aye
As the bounty curator, I would like to address the concerns raised by some community members regarding the Infrastructure Maintenance Bounty proposal. It is essential to understand that the platform we all use to discuss proposals is heavily reliant on services funded by bounties like this one. For instance, RPC service providers such as OnFinality and Dwellir, explorers like SubScan and DotScanner, and governance platforms like SubSquare and dotTreasury, all depend on the funding provided by the Infrastructure Maintenance Bounty as it is visible in the proposal document.
These services are vital for the smooth functioning of the ecosystem and drive on-chain adoption. Reducing the funding for such critical infrastructure services may not be the best course of action, as it could potentially hinder the growth and development of the ecosystem.
I urge everyone to exercise common sense when evaluating this proposal and to avoid engaging in a meaningless and counterproductive witch hunt. The Infrastructure Maintenance Bounty has been successfully running for about a year now, providing valuable support to various projects. This follow-up top-up will allow us to continue our efforts and further strengthen the ecosystem.
It is essential to have open discussions about the treasury's depletion concerns, but we must also recognize the value that this proposal brings to the community and the projects it supports.
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