Add support for generating and saving did:web DIDs. #43
Conversation
|
Can we use a plugin-like architecture here instead? It seems unsustainable to keep adding every DID method we can think of to a monolithic package. |
|
@dlongley - I'm certainly open to suggestions, architecturally. In my experience, CLI tools tend to be fairly monolithic (unlike, say, isomorphic libs). And eventually, I assume we'd add support for the CLI tool using the Universal Verifier interface (which would provide support for a whole lot more methods). |
There was a problem hiding this comment.
I don't want to hold this up -- but I don't agree with the architectural choice of making it monolithic. Since I don't have any cycles to suggest or implement something else concrete I'm approving, but I expect it will create more technical debt to have to clean up later.
To be clear, it's certainly good to be able to make this work with did:web ... I'm just concerned about the how.
Thanks!
| Supported DID methods: | ||
| - `did:key` | ||
| - [`did:web`](https://w3c-ccg.github.io/did-method-web/) | ||
| - Coming Soon: Veres One `did:v` (`capybara` testnet) |
There was a problem hiding this comment.
| - Coming Soon: Veres One `did:v` (`capybara` testnet) | |
| - Coming Soon: Veres One `did:v1` (`capybara` testnet) |
No description provided.