fa
Feedback

فریب کلاهبرداران را نخورید! تل‌متریو این کانال‌ها را شناسایی و برچسب‌گذاری می‌کند 👉 برای مشاهده برچسب، اشتراک تهیه کنید 👈

TON Status

TON Status

رفتن به کانال در 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.

نمایش بیشتر
کشور مشخص نشده استفناوری و برنامه‌ها686

📈 تحلیل کانال تلگرام TON Status

کانال TON Status (@tonstatus) در بخش زبانی انگلیسی بازیگری فعال است. در حال حاضر جامعه شامل 155 889 مشترک است و جایگاه 686 را در دسته فناوری و برنامه‌ها دارد.

📊 شاخص‌های مخاطب و پویایی

از زمان ایجاد در невідомо، پروژه رشد سریعی داشته و 155 889 مشترک جذب کرده است.

بر اساس آخرین داده‌ها در تاریخ 07 اکتبر, 2026، کانال فعالیت پایداری دارد. در ۳۰ روز گذشته تغییر اعضا برابر -3 953 و در ۲۴ ساعت گذشته برابر -125 بوده و همچنان دسترسی گسترده‌ای حفظ شده است.

  • وضعیت تأیید: تأیید شده (به صورت رسمی توسط تلگرام)
  • نرخ تعامل (ER): میانگین تعامل مخاطب 4.76% است و در ۲۴ ساعت نخست پس از انتشار، محتوا معمولاً 1.95% واکنش نسبت به کل مشترکان کسب می‌کند.
  • دسترسی پست‌ها: هر پست به طور میانگین 7 420 بازدید دریافت می‌کند. در اولین روز معمولاً 3 038 بازدید جمع‌آوری می‌شود.
  • واکنش‌ها و تعامل: مخاطبان به‌طور فعال حمایت می‌کنند؛ میانگین واکنش به هر پست 0 است.

📝 توضیح و سیاست محتوایی

نویسنده این فضا را محل بیان دیدگاه‌های شخصی توصیف می‌کند:
“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.”

به لطف به‌روزرسانی‌های پرتکرار (آخرین داده در تاریخ 08 اکتبر, 2026)، کانال همواره به‌روز و دارای دسترسی بالاست. تحلیل‌ها نشان می‌دهد مخاطبان به‌طور فعال با محتوا تعامل دارند و آن را به نقطه اثرگذاری مهم در دسته فناوری و برنامه‌ها تبدیل کرده‌اند.

155 889
مشترکین
-12524 ساعت
-9487 روز
-3 95330 روز

در حال بارگیری داده...

