Closed nitin-vavdiya closed 3 months ago
@nitin-vavdiya Thanks for reporting this. It seems this bug was introduced when we made some changes to how the DIDs are resolved. I think I managed to fix this in https://github.com/decentralized-identity/uni-resolver-driver-did-key/commit/07c0af73e0f8397b39b4ab69f41039732e99a9c8.
Can you try again with the latest
Docker image? We can also do another release tag with this fix.
Closing. Feel free to open a new issue if there is still a problem.
Hey,
I am using
universalresolver/driver-did-key:latest
to resolve did document ofdid:key:z6Mkfriq1MqLBoPWecGoDLjguo1sB9brj6wT3qZ5BxkKpuP6
.When I use docker image tag
0.2.0-f98a04a
, it is returning below response:When I use
latest
docker tag, it is returning below response:Why both docker images are returning did document in different json format?