Awesome-Mirrors/decentralized-id.github.io
1
0
Fork 0
mirror of https://github.com/Decentralized-ID/decentralized-id.github.io.git synced 2024-12-25 23:29:26 -05:00
Code Issues Packages Projects Releases Wiki Activity

new links from sort

Browse Source
This commit is contained in:
⧉ infominer 2023-06-05 07:25:11 +05:30
parent 86e5a720db
commit b463f9a790
2 changed files with 9 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
_data/content.csv
View File

File diff suppressed because one or more lines are too long

3
_data/standards.csv
View File

@ -154,7 +154,7 @@ Decentralized Identifiers,WebofTrustInfo,,,,Decentralized Identifiers,,,,rwot07-
Decentralized Identifiers,"SRI International, NIST, FIMSA",,,,Decentralized Identifiers,,,,,Cryptography Review of W3C VC Data Model and DID Standards and Implementation Recommendations,"Cryptography used by U.S. government entities in operational systems must conform to relevant federal government standards and requirements, including the Federal Information Security Management Act (FISMA) and National Institute of Technology (NIST) standards for use of cryptography. As part of its in-depth technical due-diligence to enable operational capabilities for DHS/CBP, DHS/PRIV and DHS/USCIS, the U.S. Department of Homeland Security’s Silicon Valley Innovation Program (SVIP) sponsored independent nonprofit research center SRI International to conduct a cryptographic review of the W3C Verifiable Credentials Data Model and W3C Decentralized Identifiers standards. The review provided constructive feedback and recommendations for technology developers and W3C standards developers to increase their level of compliance with federal government standards.",,https://web.archive.org/web/20230319062836/https://www.csl.sri.com/papers/vcdm-did-crypto-recs/,,Paper,,,Literature,,,,,,,,2023-03-19,,,,,,,,,,,,, Decentralized Identifiers,"SRI International, NIST, FIMSA",,,,Decentralized Identifiers,,,,,Cryptography Review of W3C VC Data Model and DID Standards and Implementation Recommendations,"Cryptography used by U.S. government entities in operational systems must conform to relevant federal government standards and requirements, including the Federal Information Security Management Act (FISMA) and National Institute of Technology (NIST) standards for use of cryptography. As part of its in-depth technical due-diligence to enable operational capabilities for DHS/CBP, DHS/PRIV and DHS/USCIS, the U.S. Department of Homeland Security’s Silicon Valley Innovation Program (SVIP) sponsored independent nonprofit research center SRI International to conduct a cryptographic review of the W3C Verifiable Credentials Data Model and W3C Decentralized Identifiers standards. The review provided constructive feedback and recommendations for technology developers and W3C standards developers to increase their level of compliance with federal government standards.",,https://web.archive.org/web/20230319062836/https://www.csl.sri.com/papers/vcdm-did-crypto-recs/,,Paper,,,Literature,,,,,,,,2023-03-19,,,,,,,,,,,,,
Decentralized Identifiers,Legendary Requirements,,,,,,,,,did:directory,"The DID Directory is a public directory of DID methods, provided by Legendary Requirements, long time advocates for decentralized identity and its emerging technologies, such as the Decentralized Identifiers from the World Wide Web Consortium.<br><br>Decentralized Identifiers (DIDs) enable identity-based services without dependence on a trusted third party. Instead of requiring centralized identity verification services, like Facebook, Google or the Department of Motor Vehicles, DIDs can be created by anyone, anywhere, and be used for any purpose.",,https://diddirectory.com/,,Directory,,,About DID Methods,,,,,,,,,,,,,,,,,,,,, Decentralized Identifiers,Legendary Requirements,,,,,,,,,did:directory,"The DID Directory is a public directory of DID methods, provided by Legendary Requirements, long time advocates for decentralized identity and its emerging technologies, such as the Decentralized Identifiers from the World Wide Web Consortium.<br><br>Decentralized Identifiers (DIDs) enable identity-based services without dependence on a trusted third party. Instead of requiring centralized identity verification services, like Facebook, Google or the Department of Motor Vehicles, DIDs can be created by anyone, anywhere, and be used for any purpose.",,https://diddirectory.com/,,Directory,,,About DID Methods,,,,,,,,,,,,,,,,,,,,,
Decentralized Identifiers,DIDWG,,,,Decentralized Identifiers,,,,,DID Specification Registries,This table summarizes the DID method specifications currently in development. The links will be updated as subsequent Implementer’s Drafts are produced.,,https://w3c-ccg.github.io/did-method-registry/#the-registry,,registry,,,About DID Methods,,,,,,,DID Working Group,2023-05-14,,,,,,,,,,,,, Decentralized Identifiers,DIDWG,,,,Decentralized Identifiers,,,,,DID Specification Registries,This table summarizes the DID method specifications currently in development. The links will be updated as subsequent Implementer’s Drafts are produced.,,https://w3c-ccg.github.io/did-method-registry/#the-registry,,registry,,,About DID Methods,,,,,,,DID Working Group,2023-05-14,,,,,,,,,,,,,
Decentralized Identifiers,Transmute,,,Margo Johnson,Decentralized Identifiers,,,,,DID:Customer,"While we are committed to providing optionality to our customers, it’s equally important to communicate the selection criteria behind these options so that customers can consider the tradeoffs of underlying DID-methods alongside the problem set they’re solving for.","Transmute builds solutions that solve real business problems. For this reason, we support a number of different decentralized identifier (DID) methods. While we are committed to providing optionality…",https://medium.com/transmute-techtalk/did-customer-4ca8b7957112,https://miro.medium.com/v2/resize:fit:1200/1*MVDiykjv5WUBP4PUWweB5w.jpeg,Post,,,About DID Methods,,,,,,,,2020-10-30,,,,,,,,,,,,, Decentralized Identifiers,Transmute,,,Margo Johnson,Decentralized Identifiers,,,,,DID:Customer,"While we are committed to providing optionality to our customers, it’s equally important to communicate the selection criteria behind these options so that customers can consider the tradeoffs of underlying DID-methods alongside the problem set they’re solving for.","Transmute builds solutions that solve real business problems. For this reason, we support a number of different decentralized identifier (DID) methods. While we are committed to providing optionality…",https://medium.com/transmute-techtalk/did-customer-4ca8b7957112,,Post,,,About DID Methods,,,,,,,,2020-10-30,,,,,,,,,,,,,
Decentralized Identifiers,WebOfTrustInfo,,,"Joe Andrieu, Shannon Appelcline, Amy Guy, Joachim Lohkamp, Drummond Reed, Markus Sabadello, Oliver Terbu, Kai Wagner",Decentralized Identifiers,,,,rwot9-prague,A Rubric for Decentralization of DID Methods,"The communities behind Decentralized Identifiers (DIDs) bring together a diverse group of contributors, who have decidedly different notions of exactly what “decentralization” means. For some, the notion of a DID anchored to DNS is anathema, for others, DIDs that cannot be publicly verified are problematic. This debate about decentralization is a continuation of a similar, ongoing argument in cryptocurrency circles: the question of whether or not bitcoin or ethereum is more decentralized is a nearly endless source of argument. Rather than attempting to resolve this potentially unresolvable question, we propose a rubric — which is a scoring guide used to evaluate performance, a product, or a project — that teaches how to evaluate a given DID method according to one’s own requirements. Our goal is to develop a guide that minimizes judgment and bias. Rather than advocating particular solutions, the rubric presents a series of criteria which an evaluator can apply to any DID method based on their particular use cases. We also avoid reducing the evaluation to a single number because the criteria tend to be multidimensional and many of the options are not necessarily good or bad: it is the obligation of the evaluator to understand how each response in each criteria might illuminate favorable or unfavorable consequences for their needs. Finally, this rubric allows evaluating aspects of decentralization of a DID method, but it is not exhaustive, and does not cover other issues that may affect selection or adoption of a particular method, such as privacy or efficiency.","RWOT9 in Prague, The Czech Republic (September 2019) - rwot9-prague/decentralized-did-rubric.md at master · WebOfTrustInfo/rwot9-prague",https://github.com/WebOfTrustInfo/rwot9-prague/blob/master/draft-documents/decentralized-did-rubric.md,,Paper,,,About DID Methods,,,,,,,,2019-09-06,,,,,,,,,,,,, Decentralized Identifiers,WebOfTrustInfo,,,"Joe Andrieu, Shannon Appelcline, Amy Guy, Joachim Lohkamp, Drummond Reed, Markus Sabadello, Oliver Terbu, Kai Wagner",Decentralized Identifiers,,,,rwot9-prague,A Rubric for Decentralization of DID Methods,"The communities behind Decentralized Identifiers (DIDs) bring together a diverse group of contributors, who have decidedly different notions of exactly what “decentralization” means. For some, the notion of a DID anchored to DNS is anathema, for others, DIDs that cannot be publicly verified are problematic. This debate about decentralization is a continuation of a similar, ongoing argument in cryptocurrency circles: the question of whether or not bitcoin or ethereum is more decentralized is a nearly endless source of argument. Rather than attempting to resolve this potentially unresolvable question, we propose a rubric — which is a scoring guide used to evaluate performance, a product, or a project — that teaches how to evaluate a given DID method according to one’s own requirements. Our goal is to develop a guide that minimizes judgment and bias. Rather than advocating particular solutions, the rubric presents a series of criteria which an evaluator can apply to any DID method based on their particular use cases. We also avoid reducing the evaluation to a single number because the criteria tend to be multidimensional and many of the options are not necessarily good or bad: it is the obligation of the evaluator to understand how each response in each criteria might illuminate favorable or unfavorable consequences for their needs. Finally, this rubric allows evaluating aspects of decentralization of a DID method, but it is not exhaustive, and does not cover other issues that may affect selection or adoption of a particular method, such as privacy or efficiency.","RWOT9 in Prague, The Czech Republic (September 2019) - rwot9-prague/decentralized-did-rubric.md at master · WebOfTrustInfo/rwot9-prague",https://github.com/WebOfTrustInfo/rwot9-prague/blob/master/draft-documents/decentralized-did-rubric.md,,Paper,,,About DID Methods,,,,,,,,2019-09-06,,,,,,,,,,,,,
Decentralized Identifiers,IDCommons,,"https://iiw.idcommons.net/13D/_We_evaluated_7_DID_methods_with_the_W3C_DID_Rubric!_did:btcr,_did:sov,_did:ion,_did:web,_did:key,_did:peer,_did:ethr",,Decentralized Identifiers,,,,IIW,DID Method Rubric v1.0,This rubric presents a set of criteria which an Evaluator can apply to any DID Method based on the use cases most relevant to them. We avoid reducing the Evaluation to a single number because the criteria tend to be multidimensional and many of the possible responses are not necessarily good or bad. It is up to the Evaluator to understand how each response in each criteria might illuminate favorable or unfavorable consequences for their needs.,,https://w3c.github.io/did-rubric/,,Guidance,Draft,,About DID Methods,,,,,,,,2022-01-11,,,,,,,,,,,,, Decentralized Identifiers,IDCommons,,"https://iiw.idcommons.net/13D/_We_evaluated_7_DID_methods_with_the_W3C_DID_Rubric!_did:btcr,_did:sov,_did:ion,_did:web,_did:key,_did:peer,_did:ethr",,Decentralized Identifiers,,,,IIW,DID Method Rubric v1.0,This rubric presents a set of criteria which an Evaluator can apply to any DID Method based on the use cases most relevant to them. We avoid reducing the Evaluation to a single number because the criteria tend to be multidimensional and many of the possible responses are not necessarily good or bad. It is up to the Evaluator to understand how each response in each criteria might illuminate favorable or unfavorable consequences for their needs.,,https://w3c.github.io/did-rubric/,,Guidance,Draft,,About DID Methods,,,,,,,,2022-01-11,,,,,,,,,,,,,
Decentralized Identifiers,IDCommons,,"https://iiw.idcommons.net/13D/_We_evaluated_7_DID_methods_with_the_W3C_DID_Rubric!_did:btcr,_did:sov,_did:ion,_did:web,_did:key,_did:peer,_did:ethr","Walid Fdhila, Markus Sabadello","did:btcr, did:sov, did:ion, did:web, did:key, did:peer, did:ethr, Decentralized Identifiers",,,,IIW,DID Methods Evaluation Report,This report evaluates a selection of DiD methods using the guidelines specified in the W3C DiD method Rubric V1.0 (draft 06 January 2021). The evaluation reflects the authors’ opinion based on documents and source code that are publicly available. The report mainly includes a comprehensive evaluation.,"Web word processing, spreadsheets and presentations",https://docs.google.com/document/d/1jP-76ul0FZ3H8dChqT2hMtlzvL6B3famQbseZQ0AGS8//,,Report,,,About DID Methods,,,,,,,,2021-04-04,,,,,,,,,,,,, Decentralized Identifiers,IDCommons,,"https://iiw.idcommons.net/13D/_We_evaluated_7_DID_methods_with_the_W3C_DID_Rubric!_did:btcr,_did:sov,_did:ion,_did:web,_did:key,_did:peer,_did:ethr","Walid Fdhila, Markus Sabadello","did:btcr, did:sov, did:ion, did:web, did:key, did:peer, did:ethr, Decentralized Identifiers",,,,IIW,DID Methods Evaluation Report,This report evaluates a selection of DiD methods using the guidelines specified in the W3C DiD method Rubric V1.0 (draft 06 January 2021). The evaluation reflects the authors’ opinion based on documents and source code that are publicly available. The report mainly includes a comprehensive evaluation.,"Web word processing, spreadsheets and presentations",https://docs.google.com/document/d/1jP-76ul0FZ3H8dChqT2hMtlzvL6B3famQbseZQ0AGS8//,,Report,,,About DID Methods,,,,,,,,2021-04-04,,,,,,,,,,,,,
@ -654,6 +654,7 @@ KERI,DIF,,,,,,,,,Q&A about KERI’s Security model and Guarantees - Part II Secu
KERI,,,,Samuel Smith,,,,,,W3C DID Security Concerns,**Certificate Transparency Solution**<br>- Public end-verifiable append-only event log with consistency and inclusion proofs <br>- End-verifiable duplicity detection = ambient verifiability of duplicity <br>- Event log is third party infrastructure but it is not trusted because logs are verifiable. <br>- Sparse Merkle trees for revocation of certificates<br>- (related EFF SSL Observatory),,https://github.com/SmithSamuelM/Papers/blob/master/presentations/W3C_DID_Security_Concerns.pdf,,,,,Development,,,,,,,,2020-01-14,,,,,,,,,,,,, KERI,,,,Samuel Smith,,,,,,W3C DID Security Concerns,**Certificate Transparency Solution**<br>- Public end-verifiable append-only event log with consistency and inclusion proofs <br>- End-verifiable duplicity detection = ambient verifiability of duplicity <br>- Event log is third party infrastructure but it is not trusted because logs are verifiable. <br>- Sparse Merkle trees for revocation of certificates<br>- (related EFF SSL Observatory),,https://github.com/SmithSamuelM/Papers/blob/master/presentations/W3C_DID_Security_Concerns.pdf,,,,,Development,,,,,,,,2020-01-14,,,,,,,,,,,,,
KERI,DIF,,https://hackmd.io/orhyiJkLT721v4PCPkvQiA?both,,,,,,,Implementation Notes for KERI,"The interpretation of the data associated with the digest or hash tree root in the seal is independent of KERI. This allows KERI to be agnostic about anchored data semantics. Another way of saying this is that seals are data agnostic; they don’t care about the semantics of its associated data. This better preserves privacy because the seal itself does not leak any information about the purpose or specific content of the associated data. Furthermore, because digests are a type of content address, they are self-discoverable. This means there is no need to provide any sort of context or content specific tag or label for the digests. Applications that use KERI may provide discovery of a digest via a hash table (mapping) whose indexes (hash keys) are the digests and the values in the table are the location of the digest in a specific event. To restate, the semantics of the digested data are not needed for discovery of the digest within a key event sequence.",,https://github.com/decentralized-identity/keri/blob/master/implementation.md,,,,,Development,,,,,,,,2020-05-16,,,,,,,,,,,,, KERI,DIF,,https://hackmd.io/orhyiJkLT721v4PCPkvQiA?both,,,,,,,Implementation Notes for KERI,"The interpretation of the data associated with the digest or hash tree root in the seal is independent of KERI. This allows KERI to be agnostic about anchored data semantics. Another way of saying this is that seals are data agnostic; they don’t care about the semantics of its associated data. This better preserves privacy because the seal itself does not leak any information about the purpose or specific content of the associated data. Furthermore, because digests are a type of content address, they are self-discoverable. This means there is no need to provide any sort of context or content specific tag or label for the digests. Applications that use KERI may provide discovery of a digest via a hash table (mapping) whose indexes (hash keys) are the digests and the values in the table are the location of the digest in a specific event. To restate, the semantics of the digested data are not needed for discovery of the digest within a key event sequence.",,https://github.com/decentralized-identity/keri/blob/master/implementation.md,,,,,Development,,,,,,,,2020-05-16,,,,,,,,,,,,,
KERI,IDCommons,,,"Samuel Smith, Dave Huseby",,,,,IIW,KERI and ADS Key State Provenance Logs Kumbaya (KEL and ADPL),"This was a meeting of the minds between myself and Sam Smith and Adrian Gropper that was hugely successful. We all decided to use the term ""endorser"" for what we all called ""registrar""/""witness""/""notary"". We also realized that the KERI proposal for encoding is good enough for authentic data provenance logs and we will be using the KERI encoding. Sam has modified the spec for KERI key event logs to include scripting capabilities needed in the authentic data economy for doing things like cross-chain atomic swaps for selling non-fungible authentic data (NFADs).<br><br>The result is that there is grand convergence on the encoding and file format for key event provenance logs that will be supported by both KERI networks and the broader authentic data economy.",,https://iiw.idcommons.net/24H/_KERI_and_ADS_Key_State_Provenance_Logs_Kumbaya_(KEL_and_ADPL),,Session Notes,,,Development,,,,,,,,2021-05-06,,,,,,,,,,,,, KERI,IDCommons,,,"Samuel Smith, Dave Huseby",,,,,IIW,KERI and ADS Key State Provenance Logs Kumbaya (KEL and ADPL),"This was a meeting of the minds between myself and Sam Smith and Adrian Gropper that was hugely successful. We all decided to use the term ""endorser"" for what we all called ""registrar""/""witness""/""notary"". We also realized that the KERI proposal for encoding is good enough for authentic data provenance logs and we will be using the KERI encoding. Sam has modified the spec for KERI key event logs to include scripting capabilities needed in the authentic data economy for doing things like cross-chain atomic swaps for selling non-fungible authentic data (NFADs).<br><br>The result is that there is grand convergence on the encoding and file format for key event provenance logs that will be supported by both KERI networks and the broader authentic data economy.",,https://iiw.idcommons.net/24H/_KERI_and_ADS_Key_State_Provenance_Logs_Kumbaya_(KEL_and_ADPL),,Session Notes,,,Development,,,,,,,,2021-05-06,,,,,,,,,,,,,
KERI,Jolocom,,,,,,,,,Jolocom’s latest contributions to DIF,"Jolocom added support for an [off-chain element based on KERI](https://github.com/decentralized-identity/keri/blob/master/kids/KERI_WP.pdf). This is in addition to the Jolocom DID method (did:jolo and did:keri), which supports the Jolocom-Lib, our own SDK and the Jolocom SmartWallet.",,https://jolocom.io/blog/jolocoms-contributions-to-dif/,,,,,Development,,,,,,,,2021-01-19,,,,,,,,,,,,,
KERI,SSI-Meetup,,https://www.youtube.com/watch?v=izNZ20XSXR0,,,,,,,Key Event Receipt Infrastructure (KERI): A secure identifier overlay for the internet – Sam Smith – Webinar 58,,,https://ssimeetup.org/key-event-receipt-infrastructure-keri-secure-identifier-overlay-internet-sam-smith-webinar-58/,,,,,Presentations,,,,,,,,2020-05-19,,,,,,,,,,,,, KERI,SSI-Meetup,,https://www.youtube.com/watch?v=izNZ20XSXR0,,,,,,,Key Event Receipt Infrastructure (KERI): A secure identifier overlay for the internet – Sam Smith – Webinar 58,,,https://ssimeetup.org/key-event-receipt-infrastructure-keri-secure-identifier-overlay-internet-sam-smith-webinar-58/,,,,,Presentations,,,,,,,,2020-05-19,,,,,,,,,,,,,
KERI,,,,Samuel Smith,,,,,,KERI Overview,"**Separation of Control** Shared (permissioned) ledger = shared control over shared data.<br>* Shared data = good, shared control = bad.<br>* Shared control between controller and validator may be problematic for governance, scalability, and performance.KERI = separated control over shared data.<br>* Separated control between controller and validator may provide better decentralization, more flexibility, better scalability, lower cost, higher performance, and more privacy at comparable security.",,https://raw.githubusercontent.com/SmithSamuelM/Papers/master/presentations/KERI2_Overview.web.pdf,,,2.54,,Presentations,,,,,,,,2020-10-22,,,,,,,,,,,,, KERI,,,,Samuel Smith,,,,,,KERI Overview,"**Separation of Control** Shared (permissioned) ledger = shared control over shared data.<br>* Shared data = good, shared control = bad.<br>* Shared control between controller and validator may be problematic for governance, scalability, and performance.KERI = separated control over shared data.<br>* Separated control between controller and validator may provide better decentralization, more flexibility, better scalability, lower cost, higher performance, and more privacy at comparable security.",,https://raw.githubusercontent.com/SmithSamuelM/Papers/master/presentations/KERI2_Overview.web.pdf,,,2.54,,Presentations,,,,,,,,2020-10-22,,,,,,,,,,,,,
KERI,,,,Samuel Smith,,,,,,The Duplicity Game: or why you can trust KERI,"**Inconsistency vs. Duplicity**<br>- inconsistency: lacking agreement, as two or more things in relation to each other<br>- duplicity: acting in two different ways to different people concerning the same matter<br>**Internal vs. External Inconsistency** <br>- Internally inconsistent log = not verifiable.<br>- Log verification from self-certifying root-of-trust protects against internal inconsistency.<br>Externally inconsistent log with a purported copy of log but both verifiable = duplicitous.<br>Duplicity detection protects against external inconsistency.",,https://raw.githubusercontent.com/SmithSamuelM/Papers/master/presentations/DuplicityGame_IIW_2020_A.pdf,,,,,Presentations,,,,,,,,2020-05-09,,,,,,,,,,,,, KERI,,,,Samuel Smith,,,,,,The Duplicity Game: or why you can trust KERI,"**Inconsistency vs. Duplicity**<br>- inconsistency: lacking agreement, as two or more things in relation to each other<br>- duplicity: acting in two different ways to different people concerning the same matter<br>**Internal vs. External Inconsistency** <br>- Internally inconsistent log = not verifiable.<br>- Log verification from self-certifying root-of-trust protects against internal inconsistency.<br>Externally inconsistent log with a purported copy of log but both verifiable = duplicitous.<br>Duplicity detection protects against external inconsistency.",,https://raw.githubusercontent.com/SmithSamuelM/Papers/master/presentations/DuplicityGame_IIW_2020_A.pdf,,,,,Presentations,,,,,,,,2020-05-09,,,,,,,,,,,,,

