Skip to content

1179-fixing-links #1180

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

1179-fixing-links #1180

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
7c1942f
mini app bot link
aigerimu May 12, 2025
26e95a7
tvm stack
aigerimu May 12, 2025
34d0bb6
till-connect-guide-prep-msgs
aigerimu May 22, 2025
118ecca
fixed links
aigerimu May 22, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/v3/concepts/dive-into-ton/go-from-ethereum/difference-of-blockchains.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -90,7 +90,7 @@ 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)
Read more in [Blockchain of blockchain](/v3/concepts/dive-into-ton/ton-blockchain/blockchain-of-blockchains).
:::

### Gas
Expand Down Expand Up @@ -126,7 +126,7 @@ 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/)
Read more about [gas](/v3/documentation/smart-contracts/transaction-fees/fees/).
:::

### Architecture
Expand Down
2 changes: 1 addition & 1 deletion docs/v3/concepts/dive-into-ton/go-from-ethereum/solidity-vs-func.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ Solidity includes the following basic data types:
- **Byte arrays** — declared with the keyword **bytes**, is a fixed-size array used to store a predefined number of bytes up to 32, usually declared along with the keyword.
- **Literals** — Immutable values such as addresses, rationals and integers, strings, Unicode, and hexadecimal can be stored in a variable.
- **Enums**
- **Arrays** fixed or dynamic)
- **Arrays** fixed or dynamic
- **Structs**
- **Mappings**

Expand Down
2 changes: 1 addition & 1 deletion docs/v3/concepts/dive-into-ton/introduction.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -92,7 +92,7 @@ If you're new to blockchain and don’t understand what makes the technology so
## Migration from Ethereum

