search

w3c-ccg / didm-btcr

WORK ITEM: BTCR DID Method Spec
https://w3c-ccg.github.io/didm-btcr/
Other
5 stars 4 forks source link

Continuation DID Document URL should support Hashlink #14

Open peacekeeper opened 5 years ago

peacekeeper commented 5 years ago

The spec says that if the Continuation DID Document is in a mutable store, it must be signed with the transaction signing key along with a timestamp. But the problem with this is that the document could change at any time. Instead we can support Hashlink which solves this and has other benefits as well:

https://github.com/w3c-ccg/community/issues/48

kimdhamilton commented 5 years ago

Yes this is a great suggestion. We didn’t have hashlink in our toolset at the time, but it will greatly cleanup the awkwardness in the BTCR method spec around mutable/immutable store handling