Node Operator Policies
This page describes the policies applied to NodeSet node operators. These policies may be updated at any time, with material changes announced in advance.
All effectiveness checks referenced below are derived from the reports by the rated.network API.
Operator Communication Channels
NodeSet will NEVER contact you through any channel other than the ones listed below. NodeSet will NEVER send you a direct message about your node through Discord or other services.
Email
Announcements in the #operator-announcement channel of our Discord server
Private support channels in our Discord server (NOT in a direct message)
Penalty and Ejection Policy
Ejections from NodeSet are PERMANENT! If you have an issue with your node, you should reach out to us as soon as possible to ensure you are not ejected. We will work with you to exit your validators or rescue your node to help you avoid ejection.
Operators must continuously meet performance requirements to operate with NodeSet. This means that node operator effectiveness must remain above the minimum threshold of 95% at all times. We understand that temporary downtime is unavoidable for certain maintenance tasks and unusual events outside operator control, but all operators should aim for 100% uptime.
Operators who do not meet performance requirements will be ejected. NodeSet will not make exceptions for any operator for any reason other than large, network-level events.
Also note that operators may also be ejected for behavioral violations, including but not limited to:
Persistently violating professional and community guidelines
Being slashed (e.g., double signing attestations)
MEV theft
Providing false or misleading information in the application
Behavior deemed detrimental to the network or community
Last updated