Key Points

...

...

Lastly, just to make sure everyone has the current links for the DID Data Model and Generic Syntax Implementer’s Draft 01 spec:

• PDF version 68 (static)
• Google docs version 20 (accepts comments)

Private DIDs in wallet not ledger

To update this thread and avoid confusion, the technology has been evolving, and pairwise DIDs are now not typically written to the ledger. They are known by and held only by their respective endpoints.

Understanding DIDs, URIs and routing agents 

...

https://identity.foundation/didcomm-messaging/spec/

DIDComm messages Over CHAPI protocol is an option for some use cases

https://iiw.idcommons.net/101_Session:_Verifiable_Credential_Handler_(CHAPI)_and_DIDComm

iiw-didcomm-chapi-101 Session_ Verifiable Credential Handler (CHAPI) and DIDComm - IIW.pdf

DIDCOMM 101

Q&A - Some requests for more explicit definitions:

From the charter of the DIDComm WG at DIF: “Produce one or more high-quality specs that embody a method (“DIDComm”) for secure, private and (where
applicable) authenticated message-based communication, where trust is rooted in DIDs and depends on the messages
themselves, not on the external properties of the transport(s) used. The method must be usable over many means of
transport, including those that are asynchronous and simplex, and ones that do not necessarily use the internet. It
must support routing and relay through untrusted intermediaries, not just point-to-point delivery. In addition to the
communication and protocols described above, the protocols for exchanging DIDs/keys to bootstrap such
communication are within scope. These protocols can be the foundation of higher-level protocols such as credential
exchange and higher-level authentication protocols.”

DIDComm in layman’s terms: http://www.windley.com/archives/2019/06/did_messaging_a_batphone_for_everyone.shtml

From Geovane Fedrecheski and Oliver Terbu, in the chat: “DIDComm is a standard way to exchange DID-aware encrypted messages, regardless of transport (e.g., unlike TLS, which is limited to TCP)
- a set of subprotocols and related messages, such as those used for credentials exchange”

Other Q&A

Sam Curren: explicit ACKs allowed (but not forced at this level), threading (see RFC [1])

Image Added

Image Added

VON Use Case - BC Gov Verifiable Organizations Network

...

france-did-ssi-biometricupdate.com-France announces user-controlled mobile digital identity app for use with national ID.pdf file

France announces a new system for proving digital identity  via a smartphone

The official announcement describes the details of the new app. SGIN will be based on the biographic data held in the new French ID cards launched in August 2021. It will only work with the new credit card-sized CNIe 

It will not access the card holder’s biometrics, in France’s case images of two fingerprints. It is also not compulsory and allows card-holders to be selective as to what data fields they share for any transaction:

“The application allows the user, in particular, to generate electronic certificates comprising only the identity attributes which he considers necessary to transmit to third parties of his choice.”

The decree also stipulates how long data can be kept. It has been developed in light of EU regulations on digital identity and the free movement of data.

SSI - the best solution for CeDeFi

...

cheqd - a decentralized, permissionless payments framework with authentic data

cheqd, are building the payment rails for authentic data*. We want to make it as easy as possible to create authentic data ecosystems through customisable commercial models and governance structures, all built upon a public permissionless network with a dedicated token for payment

Why SSI needs a token for decentralized payment systems

https://blog.cheqd.io/why-self-sovereign-identity-needs-a-token-an-expanded-version-46e93e9f519f

traditional rails don't work when issuers and receivers of credentials are unlikely to have a direct contractual relationship since the user is at the centre.

SSI DID Services Providers

...