-
Notifications
You must be signed in to change notification settings - Fork 5
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
Feature/Verify Token V2 #78
base: main
Are you sure you want to change the base?
Conversation
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.
I left some comments .
go.mod
Outdated
github.com/iden3/go-schema-processor/v2 v2.4.0 | ||
github.com/iden3/iden3comm/v2 v2.5.1 | ||
github.com/iden3/go-schema-processor/v2 v2.5.0 | ||
github.com/iden3/iden3comm/v2 v2.7.1-0.20241015160531-d8ea65210731 |
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.
It needs code in iden3/iden3comm#60 that should be accepted, merged and released before accepting this one.
}, | ||
}, | ||
{ | ||
name: "Verify JWZ token, with proof generation delay", |
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.
This test is failing because network inside token is 80001 and there is no resolver for it.
I guess I need a valid token, or to mock eth.Resolvers. To mock eth.Resolvers, we should create a new interface in iden3comm lib for map[int]eth.Resolvers
First implementation was #76 .
There is some test failing. Need some help here to generate a proper token or to mock eth.Resolver.
This PR needs this iden3/iden3comm#60 merged. Right now it compiles because direct commit is fixed in backend.
I will write some comments by myself in points I need help or I'm not totally happy with it.