Generated by GPT-5-mini| BLAKE2 | |
|---|---|
| Name | BLAKE2 |
| Designer | Jean-Philippe Aumasson, Samuel Neves, Zooko Wilcox-O'Hearn, and Christian Winnerlein |
| Introduced | 2012 |
| Derived from | BLAKE |
| Standardized by | IETF |
| Digest size | 256 or 512 bits (configurable) |
| Structure | HAIFA-like construction, ARX permutation |
| Rounds | 10/12 (configurable) |
BLAKE2 is a family of cryptographic hash functions designed for high performance and security, created as a successor to the BLAKE algorithm. It was developed by cryptographers associated with projects and organizations such as XKCP, NIST, and contributors with links to IETF work, aiming to provide a fast, secure alternative suitable for software and hardware contexts. The design emphasizes speed on general-purpose processors used by systems from Intel and ARM ecosystems while maintaining security properties sought by standards bodies like ISO and researchers at institutions such as École Polytechnique and CNRS.
BLAKE2 originates from the competition around the SHA-3 competition and shares genealogical ties with designs evaluated by panels including representatives from NIST, NSA, and academics from MIT, ETH Zurich, and EPFL. The designers—Jean-Philippe Aumasson, Samuel Neves, Zooko Wilcox-O'Hearn, and Christian Winnerlein—published specifications and reference code that influenced libraries used by projects such as OpenSSL, LibreSSL, GnuPG, and OpenSSH. Its acceptance in standards and software ecosystems involved reviews by experts affiliated with University of California, Berkeley, Princeton University, and industry groups like IETF working groups and IETF RFCs authors.
BLAKE2 uses an ARX (Addition-Rotation-XOR) permutation derived from its predecessor, tuned for implementation on processors from Intel, AMD, ARM, and IBM Power architectures. The function integrates a HAIFA-like wide-pipe construction favored in analyses by researchers at NIST and universities such as Cornell University and University of Cambridge. Features include keyed hashing suitable for applications by organizations like Google and Mozilla, a tree hashing mode used by systems from Amazon Web Services and Microsoft Azure, and personalization fields applicable in contexts like Blockchain and distributed systems developed by teams at Ethereum, Bitcoin, and Hyperledger. The design choices echo cryptographic principles discussed by scholars at Stanford University, Harvard University, and Yale University.
The family includes configurable versions targeted at different digest sizes and use cases, with implementations appearing in languages and platforms maintained by communities around GitHub, GitLab, Rust, Go (programming language), Python (programming language), and C (programming language). Notable projects and vendors integrating BLAKE2 code include OpenBSD, FreeBSD, Linux kernel contributors, and cryptographic libraries such as libsodium and BoringSSL. Hardware implementations were explored by teams at Xilinx, Intel FPGA, and research groups at ETH Zurich and TU Delft for acceleration in datacenter and embedded environments used by companies like Cisco Systems and Apple.
Security evaluations involved academic groups from École Normale Supérieure, Technical University of Munich, University of Luxembourg, and labs connected to CNRS and INRIA. Cryptanalysis work referenced methods employed in studies of SHA-2 and SHA-3 and compared resistance to length-extension attacks analyzed in seminars at Princeton University and Columbia University. Formal proofs and reductions came from collaborations between researchers at University College London and Karlsruhe Institute of Technology, while practical attack models were discussed by teams at Google and Microsoft Research. Peer-reviewed papers presented findings at conferences including CRYPTO, EUROCRYPT, and ASIACRYPT.
Benchmark studies from groups at Google, Facebook, Dropbox, and universities like UC San Diego and EPFL showed BLAKE2 outperforming several contemporaneous hashes on common CPU microarchitectures from Intel and ARM. Microbenchmarks released by contributors on GitHub and in publications compared throughput on single-core and multi-core setups typical of servers by Dell and Hewlett-Packard Enterprise. Comparisons against SHA-256, SHA-3, and MD5 were performed in cloud contexts by teams at Amazon Web Services and Microsoft Azure, with attention to branch prediction and vectorization features present in modern x86-64 and ARM64 processors.
Adoption stretches across systems and services from OpenSSH and GnuPG to container platforms from Docker and orchestration systems by Kubernetes contributors, with package managers like npm and Cargo (software) referencing BLAKE2 for integrity checks. Storage systems and filesystems in projects like ZFS, Btrfs, and cloud storage by Google Cloud Platform and AWS S3 have evaluated or integrated BLAKE2 for deduplication and content addressing used by teams at Dropbox and Box. In cryptocurrency and ledger projects such as Monero and Zcash communities, BLAKE2 variants were considered for hashing and proof systems alongside implementations researched by contributors from MIT Media Lab and Imperial College London.