2022-09-22 Aries Framework JS Meeting notes
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
@Timo Glastra (Animo Solutions) <timo@animo.id>
@Rodolfo Miranda (RootsID) <rodolfo.miranda@rootsid.com>
@Lance Byrd (RootsID) <lance.byrd@rootsid.com>
@James Ebert (Indicio) <james.ebert@indicio.tech>
Resources
Hyperledger Discord: https://discord.gg/hyperledger (#aries-javascript and #aries-bifold)
Aries JavaScript Docs: https://aries.js.org/
Repositories:
Aries Framework JavaScript: https://github.com/hyperledger/aries-framework-javascript
Aries Framework JavaScript Extension: https://github.com/hyperledger/aries-framework-javascript-ext
Aries Mobile Agent React Native: https://github.com/hyperledger/aries-mobile-agent-react-native
Status updates
Aries Bifold (Aries Bifold User Group Meetings)
Biometrics - working towards NIST standards.
Indicio working towards latest React Native
Working on holder requesting a proof
Aries Call
Rebooting Web of Trust, The Hague, September 26-30
Agenda
Record the meeting
DIDComm V2
Ursa also has crypto, but not for DIDComm we think?
Multiple approaches
Custom implemnation with lower level crypto (e.g. Askar)
lower level, more effort
Askar has storage and crypto in one, while for a modular approach we want it separated
Already separated in AFJ through interface
In browser you don't need a native backend / advanced storage, but you do need the crypto
DIDComm library from SICPA (WASM)
WASM Support in react native is not great
React Native wrapper available, but only for Android: https://github.com/sicpa-dlab/didcomm-react-native/tree/main/android/src/main/java/com/sicpa/didcomm/reactnative
Could look at JSI interface wrapper like https://github.com/animo/react-native-bbs-signatures
DIDComm v2 branch in AFJ: https://github.com/sicpa-dlab/aries-framework-javascript/tree/didcomv2-contribution
Use our own did resolver, need also our own secret resolver.
DIDComm library in typescript
storage/data layer being abstracted into a well defined interface akin to what schema inversion technologies like PostgREST/Hasura end up providing
Wallet storage which takes advantage of Row Level Security would provide a long term option for the end user to be able to access their wallet while still enabling custodian ownership of their wallet by a identity service provider
Good discussion by Daniel Hardman about separation of Encryption and storage for wallets (starting from 49minutes)
0.3.0 release
Docker container / image environments
Meeting Notes
Future topics
Next Week:
Future Topics:
React Native testing
Monorepo dependencies
TypeScript types
ACA-py and AFJ performance/scale documentation
Mike's modularization, etc documentation
Open ID Connect for Issuance/Verification
Hyperledger fabric and Aries wrapper new updates
Meeting recording: