Signature Mapping Not Cleared After Execution
After a transaction is executed, the s_signatures mapping still retains the confirmation data. This wastes storage gas and could potentially cause confusion in transaction analysis. While it doesn't directly enable attacks due to the executed flag check, it represents poor state management and unnecessary gas costs for storage.
Likelihood:
After executing transaction ID 0, s_signatures[0][signerAddress] still returns true for all signers who confirmed, wasting storage slots permanently.
Impact:
Unnecessary storage costs and potential for state analysis confusion. Each confirmation stored costs approximately 20,000 gas that could be refunded if cleared.
Clear signature mappings after execution to refund gas:
Clear signature mappings after execution to refund gas:
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.