[ { "id": 1, "name": "Aigis-Sig^+", "raw_name": "Aigis-Sig$^+$", "category": "Signature", "family": "Lattice", "spec_url": "", "code_url": "https://github.com/openHiTLS/PQCP", "notes": "The openHiTLS implementation explicitly identifies its Aigis-Sig+ KATs, exposes Sign/Verify, and constructs public keys from a polynomial matrix times short secret vectors plus error; this establishes a lattice signature. Sources: https://github.com/openHiTLS/PQCP#Aigis-Sig-KAT and https://github.com/openHiTLS/PQCP/blob/6bfd209ccb35ed68b2754bbdc3adfa558f4d71a3/src/Aigis-sig/src/aigis_sig_sign.c .", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/A6CC4J6Y2SD7LJGDFHE677JES6CIBTON/", "slug": "aigis-sig-plus" }, { "id": 2, "name": "BIT", "raw_name": "BIT", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "Reviewed the official thread (https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/U7FSJZ6KONWY36MQDOVDDB7IHHORNAJY/); it identifies BIT but gives no algorithm description. The sources reviewed did not establish its primitive or security foundation, so category and family remain unverified.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/U7FSJZ6KONWY36MQDOVDDB7IHHORNAJY/", "slug": "bit" }, { "id": 3, "name": "CEDRUS^+C", "raw_name": "CEDRUS$^+$C", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "Reviewed the official thread (https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/UFWXT6DHJ56SDI6DD3NJ6JK2PFIXCMXD/); it identifies CEDRUS^+C but gives no algorithm description. The sources reviewed did not establish its primitive or security foundation, so category and family remain unverified.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/UFWXT6DHJ56SDI6DD3NJ6JK2PFIXCMXD/", "slug": "cedrus-plus-c" }, { "id": 4, "name": "CEDRUS^{\\alpha}", "raw_name": "CEDRUS$^{\\alpha}$", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "Reviewed the official thread (https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/QTJJOIBU56LBGJ2JRXKKH5OX3ZIW3OQJ/); it identifies CEDRUS^{\\alpha} but gives no algorithm description. The sources reviewed did not establish its primitive or security foundation, so category and family remain unverified.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/QTJJOIBU56LBGJ2JRXKKH5OX3ZIW3OQJ/", "slug": "cedrus-alpha" }, { "id": 5, "name": "Chinith", "raw_name": "Chinith", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "Reviewed the official thread (https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/UBKP5VIJTAKEWQGN7R6C2UZ7OGW2XYRB/); it identifies Chinith but gives no algorithm description. The sources reviewed did not establish its primitive or security foundation, so category and family remain unverified.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/UBKP5VIJTAKEWQGN7R6C2UZ7OGW2XYRB/", "slug": "chinith" }, { "id": 6, "name": "COMPASS-SIG", "raw_name": "COMPASS-SIG", "category": "Signature", "family": "", "spec_url": "", "code_url": "", "notes": "The official name COMPASS-SIG identifies a signature candidate (https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/FACKHS3U2WG66C763VRSC44CEH7NIYHY/). The reviewed thread supplies no construction, and the sources reviewed did not establish its security foundation; family remains unverified.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/FACKHS3U2WG66C763VRSC44CEH7NIYHY/", "slug": "compass-sig" }, { "id": 7, "name": "CS", "raw_name": "CS", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "Reviewed the official thread (https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/6Y7RS3WZHP5HOVGHOSW64T4DZNPSAXDS/); it identifies CS but gives no algorithm description. The sources reviewed did not establish its primitive or security foundation, so category and family remain unverified.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/6Y7RS3WZHP5HOVGHOSW64T4DZNPSAXDS/", "slug": "cs" }, { "id": 8, "name": "DARTS", "raw_name": "DARTS", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "Reviewed the official thread (https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/ZTVJHAUOCD3ZU4J72AMG3EDEZUDRR52Q/); it identifies DARTS but gives no algorithm description. The sources reviewed did not establish its primitive or security foundation, so category and family remain unverified.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/ZTVJHAUOCD3ZU4J72AMG3EDEZUDRR52Q/", "slug": "darts" }, { "id": 9, "name": "DOVE", "raw_name": "DOVE", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "Reviewed the official thread (https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/PK36WEI2O5J6TBSBL5MRRDYPATRYYPIT/); it identifies DOVE but gives no algorithm description. The sources reviewed did not establish its primitive or security foundation, so category and family remain unverified.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/PK36WEI2O5J6TBSBL5MRRDYPATRYYPIT/", "slug": "dove" }, { "id": 10, "name": "Facto-DSA", "raw_name": "Facto-DSA", "category": "Signature", "family": "Multivariate", "spec_url": "", "code_url": "", "notes": "The primary technical analysis explicitly describes Facto-DSA key generation, signing and verification using hidden polynomial maps and polynomial factorization, establishing Signature/Multivariate. Source: https://eprint.iacr.org/2026/1403 (Section 2). No claim of identical ICCS parameter sets is made.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/X63HQQDTUFPQQGA4DJAHSAISTNYZUVC6/", "slug": "facto-dsa" }, { "id": 11, "name": "FlexTree", "raw_name": "FlexTree", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "Reviewed the official thread (https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/5DSK4DF2SIKI6RNI6NC5RYXOJG73DMAJ/); it identifies FlexTree but gives no algorithm description. The sources reviewed did not establish its primitive or security foundation, so category and family remain unverified.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/5DSK4DF2SIKI6RNI6NC5RYXOJG73DMAJ/", "slug": "flextree" }, { "id": 12, "name": "Galas", "raw_name": "Galas Signature Scheme", "category": "Signature", "family": "", "spec_url": "", "code_url": "", "notes": "The official name Galas Signature Scheme identifies a signature candidate (https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/3FJV2IP2L5BFKAPR364ISD45Z7UJBJUY/). The reviewed thread supplies no construction, and the sources reviewed did not establish its security foundation; family remains unverified.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/3FJV2IP2L5BFKAPR364ISD45Z7UJBJUY/", "slug": "galas" }, { "id": 13, "name": "GreatWall", "raw_name": "GreatWall Signature Algorithm", "category": "Signature", "family": "", "spec_url": "", "code_url": "", "notes": "The official name GreatWall Signature Algorithm identifies a signature candidate (https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/5IGQ6ZDNGTS7TSTFXE3PFVHHJL7BM2LJ/). The reviewed thread supplies no construction, and the sources reviewed did not establish its security foundation; family remains unverified.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/5IGQ6ZDNGTS7TSTFXE3PFVHHJL7BM2LJ/", "slug": "greatwall" }, { "id": 14, "name": "Lynxer", "raw_name": "Lynxer", "category": "Signature", "family": "Symmetric", "spec_url": "", "code_url": "", "notes": "The authors explicitly name Lynxer as their digital signature built from the Lynx symmetric primitive in the VOLE-in-the-Head framework. Its security foundation is symmetric; VOLE-in-the-Head is the construction technique. Source: https://eprint.iacr.org/2026/1099 .", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/A3VK2RZD6XCJB5YBKZN2OSDSYMSVFUL6/", "slug": "lynxer" }, { "id": 15, "name": "MORNING-ATLAS", "raw_name": "MORNING-ATLAS", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "Reviewed the official thread (https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/WOOBB3WCRHGVXKSTYQBTVMTW6HKPMX2U/); it identifies MORNING-ATLAS but gives no algorithm description. The sources reviewed did not establish its primitive or security foundation, so category and family remain unverified.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/WOOBB3WCRHGVXKSTYQBTVMTW6HKPMX2U/", "slug": "morning-atlas" }, { "id": 16, "name": "Octarine", "raw_name": "Octarine", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "Reviewed the official thread (https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/J32MD6K6AUGKHVUOZX6M4OJHWNPNCLWQ/); it identifies Octarine but gives no algorithm description. The sources reviewed did not establish its primitive or security foundation, so category and family remain unverified.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/J32MD6K6AUGKHVUOZX6M4OJHWNPNCLWQ/", "slug": "octarine" }, { "id": 17, "name": "OPS", "raw_name": "OPS Digital Signature Algorithm", "category": "Signature", "family": "", "spec_url": "", "code_url": "", "notes": "The official name OPS Digital Signature Algorithm identifies a signature candidate (https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/PPO3KFSJJPUVKQEVPCPOP3A3IL2DRHOQ/). The reviewed thread supplies no construction, and the sources reviewed did not establish its security foundation; family remains unverified.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/PPO3KFSJJPUVKQEVPCPOP3A3IL2DRHOQ/", "slug": "ops-digital" }, { "id": 18, "name": "Origami", "raw_name": "Origami", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "Reviewed the official thread (https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/7Z47WGTALXYFJS5YRRGDL65NJUG3CU56/); it identifies Origami but gives no algorithm description. The sources reviewed did not establish its primitive or security foundation, so category and family remain unverified.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/7Z47WGTALXYFJS5YRRGDL65NJUG3CU56/", "slug": "origami" }, { "id": 19, "name": "Phoenix", "raw_name": "Phoenix", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "Reviewed the official thread (https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/M3XAI6VRCGWEXYF5YOYXWH25JFDYAWVZ/); it identifies Phoenix but gives no algorithm description. The sources reviewed did not establish its primitive or security foundation, so category and family remain unverified.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/M3XAI6VRCGWEXYF5YOYXWH25JFDYAWVZ/", "slug": "phoenix" }, { "id": 20, "name": "Qing Luan", "raw_name": "Qing Luan", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "Reviewed the official thread (https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/UAEOBUIJPNMH5ZQ4OCYNAGCGAOYZGEAP/); it identifies Qing Luan but gives no algorithm description. The sources reviewed did not establish its primitive or security foundation, so category and family remain unverified.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/UAEOBUIJPNMH5ZQ4OCYNAGCGAOYZGEAP/", "slug": "qing-luan" }, { "id": 21, "name": "ReSolveD-\\alpha", "raw_name": "ReSolveD-$\\alpha$", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "Reviewed the official ReSolveD-alpha thread: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/HRQJE3Z4ZZYQD6SSCLYV45QWSGLIX4YR/ . The authors describe base ReSolveD as a signature based on regular syndrome decoding in https://eprint.iacr.org/2024/040, but the reviewed sources do not identify the submitted alpha variant. Category and family remain unverified for that variant.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/HRQJE3Z4ZZYQD6SSCLYV45QWSGLIX4YR/", "slug": "resolved-alpha" }, { "id": 22, "name": "Rhyme", "raw_name": "Rhyme", "category": "Signature", "family": "Lattice", "spec_url": "", "code_url": "", "notes": "The authors explicitly describe Rhyme as a Fiat-Shamir digital signature with security based on an LWE variant and 3C sampling. Source: https://eprint.iacr.org/2025/1350 .", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/AJJF7BH7DV3KC4Q43KDVGU2XIPXRJ7KH/", "slug": "rhyme" }, { "id": 23, "name": "Shuttle", "raw_name": "Shuttle", "category": "Signature", "family": "Lattice", "spec_url": "", "code_url": "", "notes": "The SHUTTLE-NIST reference implementation exposes crypto_sign_keypair, crypto_sign_signature and crypto_sign_verify; its polynomial matrix/short-vector construction and documented MLWE/MSIS assumptions establish Signature/Lattice. Evidence is the NIST-labelled implementation, not a verified ICCS submission package. Sources: https://github.com/Ji-Peng/SHUTTLE-NIST and https://github.com/Ji-Peng/SHUTTLE-NIST/blob/feff57d4e9f2798a82eaabda46494e73442249a6/ref/sign.c .", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/AOAU5JIQQTIQYH7LGFPMDI4EQAVDJM2C/", "slug": "shuttle" }, { "id": 24, "name": "Sigurd", "raw_name": "Sigurd", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "Reviewed the official thread (https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/A5LWDR4WYSLBQA55PEDVM5GTWL4SWJFH/); it identifies Sigurd but gives no algorithm description. The sources reviewed did not establish its primitive or security foundation, so category and family remain unverified.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/A5LWDR4WYSLBQA55PEDVM5GTWL4SWJFH/", "slug": "sigurd" }, { "id": 25, "name": "SQIsign2D^2", "raw_name": "SQIsign2D$^2$", "category": "Signature", "family": "Isogeny", "spec_url": "", "code_url": "https://github.com/Kaizhan-Lin/SQIsign2DSquare", "notes": "The authors explicitly describe SQIsign2D^2 as a digital signature using one- and two-dimensional isogenies. The named implementation has key_gen, signing and verify routines using these isogenies. Sources: https://eprint.iacr.org/2025/920 and https://github.com/Kaizhan-Lin/SQIsign2DSquare/blob/176634178cf8b42e7261eb383911ea5781a377d2/src/sqisign2d/sqisign2d.jl .", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/PXELFI4WKOOCWZAZGVWEN4TJWJUTMRU4/", "slug": "sqisign2d-square" }, { "id": 26, "name": "SQIsign2D-push^{1/2}", "raw_name": "SQIsign2D-push$^{1/2}$", "category": "Signature", "family": "", "spec_url": "", "code_url": "", "notes": "The official SQIsign name identifies a signature candidate: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/55H26TSNYGPQZRBE3NGNQVIDCPCUPI6Q/ . The related author paper https://eprint.iacr.org/2025/897 and implementation https://github.com/hiroshi-onuki/SQIsign2D-Push describe SQIsign2DPush, but do not establish the submitted push^{1/2} variant; its family remains unverified.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/55H26TSNYGPQZRBE3NGNQVIDCPCUPI6Q/", "slug": "sqisign2d-push-half" }, { "id": 27, "name": "SQIsignTriangle", "raw_name": "SQIsignTriangle", "category": "Signature", "family": "", "spec_url": "", "code_url": "", "notes": "The official SQIsign name identifies a signature candidate: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/463HDEM6EQ3FHMKNIT7LOT5T7CW7J7SJ/ . The reviewed thread has no construction details, and the sources reviewed did not establish the Triangle variant; family remains unverified.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/463HDEM6EQ3FHMKNIT7LOT5T7CW7J7SJ/", "slug": "sqisigntriangle" }, { "id": 28, "name": "SYDO", "raw_name": "SYDO", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "Reviewed the official thread (https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/F43FXLI3CJE33FWEIS6NUFNDL4VVJUUL/); it identifies SYDO but gives no algorithm description. The sources reviewed did not establish its primitive or security foundation, so category and family remain unverified.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/F43FXLI3CJE33FWEIS6NUFNDL4VVJUUL/", "slug": "sydo" }, { "id": 29, "name": "Tins", "raw_name": "Tins", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "The official thread identifies Tins but supplies no primitive or construction details. No matching technical source was verified; category and family remain unresolved. Sources: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/3LQUXPLSYUUHSKU4QWDFI6C3O4H3GXKF/", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/3LQUXPLSYUUHSKU4QWDFI6C3O4H3GXKF/", "slug": "tins" }, { "id": 30, "name": "TRINE", "raw_name": "TRINE", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "The official thread identifies TRINE but supplies no primitive or construction details. No matching technical source was verified; category and family remain unresolved. Sources: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/PHFOUHYOCTA42ALMCBKHF5JLD2HQGVXV/", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/PHFOUHYOCTA42ALMCBKHF5JLD2HQGVXV/", "slug": "trine" }, { "id": 31, "name": "TSUOV", "raw_name": "TSUOV", "category": "Signature", "family": "Multivariate", "spec_url": "", "code_url": "", "notes": "The authors explicitly introduce TSUOV as a UOV-based multivariate signature scheme using tensor-product constructions. Sources: https://eprint.iacr.org/2025/1778", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/BP4QW5XTWWAJOCTHWK64Z6L3LTCXEWIA/", "slug": "tsuov" }, { "id": 32, "name": "UVW", "raw_name": "UVW signature", "category": "Signature", "family": "", "spec_url": "", "code_url": "", "notes": "The official name explicitly identifies a signature scheme. No technical source verifying the UVW signature construction was located, so its family remains unresolved. Sources: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/KYXKYDE5L3DXFKASFNILENQKW4V73JXN/", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/KYXKYDE5L3DXFKASFNILENQKW4V73JXN/", "slug": "uvw-signature" }, { "id": 33, "name": "VDOO", "raw_name": "VDOO: Vinegar-Diagonal-Oil-Oil", "category": "Signature", "family": "Multivariate", "spec_url": "", "code_url": "", "notes": "The authors define VDOO (Vinegar-Diagonal-Oil-Oil) as a digital signature based on solving multivariate quadratic equations, with a diagonal layer added to an oil-vinegar construction. Sources: https://arxiv.org/abs/2312.09535", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/X2VGTA5L2EJJASOPF5TYJI2GAXDIO677/", "slug": "vdoo" }, { "id": 34, "name": "YuanYang.DSA", "raw_name": "YuanYang.DSA", "category": "Signature", "family": "", "spec_url": "", "code_url": "", "notes": "The official .DSA designation identifies a signature algorithm. No technical source verifying its security foundation was located; the name alone does not establish a hybrid construction. Sources: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/F2PXVI3WBEN5VAK7XPPPHV6MXXALAKFG/", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/F2PXVI3WBEN5VAK7XPPPHV6MXXALAKFG/", "slug": "yuanyang-dsa" }, { "id": 35, "name": "Aigis-Enc^+", "raw_name": "Aigis-Enc$^+$", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "The official thread names the plus variant without technical details. Available PQCP code implements a lattice KEM labelled Aigis-enc, but its identity with Aigis-Enc+ was not verified; category and family remain unresolved. Sources: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/HDMMQKVT6UFDKT56DVYCAUBTQ5GWSIFJ/ ; https://github.com/openHiTLS/PQCP/tree/main/src/Aigis-enc", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/HDMMQKVT6UFDKT56DVYCAUBTQ5GWSIFJ/", "slug": "aigis-enc-plus" }, { "id": 36, "name": "Amoeba", "raw_name": "Amoeba", "category": "KEM", "family": "Lattice", "spec_url": "", "code_url": "", "notes": "The authors explicitly construct Amoeba as a Ring-LWE KEM over general cyclotomic rings; its lattice security foundation is distinct from the NTT implementation technique. Sources: https://link.springer.com/chapter/10.1007/978-981-96-9098-5_9", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/OXTBKIPREWPX4YRV4BLRMLWND4R4DLTO/", "slug": "amoeba" }, { "id": 37, "name": "BAG-Loong", "raw_name": "BAG-Loong", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "The official thread identifies BAG-Loong but supplies no primitive or construction details. No matching technical source was verified; category and family remain unresolved. Sources: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/RIQCA4YWQIPGGI2BOXRMFEYCCHTY3NQY/", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/RIQCA4YWQIPGGI2BOXRMFEYCCHTY3NQY/", "slug": "bag-loong" }, { "id": 38, "name": "BAG-Piglet", "raw_name": "BAG-Piglet", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "The official thread identifies BAG-Piglet but supplies no primitive or construction details. No matching technical source was verified; category and family remain unresolved. Sources: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/QUDRCTIJQVCLQNOYCZKNQYUMZO7PPPF6/", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/QUDRCTIJQVCLQNOYCZKNQYUMZO7PPPF6/", "slug": "bag-piglet" }, { "id": 39, "name": "BIKE-MLThre", "raw_name": "BIKE-MLThre", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "The official thread identifies BIKE-MLThre but supplies no primitive or construction details. No matching technical source was verified; category and family remain unresolved. Sources: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/VMTRVK2D2DWBOKLWZHLFNQWRZB7USMUQ/", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/VMTRVK2D2DWBOKLWZHLFNQWRZB7USMUQ/", "slug": "bike-mlthre" }, { "id": 40, "name": "BRA", "raw_name": "BRA", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "The official thread identifies BRA but supplies no primitive or construction details. No matching technical source was verified; category and family remain unresolved. Sources: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/MDYQUVS5YFRUAGZJAZIJFIUTX7THNM6O/", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/MDYQUVS5YFRUAGZJAZIJFIUTX7THNM6O/", "slug": "bra" }, { "id": 41, "name": "BRQC", "raw_name": "BRQC", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "The official thread identifies BRQC but supplies no primitive or construction details. No matching technical source was verified; category and family remain unresolved. Sources: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/LA7GLQRH3VS64ISSPP6BPZ6QR75PAOVA/", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/LA7GLQRH3VS64ISSPP6BPZ6QR75PAOVA/", "slug": "brqc" }, { "id": 42, "name": "BW-KEM", "raw_name": "BW-KEM", "category": "KEM", "family": "Lattice", "spec_url": "", "code_url": "", "notes": "The author repository and paper identify BW-KEM as a Module-LWE KEM. Barnes-Wall lattices provide the encoding technique, while Module-LWE supplies the security foundation. Sources: https://github.com/SonglinCrypto/BW-KEM ; https://link.springer.com/chapter/10.1007/978-3-032-26731-3_3", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/WBK2RG2XR5VZVITNS53TVFJDBGER7T7P/", "slug": "bw-kem" }, { "id": 43, "name": "CheetahKEM", "raw_name": "CheetahKEM", "category": "KEM", "family": "", "spec_url": "", "code_url": "", "notes": "The official name explicitly identifies a KEM. No matching technical source was verified for its security foundation, so the family remains unresolved. Sources: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/3OMMI24JGKESHSRUVA5NJANKRHTQY7RM/", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/3OMMI24JGKESHSRUVA5NJANKRHTQY7RM/", "slug": "cheetahkem" }, { "id": 44, "name": "C-Multi-UR-AG", "raw_name": "C-Multi-UR-AG", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "The official thread gives no construction details. The related paper describes Multi-UR-AG rank-code encryption, but does not establish the identity or primitive of the named C-Multi-UR-AG variant; both fields remain unresolved. Sources: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/CDFH64HLL4OC7ABIDEASAHDTDQI4O3RU/ ; https://arxiv.org/abs/2207.01410", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/CDFH64HLL4OC7ABIDEASAHDTDQI4O3RU/", "slug": "c-multi-ur-ag" }, { "id": 45, "name": "COMPASS-KEM", "raw_name": "COMPASS-KEM", "category": "KEM", "family": "", "spec_url": "", "code_url": "", "notes": "The official name explicitly identifies a KEM. No matching technical source was verified for its security foundation, so the family remains unresolved. Sources: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/3ZXFAPIPIO3CVJHCQJ5AQ44UNTBIY4OP/", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/3ZXFAPIPIO3CVJHCQJ5AQ44UNTBIY4OP/", "slug": "compass-kem" }, { "id": 46, "name": "CTL", "raw_name": "CTL Algorithm", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "The official thread identifies CTL but supplies no primitive or construction details. No matching technical source was verified; category and family remain unresolved. Sources: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/XYXBZWLCJXTUZTNUFJCPYLEST5CC56AI/", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/XYXBZWLCJXTUZTNUFJCPYLEST5CC56AI/", "slug": "ctl" }, { "id": 47, "name": "DKEM", "raw_name": "DKEM (Ding Key Encapsulation)", "category": "KEM", "family": "", "spec_url": "", "code_url": "", "notes": "The official name expands DKEM as Ding Key Encapsulation, establishing KEM. No technical source for this named variant was verified; earlier Ding key-exchange work alone does not establish its family. Sources: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/RW5BIIFSPEM2HFHQ4N226TMBIRZ7TXF5/", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/RW5BIIFSPEM2HFHQ4N226TMBIRZ7TXF5/", "slug": "dkem" }, { "id": 48, "name": "DTRU", "raw_name": "DTRU", "category": "KEM", "family": "Lattice", "spec_url": "", "code_url": "", "notes": "The authors explicitly propose DTRU as an NTRU-based KEM responding to the ICCS call. Double E8 encoding supplies error correction; the security foundation remains NTRU lattices. Sources: https://eprint.iacr.org/2026/1701", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/7OIHLWTGECH3FYCUM3BEBJDAHMMLZRZK/", "slug": "dtru" }, { "id": 49, "name": "FLIT", "raw_name": "FLIT", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "The official thread identifies FLIT but supplies no primitive or construction details. No matching technical source was verified; category and family remain unresolved. Sources: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/H6SZDCUAWCTVQD7QOP7XDVHAHGWXHKHZ/", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/H6SZDCUAWCTVQD7QOP7XDVHAHGWXHKHZ/", "slug": "flit" }, { "id": 50, "name": "HARE", "raw_name": "HARE", "category": "KEM", "family": "Code-based", "spec_url": "", "code_url": "", "notes": "The authors define HARE as an HQC-based KEM using distance-informed erasure decoding and covering-code ciphertext compression. Its Hamming quasi-cyclic code foundation supports Code-based. Sources: https://eprint.iacr.org/2026/544", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/2Q2SLLCRMEJ2FOLOTDPGM7IUUZKUPUKF/", "slug": "hare" }, { "id": 51, "name": "Hybrid Equivalent Punctured and Quasi-Cyclic", "raw_name": "Hybrid Equivalent Punctured and Quasi-Cyclic", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "The official name does not specify a primitive or security assumption, and no matching technical source was verified. The words Hybrid, Punctured and Quasi-Cyclic alone do not establish category or family. Sources: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/2FLYI6DJUQ3YKJZXVGFFN4IQNPKXSHWU/", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/2FLYI6DJUQ3YKJZXVGFFN4IQNPKXSHWU/", "slug": "hybrid-equivalent-punctured-and-quasi-cyclic" }, { "id": 52, "name": "LoongKEM", "raw_name": "LoongKEM", "category": "KEM", "family": "", "spec_url": "", "code_url": "", "notes": "The official name explicitly identifies a KEM. No matching technical source was verified for its security foundation, so the family remains unresolved. Sources: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/G7IDTLL5NJ46PSNDO6ZVKFN5L4LPRS7N/", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/G7IDTLL5NJ46PSNDO6ZVKFN5L4LPRS7N/", "slug": "loongkem" }, { "id": 53, "name": "Lore", "raw_name": "Lore", "category": "KEM", "family": "Lattice", "spec_url": "", "code_url": "https://github.com/pq-CUC/Lore", "notes": "The author paper identifies Lore as an LWE-based KEM. The verified pq-CUC/Lore implementation exposes ciphertext/shared-secret encapsulation and decapsulation in api.h and kem.c; CRT compression and BCH coding do not change its lattice security foundation. Sources: https://eprint.iacr.org/2025/2093 ; https://github.com/pq-CUC/Lore/tree/main/Reference%20implementation/ref", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/37LSSFEFLBIAAXOMJXYRFAAYG5DRNK4X/", "slug": "lore" }, { "id": 54, "name": "MAMBA-Frost", "raw_name": "MAMBA-Frost", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "The official thread identifies MAMBA-Frost but supplies no primitive or construction details. No matching technical source was verified; category and family remain unresolved. Sources: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/DZASROHH4W6G64UKMRCCQJGQEUHQO4TC/", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/DZASROHH4W6G64UKMRCCQJGQEUHQO4TC/", "slug": "mamba-frost" }, { "id": 55, "name": "MAMBA-Viper", "raw_name": "MAMBA-Viper", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "The official thread identifies MAMBA-Viper but supplies no primitive or construction details. No matching technical source was verified; category and family remain unresolved. Sources: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/GVM4FAYEOQ7SAF5BDM6SKPLOTA547A5X/", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/GVM4FAYEOQ7SAF5BDM6SKPLOTA547A5X/", "slug": "mamba-viper" }, { "id": 56, "name": "Mithril", "raw_name": "Mithril", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "The official thread provides no primitive or construction details. No source linking this candidate to a specific Mithril construction was verified; unrelated same-name work is insufficient, so both fields remain unresolved. Sources: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/Z26K5NHQNMT4NHBNWZT7G6IZVVRCCZKO/", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/Z26K5NHQNMT4NHBNWZT7G6IZVVRCCZKO/", "slug": "mithril" }, { "id": 57, "name": "Mito", "raw_name": "Mito", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "Reviewed official entry https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/NPRY7XDT2ABEJK5GBZS53L4FW7VDZYMZ/ The thread identifies Mito but supplies no technical specification or implementation; category and security family remain unverified.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/NPRY7XDT2ABEJK5GBZS53L4FW7VDZYMZ/", "slug": "mito" }, { "id": 58, "name": "MORNING-Scabbard", "raw_name": "MORNING-Scabbard", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "Reviewed official entry https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/4KFYAFY5ZWKVT2D47LSNZP2LKIHBGPV7/ The thread identifies MORNING-Scabbard but supplies no technical specification or implementation; category and security family remain unverified.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/4KFYAFY5ZWKVT2D47LSNZP2LKIHBGPV7/", "slug": "morning-scabbard" }, { "id": 59, "name": "NEV", "raw_name": "NEV", "category": "KEM", "family": "Lattice", "spec_url": "", "code_url": "https://github.com/openHiTLS/PQCP", "notes": "PQCP identifies NEV as a KEM and documents ICCS SM3 known-answer tests: https://github.com/openHiTLS/PQCP . Its implementation samples small polynomials, constructs an NTRU quotient public key, and implements ciphertext encapsulation/decapsulation: https://github.com/openHiTLS/PQCP/blob/6bfd209ccb35ed68b2754bbdc3adfa558f4d71a3/src/nev/src/nev_engine.c . This establishes the lattice family; the author paper gives the NTRU/RLWE assumptions: https://eprint.iacr.org/2023/1298 .", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/7ZYN5QNIORSGBY3FNOE3DNCO43KZRVJA/", "slug": "nev" }, { "id": 60, "name": "NSS-HQC", "raw_name": "NSS-HQC", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "Reviewed official entry https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/P63ZUXHRI7QQZJ3YC6QXJYUXNGF5MMCO/ The thread identifies NSS-HQC but supplies no technical specification or implementation; category and security family remain unverified.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/P63ZUXHRI7QQZJ3YC6QXJYUXNGF5MMCO/", "slug": "nss-hqc" }, { "id": 61, "name": "NTRE", "raw_name": "NTRE Key Encapsulation Mechanism", "category": "KEM", "family": "", "spec_url": "", "code_url": "", "notes": "The official name explicitly identifies a key encapsulation mechanism: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/XPRXBWG46LFNJ4SUOZOGZM44VNIUPO34/ No verified technical source for this named variant establishes its security family.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/XPRXBWG46LFNJ4SUOZOGZM44VNIUPO34/", "slug": "ntre" }, { "id": 62, "name": "OAEP-NTRU", "raw_name": "OAEP-NTRU", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "Reviewed official entry https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/LOTU4OB6M7NAVL5OSUGTQO3L35IVP4R2/ The thread identifies OAEP-NTRU but supplies no technical specification or implementation; category and security family remain unverified.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/LOTU4OB6M7NAVL5OSUGTQO3L35IVP4R2/", "slug": "oaep-ntru" }, { "id": 63, "name": "Polar-KEM", "raw_name": "Polar-KEM", "category": "KEM", "family": "", "spec_url": "", "code_url": "", "notes": "The official name explicitly identifies a key encapsulation mechanism: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/SUWKT64BKLBIPDQMHPOBL3FDM4MRPVBJ/ No verified technical source for this named variant establishes its security family.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/SUWKT64BKLBIPDQMHPOBL3FDM4MRPVBJ/", "slug": "polar-kem" }, { "id": 64, "name": "PolarLAC", "raw_name": "PolarLAC", "category": "KEM", "family": "Lattice", "spec_url": "", "code_url": "https://github.com/openHiTLS/PQCP", "notes": "PQCP exposes PolarLAC encapsulation and decapsulation returning a ciphertext and shared secret: https://github.com/openHiTLS/PQCP/blob/6bfd209ccb35ed68b2754bbdc3adfa558f4d71a3/src/polarlac/src/polarlac.c . Its public key is a*s+e and encryption uses small secret/error polynomials, establishing a lattice construction; polar codes encode messages for error correction, not a separate code-based security assumption: https://github.com/openHiTLS/PQCP/blob/6bfd209ccb35ed68b2754bbdc3adfa558f4d71a3/src/polarlac/src/polarlac_pke.c .", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/VWVCIBQ3M7NQOWU25P7SY3XK3PCAJT4X/", "slug": "polarlac" }, { "id": 65, "name": "QIMEN-PIKE", "raw_name": "QIMEN-PIKE", "category": "KEM", "family": "Isogeny", "spec_url": "https://qimen.io/resources/main_PIKE.pdf", "code_url": "", "notes": "Specification v1.0, Sections 1.1 and 3.3, defines PIKE.KEM via a Fujisaki-Okamoto transform with ciphertext encapsulation and decapsulation. The construction relies on masked supersingular isogeny problems; it is a KEM, not NIKE. Sections 5 and 8 describe NGCC-1/2/3 parameters and security: https://qimen.io/resources/main_PIKE.pdf .", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/IRFTQQNWEALFDR27ZBMONU4M2KTRWQRS/", "slug": "qimen-pike" }, { "id": 66, "name": "Quasi-Cyclic Twisted McEliece", "raw_name": "Quasi-Cyclic Twisted McEliece Key Encapsulation Mechanism", "category": "KEM", "family": "", "spec_url": "", "code_url": "", "notes": "The official name explicitly identifies a key encapsulation mechanism: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/BKERBYXMUT27H3ZUTLBHCM7YJB5KVGZI/ No verified technical source for this named variant establishes its security family.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/BKERBYXMUT27H3ZUTLBHCM7YJB5KVGZI/", "slug": "quasi-cyclic-twisted-mceliece" }, { "id": 67, "name": "QUBE", "raw_name": "QUBE", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "Reviewed official entry https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/LVEV7LW46WHONQL6REREK4ZA7TWZT3RK/ The thread identifies QUBE but supplies no technical specification or implementation; category and security family remain unverified.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/LVEV7LW46WHONQL6REREK4ZA7TWZT3RK/", "slug": "qube" }, { "id": 68, "name": "Rudraksh2", "raw_name": "Rudraksh2", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "The official entry names Rudraksh2: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/A35C2JZDLERYJNKGAUECZ73T5Y64LCPT/ The available author paper describes the earlier MLWE KEM Rudraksh, not Rudraksh2; a source connecting the named variant to that construction was not found, so category and family remain unverified: https://eprint.iacr.org/2024/1170 .", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/A35C2JZDLERYJNKGAUECZ73T5Y64LCPT/", "slug": "rudraksh2" }, { "id": 69, "name": "Scloud+", "raw_name": "Scloud+", "category": "KEM", "family": "Lattice", "spec_url": "", "code_url": "https://github.com/scloudplus/scloudplus", "notes": "The named Scloud+ implementation exposes KEM key generation, encapsulation, and decapsulation: https://github.com/scloudplus/scloudplus . Its encryption code samples small secret/error matrices, forms A*S+E, and encrypts with S'A+E1 and S'B+E2, establishing the lattice/LWE construction: https://github.com/scloudplus/scloudplus/blob/088920a10bb5bb8e8270c6fc26ca2ea28cb5d609/Implementations/_shared/scloudplus_core/common/pke.c .", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/KZFYINTQPUTXVATTIXUONZ63TGNGQQ55/", "slug": "scloud-plus" }, { "id": 70, "name": "TRIKE", "raw_name": "TRIKE", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "Reviewed official entry https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/MFS7WQ3ZYDSMM4PIFN32QGZQ26BB4TGX/ The thread identifies TRIKE but supplies no technical specification or implementation; category and security family remain unverified.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/MFS7WQ3ZYDSMM4PIFN32QGZQ26BB4TGX/", "slug": "trike" }, { "id": 71, "name": "TriQ-KEM", "raw_name": "TriQ-KEM", "category": "KEM", "family": "", "spec_url": "", "code_url": "", "notes": "The official name explicitly identifies a key encapsulation mechanism: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/BKY3EZYVJHKKT2RJKK2IRE2X5V4UN4HO/ No verified technical source for this named variant establishes its security family.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/BKY3EZYVJHKKT2RJKK2IRE2X5V4UN4HO/", "slug": "triq-kem" }, { "id": 72, "name": "UVW", "raw_name": "UVW Key Encapsulation Mechanism", "category": "KEM", "family": "", "spec_url": "", "code_url": "", "notes": "The official name explicitly identifies a key encapsulation mechanism: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/2N7FVNDINZAC7ZES4OC5GGHIGPQVPCWL/ No verified technical source for this named variant establishes its security family.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/2N7FVNDINZAC7ZES4OC5GGHIGPQVPCWL/", "slug": "uvw" }, { "id": 73, "name": "Weaver", "raw_name": "Weaver", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "Reviewed official entry https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/OMIKZ7ZL4FLNNUIVD7CK7D4CGYJ5L3AD/ The thread identifies Weaver but supplies no technical specification or implementation; category and security family remain unverified.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/OMIKZ7ZL4FLNNUIVD7CK7D4CGYJ5L3AD/", "slug": "weaver" }, { "id": 74, "name": "YuanYang.KEM", "raw_name": "YuanYang.KEM", "category": "KEM", "family": "", "spec_url": "", "code_url": "", "notes": "The official name explicitly identifies a key encapsulation mechanism: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/JL5OIS2NICCPYKQGQWMHLTWTGEDK2OCW/ No verified technical source for this named variant establishes its security family.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/JL5OIS2NICCPYKQGQWMHLTWTGEDK2OCW/", "slug": "yuanyang-kem" }, { "id": 75, "name": "ZEN", "raw_name": "ZEN", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "Reviewed official entry https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/36OAZIFVEG3DLVR3ZU3TWYDA6KXOKN3T/ The thread identifies ZEN but supplies no technical specification or implementation; category and security family remain unverified.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/36OAZIFVEG3DLVR3ZU3TWYDA6KXOKN3T/", "slug": "zen" }, { "id": 76, "name": "ADKEX", "raw_name": "ADKEX (Authenticated Ding Key Exchange)", "category": "KEX", "family": "", "spec_url": "", "code_url": "", "notes": "The official name identifies key exchange: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/P4IG2W7BMLGEJGJGAYY73XAEE32GLCAJ/ No verified technical source establishes this variant's security family or a narrower exchange subtype.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/P4IG2W7BMLGEJGJGAYY73XAEE32GLCAJ/", "slug": "adkex" }, { "id": 77, "name": "AFS-KEX", "raw_name": "AFS-KEX", "category": "KEX", "family": "Lattice", "spec_url": "", "code_url": "", "notes": "Author Yunlei Zhao explicitly identifies AFS-KEX as the authenticated key-exchange construction in https://eprint.iacr.org/2026/1581 : https://mailarchive.ietf.org/arch/msg/cfrg/RqeFMKZwrhKyo_szmQDLQyQ77Zg/ . The paper describes a multi-message exchange using AFS-KEM and instantiates it with ML-KEM under the module-LWE assumption (Sections 5 and 7), establishing KEX/Lattice; other possible instantiations are not combined security foundations.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/ASJ42PGKD4VB5HP3LPBE22CN2FKALES7/", "slug": "afs-kex" }, { "id": 78, "name": "CreTAKE", "raw_name": "CreTAKE", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "Reviewed official entry https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/MIGUBFHREZ7R2KKULIIKQEU23BVFG3BX/ The thread identifies CreTAKE but supplies no technical specification or implementation; category and security family remain unverified.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/MIGUBFHREZ7R2KKULIIKQEU23BVFG3BX/", "slug": "cretake" }, { "id": 79, "name": "DKEX", "raw_name": "DKEX (Ding Key Exchange)", "category": "KEX", "family": "Lattice", "spec_url": "", "code_url": "", "notes": "The official expanded name is Ding Key Exchange: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/KC65HII7OYTVC6FOA5CNNGEQFDCLFZEW/ . The authors' presentation of the named scheme describes ephemeral Ring-LWE key exchange with public-key messages and reconciliation signals (slides 3 and 12), establishing KEX/Lattice: https://csrc.nist.gov/CSRC/media/Presentations/Ding-Key-Exchange/images-media/DING-KEY-EXCHANGE-April2018.pdf . ICCS-specific parameters have not been verified.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/KC65HII7OYTVC6FOA5CNNGEQFDCLFZEW/", "slug": "dkex" }, { "id": 80, "name": "Loom", "raw_name": "Loom", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "Reviewed official entry https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/QD663UPHHV3JOP7IEQUTEESR4LCALIDJ/ The thread identifies Loom but supplies no technical specification or implementation; category and security family remain unverified.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/QD663UPHHV3JOP7IEQUTEESR4LCALIDJ/", "slug": "loom" }, { "id": 81, "name": "MAMBA-NIKE", "raw_name": "MAMBA-NIKE", "category": "NIKE", "family": "", "spec_url": "", "code_url": "", "notes": "The official name explicitly identifies non-interactive key exchange: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/75NMUIOPYDJXY5WRYIBQ6FET6Z57UMPG/ . No author-linked specification or implementation establishing the security family was verified.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/75NMUIOPYDJXY5WRYIBQ6FET6Z57UMPG/", "slug": "mamba-nike" }, { "id": 82, "name": "NEV-AKE", "raw_name": "NEV-AKE", "category": "KEX", "family": "", "spec_url": "", "code_url": "", "notes": "The official NEV-AKE name identifies authenticated key exchange: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/VIYUCIMGK6I63JRWXBAM6FJ7U2XLGB5V/ The related author paper https://eprint.iacr.org/2023/1298 specifies NEV PKE/KEM, not this AKE variant or its authentication mechanism; its security family remains unverified.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/VIYUCIMGK6I63JRWXBAM6FJ7U2XLGB5V/", "slug": "nev-ake" }, { "id": 83, "name": "NIIKE", "raw_name": "NIIKE", "category": "", "family": "", "spec_url": "", "code_url": "", "notes": "The official entry supplies only the name NIIKE: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/6WRSHMUQOXTR62HBG3HEUHZEIYAIROLO/ No verified specification or implementation explains the acronym, confirms non-interactive derivation from published public keys, or establishes its security family; both fields remain unverified.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/6WRSHMUQOXTR62HBG3HEUHZEIYAIROLO/", "slug": "niike" }, { "id": 84, "name": "TriQ-KEX", "raw_name": "TriQ-KEX", "category": "KEX", "family": "", "spec_url": "", "code_url": "", "notes": "The official name identifies key exchange: https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/Y7MZTLMKIGHUVZCNIUAJQA33K4KU427Q/ No verified technical source establishes this variant's security family or a narrower exchange subtype.", "forum_url": "https://list.niccs.org.cn/archives/list/pkcforum@list.niccs.org.cn/thread/Y7MZTLMKIGHUVZCNIUAJQA33K4KU427Q/", "slug": "triq-kex" } ]