If the rate limit is exceeded or the denom is blacklisted, we emit an event.

NewMsgServerImpl returns an implementation of the ratelimit MsgServer interface.

Parse the denom from the Recv Packet that will be used by the rate limit module The denom that the rate limiter will use for a RECEIVE packet depends on whether it was a source or sink Sink: The token moves forward, to a chain different than its previous hop The new port and channel are APPENDED to the denom trace.

Parse the denom from the Send Packet that will be used by the rate limit module The denom that the rate limiter will use for a SEND packet depends on whether it was a NATIVE token (e.g.

Parses the sender and channelId and denom for the corresponding RateLimit object, and the sender/receiver/transfer amount The Stride channelID should always be used as the key for the RateLimit object (not the counterparty channelID) For a SEND packet, the Stride channelID is the SOURCE channel For a RECEIVE packet, the Stride channelID is the DESTINATION channel The Source and Desination are defined from the perspective of a packet recipient Meaning, when a send packet lands on a the host chain, the "Source" will be the Stride Channel, and the "Destination" will be the Host Channel And, when a receive packet lands on a Stride, the "Source" will be the host zone's channel, and the "Destination" will be the Stride Channel.