Dynamic home page
Search...
⌘K
Getting Started
Welcome
Quickstart
Example Apps
General Guidance
Go Live Checklist
Integrating using AI
Rate Limits
Our Embedded Wallets
Overview
MPC Fundamentals and Glossary
Why MPC Matters
Architecture & Cryptography
MPC Configuration Guide
Advanced Options
Delegated Access
How shares work
Glossary of Terms
Security
Overview
Best Practices
Mitigating Attack Vectors
Developer Dashboard
SDK and API Keys
Analytics
Users & Visitors
Test Accounts
Webhooks
Organization
Settings
Social Providers
Migrations
Migrating to Dynamic
Migrating Users via CSV
Migration from RainbowKit
Wallets & Chains Integration
Integrate your Wallet
Integrate your Chain
Explore Dynamic
Start Free
Live Support
System Status
Dynamic home page
Search...
⌘K
Ask AI
Explore Dynamic
Start Free
Live Support
System Status
Search...
Navigation
Our Embedded Wallets
MPC Configuration Guide
Overview
Implementation Guides
SDK/API References
Recipes
Troubleshooting
Overview
Implementation Guides
SDK/API References
Recipes
Troubleshooting
Our Embedded Wallets
MPC Configuration Guide
Copy page
Available threshold signature schemes for MPC wallets
Copy page
Overview
Dynamic’s MPC system supports different threshold signature schemes that determine how many parties must collaborate to sign transactions. This guide covers the available configurations.
Available Configurations
2-of-2 TSS (Default)
Two parties must collaborate to sign transactions.
Configuration:
Share 1: Dynamic Server Share (Dynamic storage + TEE)
Share 2: User Share (User device storage)
Benefits:
Simple setup and management
Good balance of security and usability
Fast transaction signing
Recommended for:
Most applications
Standard embedded wallets
When simplicity is priority
2-of-3 TSS
Any two out of three parties can sign transactions.
Configuration:
Share 1: Dynamic Server Share (Dynamic storage + TEE)
Share 2: Primary User Share (User device storage)
Share 3: Secondary User Share (User cloud storage/export)
Benefits:
Enhanced security through redundancy
Flexible recovery options
Protection against single point of failure
Recommended for:
High-value wallets
Applications requiring backup recovery
When availability is critical
3-of-5 TSS (Enterprise)
Any three out of five parties must collaborate to sign transactions.
Configuration:
Share 1: Dynamic Server Share (Dynamic storage + TEE)
Share 2: Primary User Share (Dynamic storage + relay)
Share 3: Primary Enterprise Share (Enterprise storage + API)
Share 4: Secondary User Share (User device storage)
Share 5: Tertiary User Share (User cloud storage)
Benefits:
Maximum security through distributed control
Enterprise oversight and compliance
Flexible party management
Recommended for:
Enterprise wallet solutions
Multi-stakeholder applications
High-security financial applications
Configuration Selection
Start Simple
: Begin with 2-of-2 for most applications
Scale Security
: Upgrade to 2-of-3 for enhanced security
Enterprise Needs
: Use 3-of-5 for multi-stakeholder scenarios
Getting Started
To implement MPC wallets with your preferred configuration:
Choose Configuration
: Select appropriate threshold scheme
Configure Shares
: Set up the required number of parties
Test Signing
: Verify the threshold requirements work correctly
Deploy
: Launch with proper monitoring
For detailed implementation guides, see our
Setup documentation
and
Architecture overview
.
Was this page helpful?
Yes
No
Previous
Advanced Options
Advanced options for our embedded wallets
Next
On this page
Overview
Available Configurations
2-of-2 TSS (Default)
2-of-3 TSS
3-of-5 TSS (Enterprise)
Configuration Selection
Getting Started
Assistant
Responses are generated using AI and may contain mistakes.