Distributed key generation (DKG) creates key shares without a single operator generating the complete private key. The Attester Network’s DKG runs on-chain. Each threshold signing daemon holds its node’s shares. The engine coordinates evidence and transaction submission without holding those shares.

Key separation

Infinity Solvers is a TSS-powered committee that custodies solver funds for extra security. It uses the SPEND identity. The Attester Network uses the ATTEST identity. Every signing request identifies its signature suite and key generation. For Solana and Move attestations, the encoded signer epoch remains 1 in the reviewed implementation. This protocol field does not automatically follow Attester Network key generations. Transaction fee accounts remain separate from these threshold keys.

Order-bound attestation keys

An EVM order names its input oracle in the signed order data. The FrostInputOracle stores an immutable group public key. A new attestation key generation therefore requires the corresponding oracle deployment for new orders. Existing orders retain their original oracle and require signatures under its key. The engine pins one attestation generation for the complete output signature bundle. Signatures from different generations cannot satisfy one order’s oracle requirements.

Rotation behavior

The solver pauses new intake while a relevant attestation key rotation is active. Existing admitted work follows the engine’s generation and recovery checks. The daemon retains a superseded generation until the next ceremony begins. Starting another ceremony can therefore affect unfinished orders that still require the superseded shares. Before starting another rotation, verify that orders requiring the previous generation have completed. Preserve the state needed to recover unfinished signing and settlement operations.

Operational requirements

Protect daemon state and communication keys. Maintain authenticated connectivity between signing daemons. Fund the operator and transaction fee accounts required by each role. Monitor peer health, signing refusals, discovery gaps, and unfinished settlements. Do not delete durable state to resolve an uncertain transaction or nonce allocation. Reconcile the chain result before changing recovery records.