In advance of the design workshop, all participants produced a one-or-two page advance reading to be shared with the other attendees on either:
- A specific problem that they wanted to solve with a web-of-trust solution, and why current solutions (PGP or CA-based PKI) can't address the problem?
- A specific solution related to the web-of-trust that you'd like others to use or contribute to?
These advance readings can indicate what topics you're interested in and can also help to shape the week's discussion by suggesting topics of interest or even potential solutions.
If you will be attending Rebooting the Web of Trust October 2024 in Ventura, please upload your advance readings to this directory with a pull request.
Unfortunately, the workshop has been cancelled. We are maintaining this page to list the primers and the advance readings already submitted.
These primers overview major topics which are likely to be discussed at the design workshop. If you read nothing else, read these. (But really, read as much as you can!)
- Advance Reading Primer — About the advance reading papers
- RWOT Primer — How the design workshop works
- DID Primer — Decentralized Identifiers (extended version also available)
- Functional Identity Primer — A different way to look at identity
- Verifiable Credentials Primer — the project formerly known as Verifiable Claims
- Glossary of Terms — a brief dictionary of technical terms used at RWOT
Please add a level three header (###) for your paper's topic if it's not there already, then link it in the form:
[name](link)
* by [author](mailto:if desired)
* One to two sentence synopsis or quote
* #hashtags for topics
CMS: A Consortium Management Solution for Decentralized Identifier Resolution
- by Zhiping Li, Bo Zhang
- A Consortium Management Solution based on DID universal resolver for Decentralized Identifier Resolution
- #did #universal resolve #smart contracts# ipfs #consortium-based management
- by Kevin Dean
- DID method names are prone to collision and there's no mechanism to distinguish between two DID methods with the same name. Version control is also an issue, as a significant change to a DID method's protocol may warrant a new name. This paper outlines a collision-resistant naming convention and a version management protocol to address these issues.
- #did #resolver #versioning #ipfs
Please also enter your paper alphabetically in the form:
* [Paper Name](link)