TON Core

Sub-Second for the TON Ecosystem As part of the Sub-Second mainnet rollout, ecosystem participants should review the following guidance. For Validators and Node owners Follow @tonstatus. For API developers Please update your own nodes as described in the corresponding post. APIs will continue functioning after the network upgrade. No additional compatibility changes are required. If you were previously using low-end hardware, you may need to upgrade it due to the increased block rate To deliver near-instant UX, we recommend adopting the latest API practices: — Enable WebSockets support. — Optimize general API latency. — Support Pending and Confirmed operation statuses. You can refer to the changes in the Toncenter API. For exchanges and payment services If you are running your own node, please update it as described in the corresponding post. If you are using an API, whether external or self-hosted, no action is required. No additional changes are needed. Transaction finality should continue to be determined based on masterchain finalization, as before. For products and dApps If you are running your own node, please update it as described in the corresponding post. If you are using an API, whether external or self-hosted, no action is required. Products and APIs will continue functioning after the network upgrade. No additional compatibility changes are required. To deliver near-instant UX, we recommend adopting the latest UX practices: — Use Toncenter Streaming API V2. — Display an operation in the UI once it reaches Pending status. — Mark an operation as completed once it reaches Confirmed status. You can refer to the changes in mytonwallet.io and tonscan.org.

Sub-Second is Live The vote to enable Sub-Second has passed, and the blockchain has switched to the new high-speed mode. The blockchain is currently running stably. About 7% of validators have not yet updated, so the block production rate is still slightly below the target We ask validators who have not yet updated to do so. API developers and product developers — please make sure everything is working properly in your services.

Scheduled Closure of the Token Bridge V3 Effective April 27 at 12:00 UTC, token transfers from Ethereum to TON through the bridge-v3.ton.org will be permanently discontinued. Claims for previously completed transfers will remain available. Transfers from TON to Ethereum will remain available. The token-amount-based fee for such transfers will be removed. This is a planned closure of the Token Bridge V3, following the earlier discontinuation of jUSDT and Toncoin transfers. All user funds remain safe. The Token Bridge played an important role in the early development of the TON ecosystem. The ecosystem is transitioning to newer cross-chain solutions: https://ton.org/bridges

Blockchain Fee Reduction The TON Core team has prepared a blockchain update (TON 2026.04, TON 2026.04-1) to reduce fees by 6x, in line with Pavel Durov’s MTONGA plan. This update includes: 1) Performance improvements The previous Sub-Second update improved not only operation speed but also overall blockchain performance, making a fee reduction possible. Since then, additional optimizations and performance improvements have also been implemented, including a new mempool based on a persistent Cartesian tree. 2) Fixes In addition to performance improvements, this update will include fixes for issues identified on mainnet after the Sub-Second release. In particular, it addresses loss of synchronization on some liteservers and rare block rate instability. Planned Schedule: April 28, 2026 12:00 UTC — Validator software update. April 30, 2026 13:00 UTC — Vote to lower gas prices in the blockchain configuration. Lower fees are important for the next stages of the MTONGA plan. Since fees do not constitute a significant portion of validator rewards, validator rewards are expected to decrease by less than 0.4%. Mainnet validator operators are asked to be prepared to update their software on 28 April and to participate in the vote on 30 April.

Voting by validators on reducing network fees has begun Validators, please participate in the vote. Follow the voting progress here. UPD: All proposals were accepted, fees on the mainnet have been reduced, thank you!

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 »

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

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

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

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.

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.

🫧 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, A

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 »