Skip to main content

Configuration

Before using the Lido Staking Vault CLI, you need to configure your environment variables and wallet settings. This guide covers all necessary configuration steps to get started.

Environment Variables​

Configure your environment by creating a .env file in your project root:

# Network Configuration (Required)
CHAIN_ID=560048
CL_URL=https://your-consensus-layer-endpoint
EL_URL=https://your-execution-layer-endpoint

# Contract Deployment Configuration (Required)
DEPLOYED=deployed-hoodi-vaults-testnet-2.json

# Wallet Configuration (Choose one method)
PRIVATE_KEY=0x1234567890abcdef...

# OR use encrypted account file
ACCOUNT_FILE=wallets/account.json
ACCOUNT_FILE_PASSWORD=your_secure_password

Configuration Options​

Network Configuration​

CHAIN_ID (Required)

  • Ethereum network chain ID
  • Common values:
    • 560048: Hoodi Testnet

CL_URL (Optional)

  • Consensus Layer (Beacon Chain) RPC endpoint
  • Required for validator proof generation and beacon chain queries
  • Must support the Beacon API specification

EL_URL (Optional)

  • Execution Layer RPC endpoint
  • Must match the configured CHAIN_ID
  • Used for contract interactions and transaction broadcasting

Contract Configuration​

DEPLOYED (Required)

  • JSON file containing deployed contract addresses
  • Available configurations:
    • deployed-hoodi-vaults-testnet-2.json: Hoodi v2 testnet
    • deployed-hoodi-vaults-testnet.json: Hoodi v1 testnet
    • Custom deployment files for other networks

Wallet Configuration​

Choose one of the following wallet configuration methods:

Method 1: Private Key (Development)​

PRIVATE_KEY=0x1234567890abcdef...
  • Direct private key configuration
  • Security Warning: Not recommended for production
  • Suitable for development and testing environments
ACCOUNT_FILE=wallets/account.json
ACCOUNT_FILE_PASSWORD=your_secure_password
  • Uses encrypted keystore file
  • More secure than plain private keys
  • Compatible with standard Ethereum wallet formats

Validation​

After configuration, verify your setup:

# Check account information
yarn start account r info

# Verify network connectivity
yarn start contracts hub r info

Troubleshooting Common Issues​

Invalid Chain ID

  • Ensure CHAIN_ID matches your RPC endpoint
  • Verify the network is supported by your configuration

Account Not Found

  • Check PRIVATE_KEY format (must start with 0x)
  • Verify ACCOUNT_FILE path and password
  • Ensure wallet has sufficient ETH for gas fees

Contract Address Not Found

  • Verify DEPLOYED file exists and contains valid addresses
  • Check if contracts are deployed on your target network
  • Ensure file format matches expected JSON structure

RPC Connection Issues

  • Test endpoint connectivity outside the CLI
  • Verify API key authentication if required
  • Check for rate limiting or network restrictions

Advanced Configuration​

Multiple Environment Management​

For managing multiple environments, use separate configuration files:

# Development
cp .env.example .env.dev

# Testing
cp .env.example .env.test

# Production
cp .env.example .env.prod

Load different configurations as needed:

# Use specific environment
cp .env.test .env
yarn start account r info