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
tl;dr we shouldn't rely on drand providing endpoints for historical beacons. It's both not scalable, incorrect in certain epochs and not reliable.
The downside of this is reduced performance when requesting beacon entries for really old epochs, e.g., first epoch of calibnet.
Completion Criteria
Identify places where we call the drand servers for beacon data - if the data is available on chain, we should not do this and get that tipset's drand entry. There is at least one -
Summary
An excellent summary is provided in filecoin-project/lotus#12527 (comment)
tl;dr we shouldn't rely on drand providing endpoints for historical beacons. It's both not scalable, incorrect in certain epochs and not reliable.
The downside of this is reduced performance when requesting beacon entries for really old epochs, e.g., first epoch of calibnet.
Completion Criteria
forest/src/rpc/methods/state.rs
Lines 1725 to 1758 in 5fd1ec5
Additional Links & Resources
The text was updated successfully, but these errors were encountered: