Account
TON Core

TON Core

Verified

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

Username
@toncore
Category
Cryptocurrencies
Country
United Arab EmiratesUnited Arab Emirates
Created
, 2 years
Subscribers7,332+26 last week
Avg views per post, 7d—last 7 days
ERR21.39%30-day average

Subscribers, 30 days

Oct 17 – Nov 15+239 (+3.4%)

Show as table
DateSubscribers
Oct 17, 20267,093
Oct 18, 20267,099
Oct 19, 20267,125
Oct 20, 20267,135
Oct 21, 20267,146
Oct 22, 20267,155
Oct 23, 20267,175
Oct 24, 20267,183
Oct 25, 20267,191
Oct 26, 20267,194
Oct 27, 20267,199
Oct 28, 20267,203
Oct 29, 20267,207
Oct 30, 20267,217
Oct 31, 20267,223
Nov 1, 20267,239
Nov 2, 20267,234
Nov 3, 20267,250
Nov 4, 20267,257
Nov 5, 20267,256
Nov 6, 20267,265
Nov 7, 20267,294
Nov 8, 20267,306
Nov 9, 20267,313
Nov 10, 20267,319
Nov 11, 20267,324
Nov 12, 20267,323
Nov 13, 20267,323
Nov 14, 20267,328
Nov 15, 20267,332

Average views per post by day

By publication day

Show as table
DateAvg views per post
Oct 19, 20261,506
Nov 1, 20261,474
Nov 6, 20261,820

Most viewed this month

  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.

    Photo
    Views1.82K
    Forwards38
    Reactions102
    Comments—
  2. 02
    Views1.51K
    Forwards20
    Reactions35
    Comments—
  3. 03
    Views1.49K
    Forwards12
    Reactions79
    Comments—
  4. 04

    No text

    Photoalbum
    Views1.46K
    Forwards11
    Reactions—
    Comments—

Latest posts

#134Photo

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.

Open in Telegram
Views1,820+16%vs avg
Forwards38
Reactions102
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
2 h995
14 h1,368
27 h1,546
59 h1,734
75 h1,820
  1. After 24 hours1,546
  2. Total to date1,820
#133Photoalbum
Views1,461−7%vs avg
Forwards11
Reactions—
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
11 h1,087
36 h1,298
56 h1,410
73 h1,461
  1. Total to date1,461
#132Photoalbum
Views1,486−5%vs avg
Forwards12
Reactions79
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
11 h1,101
36 h1,321
56 h1,435
73 h1,486
  1. Total to date1,486
#131Text
Views1,506−4%vs avg
Forwards20
Reactions35
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
11 h1,091
31 h1,293
35 h1,312
67 h1,506
  1. After 24 hours1,293
  2. Total to date1,506
#130Text
Views3,933+151%vs avg
Forwards44
Reactions46
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
7 h2,681
8 h2,704
34 h3,465
61 h3,836
70 h3,933
  1. After 6 hours2,681
  2. Total to date3,933
#128Text
Views2,297+46%vs avg
Forwards35
Reactions59
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
6 h1,406
6 h1,408
33 h1,790
58 h2,227
67 h2,297
  1. After 6 hours1,406
  2. Total to date2,297
#127Text
Views1,560−1%vs avg
Forwards18
Reactions25
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
1 h666
1 h669
31 h1,363
72 h1,560
  1. After 1 hour666
  2. After 24 hours1,363
  3. Total to date1,560
#126Text

Forwarded from 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.

Open in Telegram
Views1,038−34%vs avg
Forwards23
Reactions28
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
1 h474
17 h843
26 h896
36 h947
47 h991
59 h1,038
  1. After 1 hour474
  2. After 24 hours896
  3. Total to date1,038
#125Text
Views2,073+32%vs avg
Forwards17
Reactions51
Comments—

All posts

Connections