TON Foundation says Telegram Web3 mini-apps have passed 100 million monthly active users, marking another major distribution milestone for one of crypto’s most consumer-facing ecosystems.

That number is big enough to grab attention, but it needs a careful read.

Monthly active users in Telegram mini-apps can include off-chain bot interactions, app sessions, and wallet-adjacent activity. It should not be treated as the same thing as 100 million on-chain TON wallets all making direct transactions.

Still, even with that caveat, the scale is impressive.

TON has something most crypto networks badly want: access to a massive messaging platform where users already spend time.

For more details, visit the official Ton platform.

TL;DR

• TON-linked Telegram mini-apps have passed 100 million monthly active users.
• The figure includes Telegram mini-app activity, not only on-chain wallet transactions.
• TON Space and Telegram-based onboarding remain central to the ecosystem’s growth story.

Why Telegram Distribution Matters

Crypto adoption usually struggles with distribution.

Projects build wallets, exchanges, apps, games, and payment systems, then spend huge amounts trying to attract users. TON starts from a different place because it is closely tied to the Telegram environment.

That does not guarantee adoption.

But it gives TON a user funnel most chains do not have. If people can discover mini-apps inside a messaging app they already use, onboarding feels less alien than downloading a new wallet and learning a new ecosystem from scratch.

That is a real advantage.

Mini-Apps Are Not Just Wallets

The mini-app category is broad.

Some apps may involve games, rewards, bots, payments, trading, social features, or wallet interactions. That means the 100 million MAU number is not a pure measure of on-chain financial activity.

And that is fine, as long as it is explained clearly.

The point is that Telegram-based Web3 apps are reaching a large user base. The next question is how much of that activity converts into durable wallet usage, transactions, payments, and application revenue.

TON Space Helps The Wallet Story

TON Space gives the ecosystem a self-custody wallet route inside Telegram.

That matters because mini-app engagement becomes much more powerful if users can move from playing, earning, or interacting into actual wallet activity without leaving the environment. The smoother that step is, the stronger TON’s consumer crypto case becomes.

Most chains have to build consumer distribution from scratch.

TON can build inside a platform where communication and app discovery already happen.

Bot Activity Needs A Caveat

The source materials note that MAU counts include off-chain Telegram bot interactions alongside direct on-chain wallet transfers.

That caveat should not be buried.

Bot-driven ecosystems can produce huge engagement numbers, but not every interaction has the same economic value. A user clicking inside a mini-app is different from a user holding assets, making payments, or interacting with DeFi.

The quality of activity matters.

Still, engagement is the first step. Without users, none of the deeper metrics can follow.

The TON Market View

TON’s 100 million MAU milestone shows why the network remains one of the most interesting consumer crypto plays.

The number is not a clean on-chain wallet count, and it should not be treated like one. But it does show that Telegram mini-apps are operating at a scale most crypto products never reach.

Now the real test begins.

Can TON convert attention into lasting wallet adoption, useful payments, real transaction volume, and sustainable apps?

That is the question. But reaching 100 million monthly active mini-app users gives the ecosystem a serious platform to work from.

This article draws on TON Foundation materials and Tonstat ecosystem data.

This article was written by the News Desk and edited by Samuel Rae.

This report is based on information released by Ton. at Ton

TAC, a Cosmos-based EVM sidechain connected to the TON ecosystem, has halted block production after a supply-related exploit.

The incident occurred on August 22, according to public incident materials. TAC connects Ethereum-based applications with the TON network, but the exploit affected the TAC sidechain and its token supply, not the main TON blockchain.

That distinction is critical.

The TON mainnet should not be described as halted or compromised based on this incident. The affected network is TAC, an EVM sidechain connected to TON.

TL;DR

• TAC halted block production after a supply exploit.
• The incident affected the TAC sidechain and its token supply.
• TON mainnet was not the halted network.

Exploit Details

TAC halted block production after identifying a security exploit tied to token supply.

A halt is a serious operational step. It means the network stopped producing blocks while the team investigated or contained the issue. For users, that can affect transfers, applications, liquidity, and confidence until operations resume.

