diff options
| author | nicolas.dorier <nicolas.dorier@gmail.com> | 2020-06-22 10:58:08 +0900 |
|---|---|---|
| committer | nicolas.dorier <nicolas.dorier@gmail.com> | 2020-06-22 10:58:40 +0900 |
| commit | e6418e5a769d7635824f2ad1bcfe4c720be897c2 (patch) | |
| tree | 4afa2f7b070e74036e6f4c96ac1621ea0bba2738 /bip-0078.mediawiki | |
| parent | 5e4cc6d8129a94c653187c38c0bb4a1122722a60 (diff) | |
| download | bips-e6418e5a769d7635824f2ad1bcfe4c720be897c2.tar.xz | |
Fix missing word
Diffstat (limited to 'bip-0078.mediawiki')
| -rw-r--r-- | bip-0078.mediawiki | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/bip-0078.mediawiki b/bip-0078.mediawiki index d1a14ff..90aa94f 100644 --- a/bip-0078.mediawiki +++ b/bip-0078.mediawiki @@ -351,7 +351,7 @@ For example, if the sender's scriptPubKey type is P2WPKH while the receiver's pa A receiver might run the payment server (generating the BIP21 invoice) on a different server than the payjoin server, which could be less trusted than the payment server. In such case, the payment server can signal to the sender, via the BIP21 parameter <code>pjos=0</code>, that they MUST disallow [[#output-substitution|payment output substitution]]. -A compromised payjoin server could still the hot wallet outputs of the receiver, but would not be able to re-route payment to himself. +A compromised payjoin server could steal the hot wallet outputs of the receiver, but would not be able to re-route payment to himself. ===Impacted heuristics=== |