TON Connect: what it is, why it matters and how it works

TON Connect is the technical “handshake standard” between a wallet and an app. Without it, every TON dApp would have to either implement support for each wallet by hand or ask the user to export private keys (which is a non-starter). With it, any dApp works with any wallet through the same one-step flow.

If you have ever opened STON.fi, DeDust, getgems.io, or any mini-app with a “Connect Wallet” button — you have already used TON Connect, you just did not know.

Why a protocol like this is needed

A wallet’s private key must never leave the wallet. That is axiomatic. But a dApp needs three things from the user:

1. Discover the address — where to send tokens, whose NFTs to show.
2. Get a signature on arbitrary data — to authenticate the user without a password (signed message), for example.
3. Send a transaction — assembled by the dApp but signed and broadcast by the user.

TON Connect is a set of messages that the dApp and the wallet exchange to handle all three, without ever sharing the key. The analogy: the dApp and the wallet are two apps “talking” through an encrypted bridge. The user sees the request inside the wallet, taps confirm, and the signature flows back to the dApp.

What this looks like for the user

A simple scenario — swapping on STON.fi:

1. Open STON.fi in the browser.
2. Click “Connect Wallet”.
3. A list of wallets appears: Tonkeeper, MyTonWallet, OKX Wallet, Bitget, etc.
4. Pick Tonkeeper.
5. Tonkeeper opens on your phone with the prompt “STON.fi is requesting access to the address. Allow?” — tap Confirm.
6. The site shows your address and balance.

When you go on to make a swap:

1. Click “Swap”.
2. Tonkeeper opens with the transaction laid out — what you send, what you receive, the expected fee.
3. Confirm.
4. The site receives a success notification and refreshes the balance.

This is the basic loop that repeats inside every TON dApp.

Architecture: how it works under the hood

TON Connect 2.0 uses a three-tier model:

• dApp — the app to be connected.
• Bridge — a centralised or decentralised relay server through which the dApp and the wallet exchange encrypted messages.
• Wallet — the wallet that holds the key.

The connection flow:

1. The dApp generates a connect request and a connect-link (ton://... or an https deep link).
2. That request reaches the wallet — either via a click on the link (if the wallet is on the same device) or via a QR code (if the wallet is on a phone and the dApp is in a desktop browser).
3. The wallet connects to the bridge, validates the request, and shows it to the user.
4. The user confirms — the wallet returns the public address and establishes an encrypted session.
5. Subsequent transactions flow through the same session — the dApp sends a “request-transaction”, the wallet shows it, the user confirms, the wallet broadcasts it and replies with the result.

All messages between the dApp and the wallet are encrypted with the public key — the bridge sees only encrypted traffic.

How it differs from WalletConnect

The Ethereum world has a similar protocol — WalletConnect. TON Connect was built separately, because TON’s architecture is fundamentally different:

On TON only TON Connect is used. WalletConnect is not supported because architecturally it does not cover TON’s async semantics.

Which wallets support it

The main TON Connect 2.0 wallets in 2026:

• Tonkeeper — full support, the flagship.
• MyTonWallet — full support, open source.
• Tonhub — supported but on a legacy branch.
• Bitget Wallet, OKX Wallet, Binance Web3 Wallet — exchange-grade multi-chain wallets with TON support.
• SafePal, Trust Wallet — partial support.
• Wallet in Telegram — support via the Wallet Pay SDK, not full TON Connect.

The full registry of supporting wallets lives in the wallets-list repository under TON Foundation.

Where you will meet TON Connect

In 2026 TON Connect is used almost everywhere across the ecosystem:

• DEXs — STON.fi, DeDust, Megaton.
• Staking — Tonstakers, Hipo, bemo.
• NFT marketplaces — getgems.io, Disintar, mrkt.app.
• Games and mini-apps — all of them, except purely custodial flows through Wallet.
• Lending — EVAA, DAOLama.
• Cross-chain bridges — Orbit Bridge, Symbiosis.

There is no serious TON dApp without TON Connect.

Security: what to keep in mind

TON Connect does not turn bad transactions into good ones. If a dApp asks you to sign a drain function, the wallet will show it but will not be able to know it is an attack.

What to remember:

1. Read the transaction body. Tonkeeper and MyTonWallet show parameters — how much TON you send, to which address, what is in the payload. An unfamiliar payload plus a large amount is a reason to refuse.
2. Check the dApp URL. Phishing through Telegram ads constantly pushes fake DEXs. The browser address bar is the only real defence.
3. Disconnect unused sessions. Tonkeeper has “Connected dApps” in settings — that is the list of active connections. After using a dApp, disconnect.
4. Separate wallet for DeFi. Active wallet with $100–500 USDT for swaps and mini-apps; main funds on a cold wallet without TON Connect sessions.

For developers — briefly

If you build a TON dApp, integration takes a day. The main SDKs:

• @tonconnect/ui — drop-in vanilla JS UI kit.
• @tonconnect/ui-react — React wrapper.
• @tonconnect/sdk — bare SDK, no UI (for custom integrations).

Minimal React code is about a dozen lines to add a “Connect Wallet” button supporting the entire wallet registry.

Next

If you want to install a wallet that supports TON Connect — see the comparison of major wallets. General context — the full TON guide.

Sources

• TON Connect documentation
• Protocol specification, ton-blockchain GitHub
• Supported wallets registry