Get the maxExpectedTimePerBlock
parameter directly from the chain
#2037
Labels
A: blocked
Admin: blocked by another (internal/external) issue or PR
I: configuration
Internal: related to Hermes configuration
I: logic
Internal: related to the relaying logic
I: rpc
Internal: related to (g)RPC
O: usability
Objective: cause to improve the user experience (UX) and ease using the product
Milestone
Summary
hermes
currently expects users to provide themax_block_time
parameter in the config and uses it to calculate the connection block delay as well as max clock drift. We can get this parameter directly from the chain (eg. using the/header
Tendermint ABCI endpoint). Also, since this is a genesis parameter and isn't expected to change, we can cache it.PS: Thanks to @ancazamfir for these ideas!
Acceptance Criteria
maxExpectedTimePerBlock
param.max_block_time
config parameter. Also, remove this config parameter entirely.For Admin Use
The text was updated successfully, but these errors were encountered: