docs: mainnet operator notes — versions table row and network selection guide - #260
Open
osr21 wants to merge 1 commit into
Open
docs: mainnet operator notes — versions table row and network selection guide#260osr21 wants to merge 1 commit into
osr21 wants to merge 1 commit into
Conversation
…ork selection in running-an-arc-node.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
With Arc mainnet approaching, the operator docs only describe testnet. This PR adds the mainnet facts that are already verifiable from this repository — nothing speculative, no invented endpoints.
docs/installation.md— adds an Arc Mainnet row (v0.7.0 or later) to the Versions table, with a note carrying the version floor and the v0.7.0 libp2p peering implication over from BREAKING_CHANGES.md, where operators reading the installation page currently won't see it.docs/running-an-arc-node.md— adds a "Choosing a network" section after the intro:--chainvalue, chain ID, minimum versionarc-mainnetis a named chainspec since v0.7.0 —crates/execution-config/src/chainspec.rsregisters it, genesis atassets/mainnet/genesis.json)--chain=arc-mainnetonce mainnet snapshots are published, and a warning not to reuse the guide's testnet RPC/follow endpoints on mainnetWhat this PR deliberately does NOT do
v0.6.0→v0.7.3is docs: update Arc Testnet version to v0.7.3 in installation.md #226's claimed fix; this PR only adds adjacent lines, though whichever merges second will need a trivial rebase of that hunk).snapshots.arc.networkhas noarc-mainnetmanifest and no mainnet RPC hostname answers). The text says "once published" rather than inventing endpoints. Happy to follow up with concrete URLs when Circle publishes the mainnet infrastructure.Verification
5042and thearc-mainnetchainspec name verified againstcrates/shared/src/chain_ids.rsandcrates/execution-config/src/chainspec.rson main.BREAKING_CHANGES.md/CHANGELOG.mdv0.7.0 entries.