The key point is scope.

This was not a halt of TON mainnet. It was a halt of the TAC sidechain, which is designed to connect EVM applications with TON-related infrastructure.

Scope matters because crypto incidents are often misreported when networks are interconnected.

Why EVM Sidechains Carry Different Risks

Sidechains can expand an ecosystem’s functionality.

They may bring Ethereum-compatible applications, tooling, wallets, and smart contract patterns to networks that do not natively operate like Ethereum. That can be useful for developer adoption.

But sidechains also create additional risk surfaces.

They have their own validators, contracts, bridges, token mechanics, and governance. A problem on a sidechain may not compromise the base network, but it can still affect users who rely on that sidechain.

TAC’s halt shows why those distinctions matter.

Supply Exploits Are Serious

A supply exploit can be especially dangerous because it affects trust in the token’s accounting.

If an attacker can mint, inflate, duplicate, or manipulate supply, the economic integrity of the network is at risk. Teams may halt block production to prevent further damage while investigating.

That can be the responsible move, but it is disruptive.

Users need clear communication about what assets are affected, whether balances are safe, whether transactions will be rolled back, and how the network plans to restart.

TON Connection Needs Careful Framing

The TON connection is part of the story, but it should not be exaggerated.

TAC’s purpose is to connect EVM applications with TON. That makes the incident relevant to the broader TON ecosystem. But relevance is not the same as direct impact on TON’s base chain.

The clean framing is: TAC is connected to TON, but TAC is the network that halted.

That protects readers from assuming TON itself stopped.

What Comes Next

The next questions are operational.

When will TAC resume block production? What caused the supply exploit? Will balances be adjusted? Will contracts be patched? Will bridges or related applications need action from users?

Until those questions are answered, caution is warranted.

For the wider ecosystem, the incident is another reminder that sidechain infrastructure can introduce risk even when the base network remains unaffected.

TAC’s halt is serious. It just needs to be understood at the correct layer.

This article is based on TAC-related incident materials and public reporting on the August 22 sidechain halt.

This article was written by the News Desk and edited by Samuel Rae.

This report is based on information released in disclosures at primary source documentation.

The TON Foundation has confirmed that its legacy bridge will be permanently decommissioned on September 1, setting a deadline for users holding wrapped TON and related bridge assets to move back to native forms.

The shutdown affects bridge-v3.ton.org, according to TON materials. Users holding Wrapped TON as an ERC-20 token on Ethereum or BNB Chain, or j-tokens such as jUSDT on TON, need to bridge assets back before the deadline to avoid losing access.

This is a planned infrastructure transition.

It should not be described as an exploit, emergency shutdown, or security failure unless official sources say otherwise.

TL;DR

• TON’s legacy bridge will be decommissioned on September 1.
• Wrapped TON and j-token users need to bridge assets back before the deadline.
• The shutdown is planned and should not be framed as a hack.

Why Bridge Shutdowns Matter

Bridges are one of the most sensitive pieces of crypto infrastructure.

They connect assets across chains, but they also create operational risk. If a bridge is deprecated or shut down, users need clear instructions and enough time to move funds.

A missed deadline can be costly.

Tokens that depend on a bridge may become hard to redeem or move if users do not act before decommissioning. That is why bridge shutdown notices matter even when nothing has been hacked.

They are practical user-risk events.

Wrapped Assets Need Special Attention

Wrapped TON on Ethereum or BNB Chain is not the same as native TON.

A wrapped token usually depends on bridge infrastructure that locks or accounts for the native asset while issuing a representation on another chain. If that bridge is being retired, users need to unwind the wrapped position through the proper route.

The same logic applies to j-tokens on TON.

Users should follow official instructions, use the correct bridge interface, and avoid unofficial links or phishing attempts. Bridge transition periods often attract scammers because users are already expecting to move assets.

Planned Does Not Mean Unimportant

A planned shutdown can still create risk.

The risk is not necessarily technical failure. It is user coordination. Some holders may not see the announcement. Some may wait too long. Some may use the wrong interface. Some may misunderstand which assets are affected.

That is why the September 1 deadline is important.

TON’s ecosystem needs users to act before the legacy infrastructure is retired.

Why Networks Retire Bridges

Protocols may shut down old bridges for many reasons.

A bridge may be replaced by newer infrastructure, become expensive to maintain, no longer fit the ecosystem roadmap, or carry legacy risk the foundation no longer wants to support. Retiring old infrastructure can be healthy if the process is communicated clearly.

The key is migration.

Users need enough time and simple instructions to move assets safely.

What Comes Next

The next milestone is the September 1 deadline.

Until then, wrapped TON and j-token holders should confirm whether they are affected and use official TON channels to bridge assets back. After the deadline, access may become limited or impossible through the legacy route.

For TON, the shutdown is part of infrastructure cleanup.

For users, it is a deadline that should not be ignored.

This article is based on TON Foundation materials regarding the legacy bridge decommissioning.

This article was written by the News Desk and edited by Samuel Rae.

This report is based on information released in disclosures at primary source documentation.

TON validators have been instructed to update their node software and mytonctrl tooling ahead of a configuration vote tied to the network’s new collator architecture.

The validator preparation includes node commit 140320b and mytonctrl commit 7e90e26. The configuration switch vote was scheduled for August 21 at 08:00 UTC.

The important detail is status.

This is a preparation and voting-stage story. It should not be described as full collator activation if the vote and switch process have not completed.

Still, the update matters because collator architecture can affect how TON organizes block production and validator responsibilities as the network scales.

TL;DR

• TON validators were told to update node software and mytonctrl.
• The updates prepare for a collator-related configuration vote.
• The process should not be described as completed activation unless the vote has finalized.

Why Validator Updates Matter

Validator coordination is critical for any blockchain upgrade.

If validators do not update software correctly, networks can face delays, inconsistent behavior, missed blocks, or operational confusion. That is why upgrade instructions often include precise commit versions and deadlines.

TON’s validator update is part of that process.

The network needs participants to prepare their infrastructure before a configuration switch can move forward safely.

For users, this kind of work is mostly invisible — unless something goes wrong.

What Collators Do

Collators are generally tied to collecting transactions, preparing candidate blocks, or supporting block production workflows depending on the network design.

For TON, introducing or activating collator architecture is part of improving how the network handles scale and coordination. The technical details matter most to validators and infrastructure operators, but the user-facing goal is smoother network performance.

This is the kind of upgrade that can strengthen a chain’s underlying machinery.

It may not create an immediate retail-facing feature, but it can improve how the network operates under load.

Vote Status Needs Care

The vote timing is central.

Validators were preparing for a configuration vote, not necessarily announcing that the upgrade had already gone live. Crypto upgrade coverage often jumps too quickly from “vote scheduled” to “activation complete.”

That can mislead users and node operators.

The clean read is that TON’s validator set was being asked to update software and participate in a configuration decision connected to collator activation.

Final status depends on the vote and subsequent network execution.

TON’s Scaling Ambitions Remain Active

TON has positioned itself as a high-throughput blockchain with a large consumer-distribution opportunity, especially because of its connection to Telegram’s ecosystem.

That ambition requires strong infrastructure.

Large-scale consumer blockchain usage is not only about wallets and apps. It requires validators, nodes, transaction processing, developer tools, and upgrade coordination that can support heavy demand.

Collator architecture fits into that broader scaling effort.

What Comes Next

The next step is confirmation of the vote result and any completed configuration switch.

If validators approve and the transition proceeds smoothly, TON can point to another infrastructure milestone. If the vote is delayed or implementation requires more work, the upgrade remains in progress.

For now, the story is clear enough.

TON validators are preparing their software for a collator-related vote, and the network’s infrastructure roadmap is moving forward.

The market should watch the final activation status before treating the upgrade as complete.

This article is based on TON validator update materials and public upgrade notices.

This article was written by the News Desk and edited by Samuel Rae.

This report is based on information released in disclosures at primary source documentation.