Adapt to latest did-core-spec
See original GitHub issueThis library is using some assumptions that no longer hold true against the latest did core spec. More specifically, did resolution should now use:
DidResolutionResult
instead ofDIDDocument
verificationMethod
instead ofpublicKey
in theDIDDocument
- and
blockchainAccountId
instead ofethereumAddress
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Adapting To The Latest Technology Trends For Your ...
The pace of technologically is as staggering. Read our tips to keep up with the latest technology trends and use them in business....
Read more >5 ways to help your team adapt to new technology
New technologies and change help businesses stay relevant and successful. Finding a way to reduce resistance will make goals happen a lot faster....
Read more >Adapt Your Business to the New Reality
In the following pages we'll discuss how companies can reassess their growth opportunities in the new normal, reconfigure their business models to better ......
Read more >3 Reasons Executives Should Adapt to New Technologies
An executive who can effectively learn and use the latest advancement in technology gives him or herself an edge over other executives.
Read more >Adapting interventions to new contexts-the ADAPT guidance
Implementing interventions with a previous evidence base in new contexts might be more efficient than developing new interventions for each ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is excellent, thanks for capturing these changes… regarding blockchainAccountId, this may be helpful:
https://github.com/OR13/lds-blockchain2021
https://or13.github.io/lds-blockchain2021/#did-document
🎉 This issue has been resolved in version 5.1.0 🎉
The release is available on:
Your semantic-release bot 📦🚀