کانال‌های مشابه
ابر برچسب‌ها
هیچ داده‌ای
مشکلی وجود دارد؟ لطفاً صفحه را تازه کنید یا با مدیر پشتیبانی ما تماس بگیرید.
اشارات ورودی و خروجی
---
---
---
---
---
---
جذب مشترکین
اکتبر '26
اکتبر '260
در 7 کانال‌ها
سپتامبر '260
در 25 کانال‌ها
Get PRO
اوت '26
+105
در 93 کانال‌ها
Get PRO
ژوئیه '26
+221
در 71 کانال‌ها
Get PRO
ژوئن '260
در 18 کانال‌ها
Get PRO
مه '26
+123
در 49 کانال‌ها
Get PRO
آوریل '26
+207
در 90 کانال‌ها
Get PRO
مارس '260
در 9 کانال‌ها
Get PRO
فوریه '260
در 7 کانال‌ها
Get PRO
ژانویه '260
در 0 کانال‌ها
Get PRO
دسامبر '250
در 2 کانال‌ها
Get PRO
نوامبر '250
در 45 کانال‌ها
Get PRO
اکتبر '250
در 27 کانال‌ها
Get PRO
سپتامبر '250
در 25 کانال‌ها
Get PRO
اوت '250
در 8 کانال‌ها
Get PRO
ژوئیه '250
در 58 کانال‌ها
Get PRO
ژوئن '25
+638
در 163 کانال‌ها
Get PRO
مه '250
در 4 کانال‌ها
Get PRO
آوریل '250
در 5 کانال‌ها
Get PRO
مارس '250
در 14 کانال‌ها
Get PRO
فوریه '250
در 12 کانال‌ها
Get PRO
ژانویه '250
در 6 کانال‌ها
Get PRO
دسامبر '24
+835
در 10 کانال‌ها
Get PRO
نوامبر '24
+1 520
در 4 کانال‌ها
Get PRO
اکتبر '24
+5 358
در 13 کانال‌ها
Get PRO
سپتامبر '24
+13 413
در 305 کانال‌ها
Get PRO
اوت '24
+9 267
در 222 کانال‌ها
Get PRO
ژوئیه '24
+18 069
در 9 کانال‌ها
Get PRO
ژوئن '24
+40 467
در 101 کانال‌ها
Get PRO
مه '24
+179
در 63 کانال‌ها
Get PRO
آوریل '24
+16 037
در 46 کانال‌ها
Get PRO
مارس '24
+168 159
در 0 کانال‌ها
Get PRO
فوریه '24
+119 660
در 1 کانال‌ها
Get PRO
ژانویه '24
+189 030
در 13 کانال‌ها
Get PRO
دسامبر '23
+660
در 57 کانال‌ها
Get PRO
نوامبر '23
+205
در 2 کانال‌ها
Get PRO
اکتبر '23
+432
در 2 کانال‌ها
Get PRO
سپتامبر '23
+221
در 0 کانال‌ها
Get PRO
اوت '23
+49
در 0 کانال‌ها
Get PRO
ژوئیه '23
+27
در 0 کانال‌ها
Get PRO
ژوئن '23
+49
در 0 کانال‌ها
Get PRO
مه '23
+50
در 0 کانال‌ها
Get PRO
آوریل '23
+54
در 0 کانال‌ها
Get PRO
مارس '23
+55
در 0 کانال‌ها
Get PRO
فوریه '23
+92
در 0 کانال‌ها
Get PRO
ژانویه '23
+62
در 0 کانال‌ها
Get PRO
دسامبر '22
+93
در 0 کانال‌ها
Get PRO
نوامبر '22
+114
در 0 کانال‌ها
Get PRO
اکتبر '22
+125
در 0 کانال‌ها
Get PRO
سپتامبر '22
+36
در 0 کانال‌ها
Get PRO
اوت '22
+80
در 0 کانال‌ها
Get PRO
ژوئیه '22
+45
در 0 کانال‌ها
Get PRO
ژوئن '22
+101
در 0 کانال‌ها
Get PRO
مه '22
+583
در 0 کانال‌ها
Get PRO
آوریل '22
+7
در 0 کانال‌ها
Get PRO
مارس '22
+1
در 0 کانال‌ها
Get PRO
فوریه '22
+16
در 0 کانال‌ها
Get PRO
ژانویه '22
+33
در 0 کانال‌ها
Get PRO
دسامبر '21
+855
در 0 کانال‌ها
تاریخ
رشد مشترکین
اشارات
کانال‌ها
08 اکتبر0
07 اکتبر0
06 اکتبر0
05 اکتبر0
04 اکتبر0
03 اکتبر0
02 اکتبر0
01 اکتبر0
پست‌های کانال
The nominator-pool v1 smart contract is now deprecated. Operators using nominator-pool v1 should plan their migration based on the number of nominators in their pool: 1. One nominator: migrate to single-nominator v1.1. 2. Multiple nominators: migrate to nominator-pool v2. Both contracts are supported by MyTonCtrl, the validator management tool. Both contracts can be used with a vesting contract.

