The IETF has published RFC 10024, defining three hybrid post-quantum key-agreement mechanisms for TLS 1.3.
The highest-security option combines P-384 with ML-KEM-1024. Its client key share is 1,665 bytes: 97 bytes for P-384 and 1,568 bytes for ML-KEM.
That distinction matters for blockchain infrastructure. ML-KEM protects how nodes establish encrypted connections. ML-DSA protects transaction authorization.
QoreChain uses ML-KEM-1024 between nodes and ML-DSA-87 for transaction security. A credible post-quantum claim should always identify the algorithm, the standard and the layer where it is enforced. $BTC
The highest-security option combines P-384 with ML-KEM-1024. Its client key share is 1,665 bytes: 97 bytes for P-384 and 1,568 bytes for ML-KEM.
That distinction matters for blockchain infrastructure. ML-KEM protects how nodes establish encrypted connections. ML-DSA protects transaction authorization.
QoreChain uses ML-KEM-1024 between nodes and ML-DSA-87 for transaction security. A credible post-quantum claim should always identify the algorithm, the standard and the layer where it is enforced. $BTC
