# bifrost-relayer.rs

## What is bifrost-relayer.rs?

We recently introduced a Rust implementation of the CCCP-Relayer for the Bifrost Network. The new relayer has been reengineered to enhance overall performance and robustness across multiple blockchains. It retains the same functions as the [Python version](https://github.com/bifrost-platform/bifrost-relayer.py), processing cross-chain transactions and facilitating data transfers (e.g., feeding price information) from one blockchain to another.

The following section will guide you through the setup process about the [Rust implementation](https://github.com/bifrost-platform/bifrost-relayer.rs) of the Bifrost network's relayer.

## Install Requirements

To initiate the `bifrost-relayer`, certain dependencies must be manually installed. Both the executable binary file and the configuration YAML file are essential for all environments and operators.

First, install the latest `bifrost-relayer` release binary. You can check the latest releases by going to our GitHub repository under the [releases](https://github.com/bifrost-platform/bifrost-relayer.rs/releases) page.

```sh
wget "https://github.com/bifrost-platform/bifrost-relayer.rs/releases/latest/download/bifrost-relayer"
```

In order to execute the binary, the permission of the file has to be updated.

```sh
chmod +x bifrost-relayer
```

Then, install the configuration YAML file. This file serves as an example for a quick start. Given the minor differences between Testnet and Mainnet environments, it's crucial to use the appropriate file for the corresponding network.

```sh
# First create a directory to save your configuration file
mkdir configs && cd configs

# For mainnet only
wget "https://github.com/bifrost-platform/bifrost-relayer.rs/releases/latest/download/config.mainnet.yaml"

# For testnet only
wget "https://github.com/bifrost-platform/bifrost-relayer.rs/releases/latest/download/config.testnet.yaml"
```

## Configuration Setup

Next, the configuration YAML file contains certain parameters that the operator has to set. For instance, variables such as your relayer private key and each EVM provider's RPC endpoints depends to the operator itself, thus these values should be manually set.

You should prepare RPC endpoints for the following blockchain networks. There are two options for this: 1) operating your own blockchains nodes, or 2) utilizing services that offers RPC endpoints. You can find node providers on the links below. **It’s crucial that each node must be archive-mode enabled.**

* [Bifrost](https://docs.bifrostnetwork.com/bifrost-network/running-a-node/guide-for-operators/setting-up-a-validator-node) (**Must be priorly self-operating and fully synced**)
* [Ethereum](https://ethereum.org/en/developers/docs/nodes-and-clients/nodes-as-a-service/#popular-node-services)
* [Binance Smart Chain](https://docs.bnbchain.org/docs/rpc)
* [Polygon](https://wiki.polygon.technology/docs/pos/reference/rpc-endpoints/)
* [Base](https://docs.base.org/tools/node-providers/)
* [Arbitrum](https://docs.arbitrum.io/node-running/node-providers)
* [Bitcoin](https://bitcoin.org/en/full-node)
* [Core](https://docs.coredao.org/docs/Dev-Guide/rpc-list)
* [Oasys](https://docs.oasys.games/docs/staking/rpc-endpoint/1-1-rpc-endpoint)

### Configuration Templates

<details>

<summary>config.mainnet.yaml</summary>

```yaml
system:
  debug_mode: false

signer_config:
  # Two parameters below are optional, but one of them must be provided.
  # `kms_key_id` has higher priority than `private_key`.
  - kms_key_id: "<YOUR_KMS_KEY_ID_FOR_SIGNER>"
    private_key: "<YOUR_RELAYER_PRIVATE_KEY>"

keystore_config:
  path: "<YOUR_KEYSTORE_PATH>"
  # Two parameters below are optional, but one of them must be provided.
  # `kms_key_id` has higher priority than `password`.
  kms_key_id: "<YOUR_KMS_KEY_ID_FOR_KEYSTORE>"
  password: "<YOUR_KEYSTORE_PASSWORD>"

btc_provider:
  id: 10000
  chain: "main"
  provider: "<YOUR_BITCOIN_RPC_ENDPOINT>"
  call_interval: 10000
  block_confirmations: 2

evm_providers:
  - name: "bifrost"
    id: 3068
    provider: "<YOUR_BIFROST_RPC_ENDPOINT>"
    call_interval: 3000
    block_confirmations: 3
    is_native: true
    is_relay_target: true
    socket_address: "0xd551F33Ca8eCb0Be83d8799D9C68a368BA36Dd52"
    authority_address: "0x0000000000000000000000000000000000000400"
    relayer_manager_address: "0x0000000000000000000000000000000000002000"
    bitcoin_socket_address: "0x73A9E443F51eE40C1469A740D9CCf0118e8FD9ca"
    socket_queue_address: "0x0000000000000000000000000000000000000101"
    registration_pool_address: "0x0000000000000000000000000000000000000100"
    relay_executive_address: "0x0000000000000000000000000000000000000803"
    blaze_address: "0x0000000000000000000000000000000000000102"
  - name: "ethereum"
    id: 1
    provider: "<YOUR_ETHEREUM_RPC_ENDPOINT>"
    call_interval: 12000
    block_confirmations: 1
    is_relay_target: false
    eip1559: true
    socket_address: "0x4A31FfeAc276CC5e508cAC0568d932d398C4DD84"
    authority_address: "0xAdcaa90cabDc730855064d5b0f5242c16A9B7E10"
    chainlink_usdc_usd_address: "0x8fFfFfd4AfB6115b954Bd326cbe7B4BA576818f6"
    chainlink_usdt_usd_address: "0x3E7d1eAB13ad0104d2750B8863b489D65364e32D"
    chainlink_dai_usd_address: "0xAed0c38402a5d19df6E4c03F4E2DceD6e29c1ee9"
    chainlink_btc_usd_address: "0xf4030086522a5beea4988f8ca5b36dbc97bee88c"
    chainlink_wbtc_usd_address: "0xfdFD9C85aD200c506Cf9e21F1FD8dd01932FBB23"
    chainlink_cbbtc_usd_address: "0x2665701293fCbEB223D11A08D826563EDcCE423A"
  - name: "bsc"
    id: 56
    provider: "<YOUR_BSC_RPC_ENDPOINT>"
    call_interval: 3000
    block_confirmations: 5
    is_relay_target: false
    eip1559: true
    socket_address: "0xb5Fa48E8B9b89760a9f9176388D1B64A8D4968dF"
    authority_address: "0xF0500d77d5446665314722b963ab1F71872063E9"
  - name: "polygon"
    id: 137
    provider: "<YOUR_POLYGON_RPC_ENDPOINT>"
    call_interval: 2000
    block_confirmations: 7
    is_relay_target: false
    eip1559: true
    socket_address: "0x050606CC2Bcd9504991Be2c309D6c6c832Bb5bd0"
    authority_address: "0x7F48909fBd1E38f1e05B5E326A44175fc2462B13"
  - name: "base"
    id: 8453
    provider: "<YOUR_BASE_RPC_ENDPOINT>"
    call_interval: 2000
    block_confirmations: 7
    is_relay_target: false
    eip1559: true
    socket_address: "0xAe172D8c5E428D4b7C70f9E593b207F9daC9BF3e"
    authority_address: "0x4C7a44F3FB37A53F33D3fe3cCdE97A444F105239"
  - name: "arbitrum"
    id: 42161
    provider: "<YOUR_ARBITRUM_ONE_RPC_ENDPOINT>"
    call_interval: 2000
    block_confirmations: 5
    get_logs_batch_size: 8
    is_relay_target: false
    eip1559: true
    socket_address: "0xac1552e30857A814a225BAa81145bcB071B46DDd"
    authority_address: "0xA069a57426Cd4c53925c1847Bec01aAB832A5118"
  - name: "core"
    id: 1116
    provider: "<YOUR_CORE_RPC_ENDPOINT>"
    call_interval: 3000
    block_confirmations: 3
    is_relay_target: false
    eip1559: false
    socket_address: "0x4C7a44F3FB37A53F33D3fe3cCdE97A444F105239"
    authority_address: "0xA069a57426Cd4c53925c1847Bec01aAB832A5118"
  - name: "oasys"
    id: 248
    provider: "<YOUR_OASYS_RPC_ENDPOINT>"
    call_interval: 6000
    block_confirmations: 3
    is_relay_target: false
    eip1559: true
    socket_address: "0x4C7a44F3FB37A53F33D3fe3cCdE97A444F105239"
    authority_address: "0x48820089C1d4f5d768f6800CF647b4f5b8675CFA"

handler_configs:
  - handler_type: Socket
    watch_list: [3068, 1, 56, 137, 8453, 42161, 1116, 248]
  - handler_type: Roundup
    watch_list: [3068]

###  The items below are optional. ###

bootstrap_config:
  is_enabled: true
  round_offset: 3
  btc_block_offset: 3

sentry_config:
  environment: "<YOUR_SENTRY_ENVIRONMENT>"
  is_enabled: false
  dsn: "<YOUR_SENTRY_DSN>"

prometheus_config:
  is_enabled: false
  is_external: false
  port: 8000
```

</details>

<details>

<summary>config.testnet.yaml</summary>

```yaml
system:
  debug_mode: false

signer_config:
  # Two parameters below are optional, but one of them must be provided.
  # `kms_key_id` has higher priority than `private_key`.
  - kms_key_id: "<YOUR_KMS_KEY_ID_FOR_SIGNER>"
    private_key: "<YOUR_RELAYER_PRIVATE_KEY>"

keystore_config:
  path: "<YOUR_KEYSTORE_PATH>"
  # Two parameters below are optional, but one of them must be provided.
  # `kms_key_id` has higher priority than `password`.
  kms_key_id: "<YOUR_KMS_KEY_ID_FOR_KEYSTORE>"
  password: "<YOUR_KEYSTORE_PASSWORD>"

btc_provider:
  id: 10001
  chain: "test"
  provider: "<YOUR_BITCOIN_RPC_ENDPOINT>"
  call_interval: 10000

evm_providers:
  - name: "bifrost-testnet"
    id: 49088
    provider: "<YOUR_BIFROST_TESTNET_RPC_ENDPOINT>"
    call_interval: 3000
    block_confirmations: 3
    is_native: true
    is_relay_target: true
    socket_address: "0x0218371b18340aBD460961bdF3Bd5F01858dAB53"
    authority_address: "0x0000000000000000000000000000000000000400"
    relayer_manager_address: "0x0000000000000000000000000000000000002000"
    bitcoin_socket_address: "0xc292D9d5c31D5246cfAC67ba91202bbCF0AA8108"
    socket_queue_address: "0x0000000000000000000000000000000000000101"
    registration_pool_address: "0x0000000000000000000000000000000000000100"
    relay_executive_address: "0x0000000000000000000000000000000000000803"
    blaze_address: "0x0000000000000000000000000000000000000102"
  - name: "sepolia"
    id: 11155111
    provider: "<YOUR_SEPOLIA_RPC_ENDPOINT>"
    call_interval: 12000
    block_confirmations: 1
    is_relay_target: false
    eip1559: true
    socket_address: "0xdAcc4aeea580F782bB991eA862e1a57827Ea9D68"
    authority_address: "0xff95B9861eE5d44eC0b489B0DCB73932c7C7074B"
  - name: "bsc-testnet"
    id: 97
    provider: "<YOUR_BSC_TESTNET_RPC_ENDPOINT>"
    call_interval: 3000
    block_confirmations: 5
    is_relay_target: false
    eip1559: true
    socket_address: "0x8039c3AD8ED55509fD3f6Daa78867923fDe6E61c"
    authority_address: "0xCf9f6428A309b6652a1dfaA4d8aB8B61C9c7E8CF"
    chainlink_usdc_usd_address: "0x90c069C4538adAc136E051052E14c1cD799C41B7"
    chainlink_usdt_usd_address: "0xEca2605f0BCF2BA5966372C99837b1F182d3D620"
    chainlink_dai_usd_address: "0xE4eE17114774713d2De0eC0f035d4F7665fc025D"
    chainlink_btc_usd_address: "0x5741306c21795FdCBb9b265Ea0255F499DFe515C"
    chainlink_wbtc_usd_address: "0x5741306c21795FdCBb9b265Ea0255F499DFe515C"
  - name: "base-sepolia"
    id: 84532
    provider: "<YOUR_BASE_SEPOLIA_RPC_ENDPOINT>"
    call_interval: 2000
    block_confirmations: 7
    is_relay_target: false
    eip1559: true
    socket_address: "0xdAcc4aeea580F782bB991eA862e1a57827Ea9D68"
    authority_address: "0x15EDC0c65004548fa787Bc01e533366674946C5F"
  - name: "arbitrum-sepolia"
    id: 421614
    provider: "<YOUR_ARBITRUM_SEPOLIA_RPC_ENDPOINT>"
    call_interval: 2000
    block_confirmations: 5
    get_logs_batch_size: 8
    is_relay_target: false
    eip1559: true
    socket_address: "0xd1E060FD930B75DA9A709c91E6Ad03B330Fb2950"
    authority_address: "0x4dA97eCD85d4EE00E26C5f3aF21e6Da7bc3F71e2"

handler_configs:
  - handler_type: Socket
    watch_list: [49088, 11155111, 97, 84532, 421614]
  - handler_type: Roundup
    watch_list: [49088]

###  The items below are optional. ###

bootstrap_config:
  is_enabled: true
  round_offset: 3
  btc_block_offset: 3

sentry_config:
  environment: "<YOUR_SENTRY_ENVIRONMENT>"
  is_enabled: false
  dsn: "<YOUR_SENTRY_DSN>"

prometheus_config:
  is_enabled: false
  is_external: false
  port: 8000
```

</details>

### Configuration Parameters

The [following table](#parameter-descriptions) presents customizable parameters for the relayer. You can change each parameter according to your environment. However, we highly recommend to use the default values specified in the template except for fields that are not checked in the "Template Provided" column. Furthermore, "Template Provided" merely serves as an example, thus you must change the correct values for certain parameters (e.g., your private key).

**Generally, for safety and to prevent unexpected system malfunctions, you should refrain from altering parameters that are included in the YAML file but not explicitly specified.** If the network's self-monitoring mechanism detects a malfunction stemming from altered parameters, the offending relayer may be subject to slashing.

## Using Systemd

For operators who prefer on using Systemd, you should make a configuration file for the Systemd execution environment. First, create a configuration file in the following directory.

```sh
sudo vi /etc/systemd/system/bifrost-relayer.service
```

An example of the configuration is provided below. The following parameters should be set regarding to your setup environment.

* `<DIRECTORY_WHERE_BIFROST_RELAYER_LOCATES>` : The absolute path to the directory where the installed `bifrost-relayer` binary file locates.
* `<PATH_TO_BIFROST_RELAYER>` : The absolute path to the installed `bifrost-relayer` binary file.
* `<PATH_TO_CONFIG_FILE>` : The absolute path to the installed `config.testnet.yaml` or `config.mainnet.yaml`. This parameter will be the the value for the CLI option, `--chain`.

```systemd
[Unit]
Description=Bifrost Relayer Daemon
After=network.target
StartLimitIntervalSec=5

[Service]
Type=simple
Restart=always
RestartSec=30
SyslogIdentifier=bifrost-relayer
SyslogFacility=local7
WorkingDirectory=<DIRECTORY_WHERE_BIFROST_RELAYER_LOCATES>
ExecStart=<PATH_TO_BIFROST_RELAYER> --chain <mainnet|testnet|<PATH_TO_CONFIG_FILE>>
KillSignal=SIGHUP

[Install]
WantedBy=multi-user.target
```

<details>

<summary>Example</summary>

```systemd
[Unit]
Description=Bifrost Relayer Daemon
After=network.target
StartLimitIntervalSec=5

[Service]
Type=simple
Restart=always
RestartSec=30
SyslogIdentifier=bifrost-relayer
SyslogFacility=local7
WorkingDirectory=/home/ubuntu/example
ExecStart=/home/ubuntu/example/bifrost-relayer --chain /home/ubuntu/example/config.yaml
KillSignal=SIGHUP

[Install]
WantedBy=multi-user.target
```

</details>

### Run the Relayer Service <a href="#run-the-relayer-service" id="run-the-relayer-service"></a>

Now, the service can be started by executing the following commands. First, enable the service that will let it start automatically at every next system restart.

```sh
sudo systemctl enable bifrost-relayer
```

Then, start the Systemd service, executing instructions in the service’s configuration file, use the `start` command as mentioned below.

```sh
sudo systemctl start bifrost-relayer
```

And lastly, verify the service has successfully executed.

```sh
systemctl status bifrost-relayer
```

### Check Logs

To check your running `bifrost-relayer` service logs, execute the command below.

```sh
journalctl -f -u bifrost-relayer
```

Once the service has successfully started, the initial logs will show up similar as below.

```sh
2023-08-04T14:41:38 INFO  sc_sysinfo     ]💻 Operating system: macos
2023-08-04T14:41:38 INFO  sc_sysinfo     ]💻 CPU architecture: aarch64
2023-08-04T14:41:38 INFO  bifrost-relayer]-[main               ] Bifrost Relayer
2023-08-04T14:41:38 INFO  bifrost-relayer]-[main               ] ✌️  version 1.0.2-1053ac84663
2023-08-04T14:41:38 INFO  bifrost-relayer]-[main               ] ❤️  by bifrost-platform, 2023-2023
2023-08-04T14:41:38 INFO  bifrost-relayer]-[main               ] ⛓  Chain specification: testnet
2023-08-04T14:41:38 INFO  bifrost-relayer]-[main               ] 👤 Relayer: 0xf708d58820fa20405993e186a8b38fb777f3143a
2023-08-04T14:41:38 INFO  bifrost-relayer]-[main               ] 🔨 Relay Targets (Legacy): bifrost, bsc
2023-08-04T14:41:38 INFO  bifrost-relayer]-[main               ] 🔨 Relay Targets (EIP1559): ethereum, polygon
2023-08-04T14:41:38 INFO  bifrost        ]-[block-manager      ] 💤 Idle, best: #8495214
2023-08-04T14:41:38 INFO  ethereum       ]-[block-manager      ] 💤 Idle, best: #9459619
2023-08-04T14:41:38 INFO  polygon        ]-[block-manager      ] 💤 Idle, best: #38621155
2023-08-04T14:41:38 INFO  bsc            ]-[block-manager      ] 💤 Idle, best: #32143709
```

If the bootstrap configuration is enabled, it will then start to bootstrap historical events as below.

```sh
2023-07-14T16:00:35 INFO  bifrost        ]-[roundup-handler    ] ⚙️  [Bootstrap mode] Bootstrapping RoundUp events.
2023-07-14T16:00:35 INFO  bsc            ]-[bridge-handler     ] ⚙️  [Bootstrap mode] Bootstrapping Socket events.
2023-07-14T16:00:35 INFO  bifrost        ]-[bridge-handler     ] ⚙️  [Bootstrap mode] Bootstrapping Socket events.
2023-07-14T16:00:35 INFO  mumbai         ]-[bridge-handler     ] ⚙️  [Bootstrap mode] Bootstrapping Socket events.
2023-07-14T16:00:35 INFO  goerli         ]-[bridge-handler     ] ⚙️  [Bootstrap mode] Bootstrapping Socket events.
2023-07-14T16:00:37 INFO  bifrost        ]-[bridge-handler     ] ⚙️  [Bootstrap mode] Bootstrapping Socket events.
2023-07-14T16:00:37 INFO  bifrost-relayer]-[bridge-handler     ] ⚙️  [Bootstrap mode] Bootstrap process successfully ended.
```

After the initial launch and the bootstrap process ends, the system will wait until each chain has reached the block confirmations specified in your configuration YAML file. It will then import every new block on every interval as below.

```sh
2023-08-04T14:41:54 INFO  polygon        ]-[block-manager      ] ✨ Imported #38621155
2023-08-04T14:41:56 INFO  bifrost        ]-[block-manager      ] ✨ Imported #8495214
2023-08-04T14:41:56 INFO  polygon        ]-[block-manager      ] ✨ Imported #38621156
2023-08-04T14:41:57 INFO  bsc            ]-[block-manager      ] ✨ Imported #32143709
2023-08-04T14:41:58 INFO  polygon        ]-[block-manager      ] ✨ Imported #38621157
2023-08-04T14:41:59 INFO  bifrost        ]-[block-manager      ] ✨ Imported #8495215
2023-08-04T14:42:00 INFO  bsc            ]-[block-manager      ] ✨ Imported #32143710
2023-08-04T14:42:00 INFO  polygon        ]-[block-manager      ] ✨ Imported #38621158
2023-08-04T14:42:02 INFO  ethereum       ]-[block-manager      ] ✨ Imported #9459619
2023-08-04T14:42:02 INFO  bifrost        ]-[block-manager      ] ✨ Imported #8495216
2023-08-04T14:42:02 INFO  polygon        ]-[block-manager      ] ✨ Imported #38621159
2023-08-04T14:42:03 INFO  bsc            ]-[block-manager      ] ✨ Imported #32143711
```

If your relayer has met every system logs mentioned above, this means that it has successfully been launched and has started to operate in a healthy state.

### Upgrade Service

As the `bifrost-relayer` is under continuous development, there will be instances when it becomes necessary to upgrade your relayer service. When such upgrades become available, relayer operators will be notified either through our community channels or via direct communication. Please note that some upgrades may be optional rather than mandatory.

First, remove or backup the previous `bifrost-relayer` binary file.

```sh
rm <PATH_TO_BIFROST_RELAYER_BINARY>
```

Then, install the latest version of `bifrost-relayer` into the same directory and update permissions. (In case of directory changes, the Systemd configuration file should be modified as well)

```sh
chmod +x bifrost-relayer
```

At last, restart the Systemd service.

```sh
sudo systemctl restart bifrost-relayer
```

## Using Docker

For operators who prefer on using Docker, it must be pre-installed in your operating system. Once installed, you can proceed to the following steps.

To run the relayer as a Docker container, use the command as mentioned below.

* `<DIRECTORY_WHERE_CONFIG_FILE_LOCATES>` : The absolute path of the directory where the installed `config.testnet.yaml` or `config.mainnet.yaml` locates.
* `<YOUR_CONFIG_FILE_NAME>` : The file name of the installed configuration YAML file.
* `<YOUR_CONTAINER_NAME>` : Please set an explicit name for your relayer container.

```sh
docker run -d \
  --restart always \
  --network host \
  --mount type=bind,source=<DIRECTORY_WHERE_CONFIG_FILE_LOCATES>,target=/relayer/configs \
  --name <YOUR_CONTAINER_NAME> \
  thebifrost/bifrost-relayer.rs:latest --chain /relayer/configs/<YOUR_CONFIG_FILE_NAME>
```

<details>

<summary>Example</summary>

```sh
docker run -d \
  --restart always \
  --network host \
  --mount type=bind,source=/home/ubuntu/example,target=/relayer/configs \
  --name bifrost-relayer \
  thebifrost/bifrost-relayer.rs:latest --chain /relayer/configs/config.mainnet.yaml
```

</details>

### Check Logs

To check your running `bifrost-relayer` container logs, execute the command below.

```sh
docker logs -f <YOUR_CONTAINER_NAME>
```

### Upgrade Docker Image

As the `bifrost-relayer` is under continuous development, there will be instances when it becomes necessary to upgrade your relayer service. When such upgrades become available, relayer operators will be notified either through our community channels or via direct communication. Please note that some upgrades may be optional rather than mandatory.

First stop and remove your running relayer container.

```sh
docker stop "YOUR_CONTAINER_NAME"
docker rm "YOUR_CONTAINER_NAME"
```

Then, pull the latest `bifrost-relayer` Docker image.

```sh
docker pull thebifrost/bifrost-relayer.rs:latest
```

At last execute the following command below to start a new container.

```sh
docker run -d \
  --restart always \
  --network host \
  --mount type=bind,source=<DIRECTORY_WHERE_CONFIG_FILE_LOCATES>,target=/relayer/configs \
  --name <YOUR_CONTAINER_NAME> \
  thebifrost/bifrost-relayer.rs:latest --chain /relayer/configs/<YOUR_CONFIG_FILE_NAME>
```

## Parameter Descriptions

<table data-full-width="true"><thead><tr><th width="201">Name</th><th>Description</th><th>Example / Available Values</th><th width="122" data-type="checkbox">Required</th><th width="180" data-type="checkbox">Template Provided</th><th>Default</th></tr></thead><tbody><tr><td><code>system</code></td><td>System related parameters of the relayer.</td><td>-</td><td>true</td><td>true</td><td>-</td></tr><tr><td><code>system.private_key</code></td><td>The private key of the relayer.</td><td><code>"0x5fb92d6e98884f76de468fa3f6278f8807c48bebc13595d45af5bdc4da702133"</code></td><td>true</td><td>false</td><td>-</td></tr><tr><td><code>system.debug_mode</code></td><td>The flag that represents if the debug mode is enabled. If enabled, debug-level logs and sentry alerts will be enabled.</td><td><code>true</code> / <code>false</code></td><td>false</td><td>true</td><td><code>false</code></td></tr><tr><td><code>btc_provider</code></td><td>The parameters related to the Bitcoin chain provider.</td><td>-</td><td>true</td><td>true</td><td>-</td></tr><tr><td><code>btc_provider.id</code></td><td>The unique ID of the Bitcoin chain.</td><td><ul><li><code>10000</code> (For Mainnet)</li><li><code>10001</code> (For Testnet)</li></ul></td><td>true</td><td>true</td><td>-</td></tr><tr><td><code>btc_provider.chain</code></td><td>The name of the Bitcoin chain.</td><td><ul><li><code>"main"</code> (For Mainnet)</li><li><code>"test"</code> (For Testnet)</li></ul></td><td>true</td><td>true</td><td>-</td></tr><tr><td><code>btc_provider.provider</code></td><td>The RPC endpoint of the Bitcoin chain.</td><td>-</td><td>true</td><td>false</td><td>-</td></tr><tr><td><code>btc_provider.call_interval</code></td><td>The block synchronization interval in milliseconds. At every new interval, the system will synchronize every new block mined on the target chain.</td><td><code>10000</code></td><td>true</td><td>true</td><td>-</td></tr><tr><td><code>btc_provider.block_confirmations</code></td><td>The number of block confirmations required to synchronize a new block.</td><td><code>3</code></td><td>true</td><td>true</td><td><code>3</code></td></tr><tr><td><code>evm_providers</code></td><td>The parameters related to EVM chain providers.</td><td>-</td><td>true</td><td>true</td><td>-</td></tr><tr><td><code>evm_providers.id</code></td><td>The unique ID of the chain.</td><td><code>3068</code></td><td>true</td><td>true</td><td>-</td></tr><tr><td><code>evm_providers.name</code></td><td>The name of the chain.</td><td><code>"bifrost"</code></td><td>true</td><td>true</td><td>-</td></tr><tr><td><code>evm_providers.provider</code></td><td>The RPC endpoint of the node. If the node is running, or is expected to be operated on the same server with the relayer, then set this value to the provided example.</td><td><code>"http://127.0.0.1:9933"</code></td><td>true</td><td>false</td><td>-</td></tr><tr><td><code>evm_providers.call_interval</code></td><td>The block synchronization interval in milliseconds. At every new interval, the system will synchronize every new block mined on the target chain.</td><td><code>1500</code></td><td>true</td><td>true</td><td>-</td></tr><tr><td><code>evm_providers.block_confirmations</code></td><td>The number of block confirmations required to synchronize a new block.</td><td><code>5</code></td><td>true</td><td>true</td><td>-</td></tr><tr><td><code>evm_providers.is_relay_target</code></td><td>The flag which represents whether the system will participate in external-chain CCCP actions. If this value is set to <code>true</code>, the system will try to execute transactions on the target chain, so sufficient balances are required. This value must be set to <code>true</code> if it is the Bifrost Network.</td><td><code>true</code> / <code>false</code></td><td>true</td><td>true</td><td>-</td></tr><tr><td><code>evm_providers.eip1559</code></td><td>The flag which represents whether the system will execute EIP-1559 transactions. If set to <code>false</code>, transactions will be executed by legacy types.</td><td><code>true</code> / <code>false</code></td><td>false</td><td>true</td><td><code>false</code></td></tr><tr><td><code>evm_providers.min_gas_price</code></td><td>The minimum gas price (in WEI) that the system will setup when executing legacy transactions. If the value is null, it will be dynamically set. This field only has effect when the <code>eip1559</code> parameter is disabled.</td><td><code>30000000000</code></td><td>false</td><td>true</td><td><code>0</code></td></tr><tr><td><code>evm_providers.min_priority_fee</code></td><td>The minimum priority fee (in WEI) that the system will setup when executing EIP-1559 transactions. If the value is null, it will be dynamically set. This field only has effect when the <code>eip1559</code> parameter is enabled.</td><td><code>30000000000</code></td><td>false</td><td>true</td><td><code>0</code></td></tr><tr><td><code>evm_providers.escalate_percentage</code></td><td>The percentage that will be used on gas price escalation to replace a transaction that is stuck in the mempool. This option will only have effect for legacy transactions.</td><td><code>15.0</code></td><td>false</td><td>false</td><td><code>15.0</code></td></tr><tr><td><code>evm_providers.is_initially_escalated</code></td><td>The flag whether if the gas price will be initially escalated. The <code>escalate_percentage</code> will be used on escalation. This option will only have effect for legacy transactions.</td><td><code>true</code> / <code>false</code></td><td>false</td><td>false</td><td><code>false</code></td></tr><tr><td><code>evm_providers.get_logs_batch_size</code></td><td>The batch size (=block range) used when requesting <code>eth_getLogs()</code>. If increased the RPC request ration will be reduced, however event processing will be delayed regarded to the configured value. Default size is set  to 1, which means it will be requested on every new block.</td><td><code>5</code></td><td>false</td><td>false</td><td><code>1</code></td></tr><tr><td><code>sentry_config</code></td><td>Sentry related parameters. If this section does not exist in your configuration file, Sentry will be disabled.</td><td>-</td><td>false</td><td>true</td><td><code>None</code></td></tr><tr><td><code>sentry_config.is_enabled</code></td><td>The flag which represents whether Sentry is enabled.</td><td>-</td><td>true</td><td>true</td><td>-</td></tr><tr><td><code>sentry_config.environment</code></td><td>The identifier for the Sentry client. This value will be used to distinguish triggered alarms.</td><td><code>"mainnet"</code></td><td>false</td><td>true</td><td><code>""</code></td></tr><tr><td><code>sentry_config.dsn</code></td><td>The Sentry DSN. If the value has been set, error and warning alerts will be notified. If the value is empty, Sentry will be disabled.</td><td>-</td><td>false</td><td>false</td><td>-</td></tr><tr><td><code>prometheus_config</code></td><td>Prometheus related parameters. It this section does not exist in your configuration file, Prometheus will be disabled.</td><td>-</td><td>false</td><td>true</td><td><code>None</code></td></tr><tr><td><code>prometheus_config.is_enabled</code></td><td>The flag which represents whether Prometheus metric collection is enabled.</td><td><code>true</code> / <code>false</code></td><td>true</td><td>true</td><td>-</td></tr><tr><td><code>prometheus_config.is_external</code></td><td>The flag which represents whether the Prometheus server is exposed on all interfaces.</td><td><code>true</code> / <code>false</code></td><td>false</td><td>true</td><td><code>false</code></td></tr><tr><td><code>prometheus_config.port</code></td><td>The Prometheus exporter TCP port.</td><td><code>8000</code></td><td>false</td><td>true</td><td><code>8000</code></td></tr><tr><td><code>bootstrap_config</code></td><td>Bootstrap related parameters. Bootstrap is a process that will be executed whenever the relayer (re-)starts. It will collect historical CCCP events and let the relayer re-handle the event to prevent missed actions.</td><td>-</td><td>false</td><td>true</td><td><code>None</code></td></tr><tr><td><code>bootstrap_config.is_enabled</code></td><td>The flag which represents whether bootstrap is enabled</td><td><code>true</code> / <code>false</code></td><td>true</td><td>true</td><td>-</td></tr><tr><td><code>bootstrap_config.round_offset</code></td><td>The amount of rounds to search for missed events.</td><td><code>3</code></td><td>false</td><td>true</td><td><code>3</code></td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bifrostnetwork.com/bifrost-network/running-a-node/guide-for-operators/setting-up-a-relayer/bifrost-relayer.rs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.