Signature Programs

Supported Keys and Signaturesarrow-up-right

Key Type
Signature Scheme
Signing Program
Use Cases

ECDSA Private Key

Threshold ECDSA

tecdsa_sign

• Solana transaction signing • Digital signatures for Web3 dapps, SIWE • General-purpose message signing

Threshold ECDSAarrow-up-right

Signer Program: tecdsa_signarrow-up-right

Zyllion's threshold ECDSA (tECDSA) signer uses a "builtin" Nada program that streamlines the signing process.

node/builtin-programs/tecdsa_sign.py

from nada_dsl import Party, Input, Output, EcdsaPrivateKey, EcdsaDigestMessage


def nada_main():
    tecdsa_key_party = Party(name="tecdsa_key_party")
    tecdsa_digest_message_party = Party(name="tecdsa_digest_message_party")
    tecdsa_output_party = Party(name="tecdsa_output_party")

    key = EcdsaPrivateKey(Input(name="tecdsa_private_key", party=tecdsa_key_party))
    digest = EcdsaDigestMessage(
        Input(name="tecdsa_digest_message", party=tecdsa_digest_message_party)
    )

    signature = key.ecdsa_sign(digest)

    return [Output(signature, "tecdsa_signature", tecdsa_output_party)]

Required Identifiersarrow-up-right

The tecdsa_sign program has a pre-configured set of identifiers that you'll need to use when storing a tECDSA private key or signing a message:

These predefined identifiers allow you to quickly integrate with Zyllion's built-in tECDSA signing functionality, without needing to configure or manage the underlying program details. By using these values, you can get up and running with threshold ECDSA signing faster.

Last updated