On April 22, 2024, SSP Wallet v1.4.0 brings a per-chain address book into the wallet — and keeps it deliberately on your device. Contacts can be created and managed for each supported chain, sending to a saved name becomes as fluid as sending to one of your other wallets, and a new contact is captured automatically the first time you send to an unfamiliar address. There is no contacts server. There is no sync. Restoring SSP on a fresh device gives you back your funds, not your address book — and that is the intended posture.
TL;DR
- SSP Wallet v1.4.0 introduces Contacts, organised per chain.
- Sending to a saved contact is as easy as sending to one of your own wallets.
- The first send to a new address auto-creates a contact entry for next time.
- Contacts are local-only: never uploaded, never synced, never shared with any server.
- A wallet restore does NOT restore contacts — export your list yourself if you want portability.
How contacts work in SSP
Each chain in SSP keeps its own address book. A Bitcoin contact lives next to your Bitcoin balances; a Flux contact lives next to your Flux balances. The split is deliberate: address formats and chain semantics differ enough that pooling them would invite mistakes, and the per-chain view lets the send screen present only the contacts that are valid destinations for the asset you are about to move. Names are short labels you choose; nothing about a contact entry leaves the device.
Sending is the part that gets visibly faster. The send screen offers your saved contacts and your own other wallets in the same picker, so paying a regular counterparty becomes a two-tap operation rather than a copy-paste-from-elsewhere ritual. The first time you send to an address you have not used before, SSP captures it as a draft contact you can name and keep — or ignore, in which case it simply ages out as the list grows. Either way the cognitive load of remembering long strings drops to zero.
Why they're local-only
SSP is fully self-custody: keys live on your devices, never on an SSP server, and the wallet's correctness does not depend on anyone else staying online. Contacts inherit that posture. A synced address book is, in security terms, a high-signal record of who you transact with — exactly the metadata an attacker would target if it ever existed in a central place. SSP simply declines to create that target. The list is on your device because that is the only place it needs to be.
This is the same trade that runs through the rest of the wallet. The academy primer on what self-custody actually means walks through why "no server holds your data" is a security guarantee, not a missing feature. Contacts is the address-book version of the same principle.
Restore caveat
Because contacts never leave the device, they are not part of what an SSP restore brings back. A user who restores SSP on a new device will recover their funds, their multisig posture, and their identity — but the address book they built up over months of use will start empty on the new device. This is the explicit cost of keeping contacts local-only. The mitigation, for users who want portability, is to export the list themselves and re-import it on the new device. Treat the contacts list the way you would treat a notes file: something you keep your own copy of if it matters to you.
What's next
Manual export is a known rough edge, and a contacts CSV export is on the roadmap for v1.8.0 — designed to keep the same local-only posture while making it trivial to move the list between devices on your own terms. For v1.4.0 the focus is the address book itself: per-chain, local, and immediately useful the next time you open the send screen.
Source: SSP Wallet v1.4.0 release notes.