Skip to content
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

My question #325

Open
zhanb opened this issue Jul 19, 2023 · 2 comments
Open

My question #325

zhanb opened this issue Jul 19, 2023 · 2 comments

Comments

@zhanb
Copy link

zhanb commented Jul 19, 2023

"did:ion is a registry based on Bitcoin's Sidetree and it is well known that transaction fees on the Bitcoin blockchain can be very expensive. In the case of did:ion registrations, who is responsible for paying these fees, and could there be a situation where the registry provider cannot afford the high fees, resulting in unresolved did registrations?"

@thehenrytsai
Copy link
Collaborator

Anyone can perform registrations as long as they are willing to to pay the Bitcoin transaction fee. One Bitcoin transaction can "register" up to 10,000 DIDs. Even with never before seen transaction fee of $100, it'll work out to be 1c per registration, so it is not "all that expensive" if there is utility of these DIDs.

The more likely case is that a free-provider chooses to wait longer to batch more registration into one transaction, so there could be an unknown delay to a DID registration (this is already the case with Microsoft's and Block/TBD's nodes), as opposed to not being able to register at all for a prolonged period of time.

While waiting on the DID registration to occur, one can always use the "long-form" DID to start interacting with services.

@csuwildcat
Copy link
Member

Pending close, given the provided explanation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants