diff --git a/cspell.json b/cspell.json index be1ac66069..e387eb522c 100644 --- a/cspell.json +++ b/cspell.json @@ -4,7 +4,7 @@ "language": "en", "files": [ "**/*.md", - "**/*.mdx", + "**/*.mdx" ], "dictionaries": ["tvm-instructions", "names", "commands"], "dictionaryDefinitions": [ @@ -19,7 +19,7 @@ { "name":"commands", "path":"./src/grammar/commands-dictionary.txt" - }, + } ], "words": [ "ADNL", @@ -307,6 +307,7 @@ ], "flagWords": [], "ignorePaths": [ + "scripts", "static", "node_modules", "package.json", @@ -320,6 +321,6 @@ "sidebars.js", "sidebars", "i18n", - ".husky", + ".husky" ] } diff --git a/docs/v3/concepts/dive-into-ton/go-from-ethereum/difference-of-blockchains.md b/docs/v3/concepts/dive-into-ton/go-from-ethereum/difference-of-blockchains.md index b4d70de9cc..9000b67042 100644 --- a/docs/v3/concepts/dive-into-ton/go-from-ethereum/difference-of-blockchains.md +++ b/docs/v3/concepts/dive-into-ton/go-from-ethereum/difference-of-blockchains.md @@ -14,7 +14,7 @@ Ethereum, by inheriting and extending the foundational principles of Bitcoin, ha In response to these challenges, TON offers an alternative approach aimed at improving scalability and performance. Designed with the ambition to provide developers with maximum flexibility to create a variety of applications, TON uses the concept of shards and masterchain to optimize the block creation process. In each TON shardchain and masterchain, a new block is generated on average every 5 seconds, ensuring fast transaction execution. Unlike Ethereum, where state updates are synchronous, TON implements asynchronous messaging between smart contracts, allowing each transaction to be processed independently and in parallel, significantly speeding up transaction processing on the network. Sections and articles to familiarize yourself with: -* [Shards](/v3/documentation/smart-contracts/shards) +* [Shards](/v3/documentation/smart-contracts/shards/shards-intro) * [Comparison of Blockchains document](https://ton.org/comparison_of_blockchains.pdf) * [Comparison of Blockchains table (much less informative than the document, but more visual)](/v3/concepts/dive-into-ton/ton-blockchain/blockchain-comparison) diff --git a/docs/v3/concepts/dive-into-ton/go-from-ethereum/solidity-vs-func.md b/docs/v3/concepts/dive-into-ton/go-from-ethereum/solidity-vs-func.md index dd276761e2..9b6b0359c5 100644 --- a/docs/v3/concepts/dive-into-ton/go-from-ethereum/solidity-vs-func.md +++ b/docs/v3/concepts/dive-into-ton/go-from-ethereum/solidity-vs-func.md @@ -208,7 +208,7 @@ var msg = begin_cell() send_raw_message(msg, mode); ``` Let's discuss in more detail what it looks like for our smart contract to send a message to our recipient: -1. Initially, we need to build our message. The full structure of the send can be found [here](v3/documentation/smart-contracts/message-management/sending-messages). We won't go into detail on how to assemble it here, you can read about that at the link. +1. Initially, we need to build our message. The full structure of the send can be found [here](/v3/documentation/smart-contracts/message-management/sending-messages). We won't go into detail on how to assemble it here, you can read about that at the link. 2. The body of the message represents a cell. In `msg_body_cell` we do: `begin_cell()` - creates `Builder` for the future cell, first `store_uint` - stores the first uint into `Builder` (1 - this is our `op`), second `store_uint` - stores the second uint into `Builder` (num - this is our number that we will manipulate in the receiving contract), `end_cell()` - creates the cell. 3. To attach the body that will come in `recv_internal` in the message, we reference the collected cell in the message itself with `store_ref`. 4. Sending a message. diff --git a/docs/v3/concepts/dive-into-ton/ton-blockchain/sharding.md b/docs/v3/concepts/dive-into-ton/ton-blockchain/sharding.md index 93e5ef1a43..e534b5fd95 100644 --- a/docs/v3/concepts/dive-into-ton/ton-blockchain/sharding.md +++ b/docs/v3/concepts/dive-into-ton/ton-blockchain/sharding.md @@ -21,5 +21,5 @@ In addition to the dynamic creation of shards, TON uses **Split Merge** function ## See Also -* [Shards Dive In](/v3/documentation/smart-contracts/shards) -* [# Infinity Sharding Paradigm](/v3/documentation/smart-contracts/infinity-sharding-paradigm) +* [Shards Dive In](/v3/documentation/smart-contracts/shards/shards-intro) +* [# Infinity Sharding Paradigm](/v3/documentation/smart-contracts/shards/infinity-sharding-paradigm) diff --git a/docs/v3/concepts/ton-blockchain/shards.md b/docs/v3/concepts/ton-blockchain/shards.md index 96af82cac3..39e6bef97a 100644 --- a/docs/v3/concepts/ton-blockchain/shards.md +++ b/docs/v3/concepts/ton-blockchain/shards.md @@ -21,5 +21,5 @@ In addition to the dynamic creation of shards, TON uses **Split Merge** function ## See Also -* [Shards Dive In](/v3/documentation/smart-contracts/shards) -* [# Infinity Sharding Paradigm](/v3/documentation/smart-contracts/infinity-sharding-paradigm) +* [Shards Dive In](/v3/documentation/smart-contracts/shards/shards-intro) +* [# Infinity Sharding Paradigm](/v3/documentation/smart-contracts/shards/infinity-sharding-paradigm) diff --git a/docs/v3/contribute/docs/schemes-guidelines.mdx b/docs/v3/contribute/docs/schemes-guidelines.mdx index 91741191e3..ba0af8c1c6 100644 --- a/docs/v3/contribute/docs/schemes-guidelines.mdx +++ b/docs/v3/contribute/docs/schemes-guidelines.mdx @@ -42,7 +42,7 @@ If the order of transactions doesn't matter, you can omit their labels. This sim -Learn references directly from Visio [message-processing.vsdx](/static/schemes-visio/message-processing.vsdx). +Learn references directly from Visio [message-processing.vsdx](/schemes-visio/message-processing.vsdx). ### Formats and Colors diff --git a/docs/v3/documentation/dapps/oracles/red_stone.mdx b/docs/v3/documentation/dapps/oracles/red_stone.mdx index e0c03e2d34..4638eb9607 100644 --- a/docs/v3/documentation/dapps/oracles/red_stone.mdx +++ b/docs/v3/documentation/dapps/oracles/red_stone.mdx @@ -19,7 +19,7 @@ To learn more about RedStone oracles design go to the [RedStone docs](https://do ### price_manager.fc - Sample oracle contract that consumes RedStone oracles data [price_manager.fc](https://github.com/redstone-finance/redstone-oracles-monorepo/blob/main/packages/ton-connector/contracts/price_manager.fc) written in - FunC. It requires [TVM Upgrade 2023.07](v3/documentation/tvm/changelog/tvm-upgrade-2023-07). + FunC. It requires [TVM Upgrade 2023.07](/v3/documentation/tvm/changelog/tvm-upgrade-2023-07). #### initial data diff --git a/docs/v3/documentation/data-formats/tlb/tl-b-language.mdx b/docs/v3/documentation/data-formats/tlb/tl-b-language.mdx index b22181552b..e2b5535ad0 100644 --- a/docs/v3/documentation/data-formats/tlb/tl-b-language.mdx +++ b/docs/v3/documentation/data-formats/tlb/tl-b-language.mdx @@ -5,7 +5,7 @@ import ThemedImage from '@theme/ThemedImage'; TL-B (Type Language - Binary) serves to describe the type system, constructors and existing functions. For example, we can use TL-B schemes to build binary structures associated with TON Blockchain. Special TL-B parsers can read schemes to deserialize binary data into different objects. TL-B describes data schemes for `Cell` objects. If you not familiar -with `Cells`, please read [Cell & Bag of Cells(BOC)](v3/documentation/data-formats/tlb/cell-boc#cell) article. +with `Cells`, please read [Cell & Bag of Cells(BOC)](/v3/documentation/data-formats/tlb/cell-boc#cell) article. ## Overview @@ -516,7 +516,7 @@ unary_succ$1 {n:#} x:(Unary ~n) = Unary ~(n + 1); _ u:(Unary Any) = UnaryChain; ``` -This is example has good explanation in [TL-B Types](v3/documentation/data-formats/tlb/tl-b-types#unary) +This is example has good explanation in [TL-B Types](/v3/documentation/data-formats/tlb/tl-b-types#unary) article. The main idea here is that `UnaryChain` will recursively deserialize until reach of `unary_zero$0` (because we know last element of `Unary X` type by definition `unary_zero$0 = Unary ~0;` and `X` is calculated in runtime due `Unary ~(n + 1)` definition). diff --git a/docs/v3/documentation/data-formats/tlb/transaction-layout.md b/docs/v3/documentation/data-formats/tlb/transaction-layout.md index 04eb6bfe12..41821d21ef 100644 --- a/docs/v3/documentation/data-formats/tlb/transaction-layout.md +++ b/docs/v3/documentation/data-formats/tlb/transaction-layout.md @@ -22,8 +22,8 @@ transaction$0111 account_addr:bits256 lt:uint64 | Field | Type | Required | Description | | ----------------- | ---------------------------------------------------------------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `account_addr` | bits256 | Yes | The hash part of the address on which the transaction was executed. [More about addresses](v3/documentation/smart-contracts/addresses#address-of-smart-contract) | -| `lt` | uint64 | Yes | Represents _Logical time_. [More about logical time](v3/documentation/smart-contracts/message-management/messages-and-transactions#what-is-a-logical-time) | +| `account_addr` | bits256 | Yes | The hash part of the address on which the transaction was executed. [More about addresses](/v3/documentation/smart-contracts/addresses#address-of-smart-contract) | +| `lt` | uint64 | Yes | Represents _Logical time_. [More about logical time](/v3/documentation/smart-contracts/message-management/messages-and-transactions#what-is-a-logical-time) | | `prev_trans_hash` | bits256 | Yes | The hash of the previous transaction on this account. | | `prev_trans_lt` | uint64 | Yes | The `lt` of the previous transaction on this account. | | `now` | uint32 | Yes | The `now` value that was set when executing this transaction. It's a Unix timestamp in seconds. | @@ -32,7 +32,7 @@ transaction$0111 account_addr:bits256 lt:uint64 | `end_status` | [AccountStatus](#accountstatus) | Yes | The status of this account after executing the transaction. | | `in_msg` | (Message Any) | No | The incoming message that triggered the execution of the transaction. Stored in a reference. | | `out_msgs` | HashmapE 15 ^(Message Any) | Yes | The dictionary that contains the list of outgoing messages that were created while executing this transaction. | -| `total_fees` | [CurrencyCollection](/v3/documentation/data-formats/tlb/msg-tlb#currencycollection) | Yes | The total amount of fees that were collected while executing this transaction. It consists of a _Toncoin_ value and possibly some [Extra-currencies](v3/documentation/dapps/defi/coins#extra-currencies). | +| `total_fees` | [CurrencyCollection](/v3/documentation/data-formats/tlb/msg-tlb#currencycollection) | Yes | The total amount of fees that were collected while executing this transaction. It consists of a _Toncoin_ value and possibly some [Extra-currencies](/v3/documentation/dapps/defi/coins#extra-currencies). | | `state_update` | [HASH_UPDATE](#hash_update) Account | Yes | The `HASH_UPDATE` structure. Stored in a reference. | | `description` | [TransactionDescr](#transactiondescr-types) | Yes | A detailed description of the transaction execution process. Stored in a reference. | @@ -89,12 +89,12 @@ trans_ord$0000 credit_first:Bool | Field | Type | Required | Description | | -------------- | -------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `credit_first` | Bool | Yes | A flag that correlates with `bounce` flag of an incoming message. `credit_first = !bounce` | -| `storage_ph` | TrStoragePhase | No | Contains information about storage phase of a transaction execution. [More Info](v3/documentation/tvm/tvm-overview#transactions-and-phases) | -| `credit_ph` | TrCreditPhase | No | Contains information about credit phase of a transaction execution. [More Info](v3/documentation/tvm/tvm-overview#transactions-and-phases) | -| `compute_ph` | TrComputePhase | Yes | Contains information about compute phase of a transaction execution. [More Info](v3/documentation/tvm/tvm-overview#transactions-and-phases) | -| `action` | TrActionPhase | No | Contains information about action phase of a transaction execution. [More Info](v3/documentation/tvm/tvm-overview#transactions-and-phases). Stored in a reference. | +| `storage_ph` | TrStoragePhase | No | Contains information about storage phase of a transaction execution. [More Info](/v3/documentation/tvm/tvm-overview#transactions-and-phases) | +| `credit_ph` | TrCreditPhase | No | Contains information about credit phase of a transaction execution. [More Info](/v3/documentation/tvm/tvm-overview#transactions-and-phases) | +| `compute_ph` | TrComputePhase | Yes | Contains information about compute phase of a transaction execution. [More Info](/v3/documentation/tvm/tvm-overview#transactions-and-phases) | +| `action` | TrActionPhase | No | Contains information about action phase of a transaction execution. [More Info](/v3/documentation/tvm/tvm-overview#transactions-and-phases). Stored in a reference. | | `aborted` | Bool | Yes | Indicates whether the transaction execution was aborted. | -| `bounce` | TrBouncePhase | No | Contains information about bounce phase of a transaction execution. [More Info](v3/documentation/smart-contracts/message-management/non-bounceable-messages) | +| `bounce` | TrBouncePhase | No | Contains information about bounce phase of a transaction execution. [More Info](/v3/documentation/smart-contracts/message-management/non-bounceable-messages) | | `destroyed` | Bool | Yes | Indicates whether the account was destroyed during the execution. | ## Storage @@ -108,7 +108,7 @@ trans_storage$0001 storage_ph:TrStoragePhase | Field | Type | Description | | ------------ | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `storage_ph` | TrStoragePhase | Contains information about storage phase of a transaction execution. [More Info](v3/documentation/tvm/tvm-overview#transactions-and-phases) | +| `storage_ph` | TrStoragePhase | Contains information about storage phase of a transaction execution. [More Info](/v3/documentation/tvm/tvm-overview#transactions-and-phases) | ## Tick-tock @@ -123,9 +123,9 @@ trans_tick_tock$001 is_tock:Bool storage_ph:TrStoragePhase | Field | Type | Required | Description | | ------------ | -------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `is_tock` | Bool | Yes | A flag indicating the type of transaction. Used to separate `Tick` and `Tock` transactions | -| `storage_ph` | TrStoragePhase | Yes | Contains information about storage phase of a transaction execution. [More Info](v3/documentation/tvm/tvm-overview#transactions-and-phases) | -| `compute_ph` | TrComputePhase | Yes | Contains information about compute phase of a transaction execution. [More Info](v3/documentation/tvm/tvm-overview#transactions-and-phases) | -| `action` | TrActionPhase | No | Contains information about action phase of a transaction execution. [More Info](v3/documentation/tvm/tvm-overview#transactions-and-phases). Stored in a reference. | +| `storage_ph` | TrStoragePhase | Yes | Contains information about storage phase of a transaction execution. [More Info](/v3/documentation/tvm/tvm-overview#transactions-and-phases) | +| `compute_ph` | TrComputePhase | Yes | Contains information about compute phase of a transaction execution. [More Info](/v3/documentation/tvm/tvm-overview#transactions-and-phases) | +| `action` | TrActionPhase | No | Contains information about action phase of a transaction execution. [More Info](/v3/documentation/tvm/tvm-overview#transactions-and-phases). Stored in a reference. | | `aborted` | Bool | Yes | Indicates whether the transaction execution was aborted. | | `destroyed` | Bool | Yes | Indicates whether the account was destroyed during the execution. | @@ -150,9 +150,9 @@ trans_split_prepare$0100 split_info:SplitMergeInfo | Field | Type | Required | Description | | ------------ | -------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `split_info` | SplitMergeInfo | Yes | Information about split process. | -| `storage_ph` | TrStoragePhase | No | Contains information about storage phase of a transaction execution. [More Info](v3/documentation/tvm/tvm-overview#transactions-and-phases) | -| `compute_ph` | TrComputePhase | Yes | Contains information about compute phase of a transaction execution. [More Info](v3/documentation/tvm/tvm-overview#transactions-and-phases) | -| `action` | TrActionPhase | No | Contains information about action phase of a transaction execution. [More Info](v3/documentation/tvm/tvm-overview#transactions-and-phases). Stored in a reference. | +| `storage_ph` | TrStoragePhase | No | Contains information about storage phase of a transaction execution. [More Info](/v3/documentation/tvm/tvm-overview#transactions-and-phases) | +| `compute_ph` | TrComputePhase | Yes | Contains information about compute phase of a transaction execution. [More Info](/v3/documentation/tvm/tvm-overview#transactions-and-phases) | +| `action` | TrActionPhase | No | Contains information about action phase of a transaction execution. [More Info](/v3/documentation/tvm/tvm-overview#transactions-and-phases). Stored in a reference. | | `aborted` | Bool | Yes | Indicates whether the transaction execution was aborted. | | `destroyed` | Bool | Yes | Indicates whether the account was destroyed during the execution. | @@ -195,7 +195,7 @@ trans_merge_prepare$0110 split_info:SplitMergeInfo | Field | Type | Description | | ------------ | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `split_info` | SplitMergeInfo | Information about merge process. | -| `storage_ph` | TrStoragePhase | Contains information about storage phase of a transaction execution. [More Info](v3/documentation/tvm/tvm-overview#transactions-and-phases) | +| `storage_ph` | TrStoragePhase | Contains information about storage phase of a transaction execution. [More Info](/v3/documentation/tvm/tvm-overview#transactions-and-phases) | | `aborted` | Bool | Indicates whether the transaction execution was aborted. | ## Merge install @@ -220,10 +220,10 @@ trans_merge_install$0111 split_info:SplitMergeInfo | --------------------- | --------------------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `split_info` | SplitMergeInfo | Yes | Information about merge process. | | `prepare_transaction` | [Transaction](#transaction) | Yes | Information about the [transaction prepared](#merge-prepare) for the merge operation. Stored in a reference. | -| `storage_ph` | TrStoragePhase | No | Contains information about storage phase of a transaction execution. [More Info](v3/documentation/tvm/tvm-overview#transactions-and-phases) | -| `credit_ph` | TrCreditPhase | No | Contains information about credit phase of a transaction execution. [More Info](v3/documentation/tvm/tvm-overview#transactions-and-phases) | -| `compute_ph` | TrComputePhase | Yes | Contains information about compute phase of a transaction execution. [More Info](v3/documentation/tvm/tvm-overview#transactions-and-phases) | -| `action` | TrActionPhase | No | Contains information about action phase of a transaction execution. [More Info](v3/documentation/tvm/tvm-overview#transactions-and-phases). Stored in a reference. | +| `storage_ph` | TrStoragePhase | No | Contains information about storage phase of a transaction execution. [More Info](/v3/documentation/tvm/tvm-overview#transactions-and-phases) | +| `credit_ph` | TrCreditPhase | No | Contains information about credit phase of a transaction execution. [More Info](/v3/documentation/tvm/tvm-overview#transactions-and-phases) | +| `compute_ph` | TrComputePhase | Yes | Contains information about compute phase of a transaction execution. [More Info](/v3/documentation/tvm/tvm-overview#transactions-and-phases) | +| `action` | TrActionPhase | No | Contains information about action phase of a transaction execution. [More Info](/v3/documentation/tvm/tvm-overview#transactions-and-phases). Stored in a reference. | | `aborted` | Bool | Yes | Indicates whether the transaction execution was aborted. | | `destroyed` | Bool | Yes | Indicates whether the account was destroyed during the execution. | diff --git a/docs/v3/documentation/faq.md b/docs/v3/documentation/faq.md index 4a60218a7a..6e607cf042 100644 --- a/docs/v3/documentation/faq.md +++ b/docs/v3/documentation/faq.md @@ -245,7 +245,7 @@ If the contract cannot initially execute `set_code()` (via its code or execution ### Can smart contract be deleted? -Yes, either as a result of storage fee accumulation (contract needs to reach -1 TON balance to be deleted) or by sending a message with [mode 160](v3/documentation/smart-contracts/message-management/sending-messages#message-modes). +Yes, either as a result of storage fee accumulation (contract needs to reach -1 TON balance to be deleted) or by sending a message with [mode 160](/v3/documentation/smart-contracts/message-management/sending-messages#message-modes). ### Are smart contract addresses case sensitive? diff --git a/docs/v3/documentation/infra/nodes/mytonctrl/mytonctrl-overview.mdx b/docs/v3/documentation/infra/nodes/mytonctrl/mytonctrl-overview.mdx index 9427e286a5..2daf307c8b 100644 --- a/docs/v3/documentation/infra/nodes/mytonctrl/mytonctrl-overview.mdx +++ b/docs/v3/documentation/infra/nodes/mytonctrl/mytonctrl-overview.mdx @@ -184,7 +184,7 @@ MyTonCtrl> add_custom_overlay Example: ```bash -add_custom_overlay custom /config.json # check link from above to know what config this command requires (v3/guidelines/nodes/custom-overlays) +add_custom_overlay custom /config.json # check link from above to know what config this command requires (/v3/guidelines/nodes/custom-overlays) ``` ### list_custom_overlays @@ -244,7 +244,7 @@ Based on the `validator index` (can be received by `status` command), there are - **The user is not a validator**: No penalties apply, but the user is not eligible for rewards either. No `validator efficiency` to check. This can be caused by a low stake or incorrect node configuration. Additionally, ensure that `mytonctrl` is running continuously. -Read more about `max_validators` and `max_main_validators` [on config parameters page](v3/documentation/network/configs/blockchain-configs#configuration-parameters-for-the-number-of-validators-for-elections). Get the actual values [for mainnet](https://tonviewer.com/config#16) and [for testnet](https://testnet.tonviewer.com/config#16). +Read more about `max_validators` and `max_main_validators` [on config parameters page](/v3/documentation/network/configs/blockchain-configs#configuration-parameters-for-the-number-of-validators-for-elections). Get the actual values [for mainnet](https://tonviewer.com/config#16) and [for testnet](https://testnet.tonviewer.com/config#16). ## Pool commands diff --git a/docs/v3/documentation/network/configs/config-params.md b/docs/v3/documentation/network/configs/config-params.md index 93eb82b8b7..57b7517f3a 100644 --- a/docs/v3/documentation/network/configs/config-params.md +++ b/docs/v3/documentation/network/configs/config-params.md @@ -2,7 +2,7 @@ The aim of this document is to provide a basic explanation of configuration parameters of TON Blockchain, and to give step-by-step instructions for changing these parameters by a consensus of a majority of validators. -We assume that the reader is already familiar with [Fift](/v3/documentation/smart-contracts/fift/overview) and the [Lite Client](/v3/guidelines/nodes/running-nodes/liteserver-node), as explained in [FullNode-HOWTO (low-level)](/docs/v3/guidelines/nodes/running-nodes/full-node), and [Validator-HOWTO (low-level)](/v3/guidelines/nodes/running-nodes/validator-node) in the sections where validators' voting for the configuration proposals is described. +We assume that the reader is already familiar with [Fift](/v3/documentation/smart-contracts/fift/overview) and the [Lite Client](/v3/guidelines/nodes/running-nodes/liteserver-node), as explained in [FullNode-HOWTO (low-level)](/v3/guidelines/nodes/running-nodes/full-node), and [Validator-HOWTO (low-level)](/v3/guidelines/nodes/running-nodes/validator-node) in the sections where validators' voting for the configuration proposals is described. ## 1. Configuration parameters The **configuration parameters** are certain values that affect the behavior of validators and/or fundamental smart contracts of TON Blockchain. The current values of all configuration parameters are stored as a special part of the masterchain state and are extracted from the current masterchain state when needed. Therefore, it makes sense to speak of the values of the configuration parameters with respect to a certain masterchain block. Each shardchain block contains a reference to the latest known masterchain block; the values from the corresponding masterchain state are assumed to be active for this shardchain block and are used during its generation and validation. For masterchain blocks, the state of the previous masterchain block is used to extract the active configuration parameters. Therefore, even if one tries to change some configuration parameters inside a masterchain block, the changes will become active only for the next masterchain block. diff --git a/docs/v3/documentation/network/configs/network-configs.md b/docs/v3/documentation/network/configs/network-configs.md index 8be0ed1065..d98bd9b049 100644 --- a/docs/v3/documentation/network/configs/network-configs.md +++ b/docs/v3/documentation/network/configs/network-configs.md @@ -7,5 +7,5 @@ On this page you can find active network configs of TON Blockchain: ## See Also -- [Node Types](v3/documentation/infra/nodes/node-types) +- [Node Types](/v3/documentation/infra/nodes/node-types) - [Blockchain Params Config](/v3/documentation/network/configs/blockchain-configs) diff --git a/docs/v3/documentation/smart-contracts/contracts-specs/wallet-contracts.md b/docs/v3/documentation/smart-contracts/contracts-specs/wallet-contracts.md index f105024822..4c8d90e840 100644 --- a/docs/v3/documentation/smart-contracts/contracts-specs/wallet-contracts.md +++ b/docs/v3/documentation/smart-contracts/contracts-specs/wallet-contracts.md @@ -134,7 +134,7 @@ Also op-code, op::code and operational code |-----------------|-----------------|----------------------------| | Global | 0x00000000 | Text Comment | | Global | 0xffffffff | Bounce | -| Global | 0x2167da4b | [Encrypted Comment](v3/documentation/smart-contracts/message-management/internal-messages#messages-with-encrypted-comments) | +| Global | 0x2167da4b | [Encrypted Comment](/v3/documentation/smart-contracts/message-management/internal-messages#messages-with-encrypted-comments) | | Global | 0xd53276db | Excesses | | Elector | 0x4e73744b | New Stake | | Elector | 0xf374484c | New Stake Confirmation | diff --git a/docs/v3/documentation/smart-contracts/func/cookbook.md b/docs/v3/documentation/smart-contracts/func/cookbook.md index 5680d5c6b2..3fc52407d8 100644 --- a/docs/v3/documentation/smart-contracts/func/cookbook.md +++ b/docs/v3/documentation/smart-contracts/func/cookbook.md @@ -735,7 +735,7 @@ if (current_time > 1672080143) { :::caution draft Please note that this method of generating random numbers isn't safe. -Checkout [Random Number Generation](v3/guidelines/smart-contracts/securier-generation) for more information. +Checkout [Random Number Generation](/v3/guidelines/smart-contracts/security/random-number-generation) for more information. :::,. ```func diff --git a/docs/v3/documentation/smart-contracts/func/docs/dictionaries.md b/docs/v3/documentation/smart-contracts/func/docs/dictionaries.md index 548912ba20..8329da1133 100644 --- a/docs/v3/documentation/smart-contracts/func/docs/dictionaries.md +++ b/docs/v3/documentation/smart-contracts/func/docs/dictionaries.md @@ -24,7 +24,7 @@ Possible operations for hashmaps: - load from slice, store to builder - get/set/delete value by key - replace value (set new value if key was already present) / add one (if key was not present) -- move to next/previous key-value pair, in order of keys (this can be used to [iterate over dictionaries](v3/documentation/smart-contracts/func/cookbook#how-to-iterate-dictionaries) if gas limit is not a concern) +- move to next/previous key-value pair, in order of keys (this can be used to [iterate over dictionaries](/v3/documentation/smart-contracts/func/cookbook#how-to-iterate-dictionaries) if gas limit is not a concern) - retrieve minimal/maximal key with its value - get function (continuation) by key and immediately execute it diff --git a/docs/v3/documentation/smart-contracts/message-management/internal-messages.md b/docs/v3/documentation/smart-contracts/message-management/internal-messages.md index 11f457d685..819cb55d2c 100644 --- a/docs/v3/documentation/smart-contracts/message-management/internal-messages.md +++ b/docs/v3/documentation/smart-contracts/message-management/internal-messages.md @@ -59,7 +59,7 @@ If `op` is `0x2167da4b`, then the message is a "transfer message with encrypted Encryption algo is as follows: 1. Calculate `shared_secret` using `priv_1` and `pub_2`. - 2. Let `salt` be the [bas64url representation](v3/documentation/smart-contracts/addresses#user-friendly-address) of the sender wallet address with `isBounceable=1` and `isTestnetOnly=0`. + 2. Let `salt` be the [bas64url representation](/v3/documentation/smart-contracts/addresses#user-friendly-address) of the sender wallet address with `isBounceable=1` and `isTestnetOnly=0`. 3. Select byte string `prefix` of length between 16 and 31 such that `len(prefix+msg)` is divisible by 16. The first byte of `prefix` is equal to `len(prefix)`, other bytes are random. Let `data = prefix + msg`. 4. Let `msg_key` be the first 16 bytes of `hmac_sha512(salt, data)`. 5. Calculate `x = hmac_sha512(shared_secret, msg_key)`. Let `key=x[0:32]` and `iv=x[32:48]`. diff --git a/docs/v3/documentation/smart-contracts/shards/shards-intro.mdx b/docs/v3/documentation/smart-contracts/shards/shards-intro.mdx index 836f3fbe00..6961dda92f 100644 --- a/docs/v3/documentation/smart-contracts/shards/shards-intro.mdx +++ b/docs/v3/documentation/smart-contracts/shards/shards-intro.mdx @@ -65,5 +65,5 @@ An actual example: ## See Also -* [Infinity Sharding Paradigm](/v3/documentation/smart-contracts/infinity-sharding-paradigm) +* [Infinity Sharding Paradigm](/v3/documentation/smart-contracts/shards/infinity-sharding-paradigm) * [Whitepapers](/v3/documentation/whitepapers/overview) diff --git a/docs/v3/documentation/tvm/changelog/tvm-upgrade-2023-07.md b/docs/v3/documentation/tvm/changelog/tvm-upgrade-2023-07.md index fa7dd679c4..2b57dc5ab2 100644 --- a/docs/v3/documentation/tvm/changelog/tvm-upgrade-2023-07.md +++ b/docs/v3/documentation/tvm/changelog/tvm-upgrade-2023-07.md @@ -68,7 +68,7 @@ Rule of thumb when choosing gas cost on new opcodes is that it should not be les | `GASCONSUMED` | _`- g_c`_ | Returns gas consumed by VM so far (including this instruction).
_26 gas_ | ## Arithmetics -New variants of [the division opcode](v3/documentation/tvm/instructions#52-division) (`A9mscdf`) are added: +New variants of [the division opcode](/v3/documentation/tvm/instructions#52-division) (`A9mscdf`) are added: `d=0` takes one additional integer from stack and adds it to the intermediate value before division/rshift. These operations return both the quotient and the remainder (just like `d=3`). Quiet variants are also available (e.g. `QMULADDDIVMOD` or `QUIET MULADDDIVMOD`). diff --git a/docs/v3/documentation/tvm/tvm-initialization.md b/docs/v3/documentation/tvm/tvm-initialization.md index 9c8a0170f2..6b35346075 100644 --- a/docs/v3/documentation/tvm/tvm-initialization.md +++ b/docs/v3/documentation/tvm/tvm-initialization.md @@ -174,7 +174,7 @@ First component of this tuple is an _Integer_ value, which is always equal to 0x | `actions` | uint16 | Originally initialized by 0, but incremented by one whenever an output action is installed by a non-RAW output action primitive | | `msgs_sent` | uint16 | Number of messages sent | | `unixtime` | uint32 | Unix timestamp in seconds | -| `block_lt` | uint64 | Represents _logical time_ of the previous block of this account. [More about logical time](v3/documentation/smart-contracts/message-management/messages-and-transactions#what-is-a-logical-time) | +| `block_lt` | uint64 | Represents _logical time_ of the previous block of this account. [More about logical time](/v3/documentation/smart-contracts/message-management/messages-and-transactions#what-is-a-logical-time) | | `trans_lt` | uint64 | Represents _logical time_ of the previous transaction of this account | | `rand_seed` | bits256 | Initialized deterministically starting from `rand_seed` of the block, the account address, the hash of the incoming message being processed (if any), and the transaction logical time `trans_lt` | | `balance_remaining` | [CurrencyCollection](/v3/documentation/data-formats/tlb/msg-tlb#currencycollection) | Remaining balance of the smart contract | diff --git a/docs/v3/documentation/whitepapers/overview.md b/docs/v3/documentation/whitepapers/overview.md index fd7b8e4264..2a59c8c71b 100644 --- a/docs/v3/documentation/whitepapers/overview.md +++ b/docs/v3/documentation/whitepapers/overview.md @@ -14,7 +14,7 @@ Please note that here and later the code, comments and/or documentation may cont * [TON Virtual Machine](https://docs.ton.org/tvm.pdf) - TON Virtual Machine description(may include outdated information on OP Codes, actual list in [TVM Instruction](v3/documentation/tvm/tvm-overview) section). + TON Virtual Machine description(may include outdated information on OP Codes, actual list in [TVM Instruction](/v3/documentation/tvm/tvm-overview) section). * [TON Blockchain](https://docs.ton.org/tblkch.pdf) diff --git a/docs/v3/guidelines/dapps/apis-sdks/ton-adnl-apis.md b/docs/v3/guidelines/dapps/apis-sdks/ton-adnl-apis.md index c1a2aea589..d46226b7e2 100644 --- a/docs/v3/guidelines/dapps/apis-sdks/ton-adnl-apis.md +++ b/docs/v3/guidelines/dapps/apis-sdks/ton-adnl-apis.md @@ -23,7 +23,7 @@ Read more about [Merkle proofs](/v3/documentation/data-formats/tlb/proofs) at [T Public liteservers (from the global config) exist to get you started with TON quickly. It can be used for learning to program in TON, or for applications and scripts that do not require 100% uptime. For building production infrastructure - it is suggested use well prepared infrastructure: -- [set up own liteserver](v3/guidelines/nodes/running-nodes/full-node#enable-liteserver-mode), +- [set up own liteserver](/v3/guidelines/nodes/running-nodes/full-node#enable-liteserver-mode), - use Liteserver premium providers [@liteserver_bot](https://t.me/liteserver_bot) ## Pros & Cons diff --git a/docs/v3/guidelines/dapps/asset-processing/jettons.md b/docs/v3/guidelines/dapps/asset-processing/jettons.md index c599075058..69f87b8f0b 100644 --- a/docs/v3/guidelines/dapps/asset-processing/jettons.md +++ b/docs/v3/guidelines/dapps/asset-processing/jettons.md @@ -14,7 +14,7 @@ TON transactions are irreversible after just one confirmation. For the best UX/U #### Withdrawal -[Highload Wallet v3](v3/documentation/smart-contracts/contracts-specs/highload-wallet#highload-wallet-v3) - this is TON Blockchain latest solution which is the gold standard for jetton withdrawals. It allows you to take advantage of batched withdrawals. +[Highload Wallet v3](/v3/documentation/smart-contracts/contracts-specs/highload-wallet#highload-wallet-v3) - this is TON Blockchain latest solution which is the gold standard for jetton withdrawals. It allows you to take advantage of batched withdrawals. [Batched withdrawals](https://github.com/toncenter/examples/blob/main/withdrawals-jettons-highload-batch.js) - Meaning that multiple withdrawals are sent in batches, allowing for quick and cheap withdrawals. @@ -71,7 +71,7 @@ For the best user experience, it is suggested to avoid waiting on additional blo Quick jump to the core description of jetton processing: - +