## Bounty Standards This document outlines the standards applicable to all bounties funded through Polkadot OpenGov, detailing how these entities evolve and manage budgeting, transparency, and compliance. ### 1. Bounty Scope and Operations - **Defined Scope**: Bounties must have a clearly defined scope and a list of objectives for community assessment. Existing bounties have a 3-month grace period to establish and approve this via a WFC proposal. - **Budget Compliance**: Funds may only be spent within the defined scope and objectives. Any changes in scope or curator team require WFC referendum approval. - **Operational Setup**: A 3-month grace period is allowed for operational setup. If no activities occur within this timeframe, the community may request the bounty to be shut down or modified. ### 2. Funding - **Top-Up Requests**: Bounties may request a maximum of one funding top-up per quarter. - **Budget Submission**: Funding requests must include a detailed budget outlining intended use of funds and any required transparency reports up to the request date. - **Discussion Period**: Top-up requests must be discussed on established governance platforms or the Polkadot forum for at least 2 weeks before voting. ### 3. Transparency Bounties are required to provide the following to OGTracker.io: - **Overview Page/Website**: Including scope, objectives, main contact point, public communication links, and curator list. - **Expense Reports**: Monthly expense reports must include verifiable receipts, purchase orders, invoices, block transaction IDs, or transaction records. - **Progress Reports**: Monthly written reports must be submitted to OGTracker.io and posted on the Polkadot Forum Governance section, covering project status, bounty balance, plans, and notable changes. - **Financial Statements**: Quarterly financial statements detailing balance, income/expenses, curator payments, and available in open formats (XLSX, CSV). ### 4. Curators - **Compensation Plans**: Curators must disclose compensation plans in detail for community consideration and approval. Payments to curators are permitted only after first deliverables are completed. - **Curator Payments**: If it is deemed necessary to compensate a curator after the bounty has been approved, the bounty must have community approval through a treasury referendum before engaging that curator or making any commitments. - **Prohibitive Use of Child Bounties**: Filing and approving Child Bounties to compensate curators of the Parent Bounty is strictly forbidden and a violation of the Bounty Standards and Policies. Curators or participants found violating this standard will not be allowed to participate in OpenGov activities. - **Conflict of Interest (COI)**: Curators must declare any conflicts of interest publicly and report any misbehavior impacting bounty operations. ### 5. Conflict of Interest (COI) Policy - **Purpose**: Ensure transparency and accountability in curatorial decision-making. - **Disclosure Requirements**: Curators must disclose potential conflicts to OpenGov.Watch before participating in discussions or votes related to their interests. - **Recusal Procedures**: Curators with disclosed conflicts must recuse themselves from relevant voting and discussions. - **Consequences for Non-Disclosure**: Failure to disclose conflicts may result in immediate removal from curatorial positions. ### Conclusion These standards aim to enhance clarity, accountability, and efficiency within the bounty system under Polkadot OpenGov.Watch. Regular reviews and community feedback will ensure these standards remain relevant and effective. Sources [1] 9991 [WFC Draft] Bounty Standards - Polkadot Assembly https://polkadot.polkassembly.io/forum/t/wfc-draft-bounty-standards/9991 [2] [WFC Draft] Bounty Standards - Governance - Polkadot Forum https://forum.polkadot.network/t/wfc-draft-bounty-standards/9991 [3] Introduction to Polkadot OpenGov - Kusama Guide https://guide.kusama.network/docs/learn-polkadot-opengov [4] Polkadot-JS Guides about Bounties · Polkadot Wiki https://wiki.polkadot.network/docs/learn-guides-bounties [5] Polkadot-JS Guides about Bounties - Kusama Guide https://guide.kusama.network/docs/learn-guides-bounties [6] OpenGov | Polkadot https://polkadot.com/opengov [7] Bug bounty vs penetration testing: Costs, scope and methodologies https://blog.intigriti.com/business-insights/penetration-testing-vs-bug-bounty-programs [8] Treasury · Guide https://guide.kusama.network/docs/learn-polkadot-opengov-treasury