[RFC] SWIP-38 parse and direct ENS TEXT records#73
Open
significance wants to merge 2 commits intoethersphere:masterfrom
Open
[RFC] SWIP-38 parse and direct ENS TEXT records#73significance wants to merge 2 commits intoethersphere:masterfrom
significance wants to merge 2 commits intoethersphere:masterfrom
Conversation
significance
force-pushed
the
feat/SWIP-38
branch
2 times, most recently
from
d06ce64 to
3bf3847
Compare
significance
force-pushed
the
feat/SWIP-38
branch
from
3bf3847 to
76078d1
Compare
significance
changed the title
significance
changed the title
Clarified the process for handling ENS names at Swarm gateways, specifying retrieval from ENS TEXT records when the content hash is empty or not prefixed by bzz://.
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.
Enhance gateway ENS functionality by deferencing a "bzz" ENS TEXT record as well as the currently supported content record with "bzz://" protocol prefix to enable ENS users to simultaneously use Swarm as well as other providers, eg. IPFS.