232214
Technical notifications and up-to-date requests for action for TON validators, developers and integrators. If you're a validator or developer of a popular TON service you should be subscribed.
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
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
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"
Mainnet Validators
Please update your node software (see "Target versions"):
update
upgrade master
72d4357cee4c67
Recent and upcoming TON optimizations open the possibility of reducing network fees in the near future without reducing validator rewards.
Read more about our plans >>
Mainnet Validators
Please update your node software (see "Target versions"):
update
upgrade master
53594f10439613
Mainnet validators
Proposals to update vm version and increase monitor_min_split were accepted! Thank you
Self hosted ton indexer owners and operators
Please note that you must update your node and indexer latest by the end of day 12th of February.
Target versions:
* TON Node v2025.02, github commit 2a68c86
* Mytonctrl v2.4.0, github commit ee82cb6.
* TON indexer v1.1.5, github commit c4510da5
Make sure that you update indexer submodules by issuing: git submodule update --init --recursive,
To check your submodule versions please issue git submodule status --recursive
Taget submodule versions are:
57b0f804cbcf5173f175ac6643256fd768b686dc ton-index-cpp (heads/fix_sharded_block_data)
e1c31967f1b566c87cddb83a6e679cc0df9b719a ton-index-cpp/external/ton (remotes/origin/ton-index-19-dec)
7b0a9b88f0ba5ef6e258b4a4e63cc54629546467 ton-index-go (heads/main)
Mainnet Validators and Liteserver Owners
Please update your node software (see "Target versions"):
update
upgrade master
ee82cb62a68c86
Mainnet Validators and Liteserver Owners
Please update your node software (see "Target versions"):
update
upgrade master
33bd174ea0dc16
QoS maintenance
Due to emergency infrastructure maintenance work, services https://elections.toncenter.com, https://testnet-elections.toncenter.com and https://toncenter.com/api/qos will experience reduced availability in the period between 03:30am and 05:30am UTC on Tuesday, 5 of November 2024.
Mainnet validators and liteserver owners
Scheduled network update on October 28
We are asking validators to schedule a time on October 28 at 10:00 UTC for validator software update.
This update is mandatory and, beside other things, decreases network consumption, and substantially improves synchronization and garbage collection speed.
Found a bug in node that caused performance issues overnight and today. Some validators have been updated, which solved the main problem.
Block production has been restored in all shards. It will take some time to process the accumulated messages (~ 1 hour), during this time there may be a slight performance degradation.
Upd: https://telegra.ph/Report-on-September-13-2024-Operation-Incident-09-14
Block production in the shard has recovered. The situation is currently under review.
Читать полностью…
Mainnet Validators
Please update your node software (see "Target versions"):
update
upgrade master
a467af5 (updated)1bef6df/etc/systemd/system/validator.service all recently added flags (they are not required anymore):-F *:*:*,--catchain-max-block-delay 0.5--state-ttl * (note, if you intentionally set specific state-ttl, keep it as you need)
APIs for validation and effectiveness of validators
1) https://elections.toncenter.com/docs - use this API to get information about current and past validation rounds (cycles) - time of rounds, which validators participated in them, their stakes, etc.
Information on current and past elections (for the validation round) is also available.
2) https://toncenter.com/api/qos/index.html#/ - use this API to get information on the efficiency of validators over time.
This API analyses the information from the catchain and builds an estimate of the validator's efficiency. This API does not use the checkloadall utility, but is its alternative.
Unlike checkloadall which works only on validation rounds, in this API you can set any time interval to analyse the validator's efficiency.
How to use:
- pass ADNL address of your validator and time inverval (from_ts, to_ts) to API. For accurate result it makes sense to take a sufficient interval, for example from 18 hours ago the current moment.
- get the result. If your efficiency percentage field is less than 80%, your validator is not working properly.
- It is important that your validator participates in validation and has the same ADNL address throughout the specified time period.
For example, if a validator participates in validation every second round - then you need to specify only those intervals when he participated in validation. Otherwise, you will get an incorrect underestimate.
- this works not only for masterchain validators (with index < 100) but also for other validators (with index > 100).
Recommendations
1) Please check the efficiency of your validator and in case of low efficiency - take action to fix the problem. Contact technical support @mytonctrl_help_bot if necessary.
2) Please set up dashboards to monitor your validators using these APIs.
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 be prepared to vote on Monday May 5 at 9:00 UTC for new TVM behavior.
Details can be found here. Proposed changes will simplify contract development by disabling anycast functionality that clutter message processing, simplification fee flows for extracurrencies and shard-optimization.
All validators MUST be updated to the latest version before voting. Target versions:
— mytonctrl: 72d4357
— node cee4c67
Mainnet validators
Scheduled network update on April 30
We are asking validators to schedule a time on Wednesday, April 30 at 9:00 UTC for validator software update.
This update is mandatory and contains next TVM version, a list of optimizations, normalized message hashes and more. Please note, that for building this update you need Clang 16, please be prepared (instructions here). Also note, that Ubuntu 20.04 will be deprecated for running nodes soon.
Upgrade rate in mainnet reached 90%
TON Core thanks validators for quick updates and diligent node maintenance!
Mainnet validators
Scheduled network update on March 11
We are asking validators to schedule a time on Tuesday, March 11 at 9:00 UTC for validator software update.
This update is mandatory and improves validator self-assessment tools, broadcast speed control, as well as implement updated extra-currency behavior and other fixes and improvements.
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 2a68c86.
If you use mytonctrl, vote for proposal via
vo 10417343672849294554112215443001378457781115591675002087908853591275394331828
93006213601402719671660224737621496948953854898607742321670820361849739662796
1.Create signed vote in validator-engine-console:Читать полностью…createproposalvote 10417343672849294554112215443001378457781115591675002087908853591275394331828 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 vialite-client -C global-config.json -rc "sendfile wallet-query.boc"
3. repeat for93006213601402719671660224737621496948953854898607742321670820361849739662796
Upgrade rate in mainnet reached 95%, with 67% weight achieved during the first day of upgrade!
Dear validators, thank you for quick update and careful maintenance of your nodes!
Mainnet validators and liteserver owners
Scheduled network update on February 6
We are asking validators to schedule a time on February 6 at 9:00 UTC for validator software update.
This update is mandatory and improves node IP address discovery mechanism, which will allow a stable validator migration process.
Besides, it contains multiple changes to improve the developer experience, as well as unlocking of previously locked highload wallets.
We plan to hold voting for activation of these changes on February 10, please schedule a time on this day as well.
* Software upgrade on February 6, 2025.
* Voting on February 10, 2025.
Mainnet validators and liteserver owners
Scheduled network update on December 17
We are asking validators to schedule a time on December 17 at 11:00 UTC for validator software update.
This update is mandatory and, beside other things, improves work with db, adds convenient option for key backups, removes duplicative calculations by caching, introduces new opcode in tvm and more.
Mainnet Validators and Liteserver Owners
Please update your node software (see "Target versions"):
update
upgrade master
e0ead70 eed3153
Dear TON Validator
We would like to notify you that from the 26th of September 10:00 UTC we are expecting an increased load on the TON blockchain, as the Hamster Kombat game project with more than 100 million monthly active users will be minting coins on the blockchain, which is a unique and first event of this scale for the blockchain industry.
We kindly request from September 26 to September 29:
1) be in touch. Follow the @tonstatus channel. If emergency actions are required apply within the hour.
2) constantly monitor the status of your validator and hardware during these days
The quality of validators directly affects the quality of the blockchain. We appreciate your participation in The Open Network.
The network is experiencing performance issues. Transactions may take longer than usual to complete. A fix is being worked on.
Читать полностью…
Block production in the shard 0x9000000000000000 has stopped. The other shards are working normally. The core team is investigating the problem.
Читать полностью…
Mainnet validators
Scheduled network update on September 11
We are asking validators to schedule a time on September 11 at 9:00 UTC for validator software update.
This update is mandatory and introduces catchain, serialization, network and collator configuration updates that optimize work of validators.
During preparation of this update we focused on minimal and safest changes which can be reliably tested in short period of time from one hand and substantially improve stability of validation from the other.
Tool for assessing the effectiveness of validators
The new version of mytonctrl has added a new command check_ef which outputs your validator efficiency data for the last round and for current round. This command retrieves data by calling checkloadall utility.
Previous efficiency score from the status command outdated and has been removed.
To update mytonctrl, type update in the mytonctrl console.
Then type check_ef in the mytonctrl console.
Note that the previous round may not be displayed immediately after the update.
Note that the current round data becomes more accurate towards the end of the round.
Validators with an index less than 100 (sorted by effective stake) please ensure that your efficiency is greater than 90% (for the full round period).
Validators with an index greater than 100 will not receive penalties next week as they do not participate in masterchain validation, but please follow the validator guidelines, as you will be included in the penalty system in future updates.
If you need tech support please contract @mytonctrl_help_bot (validators only).