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
sha256 hash of
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.
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.
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!
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!
Mainnet full node and lite server owners
Please update your node software.
Instructions for update.
This update is mandatory for validators.
Target versions:
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).
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).
Reminder
Mainnet Validators
Please be prepared to vote to enable TVM Update tomorrow on December 19 at 9:00 UTC.
More info »
Mainnet Validators
Please be prepared to vote to enable TVM Update tomorrow on December 19 at 9:00 UTC.
More info »
Telegram
The Open Network
Meet the long awaited TVM update in mainnet
It has undergone months of testing on testnet, bug bounties and been audited by one of the world's best auditor - Trail of Bits.
This update makes TVM one of the most versatile virtual machines around, including…
It has undergone months of testing on testnet, bug bounties and been audited by one of the world's best auditor - Trail of Bits.
This update makes TVM one of the most versatile virtual machines around, including…
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
2) 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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Mainnet full node and lite server owners
Please update your node software (see "Target versions")
Instructions for update
Target versions:
mytonctrl
validator
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.
Please update your node software (see "Target versions")
Instructions for update
Target versions:
mytonctrl
b9d5937validator
9728bc6This 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.
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.
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
validator
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
- Changes of how library cells are handled
Please update your node software (see "Target versions")
Instructions for update
Target versions:
mytonctrl
b9d5937validator
8a9ff33This 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
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
validator
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
b9d5937validator
8a9ff33Mainnet 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
2) Update mytonctrl (validator should be on
2) 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.
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.
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.
All funds are safe and all transfers have been processed.
We thank users for their patience.
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
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
TON Status
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…
Network update is moved to February 26 at 10:00 UTC.
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
validator
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
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
b9d5937validator
692211fThis 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 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.
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.