-
Notifications
You must be signed in to change notification settings - Fork 406
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
Update CLI docs for mainnet acp 77 #1990
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
- Deploy a virtual machine based on Subnet-EVM. | ||
- Join a node to the newly created Avalanche L1. | ||
- Deploy an Avalanche L1. |
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.
Isn't the default still using Subnet-EVM?
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.
Yes, but don't think we need to specify using Subnet EVM, I think just saying deploying L1 makes it simpler to understand for new devs
content/docs/avalanche-l1s/deploy-a-avalanche-l1/avalanche-mainnet.mdx
Outdated
Show resolved
Hide resolved
Local Network | ||
▸ Local Network | ||
Fuji | ||
▸ Mainnet | ||
Mainnet |
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.
Should the arrow point to Mainnet
?
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.
addressed
|
||
For instructions on controlling your Avalanche L1 with a multisig, see the [Multisig Deployment Tutorial](/avalanche-l1s/deploy-a-avalanche-l1/multisig-auth). | ||
</Callout> | ||
Select `No` to using local machine as a bootstrap validator on the blockchain. |
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.
Select `No` to using local machine as a bootstrap validator on the blockchain. | |
Select `No` when asked if you want to use local machine as a bootstrap validator on the blockchain. |
After you update your config, you are going to need to restart your node for the changes to | ||
take effect. | ||
``` | ||
To get your new Avalanche L1 information, visit the [Avalanche L1 Explorer](https://subnets-test.avax.network/). The search best works by blockchain ID, so in this example, enter `2U7vNdB78xTiN6QtZ9aetfKoGtQhfeEPQG6QZC8bpq8QMf4cDx` into the search box and you should see your shiny new blockchain information. |
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.
We should also include avalanche blockchain describe
as an option for printing blockchain information
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.
addressed
content/docs/avalanche-l1s/deploy-a-avalanche-l1/avalanche-mainnet.mdx
Outdated
Show resolved
Hide resolved
…nnet.mdx Co-authored-by: Meaghan FitzGerald <meag.fitz@avalabs.org> Signed-off-by: sukantoraymond <rsukanto@umich.edu>
…nnet.mdx Co-authored-by: Meaghan FitzGerald <meag.fitz@avalabs.org> Signed-off-by: sukantoraymond <rsukanto@umich.edu>
No description provided.