TON activates collators Aug. 17, validators vote Aug. 21 on execution

TON's 2026.08 network upgrade activates collator architecture on mainnet Aug. 17, moving block assembly to dedicated collator nodes while validators handle verification only.

TON Core said the handover separates assembly from verification to push throughput while keeping validator duties focused. TON Status told validators to update mytonctrl to commit 7e90e26 and node software to commit 140320b, and to be ready to vote at 08:00 UTC on Aug. 21 on configuration switches tied to execution and queueing.

The design draws from TON's Accelerator work and adapts it for Sub-Second mode. In-memory collators are expected to raise the maximum TPS on a single shardchain, according to TON Core. The immediate effect on user-visible speed depends on configuration toggles that follow the switch.

Activation alone does not pick execution rules or queue behavior. Validators will vote on dispatch queue activation, transaction executor behavior changes and an increased minimal split after the handover. The vote is scheduled for 08:00 UTC on Aug. 21, 2026.

The code path landed weeks earlier. The project tagged v2026.07 on Aug. 3 with QUIC broadcast improvements, new QUIC metrics and stability fixes. Infrastructure providers reported mainnet deployment around Aug. 4, tying the build to early-August maintenance windows. Status pages through the month, including QuickNode, referenced collator-related protocol fixes such as PeerId handling in node and tooling. The plumbing moved first so the collator switch could be isolated to a configuration-gated handover.

For validators, the bottleneck is readiness — specific commits and a narrow vote window set by TON Status. The scheduled network update lands Aug. 12, 2026, ahead of the collator activation on Aug. 17.

The collator shift is part of TON's broader push to improve network efficiency. By taking assembly off validators, the network targets lower latency during production. The separation of assembly and verification is designed to push throughput while keeping validator duties focused on finalization. This architecture mirrors approaches seen in other sharded networks, where block production and validation are decoupled to scale transaction processing.

The vote outcome on Aug. 21 will determine how the network handles dispatch queueing, transaction execution and shard splitting thresholds. These configuration choices directly affect user-visible performance — including how quickly transactions confirm and how the network scales under load. For TON, which competes with other high-throughput L1s for developer mindshare and user activity, the success of this upgrade could influence its positioning in the broader blockchain infrastructure race.

Successful implementation could strengthen confidence in the TON ecosystem and support the network's competitive position. However, validator coordination failures or upgrade issues could pose short-term network disruption risks.

This article is for informational purposes only and does not constitute investment advice.