Proofread Nodes & Modes #967
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
reveloper
reviewed
Feb 18, 2025
| @@ -1,7 +1,7 @@ | |||
| # Message Modes Cookbook | |||
| @@ -1,7 +1,7 @@ | |||
| # Message Modes Cookbook | |||
|
|
|||
| Understanding the different modes and flags available for sending messages is crucial to ensure that your smart contracts behave as intended. | |||
| While [message modes](/v3/documentation/smart-contracts/message-management/sending-messages#message-modes) section provided detailed descriptions of these modes and flags, in this section we will illustrate their practical application through specific examples. | |||
| While the [message modes](/v3/documentation/smart-contracts/message-management/sending-messages#message-modes) section provides detailed descriptions of these modes and flags, in this section we will illustrate their practical application through specific examples. | |||
|
|
|||
| :::info IMPORTANT | |||
There was a problem hiding this comment.
Is it necessary to point to this example here?
Looks not clear, how this example will help readers, who just opened page.
| @@ -11,23 +11,23 @@ You can check [this example](https://testnet.tonviewer.com/transaction/42ed45726 | |||
|
|
|||
| Please check how [get_balance](/v3/documentation/smart-contracts/func/docs/stdlib/#get_balance) works to better understand `balance` inside TVM. | |||
|
|
|||
| All TON tokens owned by a contract are reflected in the [contract balance](https://github.com/ton-blockchain/ton/blob/7151ff26279fef6dcfa1f47fc0c5b63677ae2458/crypto/block/block.tlb#L263C1-L265C20). Some of these tokens are also attributed to the currently processed incoming [message](/v3/documentation/data-formats/tlb/msg-tlb#commonmsginfo) - a mechanism that works effectively because any TON transaction involving a [non-system contract](/v3/documentation/smart-contracts/contracts-specs/governance) processes exactly one incoming message at a time. | |||
| All TON tokens owned by a contract are reflected in the [contract balance](https://github.com/ton-blockchain/ton/blob/7151ff26279fef6dcfa1f47fc0c5b63677ae2458/crypto/block/block.tlb#L263C1-L265C20). Some of these tokens are also attributed to the currently processed incoming [message](/v3/documentation/data-formats/tlb/msg-tlb#commonmsginfo) — a mechanism that works effectively because any TON transaction involving a [non-system contract](/v3/documentation/smart-contracts/contracts-specs/governance) processes exactly one incoming message at a time. | |||
There was a problem hiding this comment.
Examples are really helpful, and links should be provided. However, let's maintain a balance, such as one link per paragraph or about three links per page.
| @@ -40,17 +40,17 @@ The table is populated based on [this example](https://tonviewer.com/transaction | |||
|
|
|||
| | Fee in Explorer | Value | How it's obtained | | |||
| | :------------------------------------------------------------------------------------------------ | :---------- | :------------------------------ | | |||
| | Total fee | 0,001982134 | gas + storage + action + import | | |||
There was a problem hiding this comment.
Capitalized Total fee seems inconsistent here. Could it be total fee?
| @@ -40,17 +40,17 @@ The table is populated based on [this example](https://tonviewer.com/transaction | |||
|
|
|||
| | Fee in Explorer | Value | How it's obtained | | |||
There was a problem hiding this comment.
Use sentence case in the headers.
Fee in explorer
| @@ -1,7 +1,7 @@ | |||
| # Message Modes Cookbook | |||
|
|
|||
| Understanding the different modes and flags available for sending messages is crucial to ensure that your smart contracts behave as intended. | |||
| While [message modes](/v3/documentation/smart-contracts/message-management/sending-messages#message-modes) section provided detailed descriptions of these modes and flags, in this section we will illustrate their practical application through specific examples. | |||
| While the [message modes](/v3/documentation/smart-contracts/message-management/sending-messages#message-modes) section provides detailed descriptions of these modes and flags, in this section we will illustrate their practical application through specific examples. | |||
There was a problem hiding this comment.
Seems better for reading:
While the [message modes](https://github.com/memearchivarius/ton-docs-meme/blob/proofread_docs/v3/documentation/smart-contracts/message-management/sending-messages#message-modes) section provides detailed descriptions of these modes and flags, this section illustrates their practical application through specific examples.
|
|
||
| Therefore, any blockchain payment may come either: | ||
|
|
||
| - From the incoming message `value`. | ||
| For instance, computation fees are paid in this way, unless contract calls [accept_message](v3/documentation/smart-contracts/transaction-fees/accept-message-effects). This ensures that malicious actors cannot spend contract's balance on handling their data. | ||
| - From the contract `balance` (will not touch amount of TON designated as incoming this transaction). | ||
| For instance, computation fees are paid in this way, unless the contract calls [accept_message](/v3/documentation/smart-contracts/transaction-fees/accept-message-effects). This ensures that malicious actors cannot spend the contract's balance on handling their data. |
There was a problem hiding this comment.
Cut unnecessary words:
For instance, computation fees are paid this way unless the contract calls [accept_message](/v3/documentation/smart-contracts/transaction-fees/accept-message-effects). This ensures malicious actors cannot spend the contract's balance handling their data.| For instance, computation fees are paid in this way, unless contract calls [accept_message](v3/documentation/smart-contracts/transaction-fees/accept-message-effects). This ensures that malicious actors cannot spend contract's balance on handling their data. | ||
| - From the contract `balance` (will not touch amount of TON designated as incoming this transaction). | ||
| For instance, computation fees are paid in this way, unless the contract calls [accept_message](/v3/documentation/smart-contracts/transaction-fees/accept-message-effects). This ensures that malicious actors cannot spend the contract's balance on handling their data. | ||
| - From the contract `balance` (will not touch the amount of TON designated as incoming this transaction). | ||
| Storage fees in workchains 0 and -1, as well as most actions, are currently examples of this. |
There was a problem hiding this comment.
Cut unnecessary words:
Storage fees in workchains 0 and -1 and most actions are currently examples of this.|
|
||
| - Storage, consisting of [account storage](https://github.com/ton-blockchain/ton/blob/7151ff26279fef6dcfa1f47fc0c5b63677ae2458/crypto/block/transaction.cpp#L651-L675) and [in_msg import](https://github.com/ton-blockchain/ton/blob/7151ff26279fef6dcfa1f47fc0c5b63677ae2458/crypto/block/transaction.cpp#L783-L816) | ||
| - [Credit](https://github.com/ton-blockchain/ton/blob/7151ff26279fef6dcfa1f47fc0c5b63677ae2458/crypto/block/transaction.cpp#L959-L981), where in_msg `value` is added to the `balance` | ||
| - [Credit](https://github.com/ton-blockchain/ton/blob/7151ff26279fef6dcfa1f47fc0c5b63677ae2458/crypto/block/transaction.cpp#L959-L981), where the in_msg `value` is added to the `balance` | ||
| - Compute, where the actual smart contract code is executed in TVM |
There was a problem hiding this comment.
Use active voice:
Compute, where TVM executes the actual smart contract code
| @@ -11,23 +11,23 @@ You can check [this example](https://testnet.tonviewer.com/transaction/42ed45726 | |||
|
|
|||
| Please check how [get_balance](/v3/documentation/smart-contracts/func/docs/stdlib/#get_balance) works to better understand `balance` inside TVM. | |||
|
|
|||
| All TON tokens owned by a contract are reflected in the [contract balance](https://github.com/ton-blockchain/ton/blob/7151ff26279fef6dcfa1f47fc0c5b63677ae2458/crypto/block/block.tlb#L263C1-L265C20). Some of these tokens are also attributed to the currently processed incoming [message](/v3/documentation/data-formats/tlb/msg-tlb#commonmsginfo) - a mechanism that works effectively because any TON transaction involving a [non-system contract](/v3/documentation/smart-contracts/contracts-specs/governance) processes exactly one incoming message at a time. | |||
| All TON tokens owned by a contract are reflected in the [contract balance](https://github.com/ton-blockchain/ton/blob/7151ff26279fef6dcfa1f47fc0c5b63677ae2458/crypto/block/block.tlb#L263C1-L265C20). Some of these tokens are also attributed to the currently processed incoming [message](/v3/documentation/data-formats/tlb/msg-tlb#commonmsginfo) — a mechanism that works effectively because any TON transaction involving a [non-system contract](/v3/documentation/smart-contracts/contracts-specs/governance) processes exactly one incoming message at a time. | |||
There was a problem hiding this comment.
Use active voice:
A contract's [balance](https://github.com/ton-blockchain/ton/blob/7151ff26279fef6dcfa1f47fc0c5b63677ae2458/crypto/block/block.tlb#L263C1-L265C20) reflects all TON tokens it owns.This approach effectively attributes some of these tokens to the currently processed incoming [message](/v3/documentation/data-formats/tlb/msg-tlb#commonmsginfo) because any TON transaction involving a non-system contract processes exactly one incoming message at a time.
|
Moved this work to the #970 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
#965
Checklist