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
Configuration Selection
For most applications, starting with the 2-of-2 configuration provides the best balance of security and simplicity. As your security requirements grow, you can upgrade to 2-of-3 for enhanced redundancy and flexible recovery options.
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.
Additional configuration option (hosting a share)
For developers that need to host a share on behalf of a user to perform limited functionality such as signing operations, see Delegated Access.Last modified on September 21, 2026
