Generate Keccak-384 hashes - the original 384-bit Keccak submission with capacity 768 and domain suffix 0x01.
About
Keccak-384 is the original Keccak submission variant producing 384-bit output using Keccak-f[1600] with capacity 768 and domain suffix 0x01, differing from SHA3-384 only in the padding suffix.
Specifications
Output Size384 bits
StandardKeccak submission to NIST SHA-3 competition
Standard Year2008
Use Cases
—Original Keccak specification compliance
—Ethereum ecosystem compatibility
—Research and academic applications
—Alternative padding to SHA3-384
—Medium-output Keccak requirements
Frequently Asked Questions
They differ only in padding suffix (0x01 vs 0x06). Keccak-384 is the original submission, SHA3-384 is NIST standardized. Use Keccak-384 for Ethereum compatibility or original specification compliance; SHA3-384 for NIST standards compliance.
Keccak-384 is rarely needed specifically. It's used when you need the original Keccak specification with 384-bit output. Most applications requiring 384-bit hashes use SHA3-384 for standards compliance or SHA-384 for SHA-2 compatibility.
Keccak-384 provides 192-bit collision resistance (birthday bound on 384 bits). This is considered very secure. For 256-bit security, use Keccak-512 or SHA3-512 with 512-bit outputs.