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

Update CLI docs for mainnet acp 77 #1990

Merged
merged 4 commits into from
Jan 9, 2025
Merged

Update CLI docs for mainnet acp 77 #1990

merged 4 commits into from
Jan 9, 2025

Conversation

sukantoraymond
Copy link
Contributor

No description provided.

@sukantoraymond sukantoraymond requested review from amandamarquis1 and a team as code owners January 7, 2025 16:17
Copy link

vercel bot commented Jan 7, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
avalanche-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 9, 2025 3:24pm
builders-hub ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 9, 2025 3:24pm

Comment on lines -16 to +15
- Deploy a virtual machine based on Subnet-EVM.
- Join a node to the newly created Avalanche L1.
- Deploy an Avalanche L1.
Copy link
Collaborator

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?

Copy link
Contributor Author

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

Comment on lines 115 to 105
Local Network
Local Network
Fuji
Mainnet
Mainnet
Copy link
Collaborator

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?

Copy link
Contributor Author

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.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.
Copy link
Collaborator

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

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

addressed

sukantoraymond and others added 2 commits January 9, 2025 22:07
…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>
@owenwahlgren owenwahlgren merged commit 5b74408 into master Jan 9, 2025
3 of 4 checks passed
@meaghanfitzgerald meaghanfitzgerald deleted the mainnet-acp-77 branch January 9, 2025 22:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants