summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorkallewoof <karljohan-alm@garage.co.jp>2021-06-15 15:49:20 +0900
committerGitHub <noreply@github.com>2021-06-15 15:49:20 +0900
commit65529b12bb01b9f29717e1735ce4d472ef9d9fe7 (patch)
treeb44f7a8ac04923f731d136461b14b74f23ccb7dc
parent127cdc3cdad11cc50fd14a5cc53c0de9253c0e20 (diff)
parent38d245421041b57ebc6f8e45b7c3a5322c5f9292 (diff)
downloadbips-65529b12bb01b9f29717e1735ce4d472ef9d9fe7.tar.xz
Merge pull request #1082 from molnard/patch-1
Fix word duplication
-rw-r--r--bip-0078.mediawiki2
1 files changed, 1 insertions, 1 deletions
diff --git a/bip-0078.mediawiki b/bip-0078.mediawiki
index 2e5a3db..3c2fe2e 100644
--- a/bip-0078.mediawiki
+++ b/bip-0078.mediawiki
@@ -209,7 +209,7 @@ In such case, the receiver will need to increase the fee of the transaction afte
* The sender's wallet software is using round fee rate.
If the sender's fee rate is always round, then a blockchain analyst can easily spot the transactions of the sender involving payjoin by checking if, when removing a single input to the suspected payjoin transaction, the resulting fee rate is round.
-To prevent this, the sender can agree to pay more more fee so the receiver make sure that the payjoin transaction fee is also round.
+To prevent this, the sender can agree to pay more fee so the receiver make sure that the payjoin transaction fee is also round.
* The sender's transaction is time sensitive.