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
Revert "feat: remove maxTimestampSpread and only rely on expiry" (#504)
This reverts commit ac1c5406441c01119eaf9c0de54512f7cfe1ff19.
### Description
Brings back the maxTimestampSpread setting. A visual explanation here:
<img width="918" alt="image"
src="https://github.com/user-attachments/assets/02dfaadb-f029-4f38-8bd5-965644b4a4b5">
We need it because CELO/USD has a heartbeat of 24hr and PHP/USD
5minutes, therefore we could be in a situation where the spread between
reports is quite large, and if we rely only on max timestamp spread we
could be reporting with stale data. The rule of thumb is:
- Set `maxTimestampSpread` by considering the largest heartbeat
frequency.
- Set `tokenExpiry` in SortedOracles by considering the shortest
heartbeat frequency.
### Other changes
N/A
### Tested
Yup
### Related issues
N/A
### Backwards compatibility
N/A
### Documentation
N/A
---------
Co-authored-by: chapati <[email protected]>
Co-authored-by: philbow61 <[email protected]>
0 commit comments