-
Notifications
You must be signed in to change notification settings - Fork 80
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
Subnet deploy including relayer deployment at the end #2436
Comments
One option is to use flag at subnet deploy command whether to include relayer deployment at the end of subnet deploy command. We will default to not deploying relayer if no flag is used |
The ability to execute cross-chain interactions relies on having a working relayer to aggregate warp(icm) signatures. The deployment flow should include a prompt with the question: Would you like to deploy and run an instance of ICM-Relayer? yes, no, explain explain should return: The ability to execute cross-chain interactions requires a running instance of the ICM-Relayer: a full-service cross-chain message delivery application that is configurable to listen to specific source and destination chain pairs and relay avalanche interchain messages (ICM). |
Is a signature aggregator deployed and run by default? i'd assume it is for L1s but not for subnets |
Signature aggregator is not deployed, but the signature aggregation function is executed by default for L1s. Not |
Coincide with giving by default the question to the user. Also ICM probably can be just installed without asking |
we should make pr to install ICM by default then |
This PR is to discuss whether subnet deploy should include relayer deployment at the end of subnet deploy process.
Currently CLI is including relayer deployment at the end of subnet deploy
The text was updated successfully, but these errors were encountered: