Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/w3c/vc-di-eddsa
EdDSA Data Integrity Cryptosuites Specification
https://github.com/w3c/vc-di-eddsa
decentralized-identifiers ed25519 jsonld multibase multicodec standard vc-wg verifiable-credentials w3c
Last synced: 2 months ago
JSON representation
EdDSA Data Integrity Cryptosuites Specification
- Host: GitHub
- URL: https://github.com/w3c/vc-di-eddsa
- Owner: w3c
- License: other
- Created: 2020-09-16T22:24:16.000Z (about 4 years ago)
- Default Branch: main
- Last Pushed: 2024-09-30T01:34:39.000Z (2 months ago)
- Last Synced: 2024-09-30T04:21:55.921Z (2 months ago)
- Topics: decentralized-identifiers, ed25519, jsonld, multibase, multicodec, standard, vc-wg, verifiable-credentials, w3c
- Language: HTML
- Homepage: https://w3c.github.io/vc-di-eddsa/
- Size: 442 KB
- Stars: 12
- Watchers: 19
- Forks: 10
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE.md
- Code of conduct: CODE_OF_CONDUCT.md
- Codeowners: CODEOWNERS
Awesome Lists containing this project
- awesome-ccamel - w3c/vc-di-eddsa - EdDSA Data Integrity Cryptosuites Specification (HTML)
README
## EdDSA Data Integrity Cryptosuites
This specification describes a Data Integrity cryptographic suite for use when
creating or verifying a digital signature using the twisted Edwards Curve
Digital Signature Algorithm (EdDSA) and Curve25519 (ed25519). The approach is
accepted by the U.S. National Institute of Standards in the latest FIPS 186-5
draft and, after ratification, is expected to meet U.S. Federal Information
Processing requirements when using cryptography to secure digital information.We encourage contributions meeting the
[Contribution Guidelines](CONTRIBUTING.md). While we prefer the creation of
issues and Pull Requests in the GitHub repository, discussions also occur on the
[public-vc-wg](http://lists.w3.org/Archives/Public/public-vc-wg/) mailing list.## Verifiable Credentials Working Group
* Group page: [https://www.w3.org/2017/vc/WG/](https://www.w3.org/2017/vc/WG/)
* Charter: [https://www.w3.org/2022/06/verifiable-credentials-wg-charter.html](https://www.w3.org/2022/06/verifiable-credentials-wg-charter.html)
* Chairs
* Brent Zundel - @brentzundel
* W3C Staff Contact
* Ivan Herman - @iherman### Other Relevant Working Group Repositories
* [Use Cases](https://github.com/w3c/vc-use-cases)
* [Data Model](https://github.com/w3c/vc-data-model)
* [Data Integrity](https://github.com/w3c/vc-data-integrity)### Discussion Forums
* [W3C Credentials Community Group Mailing List (Incubation)](https://lists.w3.org/Archives/Public/public-credentials/)
* [W3C Verifiable Credentials WG Mailing List (Standardization)](https://lists.w3.org/Archives/Public/public-vc-wg/)## Process Overview for VC Data Model Pull Requests
1. Anyone can open a PR on the repository. Note that for the PR to be merged,
the individual must agree to the
[W3C Patent Policy](https://www.w3.org/Consortium/Patent-Policy/).
2. Once a PR is opened, it will be reviewed by the Editors and other WG
Members.
3. The W3C CCG is automatically notified of PRs as they are raised and
discussed.
4. PRs are usually merged in 7 days if there is adequate review and consensus,
as determined by the Chairs and Editors.### Roadmap for 2022-2024
The VCWG has a set of
[deliverables](https://www.w3.org/2022/06/verifiable-credentials-wg-charter.html#deliverables)
and a
[timeline](https://www.w3.org/2022/06/verifiable-credentials-wg-charter.html#timeline)
listed in the most recent
[VCWG charter](https://www.w3.org/2022/06/verifiable-credentials-wg-charter.html)