2
Degraded connectivity in the public overlay Since September 23, a large number of new nodes that do not forward traffic have appeared in TON’s public overlay. This may degrade external message delivery and block synchronization for participants in the public overlay. These broken nodes are hosted on the following IP addresses, with multiple nodes per IP: 88.216.36.12 88.216.36.80 88.216.182.81 173.234.137.88 88.216.182.41 5.39.221.152 185.191.116.151 51.75.112.186 51.75.134.122 173.234.75.234 178.63.134.206 46.243.221.126 141.95.206.225 57.129.49.17 84.32.103.165 164.132.187.125 82.23.163.70 185.189.45.145 85.195.124.117 138.124.50.195 37.59.67.41 178.20.209.27 185.191.118.150 Major TON services, including exchanges, wallets, Telegram, and Toncenter API, remain unaffected and continue to operate normally, as they do not use the public overlay. Activation of the new Plumtree broadcasts in the public overlay is scheduled for October. This will improve delivery reliability even when a large number of nodes do not forward traffic. Exchanges and custodial services experiencing issues should reach out to their technical contact at TON for assistance. Other developers are advised to use one of the public HTTP APIs alongside their own nodes.
3 919
3
Attention Mainnet validators Please vote on the network configuration adjustment. Config -123: Minor improvements to the tg-wallet-v1 contract code, as well as testing of the wallet code upgrade mechanism on the mainnet. If you use mytonctrl, please vote for proposal via vo 80830481238463553029095138363073923401512085865719374095445995292694011185619
5 984
4
Mainnet Validators Please schedule time wednesday, September 30, starting from 06:00 UTC to participate in the vote on the mainnet configuration update. Voting is required.
7 563
5
Attention Mainnet validators Please vote on the network configuration adjustment. Config 30: Increase the value of the leader_window parameter (and the associated leader_window_desync) to boost TPS by up to 30%. Config -123: Add the tg-wallet-v1 contract code to the network configuration. This contract is proposed for use with the native Gram Wallet on Telegram. If you use mytonctrl, please vote for proposals via vo 103977679907079231412971872774910018708729377663169264282575516601797565636726 93463024555200663351131178258216152471992757657627817026564359306222314920856
7 319
6
Mainnet Validators Please schedule time tomorrow, August 27, at 15:00 UTC to participate in the vote on the mainnet configuration update. Voting is required.
7 135
7
Attention Mainnet validators Please prepare for an increased network load and ensure that your validator nodes: 1) Have added a public collator list in accordance with the previously posted instructions. 2) Have a working QUIC port. Currently, validators with the following ADNL addresses do not have an operating QUIC port: 81A6ED816FE7C0552CA4CEDBC3BF4F2F03185CCD318CBF61DB06881D33C967CC 7ADCF5845D9878E3C21AA18C4258187DCEEAA32946042085DFF9DCFB7AB81B34 AEAAA7C47A9F3599A9C7CA11C55E5F88171A09C80D0C3783392686FE9B804BFA B3E28C2BBF3620C5F91B8C152358123E841586A8267D0D174D9B093ADBA048A5 1CF38919D5EBB5CAE3305ECB03B99FD810F55B8510F080880FAF4941665135C0 5BBB2FEFE0D41448B297C75EDEABD0B212978E8FB4DCE7109ED343CFF8CD3C41 74B134353AB0A79C94BC4633F3045C50638B0C909B02BE032F79B585A1D7B90F If you find your machine on the list, please urgently check your configuration using the instructions. 3) Have a system configuration that corresponds to the latest requirements. Please note that failure to observe the above rules will endanger network stability. If these requirements are not met, we will be forced to submit manual requests to slash specific validators.
8 331
8
Attention Mainnet validators This update is mandatory for validators; full node owners do not need to update. Please update mytonctrl software on your machines: update master Target versions: — mytonctrl: 64c2aa9 [v2.18.0] This step will complete activation of collators on Mainnet network. If you are not using mytonctrl, please add collators to your validators by downloading the default Mainnet collators list and issuing the following command in validator-engine-console: set-collators-list <collators_list_json>
7 453
9
Attention Mainnet validators Please make sure that you have updated your machines to [2026.08] release and take part in the voting for network config adjustment: Config 29: Increase the maximum block size to fine-tune the performance of the collator's functionality. Config 31 and 46: Enable governance contracts related to the functionality of collators. If you use mytonctrl, please vote for proposal via vo 12097562318048223189791980678866953557765689069632717643120314596680459571900 34208501212381821884916867027323947451549110714692222438954375336280844532496 46820293701090638002625837343589766216202823093489845373581525548982016382986
6 330
10
Mainnet Validator Software Update [v2026.08] This update is mandatory for validators; full node owners do not need to update. Please update your node software: Update with mytonctrl: upgrade master Target versions: — node: 3d478cb [v2026.08] 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 Deadlines: Validators should apply the update within 24 hours of this announcement. Node changelog We remind validators about upcoming steps towards activation of collators: Monday 17 August at 14:00 UTC: upgrade of node software to version [2026.08]. Tuesday 18 August at 12:30 UTC: voting on network configuration changes. Thursday 20 August at 12:00 UTC: update of the mycontrol software and activation of collators.
6 006
11
Mainnet validators: Please schedule a time in accordance with the schedule outlined below to perform and activate the [2026.08] update. This update is mandatory for validators; full node owners do not need to update. The upcoming update will activate collators on the TON Mainnet network. Update schedule: Monday 17 August at 14:00 UTC: upgrade of node software to version [2026.08]. Tuesday 18 August at 12:30 UTC: voting on network configuration changes. Thursday 20 August at 12:00 UTC: update of the mycontrol software and activation of collators. Please note that validator operators will not need to take any additional actions besides those mentioned above.
5 979
12
Attention Mainnet validators Please take part in the voting for network config adjustment: Config 30: Set the protocol to stable version. If you use mytonctrl, please vote for proposal via vo 97476904964537115993827662219965215594287692635916428067774379550074503377880
7 555
13
Mainnet Validator and Node Software Update [v2026.07] Please update your node software: Update with mytonctrl: update master upgrade master reload_global_config Target versions: — node: bb935a8 [v2026.07] — mytonctrl: 90046e0 [v2.17.1] 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 and full node should apply the update within 24 hours of this announcement. Lite Server operators should apply the update no later than EOD Friday, 7th of August. 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
7 236
14
The update instructions will be published within 2 hours.
5 274
15
Mainnet validators and node owners: Please schedule a time on Monday 3 August at 11:00 UTC to perform the software update. This update is mandatory for both validators and full node owners. The update will complete the switch to the plumtree broadcast method enabled in release 2026.06, and will disable the legacy broadcast method to reduce network traffic.
7 565
16
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.
9 591
17
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.
6 957
18
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
6 332
19
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.
5 752
20
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].
7 666