Skip to content

LLMQ: Bound signature share verification batches - #1936

Open
navidR wants to merge 1 commit into
firoorg:masterfrom
navidR:dev/navidr/bounded-sig-share-verification
Open

LLMQ: Bound signature share verification batches#1936
navidR wants to merge 1 commit into
firoorg:masterfrom
navidR:dev/navidr/bounded-sig-share-verification

Conversation

@navidR

@navidR navidR commented Aug 30, 2026

Copy link
Copy Markdown
Contributor

Limit verification batches by the actual number of signature shares rather than the number of sessions. Add coverage for bounded, complete draining of a large session.

Upstream: Dash PR #7415.

@coderabbitai

coderabbitai Bot commented Aug 30, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

Next included review available in 59 minutes.

View limit details

Limit details: You’ve used all 4 included reviews currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: d24dec54-c49e-4ccc-8fbb-78c748478ede

📥 Commits

Reviewing files that changed from the base of the PR and between 4f0c771 and 8366cc7.

📒 Files selected for processing (4)
  • src/llmq/quorums_signing_shares.cpp
  • src/llmq/quorums_signing_shares.h
  • src/test/CMakeLists.txt
  • src/test/quorums_signing_share_tests.cpp

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Aug 30, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-08-30T14:57:31.408564Z 8366cc7 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@codeant-ai

codeant-ai Bot commented Aug 30, 2026

Copy link
Copy Markdown

🤖 CodeAnt AI — Review Status

Status Commit Started (UTC) Finished (UTC)
✅ Reviewed your PR 8366cc7 Aug 30, 2026 · 14:56 14:59

@codeant-ai

codeant-ai Bot commented Aug 30, 2026

Copy link
Copy Markdown

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

@codeant-ai codeant-ai Bot added the size:L This PR changes 100-499 lines, ignoring generated files label Aug 30, 2026
@codeant-ai

codeant-ai Bot commented Aug 30, 2026

Copy link
Copy Markdown

User description

Limit verification batches by the actual number of signature shares rather than the number of sessions. Add coverage for bounded, complete draining of a large session.


CodeAnt-AI Description

Bound signature-share verification batches by the number of shares

What Changed

  • Verification now processes at most the configured number of actual signature shares, even when many shares belong to one session.
  • Pending shares continue draining in bounded batches until all shares are processed.
  • Added coverage for large sessions to confirm batches stay within the limit and no shares are skipped.

Impact

✅ Lower verification workload per batch
✅ Fewer expensive per-share verification fallbacks
✅ Complete processing of large signature-share queues

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

@codeant-ai

codeant-ai Bot commented Aug 30, 2026

Copy link
Copy Markdown

CodeAnt Nitpicks

1 code suggestion

1. Duplicate pending shares do not increment sharesAdded, so many duplicates can be scanned and erased while holding cs, making collection unbounded despite maxShares.

Performance · src/llmq/quorums_signing_shares.cpp:614-619

@reubenyap reubenyap left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I traced the new share-count bound through collection and verification, including already-known shares, banned peers, randomized peer iteration, quorum lookup, and subsequent queue draining. Only admitted shares increment the counter, and the continuation condition prevents a verification batch from exceeding 32 actual shares. The focused regression coverage and full CI matrix are green; I found no actionable defect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:L This PR changes 100-499 lines, ignoring generated files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants