-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add did:btco driver. #388
base: main
Are you sure you want to change the base?
Add did:btco driver. #388
Conversation
Hello @brianorwhatever thanks for working on this; looking forward to adding support for did:btco ! |
This is now ready for review the did spec registry PR is here w3c/did-extensions#541 |
@brianorwhatever When I try this, I get the following error:
I don't have much experience with supporting different platforms in Docker.. Do you know how to fix this? Maybe the image has to be built in a different way? |
@peacekeeper I can build it on a different platform. What should I use? I'm guessing |
Yes that would be good, thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Brian, as part of Universal Resolver stability improvements, we're requiring use of a specific image version rather than "latest" (i.e. brianrichter/did-btco:latest
). Can you tag it with a version and update the PR?
@@ -287,4 +287,10 @@ services: | |||
image: kataru/content-did-driver:latest | |||
ports: | |||
- "8148:8888" | |||
|
|||
driver-did-btco: | |||
image: brianrichter/did-btco:latest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only tag available is latest
. Ideally, please tag and push an image to a Docker registry with a semantic version number.
Hello @brianorwhatever, following up on this, would it be possible to update this PR with a stable driver version? |
This PR will be ready once the explorer at https://signet.ordinals.com has been updated to the latest release and I have tested the resolver against infrastructure I don't control.