multi-party-computation-controller-api
    Preparing search index...

    Request body for POST /key-generation.

    These fields map directly to the GenerateKeyRequest proto message. The algorithm, threshold, and participants are stored in the key-metadata store after a successful key generation and reused for all subsequent signing calls on the same key.

    Index

    Constructors

    Properties

    algorithm: Algorithm

    Algorithm to use for distributed key generation.

    • FROST_ED25519 / FROST_SCHNORR_SECP256K1: fast (< 1 s), suitable for Solana, Bitcoin Schnorr.
    • CGGMP24_ECDSA_SECP256K1: slow (10–60 s+), for Ethereum/EVM.
    keyIdentifier: string

    Stable application-assigned identifier for this key. Must be unique across all keys; re-using an existing identifier will overwrite the stored key metadata on completion.

    wallet - 1;
    
    participants: number

    Total number of nodes participating in the key-generation protocol (n in t-of-n). Must be ≥ 2 and match the number of nodes configured in controller.toml.

    threshold: number

    Minimum number of nodes required to produce a valid signature (t in t-of-n). Must be ≥ 2, ≤ 255, and ≤ participants.