Conversation
WalkthroughNew Osmosis mainnet upgrade guide for v30→v31 documenting upgrade height placeholder, hardware requirements (64GB RAM, 32GB swap), Cosmovisor installation/configuration, automatic on-chain upgrade steps, manual fallback procedure, and links to additional resources. Static instructional documentation only. Changes
Sequence Diagram(s)sequenceDiagram
autonumber
participant Chain as Blockchain (on-chain upgrade signal)
participant Node as Node process
participant Cosmovisor as Cosmovisor
participant Operator as Operator
rect rgb(240,248,255)
Note over Chain: At configured upgrade block height\n(on-chain upgrade proposal passes)
end
Chain->>Node: Emit upgrade signal at block height
Node->>Cosmovisor: Detected upgrade signal (block height)
alt Cosmovisor has v31 binary in upgrade/bin
Cosmovisor->>Node: Swap to new v31 binary and restart node
Node->>Chain: Reconnect and continue with v31
Note right of Cosmovisor: Automatic upgrade (preferred)
else Missing/invalid binary
Cosmovisor->>Operator: Fail to auto-upgrade / log error
Operator->>Operator: Perform manual upgrade steps (fetch, build, install, restart)
Operator->>Node: Start node with v31 binary
Node->>Chain: Reconnect and continue with v31
Note right of Operator: Manual fallback path
end
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Areas to focus during review:
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
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: 0
🧹 Nitpick comments (5)
networks/osmosis-1/upgrades/v31/mainnet/guide.md (5)
53-53: Consider using a newer Cosmovisor version.v1.0.0 is an older version; latest recommended versions are v1.4+. Pinning to v1.0.0 may miss important bug fixes and security updates. Consider using
@latestor documenting why this specific version is required for Osmosis v31.Please verify with the Osmosis team whether v1.0.0 is intentionally required for v31 compatibility or if a newer version can be used.
73-73: Add context forUNSAFE_SKIP_BACKUP=true.This flag disables safety backups before upgrades. Add a brief explanation of why it's set to
trueand note the risk, or consider setting it tofalsewith guidance on backup procedures.
77-91: Clarify repository path expectations.The instructions assume the Osmosis repository is cloned at
$HOME/osmosis. If this is not the standard setup or if validators may have it elsewhere, consider adding a note to customize the path or verify the repository location.
102-107: Note inconsistency with Cosmovisor build process.The Cosmovisor section uses
make buildfollowed by manual binary copy, while manual upgrade usesmake install. Both are valid but document why the approaches differ, or standardize them for clarity.
94-109: Add recommendation to test the upgrade procedure first.Best practice for mainnet validators: test the upgrade process on testnet or staging environment before performing on live infrastructure. Consider adding a note recommending this.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
networks/osmosis-1/upgrades/v31/mainnet/v31_binaries.jsonis excluded by!**/*.json
📒 Files selected for processing (1)
networks/osmosis-1/upgrades/v31/mainnet/guide.md(1 hunks)
⏰ 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: Summary
🔇 Additional comments (2)
networks/osmosis-1/upgrades/v31/mainnet/guide.md (2)
9-34: Clear and practical guidance.Hardware recommendations and swap configuration are well-documented with helpful external references.
113-116: Good resource references.Clear pointers to official documentation and community support channels.
|
This pull request has been automatically marked as stale because it has not had any recent activity. It will be closed if no further activity occurs. Thank you! |
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
networks/osmosis-1/upgrades/v31/mainnet/v31_binaries.jsonis excluded by!**/*.json
📒 Files selected for processing (1)
networks/osmosis-1/upgrades/v31/mainnet/guide.md(1 hunks)
⏰ 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: Summary
🔇 Additional comments (3)
networks/osmosis-1/upgrades/v31/mainnet/guide.md (3)
3-7: Verify block height and proposal details are finalized.The PR objectives indicate that the upgrade height and proposal are still pending. Please confirm that:
- Block height
47626000(line 6) is finalized and will not change before merge.- The Mintscan proposal link on line 5 points to the correct proposal (currently linking to proposal 990).
If these values are still tentative, consider adding a placeholder note or deferring the merge until they are confirmed.
85-85: Verify v31.0.0 git tag exists or will exist before merge.The upgrade guide references the git tag
v31.0.0at lines 85 and 105. Confirm that this tag:
- Already exists in the repository, or
- Will be created before this PR is merged.
If the tag does not yet exist, consider updating the instructions to reference a branch or commit hash instead, or add a note that the tag will be created at release time.
Also applies to: 105-105
1-116: Approve documentation structure and content quality.The upgrade guide is well-organized and provides clear, step-by-step instructions covering both Cosmovisor and manual upgrade paths. The hardware requirements, swap configuration, and resource links are helpful. Technical instructions appear sound and align with standard Cosmos SDK upgrade practices.
| _Run these commands to install and configure Cosmovisor_: | ||
|
|
||
| ```sh | ||
| go install github.com/cosmos/cosmos-sdk/cosmovisor/cmd/cosmovisor@v1.0.0 | ||
| mkdir -p ~/.osmosisd | ||
| mkdir -p ~/.osmosisd/cosmovisor | ||
| mkdir -p ~/.osmosisd/cosmovisor/genesis | ||
| mkdir -p ~/.osmosisd/cosmovisor/genesis/bin | ||
| mkdir -p ~/.osmosisd/cosmovisor/upgrades | ||
| cp $GOPATH/bin/osmosisd ~/.osmosisd/cosmovisor/genesis/bin | ||
| mkdir -p ~/.osmosisd/cosmovisor/upgrades/v31/bin | ||
| cp $GOPATH/bin/osmosisd ~/.osmosisd/cosmovisor/upgrades/v31/bin | ||
| ``` |
There was a problem hiding this comment.
🧩 Analysis chain
Verify Cosmovisor version is current and appropriate.
The guide pins Cosmovisor to v1.0.0 at line 53. Since your knowledge cutoff is October 2025 and the current date is October 27, 2025, please verify that this version is still current and recommended. If a newer stable version exists, consider updating the pin.
🌐 Web query:
What is the current stable version of Cosmovisor?
💡 Result:
The latest stable Cosmovisor release is v1.4.0. [1][2]
Sources:
[1] Release notes — cosmos/cosmos-sdk (cosmovisor v1.4.0).
[2] Cosmovisor module docs / pkg (cosmovisor release and install guidance).
Update Cosmovisor to the current stable version v1.4.0.
The latest stable Cosmovisor release is v1.4.0, not v1.0.0. Update line 53 in the guide to pin @v1.4.0 instead of @v1.0.0.
🤖 Prompt for AI Agents
In networks/osmosis-1/upgrades/v31/mainnet/guide.md around lines 50 to 62, the
go install command pins cosmovisor to v1.0.0; update that to the current stable
v1.4.0 by changing the install line to use @v1.4.0, and verify the rest of the
guide references this version consistently.
2 participants
What is the purpose of the change
Add upgrade guide for v31
Pending Height, Proposal & Binaries
Testing and Verifying
This change is a trivial rework / code cleanup without any test coverage.
Documentation and Release Note
Unreleasedsection ofCHANGELOG.md?Where is the change documented?
x/{module}/README.md)