pub(crate) struct BlockSyncClientConfiguration {
pub(crate) chain_id: ChainID,
pub(crate) request_limit: u32,
pub(crate) response_timeout: Duration,
pub(crate) blacklist_expiry_time: Duration,
pub(crate) block_sync_trigger_min_view_difference: u64,
pub(crate) block_sync_trigger_timeout: Duration,
}Expand description
Configuration parameters that define the behaviour of the BlockSyncClient. These should not
change after the block sync client starts.
Fields§
§chain_id: ChainIDChain ID of the target blockchain. The block sync client will only process advertise messages whose Chain ID matches the configured value.
request_limit: u32The maximum number of blocks requested with every block sync request.
response_timeout: DurationTimeout for waiting for a single block sync response.
blacklist_expiry_time: DurationTime after which a blacklisted sync server should be removed from the block sync blacklist.
block_sync_trigger_min_view_difference: u64By how many views a PC received via AdvertisePC must be ahead of the current view in order to
trigger sync (via the event-based sync trigger).
block_sync_trigger_timeout: DurationHow much time needs to pass without any progress (i.e., updating the highest PC) or sync attempts in order to trigger sync (via the timeout-based sync trigger).