1
- # The main configuration file for the Commit-Boost sidecar.
1
+ # The main configuration file for the Commit-Boost sidecar.
2
2
# Some fields are optional and can be omitted, in which case the default value, if present, will be used.
3
3
4
4
# Chain spec id. Supported values: Mainnet, Holesky, Helder
@@ -18,7 +18,7 @@ port = 18550
18
18
# Whether to forward `status` calls to relays or skip and return 200
19
19
# OPTIONAL, DEFAULT: true
20
20
relay_check = true
21
- # Timeout in milliseconds for the `get_header` call to relays. Note that the CL has also a timeout (e.g. 1 second) so
21
+ # Timeout in milliseconds for the `get_header` call to relays. Note that the CL has also a timeout (e.g. 1 second) so
22
22
# this should be lower than that, leaving some margin for overhead
23
23
# OPTIONAL, DEFAULT: 950
24
24
timeout_get_header_ms = 950
@@ -34,10 +34,11 @@ skip_sigverify = false
34
34
# Minimum bid in ETH that will be accepted from `get_header`
35
35
# OPTIONAL, DEFAULT: 0.0
36
36
min_bid_eth = 0.0
37
+ # How late in milliseconds in the slot is "late". This impacts the `get_header` requests, by shortening timeouts for `get_header` calls to
37
38
# List of URLs of relay monitors to send registrations to
38
39
# OPTIONAL
39
40
relay_monitors = []
40
- # How late in milliseconds in the slot is "late". This impacts the `get_header` requests, by shortening timeouts for `get_header` calls to
41
+ # How late in milliseconds in the slot is "late". This impacts the `get_header` requests, by shortening timeouts for `get_header` calls to
41
42
# relays and make sure a header is returned within this deadline. If the request from the CL comes later in the slot, then fetching headers is skipped
42
43
# to force local building and miniminzing the risk of missed slots. See also the timing games section below
43
44
# OPTIONAL, DEFAULT: 2000
@@ -55,12 +56,12 @@ url = "http://0xa1cec75a3f0661e99299274182938151e8433c61a19222347ea1313d839229cb
55
56
headers = { X-MyCustomHeader = " MyCustomValue" }
56
57
# Whether to enable timing games, as tuned by `target_first_request_ms` and `frequency_get_header_ms`.
57
58
# These values should be carefully chosen for each relay, as each relay has different latency and timing games setups.
58
- # They should only be used by advanced users, and if mis-configured can result in unforeseen effects, e.g. fetching a lower header value,
59
+ # They should only be used by advanced users, and if mis-configured can result in unforeseen effects, e.g. fetching a lower header value,
59
60
# or getting a temporary IP ban.
60
- #
61
+ #
61
62
# EXAMPLES
62
63
# Assuming: timeout_get_header_ms = 950, frequency_get_header_ms = 300, target_first_request_ms = 200, late_in_slot_time_ms = 2000
63
- #
64
+ #
64
65
# 1) CL request comes at 100ms in the slot (max timeout 1050ms in the slot), then:
65
66
# - sleep for 100ms
66
67
# - send request at 200ms with 850ms timeout
@@ -112,13 +113,13 @@ id = "DA_COMMIT"
112
113
type = " commit"
113
114
# Docker image of the module
114
115
docker_image = " test_da_commit"
115
- # Additional config needed by the business logic of the module should also be set here.
116
+ # Additional config needed by the business logic of the module should also be set here.
116
117
# See also `examples/da_commit/src/main.rs` for more information
117
118
sleep_secs = 5
118
119
119
120
# Configuration for how metrics should be collected and scraped
120
121
[metrics ]
121
- # Path to a `prometheus.yml` file to use in Prometheus. If using a custom config file, be sure to add a
122
+ # Path to a `prometheus.yml` file to use in Prometheus. If using a custom config file, be sure to add a
122
123
# file discovery section as follows:
123
124
# ```yml
124
125
# file_sd_configs:
0 commit comments