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
As a result if I compare the result of substrate export-blocks command or if I make a raw query to the rpc, I get different values for these extrinsics. If the subxt client is just supposed to return the result of the API call it should not try to interpret the payload.
Instead we should probably use something like this
I think that's a fair comment; all that Decode::decode is doing is removing the Compact(length) bytes from the beginning anyway and allocating a new vec in the process. Probably we can handle this "down the line" easily enough, avoid an extra allocation and have a slgihtly "purer" RPC call.
When I query the chain_getBlock extrinsics, subxt deserialize the extrinsics bytes with scale
subxt/subxt/src/rpc/types.rs
Lines 113 to 126 in 1ad9a20
As a result if I compare the result of substrate export-blocks command or if I make a raw query to the rpc, I get different values for these extrinsics. If the subxt client is just supposed to return the result of the API call it should not try to interpret the payload.
Instead we should probably use something like this
The text was updated successfully, but these errors were encountered: