Mainnet validators:

Please start update of your node software from October 6 8:00 GMT to new version:

— in mytonctrl commandline run update then upgrade.

— if you don't use mytonctrl please manually rebuild code from master branch of https://github.com/ton-blockchain/ton.

Update your validators one by one, don't update all at the same time.

Please avoid update one hour prior and two hours after start of new validation cycle; on October 6 new validation round will start around 16:00 GMT, thus avoid update in 15:00-18:00 GMT span.

A recent update to FunC introduced a bug related to the optimization of some expressions involving the bitwise NOT ~.
Please update your FunC compiler from master.

Telegram Usernames and TON DNS

Given that Telegram usernames comply with TON DNS standard, we consider it a great idea to add the "t.me" domain zone to the TON DNS root smart contract.

Almost all TON wallets and apps allow you to enter a ".ton" domain instead of a wallet address.

After updating the root TON DNS, it will be possible to enter a Telegram username into TON apps in the same way as ".ton" domains. In other words, you will be able to send Toncoins to "any.t.me" address. The TON apps themselves will not require modifications.

Since the blockchain configuration can only be changed by validator voting, we’re scheduling a network vote for this proposal on Oct. 31 at 12:00 UTC. Validators, please be ready to send your vote at this time. Detailed instructions will be posted later.

We remind you that tomorrow at 12:00 UTC all validators will need to send their vote for the DNS proposal.

Please stay in touch.

Vote to change the root DNS smart contract

The new root DNS smart contract which supports both .ton and .t.me domains has the following address Ef_lZ1T4NCb2mwkme9h2rJfESCE0W34ma9lWp7-_uY3zXDvq.

You can check out its source code on GitHub.

— Added support for t.me domain zone - Telegram usernames.

— Added short alias www.ton for the foundation.ton site.

— .ton domain zone support without changes.

Network validators, please vote for this proposal.

To vote via mytonctrl, you need to use the command: vo 110945915504048090704740762384722970647335048403405846922858187005120712761626

If you don't use mytonctrl, use this instruction.

The voting was successfully completed, the root TON DNS smart contract was updated.

t.me support in your applications:

— if you are using tonlib no action is required.

— if you are using tonweb - make sure that tonweb version is 0.0.58 or higher.

— if you use another solution - make sure you get root DNS smart contract from network config number 4.

Testnet came back to life

Developers using testnet: please update the config and, if necessary, rebuild the tonlib from last commit of the testnet branch.

Update of the network is scheduled on January 9 2023. We are asking mainnet validators, full-node and liteserver owners to schedule time for the maintenance.

Validators: we remind you that tomorrow at 13:00 UTC an network update is scheduled - you will need to update your software at that time.

Please be in touch tomorrow at 13:00 UTC, detailed instructions will be published.

Mainnet validators and lite server owners:

Please update your node software to the new version:

— in mytonctrl run update then upgrade.

— if you don't use mytonctrl please manually rebuild code from master branch of https://github.com/ton-blockchain/ton.

Update your validators one by one, don't update all at the same time.

Scheduled network update on January 31

We are asking validators to schedule a time on January 31 at 12:00 UTC for validator software update.

The update will include the functionality needed for the last community proposal, as well as some bug fixes.

Please note that no addresses will be suspended with this update - voting for community proposal is scheduled for February 21.

Mainnet validators

Please update your node software to the new version (commit fc9542f):

— install fastcrc packet via pip install fastcrc command

— in mytonctrl run update then upgrade.

— if you don't use mytonctrl please manually rebuild code from master branch of https://github.com/ton-blockchain/ton.

Update your validators one by one, don't update all at the same time.

Mainnet validators

Please schedule a time tommorow on February 21 from 06:00 UTC to 15:00 UTC for community proposal for tokenomics optimization voting.

You will need to send your vote in that time frame.

Detailed instructions will be published tomorrow at 06:00 UTC.

Mainnet validators

Please take part in the voting for community proposal for tokenomics optimization.

1. Make sure you upgrade your validator software to fc9542f. This is a mandatory step to avoid network problems and keep your validators up and running.

Whatever your choice (vote for or against or not vote) you need to upgrade the software. The upgrade itself does not suspend any accounts.

Type status in mytonctrl and make sure that "Validator version" is "fc9542f (master)".

If not please upgrade your software as described in the previous post.

2. To vote for via mytonctrl, you need to use the command: vo 19333172216833189062833063765885523261394886618802241765562853343290715157530

If you don't use mytonctrl, use this instruction.

To vote against just do nothing.

Current validation round ends at 21 February, 17:06:27 UTC.

Next round ends at 22 February, 11:18:43 UTC.

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

Informing: gas limit increased

The number of TON validators is growing rapidly. Over the previous two months, the number of validators increased by ~30% and almost reached three hundred.

To better adjust network parameters for increased activity of TON users and validators we scheduled Network Config Adjustment in March.

But the growth of the network has exceeded our wildest expectations, and it was necessary to urgently update some parameters in order to continue the smooth operation. In particular, special_gas_limit and block_gas_limit of ConfigParam 20 were set to 25m and 27m, respectively. Full information can be found here.

These parameters, as well as some others, are planned to be overwritten by validator voting later this month.

This message is for informational purposes only and no action is required. All smart contracts, validators, etc. work without changes.

Scheduled network update on March 7

We are asking validators to schedule a time on March 7 at 10:00 UTC for validator software update.

This update contains:
— Improvement of ADNL connection stability
— Transaction emulator support and getAccountStateByTransaction method
— Fixes of typos, undefined behavior and timer warnings
— Handling incorrect literal values in funC

Mainnet validators and lite server owners:

Please update your node software to the new version (commit e37583e):

— in mytonctrl run update then upgrade.

— if you don't use mytonctrl please manually rebuild code from master branch of https://github.com/ton-blockchain/ton.

Update your validators one by one, don't update all at the same time.

Some validators with old cmake may encounter compilation errors. This issue can be resolved by update of cmake to version 3.13 or newer.

Mainnet validators

Please schedule a time on March 28 from 06:00 UTC to 18:00 UTC for network config adjustment voting.

You will need to send your vote in that time frame.

We are constantly working on the security and stability of the TON network. Based on our work, as well as the audits made, we propose to adjust some network parameters. Read more here.

Mainnet validators

Please schedule a time on March 30 from 09:00 UTC to 23:59 UTC for Ethereum-TON token bridge launch voting.

You will need to send your vote in that time frame.

Using this bridge, users can transfer any ERC-20 tokens (for example, USDC or USDT) originally created on Ethereum to the TON Blockchain, with the ability to return them back.

The transferred tokens will be represented on TON as regular Jettons so that TON services, such as DEXs, will be able to work with them without any additional modifications.

You can get acquainted with smart contracts here and here.

We have thoroughly tested smart contracts, which have also been verified by a public cracking contest and several audit teams.