FROST threshold signing
Threshold key and ceremony APIs with explicit version and custody boundaries.
FROST enables a threshold quorum to produce an Ed25519 signature. It does not by itself prove personhood, unique humans, or that a group has legitimate authority over an entity.
Published dependency versions
oas-crypto@1.1.1 declares frost-ed25519 3.x, while aegis-keys@0.2.0 declares 2.2. Serialized share/key-package interoperability across these versions is not established by a shared final-signature algorithm. Pin the actual resolved dependencies and validate migration with the exact libraries and backup material before changing a signing group.
Do not discard old shares or assume that generating a new set preserves the same public key or DID. Key refresh, new key generation and authority rotation are different operations and need an explicit ceremony and recovery plan.
Published APIs
AEGIS keys re-export generate_shares, sign_with_threshold, and verify_threshold_signature. Wallet ceremony utilities live in aegis-wallet/src/ceremony.rs. OAS crypto and the shared crypto-WASM crate expose their own threshold primitives.
Use the exact signatures and configuration from AEGIS threshold source, wallet ceremony source, and the crypto package catalog. Never reuse signing nonces across signing sessions. Test insufficient quorum, incorrect share, interrupted ceremony and mismatched public-key cases.