|
1 | 1 | # Delegation Policy |
2 | 2 |
|
3 | | -Oasis Protocol Foundation delegates ROSE tokens to node operators based on their |
4 | | -participation in the Oasis Mainnet, Testnet and ParaTimes on the network, |
5 | | -node reliability and performance, community engagement and overall support of |
6 | | -the network. |
7 | | - |
8 | | -This page describes the Oasis Protocol Foundation's Delegation Policy. |
| 3 | +The Oasis Protocol Foundation (OPF) delegates ROSE tokens to node operators who |
| 4 | +run Oasis Consensus and ParaTime nodes on Mainnet and/or Testnet. Delegations |
| 5 | +are based on node reliability, performance, community engagement, and overall |
| 6 | +contributions to the network’s growth and stability. |
9 | 7 |
|
10 | 8 | ## Requirements for Receiving Delegations |
11 | 9 |
|
| 10 | +To be eligible for a delegation, you have to [join the network], follow the [Code |
| 11 | +of Conduct], and meet [performance requirements]. |
| 12 | + |
| 13 | +For guidance on how to increase your delegation over time, please refer to the |
| 14 | +instructions at the bottom of this page. |
| 15 | + |
| 16 | +### Join the Network |
| 17 | + |
| 18 | +1. **Join the Community Channels** |
| 19 | + - Join the `#node-operators` channel on the [Oasis Discord server] |
| 20 | + - Or join the Telegram group: [@oasisnodeoperators] |
| 21 | + |
| 22 | +2. **Create Your Entity Keys** |
| 23 | + - Generate your **Testnet** and **Mainnet** [entity keys] |
| 24 | + |
| 25 | +3. **Set Up Your Nodes** |
| 26 | + - [Configure and start] your Testnet Consensus and ParaTime nodes |
| 27 | + - [Configure and start] your Mainnet Consensus and ParaTime nodes |
| 28 | + |
| 29 | +4. **Submit Your Metadata** |
| 30 | + - [Provide metadata] for both **Mainnet** and **Testnet** |
| 31 | + |
| 32 | +5. **Reach Out to the Node Operator Relationship Manager** |
| 33 | + - Message `@am3lody` on Discord or Telegram |
| 34 | + - Be prepared to answer any follow-up questions |
| 35 | + |
| 36 | +6. **Stay Updated** |
| 37 | + - Follow network announcements: |
| 38 | + - 📢 [Oasis Discord server]: [`#mainnet-announcements`], |
| 39 | + [`#testnet-announcements`], [`#node-operators`] |
| 40 | + - 📢 Telegram: [Oasis Mainnet Announcements], [Oasis Testnet Announcements] |
| 41 | + and [Oasis Node Operators Group] |
| 42 | + |
| 43 | +7. **Engage with the Community** |
| 44 | + - Actively participate on the Oasis Network Community on Discord or Telegram |
| 45 | + - Follow the Code of Conduct and meet Performance Requirements |
| 46 | + - Help others and answer questions from fellow node operators and community |
| 47 | + members |
| 48 | + |
| 49 | +[join the network]: #join-the-network |
| 50 | +[Code of Conduct]: #code-of-conduct |
| 51 | +[performance requirements]: #performance-requirements |
| 52 | +[Oasis Discord server]: https://oasis.io/discord |
| 53 | +[`#mainnet-announcements`]: https://discord.com/channels/748635004384313474/960599344745185330 |
| 54 | +[`#testnet-announcements`]: https://discord.com/channels/748635004384313474/967039075527827496 |
| 55 | +[`#node-operators`]: https://discord.com/channels/748635004384313474/748644177394532463 |
| 56 | +[@oasisnodeoperators]: https://t.me/oasisnodeoperators |
| 57 | +[entity keys]: ../node/run-your-node/validator-node#initialize-entity |
| 58 | +[Configure and start]: ../node/run-your-node/validator-node#configuration |
| 59 | +[Provide metadata]: ../node/run-your-node/validator-node#oasis-metadata-registry |
| 60 | +[Oasis Mainnet Announcements]: https://t.me/oasisMAINNETannouncements |
| 61 | +[Oasis Testnet Announcements]: https://t.me/oasisTESTNETannouncements |
| 62 | +[Oasis Node Operators Group]: https://t.me/oasisnodeoperators |
| 63 | + |
12 | 64 | ### Code of Conduct |
13 | 65 |
|
14 | | -1. Ensure commission rates and commission rate bounds are no greater than 20%. |
15 | | -2. Ensure commission rates are +/- 10% of the weighted median network commission |
16 | | - rate. |
17 | | -3. Ensure your entity’s website, social media and/or contact info in the |
18 | | - [Oasis Metadata Registry] is up-to-date. |
19 | | -4. Do not use 'Oasis' in your entity name, and do not use any Oasis Foundation |
20 | | - logos or branding in your entity logo. |
21 | | -5. Refrain from dishonest, fraudulent or malicious behavior. |
22 | | -6. Participate in on-chain governance and network upgrades proposed by Oasis |
23 | | - Foundation. |
24 | | -7. Be available and coordinate with the node operator community in case of |
25 | | - unplanned network upgrades. |
26 | | - |
27 | | -If there is any violation of the above Code of Conduct, Oasis Foundation |
28 | | -reserves the right to revoke your entire delegation. |
| 66 | +- **Set Appropriate Commission Rates** |
| 67 | + - Ensure your commission rate and commission rate bounds do not exceed *20%* |
| 68 | + - Keep your commission rate within ±10% of the weighted median commission rate |
| 69 | + on the network |
29 | 70 |
|
30 | | -### Performance Requirements |
| 71 | +- **Keep Metadata Updated** |
| 72 | + - Ensure your entity’s website, social media, and/or contact information in |
| 73 | + the [Oasis Metadata Registry] is accurate and current |
31 | 74 |
|
32 | | -1. Maintain active validator status. |
33 | | -2. Maintain >99% uptime for your validator node as well as Emerald and/or Cipher |
34 | | - ParaTime nodes (if you run them). |
35 | | -3. Ensure your nodes are upgraded within 1 hour after a planned network upgrade. |
36 | | -4. Ensure your nodes are upgraded within 24 hours after an unplanned network |
37 | | - upgrade. |
38 | | - |
39 | | -If any of the above Performance Requirements is not met, Oasis Foundation |
40 | | -reserves the right to revoke delegations. If you run into a complex technical |
41 | | -issue that prevents your node from meeting the above Performance Requirements, |
42 | | -please reach out to the Oasis team as soon as possible. |
43 | | - |
44 | | -## How to Earn Delegations? |
45 | | - |
46 | | -- Have a meaningful amount of self-delegation and/or delegations from the Oasis |
47 | | - community. |
48 | | -- Operate Emerald and/or Cipher ParaTime nodes on Mainnet. |
49 | | -- Operate validator and/or ParaTime nodes on Testnet |
50 | | -- Participate in community discussion on the network’s future roadmap. |
51 | | -- Actively participate on the Oasis Network Community server on Discord |
52 | | - and help answer questions from other community members. |
53 | | -- Build or contribute to tools, services or dApps that benefit developers, node |
54 | | - operators and/or the overall Oasis community. |
55 | | -- Contribute code to Oasis projects. |
56 | | -- Find and report issues related to any of the network protocols and/or their |
57 | | - implementations. |
58 | | -- Demonstrate a track record of successfully operating nodes on other major |
59 | | - networks. |
| 75 | +- **Respect Branding Guidelines** |
| 76 | + - Do not include the word "Oasis" in your entity name |
| 77 | + - Do not use Oasis Foundation logos or branding in your entity’s logo |
| 78 | + |
| 79 | +- **Maintain Integrity** |
| 80 | + - Avoid any dishonest, fraudulent, or malicious behavior |
| 81 | + |
| 82 | +- **Participate Actively in Governance and Network Operations** |
| 83 | + - Participate in on-chain governance and network upgrade votes |
| 84 | + - Be available and ready to collaborate with other node operators during |
| 85 | + unplanned network upgrades or events |
60 | 86 |
|
61 | 87 | [Oasis Metadata Registry]: https://github.com/oasisprotocol/metadata-registry |
| 88 | + |
| 89 | +### Performance Requirements |
| 90 | + |
| 91 | +- **Maintain Active Validator Status** |
| 92 | + Remain in good standing as an active validator on both Testnet and Mainnet. |
| 93 | + |
| 94 | +- **Achieve High Uptime Across All Networks** |
| 95 | + Ensure consistently high uptime for your Consensus, Sapphire, and |
| 96 | + Cipher nodes on both Testnet and Mainnet. |
| 97 | + |
| 98 | +- **Timely Upgrades for Planned Network Events** |
| 99 | + Apply all planned network upgrades within 1 hour of their scheduled |
| 100 | + release. |
| 101 | + |
| 102 | +- **Rapid Response to Unplanned Upgrades** |
| 103 | + Complete any unplanned or emergency upgrades within 24 hours of |
| 104 | + announcement. |
| 105 | + |
| 106 | +If you run into a complex technical issue that prevents your node from meeting |
| 107 | +the above Performance Requirements, please reach out to the Oasis team as soon |
| 108 | +as possible. |
| 109 | + |
| 110 | +## How to Increase Delegations? |
| 111 | + |
| 112 | +- **Operate Core Infrastructure Across Networks** |
| 113 | + Run and maintain high-uptime nodes for Consensus, Sapphire, and |
| 114 | + Cipher on both Testnet and Mainnet. |
| 115 | + |
| 116 | +- **Be Ready for Network Upgrades** |
| 117 | + Stay prepared for both planned and unplanned upgrades. Monitor relevant |
| 118 | + communication channels and respond quickly when action is required. |
| 119 | + |
| 120 | +- **Participate in On-Chain Governance** |
| 121 | + Actively vote on governance proposals to help shape the network’s direction. |
| 122 | + |
| 123 | +- **Communicate Downtime Transparently** |
| 124 | + If you experience downtime or technical issues, report them promptly to the |
| 125 | + Oasis Protocol Foundation (OPF) — contact `@am3lody` on Discord or Telegram. |
| 126 | + |
| 127 | +- **Maintain Credible Stakeholding** |
| 128 | + Maintain a meaningful level of self-delegation and/or |
| 129 | + community delegations. |
| 130 | + |
| 131 | +- **Engage in Strategic Discussions** |
| 132 | + Join and contribute to community discussions about the network’s long-term |
| 133 | + roadmap and strategic initiatives. |
| 134 | + |
| 135 | +- **Build and Support the Ecosystem** |
| 136 | + Develop or contribute to tools, services, or dApps that provide value to |
| 137 | + developers, node operators, and the broader Oasis community. |
| 138 | + |
| 139 | +- **Contribute Code to Oasis Projects** |
| 140 | + Actively contribute to open-source codebases or support the development of |
| 141 | + Oasis-related repositories and infrastructure. |
| 142 | + |
| 143 | +- **Identify and Report Issues** |
| 144 | + Proactively discover and report bugs or issues in Oasis network protocols |
| 145 | + and/or their implementations. |
| 146 | + |
| 147 | +- **Demonstrate Reliable Node Operations History** |
| 148 | + Demonstrate a strong track record of reliably operating nodes on |
| 149 | + other major blockchain networks. |
| 150 | + |
| 151 | +## Disclaimer |
| 152 | +Delegations from the Oasis Foundation are discretionary and may be adjusted or |
| 153 | +revoked at any time, with or without prior notice. |
0 commit comments