Files
proxmox/docs/runbooks/RECOVERY_PROCEDURES.md
defiQUG fbda1b4beb
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
docs: Ledger Live integration, contract deploy learnings, NEXT_STEPS updates
- ADD_CHAIN138_TO_LEDGER_LIVE: Ledger form done; public code review repo bis-innovations/LedgerLive; init/push commands
- CONTRACT_DEPLOYMENT_RUNBOOK: Chain 138 gas price 1 gwei, 36-addr check, TransactionMirror workaround
- CONTRACT_*: AddressMapper, MirrorManager deployed 2026-02-12; 36-address on-chain check
- NEXT_STEPS_FOR_YOU: Ledger done; steps completable now (no LAN); run-completable-tasks-from-anywhere
- MASTER_INDEX, OPERATOR_OPTIONAL, SMART_CONTRACTS_INVENTORY_SIMPLE: updates
- LEDGER_BLOCKCHAIN_INTEGRATION_COMPLETE: bis-innovations/LedgerLive reference

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-02-12 15:46:57 -08:00

2.0 KiB

Recovery Procedures

Last Updated: 2026-01-31
Document Version: 1.0
Status: Active Documentation


Purpose: Step-by-step recovery procedures for various failure scenarios


🔄 Transaction Recovery

Stuck Transaction

Scenario: Transaction pending for extended period

Recovery:

  1. Check transaction status

    cast tx <tx_hash> --rpc-url $RPC_URL
    
  2. Check nonce

    cast nonce <address> --rpc-url $RPC_URL
    
  3. Retry with higher gas

    bash scripts/retry-failed-transactions.sh
    

💰 Balance Recovery

Insufficient Balance

Scenario: Not enough ETH or LINK for operations

Recovery:

  1. Check current balances

    bash scripts/check-bridge-status.sh
    
  2. Transfer funds

    • Transfer ETH to deployer address
    • Transfer LINK tokens if needed
  3. Verify balances

    cast balance <address> --rpc-url $RPC_URL
    

🔗 Chain Configuration Recovery

Missing Destination Chain

Scenario: Destination chain not configured

Recovery:

  1. Verify chain selector

  2. Add destination

    bash scripts/configure-bridge-destinations.sh
    
  3. Verify configuration

    bash scripts/verify-bridge-configuration.sh
    

🌐 Network Recovery

RPC Outage

Scenario: RPC endpoint unavailable

Recovery:

  1. Check RPC status

    cast block-number --rpc-url $RPC_URL
    
  2. Switch to backup RPC

    • Update RPC_URL in .env
    • Restart services
  3. Verify connectivity

    bash scripts/health-check.sh
    

🔒 Security Recovery

Unauthorized Access

Scenario: Suspicious activity detected

Recovery:

  1. Pause bridge immediately

    cast send <BRIDGE_ADDRESS> "pause()" --rpc-url $RPC_URL --private-key $PRIVATE_KEY
    
  2. Review logs

    tail -1000 logs/alerts-*.log
    
  3. Rotate keys if needed

  4. Resume after security review


Last Updated: $(date)