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
{{ message }}
Repository navigation
Open question about calculating total values for the Subgraph Entity #83
The PR #147 adds batch updates for a specific curation value (currentSignalledTokens), but the logic used to update that value would also work for this issue.
Just as a side note, as in the case of curation, we would be showing "double counted" GRT, since even if they are different subgraphs, for indexers it's the same one, so it will be displayed as two different subgraphs with the same amount of GRT (which is kinda confusing if you don't really understand the details).
I think that "double counted" GRT is fine, and it's the route we decided to go with #147 since when we tried to make it more "subgraph" based it ended up with weird numbers (negative signal, for example) on cases of shared deployments, and it's even worse when comparing stakes, since that's not even possible to break it down.
Activity
juanmardefago commentedon Jul 28, 2021
The PR #147 adds batch updates for a specific curation value (
currentSignalledTokens), but the logic used to update that value would also work for this issue.Just as a side note, as in the case of curation, we would be showing "double counted" GRT, since even if they are different subgraphs, for indexers it's the same one, so it will be displayed as two different subgraphs with the same amount of GRT (which is kinda confusing if you don't really understand the details).
I think that "double counted" GRT is fine, and it's the route we decided to go with #147 since when we tried to make it more "subgraph" based it ended up with weird numbers (negative signal, for example) on cases of shared deployments, and it's even worse when comparing stakes, since that's not even possible to break it down.