-
Notifications
You must be signed in to change notification settings - Fork 9
Issues: decentralized-identity/trustdidweb
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
It may be better to enforce a normative requirement that the versionTime require a UTC offset
#112
opened Sep 27, 2024 by
daidoji
The ABNF for did:tdw seems to be missing the optional percent encoding of the port in the http url
#111
opened Sep 27, 2024 by
daidoji
It may be better to match the SubjectAltName (SAN) rather than the CommonName in the TLS certificate
#110
opened Sep 27, 2024 by
daidoji
Convert version entry to be a JSON object instead of an array, and related changes
#106
opened Sep 14, 2024 by
swcurran
[Edited] Clarify Data Integrity proof generation step for creation and update of a log entry
#103
opened Sep 8, 2024 by
PatStLouis
Add a section to the specification of how did:tdw can be used with the High Assurance DIDs Specification
#78
opened Jul 19, 2024 by
swcurran
Add section to specification about not trusting a DID based on verification alone
#73
opened Jul 17, 2024 by
swcurran
Is there a way/convention for transitioning an existing
did:web
DID to be a did:tdw
DID?
#68
opened Jul 9, 2024 by
swcurran
Implementor Guidance: Publishing AnonCreds objects using did:tdw
#51
opened Apr 29, 2024 by
swcurran
ProTip!
Type g i on any issue or pull request to go back to the issue listing page.