You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So the issue is that transactionPayment.withFeePath is only used for the initial tx fee, but not the additional EVM storage fee.
I think the best way is to have a new storage that is set on ensure_can_charge_fee_with_call and cleared on post_dispatch and update native_then_alternative_or_default to use this new path before the alternative path.
In this way, with_fee_path / with_fee_currency / with_fee_aggregated_path can be used to override EVM storage fee asset.
The account balance is only $usdc and $aca
earning.Bonded
, the account Available balance is insufficientThis transaction will fail. The possible reason is that when operating evm token, a certain nativeToken is required for Reserved
Transfer 1 $aca to this address, and use
transactionPayment.withFeePath
to specify $usdcThis transaction was successful, verifying the conjecture:
The text was updated successfully, but these errors were encountered: