Dataset guide 04
Bitcoin Hash160 List
Hash160 is the 20-byte result produced by applying RIPEMD-160 to a SHA-256 hash and appears in several standard Bitcoin locking-script constructions.
Hash160 and Bitcoin addresses
For a legacy P2PKH address, the encoded address contains a network prefix, a 20-byte public-key hash and a checksum. P2SH uses a similar address encoding around a script hash. The same-looking 40-character hexadecimal payload can therefore have different meaning depending on its script context.
A trustworthy export must preserve that distinction rather than treating every 20-byte value as interchangeable.
Why use a compact representation
Removing textual encoding and checksums reduces storage and comparison overhead. Sorted hexadecimal records can be streamed, partitioned or converted into fixed-width binary values for efficient offline processing.
Planned verification metadata
UTXO Forge plans to identify the source snapshot, included script families, byte order, encoding, deduplication rules and record count. Those details are essential for reproducing matches across independent tools.
Frequently asked
Questions about bitcoin hash160 list
Is Hash160 a private key?
No. It is a public hash value used in Bitcoin scripts and does not reveal the corresponding private key.
Does Hash160 cover Taproot?
No. Taproot uses a 32-byte x-only public key in P2TR outputs, so it requires a separate representation.