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

Update lisk.json #537

Merged
merged 3 commits into from
Jul 20, 2024
Merged

Update lisk.json #537

merged 3 commits into from
Jul 20, 2024

Conversation

aldhosutra
Copy link
Contributor

Adding contactEmail as suggested in the following comment:
#529 (comment)

@msporny
Copy link
Member

msporny commented Apr 1, 2024

@msporny
Copy link
Member

msporny commented May 14, 2024

@aldhosutra
Copy link
Contributor Author

Hello Everyone,

I would like to inform you, that due to the migration from "Lisk" to L2 EVM-based chain, and the takeover of the old L1 Lisk network to "Klayr", I changed the DID method "lisk" to "klayr". The migration occurred today (May 21, 2024).

In this case, there are no changes to the DID specification document, except for changing the name "Lisk" to "Klayr". Please kindly check.

More about Lisk migration:
https://lisk.com/blog/posts/announcing-lisk-move-to-ethereum-ecosystem

More on the takeover by Klayr:
https://klayr.xyz/news/an-introduction-to-the-new-l1/

Kind regards,

Copy link
Collaborator

@gatemezing gatemezing left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've reviewed the file and all seems fine from my side

Copy link
Member

@msporny msporny left a 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.

@msporny msporny merged commit 321bfb1 into w3c:main Jul 20, 2024
1 check passed
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

Successfully merging this pull request may close these issues.

4 participants