CEDRUS+C

Symmetric · Hash-based · niccs.org.cn(opens in a new tab)

Programmes
NGCC R1
Latest version
Round 1 ·
Security flags
Implementation findings (all sets)

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

Parameter sets

Round 1 · 20 Sep 2026

Parameter sets of CEDRUS+C
Parameter setLevelpk (B)sig (B)pk+sig (B)SignVerify
CEDRUSC-160s Implementation findings128-bit409,4609,5002.37 s5.89 ms
CEDRUSC-160f Implementation findings128-bit4019,81219,852141.75 ms4.33 ms
CEDRUSC-256s Implementation findings256-bit6424,10424,1683.54 s9.80 ms
CEDRUSC-256f Implementation findings256-bit6443,54843,612344.87 ms5.95 ms
CEDRUSC-384s Implementation findings384-bit9661,57261,66813.19 s15.07 ms
CEDRUSC-384f Implementation findings384-bit9675,98876,0843.46 s35.55 ms
CEDRUSC-512s Implementation findings512-bit12898,21298,34023.90 s32.59 ms
CEDRUSC-512f Implementation findings512-bit128121,520121,6486.94 s44.31 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 (all parameter sets): The submitted code mishandles hypertree indices so that few-time keys repeat across signatures, enabling forgery after adaptive signing queries at every parameter set (Saarinen). Full findings report(opens in a new tab)

Only one version of CEDRUS+C is recorded, so there is nothing to compare yet.

History

  1. New version

    Round 1

Full timeline →