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

Has anyone considered porting Mesh to use DIDs (Decentralized Identifiers) and DIDCOMM (as a message transport)? #8

Open
mwherman2000 opened this issue Nov 21, 2022 · 2 comments

Comments

@mwherman2000
Copy link

Has anyone considered porting Mesh to use DIDs (Decentralized Identifiers) and DIDCOMM (as a message transport)?

I'm going to take a serious look at this and was wondering if anyone has already taken a kick at this can?

References:

Michael

@ShreyasZare
Copy link
Member

Thanks for the post. Mesh uses a proprietary p2p protocol that uses TCP transport and Kademlia based DHT to find peers. There is no other kind of implementation available for the project.

There is a plan to update this project to work cross platform with .NET in future.

@mwherman2000
Copy link
Author

mwherman2000 commented Nov 21, 2022

My idea is to replace the identity functionality with DIDs and the messaging protocol with DIDCOMM ...I'm borrowing the UX and overall project structure.

p.s. @ShreyasZare I'm the same fellow who cloned your DNSServer repository to create a DID Document Registry server that exposes itself using the standard DNS protocol.

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

2 participants