Spongent: A lightweight hash function

Andrey Bogdanov, Miroslav Knežević, Gregor Leander, Deniz Toz, Kerem Varici, Ingrid Verbauwhede

    Research output: Chapter in Book/Report/Conference proceedingArticle in proceedingsResearchpeer-review


    This paper proposes spongent - a family of lightweight hash functions with hash sizes of 88 (for preimage resistance only), 128, 160, 224, and 256 bits based on a sponge construction instantiated with a present-type permutation, following the hermetic sponge strategy. Its smallest implementations in ASIC require 738, 1060, 1329, 1728, and 1950 GE, respectively. To our best knowledge, at all security levels attained, it is the hash function with the smallest footprint in hardware published so far, the parameter being highly technology dependent. spongent offers a lot of flexibility in terms of serialization degree and speed. We explore some of its numerous implementation trade-offs. We furthermore present a security analysis of spongent. Basing the design on a present-type primitive provides confidence in its security with respect to the most important attacks. Several dedicated attack approaches are also investigated. © 2011 International Association for Cryptologic Research.
    Original languageEnglish
    Title of host publicationCryptographic hardware and embedded systems - CHES 2011. Proceedings
    Publication date2011
    ISBN (Print)9783642239502
    Publication statusPublished - 2011
    Event13th International Workshop on Cryptographic Hardware and Embedded Systems - Nara, Japan
    Duration: 28 Sep 20111 Oct 2011
    Conference number: 13


    Conference13th International Workshop on Cryptographic Hardware and Embedded Systems
    SeriesLecture Notes in Computer Science


    • Spongent
    • Sponge construction
    • Hash function
    • RFID
    • Present
    • Lightweight cryptography
    • Low-power design
    • Low-cost cryptography


    Dive into the research topics of 'Spongent: A lightweight hash function'. Together they form a unique fingerprint.

    Cite this