1 main parent name supporting authors related location serving policy event title text description link image type status platform section sector industry market focus projects tech working group date github twitter youtube list feed discord crunchbase linkedin docs devtools app telegram forum
154 Decentralized Identifiers SRI International, NIST, FIMSA Decentralized Identifiers Cryptography Review of W3C VC Data Model and DID Standards and Implementation Recommendations Cryptography used by U.S. government entities in operational systems must conform to relevant federal government standards and requirements, including the Federal Information Security Management Act (FISMA) and National Institute of Technology (NIST) standards for use of cryptography. As part of its in-depth technical due-diligence to enable operational capabilities for DHS/CBP, DHS/PRIV and DHS/USCIS, the U.S. Department of Homeland Security’s Silicon Valley Innovation Program (SVIP) sponsored independent nonprofit research center SRI International to conduct a cryptographic review of the W3C Verifiable Credentials Data Model and W3C Decentralized Identifiers standards. The review provided constructive feedback and recommendations for technology developers and W3C standards developers to increase their level of compliance with federal government standards. https://web.archive.org/web/20230319062836/https://www.csl.sri.com/papers/vcdm-did-crypto-recs/ Paper Literature 2023-03-19
155 Decentralized Identifiers Legendary Requirements did:directory The DID Directory is a public directory of DID methods, provided by Legendary Requirements, long time advocates for decentralized identity and its emerging technologies, such as the Decentralized Identifiers from the World Wide Web Consortium.<br><br>Decentralized Identifiers (DIDs) enable identity-based services without dependence on a trusted third party. Instead of requiring centralized identity verification services, like Facebook, Google or the Department of Motor Vehicles, DIDs can be created by anyone, anywhere, and be used for any purpose. https://diddirectory.com/ Directory About DID Methods
156 Decentralized Identifiers DIDWG Decentralized Identifiers DID Specification Registries This table summarizes the DID method specifications currently in development. The links will be updated as subsequent Implementer’s Drafts are produced. https://w3c-ccg.github.io/did-method-registry/#the-registry registry About DID Methods DID Working Group 2023-05-14
157 Decentralized Identifiers Transmute Margo Johnson Decentralized Identifiers DID:Customer While we are committed to providing optionality to our customers, it’s equally important to communicate the selection criteria behind these options so that customers can consider the tradeoffs of underlying DID-methods alongside the problem set they’re solving for. Transmute builds solutions that solve real business problems. For this reason, we support a number of different decentralized identifier (DID) methods. While we are committed to providing optionality… https://medium.com/transmute-techtalk/did-customer-4ca8b7957112 https://miro.medium.com/v2/resize:fit:1200/1*MVDiykjv5WUBP4PUWweB5w.jpeg Post About DID Methods 2020-10-30
158 Decentralized Identifiers WebOfTrustInfo Joe Andrieu, Shannon Appelcline, Amy Guy, Joachim Lohkamp, Drummond Reed, Markus Sabadello, Oliver Terbu, Kai Wagner Decentralized Identifiers rwot9-prague A Rubric for Decentralization of DID Methods The communities behind Decentralized Identifiers (DIDs) bring together a diverse group of contributors, who have decidedly different notions of exactly what “decentralization” means. For some, the notion of a DID anchored to DNS is anathema, for others, DIDs that cannot be publicly verified are problematic. This debate about decentralization is a continuation of a similar, ongoing argument in cryptocurrency circles: the question of whether or not bitcoin or ethereum is more decentralized is a nearly endless source of argument. Rather than attempting to resolve this potentially unresolvable question, we propose a rubric — which is a scoring guide used to evaluate performance, a product, or a project — that teaches how to evaluate a given DID method according to one’s own requirements. Our goal is to develop a guide that minimizes judgment and bias. Rather than advocating particular solutions, the rubric presents a series of criteria which an evaluator can apply to any DID method based on their particular use cases. We also avoid reducing the evaluation to a single number because the criteria tend to be multidimensional and many of the options are not necessarily good or bad: it is the obligation of the evaluator to understand how each response in each criteria might illuminate favorable or unfavorable consequences for their needs. Finally, this rubric allows evaluating aspects of decentralization of a DID method, but it is not exhaustive, and does not cover other issues that may affect selection or adoption of a particular method, such as privacy or efficiency. RWOT9 in Prague, The Czech Republic (September 2019) - rwot9-prague/decentralized-did-rubric.md at master · WebOfTrustInfo/rwot9-prague https://github.com/WebOfTrustInfo/rwot9-prague/blob/master/draft-documents/decentralized-did-rubric.md Paper About DID Methods 2019-09-06
159 Decentralized Identifiers IDCommons https://iiw.idcommons.net/13D/_We_evaluated_7_DID_methods_with_the_W3C_DID_Rubric!_did:btcr,_did:sov,_did:ion,_did:web,_did:key,_did:peer,_did:ethr Decentralized Identifiers IIW DID Method Rubric v1.0 This rubric presents a set of criteria which an Evaluator can apply to any DID Method based on the use cases most relevant to them. We avoid reducing the Evaluation to a single number because the criteria tend to be multidimensional and many of the possible responses are not necessarily good or bad. It is up to the Evaluator to understand how each response in each criteria might illuminate favorable or unfavorable consequences for their needs. https://w3c.github.io/did-rubric/ Guidance Draft About DID Methods 2022-01-11
160 Decentralized Identifiers IDCommons https://iiw.idcommons.net/13D/_We_evaluated_7_DID_methods_with_the_W3C_DID_Rubric!_did:btcr,_did:sov,_did:ion,_did:web,_did:key,_did:peer,_did:ethr Walid Fdhila, Markus Sabadello did:btcr, did:sov, did:ion, did:web, did:key, did:peer, did:ethr, Decentralized Identifiers IIW DID Methods Evaluation Report This report evaluates a selection of DiD methods using the guidelines specified in the W3C DiD method Rubric V1.0 (draft 06 January 2021). The evaluation reflects the authors’ opinion based on documents and source code that are publicly available. The report mainly includes a comprehensive evaluation. Web word processing, spreadsheets and presentations https://docs.google.com/document/d/1jP-76ul0FZ3H8dChqT2hMtlzvL6B3famQbseZQ0AGS8// Report About DID Methods 2021-04-04
654 KERI Samuel Smith W3C DID Security Concerns **Certificate Transparency Solution**<br>- Public end-verifiable append-only event log with consistency and inclusion proofs <br>- End-verifiable duplicity detection = ambient verifiability of duplicity <br>- Event log is third party infrastructure but it is not trusted because logs are verifiable. <br>- Sparse Merkle trees for revocation of certificates<br>- (related EFF SSL Observatory) https://github.com/SmithSamuelM/Papers/blob/master/presentations/W3C_DID_Security_Concerns.pdf Development 2020-01-14
655 KERI DIF https://hackmd.io/orhyiJkLT721v4PCPkvQiA?both Implementation Notes for KERI The interpretation of the data associated with the digest or hash tree root in the seal is independent of KERI. This allows KERI to be agnostic about anchored data semantics. Another way of saying this is that seals are data agnostic; they don’t care about the semantics of its associated data. This better preserves privacy because the seal itself does not leak any information about the purpose or specific content of the associated data. Furthermore, because digests are a type of content address, they are self-discoverable. This means there is no need to provide any sort of context or content specific tag or label for the digests. Applications that use KERI may provide discovery of a digest via a hash table (mapping) whose indexes (hash keys) are the digests and the values in the table are the location of the digest in a specific event. To restate, the semantics of the digested data are not needed for discovery of the digest within a key event sequence. https://github.com/decentralized-identity/keri/blob/master/implementation.md Development 2020-05-16
656 KERI IDCommons Samuel Smith, Dave Huseby IIW KERI and ADS Key State Provenance Logs Kumbaya (KEL and ADPL) This was a meeting of the minds between myself and Sam Smith and Adrian Gropper that was hugely successful. We all decided to use the term "endorser" for what we all called "registrar"/"witness"/"notary". We also realized that the KERI proposal for encoding is good enough for authentic data provenance logs and we will be using the KERI encoding. Sam has modified the spec for KERI key event logs to include scripting capabilities needed in the authentic data economy for doing things like cross-chain atomic swaps for selling non-fungible authentic data (NFADs).<br><br>The result is that there is grand convergence on the encoding and file format for key event provenance logs that will be supported by both KERI networks and the broader authentic data economy. https://iiw.idcommons.net/24H/_KERI_and_ADS_Key_State_Provenance_Logs_Kumbaya_(KEL_and_ADPL) Session Notes Development 2021-05-06
657 KERI Jolocom Jolocom’s latest contributions to DIF Jolocom added support for an [off-chain element based on KERI](https://github.com/decentralized-identity/keri/blob/master/kids/KERI_WP.pdf). This is in addition to the Jolocom DID method (did:jolo and did:keri), which supports the Jolocom-Lib, our own SDK and the Jolocom SmartWallet. https://jolocom.io/blog/jolocoms-contributions-to-dif/ Development 2021-01-19
658 KERI SSI-Meetup https://www.youtube.com/watch?v=izNZ20XSXR0 Key Event Receipt Infrastructure (KERI): A secure identifier overlay for the internet – Sam Smith – Webinar 58 https://ssimeetup.org/key-event-receipt-infrastructure-keri-secure-identifier-overlay-internet-sam-smith-webinar-58/ Presentations 2020-05-19
659 KERI Samuel Smith KERI Overview **Separation of Control** Shared (permissioned) ledger = shared control over shared data.<br>* Shared data = good, shared control = bad.<br>* Shared control between controller and validator may be problematic for governance, scalability, and performance.KERI = separated control over shared data.<br>* Separated control between controller and validator may provide better decentralization, more flexibility, better scalability, lower cost, higher performance, and more privacy at comparable security. https://raw.githubusercontent.com/SmithSamuelM/Papers/master/presentations/KERI2_Overview.web.pdf 2.54 Presentations 2020-10-22
660 KERI Samuel Smith The Duplicity Game: or why you can trust KERI **Inconsistency vs. Duplicity**<br>- inconsistency: lacking agreement, as two or more things in relation to each other<br>- duplicity: acting in two different ways to different people concerning the same matter<br>**Internal vs. External Inconsistency** <br>- Internally inconsistent log = not verifiable.<br>- Log verification from self-certifying root-of-trust protects against internal inconsistency.<br>Externally inconsistent log with a purported copy of log but both verifiable = duplicitous.<br>Duplicity detection protects against external inconsistency. https://raw.githubusercontent.com/SmithSamuelM/Papers/master/presentations/DuplicityGame_IIW_2020_A.pdf Presentations 2020-05-09