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
I've noticed two scenarios where I'm calling a pallet asset dispatchable and it returns a token error, yet with a similar assets' error in existance:
mint an asset that does not exist returns DispatchError::Token(UnknownAsset) in stead of pallet assets' Unknown (ref).
burn greater amount of an asset with Preserve returns Token(FundsUnavailable) in stead of (I would say) BalanceLow, not sure though because we are burning.
Curious to hear what the expected behaviour is since for the second example it was clearly chosen to use the TokenError above the assets' error.
The text was updated successfully, but these errors were encountered:
I've noticed two scenarios where I'm calling a pallet asset dispatchable and it returns a token error, yet with a similar assets' error in existance:
DispatchError::Token(UnknownAsset)
in stead of pallet assets'Unknown
(ref).Preserve
returnsToken(FundsUnavailable)
in stead of (I would say)BalanceLow
, not sure though because we are burning.Curious to hear what the expected behaviour is since for the second example it was clearly chosen to use the TokenError above the assets' error.
The text was updated successfully, but these errors were encountered: