Skip to content

Commit f36ca8f

Browse files
committed
Update recommendation for receiver and sender
1 parent a07fef5 commit f36ca8f

File tree

1 file changed

+3
-5
lines changed

1 file changed

+3
-5
lines changed

bip-0078.mediawiki

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -232,8 +232,9 @@ The receiver needs to do some check on the original PSBT before proceeding:
232232
* Non-interactive receivers (like a payment processor) need to check that the original PSBT is broadcastable. <code>*</code>
233233
* If the sender included inputs in the original PSBT owned by the receiver, the receiver must either return error <code>invalid-transaction</code> or make sure they do not sign those inputs in the payjoin proposal.
234234
* If the sender's inputs are all from the same scriptPubKey type, the receiver must match the same type. If the receiver can't match the type, they must return error <code>unavailable</code>.
235+
* Make sure that the inputs included in the original transaction has never been seen before. (Prevent [[#probing-attack|probing attacks]].)
235236
236-
<code>*</code>: Interactive receivers are not required to validate the original PSBT because they are not exposed to probing attacks.
237+
<code>*</code>: Interactive receivers are not required to validate the original PSBT because they are not exposed to [[#probing-attack|probing attacks]].
237238

238239
===Sender's payjoin proposal checklist===
239240

@@ -266,9 +267,6 @@ Note:
266267
Our method of checking the fee allows the receiver and the sender to batch payments in the payjoin transaction.
267268
It also allows the receiver to pay the fee for batching adding his own outputs.
268269

269-
On top of those check, it is recommended, but not required for the sender to check that:
270-
* If the sender is making a payjoin with a change (ie, not in the [[#spare-change|spare change]] case), make sure the receiver is paying for any batched output.
271-
272270
==Rationale==
273271

274272
There is several consequences of our proposal:
@@ -348,7 +346,7 @@ For this reason, during a [[#spare-change|spare change]] case, the receiver may
348346

349347
==Attack vectors==
350348

351-
===On the receiver side: UTXO probing attack===
349+
===<span id="probing-attack"></span>On the receiver side: UTXO probing attack===
352350

353351
When the receiver creates a payjoin proposal, they expose one or more inputs belonging to them.
354352

0 commit comments

Comments
 (0)