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
Copy file name to clipboardExpand all lines: docs/v3/guidelines/smart-contracts/fee-calculation.md
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ Use the `GETSTORAGEFEE` opcode with the following parameters:
22
22
| bits | Number of contract bits |
23
23
| is_mc | True if the source or destination is in the masterchain |
24
24
25
-
:::info Only unique hash cells are counted for storage and fwd fees i.e. 3 identical hash cells are counted as one.
25
+
:::info Only unique hash cells are counted for storage and forward fees; for example, three identical hash cells are counted as one.
26
26
27
27
In particular, it deduplicates data: if there are several equivalent sub-cells referenced in different branches, their content is only stored once.
28
28
@@ -31,7 +31,7 @@ In particular, it deduplicates data: if there are several equivalent sub-cells r
31
31
32
32
### Calculation Flow
33
33
34
-
Each contract has its balance. You can calculate how many TONs your contract requires to remain valid for a specified `seconds` time using the function:
34
+
Each contract has its balance. You can calculate how many TONs your contract needs to remain valid for a given number of seconds using the following function:
35
35
36
36
```func
37
37
int get_storage_fee(int workchain, int seconds, int bits, int cells) asm(cells bits seconds workchain) "GETSTORAGEFEE";
@@ -67,7 +67,7 @@ If `storage_fee` is hardcoded, **remember to update it** during contract update
67
67
68
68
### Overview
69
69
70
-
In most cases use the `GETGASFEE` opcode with the following parameters:
70
+
In most cases, use the `GETGASFEE` opcode with the following parameters:
0 commit comments