-
Notifications
You must be signed in to change notification settings - Fork 60
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
New Idemix Integration with W3C support, preparation #731
base: main
Are you sure you want to change the base?
Conversation
func NewDeserializerWithBCCSP(ipk []byte, verType csp.VerificationType, nymEID []byte, cryptoProvider csp.BCCSP) (*Deserializer, error) { | ||
func NewDeserializerWithBCCSP( | ||
sm SchemaManager, | ||
schema string, |
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.
Imho the deserializer shouldn't know anything about the schema at construction time. Info on the schema type should come later through the normal APIs from the protobuf data. This is why in the initial implementation I had cached the value of the public key and only decided to parse it later as soon as the schema type was known through the proper channels. See here where I cached it and here where I deferred the parsing of the IPK.
0c11276
to
7f85de4
Compare
Use the `SerializedIdemixIdentity` proto definition from the idemix repo and not from fabric, whence idemix has been removed. Signed-off-by: Alessandro Sorniotti <[email protected]> Signed-off-by: Angelo De Caro <[email protected]>
Signed-off-by: Angelo De Caro <[email protected]>
Signed-off-by: Angelo De Caro <[email protected]>
Signed-off-by: Angelo De Caro <[email protected]>
Signed-off-by: Angelo De Caro <[email protected]>
7f85de4
to
e2b61d1
Compare
Signed-off-by: Angelo De Caro <[email protected]>
This PR does the following: