Page History

...

• AnonCreds Roadmap 2024
  • Hyperledger TOC Requirement for projects to submit an Annual Report
  • Currently working on the report
  • Looking to have a discussion about the Roadmap at next Monday's meeting
  • Possible List:
    • AnonCreds W3C VC Format
    • Finalized v1.0 Spec.
    • AnonCreds v2.0
      • Combine with other efforts around Data Integrity Proofs and BBS+ Signatures.
      • Combine ZKP/non-ZKP Revocation implementation (ALLOSAUR and StatusList2021)
      • W3C VC Format
      • Hyperledger Labs Agora
      • Draft Specification v2.0
      • Experiment with Post Quantum PS Signatures
• Aries Issue Credential / Present Proof Attachments
  • Current: Indy, JSON-LD - which do we use, or should we define another that (also) handles JWTs?
  • HackMD: https://hackmd.io/JEIOxf_ETnaX33kTIu7YJw?view
  • Outcome still to be defined.  Leading proposals:
    • Issue either:
      • With RFC 0592/0771 and add handling for an extra an proof type, or
      • With the new attachment format being proposed by Timo
    • Present either:
      • With RFC 0592/0771 for AnonCreds presentations and RFC 0510 (DIF Presentation Exchange) for JSON-LD presentations, or
      • With RFC 0510 for both AnonCreds and JSON-LD presentations
        • Extending the 0510 handling for generating/verifying AnonCreds presentations by automating the finding of AnonCreds source VCs for a presentation from DIF PE data, and creating a DIF PE Submission.
          • Challenge: I think (to be confirmed), an AnonCreds presentation requires including an AnonCreds-format presentation request. Can that be produced?  Should it be, since the verifier already has it...
      • NOTE: If an AnonCreds VC is to also have a non-AnonCreds DataIntegrityProof that also has holder binding, the AnonCreds VC MUST have an "id" field explicitly added, and hold a DID.  We can document that.
• Chat:

...