You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Gate identity-based exclusion for rotating quorum members #8134
A rotating quorum can contain the same masternode identity more than once, even after short-quarter snapshot reconstruction is corrected. In src/llmq/utils.cpp, a historical property conflict can make AddMN reject a retained member from an exclusion list. If that identity later has a different address, the current candidate may pass HasMN and be selected again. An assembled quorum can then contain duplicate member positions, such as [A, B, A].
Follow-up
Design and implement identity-based exclusion for rotating quorum selection independently of the historical property-based CDeterministicMNList::AddMN bookkeeping. This changes consensus selection even when all quarters fill, so activate the new behavior through an appropriate consensus deployment and preserve historical behavior before activation. Define how the transition handles the three retained quarters, snapshots, member caches, and any resulting shortage of eligible members.
Acceptance criteria
Add a regression test for a retained identity omitted from the exclusion list because of a historical property conflict, followed by selection of the same proTxHash with a different address. Check the assembled quorum for duplicate identities.
Verify the activated rules prevent the duplicate selection and produce deterministic quarter reconstruction, including at the activation boundary.
Verify pre-activation selection and historical snapshot replay remain unchanged. Include a full-quarter case as well as a shortage case.
Document the activation and compatibility implications for nodes and clients that rebuild rotating quorums.
Activity
UdjinM6 commentedon Nov 12, 2026
Related: #8012