Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escape special characters +-&|!(){}[]^"~*?:\ - e.g. \+ \* \!
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Is it possible to calculate input and output message hash before sending a transaction in TON?

Hi is it possible to calculate input and output message hash before sending it. For example, this is my transaction https://testnet.tonscan.org/tx/op5iqZD9X7zsYGFRc0g9R8w2hLiM8Kt3Af10-VZr0Vg= I would like to get jhibs80fCur+fC1q9fgOjjvl43F8ZbcjLfljtzAXYzE= and +lNc/MYo+/G5HGLke13XNgmwvi4W55fc7hGTN1uV6ks= before sending. is that possible?

Posted one year ago
Votes Newest


Excellent question! Predicting the input and output message hash before transmitting a transaction is not feasible.

The underlying reason is the dynamic nature of contract data, which can be altered by any previous transactions. Consequently, the current state of the contract remains unpredictable until the transaction is processed.

Hence, the exact input and output message hash values cannot be determined ahead of time. A more effective approach is to validate the input and output data in the context of transaction execution rather than attempting to predict the message hash in advance.

In conclusion, the dynamic and unpredictable nature of transaction histories and state changes in contracts makes it impossible to precisely calculate the input and output message hash prior to dispatching a transaction.

Posted one year ago
Edited one year ago
Howard Peng
10 × 1 Administrator