Crypto Without Internet
SOSWallet enables easy cryptocurrency transfers via SMS. Bridge the connectivity gap with secure, accessible transactions for everyone, everywhere.
SMS Native
No Internet
Instant
Simple SMS-based crypto transfers
Why SOSWallet
Cryptocurrency accessibility for everyone, everywhere, regardless of connectivity.
SMS-Based Transfers
Send and receive cryptocurrency using only SMS. No app download required for recipients.
Offline Transactions
Bridge connectivity gaps in low-connectivity regions. Transactions settle asynchronously.
Secure & Simple
Military-grade encryption for SMS messages. Simple verification codes for confirmations.
Universal Access
Works on any phone with SMS capability. No smartphone or internet needed.
How It Works
Send crypto via SMS in three simple steps. No internet required.
Send SMS
Text your transfer to the SOSWallet number. Example: 'send alice 100 USDC'
- Simple format
- No app needed
- Works offline
Confirm & Queue
Receive verification code via SMS. Reply to confirm your transfer securely.
Settlement
Transaction settles on-chain when connectivity returns. Recipient notified via SMS.
Secure SMS Transfers
Capture and sign transactions for seamless offline crypto transfers
What is Secure SMS Transfers?
Send and receive cryptocurrency securely via SMS, even without internet connection. Sign transactions offline and submit them whenever you're back online.
How It Works
- 1. Create transaction details
- 2. Generate EIP-191 message
- 3. Sign with your wallet
- 4. Submit to EVVM network
MATE Integrated Transfer Hub
Send crypto via SMS or dApp. Powered by MATE Protocol async execution.
Send via SMS
Format: send [recipient] [amount] [token]
SMS is queued and executed async with MATE Protocol
MATE Staking
MATE NameService
Async Nonces
Non-blocking transaction execution with async nonce management for offline scenarios.
x402 Executors
Distributed executor network ensuring reliable transaction settlement at scale.
SMS-Enabled
Send transactions directly via SMS with MATE-powered async execution.
Built for Trust & Accessibility
SOSWallet prioritizes security and accessibility. Your funds are always under your control, powered by MATE Protocol.
Security Architecture
End-to-End Encryption
All SMS messages are encrypted. Your private keys never leave your device.
Multi-Factor SMS
Verification codes and confirmation messages protect every transaction.
Offline Security
Transaction signing happens locally. No trust in connectivity required.
Transparent Settlement
All transactions are verifiable on-chain after network connectivity returns.
Non-Custodial
You maintain full control of your assets. SOSWallet never holds your funds.
MATE Async Execution
Powered by MATE Protocol's async nonces - no blocking, non-sequential execution.
Perfect For
Remittances
Send money home via SMS with no internet dependency
Rural Communities
Enable crypto access in low-connectivity areas
Emergency Aid
Distribute aid during connectivity outages via SMS
Financial Inclusion
Empower unbanked populations with basic crypto transfers
SOS Wallet Roadmap 2025
Building the future of async EVM execution and intelligent transaction routing
MATE Testnet Launch
Deploy MATE Protocol on Sepolia with core async nonce functionality
x402 Executor Network
Launch first executor nodes and validator infrastructure
MATE Staking v1
Enable staking mechanisms and reward distribution system
P2P Exchange
Deploy decentralized peer-to-peer token swap functionality
MATE NameService
Launch identity and naming service with reputation system
Mainnet Preparation
Security audit completion and mainnet readiness testing
MATE Mainnet
Production launch on Ethereum and major EVM networks
Cross-Chain Integration
Support for additional EVM networks and bridge protocols
Join SOSWallet + MATE Protocol
Build with us on the future of SMS-native crypto transfers powered by async execution.
Get Updates
Subscribe for SMS transfer improvements and MATE Protocol news.
SOSWallet on MATE Protocol • Sepolia Testnet • 2025
MATE Contracts: EVVM (0xF817...), Staking (0x8eB2...), NameService (0x8038...)