socialsirius/didcomm repository overview

⁠An intuitive solution to DIDComm Messaging, wrapped up in a single app!

⁠Summary

The dominant paradigm in mobile and web development today is duplex request-response. You call an API with certain inputs, and you get back a response with certain outputs over the same channel (Http over TCP connection)

Unfortunately, many agents are not good analogs to web servers. They may be mobile devices that turn off at unpredictable intervals and that lack a stable connection to the network. They may need to work peer-to-peer, when the internet is not available. They may need to interact in time frames of hours or days, not with 30-second timeouts. They may not listen over the same channel that they use to talk.

Because of this, the fundamental paradigm for DIDComm is

• message-based
• asynchronous
• simplex.

Agent X sends a message over channel A. Sometime later, it may receive a response from Agent Y over channel B. This is much closer to an email paradigm than a web paradigm

⁠Features

This repo contains server-side part of DIDComm⁠ infrastructure to solve DIDComm challenges in Mobile Apps development:

⁠Docs

• AdminGuide⁠
• Quick Start⁠
• Overview⁠

⁠Samples

1. Create P2P connection with Mediator https://github.com/Sirius-social/didcomm/blob/main/examples/begin.py⁠
2. Check P2P connection examples/check_connection.py⁠
3. Allocate Http endpoint (simplex transport) and receive messages from others examples/endpoint.py⁠
4. Create/Remove/Update routing keys examples/routing_keys.py⁠