-
Notifications
You must be signed in to change notification settings - Fork 3.9k
[qs] Populate BatchKind for BatchV2 #18452
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
Merged
Merged
+506
−36
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Jan 15, 2026
Draft
Contributor
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
This was referenced Jan 15, 2026
8066269 to
f9f72c8
Compare
aea0d98 to
b94c8a8
Compare
danielxiangzl
approved these changes
Jan 16, 2026
b94c8a8 to
c8fe203
Compare
f9f72c8 to
8f474b1
Compare
20044f2 to
93e5285
Compare
8f474b1 to
4a7cef3
Compare
JoshLind
approved these changes
Jan 20, 2026
| if !pulled_txns.is_empty() && max_batches_remaining > 0 { | ||
| self.push_bucket_to_batches( | ||
| // Process each batch kind group. Processing order: Normal first, then others. | ||
| // This ensures backwards compatibility and prioritizes regular transactions. |
Contributor
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.
Interesting... I wonder if we ever want to do the opposite, i.e., prioritize encrypted transactions? But, a question for another day 😄
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Contributor
✅ Forge suite
|
Contributor
✅ Forge suite
|
Contributor
✅ Forge suite
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

Description
This PR adds support for categorizing transactions into different batch kinds, specifically separating encrypted transactions from normal ones in the QuorumStore batch generation process. The implementation enables the batch generator to create separate batches for encrypted and normal transactions, ensuring they are processed appropriately.
Key changes:
batch_kind()method to theTBatchInfotrait to identify batch typesBatchGeneratorto separate encrypted and normal transactions