Fix: blog 404

[tac0turtle]

Overview

[github-actions]

The latest Buf updates on your PR. Results from workflow CI / buf-check (pull_request).

Build	Format	Lint	Breaking	Updated (UTC)
✅ passed	⏩ skipped	✅ passed	✅ passed	Jan 26, 2026, 1:37 PM

[claude]

Claude finished @tac0turtle's task in 1m 11s —— View job

---

Code Review Complete ✅

Tasks

• Read modified file and view diff
• Analyze changes against review criteria
• Provide comprehensive review feedback

---

Summary

This PR appropriately fixes a 404 error by commenting out the Blog section in the sidebar navigation. The change is consistent with the already-commented Blog entry in the main nav bar.

Review Findings

✅ Positives

1. Correctness: The fix properly addresses the 404 issue - I confirmed that no /blog/ directory exists in the docs, so the link would indeed cause a 404 error.

2. Consistency: The change makes the sidebar consistent with the nav bar, where the Blog link was already commented out (line 172 in docs/.vitepress/config.ts:172).

3. Preservation: The code is commented out rather than deleted, which is appropriate for a feature that might be added later. This maintains the structure for future blog implementation.

4. Minimal Change: The PR makes only the necessary changes - no unrelated modifications or scope creep.

5. Clean Commit History: The commit message clearly explains both the problem and the solution.

Observations & Suggestions

TypeScript/Configuration Quality

• The VitePress configuration file is well-structured and readable
• Appropriate use of TypeScript with proper typing
• Clear separation of concerns with dedicated functions (nav(), sidebarHome())

Potential Future Considerations (not blocking)

• When the blog feature is eventually implemented, both the nav and sidebar entries will need to be uncommented simultaneously to maintain consistency
• Consider adding a TODO comment indicating that the blog directory needs to be created before uncommenting these sections

Code Style

• The commenting style is consistent with the existing codebase
• Indentation and formatting are preserved correctly

Recommendation

✅ APPROVED - This PR is ready to merge. The fix is correct, minimal, and solves the stated problem effectively.

---

[gemini-code-assist]

Summary of Changes

Hello @tac0turtle, 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 significantly refactors the interaction between the sequencer and execution layers by introducing explicit transaction filtering capabilities and a mechanism to query execution parameters. These changes improve the robustness of transaction processing, particularly for transactions originating from untrusted sources, and enhance the flexibility of sequencers in constructing blocks while maintaining proper state and crash recovery. The updates span the core execution interface, sequencer logic, and various executor implementations, ensuring a more coherent and extensible design.

Highlights

• Execution Interface Refinement: The core Executor interface has been updated, removing the maxBytes return value from InitChain and ExecuteTxs to streamline its contract. This simplifies how execution clients report their state and transaction processing capabilities.
• New Transaction Filtering and Info Methods: Two new methods, FilterTxs and GetExecutionInfo, have been added to the Executor interface. FilterTxs allows execution clients to validate and filter transactions (especially force-included ones) based on size and gas, returning a detailed status for each. GetExecutionInfo provides dynamic execution parameters like the maximum gas limit per block.
• Enhanced Sequencer Transaction Processing: Both the 'Based' and 'Single' sequencers now leverage the new FilterTxs and GetExecutionInfo methods. This enables more intelligent handling of transaction batches, including robust validation of force-included transactions and proper management of transactions that are postponed due to resource limits. The ForceIncludedMask field has been removed from the Batch struct, simplifying batch representation.
• EVM and KV Executor Implementations: The EVM executor now implements the new FilterTxs method with Ethereum-specific transaction parsing and gas/size validation. The KV executor also implements FilterTxs for 'key=value' format validation and size filtering, and both provide GetExecutionInfo.
• GRPC and Telemetry Updates: The GRPC client and server have been updated to support the new FilterTxs and GetExecutionInfo RPCs, and to reflect the modified signatures of InitChain and ExecuteTxs. Telemetry tracing has also been extended to cover these new execution layer operations.

🧠 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.

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

[github-actions]

PR Preview Action v1.8.1
Preview removed because the pull request was closed.
2026-01-26 13:40 UTC

[gemini-code-assist]

Code Review

This pull request introduces significant enhancements to the execution layer and sequencer logic, primarily by integrating new transaction filtering capabilities. The Executor interface has been extended with GetExecutionInfo and FilterTxs methods, allowing execution clients to provide gas limits and perform detailed transaction validation (including size and gas filtering) for force-included transactions. The maxBytes return value has been removed from InitChain and ExecuteTxs across the codebase, as this information is now retrieved via GetExecutionInfo.

Both BasedSequencer and SingleSequencer implementations have been updated to leverage these new filtering mechanisms, ensuring that only valid and appropriately sized/gassed transactions are processed. The BasedSequencer's checkpointing and crash recovery logic has been refined to correctly handle postponed transactions and resume processing from the exact point of interruption within an epoch. Comprehensive test cases have been added or updated to validate these new behaviors, including scenarios for gas filtering, error handling, and crash recovery.

The changes are consistently applied across various components, including command-line applications, gRPC clients/servers, and telemetry tracing. The documentation in CHANGELOG.md and pkg/sequencers/based/README.md has also been updated to reflect these architectural shifts and new functionalities.