Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Oracle Lag #109

Open
jackhack00 opened this issue Jan 17, 2025 · 1 comment
Open

Oracle Lag #109

jackhack00 opened this issue Jan 17, 2025 · 1 comment
Assignees
Labels
bug Something isn't working deprioritized

Comments

@jackhack00
Copy link
Contributor

Low Priority, as current version still works

logic.py
line 396

  1. 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)

  2. 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

@jackhack00 jackhack00 added the bug Something isn't working label Jan 17, 2025
Copy link

linear bot commented Jan 17, 2025

AZTEC-13 Oracle Lag

Low Priority, as current version still works

logic.py
line 396

  1. 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)
  2. 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working deprioritized
Projects
None yet
Development

No branches or pull requests

2 participants