Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Signing multiplies assetId by 2^24 #5713

Closed
3 of 10 tasks
Chralt98 opened this issue Aug 25, 2023 · 3 comments
Closed
3 of 10 tasks

Signing multiplies assetId by 2^24 #5713

Chralt98 opened this issue Aug 25, 2023 · 3 comments

Comments

@Chralt98
Copy link

Chralt98 commented Aug 25, 2023

  • I'm submitting a ...
  • Bug report
  • Feature request
  • Support request
  • Other
  • 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
@IkerAlus
Copy link

I think this is related to (or same issue as): #5710

@Chralt98
Copy link
Author

Oh yeah thanks. It's indeed the same issue. Let me close this issue.

@polkadot-js-bot
Copy link

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.

@polkadot-js polkadot-js locked as resolved and limited conversation to collaborators Sep 1, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants