-
Notifications
You must be signed in to change notification settings - Fork 2
[Experiment]: network commits #162
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: alex/val_net_val_sig
Are you sure you want to change the base?
Conversation
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this 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 @alpe, 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 introduces an experimental network
module designed to manage validator attestations and epoch-based soft confirmation of blocks. It significantly refactors the core Adapter
component to support a flexible block event publishing mechanism, allowing events to be conditionally released based on the network
module's soft confirmation status. This change aims to lay the groundwork for more advanced consensus and finality features by enabling a "soft finality" layer where blocks are only considered fully confirmed after a certain validator quorum has attested to them.
Highlights
- New
network
module: A new Cosmos SDK module is introduced to manage validator attestations, epoch transitions, and soft confirmation of blocks. - Soft Confirmation Mechanism: Implemented a new "soft confirmation" logic in the
Adapter
that queues block commit events and only publishes them when a configurable condition (e.g., quorum from thenetwork
module) is met. - Adapter Refactoring: The
Adapter
's constructor is refactored to use functional options, improving configurability for metrics and block filtering. - CLI and gRPC Interfaces: The new
network
module exposes comprehensive CLI and gRPC query and transaction interfaces for interacting with its state and functionality.
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 is currently in preview and 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 to provide feedback.
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
-
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. ↩
return k.CommitSignatures.Has(ctx, collections.Join(height, validatorAddr)) | ||
} | ||
|
||
func (k Keeper) GetCommits(ctx sdk.Context, height int64) (*cmttypes.Commit, error) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This returns all the commits for a height, if it is the end of an epoch.
This method does also not take into account if consensus was reached !
There was a problem hiding this 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 introduces significant improvements to how validator signatures are stored and retrieved, moving from raw byte storage to structured CometBFT CommitSig
protobuf messages. This enhances type safety and aligns better with the underlying CometBFT data structures. The changes include updates to the Keeper
and MsgServer
logic, as well as corresponding test cases. Overall, the changes are well-implemented and improve the robustness of the network module. There are a few minor areas for improvement related to code clarity and potential correctness considerations for signature ordering.
}, | ||
Signatures: make([]cmttypes.CommitSig, 0), | ||
} | ||
// add the signatures (unordered) // todo (Alex): do we need them ordered? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The todo (Alex): do we need them ordered?
comment highlights a potential correctness issue. If the order of cmttypes.CommitSig
within cmttypes.Commit.Signatures
is significant for CometBFT's validation or other processes, relying on collections.Walk
might be problematic as it does not guarantee iteration order. This should be thoroughly investigated and addressed if ordering is indeed required.
// add the signatures (unordered) // todo (Alex): do we need them ordered? | |
// add the signatures (unordered) // TODO: Clarify if signature order is required for cmttypes.Commit and adjust if necessary. |
61cd975
to
f48ac21
Compare
🚧 Experimental - sharing code only