Мир сегодня с "Юрий Подоляка"

Труха⚡️Україна

Переглянути

Николаевский Ванёк

Переглянути

Труха⚡️Україна

Переглянути

Николаевский Ванёк

Переглянути

Лёха в Short’ах Long’ует

Переглянути

TON Status

Криптовалюти

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.

Рейтинг TGlist

ТипПублічний

Верифікація

Верифікований

Довіреність

Не надійний

Розташування

МоваІнша

Дата створення каналуЛист 25, 2021

Додано до TGlist

Серп 03, 2024

Я власник каналу

Історія змін

Статистика Телеграм-каналу TON Status

Детальніше

Підписників

259 468

24 год.

457-0.2%Тиждень

2 328-0.9%Місяць

5 603-2.1%

Індекс цитування

100

Згадок1Репостів на каналах0Згадок на каналах1

Середнє охоплення 1 допису

2 917

12 год.3 0960%24 год.2 9170%48 год.2 9170%

Залученість (ER)

0.34%

Репостів10Коментарів0Реакцій0

Залученість за охопленням (ERR)

1.12%

24 год.0%Тиждень

0.01%Місяць0%

Охоплення 1 рекл. допису

2 917

1 год.3 754128.69%1 – 4 год.00%4 - 24 год.00%

Детальніше

Під'єднайте нашого бота до каналу і дізнайтеся стать аудиторії цього каналу.

Всього дописів за 24 години

1

Динаміка

Останні публікації в групі "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 2a68c86.

If you use mytonctrl, vote for proposal via

vo 10417343672849294554112215443001378457781115591675002087908853591275394331828

If 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 via
lite-client -C global-config.json -rc "sendfile wallet-query.boc"
3. repeat for 93006213601402719671660224737621496948953854898607742321670820361849739662796

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 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)

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/

06.02.202509:00

Mainnet Validators and Liteserver Owners

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

update

Target versions:
— mytonctrl: ee82cb6
— node 2a68c86
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).

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

17.12.202411:01

Mainnet Validators and Liteserver Owners

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

update

Target versions:
— mytonctrl: 33bd174
— node ea0dc16
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).

28.10.202409:59

Mainnet Validators and Liteserver Owners

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

update

Target versions:
— mytonctrl: e0ead70
— node eed3153

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

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.

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.

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

14.09.202409:21

The network is experiencing performance issues. Transactions may take longer than usual to complete. A fix is being worked on.

13.09.202418:42

Block production in the shard has recovered. The situation is currently under review.

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.

11.09.202409:03

Mainnet Validators

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

update

Target versions:
— mytonctrl: ~~74e536b~~ a467af5 (updated)
— node: 1bef6df

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

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.

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

Всі дописи