-
Notifications
You must be signed in to change notification settings - Fork 179
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extrinsic Encoding differs from initial value #137
Comments
I think it could potentiialy be down to this line:
There is no corresponding encode for a potential length which would explain why only the start of the value is different. |
@infinitedaremo The length is prepended at the end of the function: go-substrate-rpc-client/types/extrinsic.go Line 242 in 904cb0b
The reason why is shorter (missing 5th byte We will support it very soon. |
Thats good to hear. In the mean time. Is there a way to get the original extrinsic hash from the current code? |
@infinitedaremo Can you elaborate a bit more on this? Do you mean from each extrinsic encoded above, get the correspondent extrinsic hash id? |
Yes. I couldnt find that data anywhere. |
@infinitedaremo I believe is just the blake2b256 of the byte array representation of the extrinsic encoded hex:
|
Please re-open another issue if there are questions related to this. |
Retrieving block 4013570 from Polkadot mainnet. The raw extrinsic hexs are as follows:
Once the extrinsic is decoded to the Go struct. Attempting to encode it again gives differing values:
Note the inherent extrinsic is as expected but the first 2nd, 3rd and 9th characters are different.
The text was updated successfully, but these errors were encountered: