-
Notifications
You must be signed in to change notification settings - Fork 173
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
Whitelist with nonexisting canonical domain #5935
base: main
Are you sure you want to change the base?
Whitelist with nonexisting canonical domain #5935
Conversation
…norepo into whitelist-with-nonexisting-canonical-domain
@@ -345,28 +345,6 @@ export const MAINNET_PRODUCTION_INIT_CONFIG: InitConfig = { | |||
}, | |||
}, | |||
}, | |||
{ | |||
// TODO: This is the old config, to be removed in execution layer upgrade |
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.
Keep this for reference, just comment out.
@@ -29,15 +29,6 @@ export const setupAsset = async (args: { | |||
`\n\tVerifying asset setup for ${asset.name} (${asset.canonical.address}). Canonical ID: ${canonical.id}; Canonical Domain: ${canonical.domain}; Key: ${key}`, | |||
); | |||
|
|||
// Set up the canonical asset on the canonical domain. |
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.
This setup script needs to be able to register xERC20s using the pseudo-canonical domain as well as maintain the ability to register other assets that are homed on Eth. I don't think we can just remove the home checks, we should still have those guards.
We need to separate logic based on whether 11111
is specifically set as the canonical domain for an asset. If not, then the original checks should still apply.
Description
Type of change
High-level change(s) description - from the user's perspective
Related Issue(s)
Fixes
Related pull request(s)