​

Delegation

​

Command Structure

taiyi-cli delegate [OPTIONS] <KEY_SOURCE> [KEY_SOURCE_OPTIONS]

​

Global Options

​

Key Source Options

​

Local Keystore (Recommended)

Use this method if you manage your validator keys locally:

taiyi-cli delegate \
  --relay-url https://relay.holesky.luban.wtf \
  --underwriter-pubkey a6767d972d21a17843ea94da59461a04d8d0baf92f7c518653170e708f4b21d537db56f9b73810252e0f4e99cc9184cb \
  --network holesky \
  local-keystore \
  --path /path/to/validators \
  --password-path /path/to/secrets

Options:

• --path: Path to validator keystore directory
• --password-path: Path to password file
• --password: Direct password input (not recommended)

​

Secret Keys

For development or testing with raw private keys:

taiyi-cli delegate \
  --relay-url https://relay.holesky.luban.wtf \
  --underwriter-pubkey a6767d972d21a17843ea94da59461a04d8d0baf92f7c518653170e708f4b21d537db56f9b73810252e0f4e99cc9184cb \
  --network holesky \
  secret-keys \
  --secret-keys 0x123...,0x456...

Options:

• --secret-keys: Comma-separated list of private keys

​

Dirk Remote Signer

For production setups using Dirk key management service:

taiyi-cli delegate \
  --relay-url https://relay.holesky.luban.wtf \
  --underwriter-pubkey a6767d972d21a17843ea94da59461a04d8d0baf92f7c518653170e708f4b21d537db56f9b73810252e0f4e99cc9184cb \
  --network holesky \
  dirk \
  --url https://dirk.example.com \
  --wallet-path /wallets \
  --passphrases pass1,pass2 \
  --client-cert-path /path/to/client.crt \
  --client-key-path /path/to/client.key \
  --ca-cert-path /path/to/ca.crt

Options:

• --url: Dirk service endpoint
• --wallet-path: Path to wallets in Dirk
• --passphrases: Comma-separated passphrases
• --client-cert-path: Client certificate path
• --client-key-path: Client key path
• --ca-cert-path: CA certificate path (optional)

​

Network Information

For Holesky testnet:

• Relay URL: https://relay.holesky.luban.wtf
• Underwriter Public Key: a6767d972d21a17843ea94da59461a04d8d0baf92f7c518653170e708f4b21d537db56f9b73810252e0f4e99cc9184cb

​

Troubleshooting

Common issues and solutions:

1. Connection Timeout: Increase timeout with --relay-request-timeout
2. Invalid Key Format: Ensure BLS public key is in correct format
3. Authentication Failed: Verify keystore path and password
4. Network Mismatch: Confirm correct --network parameter

For additional support, check the operator documentation or join our tg support channel.