Digital Signature
SNOVA
Simple Noncommutative-ring-based UOV Algorithm
Mechanism
How it works
Parameter Sets
1 variants shipped
Each variant trades security category against key, ciphertext, or signature size. QNSI exposes all variants via the @heossi/liboqs-native binding; tenant crypto-policy determines which are allowed.
| Variant | NIST Level | Public Key | Secret Key | Signature | Note |
|---|---|---|---|---|---|
| SNOVA (multiple param sets at NIST levels 1, 3, 5) | L5 | 2,456 B | 48 B | 168 B |
NIST ACVP
Conformance evidence
QNSI runs the official NIST ACVP test vectors against every shipped algorithm. Live evidence + SHA-3-256 tamper digest at /verify/conformance.
Use Cases
When to use it
- Multivariate signatures with much smaller public keys than plain UOV
- NIST PQC additional-signatures track candidate
Trade-offs
What you give up, what you get
- Compact public keys and signatures
- Non-commutative ring structure is newer — less cryptanalysis history than UOV
FAQ
SNOVA — frequently asked questions
Concise, source-of-truth answers to the questions buyers and engineers ask most about this algorithm.
What is SNOVA?
SNOVA (Simple Noncommutative-ring-based UOV Algorithm) is a multivariate post-quantum digital signature scheme. It is designed to resist attacks from both classical and quantum computers, and QNSI ships 1 of its parameter sets.
Is SNOVA NIST-standardized?
SNOVA is not a finalized NIST FIPS standard. QNSI ships it as a non-FIPS post-quantum option, typically to add an independent cryptographic assumption (multivariate) alongside the FIPS-standardized ML-KEM and ML-DSA for defence-in-depth.
What is SNOVA used for?
On QNSI, SNOVA is used for Multivariate signatures with much smaller public keys than plain UOV; NIST PQC additional-signatures track candidate. It is available from the default crypto-policy tier upward via the liboqs provider.
References