elesto-dao / elesto

The ElestoDAO node
Apache License 2.0
4 stars 1 forks source link

DID Comm information header #125

Closed PaddyMc closed 2 years ago

PaddyMc commented 2 years ago

The information header display information about the selection connection. The design and the connection information don't match, just make it make sense.

The information stored in a connection in the aries agent looks like:

ConnectionID: "af31e679-f1d1-46a0-b2b5-833fb6cc11a0"
DIDCommVersion: "v1"
Implicit: false
InvitationDID: "did:cosmos:elesto-canary-1:agent25529"
InvitationID: "d3a08328-afa3-47ea-b137-6d18723fda7b"
MediaTypeProfiles: null
MyDID: "did:peer:1zQmarRVzM1y5WgR7pmS7XAtUqzMmupfsMTbMAy8yVB7QFp8"
Namespace: "my"
ParentThreadID: ""
RecipientKeys: Array(1)
0: "did:cosmos:elesto-canary-1:agent25529#83BWD__RzbE-AsKnYBEaaWjvyF0OEvm1SsherOHXUcQ"
length: 1
[[Prototype]]: Array(0)
RoutingKeys: null
ServiceEndPoint: ""
State: "abandoned"
TheirDID: ""
TheirLabel: "EVMOSRegistry"
ThreadID: "d3a08328-afa3-47ea-b137-6d18723fda7b"

and the design is as follows: Selection_109.png

Selection_107.png