Root + Impact

Description

The CollateralDeposited event logs only the user and the amount — it does not record which collateral token was deposited. In a two-collateral system (WETH and WBTC) there is no way to tell from the event whether a deposit was WETH or WBTC. The sibling event CollateralRedeemed does include the token, so this is also inconsistent.

Compare with the redeem event, which logs the token:

Risk

Likelihood: High — every single deposit emits this event, so the missing field affects all deposits.

Impact: Low — no funds are at risk, but off-chain indexers, dashboards, and monitoring cannot attribute deposits to a collateral type, and deposit/withdraw accounting cannot be reconciled from events alone.

Proof of Concept

Depositing WETH and depositing WBTC emit byte-identical events (same user, same amount, no token field), so an observer cannot distinguish them. This is visible by inspection of the event definition and the _deposit_collateral log line:

Recommended Mitigation

Add the token address to the event, matching CollateralRedeemed.