docs: add queued & parallel submission for light node

[jcstein]

Overview

[gemini-code-assist]

Summary of Changes

Hello @jcstein, 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 enhances the documentation for Celestia light nodes by providing an in-depth guide on advanced transaction submission strategies. It clarifies how users can optimize transaction throughput and ordering guarantees by configuring different modes, namely Default, Queued, and Parallel, through the TxWorkerAccounts setting. The update aims to empower users to better manage their transaction workflows based on their application's specific needs for speed versus strict ordering.

Highlights

• New Documentation for Transaction Submission Modes: Introduces detailed documentation for three transaction submission modes (Default, Queued, and Parallel) for Celestia light nodes, explaining their configuration, behavior, and use cases.
• Queued Transaction Submission: Describes the 'Queued mode' (TxWorkerAccounts = 1) which ensures synchronous, ordered transaction submission, preventing sequence conflicts at the cost of throughput (~1 transaction per block).
• Parallel Transaction Submission: Explains the 'Parallel mode' (TxWorkerAccounts > 1) which enables high-throughput, unordered transaction submission by utilizing multiple subaccounts as parallel lanes, significantly increasing transactions per block.
• Configuration via TxWorkerAccounts: Details how to configure these modes by setting the TxWorkerAccounts parameter in the light node's config.toml file, including step-by-step instructions for each mode.

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 significantly improves the documentation by adding a detailed section on queued and parallel transaction submission modes for light nodes. The new content is well-structured, clear, and provides useful examples and a comparison table. I've found one minor inconsistency in the throughput description for the queued mode, which I've commented on. Overall, this is a great addition to the documentation.

[gemini-code-assist]

There appears to be an inconsistency in the documentation for the throughput of Queued mode. This line states it's 'approximately 1 PayForBlobs transaction every other block', but the comparison table on line 162 indicates a throughput of '~1 tx per block'. To ensure consistency and avoid confusion, I recommend aligning this description with the table.

- Throughput: approximately 1 PayForBlobs transaction per block