Кабинет
TON Core

TON Core

Подтверждён

Updates from the TON Core development team, which continues to develop open-source technologies for The Open Network (TON) ton.org.

Юзернейм
@toncore
Категория
Криптовалюты
Страна
ОАЭОАЭ
Создан
, 2 года
Подписчики7 332+26 за неделю
Просмотров на пост, 7 дн.—за 7 дней
ERR21,39 %в среднем за 30 дней

Подписчики, 30 дней

17 окт. – 15 нояб.+239 (+3,4%)

Показать таблицей
ДатаПодписчики
17 окт. 2026 г.7 093
18 окт. 2026 г.7 099
19 окт. 2026 г.7 125
20 окт. 2026 г.7 135
21 окт. 2026 г.7 146
22 окт. 2026 г.7 155
23 окт. 2026 г.7 175
24 окт. 2026 г.7 183
25 окт. 2026 г.7 191
26 окт. 2026 г.7 194
27 окт. 2026 г.7 199
28 окт. 2026 г.7 203
29 окт. 2026 г.7 207
30 окт. 2026 г.7 217
31 окт. 2026 г.7 223
1 нояб. 2026 г.7 239
2 нояб. 2026 г.7 234
3 нояб. 2026 г.7 250
4 нояб. 2026 г.7 257
5 нояб. 2026 г.7 256
6 нояб. 2026 г.7 265
7 нояб. 2026 г.7 294
8 нояб. 2026 г.7 306
9 нояб. 2026 г.7 313
10 нояб. 2026 г.7 319
11 нояб. 2026 г.7 324
12 нояб. 2026 г.7 323
13 нояб. 2026 г.7 323
14 нояб. 2026 г.7 328
15 нояб. 2026 г.7 332

Средние просмотры поста по дням

По дню публикации

Показать таблицей
ДатаПросмотров на пост
19 окт. 2026 г.1 506
1 нояб. 2026 г.1 474
6 нояб. 2026 г.1 820

Самые просматриваемые за месяц

  1. 01

    Understanding TON’s New Networking Architecture Nearly every update over the past year has introduced incremental changes to TON’s network architecture to improve security, reduce traffic and increase performance. As a result, TON’s network architecture has changed substantially. This article describes the new architecture. 1. Shared private overlays The masterchain and each shardchain have a separate private overlay. Each now includes all validators (~400) and all collators. Previously, these overlays included only their respective current validators and collators. Blocks were shared with the remaining validators and collators through a separate block-sync overlay. The block-sync overlay has now been removed, simplifying the network topology. 2. Protected overlay The protected overlay serves critical infrastructure supporting the blockchain, including rebroadcaster nodes. It was previously called fast-sync. That name is no longer appropriate: fast synchronization is a requirement for every overlay, including the public overlay. The protected overlay is intended to improve the security and stability of the blockchain and its critical infrastructure. 3. Validator and collator isolation Validators and collators no longer communicate directly over the public overlay. Rebroadcasters forward blocks to the public overlay and relay external messages in the opposite direction. This isolation improves security and reduces validators’ network traffic and CPU usage. The freed resources will be used to increase network performance. 4. Rebroadcasters Rebroadcaster code is open source and will be merged into the main branch soon. Like collators, rebroadcaster nodes are operated by some validator operators. Additional rebroadcaster deployments are not currently required. 5. Three broadcast types: Gossip, Two-Step and Plumtree Two-Step Broadcast was developed as part of Sub-Second update for private validator overlays. Plumtree Broadcast is a new Plumtree-like implementation designed for overlays with dynamic membership. It maintains reliable synchronization even when a large proportion of nodes perform poorly. It is used in the public and protected overlays. The implementation differs from the classic Plumtree algorithm but follows the same underlying ideas. Gossip Broadcast, the original implementation, remains in limited use for some broadcast types. 6. Replacing RLDP1/2 with QUIC QUIC was standardized in May 2021 as RFC 9000. TON’s initial networking implementation predated this standardization and used custom RLDP protocols for reliable data transfer, with functionality similar to QUIC. During 2026, RLDP1/2 have been progressively replaced with QUIC. The next update will complete the migration, after which RLDP1/2 will no longer be used in the TON blockchain.

    Фото
    Просмотры1,82 тыс.
    Пересылки38
    Реакции102
    Комментарии—
  2. 02
    Просмотры1,51 тыс.
    Пересылки20
    Реакции35
    Комментарии—
  3. 03
    Просмотры1,49 тыс.
    Пересылки12
    Реакции79
    Комментарии—
  4. 04

    Без текста

    Фотоальбом
    Просмотры1,46 тыс.
    Пересылки11
    Реакции—
    Комментарии—

