<h1><a href="#radworks-grant-application"></a>Radworks Grant Application</h1>
<blockquote>
<p>This document will be part of the terms and conditions of your agreement and therefore needs to contain all the required information about the project. Don't remove any of the mandatory parts presented in bold letters or as headlines! Lines starting with a <code>&gt;</code> (such as this one) can be removed.</p>
<p>See the <a href="https://github.com/radicle-dev/radicle-grants#process">Grants Program Process</a> on how to submit a proposal.</p>
</blockquote>
<ul>
<li><strong>Project Name:</strong> Name of your project (e.g. DevDAO Module)</li>
<li><strong>Team Name:</strong> Legal/Proper name of your team (e.g. Developer DAO)</li>
<li><strong>Payment Address:</strong> must be <em>ERC20 (Ethereum)</em> compatible wallet or multi-sig address</li>
<li><strong><a href="https://github.com/radicle-dev/radicle-grants#grant-categories">Category</a>:</strong> Core Infra OR Radicle Adoption</li>
</ul>
<blockquote>
<p> <em>The combination of your GitHub account submitting the application and the payment address above will be your unique identifier during the program. Please keep them safe.</em></p>
</blockquote>
<h2><a href="#project-overview-page_facing_up"></a>Project Overview </h2>
<p>If this application is in response to an RFP, please indicate this on the first line of this section.</p>
<p>If this is an application for retroactive funding (i.e. work that is completed and committed into a codebase), please drop any related PRs in this section.</p>
<h3><a href="#overview"></a>Overview</h3>
<p>Please provide the following:</p>
<ul>
<li>If the name of your project is not descriptive, a tag line (one sentence summary).</li>
<li>A brief description of your project.</li>
<li>An indication of how your project relates to / integrates into Radicle.</li>
<li>An indication of why your team is interested in creating this project.</li>
</ul>
<h2><a href="#team-busts_in_silhouette"></a>Team </h2>
<h3><a href="#team-members"></a>Team members</h3>
<ul>
<li>Name of team leader</li>
<li>Names of team members</li>
</ul>
<h3><a href="#contact"></a>Contact</h3>
<ul>
<li><strong>Contact Name:</strong> Full name of the contact person in your team</li>
<li><strong>Contact Email:</strong> Contact email (e.g. <a href="mailto:person@dev.com">person@dev.com</a>)</li>
<li><strong>Website:</strong></li>
</ul>
<h3><a href="#legal-structure"></a>Legal Structure</h3>
<ul>
<li><strong>Registered Address:</strong> Address of your registered legal entity, if available. Please keep it in a single line. (e.g. Main Street 1, London N17LJ, United Kingdom)</li>
<li><strong>Registered Legal Entity:</strong> Name of your registered legal entity, if available. (e.g. Developer DAO Ltd.)</li>
</ul>
<h3><a href="#teams-experience"></a>Team's experience</h3>
<p>Please describe the team's relevant experience.</p>
<p>If your project involves development work, please single out a few interesting projects or contributions made by team members in the past.</p>
<p>For research-related grants, references to past publications and projects in a related domain are helpful.</p>
<p>If anyone on your team has applied for a grant at Radicle or elsewhere, please share info on that here.</p>
<h3><a href="#team-code-repos"></a>Team Code Repos</h3>
<ul>
<li><a href="https://github.com/">https://github.com/</a>&lt;your_organisation&gt;</li>
<li><a href="https://github.com/">https://github.com/</a>&lt;your_organisation&gt;/&lt;project_1&gt;</li>
<li><a href="https://github.com/">https://github.com/</a>&lt;your_organisation&gt;/&lt;project_2&gt;</li>
</ul>
<p>Please also provide the GitHub accounts of all team members. If they contain no activity, references to projects/repos hosted elsewhere are also fine.</p>
<ul>
<li><a href="https://github.com/">https://github.com/</a>&lt;team_member_1&gt;</li>
<li><a href="https://github.com/">https://github.com/</a>&lt;team_member_2&gt;</li>
</ul>
<h3><a href="#team-linkedin-profiles-if-available"></a>Team LinkedIn Profiles (if available)</h3>
<ul>
<li><a href="https://www.linkedin.com/">https://www.linkedin.com/</a>&lt;person_1&gt;</li>
<li><a href="https://www.linkedin.com/">https://www.linkedin.com/</a>&lt;person_2&gt;</li>
</ul>
<h2><a href="#project-description-page_facing_up"></a>Project Description </h2>
<p>Please describe why you are applying for this grant.</p>
<h2><a href="#deliverables-nut_and_bolt"></a>Deliverables </h2>
<p>Please list the deliverables of the project in as much detail as possible. Please also estimate the amount of work required and try to divide the project into meaningful milestones.</p>
<ul>
<li><strong>Total Estimated Duration:</strong> Duration of the whole project</li>
<li><strong>Full-time equivalent (FTE):</strong> Amount of time (in days) required for a single person to complete this project (<a href="https://en.wikipedia.org/wiki/Full-time_equivalent">see</a>)</li>
<li><strong>Total Costs:</strong> Amount of Payment in USD for the whole project.</li>
</ul>
<blockquote>
<p>️ ❗<em>The more you can organize your milestones into manageable chunks that are conducive to iteration, the better!</em></p>
</blockquote>
<h3><a href="#milestone-1"></a>Milestone 1</h3>
<p>Please add additional milestones in the same way:</p>
<ul>
<li><strong>Estimated Duration:</strong> Duration of milestone 1</li>
<li><strong>FTE:</strong> Amount of time (in days) required for a single person to complete this milestone</li>
<li><strong>Costs:</strong> Amount of Payment in USD for milestone 1</li>
</ul>
<table>
<thead>
<tr>
<th>Number</th>
<th>Deliverable</th>
<th>Specification</th>
</tr>
</thead>
<tbody>
<tr>
<td>1.</td>
<td>Title of the deliverable</td>
<td>Please describe the deliverable here as detailed as possible</td>
</tr>
<tr>
<td>2.</td>
<td>...</td>
<td>...</td>
</tr>
</tbody>
</table>
<h3><a href="#milestone-2"></a>Milestone 2</h3>
<p>Please add additional milestones in the same way:</p>
<ul>
<li><strong>Estimated Duration:</strong> Duration of milestone 2</li>
<li><strong>FTE:</strong> Amount of time (in days) required for a single person to complete this milestone</li>
<li><strong>Costs:</strong> Amount of Payment in USD for milestone 2</li>
</ul>
<table>
<thead>
<tr>
<th>Number</th>
<th>Deliverable</th>
<th>Specification</th>
</tr>
</thead>
<tbody>
<tr>
<td>1.</td>
<td>Title of the deliverable</td>
<td>Please describe the deliverable here as detailed as possible</td>
</tr>
<tr>
<td>2.</td>
<td>...</td>
<td>...</td>
</tr>
</tbody>
</table>
<h2><a href="#future-plans"></a>Future Plans</h2>
<p>Please include the following:</p>
<ul>
<li>How you intend to use, enhance, promote and support your project in the short term</li>
<li>The team's long-term plans and intentions in relation to it. In other words, how will it be made sustainable?</li>
</ul>
<blockquote>
<p>️ ❗<em>This is a good place to share how you might like to get more grant funding for future work</em></p>
</blockquote>
<h2><a href="#additional-information-heavy_plus_sign"></a>Additional Information </h2>
<p><strong>How did you hear about the Grants Program?</strong> Medium / Twitter / Discord / Announcement by another team / personal recommendation / etc.</p>
<p>Here you can also add any additional information that you think is relevant to this application but isn't part of it already, such as:</p>
<ul>
<li>Work you have already done.</li>
<li>If there are any other teams who have already contributed (financially) to the project.</li>
<li>Previous grants you may have applied for.</li>
</ul>

