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 EIP: Contract Discovery and eTLD+1 Association #7815
Conversation
File
|
@@ -0,0 +1,157 @@ | |||
--- | |||
eip: XXXX |
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.
eip: XXXX | |
eip: 7528 |
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.
thank you, adding now
Hi @TtheBC01 thanks for your draft. ERC Editor here. |
Change name to match new assigned EIP number
EIPS/eip-7528.md
Outdated
@@ -0,0 +1,157 @@ | |||
--- | |||
eip: 7528 |
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.
eip: 7528 | |
eip: 7529 |
Assigning next sequential EIP/ERC number. 7528 already assigned to #7808.
EIP/ERC numbering changed to sequential from 7500 and is no longer the PR number.
Please also update the filename.
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.
thank you, on it
The commit 98c034e (as a parent of a0568b2) contains errors. |
I am closing this pull request because we are in the process of separating EIPs and ERCs into distinct repositories. Unfortunately, as far as we are aware, GitHub does not provide any tools to ease this migration, so every pull request will need to be re-opened manually. As this is a PR to create / modify an ERC, I will kindly ask you to redirect this to the new repository at ethereum/ERCs. We have prepared a guide to help with the process. If there is relevant history here, please link to this PR from the new pull request. On behalf of the EIP Editors, I apologize for this inconvenience. |
All good, we'll reopen it in the appropriate place. |
At Snickerdoodle Labs, we've had good success leveraging whats proposed in this draft EIP in our own protocol. We decided to write it up as a proposal and see if the Ethereum community would also find it useful.
This proposal describes a simple standard to leverage TXT records to discover smart contracts and verify their association with a known DNS domain. This is enabled by the relatively recent support for DNS over HTTPS (DoH) by most major DNS providers.