<p>This document lays out standards which shall apply to all bounties funded through Polkadot OpenGov. The basic intention is to ensure that minimum standards are upheld before a budget is granted. It defines how these executive bodies should handle budgeting, transparency, and compliance.</p>
<h2 id="1bountyobjectives">1. Bounty Objectives</h2>
<ol>
<li>Bounties shall have a clearly defined list of objectives by which their success can be judged by the community.</li>
<li>Funds may only spent within the boundaries of the objectives for which the funds were requested.</li>
</ol>
<h2 id="2funding">2. Funding</h2>
<ol>
<li>Bounties may request funding at a maximum of one time per quarter.</li>
<li>Funding requests must include
<ol style="list-style-type: lower-alpha;">
<li>Budget breakdown: The budget has to give an honest picture of the intended spending and be broken down into positions. Positions should be explained in sufficient detail.</li>
<li>Timeframe: The timeframe should give clarity to OpenGov when it can expect the next funding request.</li>
<li>Transparency reports that cover past activities up to the time of the request.</li>
</ol>
</li>
<li>A funding request has to be put up for discussion in any of the established governance platforms or the Polkadot forum for at least 2 weeks before it is put to a vote.</li>
</ol>
<h2 id="3curators">3. Curators</h2>
<ol>
<li>All curators must have a verified on-chain identity.</li>
<li>Payment terms of curators must be outlined in the funding request. If curators shall receive payment, including for prior work, it has to be defined in the payment terms.</li>
<li>Curators may not sign payments for work that they have executed, except curator compensation.</li>
<li>Curators must not claim compensation for work that they already have been compensated for otherwise.</li>
<li>Curators have to publicly declare and document any conflicts of interest that come up during their duty.</li>
<li>Curators have to publicly report any misbehavior or other issues that conflict with the effective and efficient operation of the bounty.</li>
</ol>
<h2 id="4recipients">4. Recipients</h2>
<ol>
<li>All recipients must have a verified on-chain identity.</li>
<li>Recipients must not claim compensation for work that they already have been compensated for otherwise.</li>
</ol>
<h2 id="5transparency">5. Transparency</h2>
<p>Bounties are required to provide the following materials for transparency:</p>
<ol>
<li>Official public communication channel where curators are regularly available and the public can participate</li>
<li>Regularly updated official overview page
<ol style="list-style-type: lower-alpha;">
<li>Objectives</li>
<li>Main contact point</li>
<li>Link to the public communication channel</li>
<li>A list of all current curators</li>
<li>Links to all progress summaries and all other transparency materials listed below</li>
<li>Links to relevant documentation</li>
<li>Link to current child bounties h. Guidance for executors on how to participate in the bounty</li>
</ol>
</li>
<li>Spending Policy, including how curators are compensated</li>
<li>A table of child bounties that contains: status, name, description, amount, beneficiary username, beneficiary address, links to evidence. The table is available in an open format (XLSX, CSV, or similar)</li>
<li>Monthly progress summary posted to the bounty page, signed off by at least one curator
<ol style="list-style-type: lower-alpha;">
<li>Current status of projects</li>
<li>Current bounty balance</li>
<li>Current plans d. Notable changes to objectives, curation team, operations, etc.</li>
</ol>
</li>
<li>Quarterly financial statement
<ol style="list-style-type: lower-alpha;">
<li>Balance</li>
<li>Income and Expenses</li>
<li>Summary of curator payments</li>
<li>Summary of payments by recipient</li>
<li>available in an open format (XLSX, CSV or similar)</li>
</ol>
</li>
</ol>
<p>&nbsp;</p>
<h1 id="appendix">Appendix</h1>
<p>These are additional questions we have received and considerations we have discussed. They are not included in the on-chain proposal (to keep the proposal minimal) and are intended to help you interpret the intention of the proposal.</p>
<p>&nbsp;</p>
<h2 id="bountyobjectives">Bounty Objectives</h2>
<h3 id="wouldastrategybeconsideredthedefinedobjectives">Would a strategy be considered the defined objectives?</h3>
<p>A strategy is much bigger. Objectives are the first part of a strategy. So yes, a proper strategy contains objectives. However, a list of objectives doesn't yet make a strategy.</p>
<p>&nbsp;</p>
<h3 id="shouldntabountybeabletochangeitsobjectives">Shouldn't a bounty be able to change its objectives?</h3>
<p>Yes. Bounties need to be able to adapt to changing circumstances. However, if a bounty promises to do work to achieve a certain goal it should not take the granted money and do something different with it. If it wants to change what the money is designated for, it should have to request a change.</p>
<p>Likewise, it is easy for a bounty to change the objectives for future funding, because it is submitting a funding request anyways. In the context of requesting new funding, it can also communicate changed objectives.</p>
<p>&nbsp;</p>
<h3 id="shouldtherebesuccessmetrics">Should there be success metrics?</h3>
<p>In general it would be very helpful to measure against hard metrics. The problem is that it is really hard to arrive at reasonable metrics and very often people come up with bad metrics just so that they can provide KPIs. We have chosen to not include a requirement for metrics yet, because the ecosystem as a whole is not yet mature enough to have agreed on the right metrics. A good first step is to start finding the metrics that make sense before prescribing that metrics have to be used.</p>
<p>&nbsp;</p>
<h3 id="shouldabountyenddatebedefined">Should a bounty end date be defined?</h3>
<p>In the past, OpenGov has shown to just close bounties when they stopped performing. We don't think this has to be explicitely defined.</p>
<p>&nbsp;</p>
<h2 id="funding">Funding</h2>
<h3 id="willbountiesbedeniedfundingiftheydontfollowtherulesoutlinedinthisdocument">Will bounties be denied funding if they don't follow the rules outlined in this document?</h3>
<p>It is still up to OpenGov, but the idea is that OpenGov shall question bounties that do not provide these things. We suggest OpenGov denies funding requests if proper scoping and transparency criteria are not fulfilled.</p>
<p>&nbsp;</p>
<h3 id="whyshouldafundingrequestcontainabudgetbreakdownwithspecificdetailsarentthedetailsalreadyprovidedwiththeobjectives">Why should a funding request contain a budget breakdown with specific details? Aren't the details already provided with the objectives?</h3>
<p>The objectives long-term and generic in nature. The quarterly budget is focused on specific projects. It might touch only some of the objectives or with different priorities. It is more specific. The idea is to communicate specific plans for how the money is used, not some general ambitions.</p>
<p>&nbsp;</p>
<h2 id="transparency">Transparency</h2>
<h3 id="summaryanddetails">Summary and Details</h3>
<p>There are 2 parts to transparency: summary and details</p>
<ul>
<li><strong>For the casual observer, getting a quick overview summary is important.</strong> For them, the answer cannot be that they can "look it up in a table, drive folder, meeting notes, or on-chain". Casual observers are the majority of the participants. For the casual observer, short summaries are important. Auditors need summaries to save time.</li>
<li><strong>For the transparency nerd, detail is important.</strong> For them (and auditors), being able to verify all the claims given in summaries is crucial. Bonus points if it is structured data to allow automation to take place.</li>
</ul>
<p>When we talk about transparency, both aspects are needed: summary and details.</p>
<p>&nbsp;</p>
<h3 id="buttransparencycreatesextrawork">But transparency creates extra work</h3>
<p>Yes, dealing with other peoples money requires making it transparent what you did with the money.</p>
<p>&nbsp;</p>
<h3 id="simpleandshortisfine">Simple and short is fine</h3>
<p>You don't need a dedicated website. Updating the description on the bounty pages in governance explorers like Subsquare/Polkassembly is very much fine. It even helps casual observers find your information quickly.</p>
<p>The same is true for summaries, reports, etc. Keep them short and simple and save everyone time.</p>
<p>&nbsp;</p>
<h3 id="overviewpage">Overview Page</h3>
<p>The overview page can be a the Subsquare/Polkassembly page, a dedicated website, Notion page or similar. See examples below:</p>
<p>Events Bounty</p>
<ul>
<li>Linktree: <a href="https://linktr.ee/dotevents_">https://linktr.ee/dotevents_</a></li>
<li>Website: <a href="https://dotevents.xyz/">https://dotevents.xyz/</a></li>
</ul>
<p>UX Bounty:</p>
<ul>
<li>Notion Page: <a href="https://braille-wtf.notion.site/UX-Bounty-Homepage-WIP-167a1782242e477bbb9f7a066ef447dd">https://braille-wtf.notion.site/UX-Bounty-Homepage-WIP-167a1782242e477bbb9f7a066ef447dd</a></li>
</ul>
<h3 id="quarterlyfinancialstatements">Quarterly Financial Statements</h3>
<p>Financial statements should provide detailed explanations and metrics of bounty operations. See examples below:</p>
<p>Events Bounty</p>
<ul>
<li><a href="https://docs.google.com/document/d/1Y8DuYnXpNuGJYALjJSUJ83ogJypWoOrL2df1_6XTfYc/edit?tab=t.0#heading=h.tv09ho3qoge">https://docs.google.com/document/d/1Y8DuYnXpNuGJYALjJSUJ83ogJypWoOrL2df1_6XTfYc/edit?tab=t.0#heading=h.tv09ho3qoge</a></li>
</ul>
<p>PAL</p>
<ul>
<li><a href="https://github.com/polkadot-assurance-legion/pal-docs/blob/main/community-reports/pal-24h1.md">https://github.com/polkadot-assurance-legion/pal-docs/blob/main/community-reports/pal-24h1.md</a></li>
</ul>
<p>&nbsp;</p>
<h3 id="monthlysummaries">Monthly summaries</h3>
<p>Summaries can be short bullet point summaries that gives the general idea of progress for public oversight, they dont have to be as detailed as quarterly reports.</p>

Make some on-chain remark.

Can be executed by every `origin`.

- **Problem Statement & Audience:** Establishing standards for bounties funded through Polkadot OpenGov to ensure transparency and compliance with funding requests, targeting the Polkadot community and governance platforms.
- **Significance:** Ensuring that bounties have clear objectives, transparent funding requests, and accountable curators and recipients to maintain integrity and efficiency in budget allocation.
- **Proposed Solution:** Implementing guidelines for bounty objectives, funding requests, curator responsibilities, recipient accountability, and transparency reports to enhance governance and financial oversight.
- **Expected Outcomes & Value proposition:** Improved transparency, accountability, and efficiency in managing bounties through standardized processes and reporting, fostering trust and effective resource allocation within the Polkadot ecosystem.

#1254 Bounty Compliance Standards 1.0

No Active Proposals