The proposeTransaction function is meant to enable the initiation of new transactions in the multi-signature workflow, with the project description stating that any signer holding the SIGNING_ROLE can propose, tying permission to the role for decentralized participation.
However, the function is gated by the onlyOwner modifier, restricting proposals exclusively to the contract owner and preventing other signers from initiating transactions, which deviates from the intended design and introduces a centralized bottleneck.
Likelihood:
During normal operations in a team setting where non-owner signers attempt to initiate transactions as per the documented role permissions.
In scenarios where the owner is offline, compromised, or uncooperative, blocking all new proposals from proceeding.
Impact:
Operational bottlenecks that prevent timely transaction initiations, leading to delays in fund movements or governance actions in time-sensitive situations.
Undermines the multi-signature model's decentralized intent, creating a single-point failure that could result in indirect financial losses from missed opportunities or stalled protocols.
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.
The contest is complete and the rewards are being distributed.