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.
Final shutdown stage for Toncoin and Token Bridge
Toncoin and Token Bridge at bridge-v3.ton.org will be permanently shut down on September 1, 2026.
All percentage-based transfer fees have been waived for the remaining bridge withdrawal period.
Users who have previously used the bridge should check their wallets and withdraw any remaining bridged assets before the shutdown date.
Required action
If you have Wrapped Toncoin in your Ethereum or BNB Smart Chain wallet, please bridge it back to TON using bridge-v3.ton.org before September 1, 2026.
If you have jUSDT, jUSDC, jDAI, jWBTC, or any other j-tokens in your TON wallet, please bridge them back to Ethereum using bridge-v3.ton.org before September 1, 2026.
After this date, the bridge will no longer be available for any transfers.
Current status
All previously submitted user transfers have been processed.
For transfers that had been executed but not claimed by users, the required TON and EVM network fees were covered, and those transfers have also been completed.
On June 2026, bridge oracles will withdraw their stakes from the bridge contracts. The oracles will continue processing bridge transfers until the final shutdown on September 1, 2026.
Toncoin and Token Bridge at bridge-v3.ton.org will be permanently shut down on September 1, 2026.
All percentage-based transfer fees have been waived for the remaining bridge withdrawal period.
Users who have previously used the bridge should check their wallets and withdraw any remaining bridged assets before the shutdown date.
Required action
If you have Wrapped Toncoin in your Ethereum or BNB Smart Chain wallet, please bridge it back to TON using bridge-v3.ton.org before September 1, 2026.
If you have jUSDT, jUSDC, jDAI, jWBTC, or any other j-tokens in your TON wallet, please bridge them back to Ethereum using bridge-v3.ton.org before September 1, 2026.
After this date, the bridge will no longer be available for any transfers.
Current status
All previously submitted user transfers have been processed.
For transfers that had been executed but not claimed by users, the required TON and EVM network fees were covered, and those transfers have also been completed.
On June 2026, bridge oracles will withdraw their stakes from the bridge contracts. The oracles will continue processing bridge transfers until the final shutdown on September 1, 2026.
Mainnet validators and node owners
Scheduled network update on June 1
We ask all validators and node owners to schedule time on Monday, June 1, at 10:00 UTC to update their validator software.
This update is mandatory and introduces security and performance-related changes to consensus.
On June 3, we expect to propose corresponding network configuration changes for voting, including:
- Config8: set TVM version to 14 and activate the
- Config17: increase
- Config29: set
- Config30: set
- Config79, 80, 81: change of addresses to proceed with bridge closure.
These changes will increase overall network performance and won't affect validation rewards
Scheduled network update on June 1
We ask all validators and node owners to schedule time on Monday, June 1, at 10:00 UTC to update their validator software.
This update is mandatory and introduces security and performance-related changes to consensus.
On June 3, we expect to propose corresponding network configuration changes for voting, including:
- Config8: set TVM version to 14 and activate the
full_collated_date capability to improve validation performance.- Config17: increase
max_stake_factor from 3 to 4.5, allowing validators with smaller stakes to continue participating in network maintenance despite higher maximum stakes.- Config29: set
max_collated_bytes to 10 MB.- Config30: set
enable_observers from 0 to 1, introducing a separate overlay for fast candidate broadcasts among validators.- Config79, 80, 81: change of addresses to proceed with bridge closure.
These changes will increase overall network performance and won't affect validation rewards
Mainnet Validator Software Update [v2026.05]
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, liteservers and archive liteservers.
Deadlines: Validators should apply the update within 24 hours of this announcement. Lite Server operators should apply the update no later than Friday, 5th of June.
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:
9520ad2— node
8e6f091If 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, liteservers and archive liteservers.
Deadlines: Validators should apply the update within 24 hours of this announcement. Lite Server operators should apply the update no later than Friday, 5th of June.
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
A scheduled network configuration adjustment will take place tomorrow, June 3, at 17:00 UTC. We ask validators to cast their votes withing 24 hours after that.
Full details of the update are available here.
This update is required to:
- activate measures that further improve network performance and make validation more stable;
- make validation more permissive by allowing a wider range of minimum and maximum stakes;
- proceed with the TON Bridge closure.
A scheduled network configuration adjustment will take place tomorrow, June 3, at 17:00 UTC. We ask validators to cast their votes withing 24 hours after that.
Full details of the update are available here.
This update is required to:
- activate measures that further improve network performance and make validation more stable;
- make validation more permissive by allowing a wider range of minimum and maximum stakes;
- proceed with the TON Bridge closure.
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
2. If you use mytonctrl, please vote for proposals 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
8e6f091.2. If you use mytonctrl, please vote for proposals via
vo 9901998680707950950238275199047408807574030713004871006823337513201412566813 21526253372328041162945873458133265853602219828453225088086555939852366673948 25457740459214303188122764586580481160870045992693138140082832275221088727435 27888037080949394985586284390638387418032132650027223566011206271775308997958 47109645929274029714503680701532923988963495538545236837911985690370399364755 91653260358164255814917090285064033870499577570446925645989803264091693189638 97476904964537115993827662219965215594287692635916428067774379550074503377880 105421554118666087537177391865877968766437175802842020945158031714676721220730 63244263381357691341252589176593235583578881537703891344526025000835647174683