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
What is the current behavior and expected behavior?
We are experiencing weird behaviour when using the pallet-asset-tx-payment pallet. When supplying the signAsync function with the payload of assetId above zero it multiplies by 2^24. So essentially after signing the transaction the assetId is changed to be multiplied by 2^24.
The same issue is currently on the asset-hub (aka statemint), so not just on our side.
The expected behaviour is obviously that the assetId stays the same after signing.
What is the motivation for changing the behavior?
It seems like there is a type conversion in any way. It could be decoding, encoding, compacting etc...
Please tell us about your environment:
Version:
Environment:
Node.js
Browser
Other (limited support for other environments)
Language:
JavaScript
TypeScript (include tsc --version)
Other
The text was updated successfully, but these errors were encountered:
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.
We are experiencing weird behaviour when using the
pallet-asset-tx-payment
pallet. When supplying thesignAsync
function with the payload ofassetId
above zero it multiplies by2^24
. So essentially after signing the transaction theassetId
is changed to be multiplied by2^24
.The same issue is currently on the asset-hub (aka statemint), so not just on our side.
The expected behaviour is obviously that the
assetId
stays the same after signing.It seems like there is a type conversion in any way. It could be decoding, encoding, compacting etc...
Version:
Environment:
Language:
The text was updated successfully, but these errors were encountered: