Skip to content
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

infra warp checker does not detect new chains #5440

Open
ltyu opened this issue Feb 11, 2025 · 0 comments
Open

infra warp checker does not detect new chains #5440

ltyu opened this issue Feb 11, 2025 · 0 comments
Milestone

Comments

@ltyu
Copy link
Contributor

ltyu commented Feb 11, 2025

Problem

Currently, the infra warp checker only uses the existing onchain routers list for enrollment violations.

override async remoteChains(chainName: string): Promise<ChainName[]> {
const router = this.router(this.contractsMap[chainName]);
const onchainRemoteChainNames = (await router.domains()).map((domain) => {
const chainName = this.multiProvider.tryGetChainName(domain);
if (chainName === null) {
throw new Error(`Chain name not found for domain: ${domain}`);
}
return chainName;
});
return onchainRemoteChainNames;
}

However, if we are adding new chains to the config, it won't show them as violations.

It should show that the existing routers have not enrolled the expected new chains.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Sprint
Development

No branches or pull requests

2 participants