the details of the recent failure in the test network TON
The user control 40% of validation testnet2, updated them with the error, which has damaged the local database.
To remedy the situation required emergency update 2/3 of all validation. This situation was a good test TON in an emergency. This is unlikely to happen in the core network, because it is unlikely that someone will control 40% of the validators individually, so they are updated with errors at the same time.
At the time of the failure have not been established forks, and inadmissible blocks, which showed the stability of the algorithm Catchain.
On the official website of TON there ad with a call to update all validators node, lite-clients and variations TONLib.
#failures
Translated using Yandex.API
The user control 40% of validation testnet2, updated them with the error, which has damaged the local database.
To remedy the situation required emergency update 2/3 of all validation. This situation was a good test TON in an emergency. This is unlikely to happen in the core network, because it is unlikely that someone will control 40% of the validators individually, so they are updated with errors at the same time.
At the time of the failure have not been established forks, and inadmissible blocks, which showed the stability of the algorithm Catchain.
On the official website of TON there ad with a call to update all validators node, lite-clients and variations TONLib.
#failures
Translated using Yandex.API
Comments
Be the first to add a comment
Log in to comment