polkadot-js / apps

Basic Polkadot/Substrate UI for interacting with a Polkadot and Substrate node. This is the main user-facing application, allowing access to all features available on Substrate chains.
https://dotapps.io
Apache License 2.0
1.75k stars 1.55k forks source link

Kusama accounts showing incorrect amount of KSM #10907

Closed laboon closed 2 months ago

laboon commented 2 months ago

I have tried this on several different endpoints and get the same result. It appears to only happen on Kusama, not Polkadot.

The majority (surprisingly, not all) of my accounts are showing much more KSM than I actually have. Specifically it is showing 1000x as much which makes me think this is a decimal placement issue. For example, this account has 0.509 KSM ( https://kusama.subscan.io/account/J9eWsRZZMJRKzfNjvq77PxoiBj5W7mZzyegBSxTf6PyYbJ7 ). However, Polkadot-JS App shows it having 509.5167 KSM.

Screenshot 2024-09-10 at 15 10 35
laboon commented 2 months ago

All elements (e.g. transferrable, locked for referenda, etc.) also show up as 1000x the amount but the tooltip shows the correct amount. Screenshot 2024-09-10 at 15 13 47 Screenshot 2024-09-10 at 15 13 51

TarikGul commented 2 months ago

Thanks for reporting this, I will check this today. I'll try and confirm this with my KSM accounts in a second. Are you using the IPFS version or polkadot js org version?

laboon commented 2 months ago

@TarikGul Thanks for looking into it so quickly. I am using the polkadot js org version.

Radha has checked and it is the same issue for him - some accounts show normally, others show as 1000x.

TarikGul commented 2 months ago

Okay I can confirm it is doing the same thing for me!

I will get this fixed shortly!

michalisFr commented 2 months ago

Another case is where transferable and total is correct, but locked is 1000x (although the tooltip shows the correct 0.2 KSM)

Screenshot 2024-09-10 at 4 42 54 PM
TarikGul commented 2 months ago

Yea I just found the source of the issue!

polkadot-js-bot commented 2 months ago

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.