You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| Witness | Only if flags is 1 | Varies |`Witness`|| See [BIP 141](https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki). Note that Elements witnesses contain more data than Bitcoin witnesses. This extra data is described further below. |
@@ -104,7 +104,7 @@ SegWit transactions have one such witness for each input.
104
104
| Script Witness | Yes | Varies |`Vector<hex>`|| The vector represents the witness stack.<br>Can be empty (length of 0). |
105
105
| Peg-in Witness | Yes | Varies |`Vector<hex>`|| The vector represents the witness stack.<br>Can be empty (length of 0). |
106
106
107
-
The range proofs must be empty if their asociated amounts (issuance / inflation keys) are explicit.
107
+
The range proofs must be empty if their associated amounts (issuance / inflation keys) are explicit.
108
108
Refer [here](https://elementsproject.org/features/confidential-transactions/investigation) for more details on range proofs.
109
109
110
110
A non-empty peg-in witness stack should always have a length of 6, and the items should be interpreted as follows:
Copy file name to clipboardExpand all lines: doc/pset.mediawiki
+50Lines changed: 50 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -255,6 +255,56 @@ The currently defined elements per-input proprietary types are as follows:
255
255
|
256
256
| 0
257
257
| 2
258
+
|-
259
+
| Explicit Value
260
+
| <tt>PSBT_ELEMENTS_IN_EXPLICIT_VALUE = 0x11</tt>
261
+
| None
262
+
| No key data
263
+
| <tt><64-bit little endian int value></tt>
264
+
| The explicit value for the input being spent. If provided, <tt>PSBT_ELEMENTS_IN_VALUE_PROOF</tt> must be provided too. Must not be provided if the input's value in the UTXO is already explicit.
265
+
|
266
+
| 0
267
+
| 2
268
+
|-
269
+
| Explicit Value Proof
270
+
| <tt>PSBT_ELEMENTS_IN_VALUE_PROOF = 0x12</tt>
271
+
| None
272
+
| No key data
273
+
| <tt><rangeproof></tt>
274
+
| An explicit value rangeproof that proves that the value commitment in this input's UTXO matches the explicit value in <tt>PSBT_ELEMENTS_IN_EXPLICIT_VALUE</tt>. If provided, <tt>PSBT_ELEMENTS_IN_EXPLICIT_VALUE</tt> must be provided too.
275
+
|
276
+
| 0
277
+
| 2
278
+
|-
279
+
| Explicit Asset
280
+
| <tt>PSBT_ELEMENTS_IN_EXPLICIT_ASSET = 0x13</tt>
281
+
| None
282
+
| No key data
283
+
| <tt><32 byte asset tag></tt>
284
+
| The explicit asset for the input being spent. If provided, <tt>PSBT_ELEMENTS_IN_ASSET_PROOF</tt> must be provided too. Must not be provided if the input's asset in the UTXO is already explicit.
285
+
|
286
+
| 0
287
+
| 2
288
+
|-
289
+
| Explicit Asset Proof
290
+
| <tt>PSBT_ELEMENTS_IN_ASSET_PROOF = 0x14</tt>
291
+
| None
292
+
| No key data
293
+
| <tt><proof></tt>
294
+
| An asset surjection proof with this input's asset as the only asset in the input set in order to prove that the asset commitment in the UTXO matches the explicit asset in <tt>PSBT_ELEMENTS_IN_EXPLICIT_ASSET</tt>. If provided, <tt>PSBT_ELEMENTS_IN_EXPLICIT_ASSET</tt> must be provided too.
| A boolean flag. <tt>0x00</tt> indicates the issuance should not be blinded, <tt>0x01</tt> indicates it should be. If not specified, assumed to be <tt>0x01</tt>. Note that this does not indicate actual blinding status, but rather the expected blinding status prior to signing.
305
+
|
306
+
| 0
307
+
| 2
258
308
|}
259
309
260
310
The currently defined elements per-output proprietary types are as follows:
0 commit comments