The CollateralDeposited event only logs the user address and amount, but omits the crucial token address.
Since the protocol supports multiple collateral types (WETH and WBTC), off-chain systems and indexers cannot distinguish which token was deposited without parsing transaction input data. This makes tracking deposits by token type impossible using events alone.
Likelihood: High
Reason 1 // Every deposit is affected
Reason 2 // Standard practice to include all relevant data
Impact: Medium
Impact 1 // Off-chain indexers cannot track deposits by token
Impact 2 // Analytics dashboards are incomplete
Impact 3 // Debugging and auditing made difficult
The following demonstrates that events from WETH and WBTC deposits are indistinguishable. Any off-chain system relying on events alone cannot determine which collateral type was deposited.
Add the token address to the event to enable proper off-chain tracking. This is standard practice for protocols supporting multiple token types and is essential for proper indexing.
The contest is live. Earn rewards by submitting a finding.
Submissions are being reviewed by our AI judge. Results will be available in a few minutes.
View all submissionsThe contest is complete and the rewards are being distributed.