BuildNot yet confirmed elsewhere1 publisher2 min readPublished
Importing a Tonkeeper recovery phrase into Keeper can show a TON address the user has never seen
Tonkeeper is now Keeper and supports seven networks, according to a dev.to post that treats key derivation as the main migration risk. The post argues a wallet UI can simplify steps but cannot remove blockchain boundaries.
The Engineer · Build desk
An old phrase restored into the wrong wallet structure can show a never-seen address; funds may not be gone. TON-only and multichain wallets can use different derivation paths. USDT on each network is separate. The post advises an explorer check and a test transfer first.
- exposure Users restoring an old phrase Importing into the wrong wallet structure can show a never-seen address; the original funds have not necessarily disappeared, claim 12
- constraint Keeper wallet types The older TON-only wallet and the new multichain wallet can use different derivation paths, claim 10
- exposure USDT holders USDT on TON, TRON, Ethereum and BNB Chain is not interchangeable; each follows its own network's rules, claim 3
- decision Migrating Tonkeeper users Post's advice: keep the original wallet, check the address on a block explorer, send a small test amount first, claim 7
| Who | How | Kind | Claim |
|---|---|---|---|
| Users restoring an old phrase | Importing into the wrong wallet structure can show a never-seen address; the original funds have not necessarily disappeared | exposure | 12 |
| Keeper wallet types | The older TON-only wallet and the new multichain wallet can use different derivation paths | constraint | 10 |
| USDT holders | USDT on TON, TRON, Ethereum and BNB Chain is not interchangeable; each follows its own network's rules | exposure | 3 |
| Migrating Tonkeeper users | Post's advice: keep the original wallet, check the address on a block explorer, send a small test amount first | decision | 7 |
What happened
- Tonkeeper began as a TON-only wallet, so it handled one set of addresses, transaction formats, fee mechanics, dApps and derivation rules.
- Keeper now has to handle Bitcoin's UTXO model, EVM-style accounts on Ethereum, Base, Arbitrum and BNB Chain, TON's wallet-contract architecture and TRON's own execution and fee model.
- The post says Keeper's documentation describes the older TON-only wallet and the new multichain wallet as able to use different derivation paths.
Why it matters
- constraint Whatever the interface unifies, it has to keep five facts visible: network, address format, gas asset, bridge involvement and receiving-platform support.
- exposure A user who restores an old phrase into the wrong wallet structure can see an unfamiliar address and take the balance for lost, though the funds may sit at the original address.
- decision Anyone moving from Tonkeeper has to sequence the move: keep the original wallet, verify the address on a block explorer, send a small test amount, confirm receipt, then move larger balances.
- cost Keeper stays self-custodial, so a user who loses both device and phrase cannot be helped: the provider cannot recreate the keys.
The derivation step is where a rebrand turns into a key-management problem. The post gives the chain as seed phrase, derivation path, private key, blockchain address [11]. Hold the phrase fixed and change the path, and the address can change [11]. The post therefore says wallet migration should be treated as a key-management operation, not a normal app upgrade [6].
The abstraction job is smaller than the seven networks suggest [13]. Four of them use EVM-style accounts, and Bitcoin, TON and TRON each use a model of their own [8]. That is four models behind seven network names [8].
The post's USDT example is where the difference bites. It lists four networks, and those four sit on three models, because Ethereum and BNB Chain share the EVM one [9]. Each version of the token follows the rules of the network it lives on [3].
In our view the design follows from that. Network has to be a required field on every send and receive screen, because the ticker alone does not say whose rules apply. That is the right call for a wallet whose users hold one asset on several chains, and the post describes exactly that case.
The post is a conceptual piece. It relays Keeper's documentation without naming the derivation paths either wallet uses, and it does not describe how the app builds or signs transactions across the four models. What it offers is a design requirement: simplify the steps, keep the network boundary visible [5]. Whether Keeper's screens meet that requirement cannot be checked from this text.
What to watch
- Keeper's own documentation naming the derivation paths for the old TON-only wallet and the multichain wallet.
- How Keeper's send screen labels network and gas asset for USDT across TON, TRON, Ethereum and BNB Chain.
- Whether users report empty-looking TON wallets after importing old Tonkeeper phrases into the new flow.
Clarity's read
What the record supports and how the coverage leans. The claims behind it follow.
Reality
- Evidence40
- Adoption
- Insufficient
- Hype gap−5
- Incentives
- Insufficient
- Confidence45
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
Tonkeeper originally focused on TON, a relatively narrow technical environment: TON addresses, TON transaction formats, TON fee mechanics, TON-specific dApps and TON wallet derivation rules.
- [2]
Bitcoin uses a UTXO model; Ethereum, Base, Arbitrum and BNB Chain use EVM-style accounts; TON has its own account and wallet-contract architecture; TRON has another execution and fee model.
- [3]
A user may see USDT on TON, TRON, Ethereum and BNB Chain and assume the balances are interchangeable; they are not, because each version exists on a specific network and follows that network's rules.
- [4]
Users still need to understand which network an asset belongs to, which address format is used, which gas asset is required, whether a bridge is involved and whether the receiving platform supports that network.
- [5]
The wallet UI can simplify these steps, but it cannot remove the underlying blockchain boundaries.
- [6]
The post says wallet migration should be treated as a key-management operation, not a normal app upgrade.
- [7]
The post's safer process for existing users: keep the original wallet accessible, add the existing TON wallet using the correct wallet type, verify the recovered address, check it against a block explorer, create a separate multichain wallet if needed, transfer a small test amount, verify receipt, and only then move larger balances; do not delete the original wallet until the new setup is verified.
- [8]
Keeper's seven networks fall into four models: EVM-style accounts (four networks), UTXO (Bitcoin), TON and TRON.
- [9]
The four networks in the post's USDT example (TON, TRON, Ethereum, BNB Chain) sit on three models, because Ethereum and BNB Chain share the EVM account model.
- [10]
Keeper's documentation, as described in the post, explains that the older TON-only wallet and the new multichain wallet can use different derivation paths.
- [11]
Wallet software combines the recovery phrase with a derivation scheme to generate private keys and addresses: seed phrase, derivation path, private key, blockchain address. Change the derivation path and the resulting address can change too.
- [12]
A recovery phrase imported into the wrong wallet structure may produce an address the user has never seen before; the original funds have not necessarily disappeared and the wallet may simply be deriving a different key.
- [13]
Tonkeeper has been rebranded as Keeper and now supports seven networks: TON, TRON, Ethereum, Bitcoin, Arbitrum, Base and BNB Chain.
- [14]
Keeper remains self-custodial and has no traditional password-reset mechanism; if a user loses both the device and the recovery phrase, the wallet provider cannot recreate the private keys.
Sources
1 independent publisher whose own reporting we read for this story.
- dev.toTonkeeper Is Now Keeper: What the Multichain Shift Means for Wallet Architecture
1 article · October 11, 2026
Topics and entities
Follow any of these and your For You feed starts watching them — no settings page required.
Topics
- Multichain walletsFollow
- Self-custodyFollow
- Wallet key derivationFollow