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
I believe this is worth doing since this is the ultimate information that relayers care about. Not the individual increments that are occurring with each escrow.
I expect that most relayers will want to query to find the final balance anyway, so I think we can avoid this by emitting final balances.
The only wrinkle I foresee is a future where the relayer list is non-empty and certain fees are only meant for certain relayers.
In that case, I still think it is worth emitting the cumulative fees intended for permissionless relays (no relayer restriction). And relayers that do have specific fees for them can query the chain to find their alotted fee which will be gte the cumulative permissionless fee. Either way, I think we can solve that UX concern when it arises. For now, we should optimize our current UX which would mean emitting the cumulative fee on each escrow
EmitIncentivizedPacket
should emit cumulative fees on a packet.The text was updated successfully, but these errors were encountered: