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
Hi,
When I publish transactions to the chain, I calculate the message hash, and use it later to track the transaction.
Unfortunately, since yesterday, I have experienced multiple occurrences where the in memory computed message hash for the boc, did not match the one on the chain.
I have not made any related changes to my code recently, and I also have not upgraded my tongo version (I am using v1.9.0).
It kept happening even after upgrading the tongo version to v1.14.4.
Is it possible that the hash computation algorithm in the chain has changed and the the algorithm in tongo is no longer relevant?
here is a code snippet which fetches the message from the chain, and computes the hash, and we can see we get a different result:
Hi,
When I publish transactions to the chain, I calculate the message hash, and use it later to track the transaction.
Unfortunately, since yesterday, I have experienced multiple occurrences where the in memory computed message hash for the boc, did not match the one on the chain.
I have not made any related changes to my code recently, and I also have not upgraded my tongo version (I am using v1.9.0).
It kept happening even after upgrading the tongo version to v1.14.4.
Is it possible that the hash computation algorithm in the chain has changed and the the algorithm in tongo is no longer relevant?
here is a code snippet which fetches the message from the chain, and computes the hash, and we can see we get a different result:
The text was updated successfully, but these errors were encountered: