2021-02-12 Aries Framework JS Meeting notes

Date

Feb 12, 2021

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

• @Jakub Koci (Absa) <jakub.koci@gmail.com>

• @Timo Glastra (Animo Solutions) <timo@animo.id>

Status updates

• Issue credential protocol

  • Still needed:

    • Start with credential proposal

    • advanced threading

    • validate credential preview against actual credential

    • storing messages

• Present proof protocol

  • Feature branch: https://github.com/hyperledger/aries-framework-javascript/tree/feature/present-proof

Agenda

• Record the meeting

• Update meeting calendar event

• WebSockets

Meeting Notes

• Move to bi-weekly meeting (for a while)

  • 2021-02-12

  • 2021-02-26

  • ...

• Import / Export

• Use record state values that match RFC

  • PROPOSAL_RECEIVED → proposal-received

• Store complete didcomm message, but add util methods to make it easier to work it.

  • next version: Add option to remove the history of messages (like in ACA-Py, auto-remove option)

• Modules will have ids that reference records as input, Services will use the actual record objects as input

• find vs get

  • findXXX → can return null

  • getXXX → will throw error if not found

  • Create dedicated error class for RecordNotFound

  • https://github.com/hyperledger/aries-framework-javascript/issues/78

  • findAll vs getAll

• Response messages

  • negotiate vs createXXXAsResponse

  • module will use negotiate

  • service will use createXXXAsResponse

• Auto accept present proof

  • Auto send ack message? (https://github.com/hyperledger/aries-rfcs/issues/471)

• State machines

  • https://github.com/hyperledger/aries-framework-javascript/pull/130#discussion_r517635298

  • Aries Framework .NET → https://github.com/hyperledger/aries-framework-dotnet/blob/a18bef91e5b9e4a1892818df7408e2383c642dfa/src/Hyperledger.Aries/Features/IssueCredential/Records/CredentialRecord.cs#L164

  • Implement ourselves rather than use a library to implement state machines

  • Make it smarter than Aries protocols

    • Transition state according to message type

Future topics