Consider Validating Alsoknownas Hostnames More Issue 16 Did Method
Consider Validating Alsoknownas Hostnames More Issue 16 Did Method Sign up for a free github account to open an issue and contact its maintainers and the community. specify intended plc host, in did document? protip! type g p on any issue or pull request to go back to the pull request listing page. Currently, atproto supports two did methods: did:web, which is a w3c standard based on https (and dns). the identifier section is a hostname. this method is supported in atproto to provide an independent alternative to did:plc.
Specify Intended Plc Host In Did Document Issue 33 Did Method
Specify Intended Plc Host In Did Document Issue 33 Did Method I've been working on some code to follow the did:plc spec and wanted to clarify, for others, that the spec doesn't follow the dag cbor guidelines for encoding cids in cbor. Did plc is a self authenticating did which is strongly consistent, recoverable, and allows for key rotation. control over a did:plc identity rests in a set of reconfigurable rotation keys pairs. Bluesky social pbc developed did plc when designing the at protocol (atproto) because we were not satisfied with any of the existing did methods. we wanted a strongly consistent, highly available, recoverable, and cryptographically secure method with fast and cheap propagation of updates. Repositories did method plc public public ledger of credentials: a cryptographic, strongly consistent, and recoverable did method.
In The Wild Signature With Non Canonical Encoding Issue 53 Did
In The Wild Signature With Non Canonical Encoding Issue 53 Did Bluesky social pbc developed did plc when designing the at protocol (atproto) because we were not satisfied with any of the existing did methods. we wanted a strongly consistent, highly available, recoverable, and cryptographically secure method with fast and cheap propagation of updates. Repositories did method plc public public ledger of credentials: a cryptographic, strongly consistent, and recoverable did method. Did plc is a self authenticating did which is strongly consistent, recoverable, and allows for key rotation. an example did is: did:plc:ewvi7nxzyoun6zhxrhs64oiz. control over a did:plc identity rests in a set of reconfigurable rotation keys pairs. Did plc is a self authenticating did which is strongly consistent, recoverable, and allows for key rotation. see web.plc.directory for details. this project is dual licensed under mit and apache 2.0 terms: downstream projects and users may chose either license, or both, at their discretion. We’ve made a minor change to the plc directory service, with the aim of expanding compatibility with non atproto apps and services: “verificationmethod” keys can now be almost any key type, including but not limited to ed25519. Go implementation of did:plc. contribute to did method plc go didplc development by creating an account on github.
Review Tweak Did Document Context Issue 32 Did Method Plc Did
Review Tweak Did Document Context Issue 32 Did Method Plc Did Did plc is a self authenticating did which is strongly consistent, recoverable, and allows for key rotation. an example did is: did:plc:ewvi7nxzyoun6zhxrhs64oiz. control over a did:plc identity rests in a set of reconfigurable rotation keys pairs. Did plc is a self authenticating did which is strongly consistent, recoverable, and allows for key rotation. see web.plc.directory for details. this project is dual licensed under mit and apache 2.0 terms: downstream projects and users may chose either license, or both, at their discretion. We’ve made a minor change to the plc directory service, with the aim of expanding compatibility with non atproto apps and services: “verificationmethod” keys can now be almost any key type, including but not limited to ed25519. Go implementation of did:plc. contribute to did method plc go didplc development by creating an account on github.