Common Issues & Solutions
Overview
This guide covers frequently encountered issues with SSP Wallet based on actual user experiences and known technical limitations. All solutions are based on SSP's actual implementation.
β¬οΈ Upgrading to v2.0.0
Question: "Will updating to v2 make me re-pair or restore my wallet?"
No. Updating SSP Wallet or SSP Key to v2.0.0 in place keeps your wallet, password, pairing, settings, and history exactly as they were. You never need to re-pair or restore from seed because of the update. See What's New in SSP v2.0.0.
Question: "Do I have to update both apps at the same time?"
No. Update in any order β SSP Wallet v2 works with SSP Key v1 and vice versa. Multi-chain batch sync and the pairing verification code activate once both apps are on v2; until then, chains sync one at a time exactly as before.
Question: "Where did the Settings menu go?"
Settings became the Menu tab β the β° icon in the bottom bar. Everything from the old menus is there: language, currency, theme, change password, network configuration, WalletConnect, Address Details, SSP Wallet Details, message signing, and the tutorial. See Navigating SSP Wallet.
Problem: "The verification words on my two devices don't match"
Stop β do not use that pairing. After every sync, both devices derive a 6-word verification code from the synced keys; a mismatch means the sync must not be trusted. Choose "They don't match" in the wallet and re-pair. If it repeats, report it. Details: Pairing Verification Code.
π Device Synchronization Issues
Problem: "Cannot sync SSP Wallet and SSP Key"
SSP's 2-of-2 Architecture Requirements:
Browser extension (SSP Wallet) must sync with mobile app (SSP Key)
Both devices need public key exchange to generate multisig addresses
Synchronization can be done via QR code or manual input
Solutions:
One-Tap Sync (both apps on v2)
SSP Wallet: Request the sync (pairing screen or chain activation) β the request is delivered to your paired SSP Key through the relay
SSP Key: Review the request and slide to approve β a batch request activates several chains with one approval
Verify: Both devices show the same 6-word verification code and the same wallet addresses
QR Code Sync Method
SSP Wallet: Display QR code during sync process
SSP Key: Use "Scan Code" to scan the QR code
Verify: Both devices show the same verification code (v2) and same wallet addresses after sync
Manual Input Method
SSP Wallet: Open the chain's Sync with SSP Key view (in SSP Wallet Details) and copy the sync data β it has the form
chain:xpub(the same value encoded in the sync QR code).SSP Key: On the sync screen, tap Manual Input and paste the copied wallet sync data (or use Scan Code to scan the wallet's QR instead).
The SSP Key builds the 2-of-2 multisig from the wallet's key and posts its own public key back through the relay; the SSP Wallet completes the sync automatically once it verifies the derived address matches.
Verify both devices show the same addresses. Repeat per chain if any chain is out of sync. (Sync data always flows Wallet β Key; there is no "Export Public Key" option in SSP Key.)
Problem: "Addresses don't match between devices"
Root Cause: Incomplete or failed synchronization
Solution:
Verify both devices completed sync process
Check that both devices show "Connected" or "Synced" status
If addresses differ, repeat synchronization process
Ensure you're viewing the same blockchain network on both devices
π Authentication Issues
Problem: "Cannot unlock SSP Wallet"
Password Recovery:
Click "Restore Wallet" option
Enter your 24-word seed phrase
Set new password
Re-sync with SSP Key
Problem: "Cannot unlock SSP Key"
PIN/Biometric Recovery:
If PIN forgotten: Use seed phrase to restore SSP Key on same or new device
If biometric fails: Use PIN as fallback
Complete recovery: Uninstall/reinstall app and restore from seed phrase
πΈ Transaction Issues
Problem: "Transaction not completing"
SSP's 2-of-2 Requirement:
Every transaction needs approval from BOTH devices
SSP Wallet initiates transaction
SSP Key must approve transaction
Both signatures required for blockchain broadcast
Solutions:
Ensure both devices are online and synced
Check that SSP Key receives transaction notification
Approve transaction on SSP Key mobile app
Wait for blockchain confirmation (varies by network)
Problem: "Transaction stuck or pending"
Blockchain-Level Issues:
Bitcoin: Transaction may be waiting in mempool
Ethereum: May need higher gas fee for faster confirmation
Network congestion can delay confirmations
Solutions:
Wait for network confirmation (can take minutes to hours)
Check transaction status on blockchain explorer
For Ethereum: Some wallets support transaction speed-up (if implemented)
π± Mobile App Issues
Problem: "SSP Key app crashes"
Basic Solutions:
Force close app and restart
Restart mobile device
Update to latest version from app store
If persistent: Uninstall, reinstall, restore from seed
Problem: "Not receiving transaction notifications"
Notification Settings:
Enable notifications for SSP Key in device settings
Ensure app has permission to send notifications
Check that device is not in Do Not Disturb mode
π» Browser Extension Issues
Problem: "SSP Wallet extension not working"
Browser Extension Solutions:
Check extension is enabled in browser settings
Update to latest version
Try disabling other extensions temporarily
Clear browser cache and cookies
If corrupted: Remove extension, reinstall, restore from seed
Problem: "Extension data lost"
Recovery Process:
Click "Restore Wallet" in extension
Enter 24-word seed phrase
Set new password
Re-sync with SSP Key mobile app
π Network Issues
Problem: "Cannot connect to blockchain networks"
Network Connectivity:
SSP Wallet connects to blockchain RPC endpoints
Some networks may have intermittent connectivity
Corporate firewalls may block blockchain connections
Solutions:
Check internet connection
Try different network (mobile data vs WiFi)
Contact IT department if using corporate network
Wait and retry if blockchain network is experiencing issues
π§ Recovery Scenarios
Device Loss Recovery
Lost Computer (SSP Wallet):
Install SSP Wallet on new computer/browser
Restore using wallet seed phrase
Re-sync with existing SSP Key
Lost Mobile Device (SSP Key):
Install SSP Key on new mobile device
Restore using SSP Key seed phrase
Re-sync with existing SSP Wallet
Lost Both Devices:
Need BOTH seed phrases for complete recovery
Install SSP Wallet and restore with wallet seed phrase
Install SSP Key and restore with key seed phrase
Sync both restored devices
Important Recovery Notes
Each device has its own seed phrase
Both seed phrases needed for full wallet recovery
Cannot recover if either seed phrase is lost
Test recovery process with small amounts
π Getting Help
Official Support Channels
Primary Support:
Support Center: sspwallet.io/support - FAQ and guides
Support Tickets: support.runonflux.io - Direct support
Contact Form: sspwallet.io/contact - Message support team
Community Support:
Discord: discord.gg/runonflux - Community help
GitHub Issues: github.com/RunOnFlux/ssp-wallet/issues - Bug reports
Before Contacting Support
Gather This Information:
Device types and operating system versions
SSP Wallet and SSP Key version numbers
Browser type and version (for SSP Wallet)
Exact error messages or screenshots
Steps you took before the issue occurred
Security Issues
Report via: GitHub Security
Critical Issues: Use GitHub's security advisory feature
Prevention Best Practices
Regular Maintenance
Keep both apps updated to latest versions
Verify seed phrase backups are secure and accessible
Test sync functionality periodically
Keep devices charged during transaction operations
Security Best Practices
Store seed phrases securely offline (paper, never digital)
Use strong passwords/PINs on both devices
Never share seed phrases with anyone
Always verify transaction details before approving
Note: This guide focuses on issues specific to SSP Wallet's 2-of-2 multisignature architecture. For general cryptocurrency or blockchain issues, consult respective network documentation.
Last updated