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 did some debugging and I found out that there are some unexpected SCALE encoding issues with the U256 types in this call like the value and max_fee_per_gas attributes.
In the metadata of the runtime, this type is defined as followed:
Somehow the metadata dictates that this U256 should be interpreted as a [u64; 4] and the library does accordingly, but this seems unwanted behaviour. So I'm not sure if this is a bug on the library end, or I'm totally missing something here.
Until this is figured out, as a workaround you can overwrite this type with:
Hi!
I'm trying to compose a call for my frontier-based node:
But I'm getting an error:
I don't know wether it's ok to expect a list in the place of
U256
, but here is the metadata for the function:Could you tell me how can I properly specify the params? Or is it a bug?
The text was updated successfully, but these errors were encountered: