Closed immrsd closed 1 week ago
Attention: Patch coverage is 95.70552%
with 7 lines
in your changes missing coverage. Please review.
Project coverage is 92.02%. Comparing base (
02c9ce6
) to head (a7c569e
). Report is 5 commits behind head on main.
Files with missing lines | Patch % | Lines |
---|---|---|
packages/governance/src/multisig/multisig.cairo | 96.47% | 5 Missing :warning: |
...ckages/governance/src/multisig/storage_utils.cairo | 85.71% | 2 Missing :warning: |
Also, if a signer is removed, should pending transactions be canceled since the signers that may have confirmed may have been the removed ones, and the confirmations of the transaction are not decreased while the quorum may have been? cc @andrew-fleming.
Also, if a signer is removed, should pending transactions be canceled since the signers that may have confirmed may have been the removed ones, and the confirmations of the transaction are not decreased while the quorum may have been? cc @andrew-fleming.
That may be an issue indeed, good call. To my mind, introducing a new tx Canceled
state and keeping track of all pending txs would overcomplicate the implementation and make it more error-prone. I addressed this issue by making confirmations
a computable property that's not stored in the storage. It's calculated by iterating through all current signers and checking if a signer has confirmed the tx.
Only execute
function becomes a bit more expensive in terms of computation, but it also removes storage variable for tracking number of confirmations and the necessity to update it in the confirm_transaction
and revoke_confirmation
functions
Fixed #21