You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently the DVM has been pushing alterts on gas price submissions. The issue here is that gas price is simply much more volatile than any spot price query ID. We should be able to set a confidence threshold override for more volatile query IDs.
For example, a confidence threshold of 10% (-c 0.10) for alerts on all query IDs unless it's ID 0x48e9e2c732ba278de6ac88a3a57a5c5ba13d3d8370e709b3b98333a57876ca95 (gas price) then use 25% confidence threshold (-c 0.25) simply because gas price is so volatile. Gas price can increase 2x in less than a minute when the network is busy.
Does this sound like a good idea? bad idea?
The text was updated successfully, but these errors were encountered:
Recently the DVM has been pushing alterts on gas price submissions. The issue here is that gas price is simply much more volatile than any spot price query ID. We should be able to set a confidence threshold override for more volatile query IDs.
For example, a confidence threshold of 10% (
-c 0.10
) for alerts on all query IDs unless it's ID0x48e9e2c732ba278de6ac88a3a57a5c5ba13d3d8370e709b3b98333a57876ca95
(gas price) then use 25% confidence threshold (-c 0.25
) simply because gas price is so volatile. Gas price can increase 2x in less than a minute when the network is busy.Does this sound like a good idea? bad idea?
The text was updated successfully, but these errors were encountered: