The Retired Handset Protocol: Closing Crypto Access Before a Phone Changes Hands

Replacing a mobile phone is now a routine event, but for a UK crypto user it is also a small security migration. A handset that has held exchange apps, authenticator codes, exchange emails and wallet shortcuts is not merely a piece of hardware. It is a bundle of access paths. The aim is not to treat the old device as hostile, but to close each path deliberately before the handset is wiped, sold, recycled or passed to someone else.

As of November 2026, many UK crypto services rely on a phone for login approvals, one-time passcodes, push notifications or passkeys. That makes the handover a useful moment to audit access rather than simply move a SIM card. JaagCoin's suggested approach is calm and sequential: establish the new handset first, then withdraw trust from the old one, then erase it. Doing this in the wrong order can leave a user locked out of an account or, worse, leave an old device able to approve activity.

Start with an access inventory

Before touching either handset, write a short inventory of what the old phone can do. This need not be a technical document. A notebook page or a password-manager note is enough. List the crypto exchange apps, self-custody wallet apps, authenticator apps, email accounts, password managers, banking apps and any browser shortcuts that lead to financial services.

Then add the less obvious items: saved withdrawal addresses in exchange apps, address books in wallet apps, recovery codes stored in notes or photos, SMS passcodes, voicemail access, cloud backups and passkeys tied to the device. The inventory is not a list of secrets. It is a list of doors. The point is to know which doors must be closed or transferred before the old handset leaves your possession.

Make the new handset operational first

A common mistake is to wipe the old phone before the new one is fully working. That can interrupt two-factor authentication at exactly the wrong moment. Set up the new handset first. Install the crypto apps you still use, sign in, and confirm that login approvals and one-time codes arrive as expected. Check that email works, that the authenticator app is present, and that any passkey or device-based approval has been registered.

If you are moving a SIM or eSIM, confirm that calls and texts reach the new device before relying on SMS codes. Test a small, low-risk action if the service allows it, such as viewing a balance or opening a withdrawal settings page without submitting a transaction. The old handset should remain available until the new one has passed these checks. Only then should the old device be treated as surplus.

Withdraw trust from the old device

Many exchanges and brokers maintain a list of trusted devices or active sessions. Sign in to each relevant account, preferably from the new handset or a secure browser, and review that list. Remove the old phone, revoke sessions you do not recognise, and sign out of sessions that are no longer needed. If the service offers a 'log out of all devices' option, consider using it after the new handset is confirmed working.

This is also a sensible moment to review app-specific passwords and connected applications. Email is particularly important because it is often the reset channel for crypto accounts. Revoke old mail sessions, check forwarding rules, and confirm that recovery addresses and phone numbers are still correct. A phone handover is not a reason to change every password in a panic, but it is a good reason to review who and what still has access.

Authenticator codes need a planned migration

Authenticator apps require care. Some allow export or migration within the app; others rely on cloud backup or a recovery key. Follow the app's own guidance and avoid moving codes by photographing a screen or storing screenshots in a camera roll. If the authenticator offers recovery codes, keep them offline and separate from the phone. Do not rely solely on SMS as a fallback, because SIM swaps and number porting can affect text-based codes.

Before wiping the old phone, confirm that the authenticator on the new handset generates valid codes for at least one account. Then check a second account if you have one. A single successful code is useful, but two confirmations are better. If a service requires re-enrolment, complete it while the old device is still available in case a confirmation prompt appears there.

Review saved withdrawal addresses and shortcuts

Saved withdrawal addresses deserve their own pass. On an exchange, an address book may be account-level rather than device-level, so removing the old phone does not necessarily remove the saved address. Review the list and delete entries you no longer recognise or use. Re-add any legitimate address deliberately on the new device, checking the first and last characters and, where possible, using a small test transfer before a larger one.

Browser shortcuts and home-screen icons are not keys in themselves, but they can lead to accounts that remain signed in. Clear saved passwords and autofill data from the old phone's browser only after confirming they exist in your password manager. Remove wallet shortcuts that could be mistaken for active wallets. A shortcut is a convenience; it should not become a misleading route into an account.

Self-custody wallets: the seed phrase is the real key

For self-custody wallets, deleting an app does not revoke access to the wallet. The seed phrase or recovery phrase is the access. If the old phone holds a seed phrase in notes, photos, messages or cloud backups, remove those copies carefully and confirm that an offline backup exists elsewhere. Restore the wallet on the new handset before wiping the old one, and never enter a seed phrase into an app or website reached through an unsolicited link.

If a hardware wallet is involved, the phone is usually only a companion device. Removing the app does not remove the keys from the hardware wallet, but it may remove convenience settings. Confirm that the hardware wallet still connects and that the recovery backup is intact. The objective is continuity without leaving a second copy of access on a device you no longer control.

Wipe, then verify the handover

Once the new handset works and the old one has been removed from trusted-device lists, sign out of cloud accounts and perform a factory reset. Remove the SIM or eSIM if it is not being transferred. Check the device management settings on the new phone and, if the old handset is being traded in or sold, follow the retailer's or manufacturer's erasure guidance. The National Cyber Security Centre offers general device-reset advice that is useful for UK readers.

Finally, keep a short record of what was changed: which sessions were revoked, which authenticator was migrated, and which addresses were reviewed. Store it away from the phone. A handover is complete not when the old screen goes dark, but when the new handset is proven to work and the old one no longer carries a route into your crypto accounts. That is the quiet point of the exercise: no drama, just fewer doors left open.