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
oracle_juice_per_wei uses generic_oracle, which sets lag to default 5. This is only true for the gas price and blob gas price oracles. The other oracles (juice_per_wei and proving_cost can be updated more frequently, but its not guaranteed that someone updates them)
I might read incorrectly, but it seems that we always update after min_oracle_update_lag_c
We should mark that as an assumption, but no need to change (it is possible for the gas price / blob gas price oracle value to change after min_oracle_update_lag_c , but not guaranteed - which can increase the lag further)
A/C:
oracle_juice_per_wei does not have a minimum lag
Ideal: Distribution of how likely it is that this oracle gets updated every L1 slot.
Why: This would have varying lag over the simulation (value is likely updated every 3-5 slots anyways I guess), and in combination with the maximum update % also increase and compound lag for shocks
Still acceptable: No minimum lag, or marking as assumption and keeping a default lag of 5 for now
The text was updated successfully, but these errors were encountered:
oracle_juice_per_wei uses generic_oracle, which sets lag to default 5. This is only true for the gas price and blob gas price oracles. The other oracles (juice_per_wei and proving_cost can be updated more frequently, but its not guaranteed that someone updates them)
I might read incorrectly, but it seems that we always update after min_oracle_update_lag_c
We should mark that as an assumption, but no need to change (it is possible for the gas price / blob gas price oracle value to change after min_oracle_update_lag_c , but not guaranteed - which can increase the lag further)
A/C:
oracle_juice_per_wei does not have a minimum lag
Ideal: Distribution of how likely it is that this oracle gets updated every L1 slot.
Why: This would have varying lag over the simulation (value is likely updated every 3-5 slots anyways I guess), and in combination with the maximum update % also increase and compound lag for shocks
Still acceptable: No minimum lag, or marking as assumption and keeping a default lag of 5 for now
Low Priority, as current version still works
logic.py
line 396
oracle_juice_per_wei uses generic_oracle, which sets lag to default 5. This is only true for the gas price and blob gas price oracles. The other oracles (juice_per_wei and proving_cost can be updated more frequently, but its not guaranteed that someone updates them)
I might read incorrectly, but it seems that we always update after min_oracle_update_lag_c
We should mark that as an assumption, but no need to change (it is possible for the gas price / blob gas price oracle value to change after min_oracle_update_lag_c , but not guaranteed - which can increase the lag further)
A/C:
oracle_juice_per_wei does not have a minimum lag
Ideal: Distribution of how likely it is that this oracle gets updated every L1 slot.
Why: This would have varying lag over the simulation (value is likely updated every 3-5 slots anyways I guess), and in combination with the maximum update % also increase and compound lag for shocks
Still acceptable: No minimum lag, or marking as assumption and keeping a default lag of 5 for now
The text was updated successfully, but these errors were encountered: