-
Notifications
You must be signed in to change notification settings - Fork 16
fix: update ENSv1Registry address in ens-test-env devnet config #1586
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
base: main
Are you sure you want to change the base?
Conversation
The ENSv1Registry was incorrectly pointing to the RootRegistry address. Updated to use the correct LegacyENSRegistry address from devnet. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
|
📝 WalkthroughWalkthroughThe ENSv1Registry contract address in the ENSRoot datasource test environment configuration is updated from one address value to another. This is a straightforward configuration value update with no structural or functional logic changes. Changes
Possibly related PRs
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
🧪 Generate unit tests (beta)
Comment |
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.
Pull request overview
This PR fixes an incorrect contract address configuration in the ens-test-env devnet environment. The ENSv1Registry was mistakenly pointing to the ENSv2 RootRegistry address instead of its correct LegacyENSRegistry address.
Changes:
- Updated ENSv1Registry address in ens-test-env configuration from the RootRegistry address to the correct LegacyENSRegistry address
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Greptile OverviewGreptile SummaryThis PR corrects a configuration error in the Key Changes:
Impact:
Confidence Score: 4/5
Important Files Changed
Sequence DiagramsequenceDiagram
participant Dev as Developer
participant Config as ens-test-env.ts
participant ENSRoot as ENSRoot Datasource
participant ENSv2 as ENSv2Root Datasource
Note over Dev,ENSv2: Configuration Fix: ENSv1Registry Address Update
Dev->>Config: Update ENSv1Registry address
Note over Config: Old: 0x9a676e781a523b5d0c0e43731313a708cb607508<br/>(RootRegistry address)
Note over Config: New: 0x5fc8d32690cc91d4c39d9d3abcbd16989f875707<br/>(LegacyENSRegistry address)
Config->>ENSRoot: ENSv1Registry points to correct contract
Note over ENSRoot: ENSRoot datasource uses<br/>LegacyENSRegistry for ENSv1
Config->>ENSv2: RootRegistry remains unchanged
Note over ENSv2: ENSv2Root datasource uses<br/>RootRegistry at 0x9a67...7508
Note over Dev,ENSv2: Result: ENSv1Registry and RootRegistry<br/>now point to their correct respective contracts
|
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.
1 file reviewed, no comments
🚀 Preview Packages -
|
Summary
0x9a676e781a523b5d0c0e43731313a708cb607508(RootRegistry) to0x5fc8d32690cc91d4c39d9d3abcbd16989f875707(LegacyENSRegistry)Test plan
🤖 Generated with Claude Code