You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Relayer operators should be able to specify packet filter to only relay incentivized packets with certain minimum fee. Depending on the type of relaying, the relayer needs to filter based on either the receive fee, ack fee, or timeout fee fields.
A complication is that if packet fee is added afterward through MsgPayPacketFeeAsync, the relayer needs to re-filter the relevant packet and perform relaying if the packet now contains sufficient fee. Implementation needs to be cautious of duplicate relaying of the same packet caused by the trigger from MsgPayPacketFeeAsync.
We may want to make use of new GRPC APIs such as IncentivizedPacketsForChannel. The relayer should also listen to new event types like EventTypeIncentivizedPacket so that it can detect packets with new fee added via MsgPayPacketFeeAsync.
Acceptance Criteria
When the relayer is started with custom fee packet filter, packets without fees or packets with insufficient fees should not get relayed. If fees are added to the packet afterward with MsgPayPacketFeeAsync, then the packet should be relayed by the relayer.
For Admin Use
Not duplicate issue
Appropriate labels applied
Appropriate milestone (priority) applied
Appropriate contributors tagged
Contributor assigned/self-assigned
The text was updated successfully, but these errors were encountered:
Summary
Relayer operators should be able to specify packet filter to only relay incentivized packets with certain minimum fee. Depending on the type of relaying, the relayer needs to filter based on either the receive fee, ack fee, or timeout fee fields.
A complication is that if packet fee is added afterward through
MsgPayPacketFeeAsync
, the relayer needs to re-filter the relevant packet and perform relaying if the packet now contains sufficient fee. Implementation needs to be cautious of duplicate relaying of the same packet caused by the trigger fromMsgPayPacketFeeAsync
.We may want to make use of new GRPC APIs such as
IncentivizedPacketsForChannel
. The relayer should also listen to new event types likeEventTypeIncentivizedPacket
so that it can detect packets with new fee added viaMsgPayPacketFeeAsync
.Acceptance Criteria
When the relayer is started with custom fee packet filter, packets without fees or packets with insufficient fees should not get relayed. If fees are added to the packet afterward with
MsgPayPacketFeeAsync
, then the packet should be relayed by the relayer.For Admin Use
The text was updated successfully, but these errors were encountered: