Skip to main content

Network Integration

This guide covers how to integrate your deployed Relay Contracts with the broader ecosystem, including multi-chain settlement deployment, preparing for Relay binary integration, and managing network lifecycle.

Multi-Chain Settlement Deployment​

Relay networks often need to commit validator sets to multiple blockchains for cross-chain applications. Each chain requires its own Settlement contract deployment.

Architecture Overview​

Relay Network (Single)
        │
        ├─ Ethereum Settlement
        ├─ Polygon Settlement
        ├─ Arbitrum Settlement
        └─ BSC Settlement

Relay Binary Integration​

Once contracts are deployed, the Relay binary can connect and begin validator network operations.

Binary Configuration​

The Relay binary will need contract ValSetDriver contract address, network and keys configuration.

See Relay Configuration for reference.

Binary Operating Modes​

The Relay binary supports three operating modes:

1. Signer Mode​

  • Purpose: Sign messages and participate in consensus
  • Requirements: Registered operator with valid keys
  • Responsibilities:
    • Monitor for messages to sign
    • Generate BLS signatures
    • Submit signatures to aggregators

2. Aggregator Mode​

  • Purpose: Collect signatures and create aggregated signatures
  • Requirements: Network connectivity to signers
  • Responsibilities:
    • Collect individual signatures from signers
    • Aggregate signatures using BLS aggregation
    • Submit aggregated signatures to committers

3. Committer Mode​

  • Purpose: Commit validator sets and aggregated signatures to Settlement contracts
  • Requirements: Gas funds and Settlement contract access
  • Responsibilities:
    • Monitor epoch transitions
    • Commit new validator set headers
    • Submit aggregated signatures for verification

Integration Readiness​

  • ValSetDriver deployed with correct configuration
  • All operators registered with valid BLS and ECDSA keys
  • Settlement contracts deployed on all target chains
  • Initial validator set committed (Genesis setup completed)
  • Binary configuration files prepared for each operator
  • Network connectivity established between operators
  • Gas funding available for committer nodes
  • Monitoring setup for network health

Security Considerations​

Multi-Chain Security​

  • Cross-Chain Replay: Ensure signatures can't be replayed across chains
  • Bridge Security: Secure cross-chain message passing
  • Key Management: Protect operator keys across all chains
  • Upgrade Coordination: Coordinate upgrades across all deployments

Operational Security​

  • Access Control: Properly manage admin roles and permissions
  • Monitoring: Set up alerting for unusual network activity
  • Incident Response: Have procedures for handling network issues
  • Backup Plans: Maintain recovery procedures for various failure modes

Binary Integration Security​

  • Authentication: Ensure only authorized binaries can connect
  • Communication: Secure communication channels between binary nodes
  • Key Protection: Secure storage and handling of operator private keys
  • Update Management: Secure binary update and deployment processes

Network integration transforms your deployed contracts into a living validator network.

Careful attention to multi-chain deployment, binary integration, and ongoing management ensures a robust and secure network operation.