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
Hey, I just wanted to start a tracking issue for the problem with the stride airdrop. Can we try and centralize all of the information about the issue here?
The problem exists in IBC 7+ and is solved in 7.2
The problem is that all transactions that do not use sign mode direct will fail. This means that ledger devices will fail to transact correctly if using IBC 7.1, and that any transaction mode other than sign mode direct but will fail on 7.0 to 7.1.
to avoid this problem, teams should make sure to be on 7.2 and higher
The problem itself was disabling legacy message types that were needed to accomplish transfers between chains using IBC 7 and higher and chains on IBC 1 through 6
Today, IBC 7.2 was released, and it has support for the legacy message types.
I suppose that the correct resolution to this issue is for chains that are using IBC7 and higher to upgrade to 7.2, and for chains that do not, to work on upgrading.
The text was updated successfully, but these errors were encountered:
faddat
changed the title
IBC v7 issue (stride related)
IBC v7 issue
Jun 23, 2023
Hey, I just wanted to start a tracking issue for the problem with the stride airdrop. Can we try and centralize all of the information about the issue here?
The problem exists in IBC 7+ and is solved in 7.2
The problem is that all transactions that do not use sign mode direct will fail. This means that ledger devices will fail to transact correctly if using IBC 7.1, and that any transaction mode other than sign mode direct but will fail on 7.0 to 7.1.
to avoid this problem, teams should make sure to be on 7.2 and higher
The problem itself was disabling legacy message types that were needed to accomplish transfers between chains using IBC 7 and higher and chains on IBC 1 through 6
Osmosis has made a front end patch:
Today, IBC 7.2 was released, and it has support for the legacy message types.
I suppose that the correct resolution to this issue is for chains that are using IBC7 and higher to upgrade to 7.2, and for chains that do not, to work on upgrading.
The text was updated successfully, but these errors were encountered: