Signer

Signers are the identity and signing mechanism used by the SDK when it needs to produce signed provenance statements, attestations, or model-signing metadata.

A signer is required, as every statement that gets created is attributed back to being created by a Signer's underlying DID (Decentralized Identifier). A signer is part of process setup: create or load a signer, call set_active_signer, and then let higher-level SDK operations use that active signer automatically.

The SDK supports local signers and service-backed signers. Choose the one that matches your security model and operational environment.

Signer

Python-exposed signer information. Contains the name and DID key of a cryptographic signer.

name property 

name: str

Returns the human-readable name of the signer. # Returns * &str - The signer's name

did_key property 

did_key: str

Returns the DID key of the signer. # Returns * &str - The signer's DID key string

new staticmethod 

new(
    algorithm: Optional[SIGNER_ALGORITHMS] = None,
    name: Optional[str] = None,
    _load_if_exists: Optional[bool] = None,
) -> Signer

vcomp_notary staticmethod 

vcomp_notary(
    url: Optional[str] = None,
    name: Optional[str] = None,
    _load_if_exists: Optional[bool] = None,
) -> Signer

Creates a VComp notary signer and persists it to disk. If name is provided, the signer is stored under that name. When _load_if_exists=True, an existing signer with the same name is loaded instead of creating a new remote signer configuration.

auth_service staticmethod 

auth_service(
    url: str,
    name: Optional[str] = None,
    _load_if_exists: Optional[bool] = None,
) -> Signer

Creates an Auth Service signer and persists it to disk. Requires the EQTY_API_KEY environment variable to be set. If name is provided, the signer is stored under that name. When _load_if_exists=True, an existing signer with the same name is loaded instead of creating a new remote signer configuration.

from_private_key staticmethod 

from_private_key(
    algorithm: SIGNER_ALGORITHMS,
    private_key: str,
    name: Optional[str] = None,
    _load_if_exists: Optional[bool] = None,
) -> Signer

Signer Algorithms

The algorithm enum controls which key type is created for signer flows that generate or import keys.

Most users can use the default unless they have an interoperability or policy reason to choose a specific algorithm.

Supported signer algorithm identifiers.

ED25519 instance-attribute 

ED25519: SIGNER_ALGORITHMS

SECP256K1 instance-attribute 

SECP256K1: SIGNER_ALGORITHMS

SECP256R1 instance-attribute 

SECP256R1: SIGNER_ALGORITHMS