RIPEMD-160 Hash Generator
Generate RIPEMD-160 hashes — used in Bitcoin address generation
How to Use the RIPEMD-160 Hash Generator
- Enter or paste text into the input field.
- Select Hex or Base64 output format.
- Click Generate Hash to compute the RIPEMD-160 digest.
RIPEMD-160 produces a 160-bit (20-byte) hash. It is commonly used in Bitcoin address generation and PGP fingerprints.
What is RIPEMD-160 Hashing?
RIPEMD-160 (RACE Integrity Primitives Evaluation Message Digest) is a 160-bit cryptographic hash function developed in Europe by Hans Dobbertin, Antoon Bosselaers, and Bart Preneel in 1996. It produces a 40-character hexadecimal output. RIPEMD-160 is globally celebrated for its pivotal role in Bitcoin address generation, where it is combined with SHA-256 (Hash160).
Common Uses
- Generating Bitcoin (BTC) and cryptocurrency public key addresses via Hash160
- PGP and GnuPG public key fingerprint calculations
- OpenPGP message authentication and legacy signature verification
- Alternative cryptographic validation where dual-algorithm security is required
Frequently Asked Questions
Why does Bitcoin use RIPEMD-160?
Satoshi Nakamoto designed Bitcoin addresses by hashing the public key first with SHA-256 and then with RIPEMD-160. This reduces the address length to 160 bits (creating shorter QR codes and addresses) and provides an extra layer of algorithmic diversity.
Is RIPEMD-160 vulnerable like SHA-1?
No practical collisions have been found for the full 160-bit RIPEMD algorithm. While older 128-bit variants were retired, RIPEMD-160 retains strong collision resistance.
What is Hash160?
Hash160 is the standard Bitcoin protocol terminology for `RIPEMD160(SHA256(data))`. It takes an input, runs SHA-256, and then passes the result through RIPEMD-160.
Notes from this implementation
Where this 40-character digest shows up
RIPEMD-160 is 160 bits, the same width as SHA-1, and a different function. Bitcoin P2PKH addresses hash the public key with SHA-256 and then RIPEMD-160 before Base58Check. If you are checking that step, hashing the hex key with SHA-1 instead will look plausible (40 hex characters) and be wrong.
The implementation here is the RIPEMD-160 compression function over the text you paste. It is not a Base58 encoder and it does not know what a Bitcoin address is. Paste the raw public-key bytes’ hex only if you have already decoded them to the bytes the spec hashes; pasting the address string hashes the characters of the address, which is a different operation.
Collision status
RIPEMD-160 has no public practical collision of the kind SHA-1 has, but it is an older design and new protocols should not adopt it for signatures. Keep the page for the address-derivation check and for archives that already committed to it.