COMPASS-KEM
Lattices · MLWR · niccs.org.cn(opens in a new tab)
- Programmes
- NGCC R1
- Status
- NGCC round 1
- Security flags
- Implementation findings (2 of 4 sets)
Third-party findings: full report on ngcc.dev(opens in a new tab).
Parameter sets
| Parameter set | Level | pk (B) | ct (B) | pk+ct (B) | Keygen | Encaps | Decaps |
|---|---|---|---|---|---|---|---|
| COMPASS-KEM-128 | 128-bit | 672 | 768 | 1,440 | 443.3 µs | 451.6 µs | 460.5 µs |
| COMPASS-KEM-256 | 256-bit | 1,312 | 1,472 | 2,784 | 1.72 ms | 1.73 ms | 1.75 ms |
| COMPASS-KEM-384 Implementation findings | 384-bit | 2,144 | 2,432 | 4,576 | 981.4 µs | 981.3 µs | 987.1 µs |
| COMPASS-KEM-512 Implementation findings | 512-bit | 2,848 | 3,264 | 6,112 | 1.73 ms | 1.73 ms | 1.74 ms |
Wall-clock times vary between runs and machines (CPU frequency scaling, other tenants on cloud VMs); cycle counts are the steadier basis for comparison.
Security flags
- Implementation findings (COMPASS-KEM-384, COMPASS-KEM-512): The submitted code derives keys from a 256-bit root, so key search costs about 2^256, below this set's target (Saarinen). Full findings report(opens in a new tab)
History
No events recorded for this scheme yet.