Skip to content

Conversation

@jcstein
Copy link
Member

@jcstein jcstein commented Sep 2, 2025

Overview

  1. adds CDC 37&38 to readme/homepage
  2. updates status of CIPs as discussed in CDC 37:
    • CIP-39 to Final
    • CIP-40 to Final
    • CIP-41 to Final
    • CIP-42 to Last Call

@jcstein jcstein requested review from cmwaters and rootulp September 2, 2025 15:51
@jcstein jcstein self-assigned this Sep 2, 2025
Copy link
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 focuses on synchronizing the project's documentation with recent Core Devs Call decisions. It primarily updates the main CIPs README to reflect the latest meeting information and advances the official status of several key Celestia Improvement Proposals (CIPs) based on their progression through the review and finalization process.

Highlights

  • Documentation Updates: Added entries for Core Devs Call (CDC) 37 and 38 to the cips/README.md file, including their respective agendas, notes, and recording links.
  • CIP Status Advancement: Updated the status of CIP-39 (Remove token filter for Hyperlane and IBC) from 'Last Call' to 'Final'.
  • CIP Status Advancement: Updated the status of CIP-40 (Privval Interface Extension for Arbitrary Message Signing) from 'Last Call' to 'Final'.
  • CIP Status Advancement: Updated the status of CIP-41 (Reduce issuance to 2.5% and increase minimum commission to 10%) from 'Last Call' to 'Final'.
  • CIP Status Advancement: Updated the status of CIP-42 (Matcha Network Upgrade) from 'Review' to 'Last Call', including the addition of a 'last-call-deadline'.
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.

@jcstein jcstein requested a review from ebuchman September 2, 2025 15:52
Copy link
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 status of several Celestia Improvement Proposals (CIPs) following Core Devs Call 37, and adds details for CDCs 37 and 38 to the main README. The changes are accurate and reflect the decisions from the call. My feedback focuses on improving the formatting of the markdown tables in the updated CIP files for better readability and consistency across the repository.

@jcstein jcstein merged commit 9cf1b20 into main Sep 2, 2025
6 of 7 checks passed
@jcstein jcstein deleted the jcs/updates branch September 30, 2025 20:34
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.

4 participants