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
With hermes v1.0.0-rc0, when using the tx raw ft-transfer command to send IBC tokens from one chain to another:
The --receiver parameter address seems to be ignored.
The funds are actually sent to the wallet used by hermes to relay, meaning the address of the wallet specified by the key_name parameter in hermes config.
Note that this has been tested on the rc-0 version of the v1 release. We know the version is not supposed to be stable. We still decided to report the bug since it was quite concerning and we could not find any mention of it elsewhere.
romac
changed the title
tx raw ft-transfer use wrong destination address with hermes v1.0.0-rc0tx raw ft-transfer use wrong destination address with hermes v1.0.0-rc0
Jul 14, 2022
Summary of Bug
With hermes
v1.0.0-rc0
, when using thetx raw ft-transfer
command to send IBC tokens from one chain to another:key_name
parameter in hermes config.Note that this has been tested on the rc-0 version of the v1 release. We know the version is not supposed to be stable. We still decided to report the bug since it was quite concerning and we could not find any mention of it elsewhere.
Version
v1.0.0-rc.0
Steps to Reproduce
We send xki tokens from osmos testnet to kichain testnet. The receiver address should be
tki1aygsj8q29lsygpt8m6mse4hch69m32kzygh5rr
The resulting transaction is 32119B54EF0F29E9D23F94D11C2C503F8117DB94DC9808B910ACAC620CEAB4E8
We can see that the receiver is actually
tki16klm67dla3cnv7k2889cyprnt62s4uy8rjpkj9
and nottki1aygsj8q29lsygpt8m6mse4hch69m32kzygh5rr
.tki16klm67dla3cnv7k2889cyprnt62s4uy8rjpkj9
is actually the address behing hermeskey_name
wallet.For reference, here is hermes configuration:
Acceptance Criteria
The IBC transaction fund are sent to the address specified by
--receiver
argument and not the address used by hermes for relaying.For Admin Use
The text was updated successfully, but these errors were encountered: