Skip to content

docs: add matcha network upgrade#2226

Merged
jcstein merged 5 commits intomainfrom
jcstein-patch-2
Sep 8, 2025
Merged

docs: add matcha network upgrade#2226
jcstein merged 5 commits intomainfrom
jcstein-patch-2

Conversation

@jcstein
Copy link
Copy Markdown
Member

@jcstein jcstein commented Sep 8, 2025

Overview

Resolves #2225

@jcstein jcstein requested a review from rootulp September 8, 2025 16:41
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 @jcstein, 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 updates the network upgrade documentation to incorporate details about the upcoming "Matcha" network upgrade (v6). The primary goal is to provide users and validators with essential information regarding the new protocol changes and their implications, ensuring they are well-informed for the transition.

Highlights

  • Documentation for Matcha Network Upgrade: Added a new section to the how-to-guides/network-upgrade-process.md file, detailing the upcoming Matcha (v6) network upgrade. This section includes a high-level overview of the upgrade's purpose and its relation to CIP-42.
  • Key Features of Matcha Upgrade: Outlined the specific changes introduced by the Matcha upgrade, referencing several Celestia Improvement Proposals (CIPs) such as CIP-36 (lowering Trusting Period), CIP-37 (lowering unbonding period), CIP-38 (increasing block/transaction size), CIP-39 (removing token filter), CIP-40 (Privval Interface Extension), and CIP-41 (adjusting issuance and commission rates).
  • Network-Specific Upgrade Details: Included a table providing upgrade details for Arabica, Mocha, and Mainnet Beta networks, specifying Chain IDs, and delay periods, with 'Date and time' and 'Upgrade height' marked as TBD.
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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

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 adds documentation for the upcoming Matcha network upgrade. The changes are a good start, but I have a couple of suggestions to improve clarity and consistency. I've recommended adding more context about the upgrade mechanism to align with other sections in the document, and I've also suggested some stylistic improvements to the list of key features for better readability.

Comment thread how-to-guides/network-upgrade-process.md
Comment thread how-to-guides/network-upgrade-process.md Outdated
Comment thread how-to-guides/network-upgrade-process.md Outdated
@jcstein jcstein merged commit 96c6ea6 into main Sep 8, 2025
7 of 8 checks passed
@jcstein jcstein deleted the jcstein-patch-2 branch September 8, 2025 18:39
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Sep 8, 2025

PR Preview Action v1.6.2
Preview removed because the pull request was closed.
2025-09-08 18:39 UTC

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.

docs: add matcha network upgrade

2 participants