Potentially incorrect calculation of the "reserved deposit" for registering a parachain state and code to use coretime

[ltfschoen]

• Bug report
• Feature request
• Support request
• Other

• What is the current behavior and expected behavior?

When you Register Parachain State and Code the Polkadot-JS Apps UI incorrectly calculates the "reserved deposit" as mentioned here
https://substrate.stackexchange.com/questions/11588/how-to-calculate-required-reserved-deposit-to-register-a-parachain-on-kusama-w, which causes the user to experience an error, and then they have to manually try and calculate what reserved deposit they need, which could prevent them from knowing how much KSM they need to register a parachain to use their coretime, which is supposed to be a priority in 2024.

• What is the motivation for changing the behavior?

The Polkadot-JS Apps UI currently appears to incorrectly calculate the "reserved deposit" amount that is necessary for users that wants to register their parachain to use coretime, and then gives them a message indicating that they don't have an adequate balance, even if they actually do have a larger transferable balance than the amount they are led to believe they need for the "reserved deposit" amount.

• Please tell us about your environment:

  • Version:
    Parity Polkadot v1.12.0
    api v11.1.1
    apps v0.138.2-9

  • Environment:

    • Browser - Brave Version 1.66.110 Chromium: 125.0.6422.60 (Official Build) (arm64)

[TarikGul]

I think this is rel: #9988

[TarikGul]

Completed via #10671

[polkadot-js-bot]

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.