Mainnet Validator Software Update [v2026.04]
Please update your node software (see "Target versions") and vote for full Catchain 2.0 activation:
Update with mytonctrl:
Target versions:
— mytonctrl:
— node
If you are not using mytonctrl or using ubuntu older than 22.04, check this instruction (https://telegra.ph/TON-Node-Upgrade-202511-11-05).
If you have several validators, please update them one by one:
update a validator => wait for synchronization => move to the next one validator
⚠️ Updated instructions related to opening QUIC port is available. It includes details how to check whether your validator setup is correct, please use it.
__________________________________________________
Update is mandatory for validators and contains measures to improve stability and defense of validators in crowded overlays under elevated TPS loads, as well as tooling for fine-tuning QUIC transport.
It is not required for liteservers and archive liteservers.
This release does not include breaking API changes and is fully compatible with recent versions of ton-http-api (acceptable versions: v2.0.64 and higher) and TON Indexer (acceptable versions: v1.2.6 and higher).
Node changelog.
Mytonctrl changelog.
Please update your node software (see "Target versions") and vote for full Catchain 2.0 activation:
Update with mytonctrl:
update master
upgrade master
vo 105891622821359345175052772982283277971723874256514599276871132830604887326799
Target versions:
— mytonctrl:
dedc7aa— node
76f0ac2If you are not using mytonctrl or using ubuntu older than 22.04, check this instruction (https://telegra.ph/TON-Node-Upgrade-202511-11-05).
If you have several validators, please update them one by one:
update a validator => wait for synchronization => move to the next one validator
⚠️ Updated instructions related to opening QUIC port is available. It includes details how to check whether your validator setup is correct, please use it.
__________________________________________________
Update is mandatory for validators and contains measures to improve stability and defense of validators in crowded overlays under elevated TPS loads, as well as tooling for fine-tuning QUIC transport.
It is not required for liteservers and archive liteservers.
This release does not include breaking API changes and is fully compatible with recent versions of ton-http-api (acceptable versions: v2.0.64 and higher) and TON Indexer (acceptable versions: v1.2.6 and higher).
Node changelog.
Mytonctrl changelog.
Catchain 2.0 activation
The proposal to activate Catchain 2.0 passed the first round with more than 85% support. Thank you!
We expect activation to take place shortly after the start of the next round, around 7:00 a.m. UTC.
⚠️ At the moment, about 7% of the network has not yet been updated. Please:
1) update immediately and
2) open QUIC port (QUIC instructions) and verify that the QUIC port is available on validators.ton.org.
The proposal to activate Catchain 2.0 passed the first round with more than 85% support. Thank you!
We expect activation to take place shortly after the start of the next round, around 7:00 a.m. UTC.
⚠️ At the moment, about 7% of the network has not yet been updated. Please:
1) update immediately and
2) open QUIC port (QUIC instructions) and verify that the QUIC port is available on validators.ton.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.
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.
Forwarded from TON Core
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
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
Lite Server and Full Node operators
A new update is available to improve node stability and synchronization. Operators experiencing issues (including error 651) with their nodes are advised to update.
This update applies to Lite Servers and Full Nodes only. Validators do not need to update.
A new update is available to improve node stability and synchronization. Operators experiencing issues (including error 651) with their nodes are advised to update.
master branch: 03cc3da51db03b8876c2cc2a43fd46410ff8bc34.This update applies to Lite Servers and Full Nodes only. Validators do not need to update.
Liteserver Synchronization Instability
Over the past several days, multiple operators have reported liteserver synchronization issues.
Our analysis has identified several potential causes affecting block and external message propagation in public overlays. We have already deployed a number of mitigations to reduce the impact. However, a full resolution will require additional analysis and a validator update.
Expected Impact:
At this time, the impact appears to be limited primarily to smaller
third-party operators running a single liteserver. The blockchain
continues to operate within an acceptable range, transaction processing performance has not deteriorated, and major services and wallets continue to function normally.
We currently expect the validator update to take place on April 28. Some validators may be asked to update earlier.
Upd: https://telegra.ph/Synchronization-Instability-Report-04-23
Over the past several days, multiple operators have reported liteserver synchronization issues.
Our analysis has identified several potential causes affecting block and external message propagation in public overlays. We have already deployed a number of mitigations to reduce the impact. However, a full resolution will require additional analysis and a validator update.
Expected Impact:
At this time, the impact appears to be limited primarily to smaller
third-party operators running a single liteserver. The blockchain
continues to operate within an acceptable range, transaction processing performance has not deteriorated, and major services and wallets continue to function normally.
We currently expect the validator update to take place on April 28. Some validators may be asked to update earlier.
Upd: https://telegra.ph/Synchronization-Instability-Report-04-23
Mainnet Validator Software Update [v2026.04-1]
Please update your node software:
Update with mytonctrl:
Target versions:
— mytonctrl:
— node
If you are not using mytonctrl or using ubuntu older than 22.04, check this instruction (https://telegra.ph/TON-Node-Upgrade-202511-11-05).
If you have several validators, please update them one by one:
update a validator => wait for synchronization => move to the next one validator
Update is mandatory for validators and contains measures to improve stability and security of validators.
It is not required, but highly recommended for liteservers and archive liteservers especially those that experienced synchronization instability.
This release does not include breaking API changes and is fully compatible with recent versions of ton-http-api (acceptable versions: v2.0.64 and higher) and TON Indexer (acceptable versions: v1.2.6 and higher).
Node changelog.
Mytonctrl changelog.
Please update your node software:
Update with mytonctrl:
update master
upgrade masterTarget versions:
— mytonctrl:
62bbe8f— node
591b34dIf you are not using mytonctrl or using ubuntu older than 22.04, check this instruction (https://telegra.ph/TON-Node-Upgrade-202511-11-05).
If you have several validators, please update them one by one:
update a validator => wait for synchronization => move to the next one validator
Update is mandatory for validators and contains measures to improve stability and security of validators.
It is not required, but highly recommended for liteservers and archive liteservers especially those that experienced synchronization instability.
This release does not include breaking API changes and is fully compatible with recent versions of ton-http-api (acceptable versions: v2.0.64 and higher) and TON Indexer (acceptable versions: v1.2.6 and higher).
Node changelog.
Mytonctrl changelog.
Mainnet Validators
We ask you to support the proposal by Pavel Durov to reduce transaction fees by 6 times as part of the broader MTONGA plan.
Technical details are available here.
If accepted, the proposal would reduce total validator rewards by less than 0.4%, because transaction fees are only a small part of the validator reward.
Please be prepared to cast your vote after 13:00 UTC on April 30, tomorrow.
We ask you to support the proposal by Pavel Durov to reduce transaction fees by 6 times as part of the broader MTONGA plan.
Technical details are available here.
If accepted, the proposal would reduce total validator rewards by less than 0.4%, because transaction fees are only a small part of the validator reward.
Please be prepared to cast your vote after 13:00 UTC on April 30, tomorrow.
Mainnet validators
Please take part in the voting for network config adjustment.
Details of updates are given above.
1. Check that your validator software is on the latest version: commit
If you use mytonctrl, please vote for proposal via
Please take part in the voting for network config adjustment.
Details of updates are given above.
1. Check that your validator software is on the latest version: commit
591b34d.If you use mytonctrl, please vote for proposal via
vo 84123553170509389098874880050862184605633619991871324449516531408050268055269 42941749423356085253181262402693749199117510848841139894863341148398531565866 65009153936108305610337904793535370282692919307756841131143481982045644609157
Mainnet Validators
Due to the heightened attractiveness of staking, significant new capital has entered the validation, resulting in a corresponding increase in the minimum and maximum effective stakes required for validation.
We advise validators to verify whether their current machine allocations are sufficient to participate in validation and to aggregate their stakes into larger positions where feasible.
In the current round, the minimum and maximum stakes are 824,000 and 2,425,000 TON, respectively. We anticipate an increase to 1,000,000 and 3,000,000 TON in the near future. Please ensure you are prepared for this adjustment.
If you do not possess sufficient stake to participate in both rounds, consider utilizing staking services, which typically offer specialized conditions for large-scale stakeholders. Alternatively, you may configure 1-of-2 rounds validation. Please contact Core support for consultation regarding the implementation of this strategy to preserve maximal capital efficiency.
Due to the heightened attractiveness of staking, significant new capital has entered the validation, resulting in a corresponding increase in the minimum and maximum effective stakes required for validation.
We advise validators to verify whether their current machine allocations are sufficient to participate in validation and to aggregate their stakes into larger positions where feasible.
In the current round, the minimum and maximum stakes are 824,000 and 2,425,000 TON, respectively. We anticipate an increase to 1,000,000 and 3,000,000 TON in the near future. Please ensure you are prepared for this adjustment.
If you do not possess sufficient stake to participate in both rounds, consider utilizing staking services, which typically offer specialized conditions for large-scale stakeholders. Alternatively, you may configure 1-of-2 rounds validation. Please contact Core support for consultation regarding the implementation of this strategy to preserve maximal capital efficiency.
Clarification for TON Node Operators
The Rust implementation of the TON node has experimental status and is not intended for use on the main network, either as a validator or as a full node/liteserver.
At this time, alternative TON node implementations do not yet provide the required quality of operation or sufficient compatibility with current protocols. For validators, this means a risk of penalties for improper operation once the slashing system is re-enabled.
The TON network currently runs on the reference C++ implementation. Bringing alternative implementations into operation is not on the agenda — the priority is the continued rapid development of protocols and technologies in support of the MTONGA plan.
For the main network, operators should use the C++ version of the TON node.
The Rust implementation of the TON node has experimental status and is not intended for use on the main network, either as a validator or as a full node/liteserver.
At this time, alternative TON node implementations do not yet provide the required quality of operation or sufficient compatibility with current protocols. For validators, this means a risk of penalties for improper operation once the slashing system is re-enabled.
The TON network currently runs on the reference C++ implementation. Bringing alternative implementations into operation is not on the agenda — the priority is the continued rapid development of protocols and technologies in support of the MTONGA plan.
For the main network, operators should use the C++ version of the TON node.