The Open Network has published TON v2026.10, a signed node-software release whose headline change removes validators and collators from public overlays. The official release notes say that separation is intended to improve stability. The update also changes external-message handling, optimises QUIC networking and starts the retirement path for RLDP2.

Validators and collators leave public overlays

TON’s notes say validators and collators have been removed from public overlays “to improve stability.” In practical terms, the change reduces their exposure within the public-facing overlay layer used to exchange network data. The release note is concise and does not publish benchmark results, incident data or a measured before-and-after stability comparison.

That distinction matters: a software design change can reduce one class of operational risk without proving that every operator has upgraded or that the live network is already performing differently.

External-message processing gets new controls

The release adds configurable limits for external-message mempools, fixes the sending of large messages and enables external-message broadcasts in fast-sync overlays. External messages are a route through which activity reaches the chain, so queue limits and propagation behaviour are operationally important during bursts of traffic.

However, TON’s release notes do not supply a transaction-throughput forecast. NetNapz therefore treats these items as node-level engineering changes, not evidence of a confirmed increase in chain capacity.

QUIC optimisation and the RLDP2 retirement path

TON also says QUIC was optimised. At the same time, RLDP2 is now deprecated and is expected to be removed in a future release. Deprecation is a warning to operators and software maintainers that reliance on the older transport should be reviewed; it is not the same as immediate removal in v2026.10.

The release additionally references global versions 16 and 17, including a change to global-balance calculation, alongside metrics improvements, stability fixes and contributions arising from the project’s bug-bounty programme. The public note does not provide enough detail to quantify the economic effect of the global-balance change, so no such conclusion should be inferred from the release alone.

What operators should verify

• Compatibility: test node and monitoring integrations against v2026.10 before production rollout.
• Transport dependencies: identify tooling that still depends on RLDP2 ahead of its eventual removal.
• Mempool configuration: review the new external-message limits for the operator’s workload rather than assuming defaults fit every deployment.
• Release authenticity: use the signed release and official repository rather than third-party binaries.

NetNapz assessment

The most consequential signal is architectural rather than market-facing: TON is tightening the separation between consensus-critical participants and public overlays while preparing to retire an older transport. That can be constructive for operational resilience, but the release is not proof of universal adoption, higher realised throughput or increased demand for Toncoin.

Those outcomes require separate evidence—operator upgrade data, observed network metrics and usage figures. Investors should also avoid treating a protocol release as a direct price catalyst without those supporting indicators.

Primary source and limitations

NetNapz reviewed the official TON v2026.10 release page and its signed release record. This report paraphrases that first-party material and separates the documented software changes from NetNapz assessment. No claim is made here about adoption levels, validator participation, token price or network-wide performance because the release page does not establish them.