Lynxer

Symmetric · Lynx OWF · niccs.org.cn(opens in a new tab)

Programmes
NGCC R1
Latest version
Round 1 ·
Security flags
Broken (6 of 8 sets)

Third-party findings: full report on ngcc.dev(opens in a new tab).

Parameter sets

Round 1 · 20 Sep 2026

Parameter sets of Lynxer
Parameter setLevelpk (B)sig (B)pk+sig (B)SignVerify
Lynxer-160s 128-bit404,6074,64719.81 ms16.94 ms
Lynxer-160f 128-bit405,8015,8412.64 ms2.38 ms
Lynxer-256s Broken256-bit6412,19112,25554.80 ms45.34 ms
Lynxer-256f Broken256-bit6415,09715,1616.05 ms5.63 ms
Lynxer-384s Broken384-bit9627,49527,591218.22 ms143.92 ms
Lynxer-384f Broken384-bit9634,10934,20520.75 ms18.62 ms
Lynxer-512s Broken512-bit12848,87949,0075.95 s5.30 s
Lynxer-512f Broken512-bit12861,09161,219589.27 ms525.90 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

  • Broken (Lynxer-256s, Lynxer-256f, Lynxer-384s, Lynxer-384f, Lynxer-512s, Lynxer-512f): A degenerate witness lets anyone forge signatures from the public key at about the cost of honest signing (Feussner). One signature also allows key recovery below the target (Xiong and Wang).

Only one version of Lynxer is recorded, so there is nothing to compare yet.

History

  1. added to site Update

    Lynxer, ReSolveD-ɑ and SYDO are now built from their submitted optimised x86 implementations (C++ with AVX2) instead of the reference code. The optimised builds reproduce the submitted test vectors and give the same key and signature sizes. Their earlier timings came from the reference code and are removed until our next benchmark run. Galas stays on its reference code, because its optimised code has no implementation of the NGCC signature interface.

  2. New version

    Round 1

Full timeline →