NodeSet
  • NodeSet Documentation
  • NodeSet
    • Introduction
    • Infrastructure Powered by NodeSet
    • Security Notice
  • Node Operators
    • Applications
    • Node Operator Policies
    • Client Diversity Policy
    • Best Practices
      • Terminology
      • Planning Your Node Architecture
      • MEV Boost
    • Hyperdrive
      • Installation
      • Configuration
      • Updating
      • Monitoring Your Node
      • Uninstallation
      • Disaster Recovery and Node Migration
      • Public Betas
    • FAQ
  • StakeWise Integration
    • Introduction
    • What's New in v1.2
    • FAQ
    • Node Operator Guide
      • Monitoring the StakeWise Module
      • Key Recovery
      • How it Works
    • Security Information
  • Constellation
    • Overview
    • xrETH
    • xRPL
    • Constellation vs Others
    • Risks and Mitigations
    • Node Operators
    • Node Operator Guide
      • Overview
      • Prerequisites
      • Registering your Node with Constellation
      • Creating and Running Minipools
      • Rewards Algorithm
    • Administrator
    • Treasurer
    • FAQ
    • Security Information
  • NodeSet Dashboard
    • Introduction
    • Authorizing Your Node
    • Security Information
Powered by GitBook
On this page
  • Intro
  • Notifications
  • Monitoring
  • Security and External Access
  • Client Diversity
  • Graffiti
  1. Node Operators

Best Practices

PreviousClient Diversity PolicyNextTerminology

Last updated 1 year ago

Intro

With NodeSet, your node's performance impacts others' rewards. Therefore, . These best practices help you uphold community standards and elevate your operation to a more professional level.

Notifications

Setting up notifications for your node will immediately notify you if there is an issue so you can fix it faster. Our suggested minimum set of notifications for are selected in the screenshot below. In the future, NodeSet will contact you automatically if there is an issue.

Monitoring

A monitoring tool stack will help you understand your node's status at a glance and quickly diagnose issues. Please see the following pages for more information:

Security and External Access

Client Diversity

Graffiti

Operators should identify themselves via their graffiti. This helps NodeSet understand our operator network better and will assist you in debugging if there is an issue.

The exact procedure for changing your graffiti depends on your setup. For example, you can use rocketpool service config to set your graffiti if you use Rocket Pool to manage your node, or you can look at your eth2 client's documentation if you manage it yourself.

StakeWise v3:

Rocket Pool:

Setting up external access to your node while preventing unauthorized activity is crucial for performing maintenance while away. will help you secure your node, and provides instructions for allowing safe access to your node no matter where you are in the world.

We encourage users to consider high-redundancy setups with at least one fallback node, and if possible, .

https://docs.stakewise.io/for-operators/operator-service/monitoring
https://docs.rocketpool.net/guides/node/grafana
This Rocket Pool documentation page
this guide for Tailscale
use a solution such as Vouch to coordinate and verify a multi-client configuration
See this page for NodeSet's client diversity policy.
Beaconcha.in
NodeSet requires strict performance standards for operators