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

Add IPNS namespace #136

Merged
merged 2 commits into from
Jul 3, 2019
Merged

Add IPNS namespace #136

merged 2 commits into from
Jul 3, 2019

Conversation

mcdee
Copy link
Contributor

@mcdee mcdee commented Jun 9, 2019

Add an IPNS namespace. This will have the same format as IPFS but allow resolution of IPNS paths.

@Amxx
Copy link

Amxx commented Jun 9, 2019

#137

@mcdee
Copy link
Contributor Author

mcdee commented Jun 17, 2019

@Stebalien any chance of merging this? Making the IPNS namespace official will help with the ENS integration.

@lidel lidel requested a review from Stebalien June 24, 2019 10:24
Copy link
Member

@lidel lidel left a comment

Choose a reason for hiding this comment

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

I know @Stebalien has limited bandwidth, is there anyone else who can review/merge this?
cc @hugomrdias @aschmahmann @parkan

Copy link
Member

@Stebalien Stebalien left a comment

Choose a reason for hiding this comment

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

Looks reasonable.

If possible, I'd like to only use this for IPNS, not /ipns/some.random.domain.name.

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