Awesome-Mirrors/decentralized-id.github.io
1
0
Fork 0
mirror of https://github.com/Decentralized-ID/decentralized-id.github.io.git synced 2025-09-21 05:04:39 -04:00
Code Issues Projects Releases Packages Wiki Activity

recategorize

Browse source
This commit is contained in:
⧉ infominer 2023-09-11 16:40:30 -04:00
parent b7d1c3b909
commit fc50f5480c
55 changed files with 135 additions and 158 deletions
Download patch file Download diff file Expand all files Collapse all files

20
_posts/web-standards/DIDs-and-VCs/2020-01-10-decentralized-identifier-did.md Normal file
View file

@ -0,0 +1,20 @@
---
title: "Decentralized Identifiers (DIDs) - W3C"
name: Decentralized Identifiers
layout: standards
headings: ["Main","Explainer","Literature","Supporting","Critique"]
description: Decentralized identifiers (DIDs) are a new type of identifier that enables verifiable, decentralized digital identity.
excerpt: >
A DID identifies any subject (e.g., a person, organization, thing, data model, abstract entity, etc.) that the controller of the DID decides that it identifies. In contrast to typical, federated identifiers, DIDs have been designed so that they may be decoupled from centralized registries, identity providers, and certificate authorities. Specifically, while other parties might be used to help enable the discovery of information related to a DID, the design enables the controller of a DID to prove control over it without requiring permission from any other party. DIDs are URIs that associate a DID subject with a DID document allowing trustable interactions associated with that subject.
categories: ["Verifiable Credentials and Decentralized Identifiers"]
tags: ["Credentials Community Group","Decentralized Identifiers","DIDWG","DIF","Evernym","FIMSA","ID2020","IETF","IIW","NIST","RWoT","SRI International","W3C"]
permalink: /web-standards/w3c/decentralized-identifier/
canonical_url: https://decentralized-id.com/web-standards/decentralized-identifier/
redirect_from:
- web-standards/w3c/wg/did/decentralized-identifier/
- web-standards/w3c/did-wg/decentralized-identifier/
- specs-standards/decentralized-identifier-did/
- web-standards/decentralized-identifier-did/
last_modified_at: 2023-08-18
toc: true
---

27
_posts/web-standards/DIDs-and-VCs/2020-01-10-verifiable-credentials.md Normal file
View file

@ -0,0 +1,27 @@
---
title: "Verifiable Credentials - W3C"
name: Verifiable Credentials
layout: standards
headings: ["About","Comparisons","Implementations","Literature","Use Case"]
description: a standard way to express credentials on the Web in a way that is cryptographically secure, privacy respecting, and machine-verifiable.
excerpt: >
Verifiable credentials (VCs) are the electronic equivalent of the physical credentials that we all possess today, such as: plastic cards, passports, driving licenses, qualifications and awards, etc. The data model for verifiable credentials is a World Wide Web Consortium Recommendation, "Verifiable Credentials Data Model 1.0 - Expressing verifiable information on the Web" published 19 November 2019.
tags: ["W3C","Verifiable Credentials","Credentials Community Group","VC-WG","JSON-LD","Claims and Credentials WG"]
categories: ["Verifiable Credentials and Decentralized Identifiers"]
permalink: web-standards/w3c/verifiable-credentials/
header:
image: /images/verifiable-credentials_head.webp
caption: "[Verifiable Credentials Data Model](https://www.w3.org/TR/vc-data-model/)"
teaser: /images/verifiable-credentials-teaser.webp
redirect_from:
- web-standards/w3c/wg/vc/
- web-standards/vc-wg/
- web-standards/w3c/wg/vc/verifiable-credentials/
- web-standards/w3c/wg/vc/verifiable-credentials/adoption/
- web-standards/w3c/vc-wg/verifiable-credentials/
- specs-standards/verifiable-credentials/
- web-standards/verifiable-credentials/
- specs-standards/verifiable credentials/
last_modified_at: 2023-08-29
---

64
_posts/web-standards/DIDs-and-VCs/2023-06-12-anoncreds.md Normal file
View file

