[LLMQ] Use a 20 member quorum for testnet - #2984
Open
Liquid369 wants to merge 1 commit into
Open
Conversation
LLMQ_50_60 needs 40 valid members, and the testnet fleet is about 40 nodes, so every DKG has to enlist every masternode and a single absent node kills the session. Membership never changes either, since the quorum is as large as the set it is drawn from. A 20 member quorum sits well under the fleet size: members are re-drawn each DKG interval so quorums actually rotate, and 4 nodes can be offline without stalling chainlocks. Add LLMQ_20_60 instead of resizing llmq50_60, which mainnet still uses.
Duddino
approved these changes
Aug 27, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Testnet chainlocks are on LLMQ_50_60, which needs 40 valid members. The testnet
fleet is around 40 masternodes, so every DKG has to enlist all of them, and one
node being offline is enough to kill the session. Membership never changes
either, since the quorum is the same size as the set it gets drawn from.
This adds LLMQ_20_60 with 20 members, a minimum of 16 and a threshold of 12,
keeping the same ratios the 50 member set uses, and points testnet chainlocks
at it. DKG interval, phase blocks and mining window are unchanged so the timing
stays the same.
With 40 masternodes, a 20 member quorum gets redrawn from the full list every
interval, so quorums actually rotate, and we can have 4 nodes offline without
stalling chainlocks.