TON Status

Mainnet validators and node owners
Scheduled network update on November 5

We are asking validators to schedule a time on Wednesday, November 5 at 8:00 UTC for validator software update.

This update is mandatory and contains improved node synchronization stability as well as slight changes in TVM version 12 (including new opcodes). Besides upgrade is required for upcoming network voting planned for November 12.
Please be prepared.

Liteserver node owners and service providers

Upcoming upgrade of network software requires your action to ensure uninterrupted operation of your infrastructure.

Please update your ton node / lite-servers according to announcement

Following components also require update if you use them in your environment:
self-hosted ton-indexer
— v1.0.x branch to v1.0.3
— v1.1.x branch to v1.1.9
— v1.2.x branch to v1.2.3
These updates do not introduce any changes that break backwards compatibility.

self-hosted ton-http-api
to v2.0.61
This update does not introduce any changes that break backwards compatibility.

Failure to apply these updates may result in service disruptions. Please act promptly.

Mainnet Validators and node owners

Please update your node software (see "Target versions"):

update master
upgrade master

Target versions:
— mytonctrl: 87823a0
— node 4ebd741
If you are not using mytonctrl, check this instruction.

This update is mandatory for validators, lite-servers and nodes. Node changelog. Mytonctrl changelog.

If you have several validator nodes, please update them one by one (update, wait for synchronization, move to the next one).

This update is also mandatory for Liteservers and full node operators.


Please schedule time on next week to upgrade.

Mainnet validators
Scheduled network update on October 13

We are asking validators to schedule a time on Monday, October 13 at 8:00 UTC for validator software update.

This update is mandatory and contains next TVM version, in particular developer friendly bounces and cheap builder-to-slice operations, optimizations of node performance, including optimistic validation, work with db, block candidate distribution and compression. Please be prepared.

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 cac968f.

If you use mytonctrl, first please ensure that you are up to date, in particular on commit 3816eb2 and vote for proposal via

vo 82972944767423313821326283030352055259326179170465528006873474837778003422390 76533703899083343601323766308882775352019089807862422256342837336826006755613

If you do not use mytonctrl, each round:

1.Create signed vote in validator-engine-console: createproposalvote 76533703899083343601323766308882775352019089807862422256342837336826006755613 vote-msg-body.boc
2. Send obtained vote-msg-body.boc to -1:5555555555555555555555555555555555555555555555555555555555555555 in internal message from any wallet from masterchain with 2 TON attached. If you are using wallet.fif script, 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"

Repeat for
82972944767423313821326283030352055259326179170465528006873474837778003422390

Mainnet validators
Scheduled voting on September 16

We are asking validators to schedule a time on Tuesday, September 16 at 12:00 UTC for network parameters voting.

Proposed voting is related to BTC Teleport operation and will allow to pass to next stage of Teleport rollout. Parameter -90, planned to be updated, won't directly affect network behavior and related to internal Teleport migration.

Upd: we also added to the list of planned parameters to update config 29, in particular bumping proto_version from 4 to 5. This will enable special overlays that will speed up synchronization of collator nodes.

Update on Validator Quality of Service API

Please note that when there is 1 shardchain in the blockchain, the QoS API collects enough data to calculate the efficiency of validators with an index >= 100 within 6-8 hours after the start of the validation cycle. Until then, efficiency estimates may be inaccurate due to insufficient data.

With more shardchains, this time is reduced; for example, with 4 shardchains, the efficiency rating is ready after 1 hour.

For validators with an index < 100, the efficiency rating is ready after 30 minutes, regardless of the number of shardchains.

Mainnet Validators

Please update your node software (see "Target versions") and vote for proposal.

update master
upgrade master
vo 103573789540304366034812131625763525885200705204393285729566949988603434542737

Target versions:
— mytonctrl: bf46931/74bdb33 (both are fine)
— node cac968f
If you are not using mytonctrl, check this instruction.

This update is mandatory for validators.
Node update introduce Accelerator update. Mytonctrl changelog. Proposal is to update -90 config that sets up BTC Teleport Governance.

If you have several validator nodes, please update them one by one (update, wait for synchronization, move to the next one).

Mainnet validators
Scheduled network update on July 28

