Supervalidators

Supervalidators

• Kubernetes-Based Deployment of a Super Validator node
  • Requirements
  • Generating an SV identity
  • Preparing a Cluster for Installation
  • Configuring Authentication
  • Configuring your CometBFT node
  • Configuring BFT Sequencer Connections
  • Installing Postgres instances
  • Installing the Software
  • SV Network Diagram
  • Configuring the Cluster Ingress
  • Configuring the Cluster Egress
  • Logging into the wallet UI
  • Logging into the CNS UI
  • Logging into the SV UI
  • Observing the Canton Coin Scan UI
  • Following an Amulet Conversion Rate Feed
• Upgrades
• Network Resets of DevNet and Testnet
• Backups
  • Backup of Node Identities
  • Backup of Postgres Instances
  • Backup of CometBFT
• Pruning
  • Sequencer pruning
  • CometBFT pruning
  • Participant pruning
• Disaster Recovery
  • Restoring From Data Corruption
  • Re-onboard an SV and recover Amulets with a validator
  • Disaster recovery from loss of CometBFT layer
• Security Hardening
  • Third-party Daml apps
  • Using an external KMS for managing participant keys
• SV Operations
  • Security Notice
  • Generate a validator onboarding secret
  • Identities used by SV nodes on different layers
  • Updating the reward weight of an SV
  • Determining good synchronizer traffic parameters
  • Ignoring party IDs of stale validators in reward expiry automation
  • Determining expired SV rewards for CIP-66 flows
  • Trigger re-ingestion of the Scan Stores
• How to Bootstrap a Network
  • cometbft helm values
  • scan helm values
  • sv helm values
  • other helm values you may need to consider
  • Infra-level things you might want to consider
  • How to run through a HDM

Comments