The Spare Key Test: Rehearsing Solace Account Recovery Before You Need It
Photo: hardware wallet notebook house keys and cup of tea on wooden desk, via i.ytimg.com
Recovery plans tend to be written in the same mood as fire drills: quickly, optimistically, then filed away. For most UK holders of a token such as Solace Coin, the plan lives somewhere between a note in a password manager and a vague memory of where the seed phrase was put. That is not carelessness so much as the ordinary result of a plan that has never been tested.
The two-key rule offers a way to test it. It separates the thing that proves who you are from the thing that moves value, keeps the two apart, and then asks a single question once a quarter: if one of them disappeared tonight, what would I actually do?
What the two keys are, and why they should not travel together
The first key is identity: the email address, the password, the authenticator app, the phone number that receives a code. The second is authority over assets: the seed phrase, the hardware wallet, the passphrase that unlocks it.
Most account compromises do not involve breaking either key. They involve one key being used to reach the other. An email inbox is compromised, a password reset follows, and a support channel is then used to talk the holder into revealing a phrase. The two-key rule exists to break that chain. Identity credentials should never be stored in the same place as, or give access to, the asset backup. Neither should be reachable from a single compromised inbox.
Three failures worth rehearsing
A useful drill does not attempt to cover every scenario. Three are enough to expose most weak points.
- Device loss. Your phone or laptop is gone, along with the authenticator app, the email session and the browser bookmarks.
- Second-factor loss. You still have the device but not the code — the authenticator was device-bound and never exported, or the backup codes are where you cannot reach them.
- Inbox lockout. The address you use for exchange and community accounts is no longer accessible, either through password loss or a provider suspension.
Each one is survivable. The question is whether you know the sequence of steps before you are under pressure.
The drill: forty-five quiet minutes
The point of a drill is that it is non-destructive. Nothing in the list below requires you to move funds or type a seed phrase into any device, and you should not do either.
- Sign in to your main exchange or wallet account from a second device you control.
- Locate your backup codes. Confirm they exist, that they are legible, and that they are stored somewhere other than the device you would lose.
- Check which email address and phone number are attached to each account, and confirm you still control both.
- Establish whether your authenticator backs up to a cloud account or is bound to the handset. Write the answer down; most people do not know.
- Confirm you can find the seed backup within two minutes, without opening it and without photographing it.
- Check that at least one other person knows the procedure for a lost device — not the secret itself.
- Re-read the account recovery policy of your main venue and note how long a manual review is quoted to take.
- Record the date in a short log.
Forty-five minutes, once a quarter, is enough. The value is not in the completion but in what the drill reveals: the backup codes in a drawer at a relative's house you can no longer visit, the phone number you changed two years ago, the authenticator on a handset scheduled for trade-in.
Trusted contacts and the social-recovery trade-off
Social recovery — splitting authority among a small group of guardians who can jointly restore access — is a genuinely useful design. It also introduces a different risk: guardians who collude, or a quorum that is easier to pressure than a single well-defended device.
A few principles keep the trade-off manageable. Keep the group small and known to each other. Prefer guardians who hold different kinds of exposure — a family member, a long-standing professional contact — rather than three people from the same circle. Never give one guardian enough information to act alone. And tell each of them, plainly, what they are and are not being asked to do; an uninformed guardian is a liability in a crisis.
For most UK holders with modest positions, the simplest version of the two-key rule is better than an elaborate scheme: one person knows where the backup is kept, and a second knows what it is for. That is enough to prevent an accidental loss without creating a new centre of gravity.
Where support scams enter
Recovery is the moment when the calm surface of any token community is most likely to be tested. Scam operators work the same window as legitimate support: the hours after someone posts that they are locked out.
The patterns are consistent and worth naming.
- Unsolicited contact. Any message that begins in a direct message rather than a public channel is a red flag. Legitimate teams do not open with a DM.
- Validation and synchronisation language. Phrases such as “wallet validation”, “node sync” or “re-authentication portal” are almost always cover for a request to enter a phrase on a website.
- Urgency with a deadline. “Your account will be suspended in two hours” is designed to prevent you from pausing.
- Lookalike domains. A single character apart from the official address, often with a padlock, is the standard trick.
- Screen sharing. Anyone asking to see your screen during a recovery process is asking to see your keys.
- Paid recovery services. A fee up front, followed by a request for the seed phrase, is the whole business model.
The calm question to keep to hand is this: what would a legitimate organisation never need? The answer is your seed phrase, your private keys, and your password in a chat window. No exceptions have yet been documented.
A small log, kept boringly
A recovery log does not need to be elaborate. A single page recording the date of each drill, which device was used, which backup codes were verified, and what was found to be out of date is sufficient. Reviewed annually, it answers the question that matters: is this plan still true, or does it describe an account structure I no longer have?
What good looks like
Good recovery is unremarkable. It does not involve memorised sequences or heroic improvisation. It involves two keys kept apart, a backup that can be found, one other person who knows the procedure, and a habit of checking before the pressure arrives. Tested in a quiet week, the plan usually holds. Where it does not, far better to discover that on a Tuesday evening with the kettle on than at two in the morning with a deadline attached.