-
Notifications
You must be signed in to change notification settings - Fork 10
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
Potential issue with extrinsic hash #62
Comments
Will publish our raw value and see if we can get to the bottom of this! |
For this 0.6.2.1 block 1_003.json here is our derivation of the extrinsic hash
If its "g" see "Guarantee 0 bytes" vs "E_G_encoded" (from this within the block) -- happy to zoom in further into that as needed but need a clue as to what to zoom into =) |
So the difference is in the start of E_G_encoded ( 0180eb vs 01). I believe it should start with a compact integer encoding of the number of guarantees and then have the hash of the first guarantee
Can you see how you derive "80eb" after the length "01" ? We both have the same report hash afterwards (bc73bbb98b756d6687090f155eed04bdd513ed5b20d3f319ee9084943429280c) |
Ok we agree with your conclusion =) -- we were encoding [][]byte rather than []GuaranteeIntermediateEncoding and ended up with that strange
|
Final extrinsic hash: 4b545b182c0d0e9b13f0a84e37d42fe5dbe7d5cc4be41bd890a2e2785039dc49 -- we are in alignment now! |
Addressed in 0.6.2.2 |
I am trying to figure out the difference in my g encoding, but it seems that the last |
I suggest using the same syntax on
|
I'm getting a mismatch of the extrinsic hash when a guarantee is included in the extrinsics.
The first vector to include one in the extrinsics is assurances/1_003.
The vector is expecting an extrinsic hash of 0xacda7941616e5d458f88c0a140396c65dc66d3d44d7bb64a84c6739095af7ddd.
I am arriving at 0x4b545b182c0d0e9b13f0a84e37d42fe5dbe7d5cc4be41bd890a2e2785039dc49.
My algorithm seems to match the GP so I'm not sure if its my issue or an issue with the vectors.
For assurances/1_003, can you please let me know the value of "g" here (prior to being hashed) so we can see which one is correct?
My value:
0x01bc73bbb98b756d6687090f155eed04bdd513ed5b20d3f319ee9084943429280c0d000000030100b269a27a06e07e9616ed1da82408b04ea8bc5cf33f24fd927170205918df5f83221683fa14a84ed95aebb51ff8cd6fedd9b48505399024c16939b5900fb3490a0200a3b4b148ca9b3fb9cc08c8b8fe615b75cb5f375e52338661756eeaad651d50382723dfc8ca268df3e708b68c2190e0783a6088eb10a07dcbd8376cef823afd0703007cd48123d6a5e19d3d8f36233d565e5cc6d70bc30777a3d594ba3678619b3c18c0cc480fb5726cb988fae8ff9372334bee4936e251c6afc02f1239bbfd239802
The text was updated successfully, but these errors were encountered: