Mainnet Validators
Please vote for for block compression and transaction costs update.
Plea for validators »
More info about voting »
1) Please check that your node software is updated to the latest version (validator should be on
2) Please check that your mytonctrl is updated to the latest version (should be on
3) To vote via mytonctrl you need to use the command:
If 75%+ of the positive votes of the validators are collected in two rounds of next 6 rounds, then the proposal will be accepted.
Update: proposals were accepted on April 19.
Please vote for for block compression and transaction costs update.
Plea for validators »
More info about voting »
1) Please check that your node software is updated to the latest version (validator should be on
4cfe1d1 commit). If your node is outdated, upgrade immediately via upgrade command in MyTonCtrl.2) Please check that your mytonctrl is updated to the latest version (should be on
9182448 commit). If necessary, you can update your mytonctrl via update command.3) To vote via mytonctrl you need to use the command:
vo 12569949138907918341069315485240244200950856934919263564437769934039235613720
vo 31401000267374798460859142836851320859735453480263346121138978843222681889801
vo 41296061520515347990487695386109651690420586907458454458768144735616166931033
vo 49537534789854976259071705210466523357997345897986090889040825189829923897628
vo 96491208725598318198215712468033934914881492234615821929017670238581734249187
If 75%+ of the positive votes of the validators are collected in two rounds of next 6 rounds, then the proposal will be accepted.
Update: proposals were accepted on April 19.
Mainnet Validators and Liteserver owners
Tomorrow we expect drastic increase in network activity due to listing and minting of the Notcoin project, which is possibly the largest launch in the entire crypto industry in terms of userbase.
Please check you validators and liteserver software is up to date:
Target versions for node is
Also, please check that your nodes and validators have enough free space on disk. If you have less than 100 GB, check section 5 here, as well as database grooming docs.
We ask you to keep an eye on the validators tomorrow and be ready to take action.
Tomorrow we expect drastic increase in network activity due to listing and minting of the Notcoin project, which is possibly the largest launch in the entire crypto industry in terms of userbase.
Please check you validators and liteserver software is up to date:
Target versions for node is
4cfe1d1.Also, please check that your nodes and validators have enough free space on disk. If you have less than 100 GB, check section 5 here, as well as database grooming docs.
We ask you to keep an eye on the validators tomorrow and be ready to take action.
Liteserver owners
1) Please update MyTonCtrl to the new major MyTonCtrl 2.0 version.
In MyTonCtrl please run:
Target MyTonCtrl revision is
2) Then please upgrade node to
In MyTonCtrl:
If you are not using MyTonCtrl please use instruction.
Target node revision is
This node update contains major optimization of liteserver resource usage.
Please upgrade your liteservers till the end of next week (June 2).
This update is mandatory for liteservers (full nodes and archive nodes). Validators do not need to update now.
1) Please update MyTonCtrl to the new major MyTonCtrl 2.0 version.
In MyTonCtrl please run:
update mytonctrl2
disable_mode validator
enable_mode liteserver
Target MyTonCtrl revision is
a4b8bf2.2) Then please upgrade node to
db505f4.In MyTonCtrl:
upgrade master
If you are not using MyTonCtrl please use instruction.
Target node revision is
db505f4.This node update contains major optimization of liteserver resource usage.
Please upgrade your liteservers till the end of next week (June 2).
This update is mandatory for liteservers (full nodes and archive nodes). Validators do not need to update now.
Scheduled network update on June 10
We are asking validators to schedule a time on June 10 at 9:00 UTC for validator software update.
This update is mandatory and, among other things, contains DB optimization, public overlay spam prevention mechanisms and optimization of block delivery.
We are asking validators to schedule a time on June 10 at 9:00 UTC for validator software update.
This update is mandatory and, among other things, contains DB optimization, public overlay spam prevention mechanisms and optimization of block delivery.
Reminder
Mainnet Validators and Liteserver owners
Please be prepared for upgrade on Monday June 10 at 9:00 UTC.
Mainnet Validators and Liteserver owners
Please be prepared for upgrade on Monday June 10 at 9:00 UTC.
Telegram
TON Status
Scheduled network update on June 10
We are asking validators to schedule a time on June 10 at 9:00 UTC for validator software update.
This update is mandatory and, among other things, contains DB optimization, public overlay spam prevention mechanisms and…
We are asking validators to schedule a time on June 10 at 9:00 UTC for validator software update.
This update is mandatory and, among other things, contains DB optimization, public overlay spam prevention mechanisms and…
Mainnet Validators and Liteserver owners
Please update your node software (see "Target versions"):
Note, that on this upgrade mytonctrl removes default flag
Target versions:
— mytonctrl: validator
— node:
If you are not using mytonctrl, check this instruction.
This update is mandatory for validators and lite servers.
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
upgrade
Note, that on this upgrade mytonctrl removes default flag
--state-ttl 604800, so if you need more history (usually only liteservers need it) explicitly set state-ttl in systemd validator.service file.Target versions:
— mytonctrl: validator
40daf3c / lite-server 55c3c0d — node:
5c392e0If you are not using mytonctrl, check this instruction.
This update is mandatory for validators and lite servers.
If you have several validator nodes, please update them one by one (update, wait for synchronization, move to the next one).
Mainnet Validators Urgent Action Required
Please be prepared to vote for new gas limits for special transactions July 2 at 8:00 UTC.
In recent weeks, the number of validators has grown to a level that threatens the normal conduct of elections. Limits must be updated to continue smooth operation. If you are planning to launch a validator soon, please postpone it until the end of next week.
Please be prepared to vote for new gas limits for special transactions July 2 at 8:00 UTC.
In recent weeks, the number of validators has grown to a level that threatens the normal conduct of elections. Limits must be updated to continue smooth operation. If you are planning to launch a validator soon, please postpone it until the end of next week.
Reminder Mainnet Validators
Please be prepared for vote tomorrow on Tuesday July 2 at 8:00 UTC.
Proposal will contain increase
More details here.
Please be prepared for vote tomorrow on Tuesday July 2 at 8:00 UTC.
Proposal will contain increase
special_gas_limit from 35'000'000 to 70'000'000 in Config Parameter 20. In particular, this will allow Elector to conduct elections when more than 400 applications are submitted. Please note that according to the current configuration, the maximum number of validators is still limited to 400.More details here.
Mainnet validators
Proposal to increase gas limit for special transactions, in particular election, was accepted! Thank you.
Proposal to increase gas limit for special transactions, in particular election, was accepted! Thank you.
Сritical vulnerability in OpenSSH
Recently a critical vulnerability in OpenSSH was discovered: https://ubuntu.com/security/CVE-2024-6387
Since most of validators work on Ubuntu/Debian releases and use OpenSSH, we recommend check and update software on validator nodes if necessary.
Recently a critical vulnerability in OpenSSH was discovered: https://ubuntu.com/security/CVE-2024-6387
Since most of validators work on Ubuntu/Debian releases and use OpenSSH, we recommend check and update software on validator nodes if necessary.
Validation slots
406 candidates participated in the last validator elections.
According to the network rules each round candidates are sorted by effective stake size and the first 400 validators are elected to become validators.
If you don't have enough stake to pass as sole validator, that is less than 355'000 TON at the moment, - please participate in network maintenance via staking https://ton.org/stake.
406 candidates participated in the last validator elections.
According to the network rules each round candidates are sorted by effective stake size and the first 400 validators are elected to become validators.
If you don't have enough stake to pass as sole validator, that is less than 355'000 TON at the moment, - please participate in network maintenance via staking https://ton.org/stake.
Scheduled network update on August 12
We are asking validators to schedule a time on August 12 at 9:00 UTC for validator software update.
This update is mandatory and, among other things, contains introduction of dispatch queue and drastic improvement of state serialization process.
In the light of upcoming increase of network load we remind validators about importance of having strong machines, in particular having at least 128 GB of Memory.
We are asking validators to schedule a time on August 12 at 9:00 UTC for validator software update.
This update is mandatory and, among other things, contains introduction of dispatch queue and drastic improvement of state serialization process.
In the light of upcoming increase of network load we remind validators about importance of having strong machines, in particular having at least 128 GB of Memory.
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 lite servers. Changelog.
In case of any issues check updated documentation and contact us.
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
Target versions:
— mytonctrl:
7e90e26 (same for all kind of nodes)— node:
140320bIf you are not using mytonctrl, check this instruction.
This update is mandatory for validators and lite servers. Changelog.
In case of any issues check updated documentation and contact us.
If you have several validator nodes, please update them one by one (update, wait for synchronization, move to the next one).
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.
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
140320bMainnet validators
Please check efficiency of your validators. In case of low efficiency or frequent crashes (including OOM) immediately contact @mytonctrl_help_bot
In particular we ask the following validators to check their nodes
Please check efficiency of your validators. In case of low efficiency or frequent crashes (including OOM) immediately contact @mytonctrl_help_bot
In particular we ask the following validators to check their nodes
2,AE083C661DAD64F734CCBF5A4BEDF398BC4CF5A6BF454E376BB4B4437CBB4C9C
9,D4AB33E3C1F558143BF63ECF82B26B6A1AD635149AFCDA508DFCF53DDEF49EA1
10,20ED0665410992AEC5F476CAC9D452D89B1C34C210C48C1D578D1B46A82A4088
65,481532E012CB8F7E1C1B179F52E31D9B4F20EFE1BB032196E2690975E5989729
88,F82905F3161A1F7108B4A3807FC5C970B2B5B45E58219C033F1614582DDEAAC5
90,95343C09F5D4F1830C8AE4C8577C66EE779FA723D0C8D10ACAFFAC9F346B1ECA
96,F1A0A4153857E5385884E4EFCE50FABBC00662F54139A58CAD6DCE97529F35F5
Mainnet validator
If your validator has index < 100 please be prepared to urgent action at 04:00 UTC (Wed Aug 28 2024 04:00:00 GMT+0000). Please set alarm.
P.S. Due to high recent activity (>20m transactions in recent 2 days), garbage collection overloaded many of validators for enough time for them to lost consensus with each other. To restore consensus back, validators need to be restarted at about the same time with specific flags.
If your validator has index < 100 please be prepared to urgent action at 04:00 UTC (Wed Aug 28 2024 04:00:00 GMT+0000). Please set alarm.
P.S. Due to high recent activity (>20m transactions in recent 2 days), garbage collection overloaded many of validators for enough time for them to lost consensus with each other. To restore consensus back, validators need to be restarted at about the same time with specific flags.