🧭RIPEMD-160

NEW

A 160-bit cryptographic hash function designed as a strengthened successor to RIPEMD and an alternative to SHA-1.

DESCRIPTION

RIPEMD-160 was introduced as a strengthened, 160-bit hash function to replace RIPEMD. It has seen niche adoption, notably in Bitcoin’s address derivation (via hash160 of SHA-256 followed by RIPEMD-160). No practical collisions are known as of today, though 160-bit hashes provide less security margin than newer 256-bit designs. For new systems, SHA-256 or SHA-3 is generally preferred, but RIPEMD-160 remains relevant for compatibility in legacy or protocol-specific contexts.

ALTERNATIVE DEFINITIONS

KU Leuven COSIC

RIPEMD-160 is a strengthened 160-bit hash function intended as an improvement over RIPEMD.

Designer-hosted summary; paraphrased due to offline generation.

Source

Bitcoin Wiki

RIPEMD-160 is used in Bitcoin to create addresses by hashing the SHA-256 hash of a public key.

Highlights protocol-specific use; paraphrased due to offline generation.

Source

RELATED TERMS

RIPEMD SHA-256 Bitcoin HMAC Collision Resistance Preimage Resistance Cryptographic Hash Function BLAKE2 Hash Function Keccak

COMPETING TERMS

SHA-1

KNOWLEDGE AREAS

Data Security Software Engineering

TARGET AUDIENCE

Security Architect Cybersecurity Engineer Software Developer DevOps Engineer IT Auditor

EXTERNAL SOURCES

• Wikipedia - RIPEMD
• KU Leuven - Authoritative RIPEMD-160 description.
• Bitcoin Developers - Explains hash160 in address derivation.
• IETF - Hash algorithm tests and definitions.

TOP QUESTIONS

Is RIPEMD-160 still secure?

No practical collisions are known, but 160-bit security margins are smaller than modern 256-bit hashes. Use SHA-256 or SHA-3 for new designs.

Category: Risks

Where is RIPEMD-160 used in practice?

It appears in Bitcoin’s address derivation and some legacy systems, mainly for compatibility.

Category: Application

How does RIPEMD-160 compare to SHA-1?

Both produce 160-bit digests, but SHA-1 is broken for collisions, whereas RIPEMD-160 has no practical collisions known to date.

Category: Distinction

Should I migrate away from RIPEMD-160?

Yes, for new applications choose SHA-256 or SHA-3. Maintain RIPEMD-160 where protocols require it.

Category: Recommendation

Is HMAC with RIPEMD-160 safe?

HMAC constructions remain robust even with some hash weaknesses, but standardized choices like HMAC-SHA-256 are preferred.

Category: BestPractice

Why was RIPEMD-160 created?

It strengthened the original RIPEMD design, aiming for improved security at 160-bit output.

Category: Background

What is a common misunderstanding about RIPEMD-160?

That it’s equivalent to SHA-1 security-wise; SHA-1 is broken for collisions, while RIPEMD-160 is not known to be.

Category: Misunderstanding

What is the digest size of RIPEMD-160?

It outputs a 160-bit (20-byte) hash.

Category: Definition

What are alternatives to RIPEMD-160?

SHA-256, SHA-3, or BLAKE2 provide stronger security margins and performance.

Category: Alternatives