Copy the .env file if you need to cutomize service ports, log-level, prometheus.yaml or other configurations.
# clone
git clone https://github.com/cosmostation/cvms.git && cd cvms
# Create a config file from example config
cp .resource/example-validator-config.yaml config.yaml
# Skip copy .env file
# cp .resource/.env.example .env
# Modify the config file for your validator
vi config.yaml
# Run cvms
docker compose up --build -dExample config.yaml for validator mode
# NOTE: Customize this variables by your needs
# 1. network mode:
# ex) monikers: ['all']
# des) This will enable network mode to monitor all validators status in the blockchain network
#
# 2. validator mode:
# ex) monikers: ['Cosmostation1', 'Cosmostation2']
# des) This will enable validator mode for whitelisted specific validators
monikers: ['Cosmostation']
# if user is one of validators, they want to operator for whole chains which already operating as validator.
chains:
# NOTE: display name will be used only this config to indicate followed arguments to communicate internal team members
- display_name: 'cosmos'
# NOTE: chain_id is a key for support_chains list. YOU SHOULD match correct CHAIN ID
chain_id: cosmoshub-4
# NOTE: these addresses will be used for balance usage tracking such as validator, broadcaster or something.
tracking_addresses:
- 'cosmos1clpqr4nrk4khgkxj78fcwwh6dl3uw4ep4tgu9q'
nodes:
# NOTE: currently grpc endpoint doens't support ssl
- rpc: 'https://rpc-cosmos.endpoint.xyz'
api: 'https://lcd-cosmos.endpoint.xyz'
grpc: 'grpc-cosmos.endpoint.xyz:9090'
- display_name: 'injective'
chain_id: injective-1
tracking_addresses:
- 'inj1rvqzf9u2uxttmshn302anlknfgsatrh5mcu6la'
- 'inj1mtxhcchfyvvs6u4nmnylgkxvkrax7c2la69l8w' # eventnonce orchestrator address or something
nodes:
- rpc: 'https://rpc-injective.endpoint.xyz'
api: 'https://lcd-injective.endpoint.xyz'
grpc: 'grpc-injective.endpoint.xyz:9090'
- display_name: 'sei'
chain_id: pacific-1
tracking_addresses: []
nodes:
- rpc: 'https://rpc-sei.endpoint.xyz'
api: 'https://lcd-sei.endpoint.xyz'
grpc: 'grpc-sei.endpoint.xyz:9090'
- display_name: dydx
chain_id: dydx-mainnet-1
tracking_addresses: []
nodes:
- rpc: 'https://rpc-dydx.endpoint.xyz'
api: 'https://lcd-dydx.endpoint.xyz'
grpc: 'grpc-dydx.endpoint.xyz:9090'
- display_name: neutron
chain_id: neutron-1
tracking_addresses: []
nodes:
- rpc: 'https://rpc-neutron.endpoint.xyz'
api: 'https://lcd-neutron.endpoint.xyz'
grpc: 'grpc-neutron.endpoint.xyz:9090'
provider_nodes:
- rpc: 'https://rpc-cosmos.endpoint.xyz'
api: 'https://lcd-cosmos.endpoint.xyz'
grpc: 'grpc-cosmos.endpoint.xyz:9090'
- display_name: axelar
chain_id: axelar-dojo-1
tracking_addresses:
- axelar146kdz9stlycvacm03hg0t5fxq6jszlc4gtxgpr
nodes:
- rpc: 'https://rpc-axelar.endpoint.xyz'
api: 'https://lcd-axelar.endpoint.xyz'
grpc: 'grpc-axelar.endpoint.xyz:9090'Example config.yaml for network mode
# NOTE: Customize this variables by your needs
# 1. network mode:
# ex) monikers: ['all']
# des) This will enable network mode to monitor all validators status in the blockchain network
#
# 2. validator mode:
# ex) monikers: ['Cosmostation1', 'Cosmostation2']
# des) This will enable validator mode for whitelisted specific validators
monikers: ['all']
# if user is one of validators, they want to operator for whole chains which already operating as validator.
chains:
# NOTE: display name will be used only this config to indicate followed arguments to communicate internal team members
- display_name: 'cosmos'
# NOTE: chain_id is a key for support_chains list. YOU SHOULD match correct CHAIN ID
chain_id: cosmoshub-4
# NOTE: these addresses will be used for balance usage tracking such as validator, broadcaster or something.
tracking_addresses:
- 'cosmos1clpqr4nrk4khgkxj78fcwwh6dl3uw4ep4tgu9q'
nodes:
# NOTE: currently grpc endpoint doens't support ssl
- rpc: 'https://rpc-cosmos.endpoint.xyz'
api: 'https://lcd-cosmos.endpoint.xyz'
grpc: 'grpc-cosmos.endpoint.xyz:9090'
- display_name: 'injective'
chain_id: injective-1
tracking_addresses:
- 'inj1rvqzf9u2uxttmshn302anlknfgsatrh5mcu6la'
- 'inj1mtxhcchfyvvs6u4nmnylgkxvkrax7c2la69l8w' # eventnonce orchestrator address or something
nodes:
- rpc: 'https://rpc-injective.endpoint.xyz'
api: 'https://lcd-injective.endpoint.xyz'
grpc: 'grpc-injective.endpoint.xyz:9090'
- display_name: 'sei'
chain_id: pacific-1
tracking_addresses: []
nodes:
- rpc: 'https://rpc-sei.endpoint.xyz'
api: 'https://lcd-sei.endpoint.xyz'
grpc: 'grpc-sei.endpoint.xyz:9090'
- display_name: dydx
chain_id: dydx-mainnet-1
tracking_addresses: []
nodes:
- rpc: 'https://rpc-dydx.endpoint.xyz'
api: 'https://lcd-dydx.endpoint.xyz'
grpc: 'grpc-dydx.endpoint.xyz:9090'
- display_name: neutron
chain_id: neutron-1
tracking_addresses: []
nodes:
- rpc: 'https://rpc-neutron.endpoint.xyz'
api: 'https://lcd-neutron.endpoint.xyz'
grpc: 'grpc-neutron.endpoint.xyz:9090'
provider_nodes:
- rpc: 'https://rpc-cosmos.endpoint.xyz'
api: 'https://lcd-cosmos.endpoint.xyz'
grpc: 'grpc-cosmos.endpoint.xyz:9090'
- display_name: axelar
chain_id: axelar-dojo-1
tracking_addresses:
- axelar146kdz9stlycvacm03hg0t5fxq6jszlc4gtxgpr
nodes:
- rpc: 'https://rpc-axelar.endpoint.xyz'
api: 'https://lcd-axelar.endpoint.xyz'
grpc: 'grpc-axelar.endpoint.xyz:9090'For devents, testnets, localnet even if unsupported mainnets, Use custom_chains.yaml for CVMS
# Copy custom_chains.yaml from example
# You should locate it into docker/cvms/custom_chains.yaml
cp docker/cvms/custom_chains.yaml.example docker/cvms/custom_chains.yaml
# And then Mount your custom_chains.yaml into docker compose
# Just uncomment the CUSTOM_CHAINS_FILE
CUSTOM_CHAINS_FILE=custom_chains.yaml
# After init CVMS, you can check current support_chains with custom_chains by using exporter app
curl -X GET http://localhost:9200/support_chainsExample custom_chains.yaml
---
mintstation-1:
protocol_type: cosmos
support_asset:
denom: umint
decimal: 6
packages:
- block
- upgrade
- uptime
- voteindexer #for cometbft consensus vote
- veindexer # for vote-extension