docs: add jovian hardfork notice

[nud3l]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
bob-docs	Ready	Preview, Comment	Mar 4, 2026 10:04am

[gemini-code-assist]

Summary of Changes

Hello, 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 updates the full node documentation to inform operators about the upcoming Jovian hardfork. It provides critical information regarding required software upgrades, new configuration parameters, and updated timelines to ensure continued node synchronization and compatibility with the network's latest improvements.

Highlights

• Jovian Hardfork Notice: The documentation for running a full node has been updated to reflect the upcoming Jovian Hardfork for BOB Testnet and Mainnet, replacing the previous Fusaka Activation notice.
• Node Operator Requirements: Required op-node and op-geth versions for external node operators have been updated, along with new override parameters specific to the Jovian hardfork for both Testnet and Mainnet.
• Documentation Updates: Important dates for the hardfork activation, details on the upgrade's scope (rollup fee calculation improvements), and links to the official Upgrade 17 Notice have been incorporated.
• Docker Image and Hardware Recommendations: The recommended Docker image versions for op-geth and op-node in the docker-compose.yml example have been updated, and the recommended hardware configuration date has been adjusted to March 2026.

🧠 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

• docs/docs/docs/bob-chain/full-node.md
  • Updated the hardfork warning from 'Fusaka Activation' to 'Jovian Hardfork'.
  • Revised the 'What's Included in the Upgrade' section to detail rollup fee calculation improvements and link to the Upgrade 17 Notice.
  • Updated 'Important Dates' for Testnet and Mainnet hardfork activation.
  • Specified new minimum and recommended versions for op-node and op-geth for node operators.
  • Added required --override.jovian parameters for both Testnet and Mainnet configurations.
  • Updated the warning message for incorrectly configured nodes.
  • Updated the 'More Info' link to reference the 'Upgrade 17 Notice'.
  • Adjusted the recommended hardware configuration date from December 2025 to March 2026.
  • Updated the op-geth Docker image version to v1.101609.0 in docker-compose.yml.
  • Updated the op-node Docker image version to v1.16.6 in docker-compose.yml.

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 documentation for running a full node to reflect the upcoming Jovian Hardfork on BOB Testnet and Mainnet. It includes revised important dates, updated op-node and op-geth versions, and new override parameters for node operators. The hardware requirements section has also been updated with the new timeline, and the docker-compose.yml example now uses the recommended image versions. The changes are clear and directly address the hardfork requirements.

_{Note: Security Review has been skipped due to the limited scope of the PR.}