diff --git a/.remarkrc.js b/.remarkrc.js index 3ea7b4a99f9..ddde7030e7d 100644 --- a/.remarkrc.js +++ b/.remarkrc.js @@ -9,5 +9,6 @@ module.exports = { 'remark-lint-rule-style', 'remark-gfm', ['remark-lint-unordered-list-marker-style', '-'], + 'remark-lint-docusaurus-empty-lines-around-admonition-content' ], }; diff --git a/docs/v3/concepts/dive-into-ton/go-from-ethereum/difference-of-blockchains.mdx b/docs/v3/concepts/dive-into-ton/go-from-ethereum/difference-of-blockchains.mdx index 6c47ca31d19..ca9fbea1315 100644 --- a/docs/v3/concepts/dive-into-ton/go-from-ethereum/difference-of-blockchains.mdx +++ b/docs/v3/concepts/dive-into-ton/go-from-ethereum/difference-of-blockchains.mdx @@ -89,7 +89,9 @@ When the wallet smart contract receives the message, it processes it and deliver We can represent the sequence of transactions as a chain. In this representation, each smart contract has its transactions, which means that each contract has its blockchain, so the network can process the transactions independently. :::info + Read more in [Blockchain of blockchain](/v3/concepts/dive-into-ton/ton-blockchain/blockchain-of-blockchains). + ::: ### Gas @@ -126,7 +128,9 @@ In TON, the calculation of transaction fees is complex. It includes several type The price of gas and some other parameters can be changed by voting on the main network. Unlike Ethereum, TON users cannot set the gas price themselves. Also, the developer needs to return the remaining gas funds to the owner manually, otherwise they will remain locked. Smart contract storage also affects the price: if a wallet's smart contract remains unused for a long time, the next transaction will incur higher costs. :::info + Read more about [gas](/v3/documentation/smart-contracts/transaction-fees/fees). + ::: ### Architecture diff --git a/docs/v3/concepts/dive-into-ton/ton-blockchain/accounts.mdx b/docs/v3/concepts/dive-into-ton/ton-blockchain/accounts.mdx index d6b64859d2e..b6599e5c6ec 100644 --- a/docs/v3/concepts/dive-into-ton/ton-blockchain/accounts.mdx +++ b/docs/v3/concepts/dive-into-ton/ton-blockchain/accounts.mdx @@ -16,7 +16,9 @@ Each account consists of: - **Code** — the logic that determines how the account reacts to incoming messages and generates outgoing ones. This defines the account’s behavior on the blockchain. :::note + Accounts that include both **code** and **data**, in addition to their properties, are considered **smart contracts** on the blockchain. + ::: diff --git a/docs/v3/concepts/dive-into-ton/ton-blockchain/cells-as-data-storage.mdx b/docs/v3/concepts/dive-into-ton/ton-blockchain/cells-as-data-storage.mdx index 51a638d4a0d..3f4efc266ea 100644 --- a/docs/v3/concepts/dive-into-ton/ton-blockchain/cells-as-data-storage.mdx +++ b/docs/v3/concepts/dive-into-ton/ton-blockchain/cells-as-data-storage.mdx @@ -37,7 +37,9 @@ The exotic types are the following: - Merkle update cell :::tip + See [**Exotic cells**](https://ton.org/tvm.pdf). + ::: ## Cell flavors diff --git a/docs/v3/concepts/dive-into-ton/ton-ecosystem/wallet-apps.mdx b/docs/v3/concepts/dive-into-ton/ton-ecosystem/wallet-apps.mdx index 22afda15e0c..17df33b736f 100644 --- a/docs/v3/concepts/dive-into-ton/ton-ecosystem/wallet-apps.mdx +++ b/docs/v3/concepts/dive-into-ton/ton-ecosystem/wallet-apps.mdx @@ -137,8 +137,10 @@ Below is a selection of prominent non-custodial software wallets. :::warning + [TONDevWallet](https://github.com/TonDevWallet/TonDevWallet) is for development and testing only. Do **NOT** use it to store real funds — it is **insecure** and does **NOT** provide adequate protection. + ::: diff --git a/docs/v3/contribute/README.mdx b/docs/v3/contribute/README.mdx index f76c5a8f3fb..e162b7f4061 100644 --- a/docs/v3/contribute/README.mdx +++ b/docs/v3/contribute/README.mdx @@ -1,7 +1,9 @@ # How to contribute :::info + Learn how to submit content to TON documentation here. + ::: ## Contribute rules @@ -17,7 +19,9 @@ We aim to educate users about TON through explicit, easily searchable content th ### How to contribute :::info + This documentation is written in English. Please refer to [localization program](/v3/contribute/localization-program/how-to-contribute/) for other languages. + ::: 1. Clone a current version from the [ton-docs](https://github.com/ton-community/ton-docs) GitHub repository. @@ -46,7 +50,9 @@ Closes [link to issue]. 4. Before submitting your pull request, complete and verify each milestone in the description checklist. :::info + To avoid excessive rework, read the contribution guidelines in the [Style guide](/v3/contribute/style-guide/), [Content standardization](/v3/contribute/content-standardization/), and [Typography](/v3/contribute/typography/) before contributing. Don't worry about minor issues; maintainers will help you fix them during the review process. + ::: ### Development diff --git a/docs/v3/contribute/contribution-rules.mdx b/docs/v3/contribute/contribution-rules.mdx index 07a2b28cbc7..1199e4e5339 100644 --- a/docs/v3/contribute/contribution-rules.mdx +++ b/docs/v3/contribute/contribution-rules.mdx @@ -3,8 +3,10 @@ import Feedback from '@site/src/components/Feedback'; # Contribution Guidelines :::danger + This page is outdated and will be deleted soon. See the [How to contribute](/v3/contribute/). + ::: Before contributing any docs.ton.org page, please review the following list of general and important requirements to guarantee a smooth experience. @@ -15,11 +17,13 @@ Before contributing any docs.ton.org page, please review the following list of g - We write _TON_ with regular nouns, and if it requires _THE_ according to English grammar, we use it. For instance: "_The_ TON Connect _protocol_ is a..." :::info + TON Blockchain... TON Ecosystem... The TON Connect protocol... + ::: Please refer to the actual TON brand assets [here](https://ton.org/en/brand-assets). diff --git a/docs/v3/contribute/docs/guidelines.mdx b/docs/v3/contribute/docs/guidelines.mdx index caba14dd636..ed2a08e69ab 100644 --- a/docs/v3/contribute/docs/guidelines.mdx +++ b/docs/v3/contribute/docs/guidelines.mdx @@ -3,8 +3,10 @@ import Feedback from '@site/src/components/Feedback'; # Common Documentation Principals :::danger + This page is outdated and will be deleted soon. See the [How to contribute](/v3/contribute/). + ::: For optimal user experience and clarity, please keep in mind the list of general and important requirements that we aim to apply to all documentation on docs.ton.org while creating new content. diff --git a/docs/v3/contribute/docs/schemes-guidelines.mdx b/docs/v3/contribute/docs/schemes-guidelines.mdx index 95c4c8b679a..370a4f6c33e 100644 --- a/docs/v3/contribute/docs/schemes-guidelines.mdx +++ b/docs/v3/contribute/docs/schemes-guidelines.mdx @@ -6,8 +6,10 @@ import ThemedImage from '@theme/ThemedImage'; # Graphic Explanations Guidelines :::danger + This page is outdated and will be deleted soon. See the [How to contribute](/v3/contribute/). + ::: Maintaining consistency in documentation is crucial, and to achieve this, a specific standard for visualizing processes in smart contracts has been developed. diff --git a/docs/v3/contribute/localization-program/how-it-works.mdx b/docs/v3/contribute/localization-program/how-it-works.mdx index 4382e5796fe..3318c23ee8f 100644 --- a/docs/v3/contribute/localization-program/how-it-works.mdx +++ b/docs/v3/contribute/localization-program/how-it-works.mdx @@ -14,7 +14,9 @@ Within this system, we integrate several applications to function seamlessly as - **Customized Glossary**: This glossary guides translators and ensures AI generates accurate translations based on the project’s context. Users can also upload their glossaries as needed. :::info + This guide won't cover the entire process but will highlight the key components that make the TownSquare Labs Localization Program unique. You can explore the program further on your own. + ::: ## GitHub synchronization for documentation and translations diff --git a/docs/v3/contribute/localization-program/how-to-contribute.mdx b/docs/v3/contribute/localization-program/how-to-contribute.mdx index 2aa193c0648..d0ae5be4cc9 100644 --- a/docs/v3/contribute/localization-program/how-to-contribute.mdx +++ b/docs/v3/contribute/localization-program/how-to-contribute.mdx @@ -15,7 +15,9 @@ Localization contribution is open to everyone. Here are a few steps you need to 5. Preview all translation results on the website after proofreading. :::info + Before contributing, read the guidelines below to ensure standardization and quality, speeding up the review process. + ::: ## Side-by-side mode @@ -82,9 +84,11 @@ Click on a file to enter the editing interface. ![proofread approved](/img/localizationProgramGuideline/proofread-approved.png) :::info + You can also review the approved lines: 1. Filter by **Approved**. 2. If an approved line has issues, click the ☑️ button to revert it to needing proofreading. + ::: 3. To move to the following file, click the file name at the top, select the new file from the pop-up window, and continue proofreading. diff --git a/docs/v3/contribute/localization-program/translation-style-guide.mdx b/docs/v3/contribute/localization-program/translation-style-guide.mdx index aaf10969313..95a480b8e03 100644 --- a/docs/v3/contribute/localization-program/translation-style-guide.mdx +++ b/docs/v3/contribute/localization-program/translation-style-guide.mdx @@ -64,7 +64,9 @@ Some strings contain titles of external articles. Most of our developer document Crowdin has a built-in feature that warns translators when they are about to make a mistake. Crowdin will automatically alert you before saving your translation if you forget to include a tag from the source, translate elements that should not be translated, add several consecutive spaces, forget end punctuation, etc. If you see a warning like this, please double-check the suggested translation. :::warning + Never ignore these warnings, as they usually mean something is wrong or the translation lacks a key part of the source text. + ::: ## Short vs. complete forms and abbreviations diff --git a/docs/v3/contribute/participate.mdx b/docs/v3/contribute/participate.mdx index 5e7548e649f..9ddedf87a7c 100644 --- a/docs/v3/contribute/participate.mdx +++ b/docs/v3/contribute/participate.mdx @@ -4,14 +4,18 @@ import Feedback from '@site/src/components/Feedback'; # Contribution Guide :::danger + This page is outdated and will be deleted soon. See the [How to contribute](/v3/contribute/). + ::: Here is a step-by-step guide of contributing to TON Documentation with Tutorials. :::tip opportunity + You're lucky! It's a good opportunity to improve TON Ecosystem here. + ::: If you decide to write tutorial, you can get some reward for outstanding materials: diff --git a/docs/v3/contribute/style-guide.mdx b/docs/v3/contribute/style-guide.mdx index 9e103ed0d43..577522d09fc 100644 --- a/docs/v3/contribute/style-guide.mdx +++ b/docs/v3/contribute/style-guide.mdx @@ -142,7 +142,9 @@ TON Documentation aims to serve as a credible, neutral source of truth that info - Example: _"This political party is better for decentralization because..."_ :::warning + Any proposed content that does not align with the platform's objectives will be rejected without additional explanation. Spam and inappropriate behavior in comments will result in a ban. + ::: ### Consistency diff --git a/docs/v3/contribute/tutorials/guidelines.mdx b/docs/v3/contribute/tutorials/guidelines.mdx index dba2f37590c..e76955f5e5c 100644 --- a/docs/v3/contribute/tutorials/guidelines.mdx +++ b/docs/v3/contribute/tutorials/guidelines.mdx @@ -3,8 +3,10 @@ import Feedback from '@site/src/components/Feedback'; # Tutorial Styling Guidelines :::danger + This page is outdated and will be updated soon. See the [How to contribute](/v3/contribute/). + ::: So you've decided to write a tutorial for TON Documentation? @@ -16,7 +18,9 @@ It is important that you take some time to become familiar with the tutorial str ## Process :::info IMPORTANT + Before you start writing, *read the guidelines below*! They will help you ensure the level of standardization and quality that will make the review process much faster. + ::: Also, be sure to refer to the [**sample tutorial structure**](/v3/contribute/tutorials/sample-tutorial) we have provided. @@ -65,7 +69,9 @@ Regarding other word combinations like "TON + noun" (e.g., "the TON world," "the ## How to structure your tutorial :::info Sample tutorial structure + Feel free to check out the [sample tutorial structure](/v3/contribute/tutorials/sample-tutorial) to see it with your own eyes. + ::: - The **Title** should be direct and clear, summarizing the tutorial's goal. Do not add the tutorial title as a heading inside the document; instead, use the markdown document filename. diff --git a/docs/v3/contribute/tutorials/principles-of-a-good-tutorial.mdx b/docs/v3/contribute/tutorials/principles-of-a-good-tutorial.mdx index ec92dab3899..de151eb1fe2 100644 --- a/docs/v3/contribute/tutorials/principles-of-a-good-tutorial.mdx +++ b/docs/v3/contribute/tutorials/principles-of-a-good-tutorial.mdx @@ -3,8 +3,10 @@ import Feedback from '@site/src/components/Feedback'; # Principles of a good tutorial :::danger + This page is outdated and will be updated soon. See the [How to contribute](/v3/contribute/). + ::: Original comment with these principles by [talkol](https://github.com/talkol): diff --git a/docs/v3/contribute/tutorials/sample-tutorial.mdx b/docs/v3/contribute/tutorials/sample-tutorial.mdx index 979013bac28..59b513ef517 100644 --- a/docs/v3/contribute/tutorials/sample-tutorial.mdx +++ b/docs/v3/contribute/tutorials/sample-tutorial.mdx @@ -3,8 +3,10 @@ import Feedback from '@site/src/components/Feedback'; # Sample tutorial structure :::danger + This page is outdated and will be updated soon. See the [How to contribute](/v3/contribute/). + ::: ## Introduction diff --git a/docs/v3/contribute/typography.mdx b/docs/v3/contribute/typography.mdx index a7956e89e35..499cdebb92d 100644 --- a/docs/v3/contribute/typography.mdx +++ b/docs/v3/contribute/typography.mdx @@ -122,7 +122,9 @@ The navigation menus should remain minimalistic in both the left sidebar and the - Use short, clear labels of two or three words. :::info + Specify the left side menu with [sidebars](https://github.com/ton-community/ton-docs/tree/main/sidebars) configuration files. + ::: #### Navigation bar menu: @@ -131,7 +133,9 @@ Specify the left side menu with [sidebars](https://github.com/ton-community/ton- - Use broad, descriptive terms to categorize content, ensuring users can quickly identify the main section they need. :::info + Specify the navigation bar menu with the [navbar.js](https://github.com/ton-community/ton-docs/blob/main/navbar.js) configuration file. + ::: #### Consistency between menu and in-page headers diff --git a/docs/v3/documentation/archive/hacktoberfest-2022/README.mdx b/docs/v3/documentation/archive/hacktoberfest-2022/README.mdx index 25e8b49417a..b1f5fd0403e 100644 --- a/docs/v3/documentation/archive/hacktoberfest-2022/README.mdx +++ b/docs/v3/documentation/archive/hacktoberfest-2022/README.mdx @@ -38,7 +38,9 @@ To motivate the community to contribute to open source projects in the TON Ecosy :::info IMPORTANT! + TON Foundation will mint a collection in November to all wallet addresses submitted to the [@toncontests_bot](https://t.me/toncontests_bot). It will happen after the calculation and validation of all contribution results. + ::: You have plenty of time to participate in the event. Let's build decentralized Internet of the future with thousands of contributors from all over the world! diff --git a/docs/v3/documentation/archive/mining.mdx b/docs/v3/documentation/archive/mining.mdx index a238758de92..9121b49c7d8 100644 --- a/docs/v3/documentation/archive/mining.mdx +++ b/docs/v3/documentation/archive/mining.mdx @@ -3,7 +3,9 @@ import Feedback from '@site/src/components/Feedback'; # TON mining guide :::warning deprecated + This information may be outdated and no longer relevant. You can skip it. + ::: diff --git a/docs/v3/documentation/archive/pow-givers.mdx b/docs/v3/documentation/archive/pow-givers.mdx index 8039e68ac6f..c4359249385 100644 --- a/docs/v3/documentation/archive/pow-givers.mdx +++ b/docs/v3/documentation/archive/pow-givers.mdx @@ -3,7 +3,9 @@ import Feedback from '@site/src/components/Feedback'; # POW Givers :::warning deprecated + This information may be outdated and no longer relevant. You can skip it. + ::: The aim of this text is to describe how to interact with Proof-of-Work Giver smart contracts to obtain Toncoin. We assume familiarity with TON Blockchain Lite Client as explained in `Getting Started`, and with the procedure required to compile the Lite Client and other software. For obtaining the larger amount of Toncoin required for running a validator, we also assume acquaintance with the `Full Node` and `Validator` pages. You will also need a dedicated server powerful enough for running a Full Node in order to obtain the larger amount of Toncoin. Obtaining small amounts of Toncoin does not require a dedicated server and may be done in several minutes on a home computer. @@ -120,7 +122,9 @@ Then you can use the Lite Client to send an external message from file `mined.bo You can wait for several seconds and check the state of your wallet: :::info + Please note here and further that the code, comments, and/or documentation may contain parameters, methods, and definitions such as “gram”, “nanogram”, etc. That is a legacy of the original TON code, developed by the Telegram. Gram cryptocurrency was never issued. The currency of TON is Toncoin and the currency of the TON testnet is Test Toncoin. + ::: ``` diff --git a/docs/v3/documentation/archive/precompiled-binaries.mdx b/docs/v3/documentation/archive/precompiled-binaries.mdx index 1d4f884c78b..20c2c8f5356 100644 --- a/docs/v3/documentation/archive/precompiled-binaries.mdx +++ b/docs/v3/documentation/archive/precompiled-binaries.mdx @@ -7,7 +7,9 @@ import Button from '@site/src/components/button' # Precompiled binaries :::caution important + You no longer need to manually install binaries with Blueprint SDK. + ::: All binaries for development and testing are provided with the Blueprint SDK. @@ -85,7 +87,9 @@ padding: '0.2rem', 4. In the "_Variable value_" field, specify the path to the files: **`/%USERNAME%/ton/lib/fiftlib`** and click OK. Done. :::caution important + Instead of the `%USERNAME%` keyword, you must insert your own `username`. + ::: @@ -122,7 +126,9 @@ Instead of the `%USERNAME%` keyword, you must insert your own `username`. ``` :::info Hey, you're almost finished :) + Remember to set the [environment variable](https://stackoverflow.com/questions/14637979/how-to-permanently-set-path-on-linux-unix) `FIFTPATH` to point to this directory. + ::: diff --git a/docs/v3/documentation/archive/tg-bot-integration-py.mdx b/docs/v3/documentation/archive/tg-bot-integration-py.mdx index f79181496b1..01d9217dad2 100644 --- a/docs/v3/documentation/archive/tg-bot-integration-py.mdx +++ b/docs/v3/documentation/archive/tg-bot-integration-py.mdx @@ -5,7 +5,9 @@ import Button from '@site/src/components/button' # TON Connect for Telegram Bots - Python :::warning deprecated + This guide explains an outdated method of integrating TON Connect with Telegram bots. For a more secure and modern approach, consider using [Telegram Mini Apps](/v3/guidelines/dapps/tma/overview for a more modern and secure integration. + ::: In this tutorial, we’ll create a sample telegram bot that supports TON Connect 2.0 authentication using Python TON Connect SDK [pytonconnect](https://github.com/XaBbl4/pytonconnect). diff --git a/docs/v3/documentation/archive/tg-bot-integration.mdx b/docs/v3/documentation/archive/tg-bot-integration.mdx index 663a179fe2d..595333c63e7 100644 --- a/docs/v3/documentation/archive/tg-bot-integration.mdx +++ b/docs/v3/documentation/archive/tg-bot-integration.mdx @@ -5,7 +5,9 @@ import Button from '@site/src/components/button' # TON Connect for Telegram Bots :::warning deprecated + This guide explains an outdated method of integrating TON Connect with Telegram bots. For a more secure and modern approach, consider using [Telegram Mini Apps](/v3/guidelines/dapps/tma/overview) for a more modern and secure integration. + ::: In this tutorial, we will develop a sample Telegram bot using the JavaScript TON Connect SDK, supporting TON Connect 2.0 authentication. diff --git a/docs/v3/documentation/dapps/assets/nft-2.0.mdx b/docs/v3/documentation/dapps/assets/nft-2.0.mdx index 89ea6bfe6b1..0b2a64c0e56 100644 --- a/docs/v3/documentation/dapps/assets/nft-2.0.mdx +++ b/docs/v3/documentation/dapps/assets/nft-2.0.mdx @@ -38,7 +38,9 @@ The execution model of the proposed royalty-enforcing solution includes both on- - Off-chain metadata includes pack configuration and sale logic: number of items per pack, royalty rules, and mutable fields (e.g., `royalty_violation`). :::info Mint API + Refer to the [Mint Platform API](https://api.getgems.io/mint-platform/docs) for detailed integration information and endpoints. + ::: **2. NFT store integration:** NFT stores integrate solely through the mint API and do not interact with smart contracts directly. @@ -234,9 +236,9 @@ This diagram illustrates the end-to-end data flow of NFT 2.0 item distribution t ## See also -* [NFT standard: TEP-62](https://github.com/ton-blockchain/TEPs/blob/master/text/0062-nft-standard.md) -* [NFT royalty standard extension: TEP-66](https://github.com/ton-blockchain/TEPs/blob/master/text/0066-nft-royalty-standard.md) -* [NFT processing](/v3/guidelines/dapps/asset-processing/nft-processing/nfts) +- [NFT standard: TEP-62](https://github.com/ton-blockchain/TEPs/blob/master/text/0062-nft-standard.md) +- [NFT royalty standard extension: TEP-66](https://github.com/ton-blockchain/TEPs/blob/master/text/0066-nft-royalty-standard.md) +- [NFT processing](/v3/guidelines/dapps/asset-processing/nft-processing/nfts) diff --git a/docs/v3/documentation/dapps/assets/overview.mdx b/docs/v3/documentation/dapps/assets/overview.mdx index 48ed4438d3a..ed86a517b3f 100644 --- a/docs/v3/documentation/dapps/assets/overview.mdx +++ b/docs/v3/documentation/dapps/assets/overview.mdx @@ -38,7 +38,9 @@ That `transactions` can span a **prolonged period** of time. Technically, transa The `transaction` accepted to the block is final and cannot be modified. :::info Transaction Confirmation + TON transactions are irreversible after just one confirmation. For the best user experience, it is suggested to avoid waiting on additional blocks once transactions are finalized on the TON Blockchain. Read more in the [Catchain.pdf](https://docs.ton.org/catchain.pdf#page=3). + ::: Smart contracts pay several types of [fees](/v3/documentation/smart-contracts/transaction-fees/fees) for transactions (usually from the balance of an incoming message, behavior depends on [message mode](/v3/documentation/smart-contracts/message-management/sending-messages#message-modes)). Amount of fees depends on workchain configs with maximal fees on `masterchain` and substantially lower fees on `basechain`. diff --git a/docs/v3/documentation/dapps/assets/usdt.mdx b/docs/v3/documentation/dapps/assets/usdt.mdx index 5f8ee2ab6b0..df45c21bf8d 100644 --- a/docs/v3/documentation/dapps/assets/usdt.mdx +++ b/docs/v3/documentation/dapps/assets/usdt.mdx @@ -11,8 +11,10 @@ import Button from '@site/src/components/button' In TON Blockchain USD₮ supported as a [Jetton asset](/v3/guidelines/dapps/asset-processing/jettons). :::info + To integrate Tether’s USD₮ Token on TON Blockchain use the contract address: [EQCxE6mUtQJKFnGfaROTKOt1lZbDiiX1kCixRv7Nw2Id_sDs](https://tonviewer.com/EQCxE6mUtQJKFnGfaROTKOt1lZbDiiX1kCixRv7Nw2Id_sDs?section=jetton) + ::: @@ -45,9 +47,11 @@ TON’s high throughput and rapid confirmation times enable USD₮ transactions ## Advanced details :::caution IMPORTANT + In TON Blockchain jettons can be created with duplicate names. Technically, it will not differ in any way from the real USD₮ but it will have no value because of no security. You can verify legitimacy and check for fraud only by confirming the Jetton Master address. See important [recommendations](/v3/guidelines/dapps/asset-processing/jettons). + ::: ## See also diff --git a/docs/v3/documentation/dapps/defi/subscriptions.mdx b/docs/v3/documentation/dapps/defi/subscriptions.mdx index f5431db8f4d..c40d69b9a2e 100644 --- a/docs/v3/documentation/dapps/defi/subscriptions.mdx +++ b/docs/v3/documentation/dapps/defi/subscriptions.mdx @@ -7,13 +7,17 @@ Due to the fact that transactions in TON Blockchain are fast and the network fee For example, users can subscribe to digital content (or anything else) and be charged a monthly fee of 1 TON. :::tip + This content is specific for wallets of version v4. Older wallets don't have this functionality; it is eligible to change in future versions as well. + ::: :::warning + Subscription contract requires authorization exactly once, on installation; then it can withdraw TON as it pleases. Do your own research before attaching unknown subscriptions. On the other hand, user can't get subscription installed without their knowledge. + ::: ## Example flow diff --git a/docs/v3/documentation/dapps/defi/tokens.mdx b/docs/v3/documentation/dapps/defi/tokens.mdx index 06a3dff2c52..e4940acd8ad 100644 --- a/docs/v3/documentation/dapps/defi/tokens.mdx +++ b/docs/v3/documentation/dapps/defi/tokens.mdx @@ -17,8 +17,10 @@ import Button from '@site/src/components/button' ## TON Course: jettons & NFTs :::tip + Before starting the course, make sure you have a good understanding of the basics of blockchain technology. If you have gaps in your knowledge, we recommend taking the [Blockchain Basics with TON](https://stepik.org/course/201294/promo) ([RU version](https://stepik.org/course/202221/), [CHN version](https://stepik.org/course/200976/)) course. Module 4 covers the basic knowledge of NFT & Jettons. + ::: The [TON Blockchain Course](https://stepik.org/course/176754/) is a comprehensive guide to TON Blockchain development. diff --git a/docs/v3/documentation/data-formats/tlb/basic-proofing-concepts.mdx b/docs/v3/documentation/data-formats/tlb/basic-proofing-concepts.mdx index 0b563fe1f16..5e5e44b622f 100644 --- a/docs/v3/documentation/data-formats/tlb/basic-proofing-concepts.mdx +++ b/docs/v3/documentation/data-formats/tlb/basic-proofing-concepts.mdx @@ -6,7 +6,9 @@ A **proof** is a tree-based structure that contains the necessary data and can b To prove something means to construct such a structure. The exact structure may differ depending on the use case. For example, suppose a proof is to be validated off-chain and requires multiple cell trees; the native TON approach is to construct a Bag of Cells (BoC) containing all the necessary cells. This is precisely what a lite server does when data is requested from the blockchain. :::info + It is highly recommended to familiarize yourself with [Cells](/v3/documentation/data-formats/tlb/cell-boc) and [Exotic cells](/v3/documentation/data-formats/tlb/cell-boc) first. This article primarily covers situations where you want to verify a proof in a smart contract. However, the same techniques can be used to validate proofs off-chain. + ::: There are several key points to consider when proving anything on-chain. @@ -99,7 +101,9 @@ Sometimes, data is not in block diffs but within the ShardState itself. To prove 2. The user provides a ShardState that must be validated against the hash obtained in *step 1*. :::info + You can only prove the state at block boundaries (not intermediate states). + ::: ## Understanding pruned branch cells @@ -124,7 +128,9 @@ graph TD - **reprHash(cell)** accounts for everything. Matching *reprHashes* ensures cell path equivalency. :::note + Use `HASHCU` for reprHash and `CHASHI`/`CHASHIX` for different-level hashes. + ::: ## Composing proofs @@ -156,9 +162,11 @@ graph TD ``` :::info + - Trusted data hashes may be separated from cells (e.g., `PREVMCBLOCKS`). - Replacing pruned cells with actual cells changes the `MERKLE_UPDATE` cell hash. Always manually validate proofs against trusted hashes in these cases. + ::: ## Real-world example diff --git a/docs/v3/documentation/data-formats/tlb/block-layout.mdx b/docs/v3/documentation/data-formats/tlb/block-layout.mdx index eb1443fd197..1a15a23cf07 100644 --- a/docs/v3/documentation/data-formats/tlb/block-layout.mdx +++ b/docs/v3/documentation/data-formats/tlb/block-layout.mdx @@ -3,7 +3,9 @@ import Feedback from '@site/src/components/Feedback'; # Block layout :::info + To maximize comprehension of this page, it is highly recommended that you familiarize yourself with the [TL-B language](/v3/documentation/data-formats/tlb/cell-boc). + ::: A block in the blockchain is a record of new transactions that, once confirmed, is added to the blockchain as a permanent and immutable part of the decentralized ledger. Each block includes transaction data, timestamps, and a reference to the previous block, forming a block chain. diff --git a/docs/v3/documentation/data-formats/tlb/cell-boc.mdx b/docs/v3/documentation/data-formats/tlb/cell-boc.mdx index b2589c28d2b..a22433b8883 100644 --- a/docs/v3/documentation/data-formats/tlb/cell-boc.mdx +++ b/docs/v3/documentation/data-formats/tlb/cell-boc.mdx @@ -89,7 +89,9 @@ To serialize this structure into a byte sequence, we first identify unique cells ``` :::note + To filter out duplicates, cells must be compared by their [hashes](#cell-hash). + ::: Next, we arrange the cells in a specific order so that parent cells never reference cells that come before them in the list. In other words, any referenced cell must appear after the cells that reference it. We get: diff --git a/docs/v3/documentation/data-formats/tlb/library-cells.mdx b/docs/v3/documentation/data-formats/tlb/library-cells.mdx index 25539b619ab..8e862a3cf3b 100644 --- a/docs/v3/documentation/data-formats/tlb/library-cells.mdx +++ b/docs/v3/documentation/data-formats/tlb/library-cells.mdx @@ -11,7 +11,9 @@ As a result, many data structures in TON are rich in information and optimized f Library cells extend this deduplication mechanism on-chain, enabling the incorporation of the same efficiency into custom smart contracts. :::info + For instance, If you store the `jetton-wallet` code as a library cell (1 cell with 256 + 8 bits, instead of ~20 cells and ~6000 bits), the forwarding fees for a message that includes `init_code` can be reduced from 0.011 TON to 0.003 TON. + ::: ## General info @@ -23,7 +25,9 @@ In earlier-generation blockchains, this typically means tracking only the most r In scenarios involving families of similar contracts, e.g., `jetton-wallets`, the node stores duplicated data—such as identical contract codes—only once. Library cells leverage this deduplication mechanism, reducing storage costs and forwarding fees for such contracts. :::info Highlevel analogy + You can think of a library cell as a C++ pointer: a small cell that references a larger one, which may include many references. The referenced cell must exist and be registered publicly, i.e., _"published"_. + ::: ## Library cells structure @@ -113,8 +117,10 @@ To test how contracts that use library cells work in Blueprint, manually add the An example implementation can be found [here](https://github.com/ton-blockchain/stablecoin-contract/blob/de08b905214eb253d27009db6a124fd1feadbf72/sandbox_tests/JettonWallet.spec.ts#L100C9-L103C32). :::info + As of version `@ton/blueprint:0.19.0`, Blueprint does not automatically update the library context if a contract publishes a new library during emulation. You must update it manually. This behavior is current as of April 2024 and is expected to be improved in a future release. + ::: ### Get methods for library cell-based contracts diff --git a/docs/v3/documentation/data-formats/tlb/proofs.mdx b/docs/v3/documentation/data-formats/tlb/proofs.mdx index 7613536dbc0..8594a81bd6a 100644 --- a/docs/v3/documentation/data-formats/tlb/proofs.mdx +++ b/docs/v3/documentation/data-formats/tlb/proofs.mdx @@ -6,9 +6,11 @@ import ThemedImage from '@theme/ThemedImage'; ## Overview :::caution + This section provides instructions and guidance for interacting with TON at a low level. It assumes you are familiar with [exotic cells](/v3/documentation/data-formats/tlb/exotic-cells) and the [TL-B language](/v3/documentation/data-formats/tlb/tl-b-language) and understand the [simple proof verifying](/v3/documentation/data-formats/tlb/exotic-cells#simple-proof-verifying-example) example. + ::: @@ -723,8 +725,10 @@ assert block_tr.get_hash(0) == tr['hash'] ``` :::note + In this example, checking the `ids` field was optional — we could have retrieved all transactions directly from the account blocks. However, verifying the transaction proofs becomes essential when using the [liteServer.listBlockTransactionsExt](https://github.com/ton-blockchain/ton/blob/v2025.03/tl/generate/scheme/lite_api.tl#L48) method, and you must compare transaction hashes. + ::: ## Config diff --git a/docs/v3/documentation/data-formats/tlb/tl-b-types.mdx b/docs/v3/documentation/data-formats/tlb/tl-b-types.mdx index e6c9bdfd7ec..db498dee231 100644 --- a/docs/v3/documentation/data-formats/tlb/tl-b-types.mdx +++ b/docs/v3/documentation/data-formats/tlb/tl-b-types.mdx @@ -4,8 +4,10 @@ import ThemedImage from '@theme/ThemedImage'; # TL-B types :::caution advanced level + This information is **very low-level **and may be difficult for newcomers to grasp. Feel free to revisit it later if needed. + ::: This section analyzes complex and unconventional typed language binary (TL-B) structures. diff --git a/docs/v3/documentation/data-formats/tlb/transaction-layout.mdx b/docs/v3/documentation/data-formats/tlb/transaction-layout.mdx index 5206ab233c7..89185fc498c 100644 --- a/docs/v3/documentation/data-formats/tlb/transaction-layout.mdx +++ b/docs/v3/documentation/data-formats/tlb/transaction-layout.mdx @@ -3,7 +3,9 @@ import Feedback from '@site/src/components/Feedback'; # Transaction layout :::info + It's highly recommended that you familiarize yourself with the [TL-B language](/v3/documentation/data-formats/tlb/cell-boc) to better understand this page. + ::: The TON blockchain functions through three main components: accounts, messages, and transactions. This section outlines the structure and organization of transactions. @@ -133,7 +135,9 @@ trans_tick_tock$001 is_tock:Bool storage_ph:TrStoragePhase ## Split prepare :::note + This type of transaction is currently not in use, and details about its implementation are limited. + ::: Split transactions are designed for large smart contracts that must be divided due to high load. The contract must support this transaction type and manage the splitting process to distribute the load effectively. @@ -161,7 +165,9 @@ trans_split_prepare$0100 split_info:SplitMergeInfo ## Split install :::note + This transaction type is currently unavailable, and available information is limited. + ::: **Split install** transactions are used to deploy new instances of large smart contracts. A [split prepare](#split-prepare) transaction generates the state for the new contract. @@ -181,7 +187,9 @@ trans_split_install$0101 split_info:SplitMergeInfo ## Merge prepare :::note + This transaction type is currently unavailable, and available information is limited. + ::: Merge transactions are triggered for large smart contracts that need to recombine after being split under high load. The contract must support this transaction type and handle the merging process to help balance system resources. @@ -204,7 +212,9 @@ trans_merge_prepare$0110 split_info:SplitMergeInfo ## Merge install :::note + This transaction type is currently unavailable, and available information is limited. + ::: **Merge install** transactions are used to merge instances of large smart contracts. A [merge prepare](#merge-prepare) transaction generates a special message that facilitates the merge. diff --git a/docs/v3/documentation/faq.mdx b/docs/v3/documentation/faq.mdx index e41d72605fc..7efdfefc074 100644 --- a/docs/v3/documentation/faq.mdx +++ b/docs/v3/documentation/faq.mdx @@ -76,21 +76,26 @@ For more information, refer to our documentation's [Explorers in TON](/v3/concep _Block time: 2-5 seconds_ :::info + You can compare TON's on-chain metrics, including block time and time-to-finality, with Solana and Ethereum by reading our analysis at: - [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) - ::: + +::: ### Time-to-finality _Time-to-finality: under 6 seconds_ + :::info + Compare TON's on-chain metrics, including block time and time-to-finality, with Solana and Ethereum by reading our analysis at: - [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) - ::: + +::: ### Average block size @@ -100,7 +105,9 @@ max_block_bytes:2097152 ``` :::info + For more up-to-date parameters, refer to the [Network configs](/v3/documentation/network/configs/network-configs) section. + ::: ### What is the layout of blocks on TON? @@ -167,7 +174,9 @@ Default wallets (v3/v4) also support sending multiple messages (up to 4) in a si _9 digits_ :::info + Mainnet supports a 9-digit accuracy for currencies. + ::: ### Are there any standardized protocols for minting, burning, and transferring fungible and non-fungible tokens in transactions? @@ -227,7 +236,9 @@ To identify a **Jetton** contract: Yes. TON includes a special master blockchain called the **MasterChain**, which holds contracts critical for network operations, including network-wide contracts with network configuration, validator-related contracts, etc. :::info + Read more about MasterChain, WorkChains and ShardChains in TON Blockchain overview article: [Blockchain of blockchains](/v3/concepts/dive-into-ton/ton-blockchain/blockchain-of-blockchains). + ::: A good example is a smart governance contract, which is a part of MasterChain: diff --git a/docs/v3/documentation/infra/crosschain/bridge-addresses.mdx b/docs/v3/documentation/infra/crosschain/bridge-addresses.mdx index dd3369476c3..bd3f7933f35 100644 --- a/docs/v3/documentation/infra/crosschain/bridge-addresses.mdx +++ b/docs/v3/documentation/infra/crosschain/bridge-addresses.mdx @@ -3,7 +3,9 @@ import Feedback from '@site/src/components/Feedback'; # Bridges addresses :::caution + For the most accurate current addresses of bridge smart contracts, please refer to the [blockchain config](/v3/documentation/infra/crosschain/overview#blockchain-configs). This is the most secure method. + ::: ## Toncoin Mainnet diff --git a/docs/v3/documentation/infra/crosschain/overview.mdx b/docs/v3/documentation/infra/crosschain/overview.mdx index e19044dfcb4..bc866fcdf6b 100644 --- a/docs/v3/documentation/infra/crosschain/overview.mdx +++ b/docs/v3/documentation/infra/crosschain/overview.mdx @@ -15,7 +15,9 @@ This bridge is managed by [decentralized oracles](/v3/documentation/infra/crossc The bridge frontend is hosted [here](https://ton.org/bridge). :::info + [Bridge frontend source code](https://github.com/ton-blockchain/bridge) + ::: ### Smart contract source codes diff --git a/docs/v3/documentation/infra/minter-flow.mdx b/docs/v3/documentation/infra/minter-flow.mdx index db63779b68e..9c8d00bfb59 100644 --- a/docs/v3/documentation/infra/minter-flow.mdx +++ b/docs/v3/documentation/infra/minter-flow.mdx @@ -54,11 +54,15 @@ where key - `currency_id` and `std_addr` is _admin_ of this currency (can be in An example of this flow is as follows: [minting 2'000'000'000 units of `currency_id=100`](https://testnet.tonviewer.com/transaction/20fe328c04b4896acecb6e96aaebfe6fef90dcc1441e27049302f29770904ef0) :::danger + Each minting of new extracurrency or an increase in the supply of existing currency necessitates a change to `ConfigParam7`, which in turn alters the configuration and creation of keyblocks. Frequent keyblock generation can slow down shard performance since each key block causes a rotation of validator groups and affects the synchronization of liteclients. Therefore, contracts like `swap.tolk` should not be utilized in production environments. Instead, it is advisable to use schemes that involve reserves to minimize minting events. + ::: :::info + Sending of extracurrency to blackhole has the following effect: extracurrency amount is burnt, but since `ConfigParam7` is not changed, on the next block, **minter** will receive the burnt amount on its balance. + ::: diff --git a/docs/v3/documentation/infra/nodes/mytonctrl/mytonctrl-overview.mdx b/docs/v3/documentation/infra/nodes/mytonctrl/mytonctrl-overview.mdx index 271c1246b40..b33319da9ac 100644 --- a/docs/v3/documentation/infra/nodes/mytonctrl/mytonctrl-overview.mdx +++ b/docs/v3/documentation/infra/nodes/mytonctrl/mytonctrl-overview.mdx @@ -525,7 +525,9 @@ MyTonCtrl> mg wallet_004 kQBxnZJq4oHVFs4ban3kJ5qllM1IQo57lIx8QP69Ue9A6Psp 1 ``` :::caution + Wallet version 'v4' is not supported for the transferring + ::: ### Transfer coins through a proxy diff --git a/docs/v3/documentation/infra/nodes/node-types.mdx b/docs/v3/documentation/infra/nodes/node-types.mdx index 7cddbd6e483..3294b1bf830 100644 --- a/docs/v3/documentation/infra/nodes/node-types.mdx +++ b/docs/v3/documentation/infra/nodes/node-types.mdx @@ -75,8 +75,10 @@ You have two options to allow your lite client application to interact with the :::caution Usage of public liteservers in production + Because of a permanent high load on public liteservers, most of them are rate-limited, so it is not recommended that they be used in production. This may cause instability in your lite client application. + :::