-
Notifications
You must be signed in to change notification settings - Fork 19
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
Verite integration updates #160
Conversation
_supportedCredentialSchemas[verificationResult.schema], | ||
"INVALID_SCHEMA" | ||
); | ||
require(_supportedCredentialSchemas[schema], "INVALID_SCHEMA"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just so I understand -- we're treating multiple schemas as a single schema, is essence? And does order matter? If there are schemas A,B, and C, and we only support A and B, would we need to register AB and BA? With many schemas, would that get complex to manage?
Another option might be to keep them as separate entries in the mapping, and then iterate here to check that each is included. On registration, we would iterate as well. Just a thought.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, in this case they must have all the schemas and they're treated as a single schema in essence
This PR updates the VeriteAccessControl contract to support Circle's verifier, specifically the new array of schemas.
I have some things that need to be cleaned up, but overall wanted to get this visible for comments ASAP