Doors Left Ajar: A Calm Audit of Dormant Wallet Permissions
Photo: The White House, Public domain, via Wikimedia Commons
Most holders can remember the last trade they made. Far fewer can name the last application they gave permission to move their tokens. That gap is not carelessness so much as arithmetic: each interaction adds a small, forgettable grant, and the grants do not expire simply because the browser tab did.
For UK holders of Solace-related assets, this is worth an hour of quiet attention once or twice a year. Not because something has gone wrong, but because permissions are the sort of housekeeping that only becomes urgent when it is already too late.
Two different locks, easily confused
It helps to separate two things that are often discussed as one.
A wallet connection is a handshake. You allow a site to see your address and request signatures. It is a doorbell, not a key, though a persistent connection makes it easier for a convincing site to ask for more.
A token approval or allowance is the key itself. You authorise a smart contract to move a specified amount of a token, sometimes an unlimited amount, on your behalf. This is what makes swaps and liquidity actions possible without a fresh signature each time.
The second is the one that deserves the calendar entry. Connection lists are tidier and more visible; allowances are quieter and more consequential.
Why the ledger fills up
Approvals accumulate for entirely ordinary reasons. A decentralised exchange you used once in a hurry. A bridge that seemed necessary during a busy week. An airdrop claim page reached through a link someone posted in a group chat. Each is a legitimate interaction at the time.
They also accumulate because revoking costs gas on most networks, so there is a natural reluctance to tidy up after every session. Over two or three years, a patient holder can end up with a dozen or more standing allowances across several addresses, several of which they have half-forgotten.
None of this is a scandal. It is simply how the tooling works, and knowing that is the first step towards handling it calmly.
A routine you can repeat
Set aside a quiet half hour. No price charts open. The aim is a list, not a decision.
- Inventory your addresses. Write down every wallet you have used for Solace-related activity, including the ones you think are empty. Empty wallets with live approvals are common.
- Check connections first. Most wallets expose a 'connected sites' screen. Remove anything you do not recognise or no longer use. This is free and reversible.
- Review allowances on a block explorer. Look up each address and read the token approval list. Note the token, the spender contract and whether the allowance is capped or unlimited.
- Sort into three piles. Keep, revoke, and investigate. The third pile should be small; if it is not, that itself is a finding.
- Revoke deliberately, one at a time. Use a reputable revocation tool, check the contract address it asks you to approve, and confirm the network. Rushing here defeats the purpose.
- Record the date. A short note in your records file saying what you reviewed and what you changed. Future you will be grateful.
What UK phishing actually looks like
The reason this matters is not hypothetical. UK investors are routinely targeted through channels that borrow the language of customer service: a direct message offering to 'help with a stuck transaction', a spoofed domain a letter or two away from the real one, an advertisement placed above a search result, a fake support form that asks for a seed phrase under the guise of verification.
The Financial Conduct Authority has repeatedly warned that crypto promotions and unsolicited approaches are a common route to loss, and the pattern is consistent: the approach is helpful, timely and just plausible enough. A live, unlimited allowance to a contract you do not remember approving is precisely the sort of loose thread such approaches are designed to find.
Revoking is therefore not a response to an incident. It is the equivalent of checking that the back gate is latched.
Revoking without drama
A few practical notes for the cautious.
- Revoke from a device you trust, ideally one that is not your everyday browsing machine.
- Where you hold significant value, consider a hardware wallet and keep the address used for experiments separate from the address used for long-term storage.
- Do not revoke everything in a single sitting if you are unsure what a contract does. Investigate the unfamiliar ones first.
- Expect to pay network fees, and treat that cost as part of maintenance rather than a loss.
- Never accept unsolicited help with the process. No legitimate support channel will ask for a seed phrase or remote access.
A standing appointment, not a scare
The useful mindset is administrative. Diarise a permissions review for the same week each year, alongside your other financial housekeeping, and again after any period of unusually high activity, such as an airdrop season or a governance vote that required signing.
Solace, as a brand, leans on the idea of quiet. There is something fitting in extending that to security: fewer open doors, fewer things to remember, and a smaller surface for anyone with unhelpful intentions. The work is dull, brief and unglamorous, which is exactly why it tends to get done only when it is scheduled.