From f1259e71075db13271255db7d073ff6afea0da25 Mon Sep 17 00:00:00 2001 From: Vincent G Date: Tue, 13 May 2025 20:28:29 -0400 Subject: [PATCH] Clarify hash lock description to emphasize preimage-hash matching This commit updates the description of "Hash Locks" to improve technical accuracy and clarity. The previous phrasing: "Requires revealing a preimage that hashes to a specific value" has been replaced with: "Requires revealing a preimage that matches a specific hash value" --- decoding/outputs-scriptpubkey.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/decoding/outputs-scriptpubkey.mdx b/decoding/outputs-scriptpubkey.mdx index 654b264..3a1850d 100644 --- a/decoding/outputs-scriptpubkey.mdx +++ b/decoding/outputs-scriptpubkey.mdx @@ -85,7 +85,7 @@ The ScriptPubKey acts like a smart contract that defines how the bitcoins can be 1. **Single Signature**: Requires one digital signature from a specific public key 2. **Multi-signature**: Requires M-of-N signatures from a set of public keys 3. **Time Locks**: Prevents spending until a certain time or block height -4. **Hash Locks**: Requires revealing a preimage that hashes to a specific value +4. **Hash Locks**: Requires revealing a preimage that matches a specific hash value An empty or invalid ScriptPubKey will make the output unspendable,