Running a Node

Configuration for Cappuccino nodes

This page give the configuration used to run different types of nodes in the Cappuccino testnet. For general information on running an Espresso node, see https://github.com/EspressoSystems/gitbook/blob/main/guides/running-a-sequencer-node.md.

All nodes in Cappuccino use the ghcr.io/espressosystems/espresso-sequencer/sequencer:cappuccino Docker image. Depending on the type of node, the configuration varies.

Regular Node

Command

sequencer -- http -- catchup -- status

Environment

Same for all nodes

ESPRESSO_SEQUENCER_ORCHESTRATOR_URL=https://orchestrator.cappuccino.testnet.espresso.network
ESPRESSO_SEQUENCER_CDN_ENDPOINT=cdn.cappuccino.testnet.espresso.network:1737
ESPRESSO_STATE_RELAY_SERVER_URL=https://state-relay.cappuccino.testnet.espresso.network
ESPRESSO_SEQUENCER_GENESIS_FILE=/genesis/cappuccino.toml
RUST_LOG="warn,libp2p=off"
RUST_LOG_FORMAT="json"

# At least one state peer is required. The following URL provided by Espresso works.
# Optionally, add endpoints for additional peers, separated by commas.
ESPRESSO_SEQUENCER_STATE_PEERS=https://query.cappuccino.testnet.espresso.network

Chosen by operators

Volumes

  • $ESPRESSO_SEQUENCER_STORAGE_PATH

  • $ESPRESSO_SEQUENCER_KEY_FILE

DA Node

Requires operator to additionally run a Postgres server

Command

sequencer -- storage-sql -- http -- catchup -- status -- query

Environment

Same for all nodes

Chosen by operators

Volumes

  • $ESPRESSO_SEQUENCER_KEY_FILE

Archival Node

Requires operator to additionally run a Postgres server

Command

sequencer -- storage-sql -- http -- catchup -- status -- query -- state

Environment

Same for all nodes

Chosen by operators

Volumes

  • $ESPRESSO_SEQUENCER_KEY_FILE

Last updated