Skip to main content

Supported Features

This section outlines the current status of feature support for Silent Network. We continuously add features based on customer needs. If you don't see a feature you're looking for here, contact us - we may already be working on it!

Feature Matrix

FeatureECDSAEDDSAV1V2No-authSDKDetails
Keygen✅✅✅✅✅TS, Rust, Go
Signgen✅✅✅✅✅TS, Rust, Go
Add ephemeral key✅✅✅✅N.A.TS, Rust, Go
Revoke ephemeral key✅✅✅✅N.A.TS, Rust, Go
Passkey registrationN.A.N.A.✅❌N.A.TSRegistration uses chal-resp by definition
Init presign✅❌❌✅✅TS, RustNo need for presigns for EdDSA
Finish presign✅❌❌✅✅TS, Rust
Key refresh✅✅✅❌❌TS, RustWe plan to support refresh in no-auth under v2
Quorum change✅✅❌✅✅GoMore SDK support soon
Key Import✅✅❌✅✅Rust
Key Export✅✅❌✅✅Rust, GoGo uses bindings to Rust here

Supported Algorithms

ECDSA (DKLS23)

  • Protocol: DKLS23 - State-of-the-art threshold ECDSA
  • Use Cases: Bitcoin, Ethereum, and other ECDSA-based blockchains

EdDSA (L22)

  • Protocol: L22 - Optimized threshold EdDSA
  • Use Cases: Solana, Algorand, and other EdDSA-based blockchains

Core Features

Key generation

Create a new wallet in a truly distributed way

  • A new wallet is generated collaboratively between the client and server.
  • The private key is never assembled or known in its entirety by any party.
  • Each party generates its own secret share, contributing to the overall private key.
  • The corresponding public key (wallet address) is derived from these shares without revealing the private key.
  • The process ensures that the complete private key never exists on any single device or at any point in time.

This distributed key generation forms the basis for all subsequent MPC operations, providing a secure foundation for the wallet with enhanced privacy and security guarantees.

Sign generation

Sign messages while maintaining the distributed nature of the private key:

  • Collaborative signature generation occurs between the client and server.
  • Each party uses its secret share to contribute to creating a valid ECDSA signature.
  • The private key remains distributed and is never reconstructed during the signing process.
  • The resulting signature is cryptographically identical to one created with a standard single-party wallet.
  • Supports signing of arbitrary messages, typically transaction data on the blockchain.

This distributed signing process allows for secure transaction authorization while preserving the key's distributed nature, exemplifying the MPC wallet's enhanced security model.

Key Refresh

Proactively update the client's and server's secret shares without altering the wallet's public address or key. This process enhances long-term security of the MPC wallet.

Key Refresh Advantages

Key refresh is a critical security feature in MPC systems, offering several advantages:

  • Forward security: Regularly refreshing shares maintains the system's security posture and invalidates the old compromised shares, at the event of share compromise.
  • Hardening Cryptanalysis : It reduces the attack vector of cryptanalysis since the potential adversary can obtain fewer signatures from the same secret key.
  • Compliance with Key Rotation Policies: Helps meet regulatory or organizational requirements for periodic key updates.

By implementing regular key refreshes, the overall security of the MPC system is significantly enhanced, creating a dynamic security environment that's resistant to long-term attacks and information leakage.