For those familiar with Ethereum development, we suggest introductory articles to help you understand what sets TON apart in this regard:
* [The Difference of Blockchains](/v3/concepts/dive-into-ton/go-from-ethereum/difference-of-blockchains/)
* [The differences of blockchains](/v3/concepts/dive-into-ton/go-from-ethereum/difference-of-blockchains)
* [Six unique aspects of TON Blockchain that will surprise Solidity developers](https://blog.ton.org/six-unique-aspects-of-ton-blockchain-that-will-surprise-solidity-developers)
* [It’s time to try something new: Asynchronous smart contracts](https://telegra.ph/Its-time-to-try-something-new-Asynchronous-smart-contracts-03-25)

Expand Down
2 changes: 1 addition & 1 deletion docs/v3/concepts/dive-into-ton/ton-blockchain/blockchain-of-blockchains.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,7 +83,7 @@ BaseChain is used for everyday transactions between actors because it's cheap, w
There is a necessity for the synchronization of message routing and transaction execution. In other words, nodes in the network need a way to fix some 'point' in a multichain state and reach a consensus about that state. In TON, a special chain called **MasterChain** is used for that purpose. Blocks of MasterChain contain additional information, like the latest block hashes, about all other chains in the system, thus any observer unambiguously determines the state of all multichain systems at a single MasterChain block.

## See also
- [Smart contract addresses](/v3/concepts/dive-into-ton/ton-blockchain/smart-contract-addresses/)
- [Smart contract addresses](/v3/concepts/dive-into-ton/ton-blockchain/smart-contract-addresses)


<Feedback />
Expand Down
2 changes: 1 addition & 1 deletion docs/v3/concepts/dive-into-ton/ton-blockchain/cells-as-data-storage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,7 @@ If you want more details about cell serialization and deserialization, read [Cel

## See also

- [Blockchain of blockchains](docs/v3/concepts/dive-into-ton/ton-blockchain/blockchain-of-blockchains/)
- [Blockchain of blockchains](/v3/concepts/dive-into-ton/ton-blockchain/blockchain-of-blockchains)
- [TL-B language](/v3/documentation/data-formats/tlb/tl-b-language)

<Feedback />
Expand Down
6 changes: 3 additions & 3 deletions docs/v3/concepts/dive-into-ton/ton-blockchain/smart-contract-addresses.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,12 +77,12 @@ However, raw addresses have two main issues:

Convert raw, user-friendly addresses using [ton.org/address](https://ton.org/address/).

For more details, refer to the refhandling guide in the [Smart contracts addresses documentation](/v3/documentation/smart-contracts/addresses/) section.
For more details, refer to the refhandling guide in the [Smart contracts addresses documentation](/v3/documentation/smart-contracts/addresses) section.

## See also

- [Explorers in TON](/v3/concepts/dive-into-ton/ton-ecosystem/explorers-in-ton/)
- [Smart contracts addresses documentation](/v3/documentation/smart-contracts/addresses/)
- [Explorers in TON](/v3/concepts/dive-into-ton/ton-ecosystem/explorers-in-ton)
- [Smart contracts addresses documentation](/v3/documentation/smart-contracts/addresses)

<Feedback />

8 changes: 4 additions & 4 deletions docs/v3/concepts/dive-into-ton/ton-blockchain/ton-networking.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,10 +19,10 @@ Multi-blockchain projects, such as TON, are much more demanding. For example, on
## TON network protocols

* [TON Connect](/v3/guidelines/ton-connect/overview/)
* [ADNL Protocol](/v3/documentation/network/protocols/adnl/overview/)
* [Overlay Subnetworks](/v3/documentation/network/protocols/overlay/)
* [RLDP Protocol](/v3/documentation/network/protocols/rldp/)
* [TON DHT Service](/v3/documentation/network/protocols/dht/ton-dht/)
* [ADNL protocol](/v3/documentation/network/protocols/adnl/overview/)
* [Overlay subnetworks](/v3/documentation/network/protocols/overlay/)
* [RLDP protocol](/v3/documentation/network/protocols/rldp/)
* [TON DHT service](/v3/documentation/network/protocols/dht/ton-dht/)

## See also
- [TON security audits](/v3/concepts/dive-into-ton/ton-blockchain/security-measures/)
Expand Down
2 changes: 1 addition & 1 deletion docs/v3/concepts/dive-into-ton/ton-ecosystem/explorers-in-ton.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -163,7 +163,7 @@ Please write to one of the [maintainers](/v3/contribute/maintainers).

## See also

- [TON wallet apps](/v3/concepts/dive-into-ton/ton-ecosystem/wallet-apps/)
- [TON wallet apps](/v3/concepts/dive-into-ton/ton-ecosystem/wallet-apps)
- [ton.app/explorers](https://ton.app/explorers)
- [Awesome TON repository](https://github.com/ton-community/awesome-ton)

Expand Down
4 changes: 2 additions & 2 deletions docs/v3/concepts/dive-into-ton/ton-ecosystem/nft.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86,8 +86,8 @@ NFT integrated into a game allows players to own and trade in-game items in a ve

## See also

- [TON wallet apps](/v3/concepts/dive-into-ton/ton-ecosystem/wallet-apps/)
- [Explorers in TON](/v3/concepts/dive-into-ton/ton-ecosystem/explorers-in-ton/)
- [TON wallet apps](/v3/concepts/dive-into-ton/ton-ecosystem/wallet-apps)
- [Explorers in TON](/v3/concepts/dive-into-ton/ton-ecosystem/explorers-in-ton)

<Feedback />

4 changes: 2 additions & 2 deletions docs/v3/documentation/dapps/oracles/red_stone.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ RedStone oracles use an alternative design of providing oracle data to smart con
streams data broadcasting protocol. Data is transferred to the contract by end users, who should attach signed data
packages to their function invocations. The information integrity is verified on-chain through signature checking.

To learn more about RedStone oracles design go to the [RedStone docs](https://docs.redstone.finance/docs/introduction)
To learn more about RedStone oracles design go to the [RedStone docs](https://docs.redstone.finance/docs/introduction).

## Documentation links

Expand Down Expand Up @@ -52,7 +52,7 @@ consisting of hex-values of the particular letters in the string. For example:
`'ETH'` as an `int` is `0x455448` in hex or `4543560` in decimal, as `256*256*ord('E')+256*ord('T')+ord('H')`.

You can use: `feed_id=hexlify(toUtf8Bytes(feed_string))` to convert particular values or
the [endpoint](https://cairo-utils-web.vercel.app/)
the [endpoint](https://cairo-utils-web.vercel.app/).

The value of `feed_ids` should be passed as a serialized `tuple` of `int`s.

Expand Down
2 changes: 1 addition & 1 deletion docs/v3/documentation/data-formats/tlb/crc32.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ import Feedback from '@site/src/components/Feedback';

CRC stands for **Cyclic Redundancy Check**, a widely used method for verifying the integrity of digital data. An error-detecting algorithm checks whether data has been altered during transmission or storage. CRC generates a short checksum or hash from the original data, which is appended to it. The checksum is recalculated and compared with the original upon retrieval or receipt. If the values match, the data is considered intact; if not, it indicates corruption and the data must be resent or recovered.

The CRC32 IEEE variant is used in TL-B schemes. You can refer to this [NFT op code](https://github.com/ton-blockchain/TEPs/blob/master/text/0062-nft-standard.md#tl-b-schema)example to better understand how CRC32 values are calculated for various TL-B messages.
The CRC32 IEEE variant is used in TL-B schemes. You can refer to this [NFT op code](https://github.com/ton-blockchain/TEPs/blob/master/text/0062-nft-standard.md#tl-b-schema) example to better understand how CRC32 values are calculated for various TL-B messages.

## Tools

Expand Down
2 changes: 1 addition & 1 deletion docs/v3/documentation/data-formats/tlb/exotic-cells.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ Library reference cells are used to incorporate libraries in smart contracts.
They always have a level of 0 and contain precisely `8 + 256` bits.

The first byte is always `02`, indicating the cell type.
The following 32 bytes represent the referenced library cell's [Representation hash](/v3/documentation/data-formats/tlb/cell-boc#standard-cell-representation-hash-calculation).
The following 32 bytes represent the referenced library cell's [Representation hash](/v3/documentation/data-formats/tlb/cell-boc#standard-representation-hash-calculation).

### Merkle proof

Expand Down
36 changes: 18 additions & 18 deletions docs/v3/documentation/data-formats/tlb/transaction-layout.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,20 +22,20 @@ transaction$0111 account_addr:bits256 lt:uint64
description:^TransactionDescr = Transaction;
```

| Field | Type | Required | Description |
| ----------------- | ---------------------------------------------------------------------- | -------- |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `account_addr` | bits256 | Yes | The hash of the address where the transaction was executed. [Learn more about addresses](/v3/documentation/smart-contracts/addresses#address-of-smart-contract) |
| `lt` | uint64 | Yes | Represents _Logical time_. [Learn 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 for this account. |
| `prev_trans_lt` | uint64 | Yes | The `lt` of the previous transaction for this account. |
| `now` | uint32 | Yes | The `now`  value set during the transaction execution. It is a UNIX timestamp in seconds. |
| `outmsg_cnt` | uint15 | Yes | The count of outgoing messages generated during the transaction execution. |
| `orig_status` | [AccountStatus](#accountstatus) | Yes | The status of this account before the transaction was executed. |
| `end_status` | [AccountStatus](#accountstatus) | Yes | The status of the account after the transaction was executed. |
| `in_msg` | (Message Any) | No | The incoming message that triggered the transaction execution. Stored as a reference. |
| `out_msgs` | HashmapE 15 ^(Message Any) | Yes | A dictionary containing the outgoing messages created during the transaction execution. |
| Field | Type | Required | Description |
| ----------------- | ---------------------------------------------------------------------- | -------- |------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `account_addr` | bits256 | Yes | The hash of the address where the transaction was executed. [Learn more about addresses](/v3/documentation/smart-contracts/addresses#address-of-smart-contract) |
| `lt` | uint64 | Yes | Represents _Logical time_. [Learn 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 for this account. |
| `prev_trans_lt` | uint64 | Yes | The `lt` of the previous transaction for this account. |
| `now` | uint32 | Yes | The `now` value set during the transaction execution. It is a UNIX timestamp in seconds. |
| `outmsg_cnt` | uint15 | Yes | The count of outgoing messages generated during the transaction execution. |
| `orig_status` | [AccountStatus](#accountstatus) | Yes | The status of this account before the transaction was executed. |
| `end_status` | [AccountStatus](#accountstatus) | Yes | The status of the account after the transaction was executed. |
| `in_msg` | (Message Any) | No | The incoming message that triggered the transaction execution. Stored as a reference. |
| `out_msgs` | HashmapE 15 ^(Message Any) | Yes | A dictionary containing the outgoing messages created during the transaction execution. |
| `total_fees` | [CurrencyCollection](/v3/documentation/data-formats/tlb/msg-tlb#currencycollection) | Yes | The total fees collected during the transaction execution, including _TON coin_ and potentially some [extra-currencies](/v3/documentation/dapps/defi/coins#extra-currencies). |
| `state_update` | [HASH_UPDATE](#hash_update) Account | Yes | The `HASH_UPDATE` structure represents the state change. Stored as a reference. |
| `state_update` | [HASH_UPDATE](#hash_update) Account | Yes | The `HASH_UPDATE` structure represents the state change. Stored as a reference. |
| `description` | [TransactionDescr](#transactiondescr-types) | Yes | A detailed description of the transaction execution process. Stored as a reference. |

## AccountStatus
Expand Down Expand Up @@ -149,11 +149,11 @@ trans_split_prepare$0100 split_info:SplitMergeInfo
= TransactionDescr;
```

| Field | Type | Required | Description |
| ------------ | -------------- | -------- |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `split_info` | SplitMergeInfo | Yes | Contains information about the split process. |
| `storage_ph` | TrStoragePhase | No | Provides details about the storage phase during transaction execution. [More info](/v3/documentation/tvm/tvm-overview#transactions-and-phases) |
| `compute_ph` | TrComputePhase | Yes | CContains details about the compute phase during transaction execution. [More info](/v3/documentation/tvm/tvm-overview#transactions-and-phases) |
| Field | Type | Required | Description |
| ------------ | -------------- | -------- |--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `split_info` | SplitMergeInfo | Yes | Contains information about the split process. |
| `storage_ph` | TrStoragePhase | No | Provides details about the storage phase during transaction execution. [More info](/v3/documentation/tvm/tvm-overview#transactions-and-phases) |
| `compute_ph` | TrComputePhase | Yes | Contains details about the compute phase during transaction execution. [More info](/v3/documentation/tvm/tvm-overview#transactions-and-phases) |
| `action` | TrActionPhase | No | Provides information about the action phase during transaction execution. [More info](/v3/documentation/tvm/tvm-overview#transactions-and-phases). Stored as a reference. |
| `aborted` | Bool | Yes | Indicates whether the transaction execution was aborted. |
| `destroyed` | Bool | Yes | Indicates whether the account was destroyed during execution. |
Expand Down
2 changes: 1 addition & 1 deletion docs/v3/documentation/infra/nodes/mytonctrl/mytonctrl-errors.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,6 +42,6 @@ This document explains the errors that users may encounter with **MyTonCtrl**.

## See also

* [Nodes Troubleshooting](/v3/guidelines/nodes/nodes-troubleshooting)
* [Troubleshooting](/v3/guidelines/nodes/nodes-troubleshooting)
<Feedback />

Loading
Loading