Vine Docs
  • Overview
    • What is Vine?
    • Layer 0 Architecture
    • Key Features
    • Network Components
  • Core Concepts
    • Layer 0 Protocol Design
    • Architecture Design
    • Node Architecture
    • Parachains
    • EVM & WASM Support
    • Nominated Proof of Stake (NPoS)
    • How NPoS Works
    • Vine Coin (VNE) and Governance
    • Transaction Fees
  • Validators
    • Who are Validators?
    • Validator Node Types
    • Validator's Guide
      • Step 1 - Validator dApp
      • Step 2 - Dashboard
      • Step 3 - Validator Setup
      • Step 4 - Validators Page
    • Manage Account
    • Validator Node Setup
      • Validator System Requirements
      • Guidelines & Precautions
  • Nominators
    • Who are Nominators?
    • Nominator dApp
    • Becoming a Nominator
      • Step 1 - Login
      • Step 2 - Dashboard
      • Step 3 - Validators Page
      • Step 4 - Nominate Validators
    • Manage Account
  • Staking, Slashing & Chilling
    • Staking
    • Slashing Guide
    • Chilling
  • Parallel Chains
    • Overview
    • Block Parameters
    • Substrate Framework-Based
    • Asset Movement
    • Pros and Cons
    • Interoperability
    • Application-Specific Parallel Chains
  • Vine RPC Calls
    • Overview
    • RPC Calls
      • Author
      • Babe
      • Beefy
      • Chain
      • childstate
      • contracts
      • dev
      • engine
      • grandpa
      • mmr
      • offchain
      • payment
      • rpc
      • state
      • syncstate
      • system
  • Vine Explorer
    • Overview
    • How to Use
      • Dashboard
      • Transaction Details
      • Block Details
      • Telemetry
      • Map View
      • Globe View
      • TPS History
      • Vine Testnet Faucet
      • Token Module
      • Contracts
  • Zen Wallet
    • Overview
    • How to Use
      • Create Account
      • Account Login
      • Dashboard
      • Balance
      • Statements
      • Send
      • Keys
      • Swap
      • Balance
      • Multisig Login
        • How To
        • Balance
        • Send
  • Additional Resources
    • Glossary
      • Blockchain
      • Node
      • Validator Node
      • Full Node
      • Validators
      • Nominators
      • Mnemonics
      • Stake
      • Slashing
      • Chilling
      • Parallel Chain
      • Era
      • Uptime
      • APY
      • Waiting State of Validator
      • Active State of Validator
      • Inactive State of Validator
      • Non-Custodial Wallet
      • Custodial Wallet
      • Points
Powered by GitBook
On this page
  1. Validators
  2. Validator Node Setup

Guidelines & Precautions

PreviousValidator System RequirementsNextWho are Nominators?

Last updated 3 months ago

The following points are generally good guidelines for validator node hosts.

They emphasize the importance of maintaining the security and availability of the node and protecting sensitive information such as keys and IP addresses:

  • Validators must never open access to their port to the public. This ensures that only authorized parties can access the node and prevents unauthorized access.

  • Validators must never share their keys (mnemonics) with anyone. This is important because sharing keys would give others access to the validator account, which could lead to financial security breaches.

  • Validators must make sure the node is up and running to prevent slashing and chilling. Keeping the node running prevents downtime and ensures that the validator can participate in the network and receive rewards.

  • Validators must never use the root user. Using the root user is a security vulnerability because it has full access to the system.

  • Validators must always update security patches for your OS. Keeping the operating system up to date helps to prevent known vulnerabilities from being exploited.

  • Validators must enable and set up a firewall. A firewall is an important security measure that helps to prevent unauthorized access to the node.

  • Validators must never allow password-based SSH, only use key-based access. Using key-based access is more secure than using a password because it makes it harder for unauthorized parties to gain access.

  • Validators must back up their storage regularly. Backing up the storage regularly is important in case the data is lost or becomes inaccessible."

Screen Application

For a seamless experience, it is recommended to run the validator node in the background. You can use the "Screen Application" for this purpose.

The "Screen Application" is a program that allows running multiple shell sessions in the command line, similar to having multiple tabs open in a browser.

Using screens has unique benefits such as the ability to 'detach' from a session without terminating any ongoing process, switch between sessions and resume where you left off. If a session is terminated, all work is kept intact. By using the screen environment, work can be accessed from multiple devices.

To learn about guidelines for using the Screen Application, please follow the links below

For Linux:

For Mac:

https://www.digitalocean.com/community/tutorials/how-to-install-and-use-screen-on-an-ubuntu-cloud-server
https://formulae.brew.sh/formula/screen