205180
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.
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.
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.
С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.
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 5c392e0.
If you use mytonctrl:
1. Update mytonctrl via command: update
2. Vote for proposal:
vo 22440293175314732041600029416833597878678297180899118901294602657772681323261
If you do not use mytonctrl, each round:Читать полностью…
1.Create signed vote in validator-engine-console:createproposalvote 22440293175314732041600029416833597878678297180899118901294602657772681323261 vote-msg-body.boc
2. Send obtainedvote-msg-body.bocto-1:5555555555555555555555555555555555555555555555555555555555555555in internal message from any wallet from masterchain with 2 TON attached. If you are usingwallet.fifscript, 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"
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.
Reminder
Mainnet Validators and Liteserver owners
Please be prepared for upgrade on Monday June 10 at 9:00 UTC.
Liteserver owners
1) Please update MyTonCtrl to the new major MyTonCtrl 2.0 version.
In MyTonCtrl please run:
update mytonctrl2
disable_mode validator
enable_mode liteserver
a4b8bf2.db505f4.upgrade master
db505f4.
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 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
Mainnet Validators and Liteserver owners
Please update your node software (see "Target versions")
Instructions for update - take into account liblz4-dev installation in section 1 and archive-ttl setting in section 5.
Target versions:
mytonctrl 9182448
validator 4cfe1d1
This update is mandatory for validators and lite servers.
ATTENTION FOR VALIDATORS — ACTION REQUIRED
We anticipate a significant increase in network activity starting in mid-April.
In order to keep the network running smoothly, please make sure your validator matches the configuration below.
If it does not match, please upgrade your hardware within the next week.
This is critical and necessary.
Minimal validators hardware:
* 16 x Cores CPU
* 128GB Memory
* 1TB NVME SSD OR Provisioned 64+k IOPS storage
* 1 Gbit/s network connectivity
We draw special attention of validators to IOPS disk requirements, it is crucially important for smooth network operation.
If you have several validators - upgrade one by one.
Mainnet Validators and Liteserver owners
Please update your node software (see "Target versions")
Instructions for update
Target versions:
mytonctrl 244cad8
validator 200508c
This update is mandatory for validators and lite servers and is required for voting scheduled for March 15.
Mainnet Validators and Liteserver owners
Please update your node software (see "Target versions")
Instructions for update. Note new section 5 for validators and section 6 for Liteserver owners.
Target versions:
mytonctrl b9d5937
validator 692211f
This update is mandatory for validators and lite servers.
Update includes:
- LS improvements: remote runmethods with full c7 and libs, caching, logging
- Precise control of open files
- Improvement of validator synchronization
Scheduled network update on February 21
We are asking validators and lite server owners to schedule a time on February 21 at 9:00 UTC for validator software update.
This update is mandatory and contains changes improvements to validator synchronization as well as reliability of lite servers.
Upd: network update was postponed to February 26
Mainnet Validators
Please vote for new gas limits behavior and parameters
More info »
1) Please check that your node software is updated to the latest version (validator should be on 8a9ff33 commit). If your node is outdated, upgrade immediately via upgrade command in MyTonCtrl.
2) Update mytonctrl (validator should be on da1811d commit), use commands:
update
set duplicateSendfile true
vo 103351160959426487254455866498906719583068006422970295467232122110660230563283
vo 20149481433343766729971377917926966688629021535513398999071024734089315101195
vo 26493909155671493333100442738656102962830077543704392831296933554790654390192
Mainnet full node and lite server owners
Please update your node software (see "Target versions")
Instructions for update
Target versions:
mytonctrl b9d5937
validator 8a9ff33
This update is mandatory for validators and lite servers.
Update includes:
- Improvement in how gas in transactions on special accounts is accounted in block limit.
- Solution for block is not applied issue
- Changes of how library cells are handled
Mainnet Validators and Liteserver owners
Please update your node software (see "Target versions"):
update master
upgrade
7e90e26 (same for all kind of nodes)140320b
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.
Mainnet validators
Proposal to increase gas limit for special transactions, in particular election, was accepted! Thank you.
Reminder Mainnet Validators
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 and Liteserver owners
Please update your node software (see "Target versions"):
update
upgrade
--state-ttl 604800, so if you need more history (usually only liteservers need it) explicitly set state-ttl in systemd validator.service file.40daf3c / lite-server 55c3c0d 5c392e0
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.
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 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.
Mainnet Validators
Please be prepared to vote for block compression and transaction costs update on April 18 at 9:00 UTC.
Plea to validators
Tech details on proposals can be found here. Proposed changes will make block rate faster and transaction execution cheaper.
All validators MUST be updated to the latest version before voting. Target versions:
mytonctrl 9182448
validator 4cfe1d1
Scheduled network update on April 16
We are asking validators to schedule a time on April 16 at 11:00 UTC for validator software update.
This update is mandatory and, among other things, contains DB and network usage optimization, LS improvement, transaction executor, tonlib and emulator updates.
Mainnet Validators
Please vote for activation of new opcodes for gas estimation.
More info about opcodes »
More info about voting »
1) Please check that your node software is updated to the latest version (validator should be on 200508c 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 244cad8 commit). If necessary, you can update your mytonctrl via:
update
vo 62943188213554950431567175890704900183650560017761039378090136381016705792762
vo 70812101792553497242391430491941881046928125710785036909221479087825374611301
Scheduled network update on March 13
We are asking validators to schedule a time on March 13 at 9:00 UTC for validator software update.
This update is mandatory and contains TVM improvements that facilitate fee calculations and handling Merkle-proofs on-chain.
Voting for activation of these improvements is scheduled for March 15, details on the voting can be found here.
Network update is moved to February 26 at 10:00 UTC.
Читать полностью…
The TON-BNB Smart Chain bridge is back on track
All funds are safe and all transfers have been processed.
We thank users for their patience.
Mainnet Validators
Please be prepared to vote for new gas limits behavior and parameters on February 1 at 9:00 UTC.
Details can be found here. Proposed changes will make block generation, as well as TVM operations regarding libraries more predictable and thus more safe.
All validators MUST be updated to the latest version before voting. Target versions:
mytonctrl b9d5937
validator 8a9ff33
Scheduled network update on January 26
We are asking validators to schedule a time on January 26 at 9:00 UTC for validator software update.
This update is mandatory and contains changes to gas_limit behavior that is more gentle for contracts and services. Technical details of upcoming updated and information for smart-contract developers is here.