Tore Frederiksen

@micwallace it looks good, but would be nice with a negative test validating that keys from "wrong" conferences cannot be used to verify. I.e. that a key for Devcon 6...

Note that the reason the tests fail is not because of the change, but because the smart contract integration tests fails due to obsolescence of Rinkeby

@colourful-land can you give me a list of the initial capabilities you are thinking about? So far I am just adding, read, write and deletage.

Hi @darakhbharat, sorry if I am misunderstanding the specific problem/assignment, but @oleggrib already implemented the AttetsationCrypto in javascript, so you can use his code to compute these aspects and then...

Part 1 has been partially handled in PR #113 where support for nonce in the ZK proofs have been added (though it is optional). So far it is only used...

Regarding point 1. the thought was that if we could make the design change relatively easy, perhaps without needing support for the old and new ASN format at the same...

If we remove them now, I think we need to first change the default issuance structure to issuer attestation that only use **notBeforeInt** and **notAfterInt**. Then after that is deployed,...

Yes, I agree with you @oleggrib on both points. I think it makes sense to make the default behaviour to just include notBeforeInt and notAfterInt. And then after a month...

Bump. This issue is still relevant, especially since others are showing interest in our ZK based ideas. @weiwu-zhang can we maybe push this?

I am not sure option 1 form #266 is sufficient in this case. It depends on the use-cage. For example if the user needs to prove the same email used...