-
Notifications
You must be signed in to change notification settings - Fork 57
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
chore(rln-relay): confirm that the provided credential is correct using onchain query #1980
Conversation
You can find the image built from this PR at
|
bb0e2b7
to
131934c
Compare
131934c
to
b0c984a
Compare
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.
ah just realized that memberExists
should actually be memberExistsOrExisted
(forget the naming). I mean, since the contract is dummy and just emit events, it can't really know if the member exists. It just can know if it exists or existed in the past. Because at some point someone can "unregister" the membership and it won't exist anymore.
Perhaps right now it doesn't matter as we dont "revoke" credentials, but in the future I guess we can't realy on this?
Err, the contract does store commitments onchain so it is possible to know if the member exists |
ah in that case we're good. Thought it was pure event based with no state kept in the contract. noice. |
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.
lgtm
Is this is the PR that introduced these contract changes? |
yessir |
Description
Updates tests to use zero-based indexing in the contract deployed at
0x59af93Bb30ED234418E6fC2324597e3FD72FB90e
on sepoliaAlso checks that the decrypted credential's commitment does in fact belong to the tree by calling
memberExists()
on the rln storage contractChanges