docs: update v7 CIPs status to Last Call

[rootulp]

Summary

• Remove CIP-43 from CIP-47 requires
• Update CIP-44, CIP-45, CIP-46, and CIP-47 status from In Review to Last Call with a deadline of 2026-03-03

v7 activated on Arabica.

🤖 Generated with Claude Code

[gemini-code-assist]

Summary of Changes

Hello @rootulp, I'm Gemini Code Assist¹! 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 advances the status of several Celestia Improvement Proposals (CIPs) related to the v7 network upgrade to 'Last Call,' indicating they are nearing finalization. It also adjusts the dependencies for CIP-47 by removing a no longer relevant requirement.

Highlights

• CIP Status Updates: The status of CIP-44, CIP-45, CIP-46, and CIP-47 has been updated from 'In Review' to 'Last Call'.
• Last Call Deadline: A 'last-call-deadline' of 2026-03-03 has been added to CIP-44, CIP-45, CIP-46, and CIP-47.
• CIP-47 Requirements Adjusted: CIP-43 has been removed from the 'requires' list in CIP-47.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• cips/cip-044.md
  • Updated the status from 'In Review' to 'Last Call'.
  • Added a 'last-call-deadline' of 2026-03-03.
• cips/cip-045.md
  • Updated the status from 'In Review' to 'Last Call'.
  • Added a 'last-call-deadline' of 2026-03-03.
• cips/cip-046.md
  • Updated the status from 'In Review' to 'Last Call'.
  • Added a 'last-call-deadline' of 2026-03-03.
• cips/cip-047.md
  • Updated the status from 'In Review' to 'Last Call'.
  • Added a 'last-call-deadline' of 2026-03-03.
  • Removed 'CIP-43' from the 'requires' field.

Activity

• The v7 network has been activated on Arabica.
• The changes were generated using Claude Code.

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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. ↩

[gemini-code-assist]

Code Review

This pull request updates the status of several Celestia Improvement Proposals (CIPs) to 'Last Call' and sets a deadline, which aligns with the v7 network upgrade process. The changes are logical and correctly reflect the removal of CIP-43 from the v7 upgrade scope. My review focuses on some minor formatting inconsistencies in the markdown tables that were affected by these changes. Addressing these will improve the readability and maintainability of the documentation.