> For the complete documentation index, see [llms.txt](https://hub.bsvblockchain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.bsvblockchain.org/higher-learning/bsv-academy/bitcoin-primitives-hash-functions/ripemd-160-overview.md).
# RIPEMD-160 Overview
#### Why Learn About RIPEMD-160?
The other important hash function used in **BSV** is **RIPEMD-160**.
* You donβt need to know its inner workings to understand Bitcoin.
* But seeing its **design philosophy and history** helps highlight why itβs trusted and still relevant.
***
#### A Brief History of RIPE (Race Integrity Primitives Evaluation)
In the **1990s**, the **European Union** established the **RIPE consortium** to develop better **integrity primitives** (cryptographic tools to ensure data integrity).
At the time:
* The most popular hash functions were **MD4** and **MD5**, created by Ron Rivest.
* RIPE evaluated these and proposed **RIPEMD**, a stronger version of MD4.
π **RIPEMD** essentially ran **two parallel versions of MD4** with improvements to **bit shifts** and **word ordering**.
Shortly after, **SHA-1** was published by NIST as an MD5-based improvement.
***
#### RIPEMD-160
In **1995**, cryptographer **Hans Dobbertin** found **collisions** in the original RIPEMD.
* In response, **Dobbertin et al. (1996)** proposed **RIPEMD-160** and **RIPEMD-128**.
* Both are still considered **secure hash functions today**.
Key changes in **RIPEMD-160**:
* **160-bit output** (longer digest for stronger security).
* **Five rounds of compression** (instead of three).
* Carefully chosen **bit shifts (5β15 bits)**.
* Each message block rotated by **different amounts**.
* Shifts and constants chosen to avoid exploitable patterns.
Performance trade-offs:
* \~15% slower than **SHA-1**.
* Half as fast as the original **RIPEMD**.
* Four times slower than **MD4**.
* On modern processors, this **performance hit is negligible**.
π **Design philosophy:** Make the **minimum necessary changes** to strengthen RIPEMD while preserving confidence from MD4, MD5, and RIPEMD research.
***
#### Use Cases
* In **Bitcoin (and therefore, BSV)**, RIPEMD-160 is combined with SHA-256 to produce **HASH-160** (used in address creation).
* Outside Bitcoin, it is notably used in **PGP (Pretty Good Privacy)** for **email encryption**.
***
β **Summary:** RIPEMD-160 is a **secure, reliable, and efficient hash function** that balances **proven design principles** with **increased security**, making it suitable for long-term cryptographic use.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://hub.bsvblockchain.org/higher-learning/bsv-academy/bitcoin-primitives-hash-functions/ripemd-160-overview.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
