Polkadot.js UI Bug When Initiating A Parathread for Parachain Auction

[xcavate2022]

While trying to secure a Parathread (to start a Parachain Auction) using the Polkadot.js we found a UI bug which meant the reserve amount was incorrect, which cost us 408.45 DOT in fees.

ParaID 3376 Controller Account 1xGrVAzbHfUfxFMRhUsDKWFcJNf1XMSNE2UqRjkYyFhrnqt

2024-05-30 13:56:24 (+UTC)

136.1501892767 DOT

0x3cf6660a1c8b471d0841a53d8261d34d8f96be57e64891eee2c8b0b8c9f4f001

2024-05-30 14:08:30 (+UTC)

136.1501892767 DOT

0xf6fcb1c2a75f4d7029bfe5619a79c177545b33272be83c12a5443811fe54f09a

2024-05-30 14:55:24 (+UTC)

136.1501892767 DOT

0xf64028ab688a24b660230eb1f112e743543d22086c7625da86278e358b3b06ec

[SBalaguer]

This might be related to polkadot-sdk #3020. The logic for charging for a wasm registration is no longer depending on the size of the wasm, but rather on the max possible wasm size to register.

[xcavate2022]

Hi SBalagar, Yes it is but the Polkadot.js UI shows the incorrect amount relative to the size of the WASM & Genesis block files. Ours said we needed 1462 DOT, so we allowed for 1711 DOT in the Controller wallet address. The transaction failed for the third time because (we then went in and analaysed the function, which calculates the amount expected) it expected nearer to 3200 DOT. Crust had the same issue on the same Auction 71. I know this reserve is there to stop a perseved attack vector. I just don't want other teams having this issue as the process is stressful enough. If the UI is correct at least you know how much you need in your wallet and can make the correct judgement whether to go for it or not. Cheers Richard

[TarikGul]

So this is not a Polkadot-js UI issue but an Apps issue: I think related to: polkadot-js/apps#10655

The UI library is strictly UI components not chain based logic.

Closing as we should take these issues to apps, and build on the related issues linked above.

[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.