Mainnet Validators and Node Owners
Please update your node software (see "Target versions"):
Target versions:
— mytonctrl:
— node
This update is mandatory for validators and node owners and contains stability fixes.
Update is fully backward compatible and doesn't require update of ton-http-api (version v2.0.64+) and ton indexer (version v1.2.6+)
If you have several validator nodes, please update them one by one (update, wait for synchronization, move to the next one)
Please update your node software (see "Target versions"):
update master
upgrade master
Target versions:
— mytonctrl:
c171ae5— node
1690ba0This update is mandatory for validators and node owners and contains stability fixes.
Update is fully backward compatible and doesn't require update of ton-http-api (version v2.0.64+) and ton indexer (version v1.2.6+)
If you have several validator nodes, please update them one by one (update, wait for synchronization, move to the next one)
Mainnet validators and node owners
Scheduled network update on March 31
We are asking validators and nodes to schedule a time on Tuesday, March 31 at 8:00 UTC for validator software update.
This update is mandatory and introduce changes to consensus that is expected to be activated in early April.
Scheduled network update on March 31
We are asking validators and nodes to schedule a time on Tuesday, March 31 at 8:00 UTC for validator software update.
This update is mandatory and introduce changes to consensus that is expected to be activated in early April.
Mainnet Node Software Update [v2026.03]
Please update your node software (see "Target versions"):
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
- archive liteservers
and should be done before EOD April 1.
This release includes breaking changes to Catchain 2.0 Consensus that will be activated in early April and are therefore required for validator operation. It also contains many stability improvements.
This release does not include breaking API changes and is fully compatible with recent versions of ton-http-api (version: v2.0.64+) and TON Indexer (version: v1.2.6+).
Node changelog.
Mytonctrl changelog.
Please update your node software (see "Target versions"):
Update with mytonctrl:
update master
upgrade master
Target versions:
— mytonctrl:
c38f540— node
af252bcIf 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
- archive liteservers
and should be done before EOD April 1.
This release includes breaking changes to Catchain 2.0 Consensus that will be activated in early April and are therefore required for validator operation. It also contains many stability improvements.
This release does not include breaking API changes and is fully compatible with recent versions of ton-http-api (version: v2.0.64+) and TON Indexer (version: v1.2.6+).
Node changelog.
Mytonctrl changelog.
Sub-Second mainnet activation timeline for validators
March 31 (today): Upgrade validator nodes to the version supporting the latest consensus changes.
April 2: Vote to activate the new consensus on the basechain and enable a moderate block rate increase.
April 7: First, vote to fully activate fast consensus on both the basechain and masterchain, and then upgrade validator nodes.
March 31 (today): Upgrade validator nodes to the version supporting the latest consensus changes.
April 2: Vote to activate the new consensus on the basechain and enable a moderate block rate increase.
April 7: First, vote to fully activate fast consensus on both the basechain and masterchain, and then upgrade validator nodes.
Mainnet validators
Tomorrow, April 2, at 8:00 UTC, we ask validators to set aside time to vote on two proposals:
— Bump the TVM version to 13. This fixes some logical issues in transaction execution and serialization (which does not affect real-world contract behavior) and allows faster than 1 block per second.
— Vote to activate Catchain 2.0 in the basechain, with a block time of 800 ms and a first-slot timeout of 1600 ms.
Due to the transition to the new consensus, and to prevent unjust penalties after the new consensus is activated, voting on fines in MyTONControl is disabled until April 20. Thank you for your attention to this matter.
Tomorrow, April 2, at 8:00 UTC, we ask validators to set aside time to vote on two proposals:
— Bump the TVM version to 13. This fixes some logical issues in transaction execution and serialization (which does not affect real-world contract behavior) and allows faster than 1 block per second.
— Vote to activate Catchain 2.0 in the basechain, with a block time of 800 ms and a first-slot timeout of 1600 ms.
Due to the transition to the new consensus, and to prevent unjust penalties after the new consensus is activated, voting on fines in MyTONControl is disabled until April 20. Thank you for your attention to this matter.
Mainnet Validators
Please ensure that your node is up-to-date (see "Target versions") and vote for proposal described above.
Target versions:
— mytonctrl:
— node
If you are not using mytonctrl, each round:
Please ensure that your node is up-to-date (see "Target versions") and vote for proposal described above.
vo 4584813700287845504087026157451368340466400045879786828806270820611372984010 67278638360635871279241310364679419892513753094383521529029204229246773004198
Target versions:
— mytonctrl:
c38f540— node
af252bcIf you are not using mytonctrl, each round:
1.Create signed vote in validator-engine-console:createproposalvote 4584813700287845504087026157451368340466400045879786828806270820611372984010 vote-msg-body.boc
2. Send obtainedvote-msg-body.bocto-1:5555555555555555555555555555555555555555555555555555555555555555in internal message from any wallet from masterchain with 2 TON attached. If you are usingwallet.fifscript, it can be done via:
fift -s wallet.fif <path-to-key> -1:5555555555555555555555555555555555555555555555555555555555555555 <seqno> 2 -B vote-msg-body.boc
and send resulting message to network.
If you are using lite-client, it can be done via
lite-client -C global-config.json -rc "sendfile wallet-query.boc"
3. Repeat for67278638360635871279241310364679419892513753094383521529029204229246773004198
Mainnet validators
The proposals for the first stage of the migration to the TON Sub-Second regime have been accepted. Thank you for your support!
The mainnet basechain is already running on Catchain 2.0 with an 800 ms target block time. Services using streaming APIs, such as MyTONWallet, have already seen up to a 3x improvement in transaction UX speed. Services relying on older, more established APIs should continue to operate as usual.
The second and final stage of the migration, which will fully enable Catchain 2.0 on the masterchain and reduce block time to 400 ms, will begin on April 7. We would appreciate your support for this step as well.
⚠️ Please note that full activation of Catchain 2.0 consensus requires an additional open UDP port for ingress traffic on nodes actively participating in validation (full nodes and lite servers are not affected). Documentation on this will be published later today in this channel.
The proposals for the first stage of the migration to the TON Sub-Second regime have been accepted. Thank you for your support!
The mainnet basechain is already running on Catchain 2.0 with an 800 ms target block time. Services using streaming APIs, such as MyTONWallet, have already seen up to a 3x improvement in transaction UX speed. Services relying on older, more established APIs should continue to operate as usual.
The second and final stage of the migration, which will fully enable Catchain 2.0 on the masterchain and reduce block time to 400 ms, will begin on April 7. We would appreciate your support for this step as well.
⚠️ Please note that full activation of Catchain 2.0 consensus requires an additional open UDP port for ingress traffic on nodes actively participating in validation (full nodes and lite servers are not affected). Documentation on this will be published later today in this channel.
New port configuration instruction for validators
https://telegra.ph/TON-Catchain-20-consensus-QUIC-Communication-Port-04-03
https://telegra.ph/TON-Catchain-20-consensus-QUIC-Communication-Port-04-03
Mainnet Validators
Voting and the upgrade have been postponed from April 7 to April 8 at 14:00 UTC.
Additional time has been allocated for infrastructure preparations by certain validators and services, as well as for additional preparation of the TON Core development team.
Voting and the upgrade have been postponed from April 7 to April 8 at 14:00 UTC.
Additional time has been allocated for infrastructure preparations by certain validators and services, as well as for additional preparation of the TON Core development team.
Mainnet validators
Tomorrow, April 8, at 14:00 UTC, we ask validators to set aside time to upgrade and vote on the following proposal:
— Vote to change Config Parameter 30, to activate Catchain 2.0 in both masterchain and basechain with block production rate of 400ms.
In addition to improving network performance from a UX speed perspective, this change is also expected, based on the current network configuration, to increase total validator rewards. However, the final validation APY cannot be determined in advance, as it depends on the dynamic relationship between the total staked amount and the reward pool.
Tomorrow, April 8, at 14:00 UTC, we ask validators to set aside time to upgrade and vote on the following proposal:
— Vote to change Config Parameter 30, to activate Catchain 2.0 in both masterchain and basechain with block production rate of 400ms.
In addition to improving network performance from a UX speed perspective, this change is also expected, based on the current network configuration, to increase total validator rewards. However, the final validation APY cannot be determined in advance, as it depends on the dynamic relationship between the total staked amount and the reward pool.
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.