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
As pointed out by @giansalex in gon-evidence#245, an NFT under a Class with a ClassId that contains the IBC separator / cannot be transferred back to its original chain.
This is because types.ParseClassTrace() assumes that there is no slash in the base ClassId. As a result, it processes p/0/1 as the path p/0 and the base ClassId 1.
To address this issue, we could:
either modify the spec and separate the ClassId field into ClassTrace and BaseClassId fields, and distinguish them without relying on a single slash.
or restrict the use of slashes in ClassId.
The text was updated successfully, but these errors were encountered:
As pointed out by @giansalex in gon-evidence#245, an NFT under a Class with a ClassId that contains the IBC separator / cannot be transferred back to its original chain.
This is because
types.ParseClassTrace()
assumes that there is no slash in the base ClassId. As a result, it processesp/0/1
as the pathp/0
and the base ClassId1
.To address this issue, we could:
ClassId
field intoClassTrace
andBaseClassId
fields, and distinguish them without relying on a single slash.The text was updated successfully, but these errors were encountered: