Tonkeeper 4.7.0 stable: the final release after the RCs

On May 25, 2026, Tonkeeper 4.7.0 officially graduated from release-candidate status to stable. Before that, between May 18 and May 22, the team shipped five RC builds (rc.1 → rc.5), squashing bugs as they went. As of May 25, 4.7.0 is the recommended version.

Here’s what made it into the final, how it differs from 4.6.x, and whether you should update.

TL;DR: what’s new in 4.7.0

In short, the release closes four big areas:

Security. Fix for a signData spoofing path through TON Connect manifest and localhost manifest. Previously a malicious dApp could theoretically trick the domain check and submit a sign-data request pretending to be a legitimate site.

Swap. Fully reworked: new token search, updated API client, improved sorting in results. In parallel, the standalone web-swap-widget is removed from the repository — the embeddable widget for third-party sites is no longer supported.

Analytics. Added analytics across transactions and the main wallet flows. Updated analytics schema. This is internal telemetry for the team, helping see where users stumble.

Localisation and UX. Pluralisation fixed via the CLDR standard (e.g., “1 wallet”, “2 wallets” — proper forms across all languages). The balance skeleton loader is polished: pre-4.7.0 the wallet briefly showed “$0” while data loaded; now it’s a grey placeholder. The fix is small but the brief “did I lose everything?” moment is gone.

Plus a batch of smaller fixes: tsTON unstake asset parsing, event propagation on address copy, dependency updates, CI workflow improvements.

What stable adds over rc.5

The five RC iterations:

• rc.1 (May 18) — first public build with the major swap rework and signData fix (TK-1104).
• rc.2 (May 19) — stabilisation after rc.1, crash fixes.
• rc.3, rc.4, rc.5 (May 22, a same-day series) — final tweaks, evidently after internal QA findings.
• 4.7.0 stable (May 25) — final with TK-1101 fix and final pluralisation polish.

Practically, stable is functionally the same build as rc.5 with one more test cycle. If you’re already on rc.5, the upgrade to stable is safe and conflict-free.

What the signData fix means

The most consequential item is closing the signData spoofing path through TON Connect manifest. Pre-fix flow:

1. User connects a dApp via TON Connect.
2. The dApp sends a sign-data request (signData).
3. The request includes a domain — supposedly the site originating the request.
4. Tonkeeper showed that domain to the user as confirmation of who’s asking for the signature.

Problem: a malicious dApp could substitute someone else’s domain through manipulation in the manifest — particularly on localhost. The user saw “Sign data for good-site.com” but the actual dApp was something else entirely. A serious social-engineering vector, because signData in newer dApps is used for authentication (Sign-In with TON).

In 4.7.0 stable Tonkeeper does strict domain verification in the manifest. The spoofing path is closed.

What this means for you:

• If you use dApps with TonProof / Sign-In with TON — update immediately. Without 4.7.0 the theoretical attack is possible.
• If you just send TON through Tonkeeper — less critical, but still update.

More on TonProof and Sign-In with TON — in our piece on the topic.

The new swap: what changed

Tonkeeper’s swap is reworked end-to-end. In practical terms:

• Token search: new result-sorting algorithm. Popular/verified tokens rank higher. Lower chance of picking a similar-ticker scam.
• API client: updated to the new version. Quote fetches are likely faster and the UI is smoother during pair selection.
• UI flow: small fixes in the swap confirmation steps.

What stays the same:

• The same routes under the hood (STON.fi/DeDust).
• The same fee model — spread of 0.5-1.5% depending on the pair, plus gas.

If you swap regularly — you’ll notice. If rarely — you’ll feel it on your next use.

TK-1101: what was fixed

Specifically about TK-1101 the public changelog says only “Resolved TK-1101 issue”. It’s an internal team bug ticket; specifics aren’t disclosed. From the context (filed as a core fix, not a feature) it’s likely something system-level, possibly tied to handling certain transaction types or connection scenarios.

Practically: if you experienced crashes, odd behaviour at transaction confirmation, or unexplained errors on 4.6.x, the upgrade to 4.7.0 stable may resolve them. If 4.6.x worked smoothly for you, TK-1101 probably didn’t affect you.

Balance skeleton loader: small but important

Pre-4.7.0, on opening the wallet or after a network reconnection, the top of the UI briefly showed “$0” while data loaded. A second of panic: “wait, did I lose everything?”

In 4.7.0 that moment is gone: a grey skeleton loader (placeholder animation) shows while data loads. When the balance is ready it appears smoothly. Small UX fix, but the “$0” annoyance is fully gone.

CLDR pluralisation: what and why

CLDR (Common Locale Data Repository) is a Unicode library describing grammar rules per language: how to inflect numbers, form plurals, output dates. Pre-4.7.0 Tonkeeper did pluralisation in a simplified way — fine for English but sometimes ugly in Russian and other languages with rich grammar.

From 4.7.0, the rules go through CLDR everywhere. Which means:

• “1 wallet”, “2 wallets”, “5 wallets” — correct forms.
• Proper inflections in Russian, Ukrainian, Polish, German locales.
• No localisation artefacts in any supported locale.

Under the hood — not the loudest change, but if you use a non-English UI, the new build reads noticeably cleaner.

What didn’t make it into 4.7.0

The release doesn’t include:

• Support for new hardware wallets (Ledger / Trezor status quo).
• Wallet v5 / migration flow changes (see our Wallet v5 piece).
• Additional staking or DeFi protocol integrations.
• TonConnect 2 protocol-level changes (UI-side only).

Likely in 4.8.0: further integrations, possibly UX upgrades on account management and multi-wallet flow. No firm info yet.

Who should update

• Any Tonkeeper user — yes, definitely. The signData security fix alone is worth it.
• If on 4.6.x — update immediately. The biggest gap on features and security.
• If on an RC (4.7.0-rc.1 .. rc.5) — update, it’s two minutes. Stable is the final of the same branch.
• If you use dApps with TonProof / Sign-In with TON — critical, don’t delay.

Full Tonkeeper overview (what it does well, what it doesn’t) — in our Tonkeeper review. Comparison with MyTonWallet, Tonhub and Wallet — here. The full release week context — TON ecosystem May 26 piece.