Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Minutes/2021 14 07 #316

Merged
merged 4 commits into from
Jul 15, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
65 changes: 65 additions & 0 deletions docs/meeting-notes/2021-07-14.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,65 @@
# 🗓️ 14-07-2021 Team Identity: Async Meeting Notes
###### tags: `IOTA Identity` `Meeting` `Docs`

## ℹ️ Info
**Location**: Google Hangouts
**Date**: Wednesday, 14-07-2021 - 17:00 to 18:00 (Berlin)
**Agenda**
- 1. Standup `15min`
- 2. Discussion topics `45min`

## 👥 Participants
- @JelleMillenaar
- @PhilippGackstatter
- @eike-hass
- @abdulmth
- @CraigBester
- @l1h3r

### ⏪ What did you achieve last week?
- @JelleMillenaar: Opened Issues, Kanban boards, new projects, presentations, Identity for Things hardware
- @eike-hass: Small discussion with @abdulmth about docusaurus/REPL integration
- @CraigBester: added `publicKeyMultibase` support, investigating slow examples/tests, reading standards.
- @abdulmth: WASM Browser Examples, Docusaurus Example integration, Learning about identity standards.
- @PhilippGackstatter: Impl async methods for the identity actor, get actor to compile to Wasm
- @l1h3r: Clean up examples, Refactor DID chains

### What did block you?
- @PhilippGackstatter: Errors aren't serializable, that's an issue for both networking and FFI, wasm-bindgen snippets don't (yet) work with nodejs :( making libp2p websocket transport unavailable there
- @CraigBester: circular dependency when updating iota.rs (iota-client) package, low-level examples throwing network errors after update
-

### ⏩ What will be the focus this week?
- @abdulmth: documentaion migration to docusaurus.
- @PhilippGackstatter: Get a Wasm PoC working for the identity actor
- @l1h3r: Finish refactoring DID chains, add account WASM bindings
- @JelleMillenaar: Finish planning 1.0, hardware, ZKP, Streams sync
- @CraigBester: investigate/fix slow examples/tests issues, start implementing `publicKeyJwk` afterwards
-

## 💬 Discussion topics
- @PhilippGackstatter: Error handling for the actor and FFI & Actor handler API
- @eike-hass: example snippets workflow / expectations
- @JelleMillenaar: IOTA Identity on IoT Hardware (ST, Intel, RFID) - C-bindings
- PublickeyBase58 removal / publicKeyJwk?


## Circular Dependency (Preserve Order)
- Shared dependency with Identity
- Either serde_json & wasm-bindgen
- https://github.com/iotaledger/crypto.rs/pull/94 Root of the problem?

## Slow Debug version
- WASM unaffected atm
- Devin Link issue:
- ~~https://github.com/iotaledger/iota.rs/pull/480~~
- [permanode support](https://github.com/iotaledger/iota.rs/pull/586)

## publicKeyJwk
- JSON web signatures - Normalization non - JSON-LD

## Error handling - Nested Enums
- Only C-style enums possible with FFI
- Needs to be serializable
- Struct with ErrorCodes linked to String descriptions
- 2 integers (Inner and outer) + Descriptions