msg.sender within event DepositForBurn can be misleading #65
Description
Request: Add tx.origin to DepositForBurn event for more transparency
Currently, the DepositForBurn event only emits msg.sender as the depositor. When a user initiates a transaction on a third party protocol, that protocol burn tokens on behalf of users (DEX aggregators, DeFi protocols, etc.), this shows the protocol address but not the end user.
Suggestion: Add tx.origin as an additional field like originalSender or initiator to provide more transparency about who ultimately initiated the cross-chain transfer.