Re: Verifiable Data Registries

Tony, no examples I know of, however the Peer DID method
<https://openssi.github.io/peer-did-method-spec/> is a method for
direct DID-to-DID connections with holders that will be one component of
deployments of Hyperledger Aries wallets and agents that are going into
production. Note that the verifier is not relying on a peer DID for
verification of the issuer of a credential, just for verifying the
connection with the holder.

On Sat, May 30, 2020 at 4:16 PM Tony Rose <tony@proofmarket.io> wrote:

> Are there any examples in production or PoC where a P2P network has been
> used by a developer to publisha DID method that verifiers are trusting?
>
> --
> *Tony Rose*
> +1 650 504 5154
>
> *This message and any attachments are intended only for the use of the
> intended recipient(s), are confidential, and may be privileged. If you are
> not the intended recipient, you are hereby notified that any review,
> retransmission, conversion to hard copy, copying, circulation or other use
> of this message and any attachments is strictly prohibited. If you are not
> the intended recipient, please notify the sender immediately by return
> e-mail, and delete this message and any attachments from your system. Thank
> You.*
> On May 30, 2020, 3:11 PM -0700, Drummond Reed <drummond.reed@evernym.com>,
> wrote:
>
> On Fri, May 29, 2020 at 10:30 AM MXS Insights <mxsinsights@gmail.com>
> wrote:
>
>> I’ve been going through the recent DID's Editor’s Draft and a question
>> came to mind on what the characteristics of a Verifiable Data Registry
>> are.  So, I started looking through the VC spec and Data Model and find
>> similar language across all the different spec’s, data models,...
>>
>> A role a system might perform by mediating the creation and verification
>> <https://www.w3.org/TR/vc-data-model/#dfn-verify> of identifiers, keys,
>> and other relevant data, such as verifiable credential
>> <https://www.w3.org/TR/vc-data-model/#dfn-verifiable-credentials>
>> schemas, revocation registries, issuer public keys, and so on, which might
>> be required to use verifiable credentials
>> <https://www.w3.org/TR/vc-data-model/#dfn-verifiable-credentials>. Some
>> configurations might require correlatable identifiers for subjects
>> <https://www.w3.org/TR/vc-data-model/#dfn-subjects>. Example verifiable
>> data registries include trusted databases, decentralized databases,
>> government ID databases, and distributed ledgers. Often there is more than
>> one type of verifiable data registry utilized in an ecosystem.
>>
>> From: VC Data Model
>>
>> The question that came to mind, is there a more definitive definition of
>> what a Verifiable Data Registry is?  What characteristics must it have?
>> Usually, i have been equating it to a DLT, but I know that I have heard
>> conversations indicating that it specifically was not restricted to this
>> technology.
>>
>
> Michael, a verifiable data registry is definitely not limited to being a
> DLT. I am currently working on a definition of the term for section 2
> (Terminology) of the DID spec, since we made decision to switch from *DID
> Registry* (which has always been a very confusing term in the context of
> DIDs) to *Verifiable Data Registry* so that we are in fact using the same
> term as was used in the Verifiable Credentials Data Model 1.0 spec.
>
> The short answer is that a VDR can be any system for which: a) a developer
> wants to develop and publish a DID method, and b) verifiers will trust as a
> cryptographic root of trust for the DIDs or other verifiable data rooted
> there.
>
> It's that simple. Literally any system can serve as a VDR, including P2P
> networks that have nothing to do with DLTs or databases at all.
>
> =Drummond
>
>
>>
>> Cheers!
>>
>> Michael Shea.
>>
>