-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrate EAS #88
Comments
@escottalexander did you have a particular reason to use the SDK instead of hitting the GraphQL API? It seems like the SDK is geared more toward writing attestations than querying them, and I didn't find any obvious way to check whether or not a connected address is a badgeholder. Lmk if I'm missing something! |
@swellander I assumed the SDK was for reading and writing. We most likely won’t be writing so feel free to use the GraphQL api if it is more straight forward. |
@swellander Let me research this some more and get back to you. |
Sounds good, thanks! |
@escottalexander any word on this? Or should I just go with the graphql API? |
@swellander I am adding the waiting tag to this because it is possible that this data will be accessed through a different API (Agora) but their API is not providing it yet. We will need to integrate with their API for other data too so might save some time if we just use them and forget about a direct EAS integration. |
Got it, that sounds good 👍 |
EAS has an SDK that we can leverage to see whether an address is a badgeholder or not. Here is the badgeholder schema that we will need to determine whether a user has voting privileges or not.
We will likely be using EAS to look at other schemas so we should make sure our methods are somewhat un-opinionated if possible.
The text was updated successfully, but these errors were encountered: