Page History

...

BC Gov Indy DiD Method Code With Us opportunity: https://digital.gov.bc.ca/marketplace/opportunities/code-with-us/e3dd1605-cc1d-4c30-a9ee-245940bccd0d

Training - significant response to these postings!

• Aries Training: https://twitter.com/Hyperledger/status/1472971986800316417
• Indy Node "Deep Dive": https://wiki.hyperledger.org/display/events/Hyperledger+Indy+Technical+Deep+Dive

Release Status and Work Updates

...

• Developer Experience:
  • VS Code Dev container: https://github.com/hyperledger/indy-node/pull/1718 - minor updates
  • Gitpod Dev container: https://github.com/hyperledger/indy-node/pull/1722 - minor updates
  • Documentation being updated and getting merged
• 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:
    • Merged (no circular dependencies!!!!!) - 16.04
    • Still to be done: 20.04 – systemd image needs to be replaced – may have to be created.
    • Workflow to trigger - needs a secret setup / Ry Jones
  • Currently releasing development artifacts – left to do is a tag-based official release process - Wade Barnes with help from Robin Klemens
  • ** Sovrin Release - Wade Barnes Status:
    • Working ready to start in the three repos in Sovrin
• Getting Started on the "did:indy" DID Method
  
  • Overview (if needed)
    • Indy DID Method – https://hyperledger.github.io/indy-did-method/
  • BC Gov (tentative) planscode with us launched
  • IDUnion plans
  • Discussion
    • Need a pull request to add the new Indy DID method to the W3C registry: https://github.com/w3c/did-spec-registries
    • Paul Bastianstarted the Indy DID Resolver driver. Will publish a WIP PR when he has an MVP.
• 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.

Future Calls

• 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
    • Campaign work
      • Landing page
      • Video: Intro to Indy Generation Next
      • Meetup channels

...