TON Core
الذهاب إلى القناة على Telegram
Updates from the TON Core development team, which continues to develop open-source technologies for The Open Network (TON) ton.org.
إظهار المزيد7 036
المشتركون
لا توجد بيانات24 ساعات
+617 أيام
+17630 أيام
جاري تحميل البيانات...
القنوات المماثلة
لا توجد بيانات
هل تواجه مشاكل؟ يرجى تحديث الصفحة أو الاتصال بمدير الدعم الخاص بنا.
سحابة العلامات
الإشارات الواردة والصادرة
---
---
---
---
---
---
جذب المشتركين
أكتوبر '26أكتوبر '26
أكتوبر '26
+122
في 8 قنوات
سبتمبر '26
+214
في 13 قنوات
Get PRO
أغسطس '26
+169
في 16 قنوات
Get PRO
يوليو '26
+169
في 7 قنوات
Get PRO
يونيو '26
+375
في 9 قنوات
Get PRO
مايو '26
+1 395
في 44 قنوات
Get PRO
أبريل '26
+622
في 57 قنوات
Get PRO
مارس '26
+517
في 56 قنوات
Get PRO
فبراير '26
+63
في 0 قنوات
Get PRO
يناير '26
+118
في 24 قنوات
Get PRO
ديسمبر '25
+121
في 17 قنوات
Get PRO
نوفمبر '25
+126
في 6 قنوات
Get PRO
أكتوبر '25
+148
في 22 قنوات
Get PRO
سبتمبر '25
+120
في 1 قنوات
Get PRO
أغسطس '25
+276
في 36 قنوات
Get PRO
يوليو '25
+542
في 99 قنوات
Get PRO
يونيو '25
+3 824
في 3 قنوات
| التاريخ | نمو المشتركين | الإشارات | القنوات | |
| 10 أكتوبر | +11 | |||
| 09 أكتوبر | +3 | |||
| 08 أكتوبر | +11 | |||
| 07 أكتوبر | +20 | |||
| 06 أكتوبر | +7 | |||
| 05 أكتوبر | +21 | |||
| 04 أكتوبر | +13 | |||
| 03 أكتوبر | +19 | |||
| 02 أكتوبر | +9 | |||
| 01 أكتوبر | +8 |
منشورات القناة
TON Connect 5.0.0
TON Connect 5.0.0 is now available with improved support for Gram Wallet in Telegram.
dApp developers, please update:
@tonconnect/sdk@5.0.0
@tonconnect/ui@5.0.0
@tonconnect/ui-react@5.0.0
Important: If your dApp uses ton_proof, ensure your implementation follows the documentation, including the get_public_key fallback when the public key cannot be extracted from walletStateInit.
Many Mini Apps currently omit this fallback, which violates the specification and causes authentication to fail with Gram Wallet in Telegram.| 2 | Tolk 1.5 Programming Language
— @inline functions with multiple returns.
— break/continue in loops.
— Type aliases as directional subtypes.
— Reorganized purity concept and dead-code removal.
— Colorful compilation errors with multiple locations and hints.
— Several bytecode optimizations.
PR »
Author's notes » | 2 912 |
| 3 | 🫧 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. | 3 651 |
| 4 | Updated staking smart contract lineup
Single-nominator (v1.1) — Direct validation with one validator and one nominator. The nominator receives 100% of the rewards.
Nominator-pool (v2) — Private staking pools with a small group of nominators and validators.
Liquid-staking — User-facing staking products with many depositors. Issues jettons representing staked Gram for use in DeFi. Used by @StakeeBot and Tonstakers. | 4 118 |
| 5 | Nominator Pool 2.0
Nominator pools let Gram holders stake funds to support network validation and earn rewards without running their own validators.
Nominator Pool 2.0 replaces the original smart contract created in 2022 with a redesigned implementation in Tolk.
Key improvements:
— Up to 32 validators per pool, up from 1.
— Up to 512 nominators per pool, up from 40.
— Reward withdrawals without withdrawing the full stake.
— Lower gas fees.
— Automatic reimbursement of validator gas costs.
— Support for nominators on both the basechain and masterchain.
— A single pool for all validation rounds. Separate pool contracts for even and odd rounds are no longer required.
— A dedicated pool owner management role has been added, separate from validators and nominators.
The contract is fully open source, with comprehensive documentation, a management web UI, and MyTonCtrl support.
https://github.com/ton-blockchain/nominator-pool-v2#ton-nominator-pool-v2-smart-contract | 3 901 |
| 6 | LLM-based content moderation in Toncenter API
Toncenter API now automatically filters inappropriate token images (NFTs and Jettons) using an LLM-based moderation system.
Following the reduction in TON transaction fees, spam and inappropriate content distributed as NFTs have become more noticeable on the network.
Building on its existing manual moderation tools, Toncenter has introduced an LLM-based image analyzer. Images flagged as inappropriate are now served by the API in blurred form. No changes are required for services already using Toncenter API.
Guidelines for Services
Toncenter API v3 metadata includes the following fields to help services handle potentially unsafe or malicious tokens:
- is_nsfw — marks tokens that have been identified as unsafe or potentially unsafe;
- is_scam — marks tokens associated with scams or spam;
- extra._image_big, extra._image_medium, and extra._image_small — contain links to processed token images. Images are resized to standard presets and automatically blurred when a token is marked as unsafe.
To better protect users, we recommend using an opt-in approach when displaying tokens in wallets, explorers, and other services.
By default, show only well-known or trusted tokens and their images. Other tokens and their images should be displayed only after the user explicitly chooses to enable them.
Please note: LLM-based filtering provides an additional layer of protection, but no automated filtering system can guarantee 100% accuracy. Both false negatives and false positives may occur. | 3 501 |
| 7 | Pending API and Streaming API Performance Improvements
We’ve shipped a major performance update to the Pending API, Streaming API and trace processing pipeline.
Key improvements:
— Moved action classification to C++ and integrated it directly into the Trace Emulator.
— Moved external message TTL tracking into the Trace Emulator, removing a separate service from the pipeline.
— Reduced Redis reads across trace processing and Streaming API.
— Made confirmed → finalized trace promotion significantly cheaper by avoiding full trace reprocessing.
With these changes, performance increased by a factor of 2.5. The system demonstrated stability during testing on a testnet at 1,500 TPS on the blockchain.
No changes are required on the part of customers. | 2 728 |
| 8 |  +1TON performance update
With the August 17 update, TON mainnet validators transitioned to a new collator-based architecture. The update has been running stably on mainnet.
The rollout of planned limit increases began on August 27. The first change raised leader_window from 4 to 16.
Single-shardchain performance tests
Two tests were conducted on mainnet to measure single-shardchain performance using a workload that simulated jetton transfers:
— August 25, approximately 10:30 UTC: an input load of approximately 1,200 TPS.
— September 4, approximately 11:30 UTC: an input load of approximately 1,500 TPS.
In the latest test, a single shardchain processed 600–650 TPS in sub-second mode for this workload. As the input load increased further, the shardchain split into two. After split operation latency increased, but the block production rate remained stable.
Next steps
Work to increase single-shardchain performance will continue. The current target is 1,000–2,000 TPS per shardchain.
As a reminder, single-shardchain throughput is not the throughput limit of the entire TON blockchain. TON can run many shardchains in parallel, allowing the network to scale beyond the capacity of any individual shardchain. | 2 765 |
| 9 | Service updates
minter.ton.org
— Updated to jetton-2.1-tolk, the latest jetton smart contract implementation. You can still manage jettons deployed with earlier contract versions.
— Made minor improvements and fixed bugs.
dns.ton.org
— Added support for starting auctions for expired domains.
multisig.ton.org
— Improved security.
unfreezer.ton.org
— Completely rewrote the utility for unfreezing smart contracts frozen due to unpaid storage fees (the tool is primarily intended for developers and is not typically needed by end users).
Updates across all services
Migrated all services to the Toncenter API and updated links. | 2 137 |
| 10 | Node Update TON 2026.08
Following the deployment of TON 2026.07 on August 4, the block production rate and other network metrics returned to their normal levels.
The next update, TON 2026.08, will activate collators on TON mainnet.
Currently, validators both assemble blocks from user transactions and validate them. After the update, these responsibilities will be separated. Dedicated collator nodes will assemble blocks, while validators will only verify them. This separation increases network throughput.
The collator architecture was introduced approximately one year ago in the Accelerator update. Its activation was scheduled for a period of significant load growth. The launch and continued development of native non-custodial wallet in Telegram are expected to increase network activity, making this the appropriate time to activate the architecture.
Since its initial implementation, Accelerator has been adapted to operate in the Sub-Second mode. TON 2026.08 can therefore be referred to as Sub-Second Accelerator.
The update is scheduled for August 17, 2026. All the details will be posted on the @tonstatus channel.
Enabling collators, particularly in in-memory mode, will increase the maximum TPS of a single shardchain.
As the next step, we plan to increase the maximum block size and other network limits. This is possible due to the new network layer introduced in TON 2026.05 and TON 2026.06, which reduced traffic between nodes. Increasing the limits will also lead to a proportional increase in the TPS of a single shardchain. | 6 998 |
| 11 | Node Update TON 2026.07
Following the voting and activation of TON 2026.06, mainnet data from July 22 showed reduced efficiency among some validators. This lowered the average masterchain block rate from ~2.47 to ~2.30 blocks per second, also reduced shardchain block rates, and increased latency for some user operations.
This behavior was not observed during testnet or local testing.
TON 2026.07 retains the legacy broadcast mechanism for now and introduces improvements to the new broadcast mechanism to better account for mainnet conditions.
https://t.me/tonstatus/233 | 3 390 |
| 12 | New Indexer Database Architecture
The database has been divided into three tiers:
Hot — transactions from the last week;
Cold — the complete transaction history;
Key-Value — states, BOCs, and metadata.
This makes processing queries to recent data, which account for most of the load, 2–4× faster.
The architecture is already used in toncenter.com/api/v3 and will later be available as a standalone build.
API V2 Hardware Update
The API V2 server infrastructure for direct requests to liteservers has been upgraded.
New Features
— A new API for nominator pools.
— A new API for validation cycles, including elections and complaints.
— Support for new DeDust V2 actions.
— Fixes and Improvements.
NFT Content Filtering
As network fees have decreased, the risk of spam and inappropriate content being distributed through NFTs has increased.
Toncenter has implemented a manual blacklist for individual NFTs and collections and is developing an automated LLM-based analyzer. Inappropriate pics will be displayed in a blurred form. | 4 239 |
| 13 | How TON Upgrades Are Evolving
To ensure TON’s technical superiority across key metrics, we are systematically upgrading or completely replacing the blockchain’s components and protocols.
Having reduced block time, finalization time, end-to-end latency, and fees, our current objective is to increase shardchain performance: the TPS that the blockchain can sustain in sub-second mode.
2026.03 — new consensus: 10× faster operations.
2026.04 — new Cartesian-tree-based mempool and networking improvements: 6× reduction in fees.
2026.05–2026.06 — new networking layer: QUIC instead of RLDP 1/2 and ADNL transport, Plumtree broadcasts, as well as block-sync and fast-sync overlays. A 2–4× reduction in network traffic.
Upgrading the networking layer is a necessary step toward further increasing shardchain TPS.
The next stages are the activation of the collator + validator architecture, adapted to the new consensus, and the implementation of a new database to replace CellDB 2.0/RocksDB. | 3 837 |
| 14 | New Networking Layer for the TON Blockchain
Following the consensus and mempool upgrades, the blockchain’s networking layer has been completely redesigned.
Versions 2026.04-1 — 2026.06 introduced QUIC as a replacement for RLDP1/2 and the ADNL transport, dedicated block-sync and fast-sync overlays, as well as Plumtree broadcasts.
The new approach reduces inbound node traffic by approximately 4× and outbound traffic by 2×, while improving synchronization and node connectivity.
The 2026.06 update is already deployed on mainnet. Validators will next vote to enable Plumtree, after which the legacy broadcasts will be disabled in a separate update. | 3 029 |
| 15 | Added guidelines for generating sub-wallets from a single mnemonic phrase:
https://github.com/ton-blockchain/TEPs/blob/master/text/0003-wallets.md#11-subwallets | 6 298 |
| 16 | Guidelines for TON wallets regarding mnemonics, IDs, and smart contracts have been published
We ask that wallets and SDKs follow these guidelines to ensure product compatibility.
https://github.com/ton-blockchain/TEPs/blob/master/text/0003-wallets.md | 5 222 |
| 17 | Next technical objective: increasing shardchain performance
Under normal load, TON operates on a single shardchain. Under peak load, dynamic sharding is activated: the network splits into multiple shardchains, increasing throughput while maintaining static fees. In this mode, operation execution time may increase by several seconds.
With TON 2026.05 we start a new series of updates focused on performance improvement of a single shardchain
The objective is to activate dynamic sharding at a load level at which other blockchains cannot operate effectively.
TON 2026.05-rc »
Update timeline » | 10 484 |
| 18 |  One of Acton’s key features is its advanced support for developing smart contracts using AI. | 12 870 |
| 19 | Introducing Acton — a new, modern toolchain for developing smart contracts on TON
Acton covers the full development lifecycle: project creation, testing, debugging, dApp integration, deployment, and verification.
CLI-first by design, it works naturally for both developers and AI agents.
1. One toolchain, not a bunch of utilities.
Create, build, test, lint, format, deploy, and verify TON contracts in a single coherent environment around Tolk.
2. A tighter build-test-debug loop.
Write tests directly in Tolk programming language, run them fast, debug failed transactions, and inspect what actually happened on-chain.
3. Security built in.
Coverage, fuzzing, mutation testing, gas profiling, and CI help catch regressions early.
4. A native debugger.
Step in, step over, step out, watch variables, and inspect the call stack. A smooth Web2-style developer experience, now inside a blockchain language.
5. Friendly for AI agents.
A modern CLI tool that becomes an agent's runtime, with skills and manuals bundled.
Read more »
Docs »
Author's notes » | 8 124 |
| 20 | Tolk 1.4 Programming Language
Introducing source maps, debugger support, ABI export, and auto-generated TypeScript wrappers.
— ABI export for toolchains, explorers, SDKs, and UI integrations.
— Auto-generated TypeScript wrappers for Tolk smart contracts.
— Source maps that connect TVM execution back to Tolk source code, variables, stack layout, and call frames.
— Debugger marks that enable step-by-step debugging of fully optimized production contracts.
— Language enhancements continuing Tolk’s evolution toward a general-purpose smart contract language.
Release » | 4 969 |
