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
There's currently a field on the TransactionPlannerRequest proto called ibc_actions:
Counterintuitively, this field does not accept an Ics20Withdrawal, but rather applies specifically to actions related to relaying, not transaction planning. Let's rename the field to something like ibc_relay_actions and the corresponding type IbcRelay.
Counterintuitively, this field does not accept an Ics20Withdrawal, but rather applies specifically to actions related to relaying, not transaction planning.
It would definitely be more clear if this were called ibc_relay_actions, but it's not the case that this isn't related to transaction planning. Rather, it's for planning transactions that relay IBC packets -- once we have nonzero gas prices, IBC relaying will require planning, so that the transaction can pay fees for the relayed data.
There's currently a field on the TransactionPlannerRequest proto called
ibc_actions
:Counterintuitively, this field does not accept an Ics20Withdrawal, but rather applies specifically to actions related to relaying, not transaction planning. Let's rename the field to something like
ibc_relay_actions
and the corresponding typeIbcRelay
.See related discussion in #3108.
The text was updated successfully, but these errors were encountered: