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
Fix two potential issues in the way pending islocks are processed (dashpay#3678)
* Always check for previous quorum set in llmq IS
* Refactor SelectQuorumForSigning and related code
Should have no changes in behaviour
* Do not use SIGN_HEIGHT_OFFSET when checking pending IS locks, use actual chain tip
This commit actually changes the behaviour
// This might end up giving different results on different members
774
768
// This might happen when we are on the brink of confirming a new quorum
775
769
// This gives a slight risk of not getting enough shares to recover a signature
776
770
// But at least it shouldn't be possible to get conflicting recovered signatures
777
771
// TODO fix this by re-signing when the next block arrives, but only when that block results in a change of the quorum list and no recovered signature has been created in the mean time
778
-
CQuorumCPtr quorum = SelectQuorumForSigning(llmqType, tipHeight, id);
772
+
CQuorumCPtr quorum = SelectQuorumForSigning(llmqType, id);
0 commit comments