Skip to content

README.md

Latest commit

 

History

History
106 lines (75 loc) · 4.15 KB

README.md

File metadata and controls

106 lines (75 loc) · 4.15 KB

Replace-Operator Scripts

Scripts to automate the replace-operator workflow for Charon distributed validators.

Overview

These scripts help operators replace a single operator in an existing distributed validator cluster. This is useful for:

  • Operator rotation: Replacing an operator who is leaving the cluster
  • Infrastructure migration: Moving an operator to new infrastructure
  • Recovery: Replacing an operator whose keys may have been compromised

Warning: This is an alpha feature in Charon and is not yet recommended for production use.

There are two scripts for the two roles involved:

  • remaining-operator.sh - For operators staying in the cluster
  • new-operator.sh - For the new operator joining the cluster

Important: All participating operators (remaining + new) run the charon alpha edit replace-operator ceremony together. The new operator must receive the current cluster-lock.json BEFORE the ceremony begins.

Prerequisites

  • .env file with NETWORK and VC variables set
  • .charon directory with cluster-lock.json and charon-enr-private-key
  • Docker running
  • jq installed

For Remaining Operators

Automates the complete workflow for operators staying in the cluster:

./scripts/edit/replace-operator/remaining-operator.sh \
    --new-enr "enr:-..." \
    --old-enr "enr:-..."

Before running: Share your current cluster-lock.json with the new operator so it can participate in the ceremony.

Options

Option Required Description
--new-enr <enr> Yes ENR of the new operator
--old-enr <enr> Yes ENR of the operator being replaced
--skip-export No Skip ASDB export if already done
--dry-run No Preview without executing
-h, --help No Show help message
Environment Variable Description
WORK_DIR Override the repository root directory (defaults to auto-detected repo root)

Workflow

  1. Export ASDB - Stop VC if running and export anti-slashing database
  2. Run ceremony - Execute charon alpha edit replace-operator with new ENR
  3. Update ASDB - Replace pubkeys in exported ASDB to match new cluster-lock
  4. Stop containers - Stop charon and VC
  5. Backup and replace - Backup old cluster-lock, install new one
  6. Import ASDB - Import updated anti-slashing database
  7. Print start commands - Display commands to start containers manually (wait ~2 epochs before starting)

For New Operators

Two-step workflow for the new operator joining the cluster.

Step 1: Generate ENR and share with remaining operators:

./scripts/edit/replace-operator/new-operator.sh --generate-enr

Step 2: After receiving cluster-lock.json from remaining operators, run the ceremony together with all other operators:

./scripts/edit/replace-operator/new-operator.sh \
    --cluster-lock ./received-cluster-lock.json \
    --old-enr "enr:-..."

After the ceremony completes, the script automatically backs up the old .charon directory and installs the new configuration from the output directory.

Options

Option Required Description
--cluster-lock <path> No Path to cluster-lock.json (for ceremony)
--old-enr <enr> No ENR of the operator being replaced (for ceremony)
--generate-enr No Generate new ENR private key
--dry-run No Preview without executing
-h, --help No Show help message
Environment Variable Description
WORK_DIR Override the repository root directory (defaults to auto-detected repo root)

Related