TON Foundation confirmed it will permanently shut down its legacy bridge on September 1. The decommissioning affects bridge-v3.ton.org, and users holding Wrapped TON as an ERC-20 token on Ethereum or BNB Chain, or j-tokens like jUSDT on TON, must bridge their assets back before the deadline. It's a planned transition, not an exploit or a security failure.
What's being retired
The bridge in question is bridge-v3.ton.org, the old gateway for wrapping TON onto other networks. If you've got Wrapped TON sitting on Ethereum or BNB Chain as an ERC-20, that's the one affected. Same goes for j-tokens — those are TON-native representations of other tokens, jUSDT being the most common example. Both types need to be moved back to the TON chain through the bridge before the cutoff.
The hard deadline
September 1 isn't a suggestion. After that date, access to assets via the legacy bridge may become limited or impossible. There's no grace period. Anyone holding these tokens has a window that closes at the end of that day.
A planned change, not a hack
The Foundation is clear: this is a planned infrastructure transition. It's not an emergency shutdown, not a vulnerability being patched, not a hack. The bridge is simply being retired as the network moves to newer infrastructure. That doesn't make it risk-free for users, though. A bridge shutdown creates coordination problems — missed deadlines, wrong interfaces, or plain confusion can leave assets stranded.
The phishing risk
TON Foundation warns users to follow official instructions and avoid unofficial links. Phishing attempts tend to spike around bridge transitions, so double-check that you're on the correct bridge interface. The only safe move is to bridge assets back before September 1 using the official bridge URL. After that, it's too late.
