/
2019-10-22 Framework Go Weekly Planning

2019-10-22 Framework Go Weekly Planning

Jan 05, 2021

Summary:

Planned topics

  • Work updates (5 mins)

  • Grooming (20 mins)

  • Design discussion (20 mins)

  • Open Discussion (10 mins)

Date

Oct 22, 2019 (7:30AM Los Angeles, 10:30AM Toronto/New York, 3:30PM London, 17:30H Moscow)

Remember the Hyperledger Code of Conduct

Anti-Trust Policy:

Linux Foundation meetings involve participation by industry competitors, and it is the intention of the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws.

Examples of types of actions that are prohibited at Linux Foundation meetings and in connection with Linux Foundation activities are described in the Linux Foundation Antitrust Policy available at http://www.linuxfoundation.org/antitrust-policy. If you have questions about these matters, please contact your company counsel, or if you are a member of the Linux Foundation, feel free to contact Andrew Updegrove of the firm of Gesmer Updegrove LLP, which provides legal counsel to the Linux Foundation.

Attendees

Welcome / Introductions

Announcements

  • None

Release status

  • None

Work updates (from the previous week)

  • Protocol Failure - Update state to abandoned and trigger message notification GitHub #480 - @Rolson Quadras

  • PeerDID Generation in Wallet GitHub #485 - @Rolson Quadras

  • Split service.Handle function for Inbound/Outbound type GitHub #490 - @Rolson Quadras

  • Introduce protocol service implementation (work in progress) #464 (@Андрій Солук )

  • Refactored Crypto operations out of Legacy Wallet #352 (@Filip Burlacu)

  • Update wallet to include signature and encryption key pairs (work in progress) #488 (@Baha A Shaaban )

  • Include key type (algorithm) to support multiple key types (Bundled with #488 above) #272 (@Baha A Shaaban)

  • persistence layer for storing and retrieving connection record details issue-527/issue-526  (talwinder)@Talwinder Kaur )

  • Service update to consume connection recorder storage issue-397 (@Talwinder Kaur )

  • HTTP DID Resolver: bddtest using sidetree-node (@Firas Qutishat )

  • HTTP DID Resolver: bddtest using sidetree-fabric ( @Firas Qutishat )

  • Support for public DID in create/handle invitation #503 (@Sandra Vrtikapa  )

  • BDD test for create invitation  with public DID  #525 (@Sandra Vrtikapa  )

  • Completed persisting DIDs in wallet #486 (@Sudesh Shetty )

  • Currently working on REST API demo/bddtest #94 #491 (@Sudesh Shetty )

  • Finished basic Webhook flow with sample notification #200 (@derektrider)

  • Make Webhook supply real data (in progress) #472 (@derektrider)

  • Support Verifiable Presentation data model #371 (@Dmitriy Kinoshenko)

  • JWT proof of Verifiable Presentation #483 (@Dmitriy Kinoshenko)

Grooming updates (from the previous week)

  • Controller/Webhook/Rest API GitHub #539 - @Rolson Quadras @derektrider

Design discussion

Milestone progress

  • TBD

Other business

  • TBD

Future topics

  • TODO -  Storage of keys in the wallet - need to support multiple types of storages (leveldb, memcache/redis, hsm, etc.) @Baha A Shaaban @Filip Burlacu

  • TODO - model separate storages - Transient data vs secrets vs did doc (public/peer did) vs connection info vs metadata vs persistent data

Action items

[Groom] Introduce protocol (callback function) @Андрій Солук
Add stories for public DID @Sandra Vrtikapa
Return recipient key  as correlation id from packager @Baha A Shaaban