-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Polkadot DID Resolver Driver #2493
base: master
Are you sure you want to change the base?
Conversation
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
I have read and hereby sign the Contributor License Agreement. |
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.
Thanks @justraman this looks really good, I'm happy to support it. Will mark as ready for review and ping the rest of the committee.
@justraman could you also please complete KYB verification for Snowpine Labs? |
Ok, kyb has been sent 😁 |
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.
Thank you for the application, @justraman, and sorry for the long wait. I think identities on Polkadot are way underutilized, so I'd be happy to support projects in this direction.
Could you explain a bit what the purpose of PolkaIdentity is, and what need to you have for W3C-compliant identities there?
Lastly, you state that you have not started development, but also put everything into one milestone. I think it might be better to break the roadmap up into two or three milestones, so we can review the work while it's going on and possibly provide some feedback.
Hello @semuelle , I will answer the part that concerns to me as I'm the maintainer of PolkaIdentity
The purpose of PolkaIdentity was to make it easier for people to have their on-chain identity registered in a fully automated way and with trustable resources to verify any data the user inputs on it. Polkassembly was already doing that when I decided to make PolkaIdentity, the reason why I chose to make it was when the People Parachain was created, when that happened, it naturally broke every single integration Polkassembly had with the Identity pallet and as their focus is governance and not identity it took them a while to fix it. Because of that I decided that a dedicated service for identity could be a good idea as we would be able to accelerate the development when integrating the identity pallet as that's would be our main goal. The website can be found at https://polkaidentity.com and there is a thread about it at: https://forum.polkadot.network/t/polkaidentity-a-friendly-on-chain-identity-service/9702 Also the referendum that made it a registrar can be found at: https://polkadot.polkassembly.io/referenda/1192
PolkaIdentity doesn't need W3C-compliant identities at all. It works fine and it will keep working fine, PolkaIdentity goal is focused on "making" the identities and not "using" them. The W3C-compliant identities are for people looking to "use" the identities, making it easier for anyone to develop a product using them and thus increasing its usefulness regardless of which registrar created it. As a result of more people, companies, products using on-chain identities we can naturally expect more people going for registrars to make their identity and that's why PolkaIdentity was mentioned here and why we have interest on keep maintaining the driver after the grant is delivered. I hope that clarifies a bit |
Thanks for the clarification, @leonardocustodio. It would be nice to for someone to also comment on the latter part of my comment, though. |
Hello @semuelle, |
Project Abstract
The Polkadot DID Resolver project aims to bridge the Polkadot ecosystem with the broader decentralized identity landscape by implementing a W3C-compliant DID driver. This driver will enable seamless resolution of Polkadot-based DIDs and enhance interoperability with other decentralized systems. By leveraging Polkadot’s identity pallet, the project will simplify access to on-chain identities without requiring specialized Substrate knowledge, making it accessible to a wider audience of developers and applications.
Grant level
Application Checklist
project_name.md
).@_______:matrix.org
(change the homeserver if you use a different one)