​
Default Networks

Dynamic provides first-class support for EVM and SVM, with signer support for networks like Sui, Bitcoin, Cosmos, or any chain using:

Need expanded support for a specific chain? Contact us to discuss your use case.

Interested in implementing these advanced features? Contact us to discuss your specific use case and how we can help customize our TSS-MPC solution for your needs.

​
Using Dynamic TSS-MPC for additional networks and chains

This guide explains how to integrate Dynamic’s TSS-MPC wallet infrastructure with blockchain networks that aren’t supported out-of-the-box, such as Cardano.

Dynamic’s TSS-MPC implementation provides secure, threshold-based signing across multiple networks. Today our out of the box implementation with abstractions support EVM, SVM, and rolling out support for Bitcoin and Cosmos. Dynamic fully supports the necessary derivation paths and signing methods for other chains including Cardano.

To integrate with an unsupported network, you will need to:

  • Install the Dynamic Browser SDK
  • Access low-level signer information
  • Handle chain-specific data (message formatting, transaction preparation, etc.)
  • Ensure proper derivation paths are configured

​
Installation

Install the Dynamic Browser SDK:

npm install @dynamic-labs-wallet/browser

​
Accessing Low-Level Signer Information

To work with other chains, you’ll need to access and use the low-level signing functionality provided by the SDK. This allows you to implement chain-specific requirements while leveraging Dynamic’s TSS-MPC infrastructure.

​
Compile and use Chain-Specific Data

Each chain has unique requirements for message formatting, transaction structures, and address derivation. You’ll need to implement these according to the network’s specifications.

​
Signature Example with Cardano

Cardano’s message signing format requires a specific prefix structure:

\x19Cardano Signed Message:\n<length><message>

Where <length> is a single-byte integer representation of the message length.

For comparison, Ethereum uses:

\x19Ethereum Signed Message:\n<length><message>

​
Transaction Generation

You’ll need to create properly formatted transactions for the target chain.

Cardano transactions require serialization using CBOR (Concise Binary Object Representation) encoding. You can use the CIP-30 wallet API or Cardano serialization libraries to construct valid transactions.

​
Public Address Derivation

To derive a Cardano-compatible address, you need to:

  • Convert the public key to a Cardano address using the correct format (Base, Enterprise, etc.)
  • Handle Shelley-era address formats as required

​
Serialization/Deserialization

Cardano transactions require:

  • CBOR encoding for transaction data
  • Proper binary structure for address formats

​
Derivation Paths

Dynamic fully supports the necessary derivation paths for different blockchains. The following are the currently supported derivation paths:

For Cardano, use:

{
  derivationPath: [44, 1815, 0, 0, 0], // 1815 is Cardano's coin type
  signingAlgorithm: SigningAlgorithm.ED25519
}

Dynamic’s core packages will ensure the correct derivation paths are applied.

​
Implementation Steps

  1. Setup the Dynamic SDK as usual
  2. Access the low-level signer from the SDK
  3. Implement chain-specific message formatting for your target blockchain
  4. Create transaction structures according to the chain’s requirements
  5. Derive addresses using the appropriate algorithm
  6. Request a signature using the proper signing algorithm
  7. Process and utilize the signature according to the chain’s needs

​
Resources