Summary
- Status of indy-node CI/CD and the Ubuntu upgrade
- did:indy PRs
- Discussion Topic: did:indy resolution of non-DIDs – schema, etc.
Recording of Call:
Chat from Call:
Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit the Hyperledger Code of Conduct. |
---|
Welcome and Introductions
Attendees
- Stephen Curran (Cloud Compass Computing Inc.) <swcurran@cloudcompass.ca>
Related Calls and Announcements
- Upcoming Indicio course on Indy Node development
Release Status and Work Updates
- Indy Node
- GitHub actions led by Wade Barnes
- Ubuntu 20.04 upgrade led by Robin Klemens
- Sovrin Updates Wade Barnes
- New branching model led by Wade Barnes
- indy-node-container Crisitan Kubis ( https://github.com/tsurai ), has created a Node Controller Container (docs), allows containerized indy nodes to participate in pool restart and upgrade
- Indy SDK
- GitHub actions led by Patrik Stas
- Indy Monitoring - https://github.com/hyperledger/indy-node-monitor
- Indy/Aries Shared Libraries - Hyperledger (indy-vdr, indy-shared-rs, aries-askar)
- Ursa
- Hyperledger Contribution Campaign ( Stephen Curran )
- Indy DID Method – https://hyperledger.github.io/indy-did-method/
Meeting Topics
- Update on CI/CD Update and Ubuntu Upgrade: Status Document
- Indy-Plenum Status:
- Done, 16.04, 20.04, Jenkins and GHA
- Indy-Node Status:
- Done, 16.04, 20.04, Jenkins and GHA
- One 20.04 running in the IDUnion network of 16.04 nodes
- indy-test-automation Status:
- Circular dependency broken
- Developer tools
- indy-node-container and GitPod tools available
- Indy-SDK build progress
- Indy-Plenum Status:
- "did:indy" DID Method
- Pull Requests:
- New method for self-certifying NYMs - #27 - updated per discussion last meeting
- Change to use SHA-256, but use the full public key as input
- Proposal - change the separator for the sub-network from ":" to "." - #31
- Fix Typos - #24
- Newly Merged: Add the new Indy DID method to the W3C registry: https://github.com/w3c/did-spec-registries - #393
- New method for self-certifying NYMs - #27 - updated per discussion last meeting
- Discussion topic - referencing non-DIDs via DID Indy and other DID Methods
- Issue raised to adjust the method: #32
- Simple Issue: Change format from
<did>/<object-type>/<object-type-identifier>
, to<did>/anoncreds/v1/<object-type>/<object-type-identifier>
- Simple Issue: Change format from
- Related issues (raised in comment):
- Is this the best approach from a DID Resolution perspective?
- What object would we expect to get back from such a DID resolution? Presumably an object of the desired type, but should it be a DIDDoc with the object embedded?
- Easy for did:indy, but for the broader use of AnonCreds, will this work with other DID Methods?
- Would other common DID Methods be able to support this? E.g. What other DID Methods are important for AnonCreds and could they support this approach?
- Issue raised to adjust the method: #32
- Issue: If Indy SDK is not updated, how do we run the Indy Node/Plenum tests? TBD
- Pull Requests:
Future Calls
- Ideas for "Good First Task" for the Indicio class coming up in two weeks
- Issues that could impact indy-node on 20.04
- indy-sdk: needs an upgrade to OpenSSL 1.1 to properly support Ubuntu 18.04/20.04. For indy-node, just using indy-sdk as is.
- Multiple libsodium versions could impact consensus – intermittent issue on a mixed network.
- Plans for a new Indy-SDK release?
- A few people from the community have asked.
- The most recent request has been for a release to include this feature; https://github.com/hyperledger/indy-sdk/pull/2400
- Indy Contributor Campaign
- Focus: Indy Generation Next
- Audience: Organizations building Indy Instances, applications built on Indy
- Not going for casual, independent developers, more on organizations that can assign developers to work on the project for a set chunk of time (e.g one month)
- Key Features:
- Indy network of networks support
- Indy support for W3C DID Standard 1.0
- Tasks:
- Update NYM to support new "diddoc_content" data element
- Indy-sdk, indy-vdr support for new "diddoc_content" data element
- Indy DID Resolver support for new "diddoc_content"
- indy-sdk, indy-vdr support for multiple ledgers
- Support for new ledger object identifiers
- Handling cred_defs that references schema on other ledgers
- Possible: support for NYM "keri_keystate" data element, indy-sdk/indy-vdr support and DID resolver support
- Other?
- Foundational Work:
- did:indy spec. as a spec.
- Tasks in GitHub Issues - tagged for campaign
- Getting started with developing indy-plenum and indy-node
- Tutorial: Sample feature to add to indy-node
- Example: rich schema feature flag
- Tutorial: Sample feature to add to indy-node
- Campaign work
- Landing page
- Video: Intro to Indy Generation Next
- Meetup channels
- Audience: Organizations building Indy Instances, applications built on Indy
- Focus: Indy Generation Next
- Status of Indy-SDK
- Statement on the future of the Indy SDK: PR 2329
- Plans for future of Indy CLI (move to Indy VDR?)
- Indy SDK in test for Indy Node (move to Indy VDR?)
- Status of GitHub Actions for the Indy-SDK
- Indy bugs
- Using GitHub tags "Good First Issue" and "Help Wanted"
- Node 1490: problems with large catch-up
- Plenum 1506: view change message consensus calculation error
- Hyperledger campaign to recruit additional developers.