[2023-07-11 08:09.06 +0000]

Looking forward to workshop.
Aries framework JS workshop @ Hyperledger

[2023-07-11 08:21.25 +0000]

Create Week 4 summary.
post @ Blog

[2023-07-12 09:35.13 +0000]

Good 10 min quick intro to sql language. https://youtu.be/IlPPUxZy-cM

Concepts: https://www.programiz.com/sql/database-introduction

[2023-07-12 10:41.38 +0000]

Sql" - Table is a set of rows, with predefined columns (/column titles). - We can select rows by value of their columns items. aka keys. - At least one column in the table must have unique values, to identify the rows uniquely. Such a column with unique values can be assigned to be the tables 'primary key'. - Primary way to identify rows of table uniquely is by using a column with unique values. Such column is termed the primary key. - Primary key must be unique.

[2023-07-12 16:27.41 +0000]

• Read about Pick up protocol, Pickup protocol v2
• Found the forward message protocol after some search. link

I am going to assume that aries-vcx will take care of the encryption and unwrapping part. I ~~have to~~ shall consider the mediator dealing with unwrapped messages for now. Of course the unwrapping will have to be done, but that should be a function call to vcx I imagine (after setting it up initially of course).

[2023-07-12 16:59.32 +0000]

Concepts: https://www.programiz.com/sql/database-introduction

https://blog.logrocket.com/interacting-databases-rust-diesel-vs-sqlx/

[2023-07-13 09:53.13 +0000]

Going through a lot of protocol and specs content today (and yesterday)

Will link them later. Rn I am going through message crate in aries-vcx repo. Looking at the Forward message definition.

Reading:

• [x] https://github.com/hyperledger/aries-rfcs/blob/main/concepts/0094-cross-domain-messaging/README.md
• [x] Forward message type
  https://github.com/hyperledger/aries-rfcs/blob/main/concepts/0094-cross-domain-messaging/README.md#agent-message-format
• [x] https://github.com/hyperledger/aries-rfcs/blob/main/concepts/0020-message-types/README.md
• [x] https://github.com/hyperledger/aries-rfcs/blob/main/features/0211-route-coordination/README.md

Hmm. Options for mediation: - endpoint based on customer. bad for privacy - Endpoint for each key. wasteful. - common endpoint. how to identify which key to send to. the to field could be a diddoc. - Maybe we can start with requiring the to field to be a full "recipient_key": "did:key:z6MkpTHR8VNsBxYAAWHut2Geadd9jSwuBV8xRoAnwWsdvktH" - And store keylist for each customer. so any mail for key will fo to corresponding mailbox. This map is sensitive info ( server should keep securely).

Q: How does server identify, the user. The key add, key update messages have no mailbox_id etc associated. Maybe we add it tot he message spec, or use requesters signing pub key to identify mailbox.

[2023-07-13 11:18.34 +0000]

@Bodgan Q: So can you tell me about message parts MsgParts Q: into_msg_with_type macro. What is kind. Is that version. Q: Why do we have PartialEq A: needed for testing. to compare 2 instances. Q: What is this NoDecorators

Aries Message enum, in lib.rs

Q: Never ~ !

Serde Tagged deserialization.

untagged serde enum is not recommended

Looks a bit like routing.

• Protocol Enum
• AriesMessage Enum

[2023-07-17 11:10.06 +0000]

@Bodgan had given a look through at the Message crate.

---

---