Add Sender
to fungible_token_packet
events
#996
Labels
20-transfer
type: refactor
Architecture, code or CI improvements that may or may not tackle technical debt.
Milestone
Summary
When creating the
fungible_token_packet
events, we have access to the sender information. It would be a small win to add thesender
field so those events can be tracked accurately.Problem Definition
When a packet is received, or acknowledged, the data object contains the sender value, but is not included in the
fungible_token_packet
event emission. When Smart Contracts are used to perform IBC actions, clients (ie, explorers) would use the events emitted to track IBC movement. Without the sender field, its impossible to match a transfer to acknowledgement, or recvPacket to acknowledgement.Proposal
Update usages of https://github.com/cosmos/ibc-go/blob/v2.0.3/modules/apps/transfer/types/events.go#L6 to include sender as an event attribute.
For Admin Use
The text was updated successfully, but these errors were encountered: