TON Status
Ir al canal en Telegram
Technical notifications and up-to-date requests for action for TON validators, developers and integrators. If you're a validator or developer of a popular TON service you should be subscribed.
Mostrar másEl país no está especificadoTecnologías y Aplicaciones649
📈 Análisis del canal de Telegram TON Status
El canal TON Status (@tonstatus) en el segmento lingüístico de Inglés es un actor destacado. Actualmente la comunidad reúne a 165 516 suscriptores, ocupando la posición 649 en la categoría Tecnologías y Aplicaciones.
📊 Métricas de audiencia y dinámica
Desde su creación el невідомо, el proyecto ha mostrado un crecimiento acelerado, reuniendo a 165 516 suscriptores.
Según los últimos datos del 26 julio, 2026, el canal mantiene una actividad estable. En los últimos 30 días la variación de miembros fue de -3 920, y en las últimas 24 horas de -130, conservando un alto alcance.
- Estado de verificación: Verificado (confirmado oficialmente por Telegram)
- Tasa de interacción (ER): El promedio de interacción de la audiencia es 6.43%. Durante las primeras 24 horas tras publicar, el contenido suele obtener 2.51% de reacciones respecto al total de suscriptores.
- Alcance de las publicaciones: Cada publicación recibe en promedio 10 648 visualizaciones. En el primer día suele acumular 4 149 visualizaciones.
- Reacciones e interacción: La audiencia responde de forma activa: el promedio de reacciones por publicación es 0.
📝 Descripción y política de contenido
El autor describe el recurso como un espacio para expresar opiniones subjetivas:
“Technical notifications and up-to-date requests for action for TON validators, developers and integrators.
If you're a validator or developer of a popular TON service you should be subscribed.”
Gracias a la alta frecuencia de actualizaciones (últimos datos recibidos el 27 julio, 2026), el canal mantiene la vigencia y un amplio alcance. La analítica demuestra que la audiencia interactúa activamente con el contenido, lo que lo convierte en un punto de referencia dentro de la categoría Tecnologías y Aplicaciones.
165 516
Suscriptores
-13024 horas
-1 1357 días
-3 92030 días
Carga de datos en curso...
Canales Similares
Nube de Etiquetas
Sin datos
¿Algún problema? Por favor, actualice la página o contacte a nuestro gerente de soporte.
Menciones Entrantes y Salientes
---
---
---
---
---
---
Atraer Suscriptores
julio '26
julio '26
+221
en 62 canales
junio '260
en 17 canales
Get PRO
mayo '26
+123
en 49 canales
Get PRO
abril '26
+207
en 90 canales
Get PRO
marzo '260
en 9 canales
Get PRO
febrero '260
en 7 canales
Get PRO
enero '260
en 0 canales
Get PRO
diciembre '250
en 2 canales
Get PRO
noviembre '250
en 44 canales
Get PRO
octubre '250
en 27 canales
Get PRO
septiembre '250
en 25 canales
Get PRO
agosto '250
en 8 canales
Get PRO
julio '250
en 58 canales
Get PRO
junio '25
+638
en 163 canales
Get PRO
mayo '250
en 4 canales
Get PRO
abril '250
en 5 canales
Get PRO
marzo '250
en 14 canales
Get PRO
febrero '250
en 12 canales
Get PRO
enero '250
en 6 canales
Get PRO
diciembre '24
+835
en 10 canales
Get PRO
noviembre '24
+1 520
en 4 canales
Get PRO
octubre '24
+5 358
en 13 canales
Get PRO
septiembre '24
+13 413
en 305 canales
Get PRO
agosto '24
+9 267
en 222 canales
Get PRO
julio '24
+18 069
en 9 canales
Get PRO
junio '24
+40 467
en 101 canales
Get PRO
mayo '24
+179
en 63 canales
Get PRO
abril '24
+16 037
en 46 canales
Get PRO
marzo '24
+168 159
en 0 canales
Get PRO
febrero '24
+119 660
en 1 canales
Get PRO
enero '24
+189 030
en 13 canales
Get PRO
diciembre '23
+660
en 57 canales
Get PRO
noviembre '23
+205
en 2 canales
Get PRO
octubre '23
+432
en 2 canales
Get PRO
septiembre '23
+221
en 0 canales
Get PRO
agosto '23
+49
en 0 canales
Get PRO
julio '23
+27
en 0 canales
Get PRO
junio '23
+49
en 0 canales
Get PRO
mayo '23
+50
en 0 canales
Get PRO
abril '23
+54
en 0 canales
Get PRO
marzo '23
+55
en 0 canales
Get PRO
febrero '23
+92
en 0 canales
Get PRO
enero '23
+62
en 0 canales
Get PRO
diciembre '22
+93
en 0 canales
Get PRO
noviembre '22
+114
en 0 canales
Get PRO
octubre '22
+125
en 0 canales
Get PRO
septiembre '22
+36
en 0 canales
Get PRO
agosto '22
+80
en 0 canales
Get PRO
julio '22
+45
en 0 canales
Get PRO
junio '22
+101
en 0 canales
Get PRO
mayo '22
+583
en 0 canales
Get PRO
abril '22
+7
en 0 canales
Get PRO
marzo '22
+1
en 0 canales
Get PRO
febrero '22
+16
en 0 canales
Get PRO
enero '22
+33
en 0 canales
Get PRO
diciembre '21
+855
en 0 canales
| Fecha | Crecimiento de Suscriptores | Menciones | Canales | |
| 27 julio | 0 | |||
| 26 julio | 0 | |||
| 25 julio | 0 | |||
| 24 julio | 0 | |||
| 23 julio | 0 | |||
| 22 julio | 0 | |||
| 21 julio | 0 | |||
| 20 julio | 0 | |||
| 19 julio | 0 | |||
| 18 julio | 0 | |||
| 17 julio | 0 | |||
| 16 julio | 0 | |||
| 15 julio | 0 | |||
| 14 julio | 0 | |||
| 13 julio | +219 | |||
| 12 julio | 0 | |||
| 11 julio | 0 | |||
| 10 julio | 0 | |||
| 09 julio | +2 | |||
| 08 julio | 0 | |||
| 07 julio | 0 | |||
| 06 julio | 0 | |||
| 05 julio | 0 | |||
| 04 julio | 0 | |||
| 03 julio | 0 | |||
| 02 julio | 0 | |||
| 01 julio | 0 |
Publicaciones del Canal
Mainnet node owners
Please update your nodes to the 2026.06 release now. See https://t.me/tonstatus/225.
Failure to update your nodes will result in loss of network synchronization once legacy broadcasts are disabled in approximately one week.
| 2 | The proposals to update Config 8 and Config 30 have passed.
The network is now using both the new Plumtree broadcast mechanism and the legacy broadcast mechanism simultaneously.
In approximately one week, we will ask operators to update their validators and nodes. After the update, the network will use only Plumtree broadcasts.
Based on our estimates, this should reduce inbound node traffic by approximately 4× and outbound traffic by 2×. It should also significantly improve synchronization and connectivity for nodes and validators. | 2 855 |
| 3 | Attention Mainnet validators
Please take part in the voting for network config adjustment:
Config 8: Increase the network version to 15. This will enable changes to improve network stability. More information can be found here.
Config 30: Increase the protocol version to 2. This will enable Plumtree broadcasts feature that was included in 2026.06 upgrade.
If you use mytonctrl, please vote for proposal via
vo 22448832751201245177779867389173635147154128832671288809721723331941883236888 43582131604392367431420013209904118299054963940426054667194752056057570768252 | 3 128 |
| 4 | Attention Mainnet validators:
On Wednesday, July 22, starting from 5:30 UTC, we ask that validators set aside time to vote on two proposals.
Config 8: Increase the network version to 15. This will enable changes to improve network stability. More information can be found here.
Config 30: Increase the protocol version to 2. This will enable Plumtree broadcasts feature that was included in [2026.06] upgrade. | 3 897 |
| 5 | Mainnet validators
Please take part in the voting for network config adjustment.
In order to improve the stability of the network, we kindly ask that you vote in favor of temporarily reducing the maximum number of shardchains from 16 to 4. This reduction will not affect the performance of the blockchain or the user experience under the current organic load. This reduction is temporary, and we will increase this setting in an upcoming update.
If you use mytonctrl, please vote for proposal via
vo 106555316457343173969073505303576653234520513474761398896187123848200763819496
You may vote before or after the update to the latest release [v2026.06]. | 6 484 |
| 6 | Mainnet Validator Software Update [v2026.06]
Please update your node software:
Update with mytonctrl:
update master
upgrade master
Target versions:
— mytonctrl: 14be068 [v2.17.0]
— node 3f598aa [v2026.06]
If you are not using mytonctrl or using ubuntu older than 22.04, check this instruction (https://telegra.ph/TON-Node-Upgrade-202511-11-05).
If you have several validators, please update them one by one:
update a validator => wait for synchronization => move to the next one validator
Update is mandatory for validators, liteservers and archive liteservers.
Deadlines: Validators should apply the update within 24 hours of this announcement. Lite Server operators should apply the update no later than EOD Friday, 17th of July.
This release does not include breaking API changes and is fully compatible with recent versions of ton-http-api (acceptable versions: v2.0.64 and higher) and TON Indexer (acceptable versions: v1.2.6 and higher).
Node changelog
Mytonctrl changelog | 5 519 |
| 7 | Mainnet validators and node owners
Please schedule a time on Wednesday, July 15, at 11:00 UTC (tomorrow) to perform the software update. Furthermore, validators will be asked to vote on adjusting the technical network operating parameters.
This update is mandatory for both validators and full node owners. The update will include important changes to improve performance and stability. | 8 293 |
| 8 | Mainnet validators and node owners
The scheduled network update planned for July 13, as well as the corresponding vote on network configuration changes planned for July 15, have been postponed.
We will communicate the new deadlines soon. | 6 437 |
| 9 | Mainnet block production on shard chains has resumed
From approximately 09:30 UTC to 11:12 UTC, there was a significant slowdown in the block rate and message processing on shardchains. Operations have now resumed.
We are monitoring the network and investigating the incident. | 7 177 |
| 10 | Mainnet shard processing slowdown
Block production and message processing in workchain shards are currently experiencing a slowdown.
The TON Core team is aware of this issue and is working to resolve it. | 28 379 |
| 11 | Mainnet validators and node owners
A scheduled network update is planned for July 13.
We ask that operators schedule a time on Monday, July 13 at 10:00 UTC to perform the software update.
This update is mandatory for both validators and full node owners and will include important changes to improve performance and stability.
On July 15, we expect to propose the corresponding network configuration changes for voting. | 12 585 |
| 12 | Mainnet validators
Please take part in the voting for network config adjustment.
Details of updates are given above.
1. Check that your validator software is on the latest version: commit 8e6f091.
2. If you use mytonctrl, please vote for proposals via
vo 9901998680707950950238275199047408807574030713004871006823337513201412566813 21526253372328041162945873458133265853602219828453225088086555939852366673948 25457740459214303188122764586580481160870045992693138140082832275221088727435 27888037080949394985586284390638387418032132650027223566011206271775308997958 47109645929274029714503680701532923988963495538545236837911985690370399364755 91653260358164255814917090285064033870499577570446925645989803264091693189638 97476904964537115993827662219965215594287692635916428067774379550074503377880 105421554118666087537177391865877968766437175802842020945158031714676721220730 63244263381357691341252589176593235583578881537703891344526025000835647174683 | 5 184 |
| 13 | Mainnet validators
A scheduled network configuration adjustment will take place tomorrow, June 3, at 17:00 UTC. We ask validators to cast their votes withing 24 hours after that.
Full details of the update are available here.
This update is required to:
- activate measures that further improve network performance and make validation more stable;
- make validation more permissive by allowing a wider range of minimum and maximum stakes;
- proceed with the TON Bridge closure. | 5 302 |
| 14 | Mainnet Validator Software Update [v2026.05]
Please update your node software:
Update with mytonctrl:
update master
upgrade master
Target versions:
— mytonctrl: 9520ad2
— node 8e6f091
If you are not using mytonctrl or using ubuntu older than 22.04, check this instruction (https://telegra.ph/TON-Node-Upgrade-202511-11-05).
If you have several validators, please update them one by one:
update a validator => wait for synchronization => move to the next one validator
Update is mandatory for validators, liteservers and archive liteservers.
Deadlines: Validators should apply the update within 24 hours of this announcement. Lite Server operators should apply the update no later than Friday, 5th of June.
This release does not include breaking API changes and is fully compatible with recent versions of ton-http-api (acceptable versions: v2.0.64 and higher) and TON Indexer (acceptable versions: v1.2.6 and higher).
Node changelog
Mytonctrl changelog | 5 272 |
| 15 | Mainnet validators and node owners
Scheduled network update on June 1
We ask all validators and node owners to schedule time on Monday, June 1, at 10:00 UTC to update their validator software.
This update is mandatory and introduces security and performance-related changes to consensus.
On June 3, we expect to propose corresponding network configuration changes for voting, including:
- Config8: set TVM version to 14 and activate the full_collated_date capability to improve validation performance.
- Config17: increase max_stake_factor from 3 to 4.5, allowing validators with smaller stakes to continue participating in network maintenance despite higher maximum stakes.
- Config29: set max_collated_bytes to 10 MB.
- Config30: set enable_observers from 0 to 1, introducing a separate overlay for fast candidate broadcasts among validators.
- Config79, 80, 81: change of addresses to proceed with bridge closure.
These changes will increase overall network performance and won't affect validation rewards | 10 745 |
| 16 | Final shutdown stage for Toncoin and Token Bridge
Toncoin and Token Bridge at bridge-v3.ton.org will be permanently shut down on September 1, 2026.
All percentage-based transfer fees have been waived for the remaining bridge withdrawal period.
Users who have previously used the bridge should check their wallets and withdraw any remaining bridged assets before the shutdown date.
Required action
If you have Wrapped Toncoin in your Ethereum or BNB Smart Chain wallet, please bridge it back to TON using bridge-v3.ton.org before September 1, 2026.
If you have jUSDT, jUSDC, jDAI, jWBTC, or any other j-tokens in your TON wallet, please bridge them back to Ethereum using bridge-v3.ton.org before September 1, 2026.
After this date, the bridge will no longer be available for any transfers.
Current status
All previously submitted user transfers have been processed.
For transfers that had been executed but not claimed by users, the required TON and EVM network fees were covered, and those transfers have also been completed.
On June 2026, bridge oracles will withdraw their stakes from the bridge contracts. The oracles will continue processing bridge transfers until the final shutdown on September 1, 2026. | 7 636 |
| 17 | Clarification for TON Node Operators
The Rust implementation of the TON node has experimental status and is not intended for use on the main network, either as a validator or as a full node/liteserver.
At this time, alternative TON node implementations do not yet provide the required quality of operation or sufficient compatibility with current protocols. For validators, this means a risk of penalties for improper operation once the slashing system is re-enabled.
The TON network currently runs on the reference C++ implementation. Bringing alternative implementations into operation is not on the agenda — the priority is the continued rapid development of protocols and technologies in support of the MTONGA plan.
For the main network, operators should use the C++ version of the TON node. | 9 253 |
| 18 | Mainnet Validators
Due to the heightened attractiveness of staking, significant new capital has entered the validation, resulting in a corresponding increase in the minimum and maximum effective stakes required for validation.
We advise validators to verify whether their current machine allocations are sufficient to participate in validation and to aggregate their stakes into larger positions where feasible.
In the current round, the minimum and maximum stakes are 824,000 and 2,425,000 TON, respectively. We anticipate an increase to 1,000,000 and 3,000,000 TON in the near future. Please ensure you are prepared for this adjustment.
If you do not possess sufficient stake to participate in both rounds, consider utilizing staking services, which typically offer specialized conditions for large-scale stakeholders. Alternatively, you may configure 1-of-2 rounds validation. Please contact Core support for consultation regarding the implementation of this strategy to preserve maximal capital efficiency. | 9 072 |
| 19 | Mainnet validators
All proposals were accepted! Thank you! | 8 893 |
| 20 | Mainnet validators
Please take part in the voting for network config adjustment.
Details of updates are given above.
1. Check that your validator software is on the latest version: commit 591b34d.
If you use mytonctrl, please vote for proposal via
vo 84123553170509389098874880050862184605633619991871324449516531408050268055269 42941749423356085253181262402693749199117510848841139894863341148398531565866 65009153936108305610337904793535370282692919307756841131143481982045644609157 | 13 717 |
