@@ -200,25 +200,25 @@ The currently defined per-input types are defined as follows:
200
200
** Value: The UTF-8 encoded commitment message string for the proof-of-reserves. See [[bip-0127.mediawiki |BIP 127 ]] for more information.
201
201
*** <tt>{porCommitment} </tt>
202
202
203
- * Type: RIPEMD160 preimage <tt>PSBT_RIPEMD160 = 0x0a </tt>
203
+ * Type: RIPEMD160 preimage <tt>PSBT_IN_RIPEMD160 = 0x0a </tt>
204
204
** Key: The resulting hash of the preimage
205
205
*** <tt>{0x0a}|{20-byte hash} </tt>
206
206
** Value: The hash preimage, encoded as a byte vector, which must equal the key when run through the `RIPEMD160` algorithm
207
207
*** <tt>{preimage} </tt>
208
208
209
- * Type: SHA256 preimage <tt>PSBT_SHA256 = 0x0b </tt>
209
+ * Type: SHA256 preimage <tt>PSBT_IN_SHA256 = 0x0b </tt>
210
210
** Key: The resulting hash of the preimage
211
211
*** <tt>{0x0b}|{32-byte hash} </tt>
212
212
** Value: The hash preimage, encoded as a byte vector, which must equal the key when run through the `SHA256` algorithm
213
213
*** <tt>{preimage} </tt>
214
214
215
- * Type: HASH160 preimage <tt>PSBT_HASH160 = 0x0c </tt>
215
+ * Type: HASH160 preimage <tt>PSBT_IN_HASH160 = 0x0c </tt>
216
216
** Key: The resulting hash of the preimage
217
217
*** <tt>{0x0c}|{20-byte hash} </tt>
218
218
** Value: The hash preimage, encoded as a byte vector, which must equal the key when run through the `SHA256` algorithm followed by the `RIPEMD160` algorithm
219
219
*** <tt>{preimage} </tt>
220
220
221
- * Type: HASH256 preimage <tt>PSBT_HASH256 = 0x0d </tt>
221
+ * Type: HASH256 preimage <tt>PSBT_IN_HASH256 = 0x0d </tt>
222
222
** Key: The resulting hash of the preimage
223
223
*** <tt>{0x0d}|{32-byte hash} </tt>
224
224
** Value: The hash preimage, encoded as a byte vector, which must equal the key when run through the `SHA256` algorithm twice
0 commit comments