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
Currently, we use the most up-to-date delegation sets when creating the delegation graph.
Instead, we should use the delegations that were active at the snapshot block.
For this, we need to select a "main chain" that we use for the snapshot block. For other networks, we will need to use the timestamp of the snapshot block (from the "main chain").
After this, the delegation graph for a specific snapshot (block number) should only need to be computed once (and cached for later retrievals).
This will force us to store a lot more information (one delegation graph for every proposal). Related issue: #17.
The text was updated successfully, but these errors were encountered:
Currently, we use the most up-to-date delegation sets when creating the delegation graph.
Instead, we should use the delegations that were active at the snapshot block.
For this, we need to select a "main chain" that we use for the snapshot block. For other networks, we will need to use the timestamp of the snapshot block (from the "main chain").
After this, the delegation graph for a specific snapshot (block number) should only need to be computed once (and cached for later retrievals).
This will force us to store a lot more information (one delegation graph for every proposal). Related issue: #17.
The text was updated successfully, but these errors were encountered: