Ensure gasFeeCap
and priorityFeeCap
are fetched at the same height
#2954
Labels
zetaclient
Issues related to ZetaClient
Describe the Issue
From the current logic
gasFeeCap
andpriorityFeeCap
at a different height and breaking the invariantgasFeeCap>=priorityFeeCap
This required the fix #2950
The values are fetched in two different query in
node/zetaclient/chains/evm/observer/observer_gas.go
Line 54 in b56e758
Possible solution
Fetch first the current height of the chain, then perform both query for this specific height.
The text was updated successfully, but these errors were encountered: