Крыптавалюты
TON Status
Крыптавалюты
10.02.202509:49
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
If you use mytonctrl, vote for proposal via
If you do not use mytonctrl, each round:
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 10417343672849294554112215443001378457781115591675002087908853591275394331828If you do not use mytonctrl, each round:
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-1:5555555555555555555555555555555555555555555555555555555555555555 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
17.12.202411:01
Mainnet Validators and Liteserver Owners
Please update your node software (see "Target versions"):
Target versions:
— mytonctrl:
— node
If you are not using mytonctrl, check this instruction.
This update is mandatory for validators and liteservers. 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).
Please update your node software (see "Target versions"):
updateTarget versions:
— mytonctrl:
33bd174— node
ea0dc16If you are not using mytonctrl, check this instruction.
This update is mandatory for validators and liteservers. 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).
14.09.202410:55
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 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
11.09.202409:03
Mainnet Validators
Please update your node software (see "Target versions"):
Target versions:
— mytonctrl:74e536b
— node:
If you are not using mytonctrl, check this instruction.
This update is mandatory for validators. Node changelog. Mytonctrl changelog.
After upgrade please remove from
If you have several validator nodes, please update them one by one (update, wait for synchronization, move to the next one).
P.S. We encourage validators to subscribe to @tonstatus_notifications channel with notifications of penalties for poorly performing TON validators.
Please update your node software (see "Target versions"):
updateTarget versions:
— mytonctrl:
a467af5 (updated)— node:
1bef6dfIf you are not using mytonctrl, check this instruction.
This update is mandatory for validators. Node changelog. Mytonctrl changelog.
After upgrade please remove from
/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)If you have several validator nodes, please update them one by one (update, wait for synchronization, move to the next one).
P.S. We encourage validators to subscribe to @tonstatus_notifications channel with notifications of penalties for poorly performing TON validators.
02.09.202416:54
ANNOUNCEMENT: DECENTRALISED SYSTEM OF PENALTIES FOR POORLY PERFORMING VALIDATORS
The current system of penalising poorly performing validators will be fully operational next Monday, September 9.
How do validators determine that another validator has performed poorly?
The TON is supplied with the lite-client utility. In lite-client there is a
This command analyses how many blocks the validator should have processed, and how many it actually processed in a given period of time.
If the validator processed less than 90% of the expected number of blocks during a validation round, it is considered to be performing poorly and should be penalised.
Technical description of the process: https://github.com/ton-blockchain/TIPs/issues/13#issuecomment-786627474
When and by whom a complaint is filed?
After each validation round (~18 hours), the validator stakes of validators that participated in that round are on the Elector smart contract for another ~9 hours.
During this time, anyone can send a complaint against a validator who performed poorly in said round. This happens onchain on the Elector smart contract.
All validators do not need to send a complaint.
How a complaint is validated?
After each validation round, validators receive a list of complaints from the Elector smart contract and double-check them by calling
If a complaint is validated, they onchain vote in favour of that complaint.
These actions are built into mytonctrl and happen automatically.
If the complaint has 66% of the validators' votes (by their weight), a penalty is taken off from the validator's stake.
What is the size of the fine?
The amount of the fine is fixed and equals 101 TON, which is roughly equal to the validator's income per round.
Where does this fine go?
The fine is distributed among the validators minus network costs and a small reward (~8 TON) to the validator who sent the correct complaint.
When was this functionality made?
This functionality was made in mytonctrl back in February 2021 https://github.com/ton-blockchain/TIPs/issues/13.
The complaints and fines functionality in the Elector system smart contract was made initially at the time of network launch.
Why didn't the penalty functionality work well earlier?
The network fee for sending complaints was significant, which as the Toncoin exchange rate increased, made it uneconomical to send them.
This has now been fixed by optimising the complaint message.
In a week from 9 September 2024, an automatic complaint sender will start working on several nodes in the network.
Is the system decentralised?
Yes, anyone can send a complaint, the penalty is only applied by a quorum of validators on the network.
There is no way for anyone to single-handedly fine anyone.
How do I prepare for the start of the penalty system?
Since this functionality is already implemented in node, you don't need to do anything to make the system work.
Please make sure you're complying with the validator guidelines.
During the week, we will publish additional tools and best practices for monitoring and maintaining the effectiveness of your validator.
Will the penalty system get stricter in the future?
Yes, the audience and the number of transactions in TON is growing rapidly and it is vital that the quality of work is at its best.
The system will improve and fines will increase this year. All updates will be announced in advance.
It makes sense to set up hardware, monitoring and validator work properly. If you don't want to do this please consider using staking services https://ton.org/stake.
The current system of penalising poorly performing validators will be fully operational next Monday, September 9.
How do validators determine that another validator has performed poorly?
The TON is supplied with the lite-client utility. In lite-client there is a
checkloadall command.This command analyses how many blocks the validator should have processed, and how many it actually processed in a given period of time.
If the validator processed less than 90% of the expected number of blocks during a validation round, it is considered to be performing poorly and should be penalised.
Technical description of the process: https://github.com/ton-blockchain/TIPs/issues/13#issuecomment-786627474
When and by whom a complaint is filed?
After each validation round (~18 hours), the validator stakes of validators that participated in that round are on the Elector smart contract for another ~9 hours.
During this time, anyone can send a complaint against a validator who performed poorly in said round. This happens onchain on the Elector smart contract.
All validators do not need to send a complaint.
How a complaint is validated?
After each validation round, validators receive a list of complaints from the Elector smart contract and double-check them by calling
checkloadall.If a complaint is validated, they onchain vote in favour of that complaint.
These actions are built into mytonctrl and happen automatically.
If the complaint has 66% of the validators' votes (by their weight), a penalty is taken off from the validator's stake.
What is the size of the fine?
The amount of the fine is fixed and equals 101 TON, which is roughly equal to the validator's income per round.
Where does this fine go?
The fine is distributed among the validators minus network costs and a small reward (~8 TON) to the validator who sent the correct complaint.
When was this functionality made?
This functionality was made in mytonctrl back in February 2021 https://github.com/ton-blockchain/TIPs/issues/13.
The complaints and fines functionality in the Elector system smart contract was made initially at the time of network launch.
Why didn't the penalty functionality work well earlier?
The network fee for sending complaints was significant, which as the Toncoin exchange rate increased, made it uneconomical to send them.
This has now been fixed by optimising the complaint message.
In a week from 9 September 2024, an automatic complaint sender will start working on several nodes in the network.
Is the system decentralised?
Yes, anyone can send a complaint, the penalty is only applied by a quorum of validators on the network.
There is no way for anyone to single-handedly fine anyone.
How do I prepare for the start of the penalty system?
Since this functionality is already implemented in node, you don't need to do anything to make the system work.
Please make sure you're complying with the validator guidelines.
During the week, we will publish additional tools and best practices for monitoring and maintaining the effectiveness of your validator.
Will the penalty system get stricter in the future?
Yes, the audience and the number of transactions in TON is growing rapidly and it is vital that the quality of work is at its best.
The system will improve and fines will increase this year. All updates will be announced in advance.
It makes sense to set up hardware, monitoring and validator work properly. If you don't want to do this please consider using staking services https://ton.org/stake.
21.08.202408:01
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
If you use mytonctrl:
1. Update mytonctrl via command:
2. Vote for proposal:
If you do not use mytonctrl, each round:
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
140320b.If you use mytonctrl:
1. Update mytonctrl via command:
update2. Vote for proposal:
vo 20308659988793623196998942342425699672407754574159059846525327984142483923860 21241086152080161891970114314094131332811466103307811578007752491905358303034If you do not use mytonctrl, each round:
1.Create signed vote in validator-engine-console: createproposalvote 20308659988793623196998942342425699672407754574159059846525327984142483923860 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.fifand send resulting message to network. If you are using lite-client, it can be done via-1:5555555555555555555555555555555555555555555555555555555555555555 2 -B vote-msg-body.boc lite-client -C global-config.json -rc "sendfile wallet-query.boc"3. repeat for 21241086152080161891970114314094131332811466103307811578007752491905358303034
08.02.202513:22
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
* Mytonctrl
* TON indexer
Make sure that you update indexer submodules by issuing:
To check your submodule versions please issue
Taget submodule versions are:
API interfaces of indexer will retain backward compatibility.
This change is related to archive slices stored in shard-wise format.
Please note that the underlying database structure for ton indexer has undergone significant changes, migrations of your existing database will be performed by the updated index-worker on first start. However, your database will miss some historical information required for new API calls, if you want to load this historical data you can restore latest indexer database backup provided by us under the URL https://dump.ton.org/dumps/index/
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 c4510da5Make sure that you update indexer submodules by issuing:
git submodule update --init --recursive, To check your submodule versions please issue
git submodule status --recursiveTaget 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)
API interfaces of indexer will retain backward compatibility.
This change is related to archive slices stored in shard-wise format.
Please note that the underlying database structure for ton indexer has undergone significant changes, migrations of your existing database will be performed by the updated index-worker on first start. However, your database will miss some historical information required for new API calls, if you want to load this historical data you can restore latest indexer database backup provided by us under the URL https://dump.ton.org/dumps/index/
28.10.202409:59
Mainnet Validators and Liteserver Owners
Please update your node software (see "Target versions"):
Target versions:
— mytonctrl:
— node
If you are not using mytonctrl, check this instruction.
This update is mandatory for validators and liteservers. 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).
Please update your node software (see "Target versions"):
updateTarget versions:
— mytonctrl:
e0ead70— node
eed3153If you are not using mytonctrl, check this instruction.
This update is mandatory for validators and liteservers. 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).
14.09.202409:21
The network is experiencing performance issues. Transactions may take longer than usual to complete. A fix is being worked on.
06.09.202408:21
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.
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.
29.08.202415:19
Important Instructions for TON Validators
Dear TON Validators, please follow these crucial steps to ensure network stability this week and to avoid new slashing penalties in the future.
Essential Actions:
1) Verify you're on the
2) Ensure your hardware meets or exceeds system requirements: https://t.me/tonstatus/102. Upgrade if necessary, one at a time.
3) We imperatively request you to use mytonctrl.
In your mytonctrl console:
- Update to the latest version:
- Enable telemetry:
4) Set up monitoring dashboards for RAM, Disk, Network, and CPU usage. For technical assistance, contact @mytonctrl_help_bot.
DOGS Project Alert:
This week, the DOGS gaming project (50 million active users) is minting and listing, causing increased network load. We experienced two network outages on August 27 and 28. Please:
1) Stay available this week and respond within 1 hour, around the clock.
2) Closely monitor your hardware. Contact @mytonctrl_help_bot immediately if you need help.
3) Follow @tonstatus and be ready to apply urgent updates if necessary.
‼️ Updates on Slashing Mechanics for TON Validators:
The TON Core team is working on implementing of new slashing penalties for non-performing validators. Executing the actions above is crucial to mitigate the risk of losing rewards for validating the network.
Your cooperation is vital for maintaining network stability and TON's prosperity. Thank you for your prompt attention to these matters.
Dear TON Validators, please follow these crucial steps to ensure network stability this week and to avoid new slashing penalties in the future.
Essential Actions:
1) Verify you're on the
stable_testnet branch (commit 97c57c3). If not, update: https://t.me/tonstatus/130. For multiple validators, update one at a time.2) Ensure your hardware meets or exceeds system requirements: https://t.me/tonstatus/102. Upgrade if necessary, one at a time.
3) We imperatively request you to use mytonctrl.
In your mytonctrl console:
- Update to the latest version:
update master- Enable telemetry:
set sendTelemetry true4) Set up monitoring dashboards for RAM, Disk, Network, and CPU usage. For technical assistance, contact @mytonctrl_help_bot.
DOGS Project Alert:
This week, the DOGS gaming project (50 million active users) is minting and listing, causing increased network load. We experienced two network outages on August 27 and 28. Please:
1) Stay available this week and respond within 1 hour, around the clock.
2) Closely monitor your hardware. Contact @mytonctrl_help_bot immediately if you need help.
3) Follow @tonstatus and be ready to apply urgent updates if necessary.
‼️ Updates on Slashing Mechanics for TON Validators:
The TON Core team is working on implementing of new slashing penalties for non-performing validators. Executing the actions above is crucial to mitigate the risk of losing rewards for validating the network.
Your cooperation is vital for maintaining network stability and TON's prosperity. Thank you for your prompt attention to these matters.
16.08.202416:15
URGENT
If you find yourself on this list - urgently restore the work of your validators:
Index, ADNL Address
64
59
60
62
69
73
66
61
58
72
71
63
68
70
67
65
Please write to @mytonctrl_help_bot for technical support.
If you find yourself on this list - urgently restore the work of your validators:
Index, ADNL Address
64
E52FC8A83D87800431577CBF3420008755CE02A8661DE87FC072F8C984F4DCF559
4D7415AE99122C69059F6AB6D2EF9C8E38D0336A037EEC7E664F08C56FD24EAD60
9B1D928553E12A72B18F74488F9BD73E482D73D506F690F5F6031132E62C577462
3A5C0F4413F59CAED2A8F6D5E0D720A39AFCC64D26EB0F3E67C33B8AA5B27DBC69
6E566FE87154616104988FD224554195CCF1D468904323FB9E3DB5ECE6C5B6DD73
5CFF0D1ED440231E8D0D9E99F834BFF37DF94089ADF7B4DA0CD424605D5C65A466
11D9FE6B53C719505C3DFC925E5898656D0612E465A8B3CF0C4079FA17F046D161
7AEE080A1B0759ED8A0F700CE00F934C12BCB8946345F2E86B02535A1336DB1A58
98B61AEF5082D429B6F16AD150FF86C4A72981EF23D483162D11A315310D720972
4770F276A692FB823A7D0B6928F54750231C34C247B5AC1C6AC0AA710FB1F14471
D69CF9187546D44749814AA01206ECCB299E021E5547AC9E08A130284FE6081D63
CC3977E7EF0BF4527AEA23E850C8E1CE68E22442589AAC1BFFAE7304CA19B0F968
5C63846DADC85DB171205E96E35AF313337A97F79F84ADB14D92C8CD34B7736F70
8012FCD6C2042080CC704B178DC6FCF648D5A80CECCC2F48EF663D59B4C28E3367
B7E16FEDA9507640A5B3ACBE047AA537B06E0033B1FA6003D0D9AFE627F973CF65
65EEBDCB7DD0C89C7964990B83E541E3B198D8F67F58A0B1B1227C88460026A0Please write to @mytonctrl_help_bot for technical support.
06.02.202509:00
Mainnet Validators and Liteserver Owners
Please update your node software (see "Target versions"):
Target versions:
— mytonctrl:
— node
If you are not using mytonctrl, check this instruction.
This update is mandatory for validators and liteservers. 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).
Please update your node software (see "Target versions"):
updateTarget versions:
— mytonctrl:
ee82cb6— node
2a68c86If you are not using mytonctrl, check this instruction.
This update is mandatory for validators and liteservers. 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).
19.10.202410:10
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.
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.
13.09.202418:42
Block production in the shard has recovered. The situation is currently under review.
05.09.202412:16
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
Unlike
How to use:
- pass ADNL address of your validator and time inverval (
- get the result. If your
- 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.
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.
Пераслаў з:
TON Community
29.08.202414:59
Dear TON Validators,
We are releasing an important TON Validator Information Form today. This form is crucial for improving our network's performance and stability, especially in light of anticipated increased loads.
- The form collects essential data about your validator setup.
- Your input is vital for network optimization.
- Please complete the form today.
- Your prompt response will help us collaborate effectively on network improvements.
Access the form here
Your cooperation is critical for the TON network's continued success. Thank you for your immediate attention to this matter.
We are releasing an important TON Validator Information Form today. This form is crucial for improving our network's performance and stability, especially in light of anticipated increased loads.
- The form collects essential data about your validator setup.
- Your input is vital for network optimization.
- Please complete the form today.
- Your prompt response will help us collaborate effectively on network improvements.
Access the form here
Your cooperation is critical for the TON network's continued success. Thank you for your immediate attention to this matter.
15.08.202414:36
Mainnet Validators
Please be prepared to vote on Wednesday August 21 at 8:00 UTC for new transaction executor behavior, dispatch queue activation and increasing minimal split.
Details can be found here. Proposed changes will allow network to more evenly distribute load, improve stability of block generation and serialization process.
All validators MUST be updated to the latest version before voting. Target versions:
mytonctrl
validator
Please be prepared to vote on Wednesday August 21 at 8:00 UTC for new transaction executor behavior, dispatch queue activation and increasing minimal split.
Details can be found here. Proposed changes will allow network to more evenly distribute load, improve stability of block generation and serialization process.
All validators MUST be updated to the latest version before voting. Target versions:
mytonctrl
7e90e26validator
140320b30.01.202509:45
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.
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.
25.09.202417:11
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.
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.
13.09.202418:19
Block production in the shard 0x9000000000000000 has stopped. The other shards are working normally. The core team is investigating the problem.
04.09.202412:52
Tool for assessing the effectiveness of validators
The new version of mytonctrl has added a new command
Previous efficiency score from the
To update mytonctrl, type
Then type
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).
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).
28.08.202419:20
URGENT - Mainnet validators
Please make sure you have done the previous update. If you haven't please do.
Then update node flags:
1. open
2. remove
3. add flags
4. restart validator:
Please make sure you have done the previous update. If you haven't please do.
Then update node flags:
1. open
/etc/systemd/system/validator.service2. remove
-F 39987437:600844:7 -F 39987437:600845:7 if they are still present3. add flags
-F 39991868:601006:7 --catchain-max-block-delay 0.5 to the end of ExecStart4. restart validator:
14.08.202413:15
Validators require 128Gb RAM
In a previous update, we implemented a Fast State Serializer, which reduces blockchain state serialization time from 18 hours to ~50 minutes.
This frees up more resources for the validator to work on validating transactions and blocks, which is necessary for network performance in general.
Fast serialization works only if there is enough RAM.
According to requirements validator should have at least 128Gb RAM. If you have less - please upgrade your hardware.
This message is for validators only.
In a previous update, we implemented a Fast State Serializer, which reduces blockchain state serialization time from 18 hours to ~50 minutes.
This frees up more resources for the validator to work on validating transactions and blocks, which is necessary for network performance in general.
Fast serialization works only if there is enough RAM.
According to requirements validator should have at least 128Gb RAM. If you have less - please upgrade your hardware.
This message is for validators only.
Паказана 1 - 24 з 27
Увайдзіце, каб разблакаваць больш функцый.