Contracts feedback #64
Merged
Conversation
This file contains hidden or 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
a-bahdanau
commented
Apr 1, 2025
| @@ -9,15 +9,26 @@ import TabItem from '@theme/TabItem'; | |||
| If you are stuck on some of the examples you can find original template project with all modifications performed during this guide [here](https://github.com/ton-community/ton-onboarding-sandbox/tree/main/quick-start/smart-contracts/Example). | |||
| ::: | |||
|
|
|||
| While it's technically possible to create smart contract on TON not having any persistent storage, almost all smart-contracts need to store their `state` between transactions. This guide explains standard ways of managing `state` of smart-contract and using `get methods` to obtain it from outside the blockchain. | |||
| While it's technically possible to create smart contract on TON not having any persistent storage, almost all smart-contracts need to store their `data` between transactions. This guide explains standard ways of managing `storage` of smart-contract and using `get methods` to obtain it from outside the blockchain. | |||
There was a problem hiding this comment.
Тут я бы убрал инфу про то что техникли посибл без стоража, просто оставил часть что эта страница объясняет как хранить какие то переменные
|
|
||
| ## Smart Contract Storage Operations | ||
|
|
||
| First thing that we should say is that there is a small, but important difference between smart-contract `persistent data` and [TVM storage](/v3/documentation/tvm/tvm-initialization#initial-state) existing only during execution of smart-contract. Remember that smart-contracts follow **transaction** concept - if any system or user exception is raised during execution, i.e. transaction fails - `TVM storage` will not be committed to smart-contract `persistent data`. From the realization point this means that smart-contract `persistent data` is copied to `TVM storage` before starting the execution and committed back, optionally modified, in case of successful **transaction**. For simplification of this guide we will not use those strict terms, instead we will describe both as `storage` and rely on context, so, keep these facts in mind. |
There was a problem hiding this comment.
Тут я бы ввёл вот эти bullet разделения. Иначе тяжело читается
persistent
tvm storage
|
|
||
| In case it's inconvenient to always serialize and deserialize storage cell, there is a pretty standard practice to define two wrapper methods that provide corresponding logic. If you didn't change smart-contract code it should contain following lines: | ||
|
|
||
| <Tabs groupId="language"> | ||
| <TabItem value="FunC" label="FunC"> | ||
| ```func | ||
| ```func title="hello_world.fc" |
There was a problem hiding this comment.
напиши тут именно ./contracts/hello_world.fc чтобы максимально наглядно было в какой папке находится
There was a problem hiding this comment.
Применимо для всех таких моментов
| There are two main instructions that provide access to smart-contract storage: | ||
| - `get_data()` returning current storage cell. | ||
| - `set_data()` setting current storage cell. | ||
| ### Step1: Edit smart-contract code |
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.
Why is it important?
Related Issue