Setting up the node

A node in the Mavryk network provides different configuration possibilities:

• tune various parameters of the node using flexible combinations of: a configuration file, command-line options, and environment variables

• specify the Mavryk network to connect to, which can be the Mainnet or different test networks.

• configure the amount of history kept by the node according to different tradeoffs, using history modes

• rapidly catch up with a given (main or test) network by loading network snapshots

• set up one or several proxy servers to decrease the load of the node by serving some RPC requests themselves

• set up infrastructure for continuosly monitoring the node to help spotting operational or efficiency issues

These possibilities are described in the following pages.

• Node Configuration
  • Node configuration file
  • RPC parameters
  • Default ACL for RPC
  • P2P parameters
  • Shell parameters

• Connecting to a Network
  • Test Networks
  • Built-In Networks
  • Custom Networks
  • Alias Versus Explicit Configuration

• History modes
  • History modes in a nutshell
  • Setting up a node in full mode
  • Setting up a node in rolling mode
  • Setting up a node in archive mode
  • Keeping additional cycles
  • Switching between node’s modes

• Snapshots
  • Importing a snapshot
  • Exporting a snapshot

• Proxy server
  • Launching a proxy server
  • Examples with the sandbox
  • Additional arguments
  • Supported RPCs
  • Unsupported RPCs
  • Deployment
  • Heuristics

• Monitoring an Mavkit Node
  • Starting a node with monitoring
  • Gathering data
  • Dashboards