Wallet V5: what's new and should you migrate

By 2026 most popular TON wallets create new accounts on the Wallet V5 contract by default (internal name w5r1, sometimes labelled “Wallet V5 Extension” by Tonkeeper). If you registered in Tonkeeper or MyTonWallet before 2024, your active contract is almost certainly V4R2, and the app probably shows an “Upgrade contract” banner. Should you accept it, what actually changes, and what are the trade-offs — let’s go through it.

A wallet on TON is not a database row, it is a standalone smart contract. When you “create a new wallet”, the app deploys an instance of a wallet contract with your public key. The contract version determines what operations the wallet can perform, how fees are calculated and what extensions are possible. V5 is the fifth iteration of this architecture, and it is materially broader than its predecessors.

A short history: V3 to V5

V4 introduced the idea of plugins, but in practice it was almost exclusively used for subscriptions and had limited UI support. V5 reframes plugins as a generic extension mechanism: any external contract can be granted the right to initiate actions on behalf of the owner — provided the owner explicitly authorised it.

What V5 changes architecturally

Several core differences set V5 apart from V4:

1. Generic extensions. In V4 a plugin was effectively a subscription. In V5 an extension is any contract address that the wallet has authorised to send an internal message with an action. This opens the door to automations: auto-top-up of jettons, limit orders, multisig overlays on top of a regular wallet.
2. Gasless transactions. V5 supports “sponsored” messages — a relayer pays TON for gas while the user only signs the intent. Tonkeeper and MyTonWallet use this for USDT transfers: you hold only USDT, no TON, and still send a payment. The relayer takes a fee in USDT equivalent to the gas cost.
3. Batch transfers. A single signed V5 message can spawn up to 255 outgoing messages (V4 capped at four). This matters for airdrops, multi-recipient payments and complex DeFi flows.
4. More compact code. The V5 contract is smaller, which slightly reduces storage fees and base gas. Cents per transaction, but it adds up at volume.
5. Internal and external entry points. V5 accepts actions both through external messages (as before) and through internal messages from authorised extensions. That dual entry point is the foundation of the extension ecosystem.

Gasless in practice

The classic newcomer problem: you bought USDT via P2P, sent it to a TON address, and discovered you cannot send a single cent to anyone because every transaction needs TON for gas. Before V5 the solution was to buy at least 0.1 TON for fees.

With V5 the flow looks like this:

• The user wants to send 10 USDT to a friend.
• The wallet builds a message with an internal flag “pay via relayer”.
• The relayer (operated by the wallet team or a third party) signs and publishes the transaction, paying TON gas from its own balance.
• The same batch contains a compensation transfer in USDT to the relayer — for example, 0.04 USDT.
• The recipient sees a clean 10 USDT transfer, the sender sees a 10.04 USDT debit.

This removes one of the biggest barriers to using TON as “the stablecoin layer for Telegram”, which is exactly why Tonkeeper and MyTonWallet pushed users toward V5 so aggressively.

Extension security

The main risk introduced by V5 is social engineering around extensions. A pattern to watch for:

• A phishing site posing as “a new DeFi protocol” prompts you to “add an auto-farming extension”.
• The user signs an extension-authorisation request.
• The extension contract can, at any later point, send a message to the V5 wallet saying “send the entire balance to address X”.
• Unlike a regular TON Connect approval, an extension does not require a signature for each action — it is authorised “forever” until you explicitly revoke it.

Defensive measures:

1. Install extensions only from official sites and only after verifying the contract address in Tonviewer or TonScan.
2. In Tonkeeper open “Settings → Active extensions” and review the list periodically.
3. Never sign “add extension” in response to a Telegram message or a DM on X — legitimate dApps do not message users privately.
4. For large balances use a separate V5 wallet without extensions, or a multisig.

Migration: step by step

If you have V4R2 in Tonkeeper or MyTonWallet and decide to move to V5:

1. Write your old wallet’s seed phrase on paper. In TON the same seed can deploy contracts of different versions, but the addresses differ. Lose the seed and you lose both V4 and V5.
2. Enable V5 in the UI. In Tonkeeper: “Settings → Wallet → Contract version → V5”. In MyTonWallet — the upgrade banner or “Account options”.
3. Note the new V5 address. The app will show it alongside the old one. Save both, the old one still matters.
4. Move TON. Send a small test transfer (0.1 TON) from V4 to the new V5 address first. Confirm the balance lands.
5. Move jettons. USDT, NOT, jUSDT, every token — one transfer per asset from old V4 to new V5. Jetton wallets deploy automatically on the V5 side on first receive.
6. Move NFTs and .ton domains. Each NFT is a separate “Transfer” transaction. Note that for a .ton domain, ownership change resets DNS records if they were hard-bound.
7. Do not close V4. Leave the old wallet empty but not “deleted”. If someone sends a jetton to the old address later, you can still claim it.

Wallets that support V5

Status mid-2026:

• Tonkeeper — V5 by default for new accounts, extensions and gasless USDT supported.
• MyTonWallet — V5 base supported; extension ecosystem coverage may differ from Tonkeeper’s — check the release notes of the version you run.
• Tonhub — supports V5, but the team’s focus has shifted and development cadence is slower than competitors’.
• Wallet (Telegram) — custodial, does not expose user-owned V4/V5 contracts directly.
• Ledger via Tonkeeper — V5 supported, but update Tonkeeper to a recent build: early 2024 releases only handled V4.

When NOT to migrate

• You run a Ledger-only cold wallet strictly for storage, with no outgoing transfers. V4R2 is enough, and every extra migration step is an attack surface for mistakes.
• You use a multisig. A multisig is a separate contract, and moving “the regular wallet” from V4 to V5 has no effect on multisig members.
• Your wallet is bound to a long-running DeFi protocol (staking, LP) that expects a specific address. Exit positions first, then migrate, then re-enter.

Bottom line

Wallet V5 is not a cosmetic update — it is a foundation swap: batching, gasless, extensions. For an active user in 2026 the upside is obvious, especially if you hold USDT and send stablecoins frequently. The price of that flexibility is a new attack surface in the form of extensions; keep it under control, audit your plugin list, and never sign “add extension” from an unfamiliar site. Migration costs an hour of time and a few cents in transfer fees. There is no path back, but you will not need one.