Blog post explaining in what ways an iroh endpoint id isn't private - #511
Open
rklaehn wants to merge 1 commit into
Open
Blog post explaining in what ways an iroh endpoint id isn't private#511rklaehn wants to merge 1 commit into
rklaehn wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This explains why iroh endpoint ids are currently not private, sketches a plan to make them more private in the future (whether we do this is another question), and provides a proof of concept blinded mainline address lookup service.
It also contains a teaser to the rcan work.
If you want to publish this while I am away, feel free to finish it.
The corresponding repo is https://github.com/n0-computer/iroh-mainline-address-lookup-blinded
Todo: