private-sentry.md

Running a Private Sentry Node manually

Prerequisites

Make sure you have all prerequisites set up

Deployment steps

Steps are the same as in full-node.md

except:

• Set <node-type> to "private-sentry" when using run_dcl_node

• Configure node specific parameters before running the node:

  [config.toml]

  [p2p]
  pex = true
  persistent_peers = "<node1-ID>@<node1-IP>:26656,..." # See the comment below on what values should be set here 
  private_peer_ids = # `Validator` node id
  unconditional_peers = # `Validator` node id
  addr_book_strict = false

  [app.toml]

  [state-sync]
  snapshot-interval = "snapshot-interval"
  snapshot-keep-recent = "snapshot-keep-recent"

• persistent_peers value:

  • Validator node with private IP + other orgs' validator/sentry nodes with public IPs.
  • For testnet-2.0 or main-net get the latest persistent_peers (other orgs' validator/sentry nodes with public IPs) from the CSA slack channel.
  • Use the following command to get node-ID of a node: ./dcld tendermint show-validator.