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
Now that the protocol has migrated to Arbitrum One we need to update the algorithm for getting epoch start blocks.
The arbitrum network subgraph tracks epoch start blocks using L1 block numbers, so we can no longer rely on it for this information. Instead, the epoch subgraph will need to be used to identify the start block for an epoch, i.e the block that POIs should be generated when closing an allocation in that epoch.
The text was updated successfully, but these errors were encountered:
fordN
changed the title
Bug: Epoch block numbers always show L1 blocks, need to use epoch subgraph to get network specific epoch start blocks
Use epoch subgraph to get network specific epoch start blocks
Sep 17, 2024
Now that the protocol has migrated to Arbitrum One we need to update the algorithm for getting epoch start blocks.
The arbitrum network subgraph tracks epoch start blocks using L1 block numbers, so we can no longer rely on it for this information. Instead, the epoch subgraph will need to be used to identify the start block for an epoch, i.e the block that POIs should be generated when closing an allocation in that epoch.
The text was updated successfully, but these errors were encountered: