Skip to content

docs: v4 activation height for Mainnet Beta#2161

Merged
jcstein merged 2 commits intocelestiaorg:mainfrom
rootulp:rp/v4-height
Jul 22, 2025
Merged

docs: v4 activation height for Mainnet Beta#2161
jcstein merged 2 commits intocelestiaorg:mainfrom
rootulp:rp/v4-height

Conversation

@rootulp
Copy link
Copy Markdown
Contributor

@rootulp rootulp commented Jul 22, 2025

Estimate based on https://www.mintscan.io/celestia/block/6680339

$ celestia-appd query signal upgrade --node [https://rpc.lunaroasis.net:443](https://rpc.lunaroasis.net/)
An upgrade is pending to app version 4 at height 6680339.

@rootulp rootulp self-assigned this Jul 22, 2025
@rootulp rootulp changed the title docs: v4 height docs: v4 activation height for Mainnet Beta Jul 22, 2025
@rootulp rootulp requested a review from jcstein July 22, 2025 14:14
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Summary of Changes

Hello @rootulp, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on enhancing the clarity and accuracy of the network upgrade documentation by incorporating the latest estimated details for the v4 Mainnet Beta upgrade. The primary goal is to provide users with precise information regarding the upgrade height and date, ensuring they are well-informed for the transition.

Highlights

  • Documentation Update: I've updated the how-to-guides/network-upgrade-process.md file to include the estimated upgrade height and date for the upcoming v4 Mainnet Beta network upgrade. This information is crucial for users to prepare for the upgrade.
  • Markdown Table Formatting: I've made minor formatting adjustments to the markdown table headers within the how-to-guides/network-upgrade-process.md file to ensure consistent rendering.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments or fill out our survey to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request updates the documentation for the v4 network upgrade on Mainnet Beta, providing the estimated activation height and time. My review focuses on improving the formatting of the markdown tables for better source code readability and consistency across the documentation.

Comment thread how-to-guides/network-upgrade-process.md Outdated
Comment thread how-to-guides/network-upgrade-process.md Outdated
Comment thread how-to-guides/network-upgrade-process.md Outdated
@jcstein jcstein merged commit 7e874c2 into celestiaorg:main Jul 22, 2025
4 of 5 checks passed
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.

2 participants