-
Notifications
You must be signed in to change notification settings - Fork 206
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
Create btc.json #558
Create btc.json #558
Conversation
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.
@sangaman could you check with there are some issues with your PR?
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.
Meets minimum requirements for registration.
Re-ping for review of did:btc -- @apuchitnis, @stenreijers, @gatemezing, @adam-burns, @Steffytan, @MizukiSonoko, @rajivrajani, @genaris, @ajile-in and @KDean-Dolphin |
2nd re-ping for review of did:btc -- @apuchitnis @stenreijers @gatemezing @esaung @michallis @richardwinputra @adam-burns @Steffytan @MizukiSonoko @rajivrajani @genaris @harleyjackthomas @ajile-in @KDean-Dolphin |
Hello, I'm afraid this method might be effectively abandoned at the moment. I would be happy to address the reviews to get this merged if we want it for posterity's sake - however as far as I know there are not any plans to keep working on this method or build applications for this method in the foreseeable future. |
So, you'll change the status in the file? or how do you see we move forward? |
I'll close the PR, then. No need to eat up space in the registry for something where the registrant has stated that there will be no future work on this method. |
DID Method Registration
As a DID method registrant, I have ensured that my DID method registration complies with the following statements:
contactEmail
address [OPTIONAL].verifiableDataRegistry
entry [OPTIONAL].