...
| Excerpt |
|---|
Planned:
|
The call
...
was recorded is available here: 20200504 Indy Contributors Call
Remember the Hyperledger Code of Conduct
...
- IIW
- BBS+
- DIDComm and CHAPI Discussion
- Update: Move to GitHub Issues from JIRA for indy-sdk, indy-node, indy-plenum
- Issues now active
- Pending: Putting in the PR to announce location of issues in READMEs
- Update: Migrate Jenkins to GitHub Actions (and perhaps Azure pipelines)
- Plan started - Sovrin resource migration
- Resources: Wade Barnes (BC Gov), Thor Wolpert (BC Gov) for first step (Indy SDK/Linux)
- Revocation 2.0 - Tech Spike on Merkle Trees in process (Daniel Hardman)
- Tech Spike Implementation: https://github.com/dhh1128/merklespike
- Notes on Issues: size of compressed leaves, resources to calculate internal nodes
- Next steps - continue with the spike
- Side note: Digital Bazaar is using a bit field as non-ZKP revocation registry
- BBS+ Signatures enables ZKPs with JSON-LD
Draft Spec: http://mattrglobal.github.io/jsonld-signatures-bbs-spec/
Draft spec repo: http://github.com/mattrglobal/jsonld-signatures-bbs-spec
BBS+ signature implementations: https://github.com/mattrglobal/node-bbs-signatures https://github.com/andrewwhitehead/ursa-bbs-py
JSON-LD signature suite to use with VC-JS: http://github.com/mattrglobal/jsonld-signatures-bbs
Regarding credential schema definitions in the vc data model: http://w3c.github.io/vc-data-model/#data-schemas
Proof formats in the VC Data Model: http://w3c.github.io/vc-data-model/#proof-formats
The paper for “provable security”: http://eprint.iacr.org/2016/663.pdf
- Next steps:
- Revocation - credential status field
- Predicates?
- CCG - being put forward by Mattr
- Question: How does required reveal work at the crypto layer.?
Future Calls
Next call:
Future:
...