Description
Summary
Intelligently compute number of packets to batch broadcast based on max_gas
.
Problem Definition
It looks like when there are a lot of pending packets the relayer will pull and try to broadcast up to 50 packets at a time. However, if the max_gas
in the config is lower than the gas requirement to broadcast all these packets, the transaction will fail and the relayer doesn’t seem to relay those pending packets, so they’re effectively stuck.
Proposal
It’s not the greatest fix to have to adjust the max_gas
requirement — is there some config for max packets to relay at once? Not sure if, after the batch broadcast fails, hermes then tries to relay the packets 1 by 1? A helpful feature that still does batch broadcasting could calculate the proper number of packets to batch broadcast that’s within the max_gas
config and relay that amount.
Acceptance Criteria
Either a feature is implemented to support this, or there is a workaround we don't yet know of!
For Admin Use
- Not duplicate issue
- Appropriate labels applied
- Appropriate milestone (priority) applied
- Appropriate contributors tagged
- Contributor assigned/self-assigned
Metadata
Metadata
Assignees
Labels
Type
Projects
Status