Новые посты

#134Фото

Understanding TON’s New Networking Architecture Nearly every update over the past year has introduced incremental changes to TON’s network architecture to improve security, reduce traffic and increase performance. As a result, TON’s network architecture has changed substantially. This article describes the new architecture. 1. Shared private overlays The masterchain and each shardchain have a separate private overlay. Each now includes all validators (~400) and all collators. Previously, these overlays included only their respective current validators and collators. Blocks were shared with the remaining validators and collators through a separate block-sync overlay. The block-sync overlay has now been removed, simplifying the network topology. 2. Protected overlay The protected overlay serves critical infrastructure supporting the blockchain, including rebroadcaster nodes. It was previously called fast-sync. That name is no longer appropriate: fast synchronization is a requirement for every overlay, including the public overlay. The protected overlay is intended to improve the security and stability of the blockchain and its critical infrastructure. 3. Validator and collator isolation Validators and collators no longer communicate directly over the public overlay. Rebroadcasters forward blocks to the public overlay and relay external messages in the opposite direction. This isolation improves security and reduces validators’ network traffic and CPU usage. The freed resources will be used to increase network performance. 4. Rebroadcasters Rebroadcaster code is open source and will be merged into the main branch soon. Like collators, rebroadcaster nodes are operated by some validator operators. Additional rebroadcaster deployments are not currently required. 5. Three broadcast types: Gossip, Two-Step and Plumtree Two-Step Broadcast was developed as part of Sub-Second update for private validator overlays. Plumtree Broadcast is a new Plumtree-like implementation designed for overlays with dynamic membership. It maintains reliable synchronization even when a large proportion of nodes perform poorly. It is used in the public and protected overlays. The implementation differs from the classic Plumtree algorithm but follows the same underlying ideas. Gossip Broadcast, the original implementation, remains in limited use for some broadcast types. 6. Replacing RLDP1/2 with QUIC QUIC was standardized in May 2021 as RFC 9000. TON’s initial networking implementation predated this standardization and used custom RLDP protocols for reliable data transfer, with functionality similar to QUIC. During 2026, RLDP1/2 have been progressively replaced with QUIC. The next update will complete the migration, after which RLDP1/2 will no longer be used in the TON blockchain.

Открыть в Telegram
Просмотры1 820+16%к среднему
Пересылки38
Реакции102
Комментарии—
Динамика просмотровСкрыть динамику

Рост просмотров

Часов после публикации

Показать таблицей
Часов после публикацииПросмотры
0 ч0
2 ч995
14 ч1 368
27 ч1 546
59 ч1 734
75 ч1 820
  1. Через 24 часа1 546
  2. Всего сейчас1 820
#133Фотоальбом
Просмотры1 461−7%к среднему
Пересылки11
Реакции—
Комментарии—
Динамика просмотровСкрыть динамику

Рост просмотров

Часов после публикации

Показать таблицей
Часов после публикацииПросмотры
0 ч0
11 ч1 087
36 ч1 298
56 ч1 410
73 ч1 461
  1. Всего сейчас1 461
#132Фотоальбом
Просмотры1 486−5%к среднему
Пересылки12
Реакции79
Комментарии—
Динамика просмотровСкрыть динамику

Рост просмотров

Часов после публикации

Показать таблицей
Часов после публикацииПросмотры
0 ч0
11 ч1 101
36 ч1 321
56 ч1 435
73 ч1 486
  1. Всего сейчас1 486
#131Текст
Просмотры1 506−4%к среднему
Пересылки20
Реакции35
Комментарии—
Динамика просмотровСкрыть динамику

Рост просмотров

Часов после публикации

Показать таблицей
Часов после публикацииПросмотры
0 ч0
11 ч1 091
31 ч1 293
35 ч1 312
67 ч1 506
  1. Через 24 часа1 293
  2. Всего сейчас1 506
#130Текст
Просмотры3 933+151%к среднему
Пересылки44
Реакции46
Комментарии—
Динамика просмотровСкрыть динамику

Рост просмотров

Часов после публикации

Показать таблицей
Часов после публикацииПросмотры
0 ч0
7 ч2 681
8 ч2 704
34 ч3 465
61 ч3 836
70 ч3 933
  1. Через 6 часов2 681
  2. Всего сейчас3 933
