-
Notifications
You must be signed in to change notification settings - Fork 402
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
Rewrite ExtendedDNSResolver to support more record types #331
Merged
Merged
Changes from 9 commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
6db6444
Add hexToBytes()
Arachnid e95380c
First version of better parser
Arachnid c321f91
More tests
Arachnid 4472f47
Text record support
Arachnid 23a3d66
Remove console log
Arachnid 513fbe1
Add support for easier encoding of EVM chain IDs
Arachnid c9535ae
Handle multiple spaces between records
Arachnid 6fc58e6
Handle no spaces between quoted records
Arachnid 38407f0
Add comment referencing ensip-11
Arachnid 8dd3f11
unify utility contracts
mdtanrikulu 63ca27e
Changesx in response to revie
Arachnid b479cd2
Merge pull request #342 from ensdomains/fix/unify-utility-contracts
mdtanrikulu d3d6b70
Merge branch 'staging' into feature/better-offchain-dns
mdtanrikulu File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
How about contenthash?
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.
There's no browsers that would prioritize a contenthash in ENS over the A records of the domain right now, and no reasonable prospect that that'll change any time soon.
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.
true, browsers won't care about any of these records, but some people still want to associate IPFS with DNS names. it would be easy to implement because it doesn't require a parameter, (
c=<hash>
), and then you have complete resolver support.ps. I know these records need to be evm-readable, but you have 255 chars to work with and humans involved. how about
addr[60]=0x00
,text[avatar]='http...'
, andcontenthash=<hash>
. maybe supportaddr=0x00
anda=0x00
as well.pps.
dnsname.ens.eth
is a mouthful,dns.resolver
would be nice.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.
If there are any integrations that want to read this field from ENS names, I'll happily add support here.
256 characters is only 5 addresses. We don't have a lot of spare space to work with here.