Run bitcoin monitor and provider

In this step we start the monitor and provider binaries, which we will use throughout the whole demo.

Step 1: Run Monitor and Provider for each validator

Let's run the monitor and provider for each validator. Make sure every process is run in a separate terminal window/pane. Also make sure you are in the bitcoin-ipc repo and have run cargo build --release.

We are already starting the monitor and the provider for all validators and users. Some of them will be used in later steps of this demo. This is only done for convenience, it is also possible to start the monitor and provider for each validator later — at the latest before deploying the docker containers for that validator.

Validator 1

./target/release/monitor --env ~/.ipc/validator1/.env

./target/release/provider --env ~/.ipc/validator1/.env

Validator 2

./target/release/monitor --env ~/.ipc/validator2/.env

./target/release/provider --env ~/.ipc/validator2/.env

Validator 3

./target/release/monitor --env ~/.ipc/validator3/.env

./target/release/provider --env ~/.ipc/validator3/.env

Validator 4

./target/release/monitor --env ~/.ipc/validator4/.env

./target/release/provider --env ~/.ipc/validator4/.env

Validator 5

./target/release/monitor --env ~/.ipc/validator5/.env

./target/release/provider --env ~/.ipc/validator5/.env

User 1

./target/release/monitor --env ~/.ipc/user1/.env

./target/release/provider --env ~/.ipc/user1/.env

User 2

./target/release/monitor --env ~/.ipc/user2/.env

./target/release/provider --env ~/.ipc/user2/.env