@blockchaincommons/components - v1.0.0-beta.4
    Preparing search index...

    Variable SignatureSchemeConst

    SignatureScheme: Readonly<
        {
            Schnorr: "Schnorr";
            Ecdsa: "Ecdsa";
            Ed25519: "Ed25519";
            MLDSA44: "MLDSA44";
            MLDSA65: "MLDSA65";
            MLDSA87: "MLDSA87";
            SshEd25519: "SshEd25519";
            SshDsa: "SshDsa";
            SshEcdsaP256: "SshEcdsaP256";
            SshEcdsaP384: "SshEcdsaP384";
        },
    > = ...

    Supported digital signature schemes.

    This enum represents the various signature schemes supported in this package.

    • Schnorr: BIP-340 Schnorr signature scheme (secp256k1) - DEFAULT
    • ECDSA: ECDSA signature scheme (secp256k1)
    • Ed25519: RFC 8032 signatures
    • MLDSA44: ML-DSA44 post-quantum signature scheme (NIST level 2)
    • MLDSA65: ML-DSA65 post-quantum signature scheme (NIST level 3)
    • MLDSA87: ML-DSA87 post-quantum signature scheme (NIST level 5)
    • SshEd25519: Ed25519 via SSH agent
    • SshDsa: DSA via SSH agent
    • SshEcdsaP256: ECDSA P-256 via SSH agent
    • SshEcdsaP384: ECDSA P-384 via SSH agent

    Wire format note: the reference models SignatureScheme as a unit-only enum; TypeScript uses string-typed values for ergonomic switch/equals checks. The CBOR/UR wire format never includes the scheme name — only the scheme's integer/byte-string discriminator on Signature, SigningPrivateKey, SigningPublicKey — so this is a stylistic difference, not a parity gap.