zec
/
zips
mirror of https://github.com/zcash/zips.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

cap in my view wouldn't be to prevent large projects that s

This commit is contained in:
Skylar Saveland 2024-07-05 11:21:33 -07:00
parent 2bfb8b72e3
commit d5703123d3
No known key found for this signature in database
GPG Key ID: A7270BD7AA2E5344
2 changed files with 11 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
draft-nuttycom-funding-allocation.html
View File

@ -105,7 +105,7 @@ Pull-Request: &lt;<a href="https://github.com/zcash/zips/pull/866">https://githu
<section id="guidance-on-future-requirements-for-alternative-1"><h4><span class="section-heading">Guidance on Future Requirements for Alternative 1</span><span class="section-anchor"> <a rel="bookmark" href="#guidance-on-future-requirements-for-alternative-1"><img width="24" height="24" class="section-anchor" src="assets/images/section-anchor.png" alt=""></a></span></h4>
<p>To support the motivations outlined, the following guidance is proposed for Alternative 1. Future ZIP(s) will define the disbursement mechanism. These are suggestions to achieve the outlined motivations that should be considered in those future ZIP(s):</p>
<ol type="1">
<li><strong>Cap on Grants</strong>: Grants should be capped to prevent any single project from depleting the lockbox funds rapidly. This ensures long-term availability of funds for various projects. Additionally, capping grants necessitates more granular definitions of work, goals, milestones, KPIs, and achievements, requiring that work be confirmed and approved in smaller, more manageable increments.</li>
<li><strong>Cap on Grants</strong>: Grants should be capped to promote more granular accountability and incremental goal-setting. This approach ensures that projects are required to define their work, goals, milestones, KPIs, and achievements in smaller, more manageable increments. Even if a single project is utilizing significant funds quickly, the cap ensures that progress is continuously evaluated and approved based on tangible results and alignment with community priorities.</li>
<li><strong>Decentralized Disbursement Mechanism</strong>: The disbursement mechanism should be sufficiently decentralized to ensure the regulatory motivations are fulfilled. A decentralized mechanism could reduce the need for recipients to undergo KYC with a controlling party, preserving privacy and aligning with the ethos of the Zcash project.</li>
<li><strong>Governance and Accountability</strong>: The governance structure for the disbursement mechanism should be open and accountable, with decisions made through community consensus or decentralized voting processes to maintain trust and accountability. This approach will help ensure that the allocation of funds is fair and aligned with the community's evolving priorities.</li>
<li><strong>Periodic Review and Adjustment</strong>: There should be provisions for periodic review and adjustment of the funding mechanism to address any emerging issues or inefficiencies and to adapt to the evolving needs of the Zcash ecosystem. This could include the ability to add or remove participants as necessary. Regular assessments will help keep the funding model responsive and effective, ensuring it continues to meet the community's goals.</li>
@ -181,7 +181,7 @@ Pull-Request: &lt;<a href="https://github.com/zcash/zips/pull/866">https://githu
<li>ZCG Committee members SHALL have a one-year term and MAY sit for reelection. The ZCG Committee is subject to the same conflict of interest policy that governs the FPF Board of Directors (i.e. they MUST recuse themselves when voting on proposals where they have a financial interest). At most one person with association with the BP/ECC, at most one person with association with the ZF, and at most one person with association with FPF are allowed to sit on the ZCG Committee. “Association” here means: having a financial interest, full-time employment, being an officer, being a director, or having an immediate family relationship with any of the above. The ZF SHALL continue to operate the Community Advisory Panel and SHOULD work toward making it more representative and independent (more on that below). Similarly, FPF should also endeavor to establish its own means of collecting community sentiment for the purpose of administering ZCG elections.</li>
<li>A portion of the ZCG Slice shall be allocated to a Discretionary Budget, which may be disbursed for expenses reasonably related to the administration of the ZCG program. The amount of funds allocated to the Discretionary Budget SHALL be decided by the ZF’s Community Advisory Panel or successor process. Any disbursement of funds from the Discretionary Budget MUST be approved by the ZCG Committee. Expenses related to the administration of the ZCG program include, without limitation the following:
<div>
<h1>System Message: ERROR/3 (draft-nuttycom-funding-allocation.rst line 501)</h1>
<h1>System Message: ERROR/3 (draft-nuttycom-funding-allocation.rst line 502)</h1>
<p>Unexpected indentation.</p>
</div>
<ul>
@ -209,14 +209,14 @@ Pull-Request: &lt;<a href="https://github.com/zcash/zips/pull/866">https://githu
<section id="transparency-and-accountability"><h3><span class="section-heading">Transparency and Accountability</span><span class="section-anchor"> <a rel="bookmark" href="#transparency-and-accountability"><img width="24" height="24" class="section-anchor" src="assets/images/section-anchor.png" alt=""></a></span></h3>
<p>FPF MUST accept the following obligations in this section on behalf of ZCG: * Publication of the ZCG Dashboard, providing a snapshot of ZCG’s current</p>
<div>
<h1>System Message: ERROR/3 (draft-nuttycom-funding-allocation.rst line 575)</h1>
<h1>System Message: ERROR/3 (draft-nuttycom-funding-allocation.rst line 576)</h1>
<p>Unexpected indentation.</p>
</div>
<blockquote>
<p>financials and any disbursements made to grantees.</p>
</blockquote>
<div>
<h1>System Message: WARNING/2 (draft-nuttycom-funding-allocation.rst line 576)</h1>
<h1>System Message: WARNING/2 (draft-nuttycom-funding-allocation.rst line 577)</h1>
<p>Block quote ends without a blank line; unexpected unindent.</p>
</div>
<ul>

13
draft-nuttycom-funding-allocation.rst
View File

@ -304,12 +304,13 @@ Alternative 1. Future ZIP(s) will define the disbursement mechanism. These
are suggestions to achieve the outlined motivations that should be considered
in those future ZIP(s):
1. **Cap on Grants**: Grants should be capped to prevent any single project
from depleting the lockbox funds rapidly. This ensures long-term
availability of funds for various projects. Additionally, capping grants
necessitates more granular definitions of work, goals, milestones, KPIs, and
achievements, requiring that work be confirmed and approved in smaller, more
manageable increments.
1. **Cap on Grants**: Grants should be capped to promote more granular
accountability and incremental goal-setting. This approach ensures that
projects are required to define their work, goals, milestones, KPIs, and
achievements in smaller, more manageable increments. Even if a single
project is utilizing significant funds quickly, the cap ensures that
progress is continuously evaluated and approved based on tangible results
and alignment with community priorities.
2. **Decentralized Disbursement Mechanism**: The disbursement mechanism should
be sufficiently decentralized to ensure the regulatory motivations are