Dynamic SDK V5 launches with TSS-MPC for enhanced wallet security

Wallet infrastructure company Dynamic Labs has shipped SDK V5, its most technically ambitious release yet. The headline feature is native Threshold Signature Scheme Multi-Party Computation, a cryptographic approach that keeps a complete private key from ever existing in one place at one time.

Traditional crypto wallets generate a single private key, which means whoever holds that key holds the assets. TSS-MPC splits the cryptographic material into separate key shares that are used together to sign transactions but never assembled into a complete key. There is no master secret to steal.

What TSS-MPC actually does

Dynamic’s default configuration runs on a 2-of-2 model, splitting ownership between a device share held by the user and a server share held by Dynamic. The setup is adjustable to a 2-of-3 arrangement for more flexibility.

Signing speeds land under one second. Recovery works without seed phrases. Users can restore wallet access through social logins, email, or password-encrypted backups.

The SDK supports Ethereum-compatible networks, Solana, Bitcoin, and Stellar, with a universal key design intended to work across those environments without requiring separate key management for each chain.

The broader security architecture

Dynamic has built the infrastructure to enterprise compliance standards, including SOC 2 Type 2 certification and third-party security audits.

The platform also supports periodic key resharing, a feature that lets key material be redistributed without changing the wallet address or disrupting the user experience. In practice, this means a compromised device share can be rotated out without requiring users to move funds to a new wallet entirely.

General availability for the MPC wallet feature is projected for mid-2025. Future SDK releases are planned in Rust and Python, expanding reach beyond the current JavaScript-focused developer base.

Disclosure: This article was edited by Editorial Team. For more information on how we create and review content, see our Editorial Policy.