var img = document.createElement('img'); img.src = "https://terradocs.matomo.cloud//piwik.php?idsite=1&rec=1&url=https://docs.terra.money" + location.pathname; img.style = "border:0"; img.alt = "tracker"; var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(img,s);
Skip to main content

Implement security practices

Each validator candidate is encouraged to run its operations independently. Diversity across individual setups increases the resilience of the network.

Manage digital keys with HSM​

Key management is mission-critical for validators. If an attacker gains access to a validator's private key, it puts the validator's entire delegated stake at risk. Hardware security modules are an important strategy for mitigating this risk.

Consider implementing this key-management method by Iqulusion.

Defend against DDoS attacks​

Validators are responsible for ensuring that the network can defend against denial-of-service (DDoS) attacks.

Validators can mitigate these attacks by carefully structuring their network topology in a sentry node architecture.

Validator nodes should only connect to full nodes that they trust. These nodes can be run by the same validator or other validators that they know. A validator node will typically run in a data center and most data centers provide direct links to major cloud providers. A validator can use these links to connect to sentry nodes in the cloud. This shifts the burden of denial-of-service from the validator's node directly to its sentry nodes. This may require new sentry nodes to be spun up or activated to mitigate attacks on existing ones.

Sentry nodes can be quickly spun up or used to change IP addresses. Because links to the sentry nodes are in private IP space, an internet-based attack cannot directly disturb them. This will ensure a validator's block proposals and votes always make it to the rest of the network.

Learn more about sentry-node architecture.

  1. For validator nodes, edit the config.toml:


    _6
    # Comma separated list of nodes to keep persistent connections to.
    _6
    # Do not add private peers to this list if you don't want them advertised.
    _6
    persistent_peers = "comma separated list of sentry node addresses"
    _6
    _6
    # Set to true to enable the peer-exchange reactor.
    _6
    pex = false

  2. For sentry nodes, edit the config.toml:


    _6
    # Comma separated list of nodes to keep persistent connections to.
    _6
    # Do not add private peers to this list if you don't want them advertised.
    _6
    persistent_peers = "validator node address"
    _6
    _6
    # Comma separated list of peer IDs to keep private (will not be gossiped to other peers).
    _6
    private_peer_ids = "nodeid of the validator"

💡tip

A node address has the following format: nodeid@ip:port. You can get the nodeid by running terrad tendermint show-node-id. The default port is 26656.

Environment Variables​

By default, uppercase environment variables with the following prefixes will replace lowercase command-line flags:

  • TE (for Terra flags)
  • TM (for Tendermint flags)
  • BC (for democli or basecli flags)

For example, the environment variable TE_CHAIN_ID will map to the command line flag --chain-id. While explicit command-line flags will take precedence over environment variables, environment variables will take precedence over any of your configuration files. For this reason, it is imperative that you lock down your environment so that any critical parameters are defined as flags on the CLI, or prevent modification of any environment variables.