We are asking validators to schedule a time on Monday, July 28 at 11:00 UTC for validator software update and network parameters voting.

This update is mandatory and contains internal node optimization related to Accelerator update [1][2][3], as well as functionality required for BTC Teleport. Proposed voting is also related to BTC Teleport operation: it won't directly affect network behavior but allow validators to participate in BTC Teleport governance.

Mainnet validators

All proposals were accepted! Thank you!

The benefits of these proposals, including larger block sizes, faster operations, optimized interaction with accounts' storage, and other enhancements, are already live and improving network performance and usability.

Mainnet validators

Please take part in the voting for network config adjustment.
Details of updates are given here.

1. Check that your validator software is on the latest version: commit 8f99af7.

If you use mytonctrl, vote for proposal via

vo 72950970141955009634493985157752471200893949891616436454729734426465997267196 34017568134187549009898704356228150517225485169222237192856032462351774897151 50468637853671300302577897933635869843820664891008449935708425835529897515286 47504358419253681406889633378045410026890000125944887347033305618500669184426 16182126426357247222833533845394616775372795037263659505290620106344006450574

If you do not use mytonctrl, each round:

1.Create signed vote in validator-engine-console: createproposalvote 72950970141955009634493985157752471200893949891616436454729734426465997267196 vote-msg-body.boc
2. Send obtained vote-msg-body.boc to -1:5555555555555555555555555555555555555555555555555555555555555555 in internal message from any wallet from masterchain with 2 TON attached. If you are using wallet.fif script, 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"

Repeat for
34017568134187549009898704356228150517225485169222237192856032462351774897151 50468637853671300302577897933635869843820664891008449935708425835529897515286 47504358419253681406889633378045410026890000125944887347033305618500669184426 16182126426357247222833533845394616775372795037263659505290620106344006450574

Liteserver node owners and service providers

Upcoming changes to the blockchain configuration require action on your part to ensure uninterrupted operation.

Please update your ton node / lite-servers according to announcement

Following componentes also require update if you use them in your environment:
- self-hosted ton-indexer to 1.1.8
- tonutils-go to 1.13.0
- gobicycle to v0.10.1

Failure to apply these updates may result in service disruptions. Please act promptly.

Mainnet Validators

Please be prepared to vote on Thursday July 3 at 10:00 UTC for a few changes that will drastically improve user experience, developer experience and blockchain efficiency.

Details can be found here.
All validators MUST be updated to the latest version before voting. Target versions:
— mytonctrl: 1b88179
— node 8f99af7

Upgrade rate in mainnet reached 90%

TON Core thanks validators for quick updates and diligent node maintenance!

Mainnet Validators and node owners

Please update your node software (see "Target versions"):

update master
upgrade master

Target versions:
— mytonctrl: 1b88179
— node 8f99af7
If you are not using mytonctrl, check this instruction.

This update is mandatory for validators, lite-servers and nodes. Node changelog. Mytonctrl changelog.

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 June 30

We are asking validators to schedule a time on Monday, June 30 at 10:00 UTC for validator software update.

This update is mandatory and contains next TVM version, optimizations of collation process and state serialization. The latter are needed to drastically improve user experience under low and moderate load of the network in the near future. Please be prepared.

Block production has been restored

A quick fix was released, and updating only a few master chain validators was sufficient to resume block production.

The incident was related to an error in the processing of the masterchain dispatch queue.

We will release a technical report on the incident shortly.

Update: https://telegra.ph/Report-on-June-1-2025-Operation-Incident-06-02

Block creation has been suspended on the TON mainnet

The TON Core team is aware of the issue and is working to resolve it.

Mainnet validators

Please take part in the voting for network config adjustment.
Details of updates are given here.

1. Check that your validator software is on the latest version: commit cee4c67.

If you use mytonctrl, vote for proposal via

vo 34798776028960531893650878155695543519007927204917026147352158691929180750546

If you do not use mytonctrl, each round:

1.Create signed vote in validator-engine-console: createproposalvote 34798776028960531893650878155695543519007927204917026147352158691929180750546 vote-msg-body.boc
2. Send obtained vote-msg-body.boc to -1:5555555555555555555555555555555555555555555555555555555555555555 in internal message from any wallet from masterchain with 2 TON attached. If you are using wallet.fif script, 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"