IBC-go antedecorator effect on Hermes operation #1228
Labels
I: dependencies
Internal: related to dependencies
I: logic
Internal: related to the relaying logic
O: new-feature
Objective: cause to add a new feature or support
Milestone
Crate
ibc-relayer
Summary
There is a new feature that the IBC-go team implemented consisting of a
CheckTx
decoratorwhich has intuitively the following side-effects:
previously, then the decorator prevents the transaction from entering the mempool and
rejects it before that.
the redundant messages are accepted as no-op, while the novel messages execute as usual.
Resources:
Problem Definition
The basic problem is that we don't know yet how this feature affects Hermes.
Point 1 has the positive side-effect that it will prevent some situations where Hermes wastes fees in the presence of competitive relayers.
Point 2 has the benefit that Hermes (and other relayers) can now adopt a strategy of minimizing the number of messages they put in a tx, so that they minimize wasting gas fees.
Proposal
We need to make sure that Hermes correctly interprets the
broadcast_tx_sync
response in situation (1) and correctly drops the operational data (since that consists of redundant messages).We also need to make sure we retain backwards compatibility, because some node may not have the antedecorator enabled (or using an older version).
Acceptance Criteria
For Admin Use
The text was updated successfully, but these errors were encountered: