You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: ecosystem/analytics.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,7 +50,7 @@ Dune analytics allows projects to build bespoke data marts for each protocol —
50
50
51
51
#### Decoding raw data
52
52
53
-
Since TON handles complex [data structures](/foundations/serialization/cells/) and doesn't have ABIs, a [special decoding framework](https://github.com/duneanalytics/spellbook/blob/main/dbt_subprojects/daily_spellbook/macros/project/ton/README.md) was created. It works on top of the [Spellbook](https://github.com/duneanalytics/spellbook) — a powerful tool for building custom tables with [dbt](https://github.com/dbt-labs/dbt-core) and Jinja macros. It helps decode important information from raw protocol message payloads.
53
+
Since TON handles complex [data structures](/foundations/serialization/cells/) and doesn't have ABIs, a [special decoding framework](https://github.com/duneanalytics/spellbook/blob/main/dbt_subprojects/daily_spellbook/macros/project/ton/README.md) was created. It works on top of the [Spellbook](https://github.com/duneanalytics/spellbook) — a powerful tool for building custom tables with [`dbt`](https://github.com/dbt-labs/dbt-core) and Jinja macros. It helps decode important information from raw protocol message payloads.
54
54
55
55
The following protocols are decoded using this framework and serve as examples:
"description": "Send query - unpacked external message. This method takes address, body and init-params (if any), packs it to external message and sends to network. All params should be boc-serialized.",
2181
+
"description": "Send query - unpacked external message. This method takes address, body and init-params (if any), packs it to external message and sends to network. All params should be BoC-serialized.",
2182
2182
"operationId": "send_query_sendQuery_post",
2183
2183
"requestBody": {
2184
2184
"content": {
@@ -2449,18 +2449,18 @@
2449
2449
"body": {
2450
2450
"type": "string",
2451
2451
"title": "Body",
2452
-
"description": "b64-encoded boc-serialized cell with message body"
2452
+
"description": "b64-encoded BoC-serialized cell with message body"
2453
2453
},
2454
2454
"init_code": {
2455
2455
"type": "string",
2456
2456
"title": "Init Code",
2457
-
"description": "b64-encoded boc-serialized cell with init-code",
2457
+
"description": "b64-encoded BoC-serialized cell with init-code",
2458
2458
"default": ""
2459
2459
},
2460
2460
"init_data": {
2461
2461
"type": "string",
2462
2462
"title": "Init Data",
2463
-
"description": "b64-encoded boc-serialized cell with init-data",
2463
+
"description": "b64-encoded BoC-serialized cell with init-data",
Copy file name to clipboardExpand all lines: ecosystem/explorers/overview.mdx
+10-8Lines changed: 10 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,28 +5,30 @@ title: "Overview"
5
5
Explorers are web tools for reading blockchain data. They let you look up accounts, transactions, blocks, and smart contracts, making it easy to verify activity and debug issues.
6
6
7
7
### Explorer
8
+
8
9
A blockchain explorer is a website that indexes on‑chain data and presents it in a searchable user interface (UI). In TON, explorers commonly show account balances, recent transactions, jettons and non‑fungible tokens (NFTs), contract code and state, and links to related blocks and messages.
9
10
10
11
### What explorers show
12
+
11
13
- Balances and assets: TON, jettons, and NFTs held by an address
12
14
- Transactions and messages: history, fees, phases, and traces
13
-
- Blocks and validators: block contents, MasterChain and ShardChain details
15
+
- Blocks and validators: block contents, masterchain and shardchain details
14
16
- Smart contracts: code, state, disassembly, and known contract type
15
17
- Analytics: top entities, volumes, gas, fees, and network health
16
18
17
19
### Indexers
20
+
18
21
Indexers continuously read blocks from nodes, parse messages and transactions, and store them in a database optimized for queries. Explorers rely on these indexers to provide fast search, traces, higher‑level events, and historical views beyond what a single node exposes by default.
19
22
20
23
### Explorers comparison
21
24
22
-
| Explorer | Type | Mainnet | Testnet | Official |
23
-
| --- | --- | --- | --- | --- |
24
-
| Tonviewer | General‑purpose |[tonviewer.com](https://tonviewer.com/)|[Testnet](https://testnet.tonviewer.com/)| No |
25
-
| Tonscan.org | General‑purpose |[tonscan.org](https://tonscan.org/)|[Testnet](https://testnet.tonscan.org/)| No |
26
-
| Tonscan.com | General‑purpose |[tonscan.com](https://tonscan.com/)| - | No |
27
-
| TON Explorer | Low‑level/core |[explorer.toncoin.org](https://explorer.toncoin.org/)|[Testnet](https://test-explorer.toncoin.org)| Yes |
|`validator`| Validator functions. Activates participating in elections and staking. |
28
-
|`nominator-pool`| Standard nominator pools. |
29
-
|`single-nominator`| Orbs' single nominator pools. |
30
-
|`liquid-staking`| Liquid staking controllers. |
31
-
|`liteserver`| For liteserver usage only without validator. |
32
-
|`collator`| Blocks collator-only module. |
33
-
|`alert-bot`| Telegram bot alerts |
34
-
|`prometheus`| Prometheus format data exporter |
28
+
|`nominator-pool`| Standard nominator pools. |
29
+
|`single-nominator`| Orbs' single nominator pools. |
30
+
|`liquid-staking`| Liquid staking controllers. |
31
+
|`liteserver`| For liteserver usage only without validator. |
32
+
|`collator`| Blocks collator-only module. |
33
+
|`alert-bot`| Telegram bot alerts |
34
+
|`prometheus`| Prometheus format data exporter |
35
35
36
36
**Example**
37
37
@@ -51,7 +51,7 @@ benchmark
51
51
52
52
**Behavior**
53
53
54
-
- Runs a bundled benchmark script with elevated privileges. The script executes two FIO scenarios (random 4K with queue depths 64 and 1) and a RocksDB stress test.
54
+
- Runs a bundled benchmark script with elevated privileges. The script executes two I/O scenarios (random 4K with queue depths 64 and 1) and a RocksDB stress test.
55
55
- The run takes up to \~200 seconds; the console blocks until completion.
56
56
- Results are printed as a table with read/write throughput, IOPS, and RocksDB random operations. On failure, the command prints the captured error log.
57
57
@@ -218,7 +218,7 @@ installer enable THA
218
218
219
219
## rollback
220
220
221
-
**Purpose:** Revert MyTonCtrl to the legacy “MTC1” configuration format.
221
+
**Purpose:** Revert MyTonCtrl to the legacy `MTC1` configuration format.
222
222
223
223
**Syntax**
224
224
@@ -247,7 +247,7 @@ status fast
247
247
248
248
- Without arguments, the command aggregates live data from the validator, lite-client, system metrics, and Git repositories. It prints:
- Local node metrics: validator index and efficiency, ADNL addresses, wallet balances, CPU/memory/swap/disk utilization, network throughput, service uptimes (mytoncore, validator, btc\_teleport when applicable), virtualization detection, version information for MyTonCtrl, TON binaries, and optional BTC Teleport.
250
+
- Local node metrics: validator index and efficiency, ADNL addresses, wallet balances, CPU/memory/swap/disk utilization, network throughput, service uptimes (mytoncore, validator, `btc_teleport` when applicable), virtualization detection, version information for MyTonCtrl, TON binaries, and optional BTC Teleport.
251
251
- Additional election metadata for validator nodes, including config parameters and the expected validation/election timeline.
252
252
-`status fast` skips remote calls that enumerate validators and offers, which is useful on constrained connections or when you only need the local section.
253
253
- If the node is out of sync, the report focuses on local health and prints warnings instead of global network data.
Copy file name to clipboardExpand all lines: ecosystem/node/mytonctrl/liquid_staking.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ create_controllers
25
25
**Behavior**
26
26
27
27
- Compares the controller addresses returned by the pool (`GetControllers`) with the addresses stored in the local database.
28
-
- If they differ, downloads the jetton pool deployment scripts (on first run), signs the deployment BOCs with the validator wallet, and sends them to the liquid pool with a small attach value.
28
+
- If they differ, downloads the jetton pool deployment scripts (on first run), signs the deployment BoCs with the validator wallet, and sends them to the liquid pool with a small attach value.
29
29
- Stores the newly active controllers under `using_controllers` so subsequent staking and voting commands target the fresh contracts.
Copy file name to clipboardExpand all lines: ecosystem/node/mytonctrl/pools.mdx
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,7 +55,7 @@ delete_pool <pool-name>
55
55
56
56
**Behavior**
57
57
58
-
- Deletes the BOC/address files created for `<pool-name>` from the pools directory; on-chain contracts remain untouched.
58
+
- Deletes the BoC/address files created for `<pool-name>` from the pools directory; on-chain contracts remain untouched.
59
59
- Useful when you migrate a pool to another host or retire a test deployment.
60
60
61
61
**Example**
@@ -105,7 +105,7 @@ activate_pool <pool-name>
105
105
106
106
- Loads `<pool-name>-query.boc` and ensures the validator wallet is active.
107
107
- If the pool account is still empty, it signs and broadcasts the deployment message; if it is already active, it logs a warning and exits without changes.
108
-
- Leaves the deployment BOC in place so you can retry if the transaction fails.
108
+
- Leaves the deployment BoC in place so you can retry if the transaction fails.
0 commit comments