@ -0,0 +1,64 @@
---
title: "Hyperledger Anoncreds: Attribute Based Credentials"
description: Anoncreds has been modularized from the Hyperledger Indy blockchain framework.
excerpt: >
Hyperledger AnonCreds – short for “Anonymous Credentials”- is the most commonly used Verifiable Credential (VC) format in the world. Ledger agnostic and with a formal open specification, AnonCreds is a VC format that adds important privacy-protecting ZKP (zero-knowledge proof) capabilities to the core VC assurances.
layout: single
categories: ["Verifiable Credentials and Decentralized Identifiers"]
tags: ["Hyperledger Foundation","IBM","IDEMIX","Anoncreds","Sovrin Foundation","Evernym"]
permalink: /projects/hyperledger/anoncreds/
canonical_url: 'https://decentralized-id.com/projects/hyperledger/anoncreds/'
last_modified_at: 2023-07-02
---
## Main
[Website](https://www.hyperledger.org/use/anoncreds) - [Specification](https://github.com/hyperledger/anoncreds-spec) - [Specification V2](https://github.com/hyperledger/anoncreds-spec-v2)
> Hyperledger AnonCreds – short for “Anonymous Credentials”- is the most commonly used Verifiable Credential (VC) format in the world. Ledger agnostic and with a formal open specification, AnonCreds is a VC format that adds important privacy-protecting ZKP (zero-knowledge proof) capabilities to the core VC assurances.
* [anoncreds-rs](https://github.com/hyperledger/anoncreds-rs) 2023-06-02 Hyperledger
> Rust library and reference implementation of the [Anoncreds V1.0](https://hyperledger.github.io/anoncreds-spec/) specification.
* [Hyperledger launches new digital identity project, AnonCreds](https://www.ledgerinsights.com/hyperledger-digital-identity-anoncreds-verifiable-credentials-privacy/) 2022-11-15
> The technology itself is not new, as it was originally part of Hyperledger Indy, the digital identity ledger project. However, it has now been separated from Indy so that it can be used for verifiable credentials on ledgers such as Hyperledger Fabric or Ethereum-based Hyperledger Besu, or others.
## Working Group
* [AnonCreds Specification Working Group](https://wiki.hyperledger.org/display/ANONCREDS/AnonCreds+Specification+Working+Group) 2022-11-02
> The AnonCreds Specification Working Group operates under the Community Specification License v1.0 to create the AnonCreds Specification. Current work is focused on Version 1.0 of the specification that covers the current CL-Signatures-based implementation of AnonCreds agnostic to the underlying ledger.
* [Video] [Hyperledger AnonCreds Specification Working Group](https://www.youtube.com/watch?v=sUcstipdEm8) 2023-06-19 Hyperledger Foundation
> The big thing I want to talk about was a couple of things on revocation approaches and and go over possibilities. There, there's a few things happening that I wanted to share. [...] as I mentioned in our credits announcements, the 0.1.0 rust implementation was officially released
## Development
* [Hyperledger AnonCreds Workshop: Using ZKP Verifiable Credentials Everywhere](https://www.youtube.com/watch?v=1RrJky42dvg) Hyperledger Foundation
> AnonCreds was accepted as an Incubated project at Hyperledger in late 2022. This is the first workshop developed by this community and it is intended for anyone interested in using Zero Knowledge Proofs (ZKPs) in a wide variety of contexts.
## Background
- [Anonymous Credential Part 1: Brief Overview and History](https://medium.com/finema/anonymous-credential-part-1-brief-overview-and-history-c6679034c914) 2020-10-01
> An anonymous credential (Anoncred), which is also known as an attribute-based credential (ABC), is a concept for a digital credential that provides a credential holder maximal privacy and an ability to selectively disclose their personal information.
- [Anonymous Credential Part 2: Selective Disclosure and CL Signature](https://medium.com/finema/anonymous-credential-part-2-selective-disclosure-and-cl-signature-b904a93a1565) 2021-02-04
> selective disclosure and an anonymous credential (Anoncred) relies on an efficient signature scheme that supports multiple messages with a single signature. One such signature scheme is known as CL signature that is named after its Jan Camenisch and Anna Lysyanskaya […] CL signature popularized Anoncreds, and it also served as a cryptographic building block in Identity Mixer (Idemix) and Hyperledger Indy projects.
* [Wrapping Indy Credentials (AnonCreds) in W3C VCs](https://hackmd.io/S6e2MeSWTICnV9lD9OukKg) 2021-04-12
> AnonCreds are typically bound to a holder by using a link secret and not by issuing a credential to a public DID. In order to add such a credential (or a subset of attributes) to the public profile, we suggest the following mechanism which expresses the intent: I self-attest that I have this credential with the specific attribute values, if you require a proof you can ask me using the Aries present proof protocol.
## Critique
* [Being “Real” about Hyperledger Indy & Aries / Anoncreds](https://identitywoman.net/being-real-about-hyperledger-indy-aries-anoncreds/) 2022-09-10 IdentityWoman
> This article surfaces a synthesis of challenges / concerns about Hyperledger Indy & Aries / Anoncreds, the most marketed Self-Sovereign Identity technical stack. It is aimed to provide both business and technical decision makers a better understanding of the real technical issues and related business risks of Hyperledger Indy & Aries / Anoncreds, which have not been shared and discussed openly or publicly as the author believes need to be.
### Response
* [Hyperledger launches new digital identity project, AnonCreds](https://www.ledgerinsights.com/hyperledger-digital-identity-anoncreds-verifiable-credentials-privacy/) 2022-11-15
> The technology itself is not new, as it was originally part of Hyperledger Indy, the digital identity ledger project. However, it has now been separated from Indy so that it can be used for verifiable credentials on ledgers such as Hyperledger Fabric or Ethereum-based Hyperledger Besu, or others.
* [A response to Identity Woman's recent blog post about Anoncreds](https://kyledenhartog.com/response-to-anoncreds-criticism/) 2022-09-08 Kyle Den Hartog
> It’s only when I started to take a step back that I realized that the architecture of Indy being a private, permissioned ledger leaves it heading in the same direction as many large corporations now extinct browser and intranet projects for many of the same reasons.
* [Moving Toward Identity Technology Ready for Mass Adoption](https://trinsic.id/moving-toward-identity-technology-ready-for-mass-adoption/) 2022-09-09 Trinsic
> when we realized our customers were facing critical limitations caused by the underlying tech stack, we began developing an updated version of our platform that would reduce our dependency on these technologies and enable a better platform for our customers.
## Prior Work
* [How is IDEMix Implemented?](https://forum.sovrin.org/t/how-idemex-is-implemented-in-sovrin-indy/)
> Identity Mixer is not directly (re)implemented by Sovrin, but its cryptographic foundations are very similar, and Sovrin’s implementation includes most of its extended features (predicates, multi-credential, revocation, advanced issuance…). One of the researchers who helped to create Identity Mixer is on Sovrin’s Technical Governance Board and has offered insight to keep the implementations aligned on goals and methods.
* [IDEMIX Blog](https://idemix.wordpress.com/)
* [ABC4Trust—Attribute-based Credentials for Trust](https://abc4trust.eu/)
* [Concepts and Features of Privacy-Preserving Attribute-Based Credentials](https://github.com/p2abcengine/p2abcengine/wiki/Concepts-and-features)
* [Concepts and Languages for Privacy-Preserving Attribute-Based Authentication](http://dl.ifip.org/db/conf/idman/idman2013/CamenischDLNPP13.pdf)

17
_posts/web-standards/DIDs-and-VCs/2023-08-18-DID-Methods.md Normal file
View file

@ -0,0 +1,17 @@
---
title: "DID Methods - Various"
name: DID Methods
layout: standards
headings: ["Main","DID Methods","Discussion"]
description: Different DID methods use different underlying mechanisms with different performance, security, and privacy tradeoffs.
excerpt: >
DID methods are the magic ingredient that gives DIDs their flexibility. Before creating any specific DID, you first choose a DID method, which determines how you perform the create, read, update, and deactivate operations on a DID of that method.
Once created, each DID includes the name of its method in the identifier itself, so that when you use the DID, others know how to retrieve the associated DID Document that contains the cryptographic material for secure interactions.
categories: ["Verifiable Credentials and Decentralized Identifiers"]
tags: ["51nodes","ABT Network","Aergo","Alastria","ArcBlock","Ardor","Baidu","BCGov","Besu","BIF","BiiLabs","Binance","Bitcoin","BlockchainCommons","Blockcore","Blocko","Blockstack","BOTLabs","bryk","BSC","Teleinfo CAICT","Celo","Ceramic Network","Chainyard","Cloudchain","Commercio","Consensys","Consent","Corda","Cosmos","Credentials Community Group","cryptonics","DID:AERGO","DID:ALA","DID:AVVCYBER","DID:BBA","DID:BID","DID:BNB","DID:BRYK","DID:BTCR","DID:CCP","DID:CELO","DID:COM","DID:CORDA","DID:DID","DID:DOCK","DID:DOGE","DID:ECHO","DID:ELASTOS","DID:ELEM","DID:EMTRUST","DID:EOS","DID:ERC725","DID:ETHO","DID:ETHR","DID:EVAN","DID:FACTOM","DID:GATC","DID:GIT","DID:GITHUB","DID:GRG","DID:HEDERA","DID:HOLO","DID:ICON","DID:INDY","DID:IO","DID:ION","DID:IPID","DID:IS","DID:IWT","DID:JLINC","DID:JNCTN","DID:JOLO","DID:JWK","DID:KEY","DID:KILT","DID:KLAY","DID:LIFE","DID:META","DID:MOAC","DID:MORPHEUS","DID:NEAR","DID:NFT","DID:OBJECT","DID:OCKAM","DID:OMN","DID:ONION","DID:ONT","DID:OP","DID:ORB","DID:PANACEA","DID:PEER","DID:PISTIS","DID:PKH","DID:PTN","DID:SAN","DID:SCHEMA","DID:SELFKEY","DID:SIGNOR","DID:SIRIUS","DID:SOV","DID:STACK","DID:TAG","DID:TANGLE","DID:TRUSTBLOC","DID:TRX","DID:TTM","DID:TWIT","DID:TYRON","DID:TYS","DID:TZ","DID:UNDID","DID:UNISOT","DID:UNS","DID:V1","DID:VAA","DID:VAULTIE","DID:VID","DID:VVO","DID:WEB","DID:WLK","DID:WORK","Decentralized Identifiers","Digital Bazaar","Dock","Echo","Elastos","Element","Email","EOS","ERC725","Ethereum","Evan Network","Evernym","Fabric","Factom","Gatica","Github","GRGBanking","GrgChain","Halialabs","Hashgraph","Holochain","Hydra","Hyland Credentials","hyperledger foundation","IBM","ICONLOOP","IIW","Indy","InfoWallet","ION","IOP","IOTA","IoTeX","IPFS","JLinc","Jnctn","Jolocom","JWK","KILT","Klaytn","lifeID","MediBloc","Metadium","Microsoft","MOAC","NEAR","Ocean Protocol","Ockam","OmniOne","Ontology","Panacea","ProximaX","Quorum","Raonsecure","RChain","RWoT","SecureKey","SelfKey Identity","SelfKey","Sovrin Foundation","Sovrin","SpaceElephant","Sphereon","SpruceID","Swisscom","TIFAC-CORE","TMChain","Token.TM","TOR","TranSendX","Transmute","TRON","Twitter","UNISOT","UNS","uPort","Vaultie","VeramoLabs","Veres One","Vivvo","VP","W3C","Weelink","Workday","YLZ Inc","Zilliqa"]
permalink: /web-standards/w3c/decentralized-identifier/did-methods/
canonical_url: https://decentralized-id.com/web-standards/w3c/decentralized-identifier/did-methods/
last_modified_at: 2023-08-18
toc: true
---

19
_posts/web-standards/DIDs-and-VCs/2023-08-29-VCs-Standards-and-Development.md Normal file
View file

@ -0,0 +1,19 @@
---
title: "Verifiable Credentials - Working Groups, Standards and Development"
name: VCs Development
layout: standards
headings: ["Verifiable Credentials Working Group","Credentials Community Group","Claims and Credentials Working Group","Varieties","Technology","User Experience"]
description: a standard way to express credentials on the Web in a way that is cryptographically secure, privacy respecting, and machine-verifiable.
excerpt: >
Verifiable credentials (VCs) are the electronic equivalent of the physical credentials that we all possess today, such as: plastic cards, passports, driving licenses, qualifications and awards, etc. The data model for verifiable credentials is a World Wide Web Consortium Recommendation, "Verifiable Credentials Data Model 1.0 - Expressing verifiable information on the Web" published 19 November 2019.
tags: ["W3C","Verifiable Credentials","Credentials Community Group","VC-WG","JSON-LD","OAuth","FIDO","Claims and Credentials WG"]
categories: ["Verifiable Credentials and Decentralized Identifiers"]
permalink: web-standards/w3c/verifiable-credentials/standards-and-development/
header:
image:
caption:
teaser:
canonical_url: "https://decentralized-id.com/web-standards/w3c/verifiable-credentials/standards-and-development/"
last_modified_at: 2023-08-29
---