#129Текст
Просмотры1 782+14%к среднему
Пересылки19
Реакции24
Комментарии—
Динамика просмотровСкрыть динамику

Рост просмотров

Часов после публикации

Показать таблицей
Часов после публикацииПросмотры
0 ч0
7 ч1 265
8 ч1 272
34 ч1 563
61 ч1 739
70 ч1 782
  1. Через 6 часов1 265
  2. Всего сейчас1 782
#128Текст
Просмотры2 297+46%к среднему
Пересылки35
Реакции59
Комментарии—
Динамика просмотровСкрыть динамику

Рост просмотров

Часов после публикации

Показать таблицей
Часов после публикацииПросмотры
0 ч0
6 ч1 406
6 ч1 408
33 ч1 790
58 ч2 227
67 ч2 297
  1. Через 6 часов1 406
  2. Всего сейчас2 297
#127Текст
Просмотры1 560−1%к среднему
Пересылки18
Реакции25
Комментарии—
Динамика просмотровСкрыть динамику

Рост просмотров

Часов после публикации

Показать таблицей
Часов после публикацииПросмотры
0 ч0
1 ч666
1 ч669
31 ч1 363
72 ч1 560
  1. Через 1 час666
  2. Через 24 часа1 363
  3. Всего сейчас1 560
#126Текст

Переслано из TOLK lang

🫧 Introducing new tools beyond smart-contract development In May, we released Tolk v1.4 and Acton — a new toolchain for building and testing TON smart contracts. Since then, we've been working on the next part of the problem. Writing a contract is only the on-chain part of dApp development. Once the contract is ready, you need an environment to work with the network, inspect transactions, verify deployed code, and run E2E scenarios — including the off-chain part. So we've been extending Acton in that direction. 🔍 Actonscan A developer-focused explorer built around Tolk ABI. Messages, get-methods, errors and storage are displayed in human-readable format instead of raw bytes. You can inspect transaction flows, emulate messages, call get-methods, explore storage mutations and network configuration. Actonscan is based on an open-source ABI catalog with 200+ frequently used contracts, so even deployed FunC bytecode can be described through Tolk types. Visit: actonscan.com and the ABI catalog. 🧪 Acton Studio A local workspace for developing the off-chain part of a dApp. Use TON Center and LiteAPI, test off-chain integration and cross-chain bridges, and check that an indexer correctly parses transactions. Two environments are available: Simulator — a fast, controllable local network. Start in 0.1 sec, fork mainnet, modify state of any account, mint jettons, time-travel blockchain.now, create snapshots, and reproduce scenarios locally. Localnet — a real TON network running actual C++ validators, liteservers and APIs in Docker. Both can be used from the CLI, making them suitable for automation, E2E tests, CI, and agents. Studio also provides UI for faucets, an embedded Actonscan, state/blocks/config view, and debugging transactions directly in the browser — for any local environment. Try: acton up and follow the docs. 🔐 TON Verifier revisited The new Verifier connects deployed code back to its source using code hash. It provides the source code, ABI, and source maps. There is no IPFS involved — contract sources are kept on GitHub and served by a dedicated backend. This means an explorer automatically understands a newly deployed contract once it's verified — showing human-readable traces and allowing failed transactions to be debugged step by step directly from the browser. Visit: verifier.ton.org. 🌳 From contracts to dApps Tolk is a language for smart contracts. With its auto-generated ABI, it provides the standard interface for external tools. Acton covers the entire on-chain development lifecycle: testing, debugging, publishing, and everything around the contract itself. Acton Studio extends that workflow to the off-chain layer of dApps — local networks and APIs, snapshots, and E2E integrations. It's the natural next step: not just developing smart contracts, but building the applications around them.

Открыть в Telegram
Просмотры1 038−34%к среднему
Пересылки23
Реакции28
Комментарии—
Динамика просмотровСкрыть динамику

Рост просмотров

Часов после публикации

Показать таблицей
Часов после публикацииПросмотры
0 ч0
1 ч474
17 ч843
26 ч896
36 ч947
47 ч991
59 ч1 038
  1. Через 1 час474
  2. Через 24 часа896
  3. Всего сейчас1 038
#125Текст
Просмотры2 073+32%к среднему
Пересылки17
Реакции51
Комментарии—

Все посты

Связи

Похожие каналы

Кто упоминает

Все упоминания