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
When I forward ibc transfer tx to osmosis via cosmoshub, if the amount is greater than the maximum value of int64, the estimated will fail, this problem exists in both mainnet and testnet
Before the v4.0.6 of packet-forward-middleware, if ibc transfer amount was greater than the maximum value of int64, the conversion would overflow, causing the code to panic, and tx would fail
Send ibc transfer tx to chainA(Any chain with which cosmoshub has created an ibc channel), receiver is cosmoshub, amount must be greater than maximum value of int64, and fill tx memo with forward data (for example, forward to osmosis/evmos/kava)
For Admin Use
Not duplicate issue
Appropriate labels applied
Appropriate contributors tagged
Contributor assigned/self-assigned
Is a spike necessary to map out how the issue should be approached?
The text was updated successfully, but these errors were encountered:
This issue should have been addressed in v4.0.6 of the packet forward middleware, it looks like Gaia is still using v4.0.5. I suspect that an upgrade to the patched version is all that is necessary to rectify the issue.
Summary of Bug
When I forward ibc transfer tx to osmosis via cosmoshub, if the amount is greater than the maximum value of int64, the estimated will fail, this problem exists in both mainnet and testnet
Before the v4.0.6 of packet-forward-middleware, if ibc transfer amount was greater than the maximum value of int64, the conversion would overflow, causing the code to panic, and tx would fail
Related issues:
gaia #2553
packet-forward-middleware #78
Version
gaia: v10.0.2(Latest)
gaia: v11.0.0(Pre-release)
Steps to Reproduce
Send ibc transfer tx to chainA(Any chain with which cosmoshub has created an ibc channel), receiver is cosmoshub, amount must be greater than maximum value of int64, and fill tx memo with forward data (for example, forward to osmosis/evmos/kava)
For Admin Use
The text was updated successfully, but these errors were encountered: