The transaction proposal process does not provide signers with a clear and human-readable representation of the transaction calldata. Instead, signers must approve transactions based solely on raw byte data stored in the transaction payload, which obscures the actual function call and parameters being executed.
Likelihood: High
Every transaction stores bytes.
Impact: High
This ambiguity increases the risk of signers unknowingly approving malicious or unintended transactions, potentially resulting in unauthorized fund transfers, state changes, or contract interactions.
Enhance the transaction proposal workflow by including a mechanism to decode and present calldata in a human-readable format to signers prior to confirmation. This can be implemented by:
Integrating the contract's ABI to decode function signatures and parameters, enabling clear display of the intended action.
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.