Built on the proven SSP Wallet foundation – extending 2-of-2 multisig security to multi-party business coordination
SSP Enterprise transforms the battle-tested SSP Wallet ecosystem into a comprehensive multi-party cryptocurrency management solution for businesses, partnerships, and organizations. While maintaining the core principle of true self-custody, SSP Enterprise adds business-grade coordination features on top of the proven 2-of-2 multisignature architecture that has secured user funds since 2024.
SSP Enterprise extends the revolutionary SSP Wallet ecosystem – a BIP48 true 2-of-2 multisignature crypto wallet that's already securing millions in digital assets – to multi-party business scenarios. Instead of a single user controlling two devices (browser + mobile), SSP Enterprise coordinates multiple parties, each with their own SSP Wallet + SSP Key setup.
The SSP ecosystem consists of three battle-tested components:
Security Track Record: Halborn security audit passed with clean results (March 2025)
Single User with 2-of-2 Multisig Security:
┌─────────────────┐ ┌─────────────────┐
│ SSP Wallet │ │ SSP Key │
│ (Browser Ext) │◄──►│ (Mobile App) │
│ │ │ │
│ • One private │ │ • Second private│
│ key stored │ │ key stored │
│ • Transaction │ │ • Biometric/PIN │
│ construction │ │ confirmation │
│ • BIP48 paths │ │ • Final signing │
└─────────────────┘ └─────────────────┘
│ │
└──── SSP Relay ────────┘
(Communication Only)
✅ Live and securing user funds since 2024
✅ 15+ blockchain networks supported
✅ WalletConnect v2, Account Abstraction (ERC-4337)
✅ Halborn security audit passed (100% issues resolved)
Each Party Uses Their Own SSP Wallet + SSP Key (2-of-2):
┌─────────────────────┐ ┌─────────────────────┐ ┌─────────────────────┐
│ Party A │ │ Party B │ │ Party C │
│ (Uses SSP Wallet │ │ (Uses SSP Wallet │ │ (Uses SSP Wallet │
│ ecosystem) │ │ ecosystem) │ │ ecosystem) │
│ ┌─────────────────┐ │ │ ┌─────────────────┐ │ │ ┌─────────────────┐ │
│ │ SSP Wallet │ │ │ │ SSP Wallet │ │ │ │ SSP Wallet │ │
│ │ (Browser Ext) │ │ │ │ (Browser Ext) │ │ │ │ (Browser Ext) │ │
│ └─────┬───────────┘ │ │ └─────┬───────────┘ │ │ └─────┬───────────┘ │
│ │ │ │ │ │ │ │ │
│ ┌─────┴───────────┐ │ │ ┌─────┴───────────┐ │ │ ┌─────┴───────────┐ │
│ │ SSP Key │ │ │ │ SSP Key │ │ │ │ SSP Key │ │
│ │ (Mobile App) │ │ │ │ (Mobile App) │ │ │ │ (Mobile App) │ │
│ └─────────────────┘ │ │ └─────────────────┘ │ │ └─────────────────┘ │
└─────────────────────┘ └─────────────────────┘ └─────────────────────┘
│ │ │
└──────────────────────────┼──────────────────────────┘
│
┌─────────────────────────────────────────┐
│ SSP Enterprise Platform │
│ (New Business Coordination) │
│ │
│ 🌐 Web portal for business management │
│ 🔗 Multi-party address generation │
│ 📋 Transaction proposal & approval │
│ 🔒 Business policy engine │
│ 📊 Audit trails & compliance reporting │
│ 👥 Role-based access control │
│ 🔄 Integrates with existing SSP infra │
└─────────────────────────────────────────┘
Key Innovation: SSP Enterprise leverages the existing, proven SSP ecosystem. Each business party continues using their familiar SSP Wallet + SSP Key setup, with the Enterprise platform coordinating multi-party decisions on top.
SSP Enterprise maintains the core security principle of never storing private keys or sensitive data, while enabling seamless business coordination:
Data Storage Model:
┌─────────────────────────────────────────────────────────┐
│ SSP Enterprise Data Architecture │
├─────────────────────────────────────────────────────────┤
│ │
│ ❌ NEVER STORED (Remains on user devices): │
│ ├── Private keys (stay in SSP Wallet/Key) │
│ ├── Seed phrases (user-controlled) │
│ ├── Transaction signing data │
│ └── Sensitive authentication tokens │
│ │
│ ✅ COORDINATION DATA (Stored in SSP Relay): │
│ ├── Public keys for address generation │
│ ├── Multi-party wallet addresses │
│ ├── Business policy configurations │
│ ├── Transaction proposals (unsigned) │
│ ├── Approval workflows and status │
│ ├── Audit trails and compliance logs │
│ └── User roles and permissions │
│ │
│ 🔒 SECURITY BENEFITS: │
│ ├── Enables seamless enterprise integration │
│ ├── Facilitates analytics and reporting │
│ ├── Maintains true self-custody principles │
│ └── Zero risk of private key exposure │
└─────────────────────────────────────────────────────────┘
Security Assurance: All stored data is non-sensitive by design. Even if the SSP Enterprise platform were compromised, no private keys or funds would be at risk since all signing operations occur on user-controlled devices.
Each blockchain network has different technical capabilities, requiring tailored approaches:
Structure: 4-of-6 Multisig (Technical Reality)
┌─────────────┐ ┌─────────────┐ ┌─────────────┐
│ Party A │ │ Party B │ │ Party C │
├─────────────┤ ├─────────────┤ ├─────────────┤
│ Wallet A │ │ Wallet B │ │ Wallet C │
│ Key A │ │ Key B │ │ Key C │
└─────────────┘ └─────────────┘ └─────────────┘
Why 4-of-6: Bitcoin's ECDSA cannot combine signatures
Bitcoin Script: OP_4 <WA> <KA> <WB> <KB> <WC> <KC> OP_6 OP_CHECKMULTISIG
Note: Public keys are sorted in redeem script for deterministic address generation
Spending: Any 2 parties provide 4 signatures total
Address Example: 3FKjZ8rLJXhpBPx8r8ycRd5kq3x7fN2m5T (P2SH)
bc1qxy2kgdygjrsqtzq2n0yrf2493p83kkfjhx0wlh (P2WSH)
Structure: 2-of-3 via Schnorr MuSig2
┌─────────────┐ ┌─────────────┐ ┌─────────────┐
│ Party A │ │ Party B │ │ Party C │
│ (Combined) │ │ (Combined) │ │ (Combined) │
└─────────────┘ └─────────────┘ └─────────────┘
Process:
1. Each party combines Wallet + Key internally (MuSig2)
2. Three combined keys create 2-of-3 threshold Schnorr
3. Spending: Any 2 parties create single aggregated signature
Address Example: bc1p5d7rjq7g6rdk2yhzks9sm5p3rczyr5yz2zkt6qgkq (P2TR)
Structure: 2-of-3 Smart Contract
┌─────────────┐ ┌─────────────┐ ┌─────────────┐
│ Party A │ │ Party B │ │ Party C │
│ (Combined) │ │ (Combined) │ │ (Combined) │
└─────────────┘ └─────────────┘ └─────────────┘
Smart Contract Implementation:
contract SSPEnterpriseWallet {
mapping(address => bool) public signers;
uint256 public threshold = 2;
function executeTransaction(
address to,
uint256 value,
bytes memory data,
bytes[] memory signatures
) external {
require(verifySchnorrSignatures(signatures), "Invalid sigs");
require(signatures.length >= threshold, "Insufficient sigs");
// Execute transaction
}
}
Address Example: 0x742d35Cc6671C4e3b8d8B8e9D2f7e2f1A5A5A5A5
SSP Enterprise uses cryptographically separate derivation paths to completely isolate personal and business funds:
Master Seed (Same device, different account numbers)
│
├── Personal Wallets: m/48'/coin'/account'/script_type'/0/address_index
│ ├── Primary Personal: m/48'/0'/0'/2'/0/0 (Bitcoin, account 0)
│ ├── Additional Personal: m/48'/0'/1'/2'/0/0 (Bitcoin, account 1)
│ └── Reserved: accounts 0-99 for personal use
│
└── Business Wallets: m/48'/coin'/account'/script_type'/0/address_index
├── Company A: m/48'/0'/100'/2'/0/0 (Bitcoin, account 100)
├── Company B: m/48'/0'/524'/2'/0/0 (Bitcoin, account 524)
├── Company C: m/48'/0'/7500'/2'/0/0 (Bitcoin, account 7500)
└── Available: accounts 100-99999 for business use
| Aspect | Personal Keys | Business Keys | Isolation Benefit |
|---|---|---|---|
| Derivation Path | account = 0-99 |
account = 100-99999 |
Cryptographically separate |
| Address Space | Individual control | Multi-party control | Cannot cross-contaminate |
| Transaction History | Private | Business compliance | Clear audit separation |
| Backup/Recovery | Personal seed phrase | Same seed, different account | Unified backup, separate access |
| Tax Reporting | Personal transactions | Business transactions | Automatic categorization |
| Account Selection | Fixed personal accounts | User-chosen 3-digit number | Easy to remember and manage |
// Bitcoin Personal (existing SSP)
const personalPath = "m/48'/0'/0'/2'/0/0"; // account=0 (primary personal)
// Bitcoin Additional Personal
const personalPath2 = "m/48'/0'/15'/2'/0/0"; // account=15 (additional personal)
// Bitcoin Business Accounts (user-chosen 3-digit numbers)
const companyA = "m/48'/0'/100'/2'/0/0"; // account=100 (Company A)
const companyB = "m/48'/0'/524'/2'/0/0"; // account=524 (Company B)
const companyC = "m/48'/0'/7500'/2'/0/0"; // account=7500 (Company C)
// Ethereum Examples
const ethPersonal = "m/48'/60'/0'/0'/0/0"; // Personal Ethereum
const ethBusiness = "m/48'/60'/250'/0'/0/0"; // Business Ethereum (account 250)
// Account Range Summary:
// 0-99: Reserved for personal wallets
// 100-99999: Available for business wallets (user selects memorable unique number)
SSP Enterprise inherits native support for 15+ blockchain networks from the proven SSP Wallet ecosystem:
| Network | Current SSP Support | Enterprise Structure | Key Advantages |
|---|---|---|---|
| Bitcoin | ✅ P2SH, P2WSH | 4-of-6 multisig | Universal compatibility, mature tooling |
| Litecoin | ✅ Native support | 4-of-6 multisig | Fast confirmations, low fees |
| Dogecoin | ✅ Native support | 4-of-6 multisig | High liquidity, community adoption |
| Bitcoin Cash | ✅ Native support | 4-of-6 multisig | Fast transactions, low fees |
| Ravencoin | ✅ Native support | 4-of-6 multisig | Asset tokenization, community-driven |
| Zcash | ✅ Native support | 4-of-6 multisig | Privacy features, shielded transactions |
| Flux | ✅ Native integration | 4-of-6 multisig | Cloud computing blockchain |
| Network | Current SSP Support | Enterprise Structure | Key Advantages |
|---|---|---|---|
| Ethereum | ✅ ERC-4337 Account Abstraction | 2-of-3 smart contract | Gasless transactions, DeFi integration |
| Polygon | ✅ Full support | 2-of-3 smart contract | Ultra-low fees, fast finality |
| BSC | ✅ Full support | 2-of-3 smart contract | High throughput, low cost |
| Base | ✅ Full support | 2-of-3 smart contract | Coinbase backing, L2 efficiency |
| Avalanche | ✅ Full support | 2-of-3 smart contract | Sub-second finality |
Total Supported Networks: 15+ with ongoing expansion
Fireblocks (Custodial MPC)
Trust Model: Company holds 2 of 3 MPC key shares
┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐
│ Key Share 1 │ │ Key Share 2 │ │ Key Share 3 │
│ (Fireblocks) │ │ (Fireblocks) │ │ (Customer) │
│ Intel SGX │ │ Intel SGX │ │ Customer Device │
│ AWS Cloud │ │ Google Cloud │ │ │
└─────────────────┘ └─────────────────┘ └─────────────────┘
Assets: 120+ blockchains
Pricing: $100,000-1,000,000+ annually
Reality: NOT self-custody - customer only controls 1/3 of keys
BitGo (Custodial + Self-Custody Options)
Trust Model: Company holds 1 of 3 keys as co-signer
Assets: 1,100+ digital assets supported
Pricing: Enterprise-grade, custom pricing
Features: Regulated custody, insurance up to $250M
Target: Institutional investors, 1,500+ institutions use it
Reality: Hybrid model - still requires trust in BitGo
Safe (formerly Gnosis Safe) - EVM Only
Technology: Smart contract multisig on Ethereum + EVM chains
Assets: Ethereum, USDC, USDT + all ERC-20 tokens, 14 EVM chains
Pricing: Free to use (pay gas fees only)
Users: Manages $100B+ in assets, used by Vitalik Buterin
Limitations: EVM chains only - no Bitcoin, no UTXO chains
Setup: Technical knowledge required, web-based interface
Casa - Hybrid Custody (NOT Full Self-Custody)
Technology: Proprietary service with Casa holding 1 key in multisig
Assets: Bitcoin (primary), Ethereum, USDC, USDT (limited)
Pricing: $250/year (3-key), $2,100/year (5-key premium) + KYC required
Setup: Casa holds 1 key, user holds majority (but not full self-custody)
Target: Individuals comfortable with trusted third party
Limitations: Not open source, Casa dependency, limited multi-chain support
Specter Desktop - Bitcoin Only
Technology: Desktop GUI for Bitcoin Core with hardware wallet support
Assets: Bitcoin ONLY (no multi-chain support)
Pricing: Free and open source
Setup: Requires Bitcoin Core + 1-2TB storage + technical expertise
Target: Bitcoin maximalists and technical users
Limitations: Bitcoin-only, extremely cumbersome setup, 350GB+ storage requirements
Nunchuk - Bitcoin Privacy-Focused
Technology: Bitcoin multisig with privacy focus (no KYC)
Assets: Bitcoin only
Pricing: Subscription model
Setup: Hardware wallet integration (Ledger, Trezor, COLDCARD)
Target: Privacy-conscious Bitcoin users
Limitations: Bitcoin-only, subscription fees, limited business features
TotalSig - Multi-Chain MPC
Technology: MPC technology (not true blockchain multisig)
Assets: Bitcoin, Ethereum, Polygon, Avalanche, BSC, 10+ chains
Pricing: Subscription model
Setup: Software-based MPC solution
Target: Multi-chain users seeking convenience
Limitations: Not true multisig, proprietary technology, subscription cost
| Feature | Fireblocks | BitGo | Safe | Casa | Specter | Nunchuk | TotalSig | SSP Enterprise |
|---|---|---|---|---|---|---|---|---|
| True Self-Custody | ❌ Custodial MPC | ⚠️ Hybrid | ✅ Yes | ❌ Casa holds key | ✅ Yes | ✅ Yes | ❌ MPC technology | ✅ Complete |
| Multi-Chain Native | ✅ 120+ chains | ✅ 1,100+ assets | ❌ EVM only | ❌ BTC + limited ETH | ❌ Bitcoin only | ❌ Bitcoin only | ✅ 10+ chains | ✅ 15+ chains |
| Business Features | ✅ Full enterprise | ✅ Institutional | ⚠️ Basic DAO tools | ❌ Consumer focus | ❌ None | ❌ None | ⚠️ Basic | ✅ Purpose-built |
| Dual-Device Workflow | ⚠️ Custom app | ⚠️ Enterprise app | ❌ Web only | ✅ Mobile app | ❌ Desktop only | ⚠️ Mobile limited | ✅ Mobile app | ✅ Desktop + Mobile |
| Setup Complexity | ⚠️ 4-8 weeks | ⚠️ Enterprise sales | ⚠️ Technical | ⚠️ Guided setup | ❌ Very technical | ⚠️ Hardware setup | ⚠️ Technical | ✅ 1-hour ceremony |
| Annual Cost | $100K-1M+ | $50K-500K+ | $0 (gas only) | $250-2,100 | $0 | Subscription | Subscription | ✅ Free* |
| Blockchain Multisig | ❌ MPC only | ⚠️ Hybrid | ✅ Smart contract | ⚠️ Hybrid | ✅ Native Bitcoin | ✅ Native Bitcoin | ❌ MPC only | ✅ Native + Smart Contract |
| Security Audited | ⚠️ Enterprise only | ⚠️ Enterprise only | ✅ Multiple audits | ❌ Proprietary | ⚠️ Limited | ❌ Unknown | ❌ Unknown | ✅ Halborn audited |
| Open Source | ❌ Proprietary | ❌ Proprietary | ✅ Core contracts | ❌ Proprietary | ✅ Fully open | ⚠️ Partial | ❌ Proprietary | ✅ Full stack |
| Target Market | Large enterprise | Institutions | DeFi/DAOs | Bitcoin users | Bitcoin maximalists | Bitcoin privacy | Multi-chain users | Universal |
| Organization Size | Fireblocks | BitGo | Safe | Casa | Specter | Nunchuk | TotalSig | SSP Enterprise |
|---|---|---|---|---|---|---|---|---|
| Small (3 parties, $1M AUC) | $300,000+ | $150,000+ | $3,000¹ | $750² | $0³ | $600⁴ | $1,200⁵ | Free⁷ |
| Medium (5 parties, $10M AUC) | $750,000+ | $400,000+ | $15,000¹ | $6,300² | $0³ | $3,000⁴ | $6,000⁵ | $0-36,000⁶ |
| Large (10 parties, $100M AUC) | $2,000,000+ | $1,200,000+ | $75,000¹ | N/A | $0³ | $12,000⁴ | $24,000⁵ | $0-360,000⁶ |
Core Platform: FREE (Open Source)
├── Multi-party wallet creation and management
├── Transaction coordination and signing
├── Basic audit trails and reporting
├── Cross-chain address generation
└── Community support
Premium Features: Subscription-Based (AUM-Dependent)
├── Advanced Analytics & Insights
├── Enhanced Compliance Reporting
├── Premium Support & SLA
├── Advanced Policy Engine
├── Integration APIs & Webhooks
└── White-label Customization
Built-in Revenue Features: Transaction-Based
├── Fiat on-boarding (credit card to crypto)
├── Fiat off-boarding (crypto to bank account)
├── Cryptocurrency swapping engine
└── Competitive rates with enterprise volume discounts
Pricing Tiers:
├── Starter: $0/month (Core features only)
├── Professional: 0.3% annually on AUM ($25 minimum)
├── Enterprise: 0.36% annually on AUM + premium features
└── Self-Hosted: Free core + premium feature licenses
Pricing Sources & Methodology:
Enterprise Custody Verification:
Transparency Note: Many enterprise providers use "contact sales" pricing, making exact comparisons difficult. Estimates based on publicly available documentation where possible.
✅ Complete Self-Custody + Multi-Chain
Market Reality:
├── Fireblocks/BitGo: Multi-chain but custodial (not self-custody)
├── Safe: Self-custody but EVM-only (no Bitcoin)
├── Casa: NOT self-custody (Casa holds keys) + limited chains
├── Specter: Self-custody but Bitcoin-only + extremely technical
├── Nunchuk: Self-custody but Bitcoin-only + subscription fees
├── TotalSig: NOT true multisig (MPC) + subscription costs
└── SSP Enterprise: TRUE self-custody + 15+ chains + Free*
✅ Blockchain-Level Enforced Multisig + Business Features
Technology Reality:
├── Fireblocks/BitGo/TotalSig: MPC (not true blockchain multisig)
├── Safe: True smart contract multisig but EVM-only
├── Casa: Hybrid approach with trusted third party
├── Specter/Nunchuk: True Bitcoin multisig but no business features
└── SSP Enterprise: True multisig (Bitcoin native + EVM smart contracts) + business coordination
✅ Open Source + Security Audited + Free
Transparency & Cost Reality:
├── Fireblocks/BitGo/Casa/TotalSig: Proprietary + expensive
├── Safe: Open source + audited but limited chains
├── Specter: Open source + free but Bitcoin-only + complex setup
├── Nunchuk: Partially open + subscription costs
└── SSP Enterprise: Fully open source + Halborn audited + Free* core platform
✅ Mobile-Native + Enterprise-Ready
User Experience Reality:
├── Fireblocks/BitGo: Enterprise complexity, weeks to setup
├── Safe: Web-only interface, technical setup
├── Specter: Desktop-only, requires Bitcoin Core + 1-2TB storage
├── Casa: Mobile but NOT self-custody + limited business features
├── Nunchuk: Mobile but Bitcoin-only + no business features
└── SSP Enterprise: Desktop + Mobile coordination + business features + 1-hour setup
┌─────────────────────────────────────────────────────────────┐
│ Enterprise Security Stack │
├─────────────────────────────────────────────────────────────┤
│ Layer 5: Regulatory & Compliance │
│ • Immutable blockchain audit trails │
│ • Multi-jurisdictional compliance support │
│ • Real-time transaction monitoring │
│ • Customizable reporting and documentation │
├─────────────────────────────────────────────────────────────┤
│ Layer 4: Business Policy Engine │
│ • Configurable spending limits and approval workflows │
│ • Role-based access control (Admin, Signer, Observer) │
│ • Time-based restrictions and emergency procedures │
│ • Integration with enterprise identity systems │
│ • Note: UI-enforced policies (true self-custody allows │
│ bypassing via custom UI implementations) │
├─────────────────────────────────────────────────────────────┤
│ Layer 3: Blockchain Security │
│ • Native multisig verification (Bitcoin 4-of-6) │
│ • Smart contract enforcement (EVM 2-of-3) │
│ • Immutable transaction finality │
│ • Network consensus validation │
├─────────────────────────────────────────────────────────────┤
│ Layer 2: SSP Wallet 2FA (Proven in Production) │
│ • Dual-device requirement per party │
│ • BIP48 hierarchical deterministic key derivation │
│ • Device-specific encryption and authentication │
│ • Separation of signing and coordination │
├─────────────────────────────────────────────────────────────┤
│ Layer 1: Device-Level Protection │
│ • Operating system security and updates │
│ • Hardware security module utilization │
│ • Biometric and PIN-based authentication │
│ • Secure enclave and keychain integration │
└─────────────────────────────────────────────────────────────┘
| Attack Type | Traditional Multisig | Fireblocks MPC | SSP Enterprise | Mitigation Strategy |
|---|---|---|---|---|
| Device Compromise | ⚠️ Single point failure | ✅ MPC protection | ✅ Multi-party + 2FA | Requires 2+ parties AND 2FA |
| Insider Threat | ❌ Full access if admin | ⚠️ Fireblocks trust | ✅ Threshold enforcement | Cannot act alone |
| Social Engineering | ⚠️ Target key holders | ⚠️ Target Fireblocks | ✅ Multi-party verification | No single point of control |
| Malware/Phishing | ❌ Can steal keys | ⚠️ Can affect shares | ✅ 2FA protection | Mobile confirmation required |
| Physical Coercion | ❌ Force signing | ⚠️ Force Fireblocks | ✅ Distributed parties | Geographic distribution |
| Vendor Failure | ✅ No vendor | ❌ Fireblocks bankruptcy | ✅ No vendor dependency | Self-sovereign architecture |
| Regulatory Seizure | ✅ Individual action | ❌ Fireblocks compliance | ✅ Individual responsibility | Cannot be collectively seized |
| Key Loss/Recovery | ⚠️ Complex recovery | ⚠️ Vendor dependent | ✅ Standard BIP48 | Industry-standard recovery |
While SSP Enterprise's core functionality relies on the proven software-based SSP ecosystem, future hardware integration will provide additional security layers for enterprise deployments.
Current SSP Security Model (Software-Based):
┌─────────────────────────────────────────────────────────┐
│ Proven Security Features │
├─────────────────────────────────────────────────────────┤
│ │
│ Device-Level Protection: │
│ ├── Mobile biometric authentication (SSP Key) │
│ ├── Browser extension secure storage │
│ ├── Device-specific encryption keys │
│ └── PIN/password protection layers │
│ │
│ Cryptographic Security: │
│ ├── BIP48 hierarchical deterministic keys │
│ ├── AES-GCM encryption with PBKDF2 │
│ ├── Device fingerprinting for secondary encryption │
│ └── Zero server-side key storage │
│ │
│ Audit & Compliance: │
│ ├── Halborn security audit passed (March 2025) │
│ ├── Enterprise coordination data model │
│ ├── Open source transparency │
│ └── Mathematical proof of security model │
└─────────────────────────────────────────────────────────┘
Level 1: FIDO2 Authentication Enhancement (Planned 2026)
Current SSP + Hardware Token:
├── Hardware key authenticates wallet access
├── Seed phrase remains in secure device storage
├── Signing operations in SSP Wallet/Key apps
├── Additional physical security layer
└── Enterprise compliance improvement
Level 2: Encrypted Seed Storage (Recommended - Target 2027)
Hardware-Encrypted Storage (Sweet Spot):
├── Seed phrase encrypted and stored on hardware key
├── PIN/biometric required for seed decryption
├── Seed temporarily transmitted to SSP Wallet/Key for signing
├── Memory cleared immediately after transaction
├── Hardware tamper resistance protects encrypted seed
└── Signing still occurs in familiar SSP apps
Level 3: Hardware-Only Operations (Future - 2028+)
Pure Hardware Signing (Maximum Security):
├── Seed never leaves hardware security key
├── Signing operations performed entirely in hardware
├── Only public keys and signatures transmitted
├── Requires custom hardware development
├── True airgapped security model
└── May be unnecessary for most enterprise use cases
| Hardware Key | Storage Capacity | Enterprise Features | Cost per Key |
|---|---|---|---|
| YubiKey 5 NFC | 25 encrypted credentials | FIDO2, OpenPGP, PIV | $55 |
| YubiKey 5C Nano | 25 encrypted credentials | USB-C, compact form | $60 |
| YubiKey Bio | 25 + biometric | Fingerprint unlock | $85 |
| Nitrokey 3 | 50+ credentials | Open source firmware | $49 |
| SoloKey | Variable | Open hardware/software | $20-40 |
Scenario 1: Executive Team Security
High-Value Asset Protection:
├── Each executive: Personal YubiKey Bio
├── Seed phrases never in device memory
├── Biometric + PIN dual protection
├── Hardware audit logs for compliance
└── Secure backup keys in company vault
Scenario 2: Distributed Team Operations
Multi-Location Security:
├── Standardized YubiKey deployment
├── Central hardware key management
├── Role-based access with different keys
├── Geographic distribution of backup keys
└── Remote attestation capabilities
Scenario 3: Regulatory Compliance
Maximum Security Requirements:
├── Hardware-only signing operations
├── Air-gapped seed storage
├── Physical key ceremonies for setup
├── Multi-party hardware key custody
└── Immutable hardware audit trails
Seed Storage Process:
┌─────────────┐ ┌─────────────┐ ┌─────────────┐
│ Seed │ │ Hardware │ │ Encrypted │
│ Generation │───▶│ Encryption │───▶│ Storage │
│ (BIP39) │ │ (YubiKey) │ │ (Hardware) │
└─────────────┘ └─────────────┘ └─────────────┘
Transaction Signing Process:
┌─────────────┐ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐
│ Transaction │ │ Hardware │ │ In-Hardware │ │ Signature │
│ Request │───▶│ PIN/Bio │───▶│ Signing │───▶│ Return │
│ │ │ Auth │ │ Operation │ │ │
└─────────────┘ └─────────────┘ └─────────────┘ └─────────────┘
vs. Software-Only Storage:
vs. Traditional Hardware Wallets:
Phase 1: FIDO2 Authentication (Q3 2026)
Phase 2: Encrypted Seed Storage (Q1 2027)
Phase 3: Hardware Signing Operations (Q3 2027)
┌─────────────────────────────────────────────────────────┐
│ SSP Enterprise Web Portal │
│ │
│ Step 1: Administrator Initiates Setup │
│ ├── Define business requirements │
│ ├── Set threshold (2-of-3, 3-of-5, etc.) │
│ ├── Configure spending policies │
│ └── Generate secure invitation links │
│ │
│ Step 2: Party Onboarding │
│ ├── Each party connects existing SSP Wallet │
│ ├── Platform verifies SSP Key pairing │
│ ├── Role assignment (Admin, Signer, Observer) │
│ └── Policy acknowledgment and acceptance │
│ │
│ Step 3: Cryptographic Setup │
│ ├── Coordinate public key exchange │
│ ├── Generate multi-chain enterprise addresses │
│ ├── Verify address derivation across parties │
│ └── Create initial funding transactions │
│ │
│ Step 4: Operational Validation │
│ ├── Test transaction workflow │
│ ├── Verify all parties can sign │
│ ├── Confirm policy enforcement │
│ └── Document setup for compliance │
└─────────────────────────────────────────────────────────┘
Transaction Lifecycle: Proposal → Approval → Execution
┌─────────────┐ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐
│ Initiator │ │ Policy │ │ Required │ │ Signature │ │ Blockchain │
│ Proposes │─►│ Engine │─►│ Parties │─►│ Collection │─►│ Execution │
│ Transaction │ │ Evaluation │ │ Approval │ │ & Broadcast │ │ │
└─────────────┘ └─────────────┘ └─────────────┘ └─────────────┘ └─────────────┘
│ │ │ │ │
│ │ ▼ │ │
│ │ ┌─────────────────────┐ │ │
│ │ │ SSP Wallet UI │ │ │
│ │ │ • Review details │ │ │
│ │ │ • Verify recipient │ │ │
│ │ │ • Check policy │ │ │
│ │ │ • Initial approval │ │ │
│ │ └─────────────────────┘ │ │
│ │ │ │ │
│ │ ▼ │ │
│ │ ┌─────────────────────┐ │ │
│ │ │ SSP Key Mobile │ │ │
│ │ │ • Biometric auth │ │ │
│ │ │ • Transaction hash │ │ │
│ │ │ • Final confirmation │ │ │
│ │ └─────────────────────┘ │ │
│ │ │ │ │
└────────────────┼────────────────┼────────────────┼────────────────┘
│ │ │
┌─────────────────────────────────────────────────┐
│ Platform Coordination │
│ • Collect signatures from required parties │
│ • Verify threshold requirements are met │
│ • Validate against business policies │
│ • Construct final transaction │
│ • Submit to blockchain network │
│ • Update audit trail and notify all parties │
└─────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────┐
│ Policy Configuration │
├─────────────────────────────────────────────────────────┤
│ │
│ Spending Limits: │
│ ├── Daily/Monthly transaction limits │
│ ├── Per-party individual limits │
│ ├── Recipient whitelist/blacklist │
│ └── Asset-specific restrictions │
│ │
│ Approval Workflows: │
│ ├── Threshold requirements by amount │
│ ├── Required approvers for specific operations │
│ ├── Time-based restrictions (business hours) │
│ └── Multi-level approval for large transactions │
│ │
│ Risk Management: │
│ ├── Transaction velocity monitoring │
│ ├── Anomaly detection and alerts │
│ ├── Compliance screening integration │
│ └── Emergency freeze procedures │
│ │
│ Audit & Compliance: │
│ ├── Immutable transaction logging │
│ ├── Role-based access tracking │
│ ├── Automated compliance reporting │
│ └── Integration with enterprise systems │
└─────────────────────────────────────────────────────────┘
Open Source Foundation (No Cost):
├── Multi-party wallet setup and management
├── Transaction coordination and signing
├── Cross-chain address generation
├── Basic transaction history and audit trails
├── Community support and documentation
├── Self-hosting capability with full source code
└── Standard compliance reporting
┌─────────────────────────────────────────────────────────┐
│ Premium Analytics Dashboard │
├─────────────────────────────────────────────────────────┤
│ │
│ Asset Intelligence: │
│ ├── Portfolio composition and diversification │
│ ├── Asset performance tracking and ROI analysis │
│ ├── Cross-chain yield optimization recommendations │
│ └── DeFi opportunity detection and risk scoring │
│ │
│ Transaction Analytics: │
│ ├── Spending pattern analysis and behavioral insights │
│ ├── Counterparty risk assessment and scoring │
│ ├── Cost basis tracking and tax optimization │
│ └── Predictive cash flow modeling │
│ │
│ Compliance Intelligence: │
│ ├── Automated regulatory reporting generation │
│ ├── AML/KYC risk screening and monitoring │
│ ├── Multi-jurisdictional compliance tracking │
│ └── Custom audit reports and documentation │
│ │
│ Business Intelligence: │
│ ├── Multi-party activity correlation analysis │
│ ├── Enterprise-grade SLA and support │
│ ├── Custom API integrations and webhooks │
│ └── White-label deployment and customization │
└─────────────────────────────────────────────────────────┘
Revenue Model Strategy:
├── Core Platform: Free (drives adoption)
├── Analytics Premium: 0.3% annually on AUM
├── Enterprise Features: 0.36% annually on AUM
├── Professional Services: Custom pricing
├── White-label Licensing: One-time + revenue share
└── Self-Hosted Premium: Feature licensing model
Value Proposition:
├── 10-50x cheaper than custodial alternatives
├── Transparent pricing based on asset value
├── No transaction limits or hidden fees
├── Pay only for premium features you use
└── Full self-hosting option available
Challenge: Multi-signature approval for company funds without giving up custody
Setup: CEO + CFO + Board Member (2-of-3)
Benefits:
✅ No single person can access funds
✅ Board oversight on major expenditures
✅ Fast mobile approval for routine payments
✅ Complete audit trail for compliance
✅ Cross-chain treasury management
Example: $50M company treasury
- Daily operations: CEO + CFO approval
- Major investments: CEO + Board Member
- Emergency procedures: Any 2 parties
Challenge: Shared control of partnership funds with clear accountability
Setup: Partner A + Partner B + Neutral Party (2-of-3)
Benefits:
✅ Equal control prevents disputes
✅ Neutral arbitrator for conflicts
✅ Transparent fund management
✅ Easy dissolution procedures
Example: Real estate investment partnership
- Property purchases: Both partners agree
- Management expenses: Either partner + neutral
- Profit distribution: Automated smart contracts
Challenge: Client escrow accounts with regulatory compliance
Setup: Lawyer + Client + Trust Account Manager (2-of-3)
Benefits:
✅ Client funds protection
✅ Regulatory compliance built-in
✅ Transparent fee structures
✅ Automated trust accounting
Example: Legal escrow for M&A transaction
- Funds release: Lawyer + Client approval
- Fee payment: Any 2 parties
- Compliance reporting: Automatic
Challenge: Decentralized decision making with security
Setup: Multiple fund managers with configurable thresholds
Benefits:
✅ Democratic fund management
✅ Transparent investment decisions
✅ Automated governance integration
✅ Institutional-grade security
Example: Crypto investment fund
- Investment decisions: Majority approval
- Routine operations: Simplified threshold
- Emergency procedures: Admin override
Challenge: Multi-generational wealth management with succession planning
Setup: Parents + Adult Children + Family Office Manager
Benefits:
✅ Gradual wealth transition
✅ Education through participation
✅ Professional oversight
✅ Estate planning integration
Example: $100M family office
- Conservative investments: Any family member + manager
- Major decisions: Multiple family members
- Next generation: Observer roles transitioning to signers
❌ Cannot Change After Creation:
├── Bitcoin: 4-of-6 multisig address is permanent
├── Ethereum: Smart contract threshold is immutable
├── Cannot add/remove signers dynamically
└── Requires new wallet setup for changes
Impact: Less flexible than MPC solutions for growing organizations
Mitigation: Plan threshold carefully during setup
❌ No Automated Payments:
├── Every transaction requires human approval
├── No policy-based automatic execution
├── Cannot schedule recurring payments
└── No algorithmic trading support
Impact: Not suitable for high-frequency operations
Mitigation: Focus on treasury and approval workflows
❌ Technical Constraints:
├── Bitcoin: Must use 4-of-6 (not 2-of-3) due to ECDSA
├── Higher transaction fees for complex multisig
├── Larger transaction sizes on UTXO chains
└── Smart contract risks on EVM chains
Impact: Higher costs and complexity than simple wallets
Mitigation: Costs still lower than custodial solutions
❌ Multi-Party Coordination:
├── All parties must be available for signing
├── Mobile connectivity required for approval
├── Time zone coordination for global teams
└── Potential delays during approval process
Impact: Slower than custodial solutions for urgent transactions
Mitigation: Plan approval workflows and emergency procedures
Better Alternative: Fireblocks
├── High-frequency trading operations
├── Algorithmic treasury management
├── Complex automated payment workflows
├── Dynamic organizational structures
└── Reason: Need automation > self-custody
Better Alternative: Safe (Gnosis Safe)
├── DeFi-focused operations
├── Ethereum/EVM-only asset portfolios
├── DAO governance requirements
├── Web3-native organizations
└── Reason: Safe is free and purpose-built for EVM
Better Alternative: Casa or Specter Desktop
├── Bitcoin maximalist organizations
├── Simple Bitcoin treasury needs
├── No multi-chain requirements
├── Preference for Bitcoin-specific tools
└── Reason: Specialized Bitcoin solutions are simpler
Perfect Fit: No good alternative exists
├── Bitcoin + Ethereum + other chains
├── True self-custody requirements
├── Business approval workflows needed
├── Mobile-friendly operations preferred
└── Reason: Only solution combining all requirements
Prioritizing True Ownership: Complete asset control
├── Organizations requiring genuine asset ownership
├── Regulatory environments favoring transparency
├── Privacy-conscious businesses
├── Institutions mandating direct asset control
└── Reason: Proven self-custody with business features
Budget Alternative To: Fireblocks/BitGo
├── Startups with crypto treasuries
├── SMBs needing multi-party approval
├── Non-profits managing donations
├── Partnerships requiring shared control
└── Reason: 90% cost savings vs enterprise custodial
Building on Proven SSP Infrastructure
🎯 Core Deliverables:
├── SSP Enterprise web portal for business coordination
├── Multi-party address generation (leveraging existing SSP chains)
├── Transaction proposal and approval workflows
├── Integration with existing SSP Wallet/Key ecosystem
├── Business policy engine and spending controls
└── Compliance audit trails and reporting
🔧 Technical Implementation:
├── Extend SSP Relay server for multi-party coordination
├── Deploy enterprise smart contracts on supported EVM chains
├── Implement BIP48 business account derivation paths (accounts 100-99999)
├── Create enterprise-specific UI components
├── Policy engine for business rules and approvals
└── Integration testing across all SSP-supported chains
🏗️ Leveraging Existing SSP Infrastructure:
├── Reuse SSP Wallet browser extension (no changes needed)
├── Reuse SSP Key mobile app (minimal UI updates)
├── Extend SSP Relay for multi-party message coordination
├── Leverage existing 15+ blockchain network support
├── Build on proven BIP48 key derivation architecture
├── Maintain zero-server-key-storage security model
└── Deliver enterprise security through open source transparency
📊 Success Metrics:
├── 10+ pilot organizations successfully onboarded
├── $1M+ in multi-party enterprise treasury managed
├── Zero security incidents during deployment
├── <1 hour average multi-party setup ceremony time
└── Seamless integration with existing SSP user base
🎯 Deliverables:
├── Advanced business policy engine with rules
├── Spending limits and approval workflow automation
├── Compliance reporting and audit export tools
├── Mobile-optimized platform interface
├── Integration APIs for business systems
└── Multi-chain expansion (Polygon, BSC, Base)
🔧 Technical Milestones:
├── Policy engine with configurable business rules
├── RESTful APIs for enterprise system integration
├── Mobile-responsive web application
├── Cross-chain transaction coordination
├── Advanced notification and alerting system
└── Performance optimization for mobile devices
📊 Success Metrics:
├── 100+ organizations using the platform
├── $10M+ in managed enterprise treasuries
├── Advanced policy features in production
└── <5 minute transaction approval times
🎯 Deliverables:
├── Bitcoin Taproot 2-of-3 implementation (MuSig2)
├── YubiKey hardware security integration
├── Zero-knowledge proof enhancements
├── Enterprise SSO and identity integration
├── Advanced fraud detection and monitoring
└── SOC 2 Type II compliance certification
🔧 Technical Milestones:
├── MuSig2 implementation for Bitcoin Taproot
├── FIDO2/WebAuthn integration with YubiKey
├── SAML/OIDC integration for enterprise identity
├── Machine learning fraud detection models
├── Security audit and certification processes
└── White-label deployment capabilities
📊 Success Metrics:
├── 500+ organizations on platform
├── $100M+ in managed treasuries
├── SOC 2 Type II certification achieved
└── Zero successful attacks or breaches
🎯 Deliverables:
├── Multi-chain expansion (Solana, Cosmos, Cardano)
├── DeFi protocol integrations and yield strategies
├── Institutional custody partnerships
├── White-label solutions for financial institutions
├── Advanced analytics and business intelligence
└── Global regulatory compliance automation
🔧 Technical Milestones:
├── Universal multi-chain architecture
├── DeFi protocol abstraction layer
├── Institutional-grade analytics dashboard
├── White-label deployment framework
├── Global compliance automation engine
└── Enterprise marketplace integrations
📊 Success Metrics:
├── 1,000+ organizations ecosystem-wide
├── $1B+ in managed digital assets
├── Multiple regulatory certifications
└── Profitable recurring revenue model
Market Reality Map:
Multi-Chain Support
↑
│
Fireblocks/BitGo │ No Solution Exists
(Custodial) │ (Market Gap)
• Multi-chain │
• Enterprise features │
• NOT self-custody │
│
─────────────────────────────────────────────────────→
Custodial │ Self-Custody
│
Not Applicable │ Safe, Casa, Specter
(No self-custody) │ (Self-custody)
│ • Single chain focus
│ • Limited business features
Single Chain Focus
Market Gap Identified: No solution exists for multi-chain business self-custody
When to choose SSP Enterprise over Fireblocks:
✅ Self-custody is non-negotiable
✅ Transparency and auditability required
✅ Cost reduction is priority (90% savings)
✅ No vendor lock-in desired
When to choose Fireblocks over SSP Enterprise:
✅ Automation and policy engines needed
✅ Dynamic threshold changes required
✅ High-frequency operations
✅ Willing to trade custody for convenience
When to choose SSP Enterprise over Safe:
✅ Need Bitcoin or other non-EVM chains
✅ Traditional business features required
✅ Mobile-native workflow preferred
✅ Unified multi-chain management
When to choose Safe over SSP Enterprise:
✅ EVM-only asset portfolio
✅ DeFi-focused operations
✅ DAO governance needs
✅ Free solution acceptable (gas fees only)
When to choose SSP Enterprise over Casa/Specter:
✅ Multi-chain asset portfolio
✅ Business coordination features needed
✅ Mobile workflow preferred
✅ Enterprise-grade audit trails
When to choose Casa/Specter over SSP Enterprise:
✅ Bitcoin-only holdings
✅ Simpler setup preferred
✅ Lower annual costs acceptable
✅ Bitcoin-maximalist philosophy
Market Size: Currently underserved/non-existent
Characteristics:
├── $100K - $100M digital asset portfolios
├── Bitcoin + Ethereum + other chains
├── 2-10 stakeholders requiring approval
├── Self-custody mandate (regulatory or philosophical)
├── Business approval workflows needed
└── Mobile-preferred operational style
Examples:
├── Crypto startups with diverse portfolios
├── Investment DAOs with multi-chain strategies
├── Family offices with cross-chain holdings
├── Partnerships managing diverse crypto assets
└── SMBs accepting multiple cryptocurrencies
Market Size: Large, price-sensitive segment
Characteristics:
├── Currently using expensive custodial solutions
├── Seeking cost reduction without losing features
├── Willing to trade some automation for savings
├── Self-custody becoming regulatory requirement
└── Multi-signature governance already established
Examples:
├── Mid-market companies reducing crypto costs
├── Non-profits managing donor cryptocurrencies
├── Professional services with shared crypto accounts
├── International businesses prioritizing direct asset control
└── Regulated entities requiring transparency
Participants: 2-10 parties per enterprise wallet
Each party needs:
├── Existing SSP Wallet (Chrome/Firefox extension)
├── Existing SSP Key (iOS/Android mobile app)
├── Modern web browser (Chrome/Firefox/Safari/Edge)
├── Reliable internet connectivity for coordination
└── Basic cryptocurrency knowledge
Setup Time: ~1 hour for initial ceremony
Ongoing: ~5 minutes per transaction approval
Roles & Responsibilities:
├── Administrator: Wallet setup and policy management
├── Signers: Transaction approval authority
├── Observers: Read-only access to transactions
└── IT Support: Technical assistance and troubleshooting
Documentation:
├── Business continuity procedures
├── Key backup and recovery processes
├── Emergency access protocols
└── Compliance and audit procedures
┌─────────────────────────────────────────────────────────┐
│ SSP Enterprise Architecture │
├─────────────────────────────────────────────────────────┤
│ Frontend: React/TypeScript SPA │
│ Backend: Node.js/Express API server │
│ Database: MongoDB for coordination and audit │
│ Blockchain: Smart contracts on target networks │
│ Security: End-to-end encryption, zero-knowledge proofs │
│ Integration: WalletConnect, enterprise SSO │
└─────────────────────────────────────────────────────────┘
SSP Wallet Extensions:
// Business account derivation (user-chosen 3-digit numbers)
const BUSINESS_ACCOUNT_MIN = 100;
const BUSINESS_ACCOUNT_MAX = 99999;
function validateBusinessAccount(account: number): boolean {
return account >= BUSINESS_ACCOUNT_MIN && account <= BUSINESS_ACCOUNT_MAX;
}
// Business wallet derivation path
const businessPath = `m/48'/${coin}'/${businessAccount}'/${scriptType}'/0/${addressIndex}`;
// Enterprise transaction handling
interface EnterpriseTransaction {
type: 'enterprise';
businessAccount: number; // 100-99999
walletId: string;
threshold: number;
parties: PartyInfo[];
policy: BusinessPolicy;
approvals: ApprovalStatus[];
}
// Multi-party address generation
export function generateEnterpriseAddress(
partyPubkeys: Buffer[],
threshold: number,
businessAccount: number,
chain: keyof cryptos
): EnterpriseAddress;
SSP Key Extensions:
// Enterprise signing context
interface EnterpriseSigningRequest {
transactionId: string;
businessContext: {
walletName: string;
policy: BusinessPolicy;
currentApprovers: string[];
amount: string;
recipient: string;
purpose: string;
};
technicalContext: {
inputs: UTXO[];
outputs: Output[];
fee: string;
chainId: number;
};
}
// Enhanced approval flow
export function approveEnterpriseTransaction(
request: EnterpriseSigningRequest,
biometricAuth: boolean
): Promise<PartialSignature>;
SSP Relay Extensions:
// Multi-party coordination service
class EnterpriseCoordinator {
async createWallet(
parties: Party[],
threshold: number,
policies: BusinessPolicy[]
): Promise<EnterpriseWallet>;
async proposeTransaction(
walletId: string,
transaction: Transaction,
proposer: string
): Promise<TransactionProposal>;
async collectApprovals(
proposalId: string
): Promise<ApprovalCollection>;
async executeTransaction(
proposalId: string
): Promise<TransactionResult>;
}
Smart Contract Infrastructure:
SSP Enterprise leverages the proven, open-source smart contract
infrastructure and SDK already developed and security-audited by the SSP
team:
SSP Enterprise represents a fundamental shift from "trust us" to "verify everything":
Traditional Approach: Trust the Institution
├── Rely on company promises
├── Accept proprietary "black box" security
├── Depend on institutional controls
└── Hope for business continuity
SSP Enterprise Approach: Verify Everything
├── Cryptographic proof of security
├── Open source transparency
├── Direct blockchain verification
└── Self-sovereign control
Problem 1: Custody vs Control Trade-off
Problem 2: Transparency vs Functionality
Problem 3: Multi-Chain vs Simplicity
Problem 4: Cost vs Quality
The Freemium Advantage:
Sustainable Value Creation:
Traditional Model Problems:
├── High upfront costs block adoption
├── Transaction fees punish usage
├── Vendor lock-in prevents switching
├── Proprietary systems hide costs
└── Fixed pricing ignores value delivered
SSP Enterprise Solution:
├── Free adoption removes barriers
├── No transaction limits encourage usage
├── Open source prevents lock-in
├── Transparent pricing builds trust
└── Value-based fees align incentives
SSP Enterprise represents the natural evolution of the proven SSP Wallet ecosystem into enterprise multi-party coordination.
Rather than building entirely new infrastructure, SSP Enterprise intelligently extends the battle-tested SSP architecture that's already securing user funds across 15+ blockchain networks. This approach delivers enterprise features while maintaining the security, simplicity, and cost-effectiveness that made SSP Wallet successful.
SSP Enterprise fills a unique gap: multi-chain business self-custody. While Fireblocks offers automation at the cost of custody, and Safe provides EVM-only self-custody, SSP Enterprise delivers true multi-chain self-custody with business coordination features.
For organizations requiring multi-chain asset management with true self-custody principles, SSP Enterprise isn't just competitive – it's the only complete solution available.
Ready to take control of your business cryptocurrency management with true self-custody?
SSP Enterprise: Where security meets simplicity, and ownership meets enterprise.
Built on the proven foundation of the SSP Wallet ecosystem, SSP Enterprise delivers institutional-grade multi-party custody without sacrificing the self-sovereignty principles that make cryptocurrency transformative.