Conversation
📝 WalkthroughWalkthroughAdds a Mainnet section and multiple Mainnet operation pages to the developer docs, inserts Mainnet into the networks registry, adds Mainnet upgrade guides (v0.7.1, v0.7.2), and adjusts several sidebar/category metadata and minor Barra testnet docs text. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes
Possibly related PRs
Suggested reviewers
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
🧰 Additional context used📓 Path-based instructions (1)**/*.md⚙️ CodeRabbit configuration file
Files:
🪛 LanguageTooldocs/developer-docs/docs/operate-a-node/mainnet/join-mainnet.md[grammar] ~5-~5: Ensure spelling is correct (QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1) [grammar] ~26-~26: Ensure spelling is correct (QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1) [grammar] ~38-~38: Ensure spelling is correct (QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1) [grammar] ~95-~95: Ensure spelling is correct (QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1) ⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 5
🧹 Nitpick comments (2)
docs/developer-docs/docs/operate-a-node/mainnet/join-mainnet.md (1)
112-112: Clarify the RPC endpoint port specification.Line 112 specifies
https://rpc.wardenprotocol.org:443, but the endpoint URL already uses the https scheme, which defaults to port 443. Consider simplifying tohttps://rpc.wardenprotocol.orgfor consistency with line 106 and the endpoint definitions in mainnet-overview.md.Apply this diff:
- export SNAP_RPC_SERVERS="https://rpc.wardenprotocol.org:443,https://rpc.wardenprotocol.org:443" + export SNAP_RPC_SERVERS="https://rpc.wardenprotocol.org,https://rpc.wardenprotocol.org"docs/developer-docs/docs/operate-a-node/mainnet/upgrade/v0.7.2.md (1)
16-16: Consider rephrasing "prior to" for conciseness (optional).Lines 16 and 85 use the phrase "prior to the upgrade." While technically correct, this could be more concise using "before the upgrade" for a more direct tone. This is optional and does not affect clarity.
Example:
- [back up](#1-verify--back-up) your data prior to the upgrade. + [back up](#1-verify--back-up) your data before the upgrade.Also applies to: 85-85
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (13)
docs/developer-docs/docs/learn/warden-networks.md(1 hunks)docs/developer-docs/docs/operate-a-node/barra-testnet/_category_.json(1 hunks)docs/developer-docs/docs/operate-a-node/introduction.md(1 hunks)docs/developer-docs/docs/operate-a-node/mainnet/_category_.json(1 hunks)docs/developer-docs/docs/operate-a-node/mainnet/create-a-validator.md(1 hunks)docs/developer-docs/docs/operate-a-node/mainnet/join-mainnet.md(1 hunks)docs/developer-docs/docs/operate-a-node/mainnet/mainnet-overview.md(1 hunks)docs/developer-docs/docs/operate-a-node/mainnet/upgrade/_category_.json(1 hunks)docs/developer-docs/docs/operate-a-node/mainnet/upgrade/v0.7.1.md(1 hunks)docs/developer-docs/docs/operate-a-node/mainnet/upgrade/v0.7.2.md(1 hunks)docs/developer-docs/docs/operate-a-node/node-api.md(1 hunks)docs/developer-docs/docs/operate-a-node/node-commands.md(1 hunks)docs/developer-docs/docs/operate-a-node/operate-skip-connect.md(1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
**/*.md
⚙️ CodeRabbit configuration file
**/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"
Files:
docs/developer-docs/docs/operate-a-node/node-api.mddocs/developer-docs/docs/operate-a-node/operate-skip-connect.mddocs/developer-docs/docs/operate-a-node/mainnet/join-mainnet.mddocs/developer-docs/docs/operate-a-node/mainnet/upgrade/v0.7.1.mddocs/developer-docs/docs/learn/warden-networks.mddocs/developer-docs/docs/operate-a-node/mainnet/create-a-validator.mddocs/developer-docs/docs/operate-a-node/mainnet/mainnet-overview.mddocs/developer-docs/docs/operate-a-node/mainnet/upgrade/v0.7.2.mddocs/developer-docs/docs/operate-a-node/introduction.mddocs/developer-docs/docs/operate-a-node/node-commands.md
🪛 Gitleaks (8.28.0)
docs/developer-docs/docs/operate-a-node/mainnet/create-a-validator.md
[high] 66-66: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
(generic-api-key)
[high] 75-75: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
(generic-api-key)
🪛 LanguageTool
docs/developer-docs/docs/operate-a-node/mainnet/join-mainnet.md
[grammar] ~5-~5: Ensure spelling is correct
Context: --- sidebar_position: 2 --- # Join Mainnet :::important Mainnet is our new EVM netw...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~26-~26: Ensure spelling is correct
Context: ... 300GB of disk space ## 1. Install the binary To be able to interact with the node, in...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~38-~38: Ensure spelling is correct
Context: ...AIN_MONIKER ``` ## 2. Configure the binary To configure wardend, update files in ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~95-~95: Ensure spelling is correct
Context: ...ainnet/genesis.json ``` ## 3. Sync the node :::tip This step is recommended but opti...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/developer-docs/docs/operate-a-node/mainnet/create-a-validator.md
[grammar] ~5-~5: Ensure spelling is correct
Context: ...--- sidebar_position: 3 --- # Create a validator :::important Mainnet is our new EVM netw...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~17-~17: Ensure spelling is correct
Context: ...structions. ## 1. Create/restore a key pair The first step is to create a new key pa...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~51-~51: Ensure spelling is correct
Context: ...k balances KEY_NAME ``` ## 3. Create a validator Once the node is synced and you have the...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~127-~127: Ensure spelling is correct
Context: ...on-node_key.json` ## 5. Check your validator Check if your validator is in the active...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/developer-docs/docs/operate-a-node/mainnet/mainnet-overview.md
[grammar] ~5-~5: Ensure spelling is correct
Context: ...--- sidebar_position: 1 --- # Mainnet overview :::important Mainnet is our new EVM netw...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~11-~11: Ensure spelling is correct
Context: ...to selected validators. ::: ## Version history | Release ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/developer-docs/docs/operate-a-node/mainnet/upgrade/v0.7.2.md
[style] ~16-~16: ‘prior to’ might be wordy. Consider a shorter alternative.
Context: ...back up your data prior to the upgrade. During the upgrade, follow...
(EN_WORDINESS_PREMIUM_PRIOR_TO)
[grammar] ~43-~43: Ensure spelling is correct
Context: ...r), take these steps: 1. Download the [wardend binary v0.7.2](https://github.com/warde...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~82-~82: Ensure spelling is correct
Context: ...es and come back online. ## Security & troubleshooting :::warning The upgrade procedure carries...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~85-~85: ‘prior to’ might be wordy. Consider a shorter alternative.
Context: ...back up your data prior to the upgrade. During the upgrade, follow...
(EN_WORDINESS_PREMIUM_PRIOR_TO)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: Analyze (go)
🔇 Additional comments (9)
docs/developer-docs/docs/operate-a-node/node-api.md (1)
2-2: Navigation update looks good.The sidebar position adjustment from 5 to 6 appropriately reflects the insertion of the new Mainnet section higher in the navigation hierarchy.
docs/developer-docs/docs/operate-a-node/node-commands.md (1)
2-2: Navigation update looks good.The sidebar position adjustment from 6 to 7 maintains consistent ordering as the new Mainnet section is inserted before existing pages.
docs/developer-docs/docs/operate-a-node/operate-skip-connect.md (1)
2-2: Navigation update looks good.The sidebar position adjustment from 4 to 5 is consistent with the broader navigation restructuring to accommodate the new Mainnet section.
docs/developer-docs/docs/operate-a-node/mainnet/upgrade/v0.7.1.md (1)
1-9: Documentation is clear and correct.The upgrade guide for v0.7.1 is appropriately concise for a simple async update. Instructions are clear, and the link to the binary release is properly formatted.
docs/developer-docs/docs/operate-a-node/mainnet/_category_.json (1)
1-11: Navigation category is properly configured.The Mainnet category structure is correct, with position 3 appropriately placing it before Barra Testnet and the link title matching the label.
docs/developer-docs/docs/operate-a-node/introduction.md (1)
22-24: Mainnet section entry is well-structured and consistent.The new Mainnet documentation entry follows the same pattern as the Barra Testnet section, with proper link structure and clear call-to-action flow (overview → join → create validator). Grammar and formatting are correct.
docs/developer-docs/docs/operate-a-node/barra-testnet/_category_.json (1)
2-2: Navigation updates are logically consistent.The position update (3 → 4) and collapsed state change (false → true) appropriately reflect that Barra Testnet now comes after Mainnet in the navigation hierarchy, with Testnet appropriately collapsed by default as a secondary network.
Also applies to: 5-5
docs/developer-docs/docs/operate-a-node/mainnet/mainnet-overview.md (1)
1-62: LGTM!The Mainnet overview page is well-structured and provides clear documentation of version history, endpoints, chain ID, and denomination. Information is consistent with the network registry and related Mainnet guides.
docs/developer-docs/docs/operate-a-node/mainnet/upgrade/v0.7.2.md (1)
1-102: LGTM!The upgrade guide is comprehensive, well-organized, and provides clear procedures for both Cosmovisor and manual upgrade paths. Security warnings are appropriately prominent, and backup guidance is specific and helpful. The separation of concerns between verification, upgrade options, and troubleshooting is logical and easy to follow.
docs/developer-docs/docs/operate-a-node/mainnet/create-a-validator.md
Outdated
Show resolved
Hide resolved
docs/developer-docs/docs/operate-a-node/mainnet/join-mainnet.md
Outdated
Show resolved
Hide resolved
docs/developer-docs/docs/operate-a-node/mainnet/upgrade/_category_.json
Outdated
Show resolved
Hide resolved
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (1)
docs/developer-docs/docs/operate-a-node/mainnet/create-a-validator.md (1)
41-41: Make section heading more explicit about Mainnet context.The section heading "## 2. Get WARD" could be clearer by explicitly referencing Mainnet, consistent with the document's focus and to avoid ambiguity with other networks.
Consider updating to:
-## 2. Get WARD +## 2. Get Mainnet WARD
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (3)
docs/developer-docs/docs/operate-a-node/mainnet/create-a-validator.md(1 hunks)docs/developer-docs/docs/operate-a-node/mainnet/join-mainnet.md(1 hunks)docs/developer-docs/docs/operate-a-node/mainnet/mainnet-overview.md(1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
**/*.md
⚙️ CodeRabbit configuration file
**/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"
Files:
docs/developer-docs/docs/operate-a-node/mainnet/mainnet-overview.mddocs/developer-docs/docs/operate-a-node/mainnet/create-a-validator.mddocs/developer-docs/docs/operate-a-node/mainnet/join-mainnet.md
🪛 Gitleaks (8.28.0)
docs/developer-docs/docs/operate-a-node/mainnet/create-a-validator.md
[high] 66-66: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
(generic-api-key)
[high] 75-75: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
(generic-api-key)
🪛 LanguageTool
docs/developer-docs/docs/operate-a-node/mainnet/mainnet-overview.md
[grammar] ~5-~5: Ensure spelling is correct
Context: ...--- sidebar_position: 1 --- # Mainnet overview :::important Mainnet is our new EVM netw...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~11-~11: Ensure spelling is correct
Context: ...to selected validators. ::: ## Version history | Release ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/developer-docs/docs/operate-a-node/mainnet/create-a-validator.md
[grammar] ~5-~5: Ensure spelling is correct
Context: ...--- sidebar_position: 3 --- # Create a validator :::important Mainnet is our new EVM netw...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~17-~17: Ensure spelling is correct
Context: ...structions. ## 1. Create/restore a key pair The first step is to create a new key pa...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~51-~51: Ensure spelling is correct
Context: ...k balances KEY_NAME ``` ## 3. Create a validator Once the node is synced and you have the...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~127-~127: Ensure spelling is correct
Context: ...on-node_key.json` ## 5. Check your validator Check if your validator is in the active...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/developer-docs/docs/operate-a-node/mainnet/join-mainnet.md
[grammar] ~5-~5: Ensure spelling is correct
Context: --- sidebar_position: 2 --- # Join Mainnet :::important Mainnet is our new EVM netw...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~26-~26: Ensure spelling is correct
Context: ... 300GB of disk space ## 1. Install the binary To be able to interact with the node, in...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~38-~38: Ensure spelling is correct
Context: ...AIN_MONIKER ``` ## 2. Configure the binary To configure wardend, update files in ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~95-~95: Ensure spelling is correct
Context: ...ainnet/genesis.json ``` ## 3. Sync the node :::tip This step is recommended but opti...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: Analyze (go)
🔇 Additional comments (1)
docs/developer-docs/docs/operate-a-node/mainnet/mainnet-overview.md (1)
1-65: Documentation is clear and technically accurate.The Mainnet overview file provides well-organized information with correct chain ID (8765-1), endpoints, version history, and denomination details. All information is consistent with the other Mainnet guides.
docs/developer-docs/docs/operate-a-node/mainnet/join-mainnet.md
Outdated
Show resolved
Hide resolved
docs/developer-docs/docs/operate-a-node/mainnet/join-mainnet.md
Outdated
Show resolved
Hide resolved
| ``` | ||
|
|
||
| ## 2. Get testnet WARD | ||
| ## 2. Get WARD |
There was a problem hiding this comment.
Why are we changing this?
There was a problem hiding this comment.
In mainnet, this is not testnet WARD, so the title has to be Get WARD
Here I deleted it for symmetry
Though, after think twice, probably it's better to keep it, otherwise people may think the faucet gives real WARD
(updated the docs)
2 participants
Added Mainnet guides