Radworks Grant Application   Radworks Grant Application 
 
 This document will be part of the terms and

Radworks Grant Application

<h1><a href="#governance-manual-v02"></a>Governance Manual [v0.2]</h1>
<blockquote>
<p> This document describes the current governance processes of the RadicleDAO. It is version-controlled and can only updated via off-chain approval. It’s currently maintained <a href="https://github.com/ethereum-optimism/Operating-manual">here</a> on Radicle.</p>
</blockquote>
<blockquote>
<p> For more on how this document is maintained please refer to contributing.md</p>
</blockquote>
<h1><a href="#overview"></a>Overview</h1>
<p>The RadicleDAO is governed by on-chain and off-chain governance processes. These together make up Radicle’s <strong>governance system.</strong> It’s on-chain governance can be referred to as the DAO’s <em><strong>governance module.</strong></em></p>
<h3><a href="#on-chain"></a>On-chain</h3>
<p>The RadicleDAO’s Treasury is controlled by a tokenized governance mechanism (<a href="https://wiki.tally.xyz/docs/compound-governor">Compound-Governor</a>) via the project’s native governance token ($RAD). As members of the RadicleDAO,  $RAD holders participate in the decision-making around the treasury by voting and creating on-chain governance proposals composed of executable actions.</p>
<p>Currently, these actions include:</p>
<ul>
<li>Treasury distributions of assets (e.g. RAD, ETH, and USDC)</li>
<li>Upgrades to the on-chain governance system (Compound Governor)</li>
<li>Changes to parameters of Treasury-governed contracts (e.g. Drips)</li>
</ul>
<p>To learn more about token governance and how the RadicleDAO’s on-chain governance system works, <a href="https://wiki.tally.xyz/docs/compound-governor">see here</a>.</p>
<h3><a href="#off-chain"></a>Off-chain</h3>
<p>In addition to the on-chain governance system, the RadicleDAO manages a set of off-chain processes and resources that define the rules for participating in the DAO. These processes and resources are maintained off-chain, but updates to these documents still require formal community approval via Snapshot vote.</p>
<p>See Proposal Process for more info.</p>
<h2><a href="#governance-toolkit"></a><strong>Governance Toolkit</strong></h2>
<p>The primary tools for The RadicleDAO governance are:</p>
<ul>
<li><strong><a href="https://snapshot.org/#/opcollective.eth">Snapshot</a></strong>: Where all Formal Reviews are submitted for vote.</li>
<li><strong><a href="https://radicle.community/">radicle.community</a>:</strong> A community forum for discussion about governance proposals and topics.</li>
<li><strong><a href="https://discord-gateway.optimism.io/">Discord</a></strong>: For governance announcements and informal governance discussion.</li>
</ul>
<p>Additional tools for voting and proposal making can be found here.</p>
<h2><a href="#proposal-process"></a>Proposal Process</h2>
<p>A Radicle Governance Proposal (RGP) can be proposed on-chain by anyone who has an amount of $RAD greater than or <strong>equal to 1% of total total supply delegated</strong> to their address. RGPs must be formally labeled in the following format: e.g. <code>RGP-1</code></p>
<p>To submit an EGP on-chain, it must first complete <strong>an off-chain review process</strong>. Having a public off-chain review process allows for proposals to be reviewed, discussed, and improved by the Radicle community before reaching an on-chain vote. It also provides on-chain voters with more context on community sentiment and proposal development which ideally leads to more informed and less contentious decisions. Ultimately, involving the community in the public review and development of the proposal is also a way to protect the RadicleDAO, ensuring that what makes its way to an on-chain vote has already been vetted and reviewed in a transparent manner.</p>
<p>See Proposal Cycles for a timeline of governance processes.</p>
<h3><a href="#proposal-types"></a>Proposal Types</h3>
<p>All proposals are considered a RGP. There are three main categories of RGPs:</p>
<table>
<thead>
<tr>
<th>Type</th>
<th>Description</th>
<th>Process</th>
</tr>
</thead>
<tbody>
<tr>
<td>Executable</td>
<td>On-chain actions such as treasury distributions, updates to contract parameters, and upgrades to governance system.</td>
<td>Discussion → Formal Review → Submission</td>
</tr>
<tr>
<td>Social</td>
<td>Changes that can not be enforced by the DAO on-chain (e.g. updates to Governance Manual)</td>
<td>Discussion → Formal Review</td>
</tr>
<tr>
<td>Consensus</td>
<td>Ad-hoc changes that “should” have community approval, but aren’t classified by an Executable or Social proposal</td>
<td>Discussion → Formal Review</td>
</tr>
</tbody>
</table>
<p>Each proposal type has a designated <a href="https://www.notion.so/Proposal-Template-Library-e8b3408c8c0a4c2d8288629f183a5f54">template</a>.</p>
<h3><a href="#proposal-cycles"></a>Proposal Cycles</h3>
<p>The RadicleDAO manages proposals in <strong>monthly cycles</strong> to sync voting periods and establish a manageable cadence for governance participants.</p>
<table>
<thead>
<tr>
<th>Monthly Schedule</th>
<th>Stage</th>
<th>Weekly Schedule</th>
<th>Action</th>
</tr>
</thead>
<tbody>
<tr>
<td>Week 1</td>
<td>Discussion</td>
<td>First Monday</td>
<td>Post proposal to forum for Discussion*</td>
</tr>
<tr>
<td>Week 2</td>
<td>Discussion</td>
<td>Second Wednesday</td>
<td>Join monthly Governance Call to present and discuss proposal with community</td>
</tr>
<tr>
<td>Week 3</td>
<td>Formal Review</td>
<td>Third Monday</td>
<td>Open proposal for Formal Review</td>
</tr>
<tr>
<td>Week 4</td>
<td>Submission</td>
<td>Fourth Monday</td>
<td>Submit proposal on-chain</td>
</tr>
</tbody>
</table>
<p>*<em>Proposals can be posted to the forum for Discussion at anytime throughout the monthly cycle, but requires at least 7 days on the forum to be considered for that month’s voting cycle</em></p>
<h3><a href="#voting-thresholds"></a>Voting Thresholds</h3>
<p>Once proposed, participants can vote for/against the proposal on-chain with their RAD. An RGP is <strong>approved</strong> if it satisfies the following minimum vote thresholds:</p>
<ul>
<li>
<p><strong>Quorum:</strong> The minimum number of total RAD votes required to be cast in connection with a proposal. Quorum is currently measured as <em><strong>a % of the total RAD supply.</strong></em> The required quorum to pass a proposal is <strong>4% (4M RAD) of total supply (100M RAD)</strong></p>
<p><em><strong>Formal Reviews</strong></em> and <em>Submissions</em> are required to meet quorum requirements.</p>
</li>
<li>
<p><strong>Approval Threshold:</strong> If quorum is met, the proposal passes if a majority of the votes are “in-favor”.</p>
</li>
</ul>
<p>*<em>Proposals can be posted to the forum for Discussion at anytime throughout the monthly cycle, but requires at least 7 days on the forum to be considered for that month’s voting cycle</em></p>
<p>**<em><strong>Submission triggers a 3-day voting period. If passed, the proposal is queued for 48hrs, then it can be executed.</strong></em></p>
<h2><a href="#voting"></a>Voting</h2>
<p>Voting requires Radicle (RAD) tokens, which you can <a href="https://docs.radicle.xyz/docs/connecting-to-ethereum/obtaining-rad">obtain here</a>. One RAD token is equal to one vote. Voting takes place both on- and off-chain:</p>
<ul>
<li><strong>Formal Reviews:</strong> <em>Off-chain</em> consensus checks done with <a href="https://snapshot.org/#/gov.radicle.eth">Snapshot polls</a>.</li>
<li><strong>Submissions:</strong> <em>On-chain</em> voting for RGPs take place on <a href="https://gov.radicle.network/#/delegates/radicle">gov.radicle.network</a>.</li>
</ul>
<p>You can keep track of all open proposals and vote directly on the <a href="https://boardroom.io/radicle/overview">Radicle Governance Portal</a> 🌱</p>
<h3><a href="#voting-thresholds-1"></a>Voting Thresholds</h3>
<p>Once proposed, participants can vote for/against the proposal on-chain with their RAD. An RGP is <strong>approved</strong> if it satisfies the following minimum vote thresholds:</p>
<ul>
<li>
<p><strong>Quorum:</strong> The minimum number of total RAD votes required to be cast in connection with a proposal. Quorum is currently measured as <em><strong>a % of the total RAD supply.</strong></em> The required quorum to pass a proposal is <strong>4% (4M RAD) of total supply (100M RAD)</strong></p>
<p><em>Formal Reviews</em> and <em>Submissions</em> are required to meet quorum requirements.</p>
</li>
<li>
<p><strong>Approval Threshold:</strong> If quorum is met, the proposal passes if a majority of the votes are “in-favor”.</p>
</li>
</ul>
<h2><a href="#delegating"></a>Delegating</h2>
<p>On-chain voting is enabled by delegating voting rights to the address (or addresses) of the token holder's choice:</p>
<ul>
<li>The owner’s own wallet, if they would like to vote on their own.</li>
<li>Another user's wallet, if they would like the other user to vote on their behalf.</li>
<li>No wallet, if they don't want to vote.</li>
</ul>
<p>Delegation takes place on-chain on various governance management platforms (e.g. via <a href="https://boardroom.io/radicle/proposals">Boardroom</a> or <a href="https://www.tally.xyz/gov/eip155:1:0x690e775361AD66D1c4A25d89da9fCd639F5198eD">Tally</a>). After connecting a wallet holding RAD, you are then able to delegate to either yourself or others. If you are delegating to yourself, after the delegation process is complete you are able to participate in on-chain voting. If you are delegating to others, they will received the amount you delegate as voting power to participate in on-chain voting.</p>
<blockquote>
<p> Any delegation made on-chain will be mirrored to Snapshot for off-chain votes - i.e. any $RAD that is delegated to your wallet on-chain will be able to be able to be used to vote in off-chain Snapshot polls.</p>
</blockquote>
<blockquote>
<p>In addition to the Code of Conduct, Radicle Delegates are expected to adhere to our Delegate Standards, a set of requirements for ensuring healthy &amp; safe community governance. Please review <a href="https://govradicle.super.site/delegate-standards">the standards</a> before announcing yourself as a delegate 👇</p>
</blockquote>
<h3><a href="#never-miss-a-vote-"></a>Never miss a vote! </h3>
<p>The best way to get live governance updates is by following the Radicle Governance Twitter (<a href="https://twitter.com/rad_gov">@rad_gov</a>) or follow the 🏛️governance-updates channel on Discord. These accounts act as governance “ticker” accounts and include all of the information and links needed to participate in voting. You can also <a href="https://app.tango.us/app/workflow/Email-Notifications-ac8d8e2eff5746f48ebd17e1f6b2b6ff">set up email notifications</a> directly from the the calendar on our <a href="https://boardroom.io/radicle/overview">Boardroom governance portal</a>.</p>
<p>The <em>Radicle Governance Updates</em> newsletter is a bi-weekly newsletter that provides updates on recent proposals, what the governance team is focusing on, as well as event and other reminders. You can <a href="https://bit.ly/3trPqXA">subscribe here</a>.</p>

Radworks Grant Application

Governance Manual [v0.2]

Got something to add?