TON Status

Attention Mainnet validators Please vote on the network configuration adjustment. Config 8: Bump global version to 16 in order to activate automated global balance verification. Config 30: Bump consensus protocol to version 2, enabling Plumtree block broadcasts in public overlay. If you use mytonctrl, please vote for proposals via vo 77174338622295924896920533053590426747223363962012796958269

Mainnet Validator and Node Operator Software Update [v2026.10] This update is mandatory for both validators and full node operators, and will activate optimisations on the TON Mainnet network aimed at improving security, performance, and stability. For more information, please refer to the release notes. Please update your node software: Update with mytonctrl: update master upgrade master Ta

Telegram Wallet: Ecosystem Guidelines — dApps: Update to the latest version of TON Connect. If your dApp uses ton_proof, verify that your implementation complies with the specification. — Explorers: We recommend adding support for identifying and displaying Telegram Wallet accounts, displaying key rotation actions, and labeling gasless transactions (example). — Standalone non-custodial wallets:

Mainnet validators and node operators: Please schedule a time to perform and activate the [2026.10] update in accordance with the schedule outlined below. This update is mandatory for both validators and full node operators. The upcoming update will activate optimizations on the TON Mainnet network aimed at increasing security, performance and stability. Update schedule - Monday 19 October at

TON Connect 5.0.0 TON Connect 5.0.0 is now available with improved support for Gram Wallet in Telegram. dApp developers, please update: @tonconnect/sdk@5.0.0 @tonconnect/ui@5.0.0 @tonconnect/ui-react@5.0.0 Important: If your dApp uses ton_proof, ensure your implementation follows the documentation, including the get_public_key fallback when the public key cannot be extracted from walletStateIn

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 contrac

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

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

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.

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 vo

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.

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 7ADCF