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
If we build a subgraph for the BrightID-EthereumAddressService, we can probably offload to The Graph any computation involved with filtering poll results based on BrightID accounts. This way, the client would only get a list of valid votes.
Better still, we may even be able to have The Graph compute the current state of the poll. So the client just receives percentages for and against.
Didn't see the issue in this repo until now. Probably an outdated response, but anyway:
Building the subgraph is related to the Burn Signal app, not the BrightID-EthereumAddressService. Since all this service does is link addresses to BrightID, without any smart contract interaction, so The Graph would have no events to listen for.
I would either close this issue or move to the Burn Signal repo along with a spec of all the information we want to get from the subgraph.
If we build a subgraph for the BrightID-EthereumAddressService, we can probably offload to The Graph any computation involved with filtering poll results based on BrightID accounts. This way, the client would only get a list of valid votes.
Better still, we may even be able to have The Graph compute the current state of the poll. So the client just receives percentages for and against.
What are your thoughts @Tomasvrba?
The text was updated successfully, but these errors were encountered: