# Radworks :::note This is a modified fork of the [Contributor’s Covenant](https://www.contributor-covenant.org/) — an open-source code of conduct created by [Coraline Ada Ehmke](https://where.coraline.codes/) and stewarded by the [Organization for Ethical Source](https://ethicalsource.dev/). ::: ### Our Pledge We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation. We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community. ### Our Standards Examples of behavior that contributes to a positive environment for our community include: * Demonstrating empathy and kindness toward other people * Being respectful of differing opinions, viewpoints, and experiences * Giving and gracefully accepting constructive feedback * Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience * Focusing on what is best not just for us as individuals, but for the overall community Examples of unacceptable behavior include: * The use of sexualized language or imagery, and sexual attention or advances of any kind * Trolling, insulting or derogatory comments, and personal or political attacks * Public or private harassment * Publishing others' private information, such as a physical or email address, without their explicit permission * Other conduct which could reasonably be considered inappropriate in a professional setting :::tip Any community member acting as an active delegate is required to adhere to an additional set of standards to ensure healthy & safe community governance. You can find these standards here → [Delegate Standards](https://www.notion.so/Delegate-Standards-63d1cbbab92440bca07d1c2eec420a2b) ::: ### Enforcement Responsibilities Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful. Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned with this Code of Conduct, and will communicate reasons for moderation decisions when appropriate. ### Scope This Code of Conduct applies within all community spaces and also applies when an individual is representing the community in public spaces. Examples of representing our community include using a Radicle e-mail address, posting via an Radicle-affiliated social media account, interacting with others on Discord using a designated role (i.e. Radicles) or acting as a representative at an online or offline event (i.e. speaking engagements, workshops etc...). ### Enforcement Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the [“Community” > “General” channel](https://discord.com/channels/841318878125490186/841318878650302490) on the Radworks Discord. All complaints will be reviewed and investigated promptly and fairly. All community leaders are obligated to respect the privacy and security of the reporter of any incident. ### Enforcement Guidelines Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct: 1. **✅ Correction** 1. **Type of Violation**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community. 2. **Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested. 2. **🚨 Warning** 1. **Type of Violation**: A violation through a single incident or series of actions. 2. **Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban. 3. 👋 **Temporary Ban** 1. **Type of Violation**: A serious violation of community standards, including sustained inappropriate behavior. 2. **Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban. 4. **🚫 Permanent Ban** 1. **Type of Violation**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals. 2. **Consequence**: A permanent ban from any sort of public interaction within the community. ### Attribution :::info This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/), version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code\_of\_conduct.html](https://www.contributor-covenant.org/version/2/1/code_of_conduct.html). ::: :::info Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity). Delegation Standards were inspired by MakerDAO’s [Recognised Delegate Code of Conduct](https://forum.makerdao.com/t/recognised-delegate-code-of-conduct/9384). ::: :::info ❓ For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are available at [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations). ::: ## The RAD token $RAD is the native token of the Radworks Network, used as the primary means to coordinate all actors, govern the treasury, and (later this year will) reward infrastructure providers to the Radicle Network. ### How it works #### Governance Radworks is a community-run network, where all aspects of the network are governed by RAD holders. RAD holders can vote on Radworks Governance Proposals (RGPs) to distribute funds from the Treasury, improve the network, and manage critical system parameters. [Read more here](https://docs.radworks.org/community/governance-overview). #### Incentivization (Coming soon) The Radicle Garden provides storage and retrieval services for the Radicle Network. Soon, a decentralized offering will be built and the RAD token will be used to reward seed nodes that provide these services. [Read more here](https://community.radworks.org/t/formal-review-rgp-22-start-the-radworks-seed-network-rsn-org/3487). ### Token Contracts * RAD Token: [0x31c8eacbffdd875c74b94b077895bd78cf1e64a3](https://etherscan.io/token/0x31c8eacbffdd875c74b94b077895bd78cf1e64a3) * Governance: [0x690e775361AD66D1c4A25d89da9fCd639F5198eD](https://etherscan.io/address/0x690e775361AD66D1c4A25d89da9fCd639F5198eD) * Timelock: [0x8dA8f82d2BbDd896822de723F55D6EdF416130ba](https://etherscan.io/address/0x8dA8f82d2BbDd896822de723F55D6EdF416130ba) * Genesis: [0x6838f63899728816f602B3e9bF73952e2bD6dc35](https://etherscan.io/address/0x6838f63899728816f602B3e9bF73952e2bD6dc35) * Registrar: [0x37723287Ae6F34866d82EE623401f92Ec9013154](https://etherscan.io/address/0x37723287Ae6F34866d82EE623401f92Ec9013154) ### Token Metrics Please see [CoinGecko](https://www.coingecko.com/en/coins/radworks) for the latest token metrics. ### Obtaining RAD $RAD is available on the following exchanges: ##### Centralized * [Binance](https://www.binance.com/en) * [Coinbase](https://www.coinbase.com/) * [Kraken](https://www.kraken.com/) * [MEXC](https://www.mexc.com/) * [HTX](https://www.htx.com/) * [Gate.io](https://www.gate.io/) * [Partibu](https://www.paribu.com/) * [Crypto.com](https://crypto.com/) ##### Decentralized * [Uniswap](https://app.uniswap.org/) ### [Coming Soon](https://community.radworks.org/t/formal-review-rgp-22-start-the-radworks-seed-network-rsn-org/3487)! There is an ongoing effort to bring new token utility to Radworks and the RAD token. Keep up to the date with discussions on [community.radworks.org](http://community.radworks.org) ## Governance FAQ :::note Please note that we are not recommending any of these third party tools over the other. This document is meant to provide some basic descriptions, examples and instructions to help make onboarding to voting and proposal creation flows in governance more approachable for our community members. Each individual is **strongly encouraged** to perform their own due diligence before trusting third-party services listed below. ::: ### Wallet Basics & Safety Most wallet providers have great documentation and safety tips on their websites. Here are a few examples: * [Basic Safety & Security Tips for MetaMask](https://support.metamask.io/hc/en-us/articles/360015489591-Basic-Safety-and-Security-Tips-for-Metamask) * [Rainbow: Protect your wallet](https://learn.rainbow.me/protect-your-wallet) * [Coinbase Security Tips](https://www.coinbase.com/security/security-tips) * [Security Tips for Hardware Wallets](https://www.ledger.com/academy/hardwarewallet/best-practices-when-using-a-hardware-wallet) #### What is the difference between a hot and hardware wallet? ##### Hot Wallet Any web-based wallet (desktop or mobile app) is considered a hot wallet. These wallets are usually less secure than hardware wallets, but are convenient to use and access. *Examples of hot wallets:* MetaMask, Rainbow, Coinbase, etc. ##### Hardware Wallet Hardware wallets are devices specially designed to securely store private keys and give the user absolute ownership and control of tokens and other assets. They usually come in the form of a USB-like device. *Examples of hardware wallets:* Ledger, Trezor, etc. #### What is the difference between a hosted vs self-hosted wallet (also known as custodial vs non-custodial wallets)? ##### Self-Hosted These can be hardware or hot wallets. These wallets don’t require you to trust a third party, but this also means there is more responsibility on you for keeping track of your keys and information. *Examples of self-hosted or non-custodial wallets:* MetaMask, Rainbow, any hardware wallet ##### Hosted These wallets require more trust in an intermediary to host your wallet than a non-custodial wallet, but many still be preferred as they don’t require as much responsibility and are usually more user friendly. As these wallets are hosted by centralized entities that are privy to regulation, there is a risk of losing access to these wallets by the company running into issues. Please note that community members have experienced issues voting with hosted wallets in the past. Please see our troubleshooting section below if you experience issues. *Examples of hosted or custodial wallets:* Coinbase, Binance ### Governance Tools #### What platform should I use to vote on off-chain Formal Reviews? Snapshot is the voting platform used for gathering off-chain consensus. Check out the [Radworks Snapshot space](https://snapshot.org/#/gov.radworks.eth). #### What platform should I use to vote for on-chain proposals? On-chain voting can take place on any on-chain governance interface. We primarily use [Boardroom](https://boardroom.io/radworks/proposals#) and [Tally](https://www.tally.xyz/gov/radworks) as they are actively curated and trusted platforms in the broader DAO ecosystem. See the ‘Voting Tips & Troubleshooting’ section below for more details on how to vote on these platforms. #### What platform should I use to create new on-chain proposals? Proposal creation is also possible on Boardroom and Tally. They make it easy for anyone to confirm they are eligible to create a proposal and to create the proposal itself. See the ‘On-chain Proposal Creation Tips & Trouble-shooting’ section below for more details on how to create a proposal on these platforms. ### Voting Tips & Trouble-shooting #### What do I need to know before voting? * No matter what wallet or voting platform you use, to participate in off-chain and on-chain voting you have to first delegate the voting power of your RAD to yourself or another address. If you do not delegate to yourself or another address before voting, the transaction will go through but the vote will show having 0 RAD voting power. * 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. * In order to utilize delegated voting power in a vote, delegation needs to take place before the vote goes live. * Delegation only needs to be set up once. The only time you need to redelegate is to change or remove the address you are delegating to, otherwise delegation will continue to the assigned address. #### What are some troubleshooting steps I can try if I am having trouble connecting a wallet or voting? * If you are having troubles on one platform (Boardroom, Tally), try using the other. * If you are having troubles in one browser, try using another. * If you are having troubles on desktop, try using mobile and vice versa. * Reach out in the [#faq-support](https://discord.gg/radworks) channel on Discord for help #### How do I connect a hot wallet to vote? ##### Delegating to yourself * Connect your wallet to an on-chain voting platform (Boardroom, Tally) * Delegate your votes by selecting “Delegate Vote” on Tally or “Set up delegation” on Boardroom in the top right part of the screen * Select “Delegate to myself” * Confirm the transaction as prompted (this will have a gas fee) * Select the proposal you would like to vote on * Review the options available to vote - “For” or “Against” or “Abstain” * Select the option you would like to vote for and select “Vote” * *Optional:* You can leave a comment on why you are voting on way or another before confirming the vote * Confirm the transaction as prompted (this will have a gas fee) ##### Delegating to another address * Connect your wallet to an on-chain voting platform (Boardroom, Tally) * Delegate your votes by selecting “Delegate Vote” on Tally or “Set up delegation” on Boardroom in the top right part of the screen * Select “Delegate to another address” * Confirm the transaction as prompted (this will have a gas fee) * The other address is ready to vote on proposals on- and off-chain with the newly delegated voting power :::note It may take a few minutes for transactions to go through and be shown on governance interfaces. ::: #### How do I connect a hardware wallet to vote? :::note **Boardroom:** supported hardware wallets include: * *Ledger:* connect via Ledger Live. * *KeepKey, Trezor and others:* connect via WalletConnect **Tally:** supported hardware wallets include: * *Ledger, Gridplus and Lattice* connect via WalletConnect ::: 1. Connect your hardware wallet to the platform. If you are having troubles, reach out to the platform’s support teams ([Tally](https://discord.gg/63Pj2mR8), [Boardroom](https://discord.gg/yRXgGNQn)) 2. Delegate to yourself or another address and confirm the transaction as prompted 3. That address is ready to vote on proposals on- and off-chain with the newly delegated voting power #### How do I connect a multisig to vote? ##### On Tally * Use Wallet Connect to connect the multisig wallet * Delegate and vote as usual ##### On Boardroom * Use Wallet Connect to connect as the multisig wallet directly * Delegate and vote as usual * Follow the rest of the steps to publish the proposal ### On-chain Proposal Creation Tips & Trouble-shooting #### What do I need to know before creating a proposal? You need at least 1M $RAD (1% of total $RAD supply) delegated to your address to post an on-chain proposal. You need at least 1K $RAD delegated to your wallet to post an off-chain Snapshot poll. Make sure that delegation is set up to the correct wallet before trying to post a proposal. *The following instructions are for on-chain proposal creation. [Follow these instructions](https://docs.snapshot.org/user-guides/proposals/create) to post an off-chain proposal on Snapshot.* #### How do I create a proposal with a hot wallet? * Connect your wallet to an on-chain voting platform (Boardroom, Tally) * Select “Create a new proposal” or “Add a new proposal” * The platform will confirm if the wallet you have connected meets all of the requirements to post a proposal. If you do not meet the requirements, follow the instructions on the screen. If you do, continue to the proposal page * Fill in the necessary information as prompted and publish the proposal #### How do I create a proposal with a hardware wallet? :::note **Boardroom:** supported hardware wallets include: * *Ledger:* connect via Ledger Live. * *KeepKey, Trezor and others:* connect via WalletConnect **Tally:** supported hardware wallets include: * *Ledger, Gridplus and Lattice* connect via WalletConnect ::: * Connect your hardware wallet via the appropriate connection option on Boardroom * Follow the steps on your device to connect * Select “Create a new proposal” or “Add a new proposal” * Boardroom will confirm if the wallet you have connected meets all of the requirements to post a proposal. If you do not meet the requirements, follow the instructions on the screen. If you do, continue to the proposal page * Fill in the necessary information as prompted and publish the proposal #### How do I create a proposal with a multisig? ##### On Tally * Login with an [Externally Owned Account (EOA)](https://ethereum.org/en/whitepaper/#ethereum-accounts) * Create a draft of the proposal * Logout * Use WalletConnect to connect as the multisig wallet * Follow remaining steps to publish the proposal ##### On Boardroom * Use WalletConnect to connect as the multisig wallet directly * Follow the regular steps to publish the proposal ## Governance Welcome to Radworks' version-controlled governance documentation! These docs consist of carefully curated information and resources that lay out the Radworks token voting governance process and how to participate in it. The Radworks’ treasury is managed by an on-chain governance mechanism ([Compound-Governor](https://wiki.tally.xyz/docs/compound-governor)) via the project’s native governance token - $RAD. Holders of $RAD can participate in decision-making by voting on and creating Radworks Governance Proposals (RGPs). Voting power is derived directly from the number of [tokens delegated](https://github.com/radicle-foundation/radworks-governance/blob/main/manual.md#delegating) to an address (1 token = 1 vote). ### Participate in Governance #### Review proposals Review proposals on the forum & leave feedback for proposal authors [here](https://community.radworks.org/c/governance/proposals/18). #### Delegate voting power Find delegates and delegate voting power [here](https://www.tally.xyz/gov/radworks/delegates). #### Vote offchain View and vote on active Snapshot polls [here](https://snapshot.org/#/gov.radworks.eth). #### Vote onchain View and vote on active onchain submissions [here](https://www.tally.xyz/gov/radworks). ### What is governance used for? #### Onchain Governance Onchain governance is used to make decisions on proposals that include executable code. This includes: * Treasury distributions of RAD, ETH, and USDC * Upgrades to the onchain governance system (e.g. quorum) * Changes to parameters of Treasury-governed contracts (e.g. Drips) #### Offchain Governance Offchain governance is used to gain community consensus on decisions. Currently, consensus is needed for: * Confirming a proposal with executable code is ready to be submitted for onchain voting (also known as [Formal Review](https://github.com/radicle-foundation/radworks-governance/blob/main/manual.md#formal-review)) * Proposals that do not include executable code, but still require consensus from the community (e.g. updates to the governance process) ### Proposal Process Radworks governance process has three phases: Request for Comments, Formal Review, and Submission. [Learn more about different proposal types and the RGP process](https://github.com/better-internet/radworks-governance/blob/main/manual.md#proposal-types). !["Diagram detailing the proposal phases of Radworks governance process"](/img/governance_phases.png) ### Proposal Cycles Radworks proposals are reviewed in monthly cycles using the following schedule. [Learn more about monthly proposal cycles](https://github.com/better-internet/radworks-governance/blob/main/manual.md#proposal-cycles). !["Diagram detailing the schedule of Radworks monthly proposal cycles"](/img/monthly_proposal-cycles.png) ### Proposal Types All proposals are referred to as RAD Governance Proposals (RGPs). There are two types of RGPs: **Executable** & **Social**. | Type | Description | Process | | ---------- | --------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------- | | Executable | On-chain actions such as treasury distributions, updates to contract parameters, and upgrades to governance system. | Request for Comments → Formal Review → Submission | | Social | Off-chain changes that can not be enforced by governance on-chain but should have community approval (e.g. updates to the governance process) | Request for Comments → Formal Review | ### Voting Thresholds A RGP is approved if it satisfies the following minimum vote thresholds: * **Quorum:** The minimum number of RAD votes required to be cast in support of a proposal in order for a quorum to be reached and for a vote to succeed. Quorum is currently measured as a % of the total $RAD supply. The required quorum to pass a proposal is **4% (4M $RAD) of total supply (100M $RAD)** * **Approval Threshold:** If quorum is met, the proposal passes if a majority of the votes are “in-favor”. Proposals in the Formal Review and Submission phases are required to meet quorum requirements. ### Delegation To participate in off-chain and on-chain voting, $RAD must be delegated to the address that will be used to vote. Delegation can be executed via various governance management platforms (e.g. Tally). [Learn more](https://github.com/better-internet/radworks-governance/blob/main/manual.md#delegating) about how to delegate $RAD and begin voting. ### Relevant Contracts * [Radworks Governance Contracts](https://github.com/radicle-foundation/radworks-governance/blob/main/manual.md#formal-review) * Governance: [0x690e775361AD66D1c4A25d89da9fCd639F5198eD](https://etherscan.io/address/0x690e775361AD66D1c4A25d89da9fCd639F5198eD) * Timelock: [0x8dA8f82d2BbDd896822de723F55D6EdF416130ba](https://etherscan.io/address/0x8dA8f82d2BbDd896822de723F55D6EdF416130ba) * Genesis: [0x6838f63899728816f602B3e9bF73952e2bD6dc35](https://etherscan.io/address/0x6838f63899728816f602B3e9bF73952e2bD6dc35) ## Stay up to date on Radworks governance ### Community Calls Community Calls are held on a quarterly basis. Each Org is responsible for sending one team member to present a progress update on what they are working on and what they have planned for the coming quarter. This is an opportunity for Orgs to touch base with each other and for our community to see what's happening within the project. A full collection of video recordings of our past and current Community Calls can be found on our [YouTube channel](https://www.youtube.com/playlist?list=PLUUjDC9sOrplFcqQxhgQGKRXKMSqJ_wOZ). ### Proposal Reviews Proposal Reviews take place on the second Wednesday of the month, when a proposal has been submitted. These calls are used as a space for proposal authors who have proposals going up for vote that month to discuss their proposals and answer questions from the community. You can find the link for upcoming calls on [the community calendar](https://calendar.google.com/calendar/u/0/r?cid=Y18wcmY3NW9ja3NyNTZsZ2prZ2xlb3R0Z2F1NEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t). More detailed updates to governance work being done can be found in the monthly written updates on the forum. ### Community Calendar You can subscribe to our [community calendar](https://bit.ly/radworks-calendar) that includes Quarterly Community Calls, monthly Proposal Review calls and each week of the monthly governance cycle. ### Twitter Check out the [Radworks Twitter page](https://twitter.com/radworks_) (@radworks\_) for important DAO-wide announcements & governance updates. ### YouTube Our [YouTube channel](https://www.youtube.com/@radworks_) has all recordings of past Community Calls and Proposal Reviews. We also have folders for all talks and events our contributors have hosted or spoken at.