Incorrect Fee Calculation for hydration to Astar ASTR Transfer via xcmPaymentApi

[snoopy1412]

Description:

Hello ,

I would like to report a potential bug related to the fee calculation when transferring ASTR from ydration to Astar using xcmPaymentApi.

Issue Details:

When I perform a transfer of ASTR from hydration to Astar, the fee returned is:

{ "ok": "0x0000000000000000055946e6fec8a799" }

Converting this hexadecimal value to decimal:

• Hexadecimal: 0x0000000000000000055946e6fec8a799
• Decimal: 385,417,201,047,873,433

Given that ASTR has 18 decimal places, I calculated the fee as:

• Calculated Fee: 385,417,201,047,873,433 / (10^18) = 0.385417201047873433 ASTR

However, the actual fee charged is 0.0385417201 ASTR, which is exactly one decimal place less than the calculated amount.

Transaction Details:

• Transaction Link: Subscan Transaction

Questions:

• Am I missing any steps or considering incorrect decimal places in my calculation?
• Is there an inconsistency in how the fee is reported versus how it's applied?

[Dinonard]

Hey @snoopy1412 ,

you're right, it's a bug in the report.
The actual value calculated is correct, but we scaled the value down for XCM fees at the beginning of the year due to some tokenomics changes.

We'll revisit this and make sure it's 0.385....

EDIT: for now we'll keep the lower price, so 0.0385, but will modify the report so it's correct.