The Newton community which participated in the maintenance of | TON technical overview

The Newton community which participated in the maintenance of testnet2 has long decided to migrate from the resources owned by the original team, since, due to external circumstances, telegram cannot develop the TON network. Today an important step has been taken on this path: the Ton code https://github.com/newton-blockchain/ton maintained by newton (and used by the vast majority of validators on the network) diverged from the original TON code. Namely, there are changes at the catchain level: versioning was activated in the validatorSession configs and starting from block 9407194 we switched from version 0 to version 1. In practice, this means that in order to participate in testnet2 validation, you must use the code from the newton repository otherwise your validator will not be able to generate the correct validation group id and participate in block creation. For non-validating nodes and other software, there are no differences at the moment: we specifically make a phased transition so that everything can be updated with no hassle. However, we recommend to use the new config https://newton-blockchain.github.io/ton-global-lite-client.config.json. In particular, a new lightserver is set in the config (the Telegram one has been periodically offline lately), in addition, this config updatea accordingly to reflect relevant parameters / public lightservers / information about new workchains will appear.
Please note that to facilitate the transition to consensus with the new parameters, we lowered the max factor and stopped slashing. However, in the near future we will significantly weaken the requirements for the max factor for wider participation in the validation, and a little later we will enable slashing (penalties for incorrect work of validators). If by this moment you do not update to the latest version of the node, you risk losing part of the stake.