Skip to content

Commit

Permalink
Staging (#798)
Browse files Browse the repository at this point in the history
* New translations principles-of-a-good-tutorial.md (Korean)

* New translations sample-tutorial.md (Korean)

* New translations readme.md (Korean)

* New translations contribution-rules.md (Korean)

* New translations maintainers.md (Korean)

* New translations participate.md (Korean)

* New translations mining.md (Korean)

* fix typos

* fix typo

* fix typo

* fix typos

* fix typo

* fix typos

* fix typos

* fix typo

* fix typo

* fix typo

* fix typo

* fix typos

* fix typo

* update dropdown menu

* fix import

* add translation of sidebar

* New translations overview.md (Chinese Simplified)

* New translations how-it-works.md (Chinese Simplified)

* New translations how-to-contribute.md (Chinese Simplified)

* New translations how-it-works.md (Chinese Simplified)

* New translations how-to-contribute.md (Chinese Simplified)

* remove content

* New translations overview.md (Chinese Simplified)

* New translations translation-style-guide.md (Chinese Simplified)

* Mandarin localization (#63)

* New translations cell-boc.mdx (Chinese Simplified)

* New translations as-contributor.md (Korean)

* New translations as-maintainer.md (Korean)

* New translations readme.mdx (Korean)

* New translations guidelines.md (Korean)

* New translations schemes-guidelines.mdx (Korean)

* New translations guidelines.md (Korean)

* New translations guidelines.md (Japanese)

* New translations principles-of-a-good-tutorial.md (Korean)

* New translations sample-tutorial.md (Korean)

* New translations readme.md (Korean)

* New translations contribution-rules.md (Korean)

* New translations maintainers.md (Korean)

* New translations participate.md (Korean)

* New translations mining.md (Korean)

* remove engines

* update dropdown menu

* fix import

* add translation of sidebar

---------

Co-authored-by: TonSquare <147710825+TonSquare@users.noreply.github.com>

* New translations how-it-works.md (Chinese Simplified)

* New translations how-to-contribute.md (Chinese Simplified)

* format fix

* Update to mytonctrl2 links in FullNode

* Add tip on how to use testnet config in Full Node

* Add tip about status fast in testnet

* Refactor

* Add link for testnet dump for archive node

* update default lang array

* New translations pow-givers.md (Korean)

* New translations sharding-lifecycle.mdx (Korean)

* fix header (#68)

* fix translation header

* Fix number of outgoing messages

* Remove duplicated

* Add tlb-parsers.md & Add tlb-codegen & fix link

* Separate parsers and tl-b generator

* add backend example for ton proof

* New translations send-transactions-from-highload.md (Chinese Simplified)

* New translations shards.mdx (Korean)

* New translations auditors.mdx (Korean)

* New translations outsource.mdx (Korean)

* New translations adnl.md (Korean)

* New translations getblock-ton-api.md (Korean)

* New translations overview.md (Chinese Simplified)

* New translations how-to-contribute.md (Chinese Simplified)

* cut_warining

* Stepik corrections

Added RU and CHN links as well as replaced EN -> CHN in CHN pages

* Update academy-overview.md

* Add AWS instance description

* ecosystem_messages_layout_init

* ecosystem_messages_layuot_2

Correction sidebars,js

* ecosystem-messages-layout_3

Scheme files added

* ecosystem-messages-layout_4

Cookbook update

* chrore: add info about gasless transactions

* Add information about node setup timings

* Revert "ecosystem-messages-layout_4"

This reverts commit c33a788.

* ecosystem_messages_layout_4

Cookbook Update according new schemes

* cookbook_schemes_update

Added dark scheme

* Cookbook_update

Deleting old scheme

* Cookbook_update_3

Deleting old schemes

* Update jetton_transfer_dark.svg

* Fix non latin symbol

* Scheme_Visio_added

* Update archive-node.md

update archive node requirements

* Update enable-liteserver-node.md

update liteserver requirements

* sidebar_fix

* Delete public proxy and C++ compile page

- participate/web3/sites-and-proxy
- public proxy

* Delete public proxy and C++ instruction

- participate/web3/sites-and-proxy
- public proxy
amend

* Revert "Delete public proxy and C++ instruction"

This reverts commit 4adc61a.

* tons_sites_for_apps_page_added

* Updated after review

* cut_jetton_text

Cut the jetton - as Standard operation text from the Cookbook.

* Update how-to-run-ton-site.md

* Update how-to-run-ton-site.md

* Revert wallet.md typo fix

* Add error of wrong user usage for nodes

* docs(cookbook): update Go address parsing example

* feat: ton connect tg bot integration archived

* Update single-nominator.mdx (#710)

* Update single-nominator.mdx (#711)

* collectiong_minging_fix

Transfer fixes from PR, which got stuck because of merge conflicts.

https://github.com/ton-community/ton-docs/pull/664/files

* 🐛 Fix link in doc (#685)

* Add some explanation for effective stake (#687)

Co-authored-by: Full-Hat <nikita3131228@gmail.com>

* feat: Add tonconnect vue sdk link (#688)

* add tonconnect vue sdk link

* fix typo

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: infinityspectra <149141428+infinityspectra@users.noreply.github.com>

* feat: upd wallets switch testnet info (#694)

Co-authored-by: igor <i.verhusha@pixelplex.io>

* Add Error parsing dependencies to troubleshooting (#695)

Co-authored-by: Full-Hat <nikita3131228@gmail.com>
Co-authored-by: AlexG <39581753+reveloper@users.noreply.github.com>

* Fix typo in mode 0 of send_raw_message (#699)

This is a non-trivial typo as developer most likely refer to mode 0 to understand how token transfer works

* Update how-to-run-ton-site.md (#700)

* update ton connect docs, add video (#701)

Co-authored-by: Aliaksandr Bahdanau <a.bahdanau@pixelplex.io>

* Update cookbook.md date->data (#703)

* Update messages.md (#706)

Fixed Send a regular message

* fix_node_troubleshooting

added lost snippet related to Version problem

* update troubleshooting (#712)

* update_ton_connect_button

* remove mytonctrl2 branch mentions (#714)

* Scheme update 2 (#707)

* Ecosystem_schemes_layout_5

Try to change font replacement

* Ecosystem_scheme_png_update

* Ecosystem_sheme_png_2

* Update nodes-troubleshooting.md

* SAP list update

SAP list updated according current status of auditors on Ecosystem.

* added contributors wall

* single-nominator-fix

* wallet-guidelines-cut-oudated-link

* Added info run docker (#611)

* add info run in docker

* change docker repository mytonctrl

* Update docs/participate/run-nodes/run-docker.md

Co-authored-by: Dr. Awesome Doge <doge@ton.org>

* Update docs/participate/run-nodes/run-docker.md

Co-authored-by: Dr. Awesome Doge <doge@ton.org>

* Update docs/participate/run-nodes/run-docker.md

Co-authored-by: Dr. Awesome Doge <doge@ton.org>

* Update docs/participate/run-nodes/run-docker.md

Co-authored-by: Dr. Awesome Doge <doge@ton.org>

* Update docs/participate/run-nodes/run-docker.md

Co-authored-by: Dr. Awesome Doge <doge@ton.org>

* Update docs/participate/run-nodes/run-docker.md

Co-authored-by: Dr. Awesome Doge <doge@ton.org>

* Update docs/participate/run-nodes/run-docker.md

Co-authored-by: Dr. Awesome Doge <doge@ton.org>

* Update docs/participate/run-nodes/run-docker.md

Co-authored-by: Dr. Awesome Doge <doge@ton.org>

* Update docs/participate/run-nodes/run-docker.md

Co-authored-by: Dr. Awesome Doge <doge@ton.org>

---------

Co-authored-by: Sergey Andreev <s.andreev@pixelplex.io>
Co-authored-by: AlexG <39581753+reveloper@users.noreply.github.com>
Co-authored-by: Dr. Awesome Doge <doge@ton.org>

* Fixed code for selling nft on getgems (#691)

* fixed code for selling nft on getgems

* fix first mistake with nanoTon

* added suggestions that tokens come in different decimals

---------

Co-authored-by: vityooook <vityooook@gmail.com>

* feat: add high-load wallet v3 to wallet tutorial (#715)

* Update difference-of-blockchains.md (#716)

The previous link is broken, fix with ton.org pdf

* Add transaction and messages hashes examples (#718)

Co-authored-by: Aliaksandr Bahdanau <a.bahdanau@pixelplex.io>

* Added message modes cookbook (#724)

Co-authored-by: Vladislav Kokosh <v.kokosh@pixelplex.io>

* Update data about archive node sync timings (#720)

Co-authored-by: Full-Hat <nikita3131228@gmail.com>

* add Japanese content document translation (#743)

* Transaction outcome description (#708)

* Transaction outcome

Definition of success and some TVM details.

* Upd transaction outcome

* Update message-delivery-guarantees.mdx

* Update tvm-overview.mdx

* Update auditors.mdx

* Additional changes to Msg & Tx page (#744)

* Transaction outcome

Definition of success and some TVM details.

* Upd transaction outcome

* Update message-delivery-guarantees.mdx

* Update tvm-overview.mdx

* Update message-delivery-guarantees.mdx

* Added an example of how to send a transaction with Wallet V5 (#721)

Co-authored-by: Vladislav Kokosh <v.kokosh@pixelplex.io>

* Added actual link to wallet v5 (#725)

Co-authored-by: Vladislav Kokosh <v.kokosh@pixelplex.io>

* feat: upd mytonwallet switch testnet info (#726)

Co-authored-by: igor <i.verhusha@pixelplex.io>

* fix bridge.ton.org link (#727)

and open external links in new page

* Add status output explanation (#728)

Co-authored-by: Full-Hat <nikita3131228@gmail.com>
Co-authored-by: Full-Hat <68519677+Full-Hat@users.noreply.github.com>

* Add information about api keys (#730)

Co-authored-by: Full-Hat <nikita3131228@gmail.com>

* supplement Korean translation (#731)

Co-authored-by: lotteam003 <lotteam003@proton.me>

* Adding Tatum under RPC Nodes provider (#745)

Adding Tatum under RPC Nodes provider as Tatum provides TON RPC Nodes and whole infrastructure to run Web3 Apps.

* Fix for buttons at academy page (#747)

* Transaction outcome

Definition of success and some TVM details.

* Upd transaction outcome

* Update message-delivery-guarantees.mdx

* Update tvm-overview.mdx

* Update message-delivery-guarantees.mdx

* Update academy-overview.md

Button

* add i18n ja translation (#732)

Co-authored-by: lotteam003 <lotteam003@proton.me>

* Mytonctrl installer (#733)

* Add information about disabling storing archive blocks

* Add explanation to mytonctrl installer section

---------

Co-authored-by: Full-Hat <nikita3131228@gmail.com>

* Add information about configs (#734)

Co-authored-by: Full-Hat <nikita3131228@gmail.com>

* change link to tonapi rates documentarion (#735)

* Examples (#736)

* Update examples & add -t flag explanation

* Complete examples

---------

Co-authored-by: Full-Hat <nikita3131228@gmail.com>

* Fix footer & add guideline (#739)

* fix & udpate footer

* update guides

* complete add footer guide

* update branch doc

* specify function

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

* improve transaction processing (#741)

Co-authored-by: Aliaksandr Bahdanau <a.bahdanau@pixelplex.io>

* Add vue section (#738)

* add vue section

* cut numbers from header

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

* Add testnet.dton.io (#750)

* Add tonpy to TLB parsers and codegen (#749)

* fix jetton sample (#742)

#637

Co-authored-by: Aliaksandr Bahdanau <a.bahdanau@pixelplex.io>

* remove numbers (#751)

* Update node-types.md (#748)

* Added tonutils SDK to the Python SDKs section (#740)

* update_bridge_example_link

* Add -c flag explanation in liteserver test node (#670)

* Add -c flag explanation in liteserver test node

* Update links to mytonctrl master

* Update examples & add -t flag explanation

* Add -c flag explanation in liteserver test node

* Update links to mytonctrl master

---------

Co-authored-by: Full-Hat <nikita3131228@gmail.com>

* Add .NET ton_proof demo (#723)

* Add information about api keys (#729)

* Add information about api keys

* Remove info about tariffs

---------

Co-authored-by: Full-Hat <nikita3131228@gmail.com>

* added translation (#752)

* Update analysis link (#674)

* Update analysis link

* Fix link

* Add eth 2.0 info

* Remove Eth 1.0 & update ton name

---------

Co-authored-by: Full-Hat <nikita3131228@gmail.com>

* node-commands_added

* Fixed cases with 16 flag in modes cookbook (#754)

Co-authored-by: Vladislav Kokosh <v.kokosh@pixelplex.io>

* Docu update on MacOS installation and docker image with MyTonCtrl 2.0 (#755)

* update ton installation on MacOS

* update docker with MyTonCtrl 2.0 docu

---------

Co-authored-by: neodiX <neodix42@ton.org>

* cut-ecosystem-sap

* Update governance.md

* lite-client-naming

* Update sign.mdx (#760)

added convenient check if proof valid

* nodes_documentation_fine_update (#762)

* nodes_documentation_fine_update

* added_wallet_deployment_for_each_shard

* added_mintless_jettons

* beauty_fixes

* beauty_fixes_2

* build_fix

* fix_node_reqierements

* node_reqierement_fix.mdx

* fix_node_reqierements_2

* fix_node_reqierements_3

* wallet_v5_caution_cut

* feat: clarified jetton errors information (#771)

Co-authored-by: Aliaksandr Bahdanau <a.bahdanau@pixelplex.io>

* Add Chainstack as node & indexer provider (#774)

* Update_node_reqierements

* feat: add nodes video (#779)

* Fix transfer example for V5R1 wallet (#778)

https://github.com/ton-blockchain/wallet-contract-v5/blob/88557ebc33047a95207f6e47ac8aadb102dff744/contracts/wallet_v5.fc#L82

Transfer will fail without IGNORE_ERRORS flag with 137 exit code

* feat: add examples with assets sdk for message builders (#667)

* feat: add examples with assets sdk for message builders

* improve assets-sdk examples

* add info about Jetton and NFT Contracts

* feat: add cells information

---------

Co-authored-by: “mlikhar” <m.likhtar@pixelplex.io>
Co-authored-by: Aliaksandr Bahdanau <a.bahdanau@pixelplex.io>

* Add OP Codes to the docs (#763)

* Transaction outcome

Definition of success and some TVM details.

* Upd transaction outcome

* Update message-delivery-guarantees.mdx

* Update tvm-overview.mdx

* Update message-delivery-guarantees.mdx

* Update academy-overview.md

Button

* op code update

Added known op codes

* Update contracts.md

* Update contracts.md

* Added DEX opcodes

StonFi&DeDust

* Update contracts.md

* add secure guidelines for nodes (#766)

Co-authored-by: AlexG <39581753+reveloper@users.noreply.github.com>

* feat: update Prism.js definitions of Tact and FunC for syntax highlighting (#768)

* feat(prism): update Tact from 1.2.0 to 1.5.0

* feat(prism): update and enhance FunC from 0.2.0 to 0.4.4

* Check ef (#773)

* check_ef description

* update check_ef description & update status info

* update check_ef description (add links to configs)

* update check_ef description (fix typos)

---------

Co-authored-by: Full-Hat <nikita3131228@gmail.com>

* Minor corrections (#780)

* Transaction outcome

Definition of success and some TVM details.

* Upd transaction outcome

* Update message-delivery-guarantees.mdx

* Update tvm-overview.mdx

* Update message-delivery-guarantees.mdx

* Update academy-overview.md

Button

* op code update

Added known op codes

* Update contracts.md

* Update contracts.md

* Added DEX opcodes

StonFi&DeDust

* Update contracts.md

* Add serokell

* Refatored page about node types (#769)

* Update cookbook.md (#777)

Fixed

* React doc wrappers (#673)

* improve react doc

* chore: add wrappers examples for react doc

* add more info about react

* add info about contract deploy

* remove protocol pages from doc, improve react doc

---------

Co-authored-by: “mlikhar” <m.likhtar@pixelplex.io>
Co-authored-by: Aliaksandr Bahdanau <a.bahdanau@pixelplex.io>

* Update custom-overlays.md

* shard-optimization-guidelines-added

* fix_address_format.mdx

* rework documentation with guidelines in first iterartion

* feat: update docusaurus version

* feat: divide sidebars

* feat: divide sidebars

* add husky and cspell for grammar check

* fix docs/develop/howto/step-by-step.mdx

* fix some spelling

* fix: fix husky

* feat: reorganize learn sidebar

* nodes section renewal

* refactor TON Node Command-Line Flags

* feat: extract navbar

* feat: update navbar

* aws_node_req_update.mdx

* Update full-node.mdx

* Update full-node.mdx

* feat: add contribute link

* add redirect script

* Add smart contracts specs (#6)

* refactor wallets page

* fix highload ref

---------

Co-authored-by: Gleb Karavatski <g.karavatski@pixelplex.io>

* feat: improve difference in the naming

* feat: improve concepts

* feat: remove web3 from upper bar

* feat: move wallets

* feat: rename mytonctrl

* feat: add guidelines

* feat: fix assets

* fix: fix move script

---------

Co-authored-by: AlexG <39581753+reveloper@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: TonSquare <147710825+TonSquare@users.noreply.github.com>
Co-authored-by: omahs <73983677+omahs@users.noreply.github.com>
Co-authored-by: sansx <646924078@qq.com>
Co-authored-by: sansx <xiathxth@gmail.com>
Co-authored-by: Full-Hat <nikita3131228@gmail.com>
Co-authored-by: “mlikhar” <m.likhtar@pixelplex.io>
Co-authored-by: Antonoff <35700168+memearchivarius@users.noreply.github.com>
Co-authored-by: p.nazarychev <pavel.nazarychev@copper.co>
Co-authored-by: Airam G <169088121+AiramGol@users.noreply.github.com>
Co-authored-by: Vladislav Kokosh <v.kokosh@pixelplex.io>
Co-authored-by: Oleg Baranov <xssnick8@gmail.com>
Co-authored-by: Anthony Tsivarev <tsivarev.a@gmail.com>
Co-authored-by: 70sh1 <70sh1@proton.me>
Co-authored-by: igor <i.verhusha@pixelplex.io>
Co-authored-by: Maksim Kurbatov <94808996+yungwine@users.noreply.github.com>
Co-authored-by: Ginta <775650117@qq.com>
Co-authored-by: PixelPlex Dev team <10460630+pixelplex@users.noreply.github.com>
Co-authored-by: infinityspectra <149141428+infinityspectra@users.noreply.github.com>
Co-authored-by: NakeyJakey <jimip6c12@gmail.com>
Co-authored-by: Devin <studyzy@gmail.com>
Co-authored-by: Duginets Nikita <duginetsn98@gmail.com>
Co-authored-by: Roman <krutovoyroman@gmail.com>
Co-authored-by: Sergey Andreev <s.andreev@pixelplex.io>
Co-authored-by: Dr. Awesome Doge <doge@ton.org>
Co-authored-by: Victor <129557549+vityooook@users.noreply.github.com>
Co-authored-by: vityooook <vityooook@gmail.com>
Co-authored-by: aSpite <45543119+aSpite@users.noreply.github.com>
Co-authored-by: zhangchitc <95238503+zhangchitc@users.noreply.github.com>
Co-authored-by: SilentPine <SilentPine@proton.me>
Co-authored-by: spookyahell <9724215+spookyahell@users.noreply.github.com>
Co-authored-by: Full-Hat <68519677+Full-Hat@users.noreply.github.com>
Co-authored-by: lotteam003 <Kafkaesqt@proton.me>
Co-authored-by: lotteam003 <lotteam003@proton.me>
Co-authored-by: blockchaingirl1407 <142514003+blockchaingirl1407@users.noreply.github.com>
Co-authored-by: Moiseev Ilya <ilya@mois.pro>
Co-authored-by: Andrey Tvorozhkov <tvorog@tvorog.me>
Co-authored-by: Artem <79601745+Sovenok-Hacker@users.noreply.github.com>
Co-authored-by: Shon Ness <78713403+nessshon@users.noreply.github.com>
Co-authored-by: Alexander <Seviant88@gmail.com>
Co-authored-by: StarryHazex <StarryHaze@proton.me>
Co-authored-by: neodix42 <namlem@gmail.com>
Co-authored-by: neodiX <neodix42@ton.org>
Co-authored-by: EmelyanenkoK <emelyanenko.kirill@gmail.com>
Co-authored-by: JeanClaude (JC) <Jeanclaude.aoun@hotmail.com>
Co-authored-by: Ake <10195782+akegaviar@users.noreply.github.com>
Co-authored-by: Max Voloshinskii <me@voloshinskii.com>
Co-authored-by: Novus Nota <68142933+novusnota@users.noreply.github.com>
Co-authored-by: Pavel Nazarychev <73617204+fmira21@users.noreply.github.com>
Co-authored-by: yycceth <zhichunqi93@gmail.com>
Co-authored-by: Gleb Karavatski <g.karavatski@pixelplex.io>
Co-authored-by: Karavatski Gleb <gleb498@yandex.ru>
  • Loading branch information
Show file tree
Hide file tree
Showing 21 changed files with 428 additions and 202 deletions.
22 changes: 21 additions & 1 deletion docs/develop/network/overlay.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,10 @@
# Overlay subnetworks

Implementation:
* https://github.com/ton-blockchain/ton/tree/master/overlay

## Overview

The architecture of TON is built in such a way that a lot of chains can exist simultaneously and independently in it - they can be both private or public.
Nodes have the ability to choose which shards and chains they store and process.
At the same time, the communication protocol remains unchanged due to its universality. Protocols such as DHT, RLDP and Overlays allow this to be achieved.
Expand All @@ -11,6 +16,21 @@ All chains in TON, including the masterchain, communicate using their own overla
To join it, you need to find the nodes that are already in it, and start exchanging data with them.
For the public overlays you can find nodes using DHT.

## ADNL vs Overlay networks

In contrast to ADNL, the TON overlay networks usually do not support
sending datagrams to other arbitrary nodes. Instead, some “semi-permanent
links” are established between certain nodes (called “neighbors” with respect to
the overlay network under consideration) and messages are usually forwarded
along these links (i.e. from a node to one of its neighbors).

Each overlay subnetwork has a 256-bit network identifier usually equal
to a SHA256 of the description of the overlay network—a TL-serialized object.

Overlay subnetworks can be public or private.

Overlay subnetworks work according to a special [gossip](https://en.wikipedia.org/wiki/Gossip_protocol) protocol.

## Interaction with overlay nodes

We have already analyzed an example with finding overlay nodes in an article about DHT,
Expand Down Expand Up @@ -70,4 +90,4 @@ Thus, we can receive information directly from the nodes.

## References

_Here a [link to the original article](https://github.com/xssnick/ton-deep-doc/blob/master/Overlay-Network.md) by [Oleg Baranov](https://github.com/xssnick)._
_Here a [link to the original article](https://github.com/xssnick/ton-deep-doc/blob/master/Overlay-Network.md) by [Oleg Baranov](https://github.com/xssnick)._
9 changes: 8 additions & 1 deletion docs/develop/network/rldp.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,12 @@
# RLDP

Implementation:
* https://github.com/ton-blockchain/ton/tree/master/rldp
* https://github.com/ton-blockchain/ton/tree/master/rldp2
* https://github.com/ton-blockchain/ton/tree/master/rldp-http-proxy

## Overview

RLDP - Reliable Large Datagram Protocol - is a protocol that runs on top of ADNL UDP, which is used to transfer large data blocks and
includes Forward Error Correction (FEC) algorithms as a replacement of acknowledgment packets on the other side.
This makes it possible to transfer data between network components more efficiently, but with more traffic consumption.
Expand Down Expand Up @@ -179,4 +186,4 @@ If `last` = true, then we have reached the end, we can put all the pieces togeth

## References

_Here a [link to the original article](https://github.com/xssnick/ton-deep-doc/blob/master/RLDP.md) by [Oleg Baranov](https://github.com/xssnick)._
_Here a [link to the original article](https://github.com/xssnick/ton-deep-doc/blob/master/RLDP.md) by [Oleg Baranov](https://github.com/xssnick)._
2 changes: 1 addition & 1 deletion docs/develop/smart-contracts/tutorials/wallet.md
Original file line number Diff line number Diff line change
Expand Up @@ -2105,7 +2105,7 @@ When working with many messages in a short period, there is a need for special w

:::note
We will work [with a slightly modified version of Wrapper](https://github.com/aSpite/highload-wallet-contract-v3/blob/main/wrappers/HighloadWalletV3.ts) for the contract, as it protects against some non-obvious mistakes.
:::note
:::


### Storage Structure
Expand Down
File renamed without changes.
33 changes: 0 additions & 33 deletions docs/learn/networking/overlay-subnetworks.md

This file was deleted.

6 changes: 6 additions & 0 deletions docs/learn/networking/overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,3 +19,9 @@ The TON Project uses its own peer-to-peer network protocols.
blockchain itself, thus providing more possibilities and flexibility for creating
new services in the TON Ecosystem.

## See Also

* [ADNL Protocol](/learn/networking/adnl)
* [Overlay Subnetworks](/learn/networking/overlay-subnetworks)
* [RLDP Protocol](/learn/networking/rldp)
* [TON DHT Service](/learn/networking/ton-dht)
17 changes: 0 additions & 17 deletions docs/learn/networking/rldp.md

This file was deleted.

2 changes: 1 addition & 1 deletion docs/learn/overviews/addresses.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# Smart Contract Addresses
# Smart Contract Addresses Documentation

This section will describe the specifics of smart contract addresses on TON Blockchain. It will also explain how actors are synonymous with smart contracts on TON.

Expand Down
2 changes: 1 addition & 1 deletion docs/participate/wallets/apps.mdx
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
import Player from '@site/src/components/player'

# Wallet Apps (for Devs)
# Wallet Apps

## Overview

Expand Down
59 changes: 2 additions & 57 deletions docs/participate/wallets/contracts.md
Original file line number Diff line number Diff line change
Expand Up @@ -101,64 +101,9 @@ Sometimes the functionality of basic wallets isn't enough. That's why there are

Let's have a look at them.

### Highload Wallet v3
### Highload Wallets

This wallet is made for who need to send transactions at very high rates. For example, crypto exchanges.

- [Source code](https://github.com/ton-blockchain/highload-wallet-contract-v3)

Any given external message (transfer request) to a highload v3 contains:
- a signature (512 bits) in the top level cell - the other parameters are in the ref of that cell
- subwallet ID (32 bits)
- message to send as a ref (the serialized internal message that will be sent)
- send mode for the message (8 bits)
- composite query ID - 13 bits of "shift" and 10 bits of "bit number", however the 10 bits of bit number can only go up to 1022, not 1023, and also the last such usable query ID (8388605) is reserved for emergencies and should not be normally used
- created at, or message timestamp
- timeout

Timeout is stored in highload as a parameter and is checked against the timeout in all requests - so the timeout for all requests is equal. The message should be not older than timeout at the time of arrival to the highload wallet, or in code it is required that `created_at > now() - timeout`. Query IDs are stored for the purposes of replay protection for at least timeout and possibly up to 2 * timeout, however one should not expect them to be stored for longer than timeout. Subwallet ID is checked against the one stored in the wallet. Inner ref's hash is checked along with the signature against the public key of the wallet.

Highload v3 can only send 1 message from any given external message, however it can send that message to itself with a special op code, allowing one to set any action cell on that internal message invocation, effectively making it possible to send up to 254 messages per 1 external message (possibly more if another message is sent to highload wallet again among these 254).

Highload v3 will always store the query ID (replay protection) once all the checks pass, however a message may not be sent due to some conditions, including but not limited to:
- **containing state init** (such messages, if required, may be sent using the special op code to set the action cell after an internal message from highload wallet to itself)
- not enough balance
- invalid message structure (that includes external out messages - only internal messages may be sent straight from the external message)

Highload v3 will never execute multiple externals containing the same `query_id` **and** `created_at` - by the time it forgets any given `query_id`, the `created_at` condition will prevent such a message from executing. This effectively makes `query_id` **and** `created_at` together the "primary key" of a transfer request for highload v3.

When iterating (incrementing) query ID, it is cheaper (in terms of TON spent on fees) to iterate through bit number first, and then the shift, like when incrementing a regular number. After you've reached the last query ID (remember about the emergency query ID - see above), you can reset query ID to 0, but if highload's timeout period has not passed yet, then the replay protection dictionary will be full and you will have to wait for the timeout period to pass.


### Highload wallet v2

:::danger
Legacy contract, it is suggest to use High-load wallet v3.
:::

This wallet is made for those who need to send hundreds of transactions in a short period of time. For example, crypto exchanges.

It allows you to send up to `254` transactions in one smart contract call. It also uses a slightly different approach to solve replay attacks instead of seqno, so you can call this wallet several times at once to send even thousands of transactions in a second.

:::caution Limitations
Note, when dealing with highload-wallet the following limits need to be checked and taken into account.
:::

1. **Storage size limit.** Currently, size of contract storage should be less than 65535 cells. If size of
old_queries will grow above this limit, exception in ActionPhase will be thrown and transaction will fail.
Failed transaction may be replayed.
2. **Gas limit.** Currently, gas limit is 1'000'000 GAS units, that means that there is a limit of how much
old queries may be cleaned in one tx. If number of expired queries will be higher, contract will stuck.

That means that it is not recommended to set too high expiration date:
number of queries during expiration time span should not exceed 1000.

Also, number of expired queries cleaned in one transaction should be below 100.



Wallet source code:
* [ton/crypto/smartcont/highload-wallet-v2-code.fc](https://github.com/ton-blockchain/ton/blob/master/crypto/smartcont/highload-wallet-v2-code.fc)
When working with many messages in a short period, there is a need for special wallet called Highload Wallet. Read [the article](/participate/wallets/highload) for more information.

### Lockup wallet

Expand Down
64 changes: 64 additions & 0 deletions docs/participate/wallets/highload.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,64 @@
# Highload Wallet

When working with many messages in a short period, there is a need for special wallet called Highload Wallet. Highload Wallet V2 was the main wallet on TON for a long time, but you had to be very careful with it. Otherwise, you could [lock all funds](https://t.me/tonstatus/88).

[With the advent of Highload Wallet V3](https://github.com/ton-blockchain/Highload-wallet-contract-v3), this problem has been solved at the contract architecture level and consumes less gas. This chapter will cover the basics of Highload Wallet V3 and important nuances to remember.

## Highload Wallet v3

This wallet is made for who need to send transactions at very high rates. For example, crypto exchanges.

- [Source code](https://github.com/ton-blockchain/Highload-wallet-contract-v3)

Any given external message (transfer request) to a Highload v3 contains:
- a signature (512 bits) in the top level cell - the other parameters are in the ref of that cell
- subwallet ID (32 bits)
- message to send as a ref (the serialized internal message that will be sent)
- send mode for the message (8 bits)
- composite query ID - 13 bits of "shift" and 10 bits of "bit number", however the 10 bits of bit number can only go up to 1022, not 1023, and also the last such usable query ID (8388605) is reserved for emergencies and should not be normally used
- created at, or message timestamp
- timeout

Timeout is stored in Highload as a parameter and is checked against the timeout in all requests - so the timeout for all requests is equal. The message should be not older than timeout at the time of arrival to the Highload wallet, or in code it is required that `created_at > now() - timeout`. Query IDs are stored for the purposes of replay protection for at least timeout and possibly up to 2 * timeout, however one should not expect them to be stored for longer than timeout. Subwallet ID is checked against the one stored in the wallet. Inner ref's hash is checked along with the signature against the public key of the wallet.

Highload v3 can only send 1 message from any given external message, however it can send that message to itself with a special op code, allowing one to set any action cell on that internal message invocation, effectively making it possible to send up to 254 messages per 1 external message (possibly more if another message is sent to Highload wallet again among these 254).

Highload v3 will always store the query ID (replay protection) once all the checks pass, however a message may not be sent due to some conditions, including but not limited to:
- **containing state init** (such messages, if required, may be sent using the special op code to set the action cell after an internal message from Highload wallet to itself)
- not enough balance
- invalid message structure (that includes external out messages - only internal messages may be sent straight from the external message)

Highload v3 will never execute multiple externals containing the same `query_id` **and** `created_at` - by the time it forgets any given `query_id`, the `created_at` condition will prevent such a message from executing. This effectively makes `query_id` **and** `created_at` together the "primary key" of a transfer request for Highload v3.

When iterating (incrementing) query ID, it is cheaper (in terms of TON spent on fees) to iterate through bit number first, and then the shift, like when incrementing a regular number. After you've reached the last query ID (remember about the emergency query ID - see above), you can reset query ID to 0, but if Highload's timeout period has not passed yet, then the replay protection dictionary will be full and you will have to wait for the timeout period to pass.


## Highload wallet v2

:::danger
Legacy contract, it is suggest to use Highload wallet v3.
:::

This wallet is made for those who need to send hundreds of transactions in a short period of time. For example, crypto exchanges.

It allows you to send up to `254` transactions in one smart contract call. It also uses a slightly different approach to solve replay attacks instead of seqno, so you can call this wallet several times at once to send even thousands of transactions in a second.

:::caution Limitations
Note, when dealing with Highload wallet the following limits need to be checked and taken into account.
:::

1. **Storage size limit.** Currently, size of contract storage should be less than 65535 cells. If size of
old_queries will grow above this limit, exception in ActionPhase will be thrown and transaction will fail.
Failed transaction may be replayed.
2. **Gas limit.** Currently, gas limit is 1'000'000 GAS units, that means that there is a limit of how much
old queries may be cleaned in one tx. If number of expired queries will be higher, contract will stuck.

That means that it is not recommended to set too high expiration date:
number of queries during expiration time span should not exceed 1000.

Also, number of expired queries cleaned in one transaction should be below 100.



Wallet source code:
* [ton/crypto/smartcont/Highload-wallet-v2-code.fc](https://github.com/ton-blockchain/ton/blob/master/crypto/smartcont/Highload-wallet-v2-code.fc)
25 changes: 25 additions & 0 deletions docs/v3/concepts/ton-blockchain/shards.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
# Overview: Sharding and Split Merge in the TON Blockchain

[//]: # (TODO, this is from gpt)

The TON Blockchain employs advanced sharding mechanisms to enhance scalability and performance, allowing it to efficiently process a massive number of transactions.
The core concept is splitting the blockchain into smaller, independent pieces called **shards**. These shards can handle transactions in parallel, ensuring high throughput even as the network grows.

In TON, sharding is highly dynamic. Unlike other blockchains, which have a fixed number of shards, TON can create new shards on demand.
As the transaction load increases, shards split, and as the load decreases, they merge.
This flexibility ensures that the system can adapt to varying workloads while maintaining efficiency.

The **Masterchain** plays a crucial role, maintaining the network configuration and the final state of all **workchains** and **shardchains**.
While the masterchain is responsible for overall coordination, **workchains** operate under their specific rules, each of which can be split further into shardchains.
Currently, only one workchain (the **Basechain**) operates on TON.

At the heart of TON's efficiency is the **Infinity Sharding Paradigm**, which treats each account as part of its own "accountchain."
These accountchains are then aggregated into shardchain blocks, facilitating efficient transaction processing.

In addition to the dynamic creation of shards, TON uses **Split Merge** functionality, which allows the network to efficiently respond to changing transaction loads. This system enhances scalability and interaction within the blockchain network, exemplifying TON's approach to resolving common blockchain challenges with a focus on efficiency and global consistency.


## See Also

* [Shards Dive In](/develop/blockchain/shards)
* [# Infinity Sharding Paradigm](/develop/blockchain/sharding-lifecycle)
Loading

0 comments on commit 6829d25

Please sign in to comment.