Platform

Keygen

Generate a new MPC wallet. The app and the two Trio nodes run distributed key generation, and each ends up with its own keyshare. The resulting public key is the wallet address. No seed phrase is ever created.

Please refer to the Session creation section to learn how to create a new session.

Full example

ECDSA
EdDSA

App.tsx
import { type EcdsaSession } from '@silencelaboratories/silent-shard-sdk/ecdsa';

export const keygen = async (session: EcdsaSession) => {
  const keyshare = await session.keygen();
  console.log('Created new keyshare with public key: ', keyshare.publicKeyHex);
};

App.tsx
import { type EddsaSession } from '@silencelaboratories/silent-shard-sdk/eddsa';

export const keygen = async (session: EddsaSession) => {
  const keyshare = await session.keygen();
  console.log('Created new keyshare with public key: ', keyshare.publicKeyHex);
};

When session.keygen() is called, the app and the server exchange messages to generate a new MPC wallet.
Two new "shares" are generated: one for the client and one for the server. Both shares together form the MPC wallet.
keyshare is of type Keyshare and represents the client's "share" of the MPC wallet.
The keyshare.publicKeyHex property is the public key of the MPC wallet in hex format.

Please refer to the Session creation section to learn how to create a new session.

Full example

ECDSA
EdDSA
Taproot

main.dart
import 'package:silent_shard_sdk/silent_shard_sdk.dart' as sdk;

Future<sdk.DklsKeyshare> keygen(sdk.EcdsaSession session) async {
  final sdk.DklsKeyshare keyshare = await session.keygen();
  print('Keyshare created, public key: ${keyshare.publicKeyHex}');
  return keyshare;
}

main.dart
import 'package:silent_shard_sdk/silent_shard_sdk.dart' as sdk;

Future<sdk.SchnorrKeyshare> keygen(sdk.EddsaSession session) async {
  final sdk.SchnorrKeyshare keyshare = await session.keygen();
  print('Keyshare created, public key: ${keyshare.publicKeyHex}');

  return keyshare;
}

main.dart
import 'package:silent_shard_sdk/silent_shard_sdk.dart' as sdk;

Future<sdk.TaprootKeyshare> keygen(sdk.TaprootSession session) async {
  final sdk.TaprootKeyshare keyshare = await session.keygen();
  print('Keyshare created, public key: ${keyshare.publicKeyHex}');
  return keyshare;
}

When session.keygen() is called, the app and the server exchange messages to generate a new MPC wallet.
Two new DklsKeyshare are generated: one for the client and one for the server. Both shares together form the MPC wallet.
The keyshare.publicKeyHex property is the public key of the MPC wallet in hex format.

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.

Step 1 : Create Session

Create TrioSession if you haven't already.

Step 2 : Perform Keygen

Call trioSession.keygen() which returns Result of Success with a keyId (String) or Failure with exception.

Example

Example.kt
// keygen runs distributed key generation and returns the new keyId.
// The keyshare itself is persisted to your StorageClient — keep the keyId to
// address it in later operations (sign, refresh, export, delete, …).
suspend fun performKeygen(trioSession: TrioSession): String {
    return withContext(Dispatchers.IO) {
        trioSession.keygen().getOrThrow()
    }
}

trioSession.keygen() performs message exchange between mobile and server to generate a new MPC wallet.
Three new "shares" are generated: one for the client(on mobile) and two for the respective servers(on server). All of the shares together form the MPC wallet.
Result of trioSession.keygen() could be a Success with a String (the keyId addressing the client's keyshare in your storage) or Failure with Exception
SilentShard.ECDSA.deriveChildPublicKey() or SilentShard.EdDSA.deriveChildPublicKey() could be used to get the compressed public key of the MPC wallet. Refer to SDK-Reference for additional Info and Utils.

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.

Step 1 : Create Session

Create TrioSession if you haven't already.

Step 2 : Perform Keygen

Call trioSession.keygen() which returns Result of Success with the generated key's keyId as a String or Failure with an error.

Example

Example.swift
    // keygen returns the new keyId (a String). The keyshare is persisted to your
    // StorageClient — keep the keyId to address it in later operations.
    func performKeygen(trioSession: TrioSession) async -> String? {
        let result: Result<String, any Error> = await trioSession.keygen()
        // returns nil if the operation fails, or handle it however your flow needs
        switch result {
        case .success(let keyId):
            // do something with the keyId
            Swift.print(keyId)
            return keyId
        case .failure(let error):
            // show the error to the user or abort the process
            Swift.print(error)
            return nil
        }
    }

trioSession.keygen() performs message exchange between mobile and server to generate a new MPC wallet.
Two new "shares" are generated: one for the client(on mobile) and one for the server(on server). Both shares together form the MPC wallet.
Result of trioSession.keygen() could be a Success with a keyId (String) that identifies the generated key or Failure with error. The client's keyshare is persisted through your StorageClient, addressed by this keyId.
SilentShard.ECDSA.getKeysharePublicKey() or SilentShard.EdDSA.getKeysharePublicKey() could be used to get the compressed public key of the MPC wallet. Refer to SDK-Reference for additional Info and Utils.

Handling the operation

This is an MPC operation, so it takes a few seconds (the app and the Trio nodes exchange several messages). Show a non-blocking loading state while it runs, confirm on success, and offer a retry on failure. When something goes wrong, the SDK surfaces the error for you to handle:

Error	What it means	How to handle
Keyshares not in sync, run reconcile	A previous operation didn't finish cleanly (for example the app was force-closed mid-operation)	Run reconcile, then retry
Server error	A server ended the session unexpectedly	Show the error and offer a retry
Connection / transport error	A server was unreachable or the connection dropped	Show the error and offer a retry

All of these operations are safe to retry from the start.