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
We currently (<=nv21) load the "latest" beacon entry when validating a new block. This is needed to validate our current chained beacon.
Post-nv22, we will be using unchained randomness (see FIP-0063), and therefore do not need to look up the previous randomness when validating. We can omit this step from block validation as a sync optimization.
The text was updated successfully, but these errors were encountered:
We currently (<=nv21) load the "latest" beacon entry when validating a new block. This is needed to validate our current chained beacon.
Post-nv22, we will be using unchained randomness (see FIP-0063), and therefore do not need to look up the previous randomness when validating. We can omit this step from block validation as a sync optimization.
The text was updated successfully, but these errors were encountered: