Futures
Access hundreds of perpetual contracts
TradFi
Gold
One platform for global traditional assets
Options
Hot
Trade European-style vanilla options
Unified Account
Maximize your capital efficiency
Demo Trading
Introduction to Futures Trading
Learn the basics of futures trading
Futures Events
Join events to earn rewards
Demo Trading
Use virtual funds to practice risk-free trading
Launch
CandyDrop
Collect candies to earn airdrops
Launchpool
Quick staking, earn potential new tokens
HODLer Airdrop
Hold GT and get massive airdrops for free
Launchpad
Be early to the next big token project
Alpha Points
Trade on-chain assets and earn airdrops
Futures Points
Earn futures points and claim airdrop rewards
TON Sub-Second Mainnet Upgrade Coming Soon: New Narrative for Payments and Gaming on the Telegram Blockchain
In April 2026, The Open Network is set to deliver the most meaningfully substantive performance upgrade since its mainnet went live. The Sub-Second upgrade announced by the TON Core team has entered the final phase of mainnet deployment, with a plan to complete full activation on April 7. This upgrade will compress the time to final block confirmation from the current ~10 seconds to ~1 second, and reduce the block interval from ~2.5 seconds to 200-400 milliseconds.
As competition among public chains increasingly centers on “who can handle real applications,” TON has secured a unique advantage thanks to its deep integration with Telegram and the resulting user base. Whether this sub-second upgrade can truly unlock the potential of that user pool depends on the dual push of technological rollout and ecosystem adaptation.
The real technical substance of the upgrade: How Catchain 2.0 compresses time
The core of the Sub-Second upgrade is the deployment of the consensus-layer protocol Catchain 2.0. Unlike simple parameter tuning, this upgrade involves a redesign of TON’s underlying consensus mechanism.
Judging by performance metrics, the change before and after the upgrade is substantial. On the current mainnet, the block interval is about 2.5 seconds, meaning the network processes about 0.4 blocks per second, with final confirmation requiring about 10 seconds to wait; meanwhile, on the testnet under the Catchain 2.0 environment, it has already achieved an approximate 450-millisecond block interval and 1-2 seconds for final confirmation. The mainnet target after the upgrade is to further compress the block interval to 200-400 milliseconds, processing 2.5-5 blocks per second, with final confirmation controlled to about 1 second.
This performance leap follows an optimized version of the Catchain consensus algorithm. TON’s original infinite-sharding architecture provides theoretical high-throughput capacity—during a public test in October 2023, TON reached a peak of 104,715 transactions per second. But there is a difference between throughput capacity and actual confirmation speed: a high TPS guarantees the network’s ability to carry large-scale transactions, while sub-second finality solves the time cost from a single transaction being issued to becoming non-reversible confirmation. The latter has a more direct impact on user experience.
At the same time, TON Center has released the accompanying Streaming API v2, providing push-based transaction status updates, with on-chain event to client latency controllable to 30-100 milliseconds. This infrastructure upgrade is as important as the technical improvements at the protocol level, and may even be a deciding variable in whether users can actually perceive an “sub-second” experience.
Deployment roadmap and key timeline milestones
The Sub-Second upgrade uses a three-stage推进 strategy to ensure mainnet security and coordination among validating nodes:
March 31: Validating nodes complete version updates and upgrade to the latest version that supports Catchain 2.0
April 2: Validators vote on the base chain to activate the new consensus mechanism, increasing block-production frequency
April 7: The base chain and master chain are fully synchronized and the fast consensus mechanism is enabled; upgrade completed
The TON Core team specifically reminds that during the two weeks from March 31 to April 12, validators must remain highly alert in operations and maintenance to handle potentially abnormal situations. This arrangement reflects the complexity of a consensus-layer upgrade—even after validation on the testnet, uncertainty still exists in real operations under mainnet conditions.
Unlocking application scenarios: Three tracks will see structural changes
The value of sub-second finality for blockchain applications is not simply “faster,” but that it makes possible use cases that previously couldn’t be realized due to latency issues. Three tracks will benefit directly from this upgrade:
Instant small payments: For a long time, user experience for on-chain payments has been constrained by confirmation wait times. The 10-second final confirmation already creates noticeable friction costs in scenarios such as cafés and convenience stores—users often have to wait for confirmation prompts to appear on the cashier-screen. Sub-second confirmation brings on-chain payments closer to the feel of card swipes or QR scans, making small-payment scenarios in the TON ecosystem within Telegram a viable alternative to traditional payment methods.
High-frequency interactions in on-chain games and Mini Apps: High-frequency interactions in GameFi and Telegram Mini Apps are extremely sensitive to latency. Previously, each on-chain action required waiting several seconds for a response, and users could clearly feel “lag.” After the upgrade, actions such as asset transfers within the game, reward claiming, and battle settlement can achieve near-real-time feedback. This change could drive increased activity for lightweight on-chain games in the TON ecosystem.
Stablecoin settlement efficiency: The on-chain stablecoin supply on the TON chain has grown from about $1.8 billion at the beginning of 2024 to about $12 billion. One of the core use cases for stablecoins is fast settlement; sub-second confirmation further compresses funds-in-transit time, which has direct value for high-frequency transfers and cross-border payment scenarios.
In addition, the Telegram ecosystem’s infrastructure is improving in parallel. Dynamic has added an embedded wallet feature to Telegram Mini Apps, allowing developers to deploy a TON wallet inside their apps without building a wallet system themselves. The TON Pay payment SDK was also released in February 2026, enabling merchants and Mini App developers to directly integrate crypto payment functionality. These tools, combined with the sub-second upgrade, create an additive effect that lowers the technical barrier for integrating TON at the application layer.
Constraints on upgrade outcomes: Ecosystem adaptation is the key variable
In its technical announcement, TON official explicitly pointed out a fact that is easy to overlook: even if the underlying blockchain produces blocks at 10x speed, if applications continue to use HTTP polling rather than Streaming API, the latency for transaction status updates in the user interface may still exceed 10 seconds.
A concrete comparison shows this clearly: with HTTP polling, after a user clicks “send,” the transaction is included into a shard block within about 0.4 seconds, then submitted to the main chain in 0.8 seconds, but the UI must wait until the next polling request to update—latency may exceed 10 seconds. After switching to Streaming API v2, the whole process can be completed within 1 second—0.1 seconds to show a pending state, 0.4 seconds to show confirmed, and 0.8 seconds to show final confirmation.
This means whether users can perceive an “sub-second” experience does not depend entirely on the mainnet upgrade itself; it also depends on whether wallets, dApps, and payment providers complete client-side adaptation. The TON core team has stated clearly: “If applications cannot perform adaptation, even if the underlying system is operating normally, the upgrade will appear to be ineffective.”
This constraint cannot be ignored when evaluating the real impact of the upgrade. As of April 2, products such as MyTonWallet and tonscan.org have already adopted the new API, reducing transaction response time by nearly half. However, within the ecosystem, many Mini Apps and third-party services have uneven adaptation progress, which may cause a split in user experience during the early phase of the upgrade.
Ecosystem expansion and potential challenges
In early 2026, the TON ecosystem has already shown signs of accelerated expansion. MoonPay has integrated cross-chain top-up functionality into Telegram self-custody wallets, allowing more than 100 million users to directly top up TON wallets with assets such as BTC and ETH. xStocks under Kraken has launched tokenized U.S. stock trading on TON, covering underlying assets such as Tesla and Nvidia. These application scenarios place naturally high demands on transaction confirmation speed, and user experience will improve directly after the sub-second upgrade.
However, the risks that come with ecosystem expansion must also be examined:
Security risks: Accelerating the consensus mechanism may introduce new attack vectors. Catchain 2.0 shortens the time window for block production and confirmation, and significantly increases the response speed requirements for validating nodes. If some validating nodes fail to synchronize the upgrade or fall behind due to network latency, fork risk may arise. The TON Core requires validators to remain highly alert in operations and maintenance within two weeks—this itself reflects the system fragility at the beginning of the upgrade.
Adaptation costs: Application-layer developers need to perform technical migration, including switching to Streaming API v2, handling four transaction states (pending、confirmed、finalized、trace_invalidated), and updating UI design. For small development teams, this migration requires engineering resources and may cause some application upgrades to lag.
Competitive landscape: High-performance public chains such as Solana, Aptos, and Sui are also pursuing low latency and high throughput. TON’s differentiation advantage lies in Telegram’s 900 million user base and social entry points—not simply in technical parameters. The significance of the sub-second upgrade is to remove technical shortcomings, so ecosystem competition can return to application quality and user acquisition capability.
Multi-scenario evolution simulations
Based on the upgrade technical path and the current ecosystem situation, three possible evolution scenarios can be simulated:
Scenario one: smooth rollout
Validating nodes complete synchronization, and Streaming API is rapidly adopted across mainstream applications. In real usage, users perceive a significant improvement in confirmation speed, and on-chain transaction volume shows a sequential increase within 4-8 weeks after the upgrade. User retention for payment-type Mini Apps improves, bringing more developers to integrate into the TON ecosystem. Improvements in stablecoin settlement efficiency attract more payment scenarios to onboard.
Scenario two: experience divergence
The mainnet technical upgrade completes smoothly, but many Mini Apps and mid-/small-sized wallet service providers lag behind in adaptation. User experience differences across different applications become obvious—applications that have adapted have confirmation speeds close to 1 second, while applications that have not adapted still show noticeable latency. This divergence may lead users to concentrate on top-of-market applications with better experiences, accelerating the trend of ecosystem “top-heaviness.”
Scenario three: technical risk triggered
After the upgrade, anomalies occur at the consensus layer, such as a fork or validating node synchronization failure. TON Core launches an emergency response plan, which may require rolling back part of the node versions. Market trust in the upgrade’s effectiveness may be temporarily damaged, and the TON token price faces downward pressure. But given that the testnet has been validated and the upgrade uses a phased rollout strategy, the probability of severe failure is relatively low.
Conclusion and outlook
TON’s Sub-Second upgrade is a technology iteration with substantive significance. It compresses confirmation time from about 10 seconds to about 1 second, bringing the responsiveness of on-chain interactions close to the standards of Web2 applications. This change provides the technical foundation for scenarios such as instant payments, high-frequency interactions in chain games, and rapid stablecoin settlement.
However, the real effect of the upgrade depends on the quality of rollout across two layers: first, the stable operation of the mainnet consensus layer after April 7; second, the pace of ecosystem applications migrating to Streaming API. The former has been validated via the testnet, while the latter depends on developers’ engineering investment and technical support from the TON Foundation.
Over a longer time horizon, the sub-second upgrade is a key step for TON’s transformation from a “user scale narrative” to an “application rollout narrative.” The value of Telegram’s traffic entry point has already been established, but converting traffic into on-chain activity requires a smooth user experience. This upgrade fills the performance shortfall, giving TON more sufficient conditions to compete in carrying real application scenarios.
As of April 2, 2026, according to Gate market data, the TON price is $1.21, with a 24-hour trading volume of $412,590, a market cap of $3.01 billion, and a market share of 0.25%. The price changed by -0.43% over the past 24 hours, -6.85% over the past 7 days, and -1.23% over the past 30 days. The current circulating supply is 2.47 billion TON, and the total supply is 5.15 billion TON.
There is no linear mapping between the upgrade’s technical value and market price. How the market responds will depend on the effectiveness of real-world rollout—whether users can perceive the change, whether developers actively adapt, and whether on-chain activity shows measurable growth. Verifying these indicators takes time, and April 7 is only the starting point, not the endpoint.