audience statistics TON Status

Since the beginning of the war, more than 2000 civilians have been killed by Russian missiles, according to official data. Help us protect Ukrainians from missiles - provide max military assisstance to Ukraine #Ukraine. #StandWithUkraine

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

If 75%+ of the positive votes of the validators are collected in two rounds of next 6 rounds, then the proposal will be accepted.

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

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.

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.

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

command. 3) To vote via mytonctrl you need to use the command:

vo 62943188213554950431567175890704900183650560017761039378090136381016705792762
vo 70812101792553497242391430491941881046928125710785036909221479087825374611301

If 75%+ of the positive votes of the validators are collected in two rounds of next 6 rounds, then the proposal will be accepted.

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.

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.

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

Network update is moved to February 26 at 10:00 UTC.

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.

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

2) To vote via mytonctrl you need to use the command:

vo 103351160959426487254455866498906719583068006422970295467232122110660230563283
vo 20149481433343766729971377917926966688629021535513398999071024734089315101195
vo 26493909155671493333100442738656102962830077543704392831296933554790654390192

If 75%+ of the positive votes of the validators are collected in two rounds of next 6 rounds, then the proposal will be accepted.

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

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

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.

Mainnet full node and lite server owners Please update your node software (see "Target versions") Instructions for update Target versions: mytonctrl

b9d5937

validator

9728bc6

This update is mandatory for validators and lite servers. Update includes: - Fixes in how gas in transactions on special accounts is accounted in block limit. - Improvements in LS behavior - Improvements in DHT work and storage, CellDb, config.json ammendment, peer misbehavior detection, validator session stats collection, emulator. Update also includes conditional increase of gas limit which may be activated by validator voting.

Recently a highload wallet of @wallet in mainnet was stuck because current gas limit (1M) is not enough to clean up old queries, thus locking funds inside. More technical details can be found in crypto/smartcont/highload-wallet-v2-code.fc. While locked funds represent only a small part of the total user assets on platform, loss of access to it can undermine the trust and user experience in TON. To restore access to funds we plan to propose to validators temporarily increase gas limit for account EQD_v9j1rlsuHHw2FIhcsCFFSD367ldfDdCKcsNmNpIRzUlu. Next update planned to January 18 will contains (disabled by default) corresponding changes among other things and, once network will be upgraded, we will propose validators to vote for increased gas limits. When developing node software, we strive for the best user experience. To this end, we collaborate with projects in the ecosystem, including exchanges and wallets. In particular, in situations where it is possible to correct problems without undermining monetary policy (without printing new money), we develop and invite validators to approve changes to the node like those mentioned above. In addition, contracts, guidelines, tools and documentation are being improved to prevent such situations from arising.

Scheduled network update on January 18 We are asking validators to schedule a time on January 18 at 9:00 UTC for validator software update. This update is mandatory and contains optimization of node stability as well as disabled by default changes to gas_limit behavior.

BSC Bridge Mantainance Toncoin transfers between the BSC and TON networks via bridge.ton.org have been suspended for unscheduled technical works. The work will take approximately one week. We apologize for any inconvenience. All funds are safe and all unprocessed transfers will be processed after the technical work is completed. Toncoin and token transfers between Ethereum and TON networks are operating as normal.

Guidelines for API clients Public liteservers (from the global config) and free plans in TON API and Toncenter exist to get you started with TON quickly. It can be used for learning to program in TON, or for applications and scripts that do not require 100% uptime. If you're a developer of a popular product you can use: — More advanced plans in Toncenter or TON API, which provide more requests per second and better stability. — Other APIs like dton, re:doubt, TON Access may also provide extended plans. — Run your own node. In this case please pay attention to the hardware requirements.

New hardware requirements Validators: * 16 x Cores CPU * 64GB Memory * 1TB NVME SSD OR Provisioned 64+k IOPS storage * 1 Gbit/s network connectivity Full Nodes: * 16 x Cores CPU * 64GB Memory * 1TB SSD OR Provisioned 32+k IOPS storage * 1 Gbit/s network connectivity Archival Nodes: * 16 x Cores CPU * 128GB ECC Memory * 3.8TB SSD OR Provisioned 32+k IOPS storage (3.8TB assumes usage of ZFS volume with compression enabled). * 1 Gbit/s network connectivity Note that disk performance is important.

Mainnet Validators Please vote for enabling new TVM features. More info » 1) Please check that your node software is updated to the latest version (it should be on

6897b56

commit). If your node is outdated, upgrade immediately via

upgrade

command in MyTonCtrl. 2) To vote via mytonctrl you need to use the command:

vo 85710661254977802982316316252924652442954445780328502685001287213020431864656

If 75%+ of the positive votes of the validators are collected in two rounds of next 6 rounds, then the proposal will be accepted.

Reminder Mainnet Validators Please be prepared to vote to enable TVM Update tomorrow on December 19 at 9:00 UTC. More info »

Mainnet full node and lite server owners Please update your node software. Instructions for update. This update is mandatory for validators. Target versions:

mytonctrl: 342bad2 (master)
validator: 6897b56 (master)

This update includes: — Optimized message queue handling, now queue cleaning speed doesn't depend on total queue size If you have several validator nodes, update them one by one (update, waite for synchronization, move to the next one).

TON coped with minting activity! What a week! Not without difficulty, but we did it. Just for yesterday, TON has processed more than 21 million transactions (which is ~10% of all transactions over the entire previous period). At the same time, we have maintained the cheap fixed cost of transactions, as before. In total, more than 90K TON were spent on network commissions over the past week. We have learned lessons, some of the fixes have already been made, and work on the remaining ones is planned. What is next? This stress test revealed points of further growth and improvement throughout the entire ecosystem: Liteservers network, Resilient indexing APIs, message delivery infrastructure. Recent days results reassured our confidence that we will solve huge challenge of truly mass-adoption and will bring the crypto to every pocket! The upcoming updates are as follows: • Next TON validator software upgrade is planned to December 14. • Voting for TVM upgrade is moved for December 19. • Tech report on events December 5 - December 12 is planned to the end of this week. • New requirements and benchmarks for validator and lite-server hardware are planned to be released on next week. Thanks to the community We would like to note the well-coordinated and efficient work of community, in particular @Wallet, Tonkeeper, TON API, dTON, re:doubt, Tonhub and Orbs. Services have already begun eliminating detected bottlenecks. Stay in touch!

Critical bug detected and fixed thanks to bug bounty It was found that no special check against "all bytes same" public keys in OpenSSL crypto. Thus, due to the recent zeroing of the configuration key, a vulnerability has opened up. Just now we have used this issue to yet another time update config contract storage - bytes of public key are replaced with

82b17caadb303d53c3286c06a6e1affc517d1bc1d3ef2e4489d18b873f5d7cd1

- sha256 hash of

Not a valid curve point

phrase. This means that the vulnerability is closed and no one can use the configuration key. We thank everyone who participated in the TON bug bounty! This is an example of a bug that gets a top reward.

Mainnet validators Please update your validator software to commit

9b6d699

of master branch. To do it run in mytonctrl:

upgrade master

If you have several validator nodes, update them one by one (updated, waited for synchronization, and moved on to the next one).

Mainnet validators, get ready to update your software today at 12:00 UTC. More updates are also possible during this day, please stay in touch.

Mainnet Validators Mandatory action required If your validator nodes have less than 15 vCPUs we ask you to not participate in next elections for some times. To do it, use

set stake 0

command in MyTONCtrl. If, instead of MyTONCtrl you use your own election scripts and has less than 15 vCPU, please stop them.