Deploy commit-boost-signer and taiyi-boost

This guide will walk you through the process of deploying commit-boost-signer and taiyi-boost on the Helder Devnet.

Prerequisites

  • A Helder validator (reth + lighthouse bn + lighthouse vc) deployed on the same server

Build Binaries

commit-boost-signer

  1. Clone the repository:

    git clone https://github.com/Commit-Boost/commit-boost-client.git
    
  2. Build the binary:

    cargo build --release # target binary: ./target/release/commit-boost-signer
    

    The target binary will be located at ./target/release/commit-boost-signer.

taiyi-boost

  1. Clone the repository:

    git clone git@github.com:lu-bann/taiyi.git
    
  2. Build the binary:

    cargo build --release # target binary: ./target/release/taiyi-boost
    

    The target binary will be located at ./target/release/taiyi-boost.

Configuration

Create a configuration file that will be shared by both cb-signer and taiyi-boost. Save this as cb-config.toml:

Run

<path-to>/commit-boost-signer
<path-to>/taiyi-boost