Skip to content

Conversation

@kclowes
Copy link
Collaborator

@kclowes kclowes commented Sep 21, 2020

What was wrong?

ENS names were throwing an InvalidAddress in methods that were using Method.

Related to Issue #1585

How was it fixed?

Added a new method that does a high-level validation of an ENS address, before it gets resolved in the middleware.

Todo:

  • Add entry to the release notes
  • Manually test
  • Address PR feedback
  • Make sure all changed methods are programmatically tested
  • Squash/cleanup

Cute Animal Picture

@kclowes kclowes force-pushed the accept-ens-names branch 4 times, most recently from 3837e56 to 672f6d9 Compare September 23, 2020 21:50
@@ -1,6 +1,10 @@
import pytest

from web3._utils.ens import (
Copy link
Member

Choose a reason for hiding this comment

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

Random plumbing work that should be done at some point. Anything under the web3 namespace like this that is purely a testing tool should get moved to live under web3.tools

@kclowes kclowes force-pushed the accept-ens-names branch 2 times, most recently from 3432aac to 4319ae9 Compare September 23, 2020 22:53
@kclowes kclowes requested a review from wolovim September 23, 2020 22:59
@kclowes kclowes changed the title [WIP] Allow for ENS name resolution Allow for ENS name resolution Sep 24, 2020
Copy link
Member

@wolovim wolovim left a comment

Choose a reason for hiding this comment

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

Looks good via manual testing!

@kclowes kclowes merged commit c0909fe into ethereum:master Sep 24, 2020
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.

3 participants