Conversation
This comment has been minimized.
This comment has been minimized.
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
|
||
| When an incoming external message is sent to the blockchain, validators share them with each other, and might accidentally (or intentionally) deliver it several times. As it's usually preferred to process a unique incoming external message only once, some measures need to be taken to ensure duplicate messages are not accepted. Some of these techniques can be found in [wallet](/standard/wallets/comparison) contracts. | ||
|
|
||
| For reliable off-chain transaction tracking, the ecosystem relies on the [normalized message hash](/foundations/messages/normalized-hash) standard. |
There was a problem hiding this comment.
[HIGH] Banned marketing adjective “reliable” in external-in tracking sentence
The phrase “For reliable off-chain transaction tracking” uses the banned vague adjective “reliable” without specifying measurable conditions. According to the marketing language ban in the style guide (https://github.com/ton-org/docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L168-L180), such subjective, promotional wording (including “reliable”) must not appear in technical documentation. This phrasing adds hype instead of explaining what the tracking does or under what constraints it works. Removing “reliable” keeps the sentence factual while preserving its meaning.
| For reliable off-chain transaction tracking, the ecosystem relies on the [normalized message hash](/foundations/messages/normalized-hash) standard. | |
| For off-chain transaction tracking, the ecosystem relies on the [normalized message hash](/foundations/messages/normalized-hash) standard. |
Please leave a reaction 👍/👎 to this suggestion to improve future reviews for everyone!
|
|
||
| import { Aside } from "/snippets/aside.jsx"; | ||
|
|
||
| The normalized message hash is a consistent and reliable identifier for [external-in](/foundations/messages/external-in) messages. It remains constant regardless of variations in the `src`, `import_fee`, and `init` fields, which can change without affecting the validity of the message. This hash is particularly useful for tracking transactions. |
There was a problem hiding this comment.
[HIGH] Banned marketing adjective “reliable” in normalized hash intro
The sentence describes the normalized message hash as “a consistent and reliable identifier,” which uses the banned vague positive adjective “reliable” without measurable criteria. The style guide explicitly prohibits marketing-style language such as “reliable” in technical content (see https://github.com/ton-org/docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L168-L180). Keeping this wording would introduce promotional tone instead of precise, testable behavior. Removing the adjective keeps the focus on the concrete role of the identifier.
| The normalized message hash is a consistent and reliable identifier for [external-in](/foundations/messages/external-in) messages. It remains constant regardless of variations in the `src`, `import_fee`, and `init` fields, which can change without affecting the validity of the message. This hash is particularly useful for tracking transactions. | |
| The normalized message hash is a consistent identifier for [external-in](/foundations/messages/external-in) messages. It remains constant regardless of variations in the `src`, `import_fee`, and `init` fields, which can change without affecting the validity of the message. This hash is particularly useful for tracking transactions. |
Please leave a reaction 👍/👎 to this suggestion to improve future reviews for everyone!
|
To fix the formatting issues:
Alternatively, a maintainer can comment /fmt in this PR to auto-apply fixes in a new commit from the bot. |
2 participants
Closes #1877
This PR adds a new page about the normalized hash