Merge pull request #3756 from bisq-network/release/v1.2.4

Release/v1.2.4

build.gradle

@@ -275,7 +275,7 @@ configure(project(':desktop')) {
     apply plugin: 'witness'
     apply from: '../gradle/witness/gradle-witness.gradle'
 
-    version = '1.2.3-SNAPSHOT'
+    version = '1.2.4-SNAPSHOT'
 
     mainClassName = 'bisq.desktop.app.BisqAppMain'
 

common/src/main/java/bisq/common/app/Version.java

@@ -27,7 +27,7 @@ public class Version {
     // VERSION = 0.5.0 introduces proto buffer for the P2P network and local DB and is a not backward compatible update
     // Therefore all sub versions start again with 1
     // We use semantic versioning with major, minor and patch
-    public static final String VERSION = "1.2.3";
+    public static final String VERSION = "1.2.4";
 
     public static int getMajorVersion(String version) {
         return getSubVersion(version, 0);

core/src/main/resources/i18n/displayStrings_de.properties

@@ -208,12 +208,12 @@ shared.learnMore=Mehr erfahren
 shared.dismiss=Verwerfen
 shared.selectedArbitrator=Gewählte Vermittler
 shared.selectedMediator=Gewählter Vermittler
-shared.selectedRefundAgent=Gewählte Vermittler
+shared.selectedRefundAgent=Gewählter Vermittler
 shared.mediator=Mediator
 shared.arbitrator=Vermittler
 shared.refundAgent=Vermittler
-shared.refundAgentForSupportStaff=Rückerstattung des Agenten
-shared.delayedPayoutTxId=Rückerstattung von Sicherheiten Transaktion-ID
+shared.refundAgentForSupportStaff=Rückerstattungsbeauftragten
+shared.delayedPayoutTxId=Rückerstattung von Sicherheiten Transaktions-ID
 
 
 ####################################################################
@@ -274,7 +274,7 @@ mainView.p2pNetworkWarnMsg.connectionToP2PFailed=Verbinden mit Bisq-Netzwerk feh
 mainView.walletServiceErrorMsg.timeout=Verbindung mit Bitcoin-Netzwerk aufgrund einer Zeitüberschreitung fehlgeschlagen.
 mainView.walletServiceErrorMsg.connectionError=Verbindung mit Bitcoin-Netzwerk aufgrund eines Fehlers fehlgeschlagen: {0}
 
-mainView.walletServiceErrorMsg.rejectedTxException=A transaction was rejected from the network.\n\n{0}
+mainView.walletServiceErrorMsg.rejectedTxException=Eine Transaktion wurde aus dem Netzwerk abgelehnt.\n\n{0}
 
 mainView.networkWarning.allConnectionsLost=Sie haben die Verbindung zu allen {0} Netzwerk-Peers verloren.\nMöglicherweise haben Sie Ihre Internetverbindung verloren oder Ihr Computer war im Standbymodus.
 mainView.networkWarning.localhostBitcoinLost=Sie haben die Verbindung zum localhost Bitcoinknoten verloren.\nBitte starten Sie die Bisq Anwendung neu, um mit anderen Bitcoinknoten zu verbinden oder starten Sie den localhost Bitcoinknoten neu.
@@ -376,9 +376,9 @@ offerbook.warning.noMatchingAccount.msg=Um dieses Angebot anzunehmen, müssen Si
 
 offerbook.warning.counterpartyTradeRestrictions=Dieses Angebot kann aufgrund von Handelsbeschränkungen der Gegenpartei nicht angenommen werden
 
-offerbook.warning.newVersionAnnouncement=Mit dieser Version der Software können Trading-Partner die Zahlungskonten der anderen verifizieren und unterzeichnen, um ein Netzwerk von vertrauenswürdigen Zahlungskonten zu erstellen.\n\nNach erfolgreichem Trading mit einem Partner mit einem verifizierten Zahlungskonto wird Ihr Zahlungskonto unterzeichnet und die Handelslimits werden nach einem bestimmten Zeitintervall aufgehoben (die Länge dieses Intervalls basiert auf der Verifizierungsmethode).\n\nWeitere Informationen zur Kontounterzeichnung finden Sie in der Dokumentation unter https://docs.bisq.network/payment-methods#account-signing.
+offerbook.warning.newVersionAnnouncement=Mit dieser Version der Software können Trading-Partner die Zahlungskonten der anderen verifizieren und unterzeichnen, um ein Netzwerk von vertrauenswürdigen Zahlungskonten zu erstellen.\n\nNach erfolgreichem Trading mit einem Partner mit einem verifizierten Zahlungskonto wird Ihr Zahlungskonto unterzeichnet und die Trade-Limits werden nach einem bestimmten Zeitintervall aufgehoben (die Länge dieses Intervalls basiert auf der Verifizierungsmethode).\n\nWeitere Informationen zur Kontounterzeichnung finden Sie in der Dokumentation unter https://docs.bisq.network/payment-methods#account-signing.
 
-popup.warning.tradeLimitDueAccountAgeRestriction.seller=Der zulässige Handelsbetrag ist aufgrund von Sicherheitseinschränkungen, die auf den folgenden Kriterien basieren, auf {0} begrenzt:\n- Das Konto des Käufers wurde nicht von einem Vermittler oder einem Partner unterzeichnet\n- Die Zeit seit der Unterzeichnung des Kontos des Käufers beträgt nicht mindestens 30 Tage\n- Die Zahlungsmethode für dieses Angebot gilt als riskant für Bankrückbuchungen\n\n{1}
+popup.warning.tradeLimitDueAccountAgeRestriction.seller=Der zulässige Trade-Betrag ist aufgrund von Sicherheitseinschränkungen, die auf den folgenden Kriterien basieren, auf {0} begrenzt:\n- Das Konto des Käufers wurde nicht von einem Vermittler oder einem Partner unterzeichnet\n- Die Zeit seit der Unterzeichnung des Kontos des Käufers beträgt nicht mindestens 30 Tage\n- Die Zahlungsmethode für dieses Angebot gilt als riskant für Bankrückbuchungen\n\n{1}
 popup.warning.tradeLimitDueAccountAgeRestriction.buyer=Der zulässige Trade-Betrag ist aufgrund von Sicherheitseinschränkungen, die auf den folgenden Kriterien basieren, auf {0} begrenzt:\n- Ihr Konto wurde nicht von einem Vermittler oder einem Partner unterzeichnet\n- Die Zeit seit der Unterzeichnung Ihres Kontos beträgt nicht mindestens 30 Tage\n- Die Zahlungsmethode für dieses Angebot gilt als riskant für Bankrückbuchungen\n\n{1}
 
 offerbook.warning.wrongTradeProtocol=Dieses Angebot benötigt eine andere Protokollversion, als die Version Ihrer Software.\n\nBitte überprüfen Sie, ob Sie die aktuellste Version installiert haben. Andernfalls hat der Nutzer, der das Angebot erstellt hat, eine ältere Version benutzt.\n\nNutzer können nicht mit inkompatiblen Protokollversionen handeln.
@@ -638,7 +638,7 @@ portfolio.pending.step3_seller.moneyGram=Der Käufer muss Ihnen die Authorisieru
 portfolio.pending.step3_seller.westernUnion=Der Käufer muss Ihnen die MTCN (Sendungsnummer) und ein Foto der Quittung per E-Mail zusenden.\nDie Quittung muss deutlich Ihren vollständigen Namen, Ihre Stadt, Ihr Land und den Betrag enthalten. Bitte überprüfen Sie Ihre E-Mail, wenn Sie die MTCN erhalten haben.\n\nNach dem Schließen dieses Pop-ups sehen Sie den Namen und die Adresse des BTC-Käufers, um das Geld von Western Union abzuholen.\n\nBestätigen Sie den Erhalt erst, nachdem Sie das Geld erfolgreich abgeholt haben!
 portfolio.pending.step3_seller.halCash=Der Käufer muss Ihnen den HalCash-Code als SMS zusenden. Außerdem erhalten Sie eine Nachricht von HalCash mit den erforderlichen Informationen, um EUR an einem HalCash-fähigen Geldautomaten abzuheben.\n\nNachdem Sie das Geld am Geldautomaten abgeholt haben, bestätigen Sie bitte hier den Zahlungseingang!
 
-portfolio.pending.step3_seller.bankCheck=Bitte überprüfen Sie auch, ob der Name des im Trading-Vertrag angegebenen Absenders mit dem Namen auf Ihrem Kontoauszug übereinstimmt:\nName des Absenders, pro Trade-Vertrag: {0}\n\nWenn die Namen nicht genau gleich sind, {1}
+portfolio.pending.step3_seller.bankCheck=\n\nBitte überprüfen Sie auch, ob der Name des im Trading-Vertrag angegebenen Absenders mit dem Namen auf Ihrem Kontoauszug übereinstimmt:\nName des Absenders, pro Trade-Vertrag: {0}\n\nWenn die Namen nicht genau gleich sind, {1}
 portfolio.pending.step3_seller.openDispute=bestätigen Sie den Zahlungseingang nicht. Eröffnen Sie stattdessen einen Konflikt, indem Sie \"alt + o\" oder \"option + o\" drücken.\n\n
 portfolio.pending.step3_seller.confirmPaymentReceipt=Zahlungserhalt bestätigen
 portfolio.pending.step3_seller.amountToReceive=Zu erhaltender Betrag
@@ -672,7 +672,6 @@ portfolio.pending.step5_buyer.takersMiningFee=Gesamte Mining-Gebühr
 portfolio.pending.step5_buyer.refunded=Rückerstattete Kaution
 portfolio.pending.step5_buyer.withdrawBTC=Ihre Bitcoins abheben
 portfolio.pending.step5_buyer.amount=Abzuhebender Betrag
-portfolio.pending.step5_buyer.signer=Indem Sie Ihre Bitcoins auszahlen, verifizieren Sie, dass die Gegenpartei gemäß dem Handelsprotokoll gehandelt hat.
 portfolio.pending.step5_buyer.withdrawToAddress=An diese Adresse abheben
 portfolio.pending.step5_buyer.moveToBisqWallet=Gelder in Bisq-Wallet bewegen
 portfolio.pending.step5_buyer.withdrawExternal=An externe Wallet abheben
@@ -706,9 +705,9 @@ portfolio.pending.openSupportTicket.headline=Support-Ticket öffnen
 portfolio.pending.openSupportTicket.msg=Bitte verwenden Sie diese Funktion nur in Notfällen, wenn Sie keinen \"Open support\" oder \"Open dispute\" Button sehen.\n\nWenn Sie ein Support-Ticket öffnen, wird der Trade unterbrochen und von einem Mediator oder Vermittler bearbeitet.
 
 portfolio.pending.timeLockNotOver=Sie müssen ≈{0} ({1} weitere Blöcke) warten, bevor Sie einen Vermittlungskonflikt eröffnen können.
-portfolio.pending.error.depositTxNull=The deposit transaction is null. You cannot open a dispute without a valid deposit transaction. Please go to \"Settings/Network info\" and do a SPV resync.\n\nFor further help please contact the Bisq support channel at the Bisq Keybase team.
-portfolio.pending.mediationResult.error.depositTxNull=The deposit transaction is null. The trade gets moved to the failed trades section.
-portfolio.pending.error.depositTxNotConfirmed=The deposit transaction is not confirmed. You can not open an arbitration dispute with an unconfirmed deposit transaction. Please wait until it is confirmed or go to \"Settings/Network info\" and do a SPV resync.\n\nFor further help please contact the Bisq support channel at the Bisq Keybase team.
+portfolio.pending.error.depositTxNull=Die Einzahlungstransaktion ist null. Sie können einen Streitfall nicht ohne eine gültige Einzahlungstransaktion eröffnen. Bitte gehen Sie zu \"Einstellungen/Netzwerkinformationen\" und führen Sie eine SPV-Resynchronisierung durch.\n\nFür weitere Hilfe wenden Sie sich bitte an den Bisq-Support-Kanal des Bisq Keybase Teams.
+portfolio.pending.mediationResult.error.depositTxNull=Die Einzahlungstransaktion ist Null. Der Trade wird in den Abschnitt für fehlgeschlagene Trades verschoben.
+portfolio.pending.error.depositTxNotConfirmed=Die Einzahlungstransaktion ist bestätigt. Sie können einen Vermittlungsfall nicht ohne eine bestätigte Einzahlungstransaktion eröffnen. Bitte warten Sie, bis sie bestätigt ist, oder gehen Sie zu \"Einstellungen/Netzwerkinformationen\" und führen Sie eine SPV-Resynchronisierung durch.\n\nFür weitere Hilfe wenden Sie sich bitte an den Bisq-Support-Kanal des Bisq Keybase Teams.
 
 portfolio.pending.notification=Benachrichtigung
 
@@ -740,7 +739,7 @@ portfolio.pending.mediationResult.headline=Vorgeschlagene Auszahlung aus der Med
 portfolio.pending.mediationResult.info.noneAccepted=Schließen Sie den Trade ab, indem Sie den Vorschlag des Mediators für die Trade-Auszahlung annehmen.
 portfolio.pending.mediationResult.info.selfAccepted=Sie haben den Vorschlag des Mediators angenommen. Warten Sie darauf, dass auch der Partner akzeptiert.
 portfolio.pending.mediationResult.info.peerAccepted=Ihr Trade-Partner hat den Vorschlag des Mediators angenommen. Akzeptieren Sie ihn auch?
-portfolio.pending.mediationResult.button=Lösungsvorschlag ansehen 
+portfolio.pending.mediationResult.button=Lösungsvorschlag ansehen
 portfolio.pending.mediationResult.popup.headline=Mediationsergebnis für Trade mit ID: {0}
 portfolio.pending.mediationResult.popup.headline.peerAccepted=Ihr Trade-Partner hat den Vorschlag des Mediators akzeptiert für Trade {0}
 portfolio.pending.mediationResult.popup.info=Der Mediator hat die folgende Auszahlung vorgeschlagen:\nSie erhalten: {0}\nIhr Trading-Partner erhält: {1}\n\nSie können diese vorgeschlagene Auszahlung akzeptieren oder ablehnen.\n\nMit der Annahme unterzeichnen Sie die vorgeschlagene Auszahlungstransaktion. Wenn Ihr Trading-Partner auch akzeptiert und unterzeichnet, wird die Auszahlung abgeschlossen und der Trade geschlossen.\n\nWenn einer oder beide von Ihnen den Vorschlag ablehnen, müssen Sie bis {2} (Block {3}) warten, um einen Konflikt in der zweiten Runde mit einem Vermittler zu eröffnen, der den Fall erneut untersuchen und eine Auszahlung auf der Grundlage seiner Erkenntnisse vornehmen wird.\n\nDer Vermittler kann eine geringe Gebühr (Gebühr maximal: die Kaution des Traders) als Entschädigung für seine Arbeit erheben. Der Idealfall wäre, dass beide Trader dem Vorschlag des Mediators zustimmen, da das Schlichtungsverfahren für außergewöhnliche Umstände gedacht ist, z.B. wenn ein Trader sicher ist, dass der Mediator keinen fairen Auszahlungsvorschlag gemacht hat (oder wenn der andere Trader nicht reagiert).\n\nMehr Details zum neuen Vermittlungsmodell:\nhttps://docs.bisq.network/trading-rules.html#arbitration
@@ -838,7 +837,7 @@ funds.tx.dustAttackTx.popup=Diese Transaktion sendet einen sehr kleinen BTC Betr
 support.tab.mediation.support=Mediation
 support.tab.arbitration.support=Vermittlung
 support.tab.legacyArbitration.support=Legacy-Vermittlung
-support.tab.ArbitratorsSupportTickets={0}s Tickets
+support.tab.ArbitratorsSupportTickets={0} Tickets
 support.filter=Liste filtern
 support.filter.prompt=Tragen sie Handel ID, Datum, Onion Adresse oder Kontodaten
 support.noTickets=Keine offenen Tickets vorhanden
@@ -873,7 +872,7 @@ support.sellerOfferer=BTC-Verkäufer/Ersteller
 support.buyerTaker=BTC-Käufer/Abnehmer
 support.sellerTaker=BTC-Verkäufer/Abnehmer
 
-support.backgroundInfo=Bisq ist kein Unternehmen, daher behandelt es Konflikte auf andere Weise.\n\nTrader können innerhalb der Anwendung über einen sicheren Chat auf dem Bildschirm für offene Trades kommunizieren, um zu versuchen, einen Konflikt selbst zu lösen. Wenn das nicht ausreicht, kann ein Mediator einschreiten und helfen. Der Mediator bewertet die Situation und gibt eine Empfehlung für die Auszahlung der Trade Funds. Wenn beide Händler diesen Vorschlag annehmen, ist die Auszahlungstransaktion abgeschlossen und der Trade geschlossen. Wenn einer oder beide Trader mit der vom Mediator empfohlenen Auszahlung nicht einverstanden sind, können sie ein Schiedsverfahren beantragen: Der Vermittler hat den dritten Schlüssel der Einzahlungstransaktion und wird die Auszahlung auf der Grundlage seiner Ergebnisse vornehmen.
+support.backgroundInfo=Bisq ist kein Unternehmen, daher behandelt es Konflikte unterschiedlich.\n\nTrader können innerhalb der Anwendung über einen sicheren Chat auf dem Bildschirm für offene Trades kommunizieren, um zu versuchen, Konflikte selbst zu lösen. Wenn das nicht ausreicht, kann ein Mediator einschreiten und helfen. Der Mediator wird die Situation bewerten und eine Auszahlung von Trade Funds vorschlagen. Wenn beide Trader diesen Vorschlag annehmen, ist die Auszahlungstransaktion abgeschlossen und der Trade geschlossen. Wenn ein oder beide Trader mit der vom Mediator vorgeschlagenen Auszahlung nicht einverstanden sind, können sie ein Vermittlungsverfahren beantragen, bei dem der Vermittler die Situation neu bewertet und, falls gerechtfertigt, dem Trader persönlich eine Rückerstattung leistet und die Rückerstattung dieser Zahlung vom Bisq DAO verlangt.
 support.initialInfo=Bitte geben Sie eine Beschreibung Ihres Problems in das untenstehende Textfeld ein. Fügen Sie so viele Informationen wie möglich hinzu, um die Zeit für die Konfliktlösung zu verkürzen.\n\nHier ist eine Checkliste für Informationen, die Sie angeben sollten:\n\t● Wenn Sie der BTC-Käufer sind: Haben Sie die Fiat- oder Altcoin-Überweisung gemacht? Wenn ja, haben Sie in der Anwendung auf die Schaltfläche "Zahlung gestartet" geklickt?\n\t● Wenn Sie der BTC-Verkäufer sind: Haben Sie die Fiat- oder Altcoin-Zahlung erhalten? Wenn ja, haben Sie in der Anwendung auf die Schaltfläche "Zahlung erhalten" geklickt?\n\t● Welche Version von Bisq verwenden Sie?\n\t● Welches Betriebssystem verwenden Sie?\n\t● Wenn Sie ein Problem mit fehlgeschlagenen Transaktionen hatten, überlegen Sie bitte, in ein neues Datenverzeichnis zu wechseln.\n\t Manchmal wird das Datenverzeichnis beschädigt und führt zu seltsamen Fehlern. \n\t Siehe: https://docs.bisq.network/backup-recovery.html#switch-to-a-new-data-directory\n\nBitte machen Sie sich mit den Grundregeln für den Konfliktprozess vertraut:\n\t● Sie müssen auf die Anfragen der {0}'' innerhalb von 2 Tagen antworten.\n\t● Mediatoren antworten innerhalb von 2 Tagen. Die Vermittler antworten innerhalb von 5 Werktagen.\n\t● Die maximale Frist für einen Konflikt beträgt 14 Tage.\n\t● Sie müssen mit den {1} zusammenarbeiten und die Informationen zur Verfügung stellen, die sie anfordern, um Ihren Fall zu bearbeiten.\n\t● Mit dem ersten Start der Anwendung haben Sie die Regeln des Konfliktdokuments in der Nutzervereinbarung akzeptiert.\n\nSie können mehr über den Konfliktprozess erfahren unter: {2}
 support.systemMsg=Systemnachricht: {0}
 support.youOpenedTicket=Sie haben eine Anfrage auf Support geöffnet.\n\n{0}\n\nBisq-Version: {1}
@@ -978,7 +977,7 @@ settings.net.inbound=eingehend
 settings.net.outbound=ausgehend
 settings.net.reSyncSPVChainLabel=SPV-Kette neu synchronisieren
 settings.net.reSyncSPVChainButton=SPV-Datei löschen und neu synchronisieren
-settings.net.reSyncSPVSuccess=The SPV chain file will be deleted on the next startup. You need to restart your application now.\n\nAfter the restart it can take a while to resync with the network and you will only see all transactions once the resync is completed.\n\nDepending on the number of transactions and the age of your wallet the resync can take up to a few hours and consumes 100% of CPU. Do not interrupt the process otherwise you have to repeat it.
+settings.net.reSyncSPVSuccess=Die SPV-Chain-Datei wird beim nächsten Start gelöscht. Sie müssen Ihre Anwendung jetzt neu starten.\n\nNach dem Neustart kann es eine Weile dauern, bis die Neusynchronisierung mit dem Netzwerk abgeschlossen ist, und Sie sehen erst nach Abschluss der Neusynchronisierung alle Transaktionen.\n\nAbhängig von der Anzahl der Transaktionen und dem Alter Ihrer Wallet kann die Resynchronisation bis zu einigen Stunden dauern und verbraucht 100% der CPU. Unterbrechen Sie den Prozess nicht, da Sie ihn sonst wiederholen müssen.
 settings.net.reSyncSPVAfterRestart=Die SPV-Kettendatei wurde gelöscht. Haben Sie bitte Geduld, es kann eine Weile dauern mit dem Netzwerk neu zu synchronisieren.
 settings.net.reSyncSPVAfterRestartCompleted=Die erneute Synchronisation ist jetzt abgeschlossen. Bitte starten Sie die Anwendung neu.
 settings.net.reSyncSPVFailed=Konnte SPV-Kettendatei nicht löschen.\nFehler: {0}
@@ -1011,7 +1010,7 @@ account.tab.mediatorRegistration=Mediator-Registrierung
 account.tab.refundAgentRegistration=Registrierung des Rückerstattungsbeauftragten
 account.tab.account=Konto
 account.info.headline=Willkommen in Ihrem Bisq-Konto
-account.info.msg=Hier können Sie Trading-Konten für nationale Währungen und Altcoins hinzufügen und Backups für Ihre Wallets & Kontodaten erstellen.\n\nEine leere Bitcoinwallet wurde erstellt, als Sie das erste Mal Bisq gestartet haben.\n\nWir empfehlen, dass Sie Ihre Bitcoin-Wallet-Seed-Wörter aufschreiben (siehe Tab oben) und sich überlegen ein Passwort hinzuzufügen, bevor Sie einzahlen. Bitcoin-Einzahlungen und Auszahlungen werden unter \"Gelder\" verwaltet.\n\nHinweis zu Privatsphäre & Sicherheit: da Bisq eine dezentralisierte Börse ist, bedeutet dies, dass all Ihre Daten auf ihrem Computer bleiben. Es gibt keine Server und wir haben keinen Zugriff auf Ihre persönlichen Informationen, Ihre Gelder oder selbst Ihre IP Adresse. Daten wie Bankkontonummern, Altcoin- & Bitcoinadressen, etc werden nur mit Ihrem Trading-Partner geteilt, um Trades abzuschließen, die Sie initiiert haben (im Falle eines Konflikts wird der Vermittler die selben Daten sehen wie Ihr Handelspartner).
+account.info.msg=Hier können Sie Trading-Konten für nationale Währungen und Altcoins hinzufügen und Backups für Ihre Wallets & Kontodaten erstellen.\n\nEine leere Bitcoin-Wallet wurde erstellt, als Sie das erste Mal Bisq gestartet haben.\n\nWir empfehlen, dass Sie Ihre Bitcoin-Wallet-Seed-Wörter aufschreiben (siehe Tab oben) und sich überlegen ein Passwort hinzuzufügen, bevor Sie einzahlen. Bitcoin-Einzahlungen und Auszahlungen werden unter \"Gelder\" verwaltet.\n\nHinweis zu Privatsphäre & Sicherheit: da Bisq eine dezentralisierte Börse ist, bedeutet dies, dass all Ihre Daten auf ihrem Computer bleiben. Es gibt keine Server und wir haben keinen Zugriff auf Ihre persönlichen Informationen, Ihre Gelder oder selbst Ihre IP-Adresse. Daten wie Bankkontonummern, Altcoin- & Bitcoinadressen, etc werden nur mit Ihrem Trading-Partner geteilt, um Trades abzuschließen, die Sie initiiert haben (im Falle eines Konflikts wird der Vermittler die selben Daten sehen wie Ihr Trading-Partner).
 
 account.menu.paymentAccount=Nationale Währungskonten
 account.menu.altCoinsAccountView=Altcoin-Konten
@@ -1038,7 +1037,7 @@ account.altcoin.popup.wallet.msg=Bitte stellen Sie sicher, dass Sie die Anforder
 account.altcoin.popup.wallet.confirm=Ich verstehe und bestätige, dass ich weiß, welche Wallet ich benutzen muss.
 account.altcoin.popup.upx.msg=Der Handel mit UPX auf Bisq setzt voraus, dass Sie die folgenden Anforderungen verstehen und erfüllen:\n\nFür das Senden von UPX müssen Sie entweder das offizielle uPlexa GUI-Wallet oder das uPlexa CLI-Wallet mit aktiviertem store-tx-info Flag verwenden (Standard in neuen Versionen). Bitte stellen Sie sicher, dass Sie auf den tx key zugreifen können, da dies bei einem Konfliktfall erforderlich wäre.\nuplexa-wallet-cli (verwenden Sie den Befehl get_tx_key)\nuplexa-wallet-gui (gehen Sie zum History Tab und klicken Sie auf (P) für den Zahlungsnachweis)\n\nBei normalen Blockexplorern ist der Transfer nicht verifizierbar.\n\nSie müssen dem Vermittler im Konfliktfall die folgenden Daten zur Verfügung stellen:\n- Der tx Private Key\n- Der Transaktionshash\n- Die öffentliche Adresse des Empfängers\n\nWenn Sie die oben genannten Daten nicht angeben oder wenn Sie eine inkompatible Wallet verwendet haben, verlieren Sie den Konfliktfall. Der UPX-Sender ist dafür verantwortlich, im Konfliktfall dem Vermittler die Verifizierung des UPX-Transfers nachzuweisen.\n\nEs ist keine Zahlungs-ID erforderlich, sondern nur die normale öffentliche Adresse.\nWenn Sie sich über diesen Prozess nicht sicher sind, besuchen Sie den uPlexa discord channel (https://discord.gg/vhdNSrV) oder den uPlexa Telegram Chat (https://t.me/uplexaOfficial), um weitere Informationen zu erhalten.
 account.altcoin.popup.arq.msg=Der Handel mit ARQ auf Bisq setzt voraus, dass Sie die folgenden Anforderungen verstehen und erfüllen:\n\nFür den Versand von ARQ müssen Sie entweder das offizielle ArQmA GUI-Wallet oder das ArQmA CLI-Wallet mit aktiviertem store-tx-info Flag verwenden (Standard in neuen Versionen). Bitte stellen Sie sicher, dass Sie auf den tx Key zugreifen können, da dies im Falle eines Konfliktes erforderlich wäre.\narqma-wallet-cli (verwenden Sie den Befehl get_tx_key)\narqma-wallet-gui (gehen Sie zur History Tab und klicken Sie auf (P) für den Zahlungsnachweis)\n\nBei normalen Blockexplorern ist der Transfer nicht verifizierbar.\n\nSie müssen dem Mediator oder Vermittler im Konfliktfall die folgenden Daten zur Verfügung stellen:\n- Der tx Private Key\n- Der Transaktionshash\n- Die öffentliche Adresse des Empfängers\n\nWenn Sie die oben genannten Daten nicht angeben oder wenn Sie eine inkompatible Wallet verwendet haben, verlieren Sie den Konfliktfall. Der ARQ-Sender ist im Fall eines Konflikts dafür verantwortlich, die Verifizierung des ARQ-Transfers dem Mediator oder Vermittler nachzuweisen.\n\nEs ist keine Zahlungs-ID erforderlich, sondern nur die normale öffentliche Adresse.\nWenn Sie sich über diesen Prozess nicht sicher sind, besuchen Sie den ArQmA Discord Channel (https://discord.gg/s9BQpJT) oder das ArQmA Forum (https://labs.arqma.com), um weitere Informationen zu erhalten.
-account.altcoin.popup.xmr.msg=Der Handel mit XMR auf Bisq setzt voraus, dass Sie die folgenden Anforderungen verstehen und erfüllen:\n\nFür das Senden von XMR müssen Sie entweder das offizielle Monero GUI-Wallet oder das Monero CLI-Wallet mit aktiviertem store-tx-info Flag verwenden (Standard in neuen Versionen). Bitte stellen Sie sicher, dass Sie auf den tx Key zugreifen können, da dies im Falle eines Konfliktes erforderlich wäre.\nmonero-wallet-cli (verwenden Sie den Befehl get_tx_key)\nmonero-wallet-gui (gehen Sie zur History Tab und klicken Sie auf (P) für den Zahlungsnachweis)\n\nZusätzlich zum XMR checktx tool (https://xmr.llcoins.net/checktx.html) kann die Verifizierung auch im Wallet durchgeführt werden.\nmonero-wallet-cli : mit dem Befehl (check_tx_key).\nmonero-wallet-gui : auf der Seite Advanced > Prove/Check.\nBei normalen Blockexplorern ist der Transfer nicht verifizierbar.\n\nSie müssen dem Mediator oder Vermittler im Konfliktfall die folgenden Daten zur Verfügung stellen:\n- Den tx Private Key\n- Den Transaktionshash\n- Die öffentliche Adresse des Empfängers\n\nWenn Sie die oben genannten Daten nicht angeben oder wenn Sie eine inkompatible Wallet verwendet haben, verlieren Sie den Konfliktfall. Der XMR-Sender ist im Fall eines Konflikts dafür verantwortlich, die Verifizierung des XMR-Transfers dem Mediator oder Schiedsrichter nachzuweisen.\n\nEs ist keine Zahlungs-ID erforderlich, sondern nur die normale öffentliche Adresse.\nWenn Sie sich über diesen Prozess nicht sicher sind, besuchen Sie (https://www.getmonero.org/resources/user-guides/prove-payment.html) oder das Monero-Forum (https://forum.getmonero.org), um weitere Informationen zu erhalten.
+account.altcoin.popup.xmr.msg=Trading XMR on Bisq requires that you understand and fulfill the following requirements:\n\nProve payments: since Monero is a private coin, some transaction details aren't publicly available in the blockchain, and, in case of a dispute, the mediator or arbitrator needs them to check if the transaction was really made. In Bisq, the sender of the XMR transaction is the one responsible for providing this information to the mediator or arbitrator in case of a dispute. In order to do that, you must send XMR using a wallet that provides the information required to prove the payment was made, which includes:\n\n- the transaction key (Tx Key, Tx Secret Key or Tx Private Key)\n- the transaction ID (Tx ID or Tx Hash)\n- the destination address (recipient's address)\n\nThis information can be found in the official Monero GUI & CLI wallets, MyMonero, and Exodus (desktop) as well as in Cake Wallet, MyMonero, and Monerujo (mobile), in the following locations:\n\n- Monero GUI: go to Transactions tab\n- Monero CLI: use the command get_tx_key TXID. The flag store-tx-info must be enabled (enabled by default in new versions)\n- Other wallets: go to Transactions history and search for Transaction key (Tx key or Secret key) and the destination address in a sent transaction. Save recipient address option must be enabled in Cake Wallet settings.\n\nIf you are using a wallet different from the mentioned above, please be sure you can access those three pieces of information.Since the transaction key and the destination address are stored in the Monero wallet software, and they cannot be recovered in the Monero blockchain, you should never delete or restore your Monero wallet before a Bisq trade is completed. Failure to provide the above data will result in losing the dispute case.\n\nCheck payments: with those three pieces of information, the verification that a quantity of Monero was sent to a specific address can be accomplished the following way:\n\n- Monero GUI: change wallet to Advanced mode and go to Advanced > Prove/check > Check Transaction\n- Monero CLI: use the command check_tx_key TXID TXKEY ADDRESS\n- XMR checktx tool (https://xmr.llcoins.net/checktx.html)\n- Explore Monero website (https://www.exploremonero.com/receipt)\n\nIf you are still not sure about this process, visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) to find more information or ask a question on the Monero support subreddit (https://www.reddit.com/r/monerosupport/).
 # suppress inspection "TrailingSpacesInProperty"
 account.altcoin.popup.msr.msg=Der Handel mit MSR auf Bisq setzt voraus, dass Sie die folgenden Anforderungen verstehen und erfüllen:\n\nFür den Versand von MSR müssen Sie entweder das offizielle Masari GUI Wallet, das Masari CLI Wallet mit dem aktivierten store-tx-info Flag (standardmäßig aktiviert) oder das Masari Web Wallet (https://wallet.getmasari.org) verwenden. Bitte stellen Sie sicher, dass Sie auf den tx Key zugreifen können, da dies im Falle eines Konfliktes erforderlich wäre.\nmasari-wallet-cli (verwenden Sie den Befehl get_tx_key)\nmasari-wallet-gui (gehen Sie zur History Tab und klicken Sie auf (P) für den Zahlungsnachweis).\n\nMasari Web Wallet (gehen Sie zum Konto -> Transaktionshistorie und lassen Sie Details zu Ihrer gesendeten Transaktion anzeigen)\n\nDie Verifizierung kann im Wallet durchgeführt werden.\nmasari-wallet-cli : mit dem Befehl (check_tx_key).\nmasari-wallet-gui : auf der Seite Advanced > Prove/Check.\nDie Verifizierung kann im Block-Explorer durchgeführt werden. \nÖffnen Sie den Block-Explorer (https://explorer.getmasari.org), verwenden Sie die Suchleiste, um Ihren Transaktionshash zu finden.\nSobald die Transaktion gefunden wurde, scrollen Sie nach unten zum Bereich 'Prove Sending' und geben Sie bei Bedarf Details ein.\nSie müssen dem Mediator oder Vermittler im Konfliktfall die folgenden Daten zur Verfügung stellen:\n- Den tx Private Key\n- Den Transaktionshash\n- Die öffentliche Adresse des Empfängers\n\nWenn Sie die oben genannten Daten nicht angeben oder wenn Sie eine inkompatible Wallet verwendet haben, verlieren Sie den Konfliktfall. Der MSR-Sender ist im Fall eines Konflikts dafür verantwortlich, die Verifizierung des MSR-Transfers dem Mediator oder Vermittler nachzuweisen.\n\nEs ist keine Zahlungs-ID erforderlich, sondern nur die normale öffentliche Adresse.\nWenn Sie sich über diesen Prozess nicht sicher sind, fragen Sie um Hilfe auf der offiziellen Masari Discord (https://discord.gg/sMCwMqs).
 account.altcoin.popup.blur.msg=Der Handel mit BLUR auf Bisq setzt voraus, dass Sie die folgenden Anforderungen verstehen und erfüllen:\n\nUm BLUR zu senden, müssen Sie die Blur Network CLI oder GUI Wallet verwenden. \n\nWenn Sie die CLI-Wallet verwenden, wird nach dem Senden eines Transfers ein Transaktionshash (tx ID) angezeigt. Sie müssen diese Informationen speichern. Unmittelbar nach dem Senden des Transfers müssen Sie den Private Key der Transaktion mit dem Befehl 'get_tx_key' ermitteln. Wenn Sie diesen Schritt nicht ausführen, können Sie den Key möglicherweise später nicht mehr abrufen. \n\nWenn Sie das Blur Network GUI Wallet verwenden, können Sie problemlos den Private Key der Transaktion und die Transaktion-ID im "History" Tab finden. Suchen Sie sofort nach dem Absenden die Transaktion, die von Interesse ist. Klicken Sie auf das Symbol "?" in der unteren rechten Ecke des Feldes, das die Transaktion enthält. Sie müssen diese Informationen speichern. \n\nFalls ein Vermittlungsverfahren erforderlich ist, müssen Sie einem Mediator oder Vermittler Folgendes vorlegen: 1.) die Transaktions-ID, 2.) den Private Key der Transaktion und 3.) die Adresse des Empfängers. Der Mediator oder Vermittler überprüft dann den BLUR-Transfer mit dem Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nWenn Sie dem Mediator oder Vermittler nicht die erforderlichen Informationen zur Verfügung stellen, verlieren Sie den Konfliktfall. In allen Konfliktfällen trägt der BLUR-Sender 100% der Verantwortung für die Verifizierung von Transaktionen gegenüber einem Mediator oder Vermittler. \n\nWenn Sie diese Anforderungen nicht verstehen, handeln Sie nicht auf Bisq. Als Erstes suchen Sie Hilfe im Blur Network Discord (https://discord.gg/dMWaqVW).
@@ -1169,6 +1168,7 @@ dao.lockedForVoteBalance=Zum wählen genutzt
 dao.lockedInBonds=In Kopplungen gesperrt
 dao.availableNonBsqBalance=Verfügbares nicht-BSQ-Guthaben (BTC)
 dao.totalBsqBalance=Gesamtes BSQ-Guthaben
+dao.reputationBalance=Merit Value (not spendable)
 
 dao.tx.published.success=Ihre Transaktion wurde erfolgreich veröffentlicht.
 dao.proposal.menuItem.make=Antrag erstellen
@@ -1961,7 +1961,7 @@ showWalletDataWindow.includePrivKeys=Private Schlüssel einbeziehen
 tacWindow.headline=Nutzervereinbarung
 tacWindow.agree=Ich stimme zu
 tacWindow.disagree=Ich stimme nicht zu und beende
-tacWindow.arbitrationSystem=Vermittlersystem
+tacWindow.arbitrationSystem=Dispute resolution
 
 tradeDetailsWindow.headline=Handel
 tradeDetailsWindow.disputedPayoutTxId=Transaktions-ID der strittigen Auszahlung:
@@ -2025,8 +2025,8 @@ popup.error.takeOfferRequestFailed=Es ist ein Fehler aufgetreten, als jemand ver
 
 error.spvFileCorrupted=Beim Einlesen der SPV-Kettendatei ist ein Fehler aufgetreten.\nDie SPV-Kettendatei ist möglicherweise beschädigt.\n\nFehlermeldung: {0}\n\nMöchten Sie diese löschen und neu synchronisieren?
 error.deleteAddressEntryListFailed=Konnte AddressEntryList-Datei nicht löschen.\nFehler: {0}
-error.closedTradeWithUnconfirmedDepositTx=The deposit transaction of the closed trade with the trade ID {0} is still unconfirmed.\n\nPlease do a SPV resync at \"Setting/Network info\" to see if the transaction is valid.
-error.closedTradeWithNoDepositTx=The deposit transaction of the closed trade with the trade ID {0} is null.\n\nPlease restart the application to clean up the closed trades list.
+error.closedTradeWithUnconfirmedDepositTx=Die Einzahlungstransaktion des geschlossenen Trades mit der Trade ID {0} ist noch immer unbestätigt.\n\nBitte führen Sie eine SPV-Resynchronisation unter \" Einstellungen/Netzwerkinformationen\" durch, um zu sehen, ob die Transaktion gültig ist.
+error.closedTradeWithNoDepositTx=Die Einzahlungstransaktion des geschlossenen Trades mit der Trade-ID {0} ist null.\n\nBitte starten Sie die Anwendung neu, um die Liste der geschlossenen Trades zu bereinigen.
 
 popup.warning.walletNotInitialized=Die Wallet ist noch nicht initialisiert
 popup.warning.wrongVersion=Sie verwenden vermutlich die falsche Bisq-Version für diesen Computer.\nDie Architektur Ihres Computers ist: {0}.\nDie installierten Bisq-Binärdateien sind: {1}.\nBitte fahren Sie Bisq herunter und installieren die korrekte Version ({2}).
@@ -2034,7 +2034,7 @@ popup.warning.incompatibleDB=Wir haben nicht kompatible Datenbankdateien entdeck
 popup.warning.startupFailed.twoInstances=Bisq läuft bereits. Sie können nicht zwei Instanzen von Bisq laufen lassen.
 popup.warning.cryptoTestFailed=Es scheint so, als würden Sie selbst kompilierte Binärdateien verwenden und wären nicht den Anweisung auf https://github.com/bisq-network/exchange/blob/master/doc/build.md#7-enable-unlimited-strength-for-cryptographic-keys gefolgt.\n\nWenn dies nicht der Fall ist und Sie die offiziellen Bisq-Binärdateien genutzt haben, erstellen Sie bitte einen Fehlerbericht auf der Github-Seite.\nFehler={0}
 popup.warning.tradePeriod.halfReached=Ihr Handel mit der ID {0} hat die Hälfte der maximal erlaubten Handelsdauer erreicht und ist immer noch nicht abgeschlossen.\n\nDie Handelsdauer endet am {1}\n\nBitte überprüfen Sie den Status Ihres Handels unter \"Portfolio/Offene Händel\" für weitere Informationen.
-popup.warning.tradePeriod.ended=Ihr Trade mit der ID {0} hat die maximal zulässige Trade-Periode erreicht und ist nicht abgeschlossen.\n\nDie Trade-Periode endete am {1}.\n\nBitte überprüfen Sie Ihren Trade unter \"Portfolio/Open Trades\", um den Mediator zu kontaktieren.
+popup.warning.tradePeriod.ended=Ihr Trade mit der ID {0} hat die maximal zulässige Trade-Periode erreicht und ist nicht abgeschlossen.\n\nDie Trade-Periode endete am {1}.\n\nBitte überprüfen Sie Ihren Trade unter \"Portfolio/Offene Trades\", um den Mediator zu kontaktieren.
 popup.warning.noTradingAccountSetup.headline=Sie haben kein Handelskonto eingerichtet
 popup.warning.noTradingAccountSetup.msg=Sie müssen ein nationales Währung- oder Altcoin-Konto einrichten, bevor Sie ein Angebot erstellen können.\nMöchten Sie ein Konto einrichten?
 popup.warning.noArbitratorsAvailable=Momentan sind keine Vermittler verfügbar.
@@ -2064,16 +2064,16 @@ popup.warning.mandatoryUpdate.dao=Bitte aktualisieren Sie auf die neueste Bisq-V
 popup.warning.disable.dao=Der Bisq DAO und BSQ sind temporär deaktiviert. Bitte besuchen sie das Bisq-Forum für weitere Informationen.
 popup.warning.burnBTC=Die Transaktion ist nicht möglich, da die Mininggebühren von {0} den übertragenen Betrag von {1} überschreiten würden. Bitte warten Sie, bis die Gebühren wieder niedrig sind, oder Sie mehr BTC zum übertragen angesammelt haben.
 
-popup.warning.openOffer.makerFeeTxRejected=The maker fee transaction for offer with ID {0} was rejected by the Bitcoin network.\nTransaction ID={1}.\nThe offer has been removed to avoid further problems.\nPlease go to \"Settings/Network info\" and do a SPV resync.\nFor further help please contact the Bisq support channel at the Bisq Keybase team.
+popup.warning.openOffer.makerFeeTxRejected=Die Verkäufergebühren-Transaktion für das Angebot mit der ID {0} wurde vom Bitcoin-Netzwerk abgelehnt.\nTransaktions-ID={1}.\nDas Angebot wurde entfernt, um weitere Probleme zu vermeiden.\nBitte gehen Sie zu \"Einstellungen/Netzwerkinformationen\" und führen Sie eine SPV-Resynchronisierung durch.\nFür weitere Hilfe wenden Sie sich bitte an den Bisq-Support-Kanal des Bisq Keybase Teams.
 
-popup.warning.trade.txRejected.tradeFee=trade fee
-popup.warning.trade.txRejected.deposit=deposit
-popup.warning.trade.txRejected=The {0} transaction for trade with ID {1} was rejected by the Bitcoin network.\nTransaction ID={2}}\nThe trade has been moved to failed trades.\nPlease go to \"Settings/Network info\" and do a SPV resync.\nFor further help please contact the Bisq support channel at the Bisq Keybase team.
+popup.warning.trade.txRejected.tradeFee=Trade-Gebühr
+popup.warning.trade.txRejected.deposit=Kaution
+popup.warning.trade.txRejected=Die {0} Transaktion für den Trade mit der ID {1} wurde vom Bitcoin-Netzwerk abgelehnt.\nTransaktions-ID={2}}\nDer Trade wurde in gescheiterte Trades verschoben.\nBitte gehen Sie zu \"Einstellungen/Netzwerkinformationen\" und führen Sie eine SPV-Resynchronisierung durch.\nFür weitere Hilfe wenden Sie sich bitte an den Bisq-Support-Kanal des Bisq Keybase Teams.
 
-popup.warning.openOfferWithInvalidMakerFeeTx=The maker fee transaction for offer with ID {0} is invalid.\nTransaction ID={1}.\nPlease go to \"Settings/Network info\" and do a SPV resync.\nFor further help please contact the Bisq support channel at the Bisq Keybase team.
+popup.warning.openOfferWithInvalidMakerFeeTx=Die Verkäufergebühren-Transaktion für das Angebot mit der ID {0} ist ungültig.\nTransaktions-ID={1}.\nBitte gehen Sie zu \"Einstellungen/Netzwerkinformationen\" und führen Sie eine SPV-Resynchronisierung durch.\nFür weitere Hilfe wenden Sie sich bitte an den Bisq-Support-Kanal des Bisq Keybase Teams.
 
-popup.warning.trade.depositTxNull=The trade with ID {0} has no deposit transaction set.\nPlease restart the application and if the problem remains move the trade to failed trades and report the problem to the Bisq support channel at the Bisq Keybase team.
-popup.warning.trade.depositTxNull.moveToFailedTrades=Move to failed trades
+popup.warning.trade.depositTxNull=Der Trade mit der ID {0} hat keine Einzahlungstransaktion gesetzt.\nBitte starten Sie die Anwendung neu und wenn das Problem weiterhin besteht, verschieben Sie den Trade in fehlgeschlagene Trades und melden Sie das Problem an den Bisq-Support-Kanal des Bisq Keybase Teams.
+popup.warning.trade.depositTxNull.moveToFailedTrades=Verschieben in fehlgeschlagene Trades
 
 popup.info.securityDepositInfo=Um sicherzustellen, dass beide Händler dem Handelsprotokoll folgen, müssen diese eine Kaution zahlen.\n\nDie Kaution bleibt in Ihrer lokalen Wallet, bis das Angebot von einem anderen Händler angenommen wurde.\nSie wird Ihnen zurückerstattet, nachdem der Handel erfolgreich abgeschlossen wurde.\n\nBitte beachten Sie, dass Sie die Anwendung laufen lassen müssen, wenn Sie ein offenes Angebot haben.\nWenn ein anderer Händler Ihr Angebot annehmen möchte ist es notwendig, dass Ihre Anwendung online ist und reagieren kann.\nStellen Sie sicher, dass Sie den Ruhezustand deaktiviert haben, da dieser Ihren Client vom Netzwerk trennen würde (Der Ruhezustand des Monitors ist kein Problem).
 
@@ -2152,7 +2152,7 @@ systemTray.show=Anwendungsfenster anzeigen
 systemTray.hide=Anwendungsfenster verstecken
 systemTray.info=Informationen zu Bisq
 systemTray.exit=Beenden
-systemTray.tooltip=Bisq: Das dezentrale Handelsnetzwerk
+systemTray.tooltip=Bisq: A decentralized bitcoin exchange network
 
 
 ####################################################################
@@ -2403,7 +2403,7 @@ payment.clearXchange.info=\tStellen Sie bitte sicher, dass Sie die Voraussetzung
 payment.moneyGram.info=Wenn MoneyGram verwendet wird, muss der BTC Käufer die MoneyGram und ein Foto der Quittung per E-Mail an den BTC-Verkäufer senden. Die Quittung muss den vollständigen Namen, das Land, das Bundesland des Verkäufers und den Betrag deutlich zeigen. Der Käufer bekommt die E-Mail-Adresse des Verkäufers im Handelsprozess angezeigt.
 payment.westernUnion.info=Wenn Western Union verwendet wird, muss der BTC Käufer die MTCN (Tracking-Nummer) und ein Foto der Quittung per E-Mail an den BTC-Verkäufer senden. Die Quittung muss den vollständigen Namen, die Stadt, das Land des Verkäufers und den Betrag deutlich zeigen. Der Käufer bekommt die E-Mail-Adresse des Verkäufers im Handelsprozess angezeigt.
 payment.halCash.info=Bei Verwendung von HalCash muss der BTC-Käufer dem BTC-Verkäufer den HalCash-Code per SMS vom Mobiltelefon senden.\n\nBitte achten Sie darauf, dass Sie den maximalen Betrag, den Sie bei Ihrer Bank mit HalCash versenden dürfen, nicht überschreiten. Der Mindestbetrag pro Auszahlung beträgt 10 EUR und der Höchstbetrag 600 EUR. Bei wiederholten Abhebungen sind es 3000 EUR pro Empfänger pro Tag und 6000 EUR pro Empfänger pro Monat. Bitte überprüfen Sie diese Limits bei Ihrer Bank, um sicherzustellen, dass sie die gleichen Limits wie hier angegeben verwenden.\n\nDer Auszahlungsbetrag muss ein Vielfaches von 10 EUR betragen, da Sie keine anderen Beträge an einem Geldautomaten abheben können. Die Benutzeroberfläche beim Erstellen und Annehmen eines Angebots passt den BTC-Betrag so an, dass der EUR-Betrag korrekt ist. Sie können keinen marktbasierten Preis verwenden, da sich der EUR-Betrag bei sich ändernden Preisen ändern würde.\n\nIm Streitfall muss der BTC-Käufer den Nachweis erbringen, dass er die EUR geschickt hat.
-payment.limits.info=Beachten Sie bitte, dass alle Banküberweisungen ein gewisses Rückbuchungsrisiko mitbringen.\n\nUm diese Risiko zu minimieren, setzt Bisq vor-Handel Grenzen basierend auf zwei Faktoren:\n\n1. Das erwartete Rückbuchungsrisiko für die genutzte Zahlungsmethode\n2. Das Alter des Kontos für diese Zahlungsmethode\n\nDas Konto, das Sie jetzt erstellen, ist neu und sein Alter ist null. So wie Ihr Konto über zwei Monate altert, wächst auch Ihre vor-Handel Grenze:\n\n● Während des 1sten Monats, ist Ihre vor-Handel Grenze {0}\n● Während des 2ten Monats, ist Ihre vor-Handel Grenze {1}\n● Nach dem 2ten Monat, ist Ihre vor-Handel Grenze {2}\n\nBeachten Sie bitte, dass es keine Grenze, wie oft Sie handeln können.
+payment.limits.info=Beachten Sie bitte, dass alle Banküberweisungen ein gewisses Rückbuchungsrisiko mit sich bringen.\n\nUm diese Risiko zu minimieren, setzt Bisq Per-Trade-Limits basierend auf zwei Faktoren:\n\n1. Das erwartete Rückbuchungsrisiko für die genutzte Zahlungsmethode\n2. Das Alter des Kontos für diese Zahlungsmethode\n\nDas Konto, das Sie jetzt erstellen, ist neu und sein Alter ist null. So wie Ihr Konto über zwei Monate altert, wächst auch Ihr Per-Trade-Limit:\n\n● Während des 1. Monats ist Ihr Per-Trade-Limit {0}\n● Während des 2. Monats ist Ihr Per-Trade-Limit {1}\n● Nach dem 2. Monat ist Ihr Per-Trade-Limit {2}\n\nBitte beachten Sie, dass es kein Limit für die Gesamtzahl der Trades gibt, die Sie tätigen können.
 payment.limits.info.withSigning=Um das Rückbuchungsrisiko zu begrenzen, setzt Bisq Limits für den Kauf pro Trade fest, die auf den folgenden 2 Faktoren basieren:\n\n1. Allgemeines Rückbuchungsrisiko für die Zahlungsmethode\n2. Status der Kontounterzeichnung\n\nDieses Zahlungskonto, das Sie gerade erstellt haben, birgt ein gewisses Rückbuchungsrisiko und ist noch nicht von einem Vermittler oder vertrauenswürdigen Partner unterzeichnet, so dass es auf den Kauf von {0} pro Trade beschränkt ist. Nach der Unterzeichnung erhöhen sich die Kauflimits wie folgt:\n\n● Vor der Unterzeichnung und bis zu 30 Tage nach der Unterzeichnung beträgt Ihr Kauflimit pro Trade {0}.\n● 30 Tage nach der Unterzeichnung wird Ihr Kauflimit pro Trade {1} betragen.\n● 60 Tage nach der Unterzeichnung wird Ihr Kauflimit pro Trade {2} betragen.\n\nVerkaufslimits sind von der Kontounterzeichnung nicht betroffen und steigen lediglich mit zunehmendem Alter des Kontos. Weitere Informationen finden Sie unter https://docs.bisq.network/payment-methods#account-signing.\n\nEs gibt keine Begrenzung der Anzahl der Trades, die Sie tätigen können.
 
 payment.cashDeposit.info=Bitte bestätigen Sie, dass Ihre Bank Bareinzahlungen in Konten von anderen Personen erlaubt. Zum Beispiel werden diese Einzahlungen bei der Bank of America und Wells Fargo nicht mehr erlaubt.
@@ -2627,7 +2627,7 @@ validation.mustBeDifferent=Ihre Eingabe muss vom aktuellen Wert abweichen
 validation.cannotBeChanged=Parameter kann nicht geändert werden
 validation.numberFormatException=Zahlenformat Ausnahme {0}
 validation.mustNotBeNegative=Eingabe darf nicht negativ sein
-validation.phone.missingCountryCode=Es wird ein zweistelliger Ländercode benötigt, um die Telefonnummer zu bestätigen
+validation.phone.missingCountryCode=Es wird eine zweistellige Ländervorwahl benötigt, um die Telefonnummer zu bestätigen
 validation.phone.invalidCharacters=Telefonnummer {0} enthält ungültige Zeichen
 validation.phone.insufficientDigits=Nicht genügend Ziffern in {0} für eine gültige Telefonnummer
 validation.phone.tooManyDigits=Zu viele Ziffern in {0} für eine gültige Telefonnummer

core/src/main/resources/i18n/displayStrings_el.properties

@@ -225,8 +225,8 @@ shared.delayedPayoutTxId=Ταυτότητα συναλλαγής επιστρο
 ####################################################################
 
 mainView.menu.market=Αγορά
-mainView.menu.buyBtc=Αγορά BTC
-mainView.menu.sellBtc=Πώληση BTC
+mainView.menu.buyBtc=Προσφορά BTC
+mainView.menu.sellBtc=Ζήτηση BTC
 mainView.menu.portfolio=Χαρτοφυλάκιο
 mainView.menu.funds=Κεφάλαια
 mainView.menu.support=Υποστήριξη
@@ -672,7 +672,6 @@ portfolio.pending.step5_buyer.takersMiningFee=Σύνολο αμοιβών εξό
 portfolio.pending.step5_buyer.refunded=Ποσό εγγύησης που επεστράφη
 portfolio.pending.step5_buyer.withdrawBTC=Ανάληψη bitcoin
 portfolio.pending.step5_buyer.amount=Ποσό προς ανάληψη
-portfolio.pending.step5_buyer.signer=Αποσύροντας τα bitcoin σου επιβεβαιώνεις πως η άλλη πλευρά έπραξε σύμφωνα με το πρωτόκολλο συναλλαγών.
 portfolio.pending.step5_buyer.withdrawToAddress=Μεταφορά στη διεύθυνση
 portfolio.pending.step5_buyer.moveToBisqWallet=Μετάφερε κεφάλαια στο πορτοφόλι Bisq.
 portfolio.pending.step5_buyer.withdrawExternal=Μεταφορά σε εξωτερικό ποσρτοφόλι
@@ -873,7 +872,7 @@ support.sellerOfferer=Πωλητής/Maker BTC
 support.buyerTaker=Αγοραστής/Taker BTC
 support.sellerTaker=Πωλητής/Taker BTC
 
-support.backgroundInfo=Το Bisq δεν είναι εταιρία και γι' αυτό διαχειρίζεται τις διενέξεις διαφορετικά.\n\nΟι συναλλασσόμενοι μπορούν να επικοινωνούν εντός της εφαρμογής μέσω ασφαλούς συνομιλίας στην οθόνη των ανοικτών συναλλαγών, ώστε να προσπαθήσουν να επιλύσουν μία διένεξη οι ίδιοι. Αν αυτό δεν είναι επαρκές, μία διαμεσολαβήτρια μπορεί να επέμβει για να βοηθήσει. Η διαμεσολαβήτρια θα αξιολογήσει την κατάσταση και θα κάνει πρόταση για την αποπληρωμή των κεφαλαίων της συναλλαγής. Αν και οι δύο συναλλασσόμενοι αποδεχτούν την πρόταση, η συναλλαγή ολοκληρώνεται και κλείνει. Αν μία ή και οι δύο συναλλασσόμενες διαφωνήσουν με την πρόταση του διαμεσολαβητή, μπορούν να ζητήσουν διαιτησία. Η διαιτητής κατέχει το τρίτο κλειδί της κατάθεσης και τα ολοκληρώσει την πληρωμή βασιζόμενη στα ευρήματά της.
+support.backgroundInfo=Bisq is not a company, so it handles disputes differently.\n\nTraders can communicate within the application via secure chat on the open trades screen to try solving disputes on their own. If that is not sufficient, a mediator can step in to help. The mediator will evaluate the situation and suggest a payout of trade funds. If both traders accept this suggestion, the payout transaction is completed and the trade is closed. If one or both traders do not agree to the mediator's suggested payout, they can request arbitration.The arbitrator will re-evaluate the situation and, if warranted, personally pay the trader back and request reimbursement for this payment from the Bisq DAO.
 support.initialInfo=\tΕισήγαγε μια περιγραφή του προβλήματός σου στο κάτωθι πεδίο. Συμπεριέλαβε όσο το δυνατόν περισσότερες πληροφορίες, ώστε να επιταχυνθεί ο χρόνος επίλυσης της διένεξης.\n\nΑκολουθεί μια λίστα με πληροφορίες που πρέπει να εισάγεις:\n\t● Αν είσαι ο αγοραστής BTC: Ολοκλήρωσες τη μεταφορά χρημάτων ή κρυπτονομισμάτων; Εάν ναι, πίεσες το κουμπί "'πληρωμή απεστάλη" της εφαρμογής;\n\t● Εάν είσαι ο πωλητής BTC: Έλαβες πληρωμή χρημάτων ή κρυπτονομισμάτων; Αν ναι, πίεσες το κουμπί "πληρωμή ελήφθη" της εφαρμογής;\n\t● Ποια έκδοση του Bisq χρησιμοποιείς;\n\t● Ποιο λειτουργικό χρησιμοποιείς;\n\t● Αν αντιμετώπισες κάποιο πρόβλημα με αποτυχημένες συναλλαγές, προσπάθησε να αλλάξεις το αρχείο δεδομένων.\n\t Μερικές φορές το αρχείο δεδομένων καταστρέφεται και προκαλεί απρόσμενα σφάλματα.\n\nΔες: https://docs.bisq.network/backup-recovery.html#switch-to-a-new-data-directory\n\nΕξοικειώσου με τους βασικούς κανόνες επίλυσης διένεξης:\n\t● Πρέπει να απαντήσεις στα αιτήματα του {0} εντός 2 ημερών.\n\t● Οι διαμεσολαβητές αποκρίνονται εντός 2 ημερών. Οι διαιτητές αποκρίνονται εντός 5 ημερών.\n\t● Η μέγιστη χρονικής περίοδος μιας διένεξης είναι 14 ημέρες.\n\t● Πρέπει να συνεργαστείς με τον {1} και να παραδώσεις τα στοιχεία που αιτείται ώστε να στοιχειοθετήσεις την υπόθεσή σου.\n\t● Αποδέχτηκες τους κανόνες που αναφέρονται στο έγγραφο διενέξεων στη συμφωνία χρήστη, όταν εκκίνησες για πρώτη φορά την εφαρμογή.\n\nΜπορείς να διαβάσεις περισσότερες λεπτομέρειες σχετικές με τη διαδικασία επίλυσης διενέξεων στο: {2}
 support.systemMsg=Μήνυμα συστήματος: {0}
 support.youOpenedTicket=Άνοιξες ένα αίτημα υποστήριξης.\n\n{0}\n\nΈκδοση Bisq: {1}
@@ -1038,7 +1037,7 @@ account.altcoin.popup.wallet.msg=Βεβαιώσου πως πληρείς τις
 account.altcoin.popup.wallet.confirm=Κατανοώ και επιβεβαιώνω πως γνωρίζω ποιο πορτοφόλι πρέπει να χρησιμοποιήσω.
 account.altcoin.popup.upx.msg=Trading UPX on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending UPX, you need to use either the official uPlexa GUI wallet or uPlexa CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nuplexa-wallet-cli (use the command get_tx_key)\nuplexa-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The UPX sender is responsible for providing verification of the UPX transfer to the arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit uPlexa discord channel (https://discord.gg/vhdNSrV) or the uPlexa Telegram Chat (https://t.me/uplexaOfficial) to find more information.
 account.altcoin.popup.arq.msg=Συναλλαγές με ARQ στο Bisq απαιτούν την κατανόηση και εκπλήρωση των ακόλουθων προαπαιτήσεων:\n\nΓια αποστολή ARQ απαιτείται η χρήση είτε του επίσημου ArQmA GUI πορτοφολιού, είτε του ArQmA CLI πορτοφολιού με ενεργοποιημένο το store-tx-info flag (προεπιλεγμένο σε νέες εκδόσεις). Βεβαιώσου πως έχεις πρόσβαση στο tx key, καθώς σε περίπτωση διένεξης θα χρειαστεί.\n\narqma-wallet-cli (χρησιμοποίησε την εντολή get_tx_key)\narqma-wallet-gui (πήγαινε στην καρτέλα history και πάτα το πλήκτρο (P) button για απόδειξη πληρωμής)\n\nΣε απλούς block explorers η συναλλαγή δεν είναι επαληθεύσιμη.\n\nΣε περίπτωση διένεξης θα χρειαστεί να προσφέρεις στον διαμεσολαβητή ή τη διαιτήτρια τις ακόλουθες πληροφορίες:\n- Το ιδιωτικό tx κλειδί\n- Το hash της συναλλαγής\n- Τη δημόσια διεύθυνση του παραλήπτη\n\nΕάν δεν μπορέσεις να προσφέρεις τις παραπάνω πληροφορίες ή αν χρησιμοποίησες ένα μη συμβατό πορτοφόλι, θα χάσεις την επίλυση της διένεξης. Ο αποστολέας ARQ είναι υπεύθυνος για την επιβεβαίωση της μεταφοράς ARQ στον διαμεσολαβητή ή τη διαιτήτρια σε περίπτωση διένεξης.\n\nΔεν απαιτείται η ταυτότητα πληρωμής, παρά μονάχα η δημόσια διεύθυνση.\nΕάν δεν είσαι σίγουρη σχετικά με τη διαδικασία, επισκέψου το discord κανάλι ArQmA  (https://discord.gg/s9BQpJT) ή το φόρουμ ArQmA (https://labs.arqma.com) για περαιτέρω πληροφορίες.
-account.altcoin.popup.xmr.msg=Συναλλαγές με XMR στο Bisq απαιτούν την κατανόηση και εκπλήρωση των ακόλουθων προαπαιτήσεων:\n\nΓια αποστολή XMR απαιτείται είτε η χρήση του επίσημου Monero GUI πορτοφολιού, είτε του Monero CLI πορτοφολιού με την επισήμανση store-tx-info ενεργοποιημένη (προεπιλεγμένη στις νεώτερες εκδόσεις). Βεβαιώσου πως έχεις πρόσβαση στο tx key, καθώς σε περίπτωση διένεξης θα χρειαστεί.\nΠορτοφόλι Monero CLI (χρησιμοποίησε την εντολή get_tx_key)\nΠορτοφόλι Monero GUI (πήγαινε στην καρτέλα History και πάτα το πλήκτρο (P) για απόδειξη πληρωμής)\n\nΕπιπροσθέτως του εργαλείου XMR checktx (https://xmr.llcoins.net/checktx.html) επιβεβαίωση μπορεί να επιτευχθεί και εντός των πορτοφολιών.\nΠορτοφόλι Monero CLI: με χρήση της εντολής (check_tx_key).\nΠορτοφόλι Monero GUI: στην καρτέλα Advanced > Prove/Check.\nΣε απλούς block explorers  η συναλλαγή δεν είναι επαληθεύσιμη.\n\nΣε περίπτωση διένεξης θα χρειαστεί να προσφέρεις στον διαμεσολαβητή ή τη διαιτήτρια τις ακόλουθες πληροφορίες:\n- Το ιδιωτικό tx κλειδί\n- Το hash της συναλλαγής\n- Τη δημόσια διεύθυνση του παραλήπτη\n\nΕάν δεν μπορέσεις να προσφέρεις τις παραπάνω πληροφορίες ή αν χρησιμοποίησες ένα μη συμβατό πορτοφόλι, θα χάσεις την επίλυση της διένεξης. Ο αποστολέας XMR είναι υπεύθυνος για την επιβεβαίωση της μεταφοράς XMR στον διαμεσολαβητή ή τη διαιτήτρια σε περίπτωση διένεξης.\n\nΔεν απαιτείται η ταυτότητα πληρωμής, παρά μονάχα η δημόσια διεύθυνση.\nΕάν δεν είσαι σίγουρη σχετικά με τη διαδικασία, μπορείς να επισκεφτείς το (https://www.getmonero.org/resources/user-guides/prove-payment.html) ή το φόρουμ του Monero (https://forum.getmonero.org) για περαιτέρω πληροφορίες.
+account.altcoin.popup.xmr.msg=Trading XMR on Bisq requires that you understand and fulfill the following requirements:\n\nProve payments: since Monero is a private coin, some transaction details aren't publicly available in the blockchain, and, in case of a dispute, the mediator or arbitrator needs them to check if the transaction was really made. In Bisq, the sender of the XMR transaction is the one responsible for providing this information to the mediator or arbitrator in case of a dispute. In order to do that, you must send XMR using a wallet that provides the information required to prove the payment was made, which includes:\n\n- the transaction key (Tx Key, Tx Secret Key or Tx Private Key)\n- the transaction ID (Tx ID or Tx Hash)\n- the destination address (recipient's address)\n\nThis information can be found in the official Monero GUI & CLI wallets, MyMonero, and Exodus (desktop) as well as in Cake Wallet, MyMonero, and Monerujo (mobile), in the following locations:\n\n- Monero GUI: go to Transactions tab\n- Monero CLI: use the command get_tx_key TXID. The flag store-tx-info must be enabled (enabled by default in new versions)\n- Other wallets: go to Transactions history and search for Transaction key (Tx key or Secret key) and the destination address in a sent transaction. Save recipient address option must be enabled in Cake Wallet settings.\n\nIf you are using a wallet different from the mentioned above, please be sure you can access those three pieces of information.Since the transaction key and the destination address are stored in the Monero wallet software, and they cannot be recovered in the Monero blockchain, you should never delete or restore your Monero wallet before a Bisq trade is completed. Failure to provide the above data will result in losing the dispute case.\n\nCheck payments: with those three pieces of information, the verification that a quantity of Monero was sent to a specific address can be accomplished the following way:\n\n- Monero GUI: change wallet to Advanced mode and go to Advanced > Prove/check > Check Transaction\n- Monero CLI: use the command check_tx_key TXID TXKEY ADDRESS\n- XMR checktx tool (https://xmr.llcoins.net/checktx.html)\n- Explore Monero website (https://www.exploremonero.com/receipt)\n\nIf you are still not sure about this process, visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) to find more information or ask a question on the Monero support subreddit (https://www.reddit.com/r/monerosupport/).
 # suppress inspection "TrailingSpacesInProperty"
 account.altcoin.popup.msr.msg=Trading MSR on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending MSR, you need to use either the official Masari GUI wallet, Masari CLI wallet with the store-tx-info flag enabled (enabled by default) or the Masari web wallet (https://wallet.getmasari.org). Please be sure you can access the tx key as that would be required in case of a dispute.\nmasari-wallet-cli (use the command get_tx_key)\nmasari-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nMasari Web Wallet (goto Account -> transaction history and view details on your sent transaction)\n\nVerification can be accomplished in-wallet.\nmasari-wallet-cli : using command (check_tx_key).\nmasari-wallet-gui : on the Advanced > Prove/Check page.\nVerification can be accomplished in the block explorer \nOpen block explorer (https://explorer.getmasari.org), use the search bar to find your transaction hash.\nOnce transaction is found, scroll to bottom to the 'Prove Sending' area and fill in details as needed.\nYou need to provide the mediator or arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The MSR sender is responsible for providing verification of the MSR transfer to the mediator or arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process, ask for help on the Official Masari Discord (https://discord.gg/sMCwMqs).
 account.altcoin.popup.blur.msg=Συναλλαγές με BLUR στο Bisq απαιτούν την κατανόηση και εκπλήρωση των ακόλουθων προαπαιτήσεων:\n\nΓια αποστολή BLUR απαιτείται η χρήση του πορτοφολιού Blur Network CLI ή GUI.\n\nΑν χρησιμοποιείς το CLI πορτοφόλι, θα εμφανιστεί το hash της συναλλαγής (tx ID) μετά την αποστολή της συναλλαγής. Απαιτείται να αποθηκεύσεις αυτή την πληροφορία. Αμέσως μετά την αποστολή της συναλλαγής, θα πρέπει να χρησιμοποιήσεις την εντολή 'get_tx_key' για να ανακτήσεις το ιδιωτικό κλειδί της συναλλαγής. Αν αμελήσεις να ολοκληρώσεις αυτό το βήμα, ίσως να μην καταφέρεις να ανακτήσεις το κλειδί αργότερα.\n\nΑν χρησιμοποιείς το πορτοφόλι Blur Network GUI, το ιδιωτικό κλειδί και η ταυτότητα της συναλλαγής μπορούν εύκολα να βρεθούν στην καρτέλα "History". Αμέσως μετά την αποστολή, βρες τη συναλλαγή. Πάτα το σύμβολο "?" στην κάτω δεξιά γωνία της οθόνης που περιλαμβάνει τη συναλλαγή. Θα πρέπει να αποθηκεύσεις αυτή την πληροφορία.\n\nΣε περίπτωση διένεξης θα χρειαστεί να προσφέρεις στον διαμεσολαβητή ή τη διαιτήτρια τις ακόλουθες πληροφορίες: 1.) Την ταυτότητα της συναλλαγής, 2.) Το ιδιωτικό κλειδί της συναλλαγής, και 3.) Τη διεύθυνση του παραλήπτη. Ο διαμεσολαβητής ή η διαιτήτρια θα μπορέσει έτσι να επιβεβαιώσει τη μεταφορά BLUR χρησιμοποιώντας τον Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nΕάν δεν μπορέσεις να προσφέρεις τις απαιτούμενες πληροφορίες προς τον διαμεσολαβητή ή τη διαιτήτρια θα έχει ως αποτέλεσμα να χάσεις την επίλυση της διένεξης. Σε όλες τις περιπτώσεις διένεξης ο αποστολέας BLUR είναι 100% υπεύθυνος για την επαλήθευση των συναλλαγών προς τον διαμεσολαβητή ή τη διαιτήτρια.\n\nΑν δεν κατανοείς αυτές τις απαιτήσεις, μην συναλλαχθείς στο Bisq. Πρώτα ζήτα βοήθεια στο Blur Network Discord (https://discord.gg/dMWaqVW).
@@ -1122,8 +1121,8 @@ account.notifications.dispute.message.msg=Έλαβες ένα μήνυμα δι
 account.notifications.marketAlert.title=Ειδοποιήσεις προσφορών
 account.notifications.marketAlert.selectPaymentAccount=Προσφορές που αντιστοιχούν στο λογαριασμό πληρωμών
 account.notifications.marketAlert.offerType.label=Είδος προσφορών για τις οποίες ενδιαφέρομαι
-account.notifications.marketAlert.offerType.buy=Προσφορές αγοράς (θέλω να πουλήσω BTC)
-account.notifications.marketAlert.offerType.sell=Προσφορές πώλησης (θέλω να αγοράσω BTC)
+account.notifications.marketAlert.offerType.buy=Ζήτηση (θέλω να πουλήσω BTC)
+account.notifications.marketAlert.offerType.sell=Προσφορά (θέλω να αγοράσω BTC)
 account.notifications.marketAlert.trigger=Διαφορά (%) τιμής προσφοράς
 account.notifications.marketAlert.trigger.info=Ορίζοντας τη διαφορά τιμής, θα λάβεις ειδοποίηση μονάχα όταν κοινοποιείται μια προσφορά η οποία ικανοποιεί (ή υπερβαίνει) τις απαιτήσεις σου. Παράδειγμα: θέλεις να πουλήσεις BTC, αλλά θέλεις να πουλήσεις με τουλάχιστον μία 2% αύξηση επί της τρέχουσας τιμής αγοράς. Εισάγοντας στο πεδίο 2% θα κατοχυρώσει πως θα λαμβάνεις ειδοποιήσεις μονάχα για προσφορές με αυξημένες τιμές κατά 2% (ή περισσότερο) από την τρέχουσα τιμή αγοράς.
 account.notifications.marketAlert.trigger.prompt=Ποσοστιαία διαφορά από τιμή αγοράς (π.χ. 2.50%, -0.50%, κλπ)
@@ -1169,6 +1168,7 @@ dao.lockedForVoteBalance=Χρησιμοποιημένα για ψηφοφορί
 dao.lockedInBonds=Locked in bonds
 dao.availableNonBsqBalance=Διαθέσιμο μη BSQ υπόλοιπο (BTC)
 dao.totalBsqBalance=Συνολικό υπόλοιπο BSQ
+dao.reputationBalance=Merit Value (not spendable)
 
 dao.tx.published.success=Η συναλλαγή σου κοινοποιήθηκε επιτυχώς.
 dao.proposal.menuItem.make=Κατάθεσε πρόταση
@@ -1961,7 +1961,7 @@ showWalletDataWindow.includePrivKeys=Επισύναψη ιδιωτικού κλ
 tacWindow.headline=Συμφωνητικό χρήσης
 tacWindow.agree=Συμφωνώ
 tacWindow.disagree=Διαφωνώ και έξοδος
-tacWindow.arbitrationSystem=Σύστημα διαμεσολάβησης
+tacWindow.arbitrationSystem=Dispute resolution
 
 tradeDetailsWindow.headline=Συναλλαγή
 tradeDetailsWindow.disputedPayoutTxId=Ταυτότητα αμφισβητούμενης συναλλαγής αποπληρωμής:
@@ -2152,7 +2152,7 @@ systemTray.show=Εμφάνιση παραθύρου εφαρμογής
 systemTray.hide=Απόκρυψη παραθύρου εφαρμογής
 systemTray.info=Πληροφορίες σχετικά με το Bisq
 systemTray.exit=Έξοδος
-systemTray.tooltip=Bisq: Αποκεντρωμένο χρηματιστηριακό δίκτυο
+systemTray.tooltip=Bisq: A decentralized bitcoin exchange network
 
 
 ####################################################################

core/src/main/resources/i18n/displayStrings_es.properties

@@ -274,7 +274,7 @@ mainView.p2pNetworkWarnMsg.connectionToP2PFailed=Fallo conectándose a la red Bi
 mainView.walletServiceErrorMsg.timeout=Error al conectar a la red Bitcoin en el  límite de tiempo establecido.
 mainView.walletServiceErrorMsg.connectionError=La conexión a la red Bitcoin falló por un error: {0}
 
-mainView.walletServiceErrorMsg.rejectedTxException=A transaction was rejected from the network.\n\n{0}
+mainView.walletServiceErrorMsg.rejectedTxException=Se rechazó una transacción desde la red.\n\n{0}
 
 mainView.networkWarning.allConnectionsLost=Perdió la conexión a todos los {0} usuarios de red.\nTal vez se ha interrumpido su conexión a Internet o su computadora estaba en modo suspendido.
 mainView.networkWarning.localhostBitcoinLost=Perdió la conexión al nodo Bitcoin localhost.\nPor favor reinicie la aplicación Bisq para conectarse a otros nodos Bitcoin o reinice el nodo Bitcoin localhost.
@@ -672,7 +672,6 @@ portfolio.pending.step5_buyer.takersMiningFee=Comisiones de minado totales
 portfolio.pending.step5_buyer.refunded=Depósito de seguridad devuelto
 portfolio.pending.step5_buyer.withdrawBTC=Retirar bitcoins
 portfolio.pending.step5_buyer.amount=Cantidad a retirar
-portfolio.pending.step5_buyer.signer=Retirando sus bitcoins, verifica que la contraparte ha actuado de acuerdo al protocolo de intercambio.
 portfolio.pending.step5_buyer.withdrawToAddress=Retirar a la dirección
 portfolio.pending.step5_buyer.moveToBisqWallet=Mover fondos a la billetera Bisq
 portfolio.pending.step5_buyer.withdrawExternal=Retirar al monedero externo
@@ -706,9 +705,9 @@ portfolio.pending.openSupportTicket.headline=Abrir ticket de soporte
 portfolio.pending.openSupportTicket.msg=Por favor use esta función solo en caso de emergencia si no se muestra el botón \"Abrir soporte\" o \"Abrir disputa\".\n\nCuando abra un ticket de soporte el intercambio se interrumpirá y será manejado por un mediador o un árbitro.
 
 portfolio.pending.timeLockNotOver=Tiene hasta ≈{0} ({1} bloques más) antes de que pueda abrir una disputa de arbitraje.
-portfolio.pending.error.depositTxNull=The deposit transaction is null. You cannot open a dispute without a valid deposit transaction. Please go to \"Settings/Network info\" and do a SPV resync.\n\nFor further help please contact the Bisq support channel at the Bisq Keybase team.
-portfolio.pending.mediationResult.error.depositTxNull=The deposit transaction is null. The trade gets moved to the failed trades section.
-portfolio.pending.error.depositTxNotConfirmed=The deposit transaction is not confirmed. You can not open an arbitration dispute with an unconfirmed deposit transaction. Please wait until it is confirmed or go to \"Settings/Network info\" and do a SPV resync.\n\nFor further help please contact the Bisq support channel at the Bisq Keybase team.
+portfolio.pending.error.depositTxNull=La transacción de depósito es inválida. No puede abrir una disputa sin una transacción de depósito válida. Por favor vaya a \"Configuración/Información de red\" y haga una resincronización SPV.\n\nPara obtener ayuda contacte con el equipo de soporte en el canal Bisq de Keybase.
+portfolio.pending.mediationResult.error.depositTxNull=El dpósito de transacción es inválido. El intercambio se elimina a la sección de intercambios fallidos.
+portfolio.pending.error.depositTxNotConfirmed=El depósito de transacción no se ha confirmado. No puede abrir una disputa de arbitraje con una transacción de depósito no confirmada. Por favor espere a que se confirme o vaya a \"Configuración/Información de red\" y haga una resincronización SPV.\n\nPara más ayuda por favor contacte con el equipo de soporte en el canal Bisq de Keybase.
 
 portfolio.pending.notification=Notificación
 
@@ -873,7 +872,7 @@ support.sellerOfferer=vendedor/creador BTC
 support.buyerTaker=comprador/Tomador BTC
 support.sellerTaker=vendedor/Tomador BTC
 
-support.backgroundInfo=Bisq no es una compañía, por ello maneja las disputas de una forma diferente.\n\nLos compradores y vendedores pueden comunicarse a través de la aplicación por un chat seguro en la pantalla de intercambios abiertos para intentar resolver una disputa por su cuenta. Si eso no es suficiente, un mediador puede intervenir para ayudar. El mediador evaluará la situación y dará una recomendación para el pago de los fondos de la transacción. Si ambos aceptan esta sugerencia, la transacción del pago se completa y el intercambio se cierra. Si uno o ambos no están de acuerdo con el pago recomendado por el mediador, pueden solicitar arbitraje (hasta v1.2). El árbitro tiene la tercera llave de la transacción de depósito y hará el pago basado en sus hallazgos.
+support.backgroundInfo=Bisq no es una compañía, por ello maneja las disputas de una forma diferente.\n\nLos compradores y vendedores pueden comunicarse a través de la aplicación por un chat seguro en la pantalla de intercambios abiertos para intentar resolver una disputa por su cuenta. Si eso no es suficiente, un mediador puede intervenir para ayudar. El mediador evaluará la situación y dará una recomendación para el pago de los fondos de la transacción. Si ambos aceptan esta sugerencia, la transacción del pago se completa y el intercambio se cierra. Si uno o ambos no están de acuerdo con el pago recomendado por el mediador, pueden solicitar arbitraje. El árbitro re-evaluará la situación y, si es necesario, hará el pago personalmente y solicitará un reembolso de este pago a la DAO de Bisq.
 support.initialInfo=Por favor, introduzca una descripción de su problema en el campo de texto de abajo. Añada tanta información como sea posible para agilizar la resolución de la disputa.\n\nEsta es una lista de la información que usted debe proveer:\n\t● Si es el comprador de BTC: ¿Hizo la transferencia Fiat o Altcoin? Si es así, ¿Pulsó el botón 'pago iniciado' en la aplicación?\n\t● Si es el vendedor de BTC: ¿Recibió el pago Fiat o Altcoin? Si es así, ¿Pulsó el botón 'pago recibido' en la aplicación?\n\t● ¿Qué versión de Bisq está usando?\n\t● ¿Qué sistema operativo está usando?\n\t● Si tiene problemas con transacciones fallidas, por favor considere cambiar a un nuevo directorio de datos.\n\tA veces el directorio de datos se corrompe y causa errores extraños.\n\tVer: https://docs.bisq.network/backup-recovery.html#switch-to-a-new-data-directory\n\nPor favor, familiarícese con las reglas básicas del proceso de disputa:\n\t● Tiene que responder a los requerimientos de {0} en 2 días.\n\t● Los mediadores responden en 2 días. Los árbitros responden en 5 días laborables.\n\t● El periodo máximo para una disputa es de 14 días.\n\t● Tiene que cooperar con {1} y proveer la información necesaria que soliciten.\n\t● Aceptó la reglas esbozadas en el documento de disputa en el acuerdo de usuario cuando inició por primera ver la aplicación.\n\nPuede leer más sobre el proceso de disputa en: {2}
 support.systemMsg=Mensaje de sistema: {0}
 support.youOpenedTicket=Ha abierto una solicitud de soporte.\n\n{0}\n\nVersión Bisq: {1}
@@ -978,7 +977,7 @@ settings.net.inbound=entrante
 settings.net.outbound=saliente
 settings.net.reSyncSPVChainLabel=Resincronizar cadena SPV
 settings.net.reSyncSPVChainButton=Borrar archivo SPV y resincronizar
-settings.net.reSyncSPVSuccess=The SPV chain file will be deleted on the next startup. You need to restart your application now.\n\nAfter the restart it can take a while to resync with the network and you will only see all transactions once the resync is completed.\n\nDepending on the number of transactions and the age of your wallet the resync can take up to a few hours and consumes 100% of CPU. Do not interrupt the process otherwise you have to repeat it.
+settings.net.reSyncSPVSuccess=El archivo de cadena SPV se borrará en el siguiente inicio. Necesita reiniciar la aplicación ahora.\n\nDespués del reinicio puede llevar un rato resincronizar con la red y verá todas las transacciones una vez completada la resincronización.\n\nDependiendo de el número de transacciones y la edad de su monedero la resincronización puede llevar unas horas y consume el 100% de la CPU. No interrumpa el proceso o tendrá que repetirlo.
 settings.net.reSyncSPVAfterRestart=La cadena SPV ha sido borrada. Por favor, sea paciente. Puede llevar un tiempo resincronizar con la red.
 settings.net.reSyncSPVAfterRestartCompleted=La resincronización se ha completado. Por favor, reinicie la aplicación.
 settings.net.reSyncSPVFailed=No se pudo borrar el archivo de cadena SPV\nError: {0}
@@ -1038,11 +1037,11 @@ account.altcoin.popup.wallet.msg=Por favor, asegúrese que sigue los requisitos
 account.altcoin.popup.wallet.confirm=Entiendo y confirmo que sé qué monedero tengo que utilizar.
 account.altcoin.popup.upx.msg=Para intercambiar UPX en bisq es preciso que usted entienda y cumpla los siguientes requerimientos:\n\nPara enviar upx es preciso que use el monedero oficial de uPlexa GUI o el de uPlexa CLI con la opción "store-tx-info" habilitada (predeterminada en las nuevas versiones). Por favor, asegúrese de poder acceder a las llaves tx, ya que podrían requerirse en caso de disputa.\nuplexa-wallet-cli (utilice el comando get_tx_key)\nuplexa-wallet-gui (vaya a la pestaña historial y haga clic en el botón (P) para prueba de pago).\nEn los exploradores de bloques normales la transferencia no es verificable.\nUsted necesita proporcionar al árbitro los siguientes datos en caso de disputa:\n- La llave privada tx\n- El hash de la transacción\n- La dirección publica de recepción\nSi no proporciona los datos arriba señalados, o si utilizó una cartera incompatible, perderá la disputa.\nLa parte que envía UPX es responsable de proporcionar las evidencias de la transferencia de UPX al árbitro en caso de disputa.\nNo se requiere ID de pago, solo la dirección pública normal.\nSi no está seguro sobre el proceso, visite el canal de conflictos de uPlexa  https://discord.gg/vhdNSrV) o el Chat de Telegram de uPlexa (https://t.me/uplexaOfficial) para encontrar más información.
 account.altcoin.popup.arq.msg=El ARQ de intercambio de Bisq requiere que entienda y cumpla los siguientes requerimientos:\n\nPara el ARQ de envío, necesita utilizar la cartera oficial ArQmA GUI o una cartera ArQmA CLI con la opción store-tx-info habilitada (predeterminada en nuevas versiones). Por favor asegúrese de poder acceder a la llave tx ya que podría ser requerido en caso de disputa.\narqma-wallet-cli (utilice el comando get_tx_key)\narqma-wallet-gui (vaya a la pestaña historial y pulse el botón (P) para prueba de pago)\n\nEn los exploradores de bloques normales la transferencia no es verificable.\n\nNecesita proveer al mediador o al árbitro los siguientes datos en caso de disputa:\n- El tx de la llave privada\n- El hash de transacción\n- La dirección publica de recepción\n\nNo proveer los datos arriba señalados, o si utilizó una cartera incompatible, resultará en perder la disputa. La parte ARQ que envía es responsable de proveer verificación de la transferencia ARQ al mediador o al árbitro en caso de disputa.\n\nNo se requiere ID de pago, solo la dirección pública normal.\nSi no está seguro sobre el proceso visite el canal ArQmA en discord (https://discord.gg/s9BQpJT) o el foro de ArQmA (https://labs.arqma.com) para encontrar más información.
-account.altcoin.popup.xmr.msg=Intercambiar XMR en Bisq, requiere entender y cumplir los siguientes requisitos\n\nPara enviar XMR necesita usar o la cartera oficial Monero GUI o la cartera Monero CLI con la bandera store-tx-info habilitada (por defecto en las nuevas versiones). Por favor asegúrese de que puede acceder a la tx key porque podría requerirse en caso de disputa.\nmonero-wallet-cli (use el comando get_tx_key)\nmonero-wallet-gui (vaya a la pestaña de historia y pulse el botón (P) para prueba de pago)\n\nAdemás de la herramienta XMR checktx (https://xmr.llcoins.net/checktx.html) la verificación también se puede cumplir dentro de la cartera.\nmonero-wallet-cli : usando el comando (check_tx_key).\nmonero-wallet-gui : en Avanzado > Probar/Comprobar página.\nEn exploradores de bloque normales la transferencia no es verificable.\n\nNecesita entregar al mediador o árbitro la siguiente información en caso de disputa:\n- La clave privada de transacción (tx private key).\n- El hash de transacción.\n- La dirección pública del receptor.\n\nSi no puede proveer la información o si ha usado una cartera incompatible resultaría en la pérdida del caso de disputa. El emisor de XMR es responsable de ser capaz de verificar la transacción XMR al mediador o al árbitro en caso de disputa.\n\nNo se requiere la ID de pago, sólo la dirección pública normal.\nSi no está seguro del proceso visite (https://www.getmonero.org/resources/user-guides/prove-payment.html) o el foro Monero (https://forum.getmonero.org) para más información.
+account.altcoin.popup.xmr.msg=Intercambiar XMR en Bisq requiere entender y cumplir los siguientes requisitos\n\nPruebas de pago:\nComo Monero es una monda privada, algunos detalles de la transacción no están disponibles públicamente en la cadena de bloques y, en caso de dsiputa, el mediador o el árbitro necesita comprobarlas para verificar si una transacción realmente se realizó. En Bisq, el emisor de la transacción XMR es el responsable de proveer esta información a el mediador o árbitro en caso de disputa. Para hacerlo, debe enviar XMR usando un monedero que proporcione la información necesaria para probar que el pago se haya realizado, lo que incluye:\n\n- La clave de transacción (Tx key, Tx Secret Key o Tx Private Key)\n- La ID de transacción (Tx ID o Tx Hash)\n- La dirección de destino (recipient's address)\n\nEsta información puede encontrarse en el monedero oficial  Monero GUI y CLI, así como MyMonero o Exodus (escritorio) así como en Cake Wallet, MyMonero y Monerujo (móvil), en las siguientes ubicaciones:\n\n- GUI Monero: Vaya a la pestaña de Transacciones.\n- CLI Monero: Use el comando get_tx_key TXID. Debe habilitar la bandera store-tx-info (habilitada por defecto en las nuevas versiones).\n- Otros monederos: vaya a Historial de transacciones y busque la Clave de transacción (Tx key o Secret key) y la dirección de destino en la transacción enviada. Deberá activar "Guardar la dirección del receptor" en la configuración  de Cake Wallet.\n\nSi está usando un monedero diferente de los anteriores, por favor asegúrese de que puede acceder a estos tres requerimientos de información. Como la clave de transacción y la dirección de destino se guardan en el software del monedero de Monero, y no se pueden recuperar desde la cadena de bloques de Monero, no debe borrar o restaurar su monedero de Monero antes de completar los intercambios de Bisq. Si no entrega los datos mencionados anteriormente, perderá el caso de disputa.\n\nComprobación de pagos: con estos tres datos de información, la verificación de que una cantidad específica de Monero se envió a una dirección específica puede completarse de la siguiente manera:\n\n- GUI Monero: cambiar el monedero a Modo avanzado > Prueba/comprobar > Comprobar transacción\n- CLI Monero: Use el comando check_tx_key TXID TXKEY ADDRESS\n-XMR checktx tool (https://xmr.llcoins.net/checktx.html)\n- Web de Explore Monero (https://www.exploremonero.com/receipt)\n\nSu aún no está seguro del proceso, visite (https://www.getmonero.org/resources/user-guides/prove-payment.html) para encontrar más información o pregunte en el subreddit de soporte de Monero (https://www.reddit.com/r/monerosupport/). 
 # suppress inspection "TrailingSpacesInProperty"
-account.altcoin.popup.msr.msg=Trading MSR on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending MSR, you need to use either the official Masari GUI wallet, Masari CLI wallet with the store-tx-info flag enabled (enabled by default) or the Masari web wallet (https://wallet.getmasari.org). Please be sure you can access the tx key as that would be required in case of a dispute.\nmasari-wallet-cli (use the command get_tx_key)\nmasari-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nMasari Web Wallet (goto Account -> transaction history and view details on your sent transaction)\n\nVerification can be accomplished in-wallet.\nmasari-wallet-cli : using command (check_tx_key).\nmasari-wallet-gui : on the Advanced > Prove/Check page.\nVerification can be accomplished in the block explorer \nOpen block explorer (https://explorer.getmasari.org), use the search bar to find your transaction hash.\nOnce transaction is found, scroll to bottom to the 'Prove Sending' area and fill in details as needed.\nYou need to provide the mediator or arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The MSR sender is responsible for providing verification of the MSR transfer to the mediator or arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process, ask for help on the Official Masari Discord (https://discord.gg/sMCwMqs).
+account.altcoin.popup.msr.msg=Para intercambiar MSR en Bisq es necesario que usted entienda y cumpla los siguientes requerimientos:\n\nPara enviar MSR es necesario que use el monedero oficial de Masari GUI o Masari CLI con la opción "store-tx-info" habilitada (predeterminada en las nuevas versiones) o el monedero oficial Masari Web (https://wallet.getmasari.org). Por favor, asegúrese de poder acceder a las llaves tx, ya que podrían requerirse en caso de alguna disputa. \nmasari-wallet-cli (utilice el comando get_tx_key)\nmasari-wallet-gui (vaya a la pestaña historial y haga clic en el botón (P) para prueba de pago). \n\nMonedero Masari Web (vaya a Cuenta -> historial transacción y vea los detalles de su transacción enviada.\n\nPuede lograr verificación de la transacción dentro del monedero:\nmasari-wallet-cli : usando el comando (check_tx_key).\nmasari-wallet-gui: vaya a la pestaña Avanzado > Comprobar/Revisar.\nVerificación de transacción también se puede lograr desde el explorador de bloques\nAbrir explorador de bloques (https://explorer.getmasari.org), use la barra de búsqueda para buscar el hash de su transacción. \nCuando encuentre su transacción, navegue hacia el final donde dice "Comprobar Envío" y rellene los detalles necesarios. \nUsted necesita compartir esta información con el mediador o árbitro en caso de disputa:\n- La llave privada tx\n- El hash de la transacción\n- La dirección publica de recepción\n\nSi no proporciona los datos arriba señalados, o si utilizó una cartera incompatible, perderá la disputa.  El que envía MSR es responsable de entregar la verificación de envío al mediador o árbitro en caso de disputa.\n\nNo se requiere el ID de pago, sólo la dirección pública normal.\nSi no está seguro sobre el proceso, pida ayuda visitando el canal oficial de Masari en Discord (https://discord.gg/sMCwMqs).
 account.altcoin.popup.blur.msg=Intercambiar BLUR en Bisq requiere que entienda y cumpla los siguientes requisitos:\n\nPara enviar BLUR debe usar Blur Network CLI o la cartera GUI. \n\nSi utiliza la cartera CLI, un hash de transacción (tx ID) se mostrará después de hacer una transferencia. Deberá guardar esta información. Inmediatamente después de enviar la transferencia, deberá utilizar el comando 'get_tx_key' para obtener la clave privada de transacción. Si no realiza este paso, es posible que no pueda obtener la llave mas tarde. \n\nSi utiliza la cartera Blur Network GUI, la clave privada de transacción y el ID de transacción puede ser encontrada convenientemente en la pestaña "Historia". Inmediatamente después del envío, localice la transacción de interés. Pulse en el símbolo "?" en la esquina inferior derecha de la caja que contiene la transacción. Debe guardar esta información. \n\nEn caso de que sea necesaria una disputa, deberá presentar lo siguiente al mediador o al árbitro: 1.) el ID de transacción, 2.) la clave privada de transacción, y 3.) la dirección de destino. El mediador o árbitro entonces verificará la transferencia BLUR utilizando el Visor de Transacción Blur (https://blur.cash/#tx-viewer).\n\nSi no se proporciona la información requerida al mediador o al árbitro se perderá el caso de disputa. En todos los casos de disputa, el remitente BLUR asume el 100% de la responsabilidad en la verificación de las transacciones a un mediador o a un árbitro.. \n\nSi no comprende estos requisitos, no realice transacciones en Bisq. Primero, busque ayuda en Blur Network Discord (https://discord.gg/dMWaqVW).
-account.altcoin.popup.solo.msg=Trading Solo on Bisq requires that you understand and fulfill the following requirements:\n\nTo send Solo you must use the Solo Network CLI Wallet. \n\nIf you are using the CLI wallet, a transaction hash (tx ID) will be displayed after a transfer is sent. You must save this information. Immediately after sending the transfer, you must use the command 'get_tx_key' to retrieve the transaction private key. If you fail to perform this step, you may not be able to retrieve the key later. \n\nIn the event that arbitration is necessary, you must present the following to an mediator or arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address.  The mediator or arbitrator will then verify the Solo transfer using the Solo Block Explorer by searching for the transaction and then using the "Prove sending" function (https://explorer.minesolo.com/).\n\nfailure to provide the required information to the mediator or arbitrator will result in losing the dispute case. In all cases of dispute, the Solo sender bears 100% of the burden of responsibility in verifying transactions to an mediator or arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Solo Network Discord (https://discord.minesolo.com/).
+account.altcoin.popup.solo.msg=Para intercambiar Solo en Bisq es necesario que usted entienda y cumpla los siguientes requisitos:\n\nPara enviar Solo es necesario que use el monedero Solo Network Monedero CLI\n\nSi usted usa el monedero CLI el hash de transacción (tx ID) aparecerá después de la transferencia. Usted debe guardar esta información. Inmediatamente después de mandar de la transferencia, usted debe usar el comando 'get_tx_key' para guardar la clave privada de transacción. Si usted no guarda esta información, es posible que no podrá coleccionar esta clave después .\n\nUsted necesita compartir esta información con el mediador o árbitro en caso de disputa:\n1.) el ID de transacción,  2.) la clave privada de transacción y 3.) la dirección pública de recepción. El mediador o árbitro podrá verificar la transferencia de Solo usando el explorador de bloques Solo, buscando la transacción y usando la función "Prove sending" (https://explorer.minesolo.com/).\n\nSi no proporciona los datos arriba señalados al mediador o árbitro perderá la disputa. En todos los casos de disputa, el emisor de Solo es 100% responsable de entregar la verificación de envío al mediador o árbitro.\n\nSi no está seguro o no entiendo estos requisitos, no haga intercambio/transacción en Bisq. Primero, pida ayuda visitando el canal oficial de Solo Network en Discord (https://discord.minesolo.com/).
 account.altcoin.popup.cash2.msg=Intercambiar CASH2 en Bisq requiere que usted comprenda y cumpla con los siguientes requisitos:\n\nPara enviar CASH2, debe utilizar la cartera Cash2 versión 3 o superior. \n\nDespués de que se envía una transacción, se mostrará el ID de transacción. Debe guardar esta información. Inmediatamente después de enviar la transacción, debe usar el comando 'getTxKey' en simplewallet para recuperar la llave secreta de la transacción. \n\nEn el caso de que sea necesario un arbitraje, debe presentar lo siguiente a un mediador o a un árbitro: 1) ID de transacción, 2) la llave secreta de la transacción y 3) la dirección Cash2 del destinatario. El mediador o el árbitro entonces verificará la transferencia CASH2 usando el Explorador de Bloques Cash2 (https://blocks.cash2.org).\n\nSi no se proporciona la información requerida al mediador o al árbitro, se perderá el caso de disputa. En todos los casos de disputa, el remitente de CASH2 lleva el 100% de la carga de la responsabilidad de verificar las transacciones a un mediador o a un árbitro.\n\nSi no comprende estos requisitos, no realice transacciones en Bisq. Primero, busque ayuda en Cash2 Discord (https://discord.gg/FGfXAYN).
 account.altcoin.popup.qwertycoin.msg=Intercambiar Qwertycoin en Bisq requiere que usted comprenda y cumpla los siguientes requisitos:\n\nPara enviar QWC, debe utilizar la cartera oficial QWC versión 5.1.3 o superior. \n\nDespués de que se envía una transacción, se mostrará el ID de transacción. Debe guardar esta información. Inmediatamente después de enviar la transacción, debe usar el comando 'get_Tx_Key' en simplewallet para recuperar la llave secreta de la transacción.\n\nEn el caso de que sea necesario un arbitraje, debe presentar lo siguiente a un mediador o un árbitro: 1) ID de transacción, 2) la llave secreta de la transacción y 3) la dirección QWC del destinatario. El mediador o el árbitro entonces verificará la transferencia QWC usando el Explorador de Bloques QWC (https://explorer.qwertycoin.org).\n\nSi no se proporciona la información requerida al mediador o al árbitro, se perderá el caso de disputa. En todos los casos de disputa, el remitente de QWC lleva el 100% de la carga de la responsabilidad de verificar las transacciones a un mediador o un árbitro.\n\nSi no comprende estos requisitos, no realice transacciones en Bisq. Primero, busque ayuda en QWC Discord (https://discord.gg/rUkfnpC).
 account.altcoin.popup.drgl.msg=Intercambiar Dragonglass on Bisq requiere que usted comprenda y cumpla los siguientes requisitos:\n\nDebido a la privacidad que Dragonglass provee, una transacción no es verificable en la blockchain pública. Si es requerido, usted puede probar su pago a través del uso de su TXN-Private-Key.\nLa TXN-clave privada es una one-time clave generada automáticamente para cada transacción que solo puede ser accedida desde dentro de su cartera DRGL.\nO por DRGL-wallet GUI (dentro del diálogo de detalles de transacción) o por la Dragonglass CLI simplewallet (usando el comando "get_tx_key").\n\nDRGL version 'Oathkeeper' y superior son REQUERIDAS para ambos.\n\nEn caso de que sea necesario un arbitraje, debe presentar lo siguiente a un mediador o un árbitro:\n- La TXN-clave privada\n- El hash de transacción\n- La dirección pública del destinatario\n\nLa verificación de pago puede ser hecha usando los datos de arriba en (http://drgl.info/#check_txn).\n\nNo proporcionar los datos anteriores, o si usted usó una cartera incompatible, resultará en la pérdida del caso de disputa. El Dragonglass remitente es responsable de proveer verificación de la transferencia DRGL al mediador o al árbitro en caso de una disputa. El uso de PaymentID no es requerido.\n\nSi usted no está seguro sobre cualquier parte de este proceso, visite Dragonglass en Discord (http://discord.drgl.info) para ayuda.
@@ -1052,7 +1051,7 @@ account.altcoin.popup.grin.msg=GRIN requiere un proceso interactivo entre el emi
 account.altcoin.popup.beam.msg=BEAM requiere un proceso interactivo entre el emisor y el receptor para crear la transacción.\n\nAsegúrese de seguir la instrucciones de la página web del proyecto BEAM para enviar y recibir BEAM con seguridad (el receptor necesita estar el línea o por lo menos estar en línea durante cierto periodo de tiempo).\n\nEl emisor BEAM requiere proveer prueba de que envió BEAM correctamente. Asegúrese de usar software de monedero que pueda producir tal prueba. Si el monedero no provee la prueba, una posible controversia será resuelta en favor del BEAM receptor.
 account.altcoin.popup.pars.msg=Intercambiar ParsiCoin en Bisq requiere que usted comprenda y cumpla con los siguientes requisitos:\n\nPara enviar PARS, debe usar la cartera oficial ParsiCoin version 3.0.0 o superior.\n\nPuede comprobar su hash de transacción y la clave de la transacción en la sección de Transacciones en su cartera GUI (ParsiPay). Necesita pulsar el botón derecho en la transacción y pulsar mostrar detalles.\n\nEn el caso de que sea necesario arbitraje, debe presentar lo siguiente al mediador o al árbitro: 1) El hash de transacción, 2) La llave de la transacción, y 3) La dirección del receptor PARS. El árbitro entonces verificará la transferencia PARS usando el ParsiCoin Explorador de Bloques (http://explorer.parsicoin.net/#check_payment).\n\nSi no se proporciona la información requerida al mediador o al árbitro, se perderá el caso de disputa. En todos los casos de disputa, el remitente de ParsiCoin lleva 100% de la carga de la responsabilidad de verificar las transacciones a un mediador o un árbitro\n\nSi no comprende estos requisitos, no realice transacciones en Bisq. Primero, busque ayuda en ParsiCoin Discord (https://discord.gg/c7qmFNh).
 
-account.altcoin.popup.blk-burnt.msg=To trade burnt blackcoins, you need to know the following:\n\nBurnt blackcoins are unspendable. To trade them on Bisq, output scripts need to be in the form: OP_RETURN OP_PUSHDATA, followed by associated data bytes which, after being hex-encoded, constitute addresses. For example, burnt blackcoins with an address 666f6f (“foo” in UTF-8) will have the following script:\n\nOP_RETURN OP_PUSHDATA 666f6f\n\nTo create burnt blackcoins, one may use the “burn” RPC command available in some wallets.\n\nFor possible use cases, one may look at https://ibo.laboratorium.ee .\n\nAs burnt blackcoins are unspendable, they can not be reselled. “Selling” burnt blackcoins means burning ordinary blackcoins (with associated data equal to the destination address).\n\nIn case of a dispute, the BLK seller needs to provide the transaction hash.
+account.altcoin.popup.blk-burnt.msg=Para intercambiar blackcoins quemados. usted necesita saber lo siguiente:\n\nBlackcoins quemados son indestructibles. Para intercambiarlos en Bisq, los guiones de output tienen que estar en la forma: OP_RETURN OP_PUSHDATA, seguidos por bytes de datos asociados que, después de codificarlos en hexadecimal, construyen direcciones. Por ejemplo, blackcoins quemados con una dirección 666f6f ("foo" en UTF-8) tendrán el siguiente guion:\n\nOP_RETURN OP_PUSHDATA 666f6f\n\nPara crear blackcoins quemados, uno puede usar el comando RPC "quemar" disponible en algunas carteras.\n\nPara posibles casos de uso, uno puede mirar en https://ibo.laboratorium.ee .\n\nComo los blackcoins quemados son undestructibles, no pueden ser revendidos. "Vender" blackcoins quemados significa quemar blackcoins comunes (con datos asociados igual a la dirección de destino).\n\nEn caso de una disputa, el vendedor BLK necesita proveer el hash de transacción.
 
 account.fiat.yourFiatAccounts=Sus cuentas de moneda nacional:
 
@@ -1169,6 +1168,7 @@ dao.lockedForVoteBalance=Usado para votar
 dao.lockedInBonds=Bloqueado en garantías
 dao.availableNonBsqBalance=Saldo no-BSQ disponible (BTC)
 dao.totalBsqBalance=Saldo total BSQ
+dao.reputationBalance=Valor de mérito (no se puede gastar)
 
 dao.tx.published.success=Su transacción ha sido publicada satisfactoriamente.
 dao.proposal.menuItem.make=Hacer propuesta
@@ -1872,8 +1872,8 @@ disputeSummaryWindow.summaryNotes=Nota de resumen
 disputeSummaryWindow.addSummaryNotes=Añadir notas de sumario
 disputeSummaryWindow.close.button=Cerrar ticket
 disputeSummaryWindow.close.msg=Ticket cerrado en {0}\n\nSumario:\nCantidad de pago para comprador de BTC: {1}\nCantidad de pago para vendedor de BTC: {2}\n\nNotas del sumario:\n{3}
-disputeSummaryWindow.close.nextStepsForMediation=\n\nNext steps:\nOpen trade and accept or reject suggestion from mediator
-disputeSummaryWindow.close.nextStepsForRefundAgentArbitration=\n\nNext steps:\nNo further action is required from you. If the arbitrator decided in your favor, you'll see a "Refund from arbitration" transaction in Funds/Transactions
+disputeSummaryWindow.close.nextStepsForMediation=\n\nSiguientes pasos:\nAbrir intercambio y aceptar o rechazar la sugerencia del mediador
+disputeSummaryWindow.close.nextStepsForRefundAgentArbitration=\n\nSiguientes pasos:\nNo se requiere ninguna acción adicional. Si el árbitro decide en su favor, verá una transacción de "Devolución de fondos de arbitraje" en Fondos/Transacciones 
 disputeSummaryWindow.close.closePeer=Necesitar cerrar también el ticket del par de intercambio!
 disputeSummaryWindow.close.txDetails.headline=Publicar transacción de devolución de fondos
 disputeSummaryWindow.close.txDetails.buyer=El comprador recibe {0} en la dirección: {1}\n
@@ -1961,7 +1961,7 @@ showWalletDataWindow.includePrivKeys=Incluir claves privadas:
 tacWindow.headline=Acuerdo de usuario
 tacWindow.agree=Estoy de acuerdo
 tacWindow.disagree=No estoy de acuerdo, salir
-tacWindow.arbitrationSystem=Sistema arbitraje
+tacWindow.arbitrationSystem=Disputa resolución
 
 tradeDetailsWindow.headline=Intercambio
 tradeDetailsWindow.disputedPayoutTxId=ID transacción de pago en disputa:
@@ -2025,8 +2025,8 @@ popup.error.takeOfferRequestFailed=Un error ocurrió cuando alguien intentó tom
 
 error.spvFileCorrupted=Ocurrió un error al leer el archivo de cadena SPV.\nPuede ser que el archivo de cadena SPV se haya corrompido.\n\nMensaje de error: {0}\n\n¿Quiere borrarlo y comenzar una resincronización?
 error.deleteAddressEntryListFailed=No se pudo borrar el archivo AddressEntryList.\nError: {0}
-error.closedTradeWithUnconfirmedDepositTx=The deposit transaction of the closed trade with the trade ID {0} is still unconfirmed.\n\nPlease do a SPV resync at \"Setting/Network info\" to see if the transaction is valid.
-error.closedTradeWithNoDepositTx=The deposit transaction of the closed trade with the trade ID {0} is null.\n\nPlease restart the application to clean up the closed trades list.
+error.closedTradeWithUnconfirmedDepositTx=La transacción de depósito de el intercambio cerrado con la ID de intercambio {0} aún no se ha confirmado.\n\nPor favor haga una resincronización SPV en \"Configuración/Información de red\" para ver si la transacción es válida.
+error.closedTradeWithNoDepositTx=El depósito de transacción de el intercambio cerrado con ID de intercambio {0} es inválido.\nPor favor reinicie la aplicación para limpiar la lista de intercambios cerrados.
 
 popup.warning.walletNotInitialized=La cartera aún no sea ha iniciado
 popup.warning.wrongVersion=Probablemente tenga una versión de Bisq incorrecta para este ordenador.\nLa arquitectura de su ordenador es: {0}.\nLos binarios de Bisq instalados son: {1}.\nPor favor cierre y reinstale la versión correcta ({2}).
@@ -2064,16 +2064,16 @@ popup.warning.mandatoryUpdate.dao=Por favor, actualice a la última versión de
 popup.warning.disable.dao=El DAO Bisq y BSQ estén temporalmente deshabilitados. Por favor revise el foro de Bisq para más información.
 popup.warning.burnBTC=Esta transacción no es posible, ya que las comisiones de minado de {0} excederían la cantidad a transferir de {1}. Por favor, espere a que las comisiones de minado bajen o hasta que haya acumulado más BTC para transferir.
 
-popup.warning.openOffer.makerFeeTxRejected=The maker fee transaction for offer with ID {0} was rejected by the Bitcoin network.\nTransaction ID={1}.\nThe offer has been removed to avoid further problems.\nPlease go to \"Settings/Network info\" and do a SPV resync.\nFor further help please contact the Bisq support channel at the Bisq Keybase team.
+popup.warning.openOffer.makerFeeTxRejected=La tasa de transacción para la oferta con ID {0} se rechazó por la red Bitcoin.\nID de transacción={1}\nLa oferta se ha eliminado para evitar futuros problemas.\nPor favor vaya a \"Configuración/Información de red\" y haga una resincronización SPV.\nPara más ayuda por favor contacte con el equipo de soporte de Bisq en el canal de Bisq en Keybase.
 
-popup.warning.trade.txRejected.tradeFee=trade fee
-popup.warning.trade.txRejected.deposit=deposit
-popup.warning.trade.txRejected=The {0} transaction for trade with ID {1} was rejected by the Bitcoin network.\nTransaction ID={2}}\nThe trade has been moved to failed trades.\nPlease go to \"Settings/Network info\" and do a SPV resync.\nFor further help please contact the Bisq support channel at the Bisq Keybase team.
+popup.warning.trade.txRejected.tradeFee=tasa de intercambio
+popup.warning.trade.txRejected.deposit=depósito
+popup.warning.trade.txRejected=La transacción {0} para el intercambio con ID {1} se rechazó por la red Bitcoin.\nID de transacción={2}\nEl intercambio se movió a intercambios fallidos.\nPor favor vaya a \"Configuración/Información de red\" y haga una resincronización SPV.\nPara más ayuda por favor contacte con el equipo de soporte de Bisq en el canal de Bisq en Keybase.
 
-popup.warning.openOfferWithInvalidMakerFeeTx=The maker fee transaction for offer with ID {0} is invalid.\nTransaction ID={1}.\nPlease go to \"Settings/Network info\" and do a SPV resync.\nFor further help please contact the Bisq support channel at the Bisq Keybase team.
+popup.warning.openOfferWithInvalidMakerFeeTx=La transacción de tasa de creador para la oferta con ID {0} es inválida.\nID de transacción={1}.\nPor favor vaya a \"Configuración/Información de red\" y haga una resincronización SPV.\nPara más ayuda por favor contacte con el equipo de soporte de Bisq en el canal de Bisq de Keybase.
 
-popup.warning.trade.depositTxNull=The trade with ID {0} has no deposit transaction set.\nPlease restart the application and if the problem remains move the trade to failed trades and report the problem to the Bisq support channel at the Bisq Keybase team.
-popup.warning.trade.depositTxNull.moveToFailedTrades=Move to failed trades
+popup.warning.trade.depositTxNull=El intercambio con ID {0} no tiene transacción de depósito establecida.\nPor favor reinicie la aplicación y si el problema continúa, mueva el intercambio a intercambios fallidos y reporte el problema a el equipo de soporte de Bisq en Keybase.
+popup.warning.trade.depositTxNull.moveToFailedTrades=Mover a intercambios fallidos
 
 popup.info.securityDepositInfo=Para asegurarse de que ambos comerciantes siguen el protocolo de intercambio, ambos necesitan pagar un depósito de seguridad.\n\nEl depósito se guarda en su monedero de intercambio hasta que el intercambio se complete, y entonces se devuelve.\n\nPor favor, tenga en cuenta que al crear una nueva oferta, Bisq necesita estar en ejecución para que otro comerciante la tome. Para mantener sus ofertas en línea, mantenga Bisq funcionando y asegúrese de que su computadora está en línea también (Ej. asegúrese de que no pasa a modo standby...el monitor en standby no es problema!)
 
@@ -2152,7 +2152,7 @@ systemTray.show=Mostrar ventana de aplicación
 systemTray.hide=Esconder ventana de aplicación
 systemTray.info=Información sobre Bisq
 systemTray.exit=Salir
-systemTray.tooltip=Bisq: La red de intercambio descentralizada
+systemTray.tooltip=Bisq: Un network de intercambio de bitcoin decentralizado
 
 
 ####################################################################

core/src/main/resources/i18n/displayStrings_fa.properties

@@ -672,7 +672,6 @@ portfolio.pending.step5_buyer.takersMiningFee=کل کارمزد استخراج
 portfolio.pending.step5_buyer.refunded=سپرده اطمینان مسترد شده
 portfolio.pending.step5_buyer.withdrawBTC=برداشت بیتکوین شما
 portfolio.pending.step5_buyer.amount=مبلغ قابل برداشت
-portfolio.pending.step5_buyer.signer=By withdrawing your bitcoins, you verify that the counterparty has acted according to the trade protocol.
 portfolio.pending.step5_buyer.withdrawToAddress=برداشت به آدرس
 portfolio.pending.step5_buyer.moveToBisqWallet=انتقال وجوه به کیف پول Bisq
 portfolio.pending.step5_buyer.withdrawExternal=برداشت به کیف پول خارجی
@@ -873,7 +872,7 @@ support.sellerOfferer=فروشنده/سفارش گذار بیتکوین
 support.buyerTaker=خریدار/پذیرنده‌ی بیتکوین
 support.sellerTaker=فروشنده/پذیرنده‌ی بیتکوین
 
-support.backgroundInfo=Bisq is not a company, so it handles disputes differently.\n\nTraders can communicate within the application via a secure chat on the open trades screen to attempt solving a dispute on their own. If that is not sufficient, a mediator can step in to help. The mediator will evaluate the situation and give a recommendation for the payout of the trade funds. If both traders accept this suggestion, the payout transaction is completed and the trade is closed. If one or both traders do not agree to the mediator's recommended payout, they can request arbitration.The arbitrator has the third key of the deposit transaction and will make the payout based on their findings.
+support.backgroundInfo=Bisq is not a company, so it handles disputes differently.\n\nTraders can communicate within the application via secure chat on the open trades screen to try solving disputes on their own. If that is not sufficient, a mediator can step in to help. The mediator will evaluate the situation and suggest a payout of trade funds. If both traders accept this suggestion, the payout transaction is completed and the trade is closed. If one or both traders do not agree to the mediator's suggested payout, they can request arbitration.The arbitrator will re-evaluate the situation and, if warranted, personally pay the trader back and request reimbursement for this payment from the Bisq DAO.
 support.initialInfo=Please enter a description of your problem in the text field below. Add as much information as possible to speed up dispute resolution time.\n\nHere is a check list for information you should provide:\n\t● If you are the BTC buyer: Did you make the Fiat or Altcoin transfer? If so, did you click the 'payment started' button in the application?\n\t● If you are the BTC seller: Did you receive the Fiat or Altcoin payment? If so, did you click the 'payment received' button in the application?\n\t● Which version of Bisq are you using?\n\t● Which operating system are you using?\n\t● If you encountered an issue with failed transactions please consider switching to a new data directory.\n\t  Sometimes the data directory gets corrupted and leads to strange bugs. \n\t  See: https://docs.bisq.network/backup-recovery.html#switch-to-a-new-data-directory\n\nPlease make yourself familiar with the basic rules for the dispute process:\n\t● You need to respond to the {0}''s requests within 2 days.\n\t● Mediators respond in between 2 days. Arbitrators respond in between 5 business days.\n\t● The maximum period for a dispute is 14 days.\n\t● You need to cooperate with the {1} and provide the information they request to make your case.\n\t● You accepted the rules outlined in the dispute document in the user agreement when you first started the application.\n\nYou can read more about the dispute process at: {2}
 support.systemMsg=پیغام سیستم: {0}
 support.youOpenedTicket=شما یک درخواست برای پشتیبانی باز کردید.\n\n{0}\n\nنسخه Bisq شما: {1}
@@ -1038,7 +1037,7 @@ account.altcoin.popup.wallet.msg=Please be sure that you follow the requirements
 account.altcoin.popup.wallet.confirm=من می فهمم و تأیید می کنم که می دانم از کدام کیف پول باید استفاده کنم.
 account.altcoin.popup.upx.msg=Trading UPX on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending UPX, you need to use either the official uPlexa GUI wallet or uPlexa CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nuplexa-wallet-cli (use the command get_tx_key)\nuplexa-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The UPX sender is responsible for providing verification of the UPX transfer to the arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit uPlexa discord channel (https://discord.gg/vhdNSrV) or the uPlexa Telegram Chat (https://t.me/uplexaOfficial) to find more information.
 account.altcoin.popup.arq.msg=Trading ARQ on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending ARQ, you need to use either the official ArQmA GUI wallet or ArQmA CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\narqma-wallet-cli (use the command get_tx_key)\narqma-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the mediator or arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The ARQ sender is responsible for providing verification of the ARQ transfer to the mediator or arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit ArQmA discord channel (https://discord.gg/s9BQpJT) or the ArQmA forum (https://labs.arqma.com) to find more information.
-account.altcoin.popup.xmr.msg=Trading XMR on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending XMR, you need to use either the official Monero GUI wallet or Monero CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nmonero-wallet-cli (use the command get_tx_key)\nmonero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nIn addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\nmonero-wallet-cli : using command (check_tx_key).\nmonero-wallet-gui : on the Advanced > Prove/Check page.\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the mediator or arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The XMR sender is responsible for providing verification of the XMR transfer to the mediator or arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) or the Monero forum (https://forum.getmonero.org) to find more information.
+account.altcoin.popup.xmr.msg=Trading XMR on Bisq requires that you understand and fulfill the following requirements:\n\nProve payments: since Monero is a private coin, some transaction details aren't publicly available in the blockchain, and, in case of a dispute, the mediator or arbitrator needs them to check if the transaction was really made. In Bisq, the sender of the XMR transaction is the one responsible for providing this information to the mediator or arbitrator in case of a dispute. In order to do that, you must send XMR using a wallet that provides the information required to prove the payment was made, which includes:\n\n- the transaction key (Tx Key, Tx Secret Key or Tx Private Key)\n- the transaction ID (Tx ID or Tx Hash)\n- the destination address (recipient's address)\n\nThis information can be found in the official Monero GUI & CLI wallets, MyMonero, and Exodus (desktop) as well as in Cake Wallet, MyMonero, and Monerujo (mobile), in the following locations:\n\n- Monero GUI: go to Transactions tab\n- Monero CLI: use the command get_tx_key TXID. The flag store-tx-info must be enabled (enabled by default in new versions)\n- Other wallets: go to Transactions history and search for Transaction key (Tx key or Secret key) and the destination address in a sent transaction. Save recipient address option must be enabled in Cake Wallet settings.\n\nIf you are using a wallet different from the mentioned above, please be sure you can access those three pieces of information.Since the transaction key and the destination address are stored in the Monero wallet software, and they cannot be recovered in the Monero blockchain, you should never delete or restore your Monero wallet before a Bisq trade is completed. Failure to provide the above data will result in losing the dispute case.\n\nCheck payments: with those three pieces of information, the verification that a quantity of Monero was sent to a specific address can be accomplished the following way:\n\n- Monero GUI: change wallet to Advanced mode and go to Advanced > Prove/check > Check Transaction\n- Monero CLI: use the command check_tx_key TXID TXKEY ADDRESS\n- XMR checktx tool (https://xmr.llcoins.net/checktx.html)\n- Explore Monero website (https://www.exploremonero.com/receipt)\n\nIf you are still not sure about this process, visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) to find more information or ask a question on the Monero support subreddit (https://www.reddit.com/r/monerosupport/).
 # suppress inspection "TrailingSpacesInProperty"
 account.altcoin.popup.msr.msg=Trading MSR on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending MSR, you need to use either the official Masari GUI wallet, Masari CLI wallet with the store-tx-info flag enabled (enabled by default) or the Masari web wallet (https://wallet.getmasari.org). Please be sure you can access the tx key as that would be required in case of a dispute.\nmasari-wallet-cli (use the command get_tx_key)\nmasari-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nMasari Web Wallet (goto Account -> transaction history and view details on your sent transaction)\n\nVerification can be accomplished in-wallet.\nmasari-wallet-cli : using command (check_tx_key).\nmasari-wallet-gui : on the Advanced > Prove/Check page.\nVerification can be accomplished in the block explorer \nOpen block explorer (https://explorer.getmasari.org), use the search bar to find your transaction hash.\nOnce transaction is found, scroll to bottom to the 'Prove Sending' area and fill in details as needed.\nYou need to provide the mediator or arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The MSR sender is responsible for providing verification of the MSR transfer to the mediator or arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process, ask for help on the Official Masari Discord (https://discord.gg/sMCwMqs).
 account.altcoin.popup.blur.msg=Trading BLUR on Bisq requires that you understand and fulfill the following requirements:\n\nTo send BLUR you must use the Blur Network CLI or GUI Wallet. \n\nIf you are using the CLI wallet, a transaction hash (tx ID) will be displayed after a transfer is sent. You must save this information. Immediately after sending the transfer, you must use the command 'get_tx_key' to retrieve the transaction private key. If you fail to perform this step, you may not be able to retrieve the key later. \n\nIf you are using the Blur Network GUI Wallet, the transaction private key and transaction ID can be found conveniently in the "History" tab.  Immediately after sending, locate the transaction of interest. Click the "?" symbol in the lower-right corner of the box containing the transaction. You must save this information. \n\nIn the event that arbitration is necessary, you must present the following to an mediator or arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address.  The mediator or arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nFailure to provide the required information to the mediator or arbitrator will result in losing the dispute case. In all cases of dispute, the BLUR sender bears 100% of the burden of responsibility in verifying transactions to an mediator or arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW).
@@ -1169,6 +1168,7 @@ dao.lockedForVoteBalance=در حال استفاده برای رای دادن
 dao.lockedInBonds=قفل شده در ضمانت
 dao.availableNonBsqBalance=موجودی غیر BSQ در دسترس (BTC)
 dao.totalBsqBalance=مجموع موجودی BSQ
+dao.reputationBalance=Merit Value (not spendable)
 
 dao.tx.published.success=تراکنش شما به طور موفقیت آمیز منتشر شد.
 dao.proposal.menuItem.make=ارائه ی پیشنهاد
@@ -1961,7 +1961,7 @@ showWalletDataWindow.includePrivKeys=شامل کلیدهای خصوصی
 tacWindow.headline=موافقتنامه کاربر
 tacWindow.agree=من موافقم
 tacWindow.disagree=من مخالفم و خارج می شوم
-tacWindow.arbitrationSystem=سیستم داوری
+tacWindow.arbitrationSystem=Dispute resolution
 
 tradeDetailsWindow.headline=معامله
 tradeDetailsWindow.disputedPayoutTxId=شناسه تراکنش پرداختی مورد مناقشه:
@@ -2152,7 +2152,7 @@ systemTray.show=نمایش پنجره ی برنامه
 systemTray.hide=مخفی کردن پنجره ی برنامه
 systemTray.info=اطلاعات درباره ی Bisq 
 systemTray.exit=خروج
-systemTray.tooltip=Bisq: شبکه تبادل غیرمتمرکز
+systemTray.tooltip=Bisq: A decentralized bitcoin exchange network
 
 
 ####################################################################

core/src/main/resources/i18n/displayStrings_fr.properties

@@ -62,10 +62,10 @@ shared.priceWithCur=Prix en {0}
 shared.priceInCurForCur=Prix en {0} pour 1 {1}
 shared.fixedPriceInCurForCur=Prix fixé en {0} pour 1 {1}
 shared.amount=Montant
-shared.txFee=Transaction Fee
-shared.makerFee=Maker Fee
-shared.buyerSecurityDeposit=Buyer Deposit
-shared.sellerSecurityDeposit=Seller Deposit
+shared.txFee=Frais de transaction
+shared.makerFee=Frais du maker
+shared.buyerSecurityDeposit=Dépôt de l'acheteur
+shared.sellerSecurityDeposit=Dépôt du vendeur
 shared.amountWithCur=Montant en {0}
 shared.volumeWithCur=Volume en {0}
 shared.currency=Devise
@@ -152,7 +152,7 @@ shared.save=Sauvegarder
 shared.onionAddress=Adresse Onion
 shared.supportTicket=Ticket de support
 shared.dispute=conflit
-shared.mediationCase=mediation case
+shared.mediationCase=Litige en médiation
 shared.seller=vendeur
 shared.buyer=acheteur
 shared.allEuroCountries=Tous les pays de la zone Euro
@@ -207,13 +207,13 @@ shared.votes=Votes
 shared.learnMore=En savoir plus
 shared.dismiss=Rejeter
 shared.selectedArbitrator=Arbitre sélectionné
-shared.selectedMediator=Selected mediator
+shared.selectedMediator=Médiateur sélectionné
 shared.selectedRefundAgent=Arbitre sélectionné
 shared.mediator=Médiateur
 shared.arbitrator=Arbitre
 shared.refundAgent=Arbitre
-shared.refundAgentForSupportStaff=Refund agent
-shared.delayedPayoutTxId=Refund collateral transaction ID
+shared.refundAgentForSupportStaff=Agent de remboursement
+shared.delayedPayoutTxId=Remboursement du dépôt de garantie de la transaction ID
 
 
 ####################################################################
@@ -256,7 +256,7 @@ mainView.footer.btcInfo.synchronizingWith=Synchronisation avec
 mainView.footer.btcInfo.synchronizedWith=Synchronisé avec
 mainView.footer.btcInfo.connectingTo=Se connecte à
 mainView.footer.btcInfo.connectionFailed=Echec de la connexion
-mainView.footer.p2pInfo=Bisq network peers: {0}
+mainView.footer.p2pInfo=Pairs du réseau Bisq: {0}
 mainView.footer.daoFullNode=DAO full node
 
 mainView.bootstrapState.connectionToTorNetwork=(1/4) Connection au réseau Tor...
@@ -266,15 +266,15 @@ mainView.bootstrapState.initialDataReceived=(4/4) Données initiales reçues
 
 mainView.bootstrapWarning.noSeedNodesAvailable=Pas de seed nodes disponible
 mainView.bootstrapWarning.noNodesAvailable=Pas de noeuds de seed ou de pairs disponibles
-mainView.bootstrapWarning.bootstrappingToP2PFailed=Bootstrapping to Bisq network failed
+mainView.bootstrapWarning.bootstrappingToP2PFailed=L'initialisation du réseau Bisq a échoué
 
 mainView.p2pNetworkWarnMsg.noNodesAvailable=Il n'y a pas de noeud de seed ou de persisted pairs disponibles pour demander des données.\nVeuillez vérifier votre connexion Internet ou essayer de redémarrer l'application.
-mainView.p2pNetworkWarnMsg.connectionToP2PFailed=Connecting to the Bisq network failed (reported error: {0}).\nPlease check your internet connection or try to restart the application.
+mainView.p2pNetworkWarnMsg.connectionToP2PFailed=La connexion au réseau Bisq a échoué (erreur signalé: {0}).\nVeuillez vérifier votre connexion Internet ou essayer de redémarrer l'application.
 
 mainView.walletServiceErrorMsg.timeout=La connexion au réseau Bitcoin a échoué car le délai d'attente a expiré.
 mainView.walletServiceErrorMsg.connectionError=La connexion au réseau Bitcoin a échoué à cause d''une erreur: {0}
 
-mainView.walletServiceErrorMsg.rejectedTxException=A transaction was rejected from the network.\n\n{0}
+mainView.walletServiceErrorMsg.rejectedTxException=Le réseau a rejeté une transaction.\n\n{0}
 
 mainView.networkWarning.allConnectionsLost=Vous avez perdu la connexion avec tous les {0} pairs du réseau.\nVous avez peut-être perdu votre connexion Internet ou votre ordinateur était passé en mode veille.
 mainView.networkWarning.localhostBitcoinLost=Vous avez perdu la connexion avec le localhost Bitcoin node.\nVeuillez redémarrer l'application Bisq pour vous connecter à d'autres Bitcoin nodes ou redémarrer le localhost Bitcoin node.
@@ -315,7 +315,7 @@ market.trades.tooltip.candle.close=Fermer:
 market.trades.tooltip.candle.high=Haut:
 market.trades.tooltip.candle.low=Bas:
 market.trades.tooltip.candle.average=Moyenne:
-market.trades.tooltip.candle.median=Median:
+market.trades.tooltip.candle.median=Médiane:
 market.trades.tooltip.candle.date=Date:
 
 ####################################################################
@@ -335,20 +335,20 @@ offerbook.offerersAcceptedBankSeats=Pays acceptés où se situe le siège de la
 offerbook.availableOffers=Ordres disponibles
 offerbook.filterByCurrency=Filtrer par devise
 offerbook.filterByPaymentMethod=Filtrer par mode de paiement
-offerbook.timeSinceSigning=Time since signing
-offerbook.timeSinceSigning.info=This account was verified and {0}
-offerbook.timeSinceSigning.info.arbitrator=signed by an arbitrator and can sign peer accounts
-offerbook.timeSinceSigning.info.peer=signed by a peer, waiting for limits to be lifted
-offerbook.timeSinceSigning.info.peerLimitLifted=signed by a peer and limits were lifted
-offerbook.timeSinceSigning.info.signer=signed by peer and can sign peer accounts (limits lifted)
+offerbook.timeSinceSigning=Temps depuis la signature
+offerbook.timeSinceSigning.info=Ce compte a été vérifié et {0}
+offerbook.timeSinceSigning.info.arbitrator=signé par un arbitre et pouvant signer des comptes pairs
+offerbook.timeSinceSigning.info.peer=signé par un pair, en attente de la levée des limites
+offerbook.timeSinceSigning.info.peerLimitLifted=signé par un pair et les limites ont été levées
+offerbook.timeSinceSigning.info.signer=signé par un pair et pouvant signer des comptes de pairs (limites levées)
 offerbook.timeSinceSigning.daysSinceSigning={0} jours
-offerbook.timeSinceSigning.daysSinceSigning.long={0} since signing
+offerbook.timeSinceSigning.daysSinceSigning.long={0} depuis la signature
 
-offerbook.timeSinceSigning.help=When you successfully complete a trade with a peer who has a signed payment account, your payment account is signed.\n{0} days later, the initial limit of {1} is lifted and your account can sign other peers'' payment accounts.
-offerbook.timeSinceSigning.notSigned=Not signed yet
+offerbook.timeSinceSigning.help=Lorsque vous effectuez avec succès une transaction avec un pair disposant d'un compte de paiement signé, votre compte de paiement est signé.\n{0} Jours plus tard, la limite initiale de {1} est levée et votre compte peut signer les comptes de paiement d'un autre pair.
+offerbook.timeSinceSigning.notSigned=Pas encore signé
 offerbook.timeSinceSigning.notSigned.noNeed=N/A
-shared.notSigned=This account hasn't been signed yet
-shared.notSigned.noNeed=This account type doesn't use signing
+shared.notSigned=Ce compte n'a pas encore été signé
+shared.notSigned.noNeed=Ce type de compte n'utilise pas de signature
 
 offerbook.nrOffers=Nombre d'ordres: {0}
 offerbook.volume={0} (min - max)
@@ -374,12 +374,12 @@ offerbook.warning.noTradingAccountForCurrency.msg=Vous n'avez pas de compte de t
 offerbook.warning.noMatchingAccount.headline=Pas de compte de trading correspondant.
 offerbook.warning.noMatchingAccount.msg=Pour accepter cet ordre, vous devrez établir un compte de paiement qui utilise ce mode de paiement.\n\nSouhaitez-vous le faire maintenant ?
 
-offerbook.warning.counterpartyTradeRestrictions=This offer cannot be taken due to counterparty trade restrictions
+offerbook.warning.counterpartyTradeRestrictions=Cette offre ne peut être acceptée en raison de restrictions d'échange imposées par les contreparties
 
-offerbook.warning.newVersionAnnouncement=With this version of the software, trading peers can verify and sign each others' payment accounts to create a network of trusted payment accounts.\n\nAfter successfully trading with a peer with a verified payment account, your payment account will be signed and trading limits will be lifted after a certain time interval (length of this interval is based on the verification method).\n\nFor more information on account signing, please see the documentation at https://docs.bisq.network/payment-methods#account-signing.
+offerbook.warning.newVersionAnnouncement=Avec cette version du logiciel, les pairs de trading peuvent vérifier et signer les comptes de paiement des autres pour créer un réseau de comptes de paiement vérifiés entre eux.\n\nAprès avoir effectué des transactions avec un pair disposant d'un compte de paiement vérifié, votre compte de paiement sera signé et les limites de trading seront levées après une période déterminée (la durée de cette période est basée sur la méthode de vérification).\n\nPour plus d'informations sur la signature de compte, veuillez consulter la documentation à l'adresse suivante https://docs.bisq.network/payment-methods#account-signing.
 
-popup.warning.tradeLimitDueAccountAgeRestriction.seller=The allowed trade amount is limited to {0} because of security restrictions based on the following criteria:\n- The buyer''s account has not been signed by an arbitrator or a peer\n- The time since signing of the buyer''s account is not at least 30 days\n- The payment method for this offer is considered risky for bank chargebacks\n\n{1}
-popup.warning.tradeLimitDueAccountAgeRestriction.buyer=The allowed trade amount is limited to {0} because of security restrictions based on the following criteria:\n- Your account has not been signed by an arbitrator or a peer\n- The time since signing of your account is not at least 30 days\n- The payment method for this offer is considered risky for bank chargebacks\n\n{1}
+popup.warning.tradeLimitDueAccountAgeRestriction.seller=Le montant de transaction autorisé est limité à {0} en raison des restrictions de sécurité basées sur les critères suivants:\n- Le compte de l'acheteur n'a pas été signé par un arbitre ou par un pair\n- Le délai depuis la signature du compte de l'acheteur est inférieur à 30 jours\n- Le mode de paiement pour cette offre est considéré comme présentant un risque de rétrofacturation bancaire\n\n{1}
+popup.warning.tradeLimitDueAccountAgeRestriction.buyer=Le montant de transaction autorisé est limité à {0} en raison des restrictions de sécurité basées sur les critères suivants:\n- Le compte de l'acheteur n'a pas été signé par un arbitre ou par un pair\n- Le délai depuis la signature du compte de l'acheteur est inférieur à 30 jours\n- Le mode de paiement pour cette offre est considéré comme présentant un risque de rétrofacturation bancaire\n\n{1}
 
 offerbook.warning.wrongTradeProtocol=Cet ordre exige une version de protocole différente de celle utilisée actuellement par votre logiciel.\n\nVeuillez vérifier que vous avez bien la dernière version d'installée, il est possible que l'utilisateur qui a créé cet ordre utilise une ancienne version.\n\nIl n'est pas possible de trader avec des versions différentes de protocole.
 offerbook.warning.userIgnored=Vous avez ajouté l'adresse onion de cet utilisateur à votre liste noire.
@@ -388,7 +388,7 @@ offerbook.warning.currencyBanned=La devise utilisée pour cet ordre a été bloq
 offerbook.warning.paymentMethodBanned=Le mode de paiement utilisé pour cet ordre a été bloqué par les développeurs de Bisq.\nVeuillez visiter le Forum Bisq pour obtenir plus d'informations.
 offerbook.warning.nodeBlocked=L'adresse onion de ce trader a été bloquée par les développeurs de Bisq.\nIl s'agit peut être d'un bug qui cause des problèmes lors de l'acceptation de cet ordre.
 offerbook.warning.requireUpdateToNewVersion=Votre version de Bisq n'est plus compatible pour le trading.\nVeuillez mettre à jour votre version de Bisq sur https://bisq.network/downloads.
-offerbook.warning.tradeLimitNotMatching=Votre compte de paiement a été créé il y a {0} jours. Votre limite de trading est basée sur l'ancienneté du compte qui est insuffisante pour cet ordre.\n\nVotre limite de trading est: {1}\nLe montant min. de trade pour cet ordre est: {2}.\n\nVous ne pouvez pas accepter cet ordre pour le moment. Une fois que votre compte aura atteint 2 mois d'ancienneté, cette restriction sera levée.
+offerbook.warning.tradeLimitNotMatching=Votre compte de paiement a été créé il y a {0} jours. Votre limite de trading est basée sur l'ancienneté du compte qui est insuffisante pour cet ordre.\n\nVotre limite de trading est: {1}\nLe montant min. de trade pour cet ordre est: {2}.\n\nVous ne pouvez pas accepter cet ordre pour le moment. Une fois que votre compte aura atteint 2 mois d''ancienneté, cette restriction sera levée.
 
 
 offerbook.info.sellAtMarketPrice=Vous vendrez au prix du marché (mis à jour chaque minute).
@@ -505,7 +505,7 @@ takeOffer.failed.offerTaken=Vous ne pouvez pas saisir cet ordre car elle a déj
 takeOffer.failed.offerRemoved=Vous ne pouvez pas saisir cet ordre car elle a été supprimée entre-temps.
 takeOffer.failed.offererNotOnline=La demande de prise de l'ordre a échoué parce que le maker n'est plus en ligne.
 takeOffer.failed.offererOffline=Vous ne pouvez pas saisir cet ordre car le maker n'est pas connecté.
-takeOffer.warning.connectionToPeerLost=You lost connection to the maker.\nThey might have gone offline or has closed the connection to you because of too many open connections.\n\nIf you can still see their offer in the offerbook you can try to take the offer again.
+takeOffer.warning.connectionToPeerLost=Vous avez perdu la connexion avec le maker.\nIl se peut qu'ils se soient déconnectés ou qu'ils aient interrompu la connexion avec vous en raison d'un trop grand nombre de connexions en cours.\n\nSi vous pouvez encore voir leur offre dans le livre des ordres, vous pouvez essayer d'accepter une nouvelle fois l'offre.
 
 takeOffer.error.noFundsLost=\n\nAucun fonds n'a quitté votre portefeuille pour le moment.\nVeuillez essayer de redémarrer votre application et vérifier votre connexion réseau pour voir si vous pouvez résoudre le problème.
 takeOffer.error.feePaid=\n\nVeuillez essayer de redémarrer votre application et vérifier votre connexion réseau pour voir si vous pouvez résoudre le problème.
@@ -543,8 +543,8 @@ portfolio.pending.step3_seller.confirmPaymentReceived=Confirmation de paiement r
 portfolio.pending.step5.completed=Terminé
 
 portfolio.pending.step1.info=La transaction de dépôt à été publiée.\n{0} devez attendre au moins une confirmation de la blockchain avant d''initier le paiement.
-portfolio.pending.step1.warn=The deposit transaction is still not confirmed. This sometimes happens in rare cases when the funding fee of one trader from an external wallet was too low.
-portfolio.pending.step1.openForDispute=The deposit transaction is still not confirmed. You can wait longer or contact the mediator for assistance.
+portfolio.pending.step1.warn=La transaction de dépôt n'est toujours pas confirmée. Cela se produit parfois dans de rares occasions lorsque un frais de financement d'un trader en provenance d'un portefeuille externe est trop bas.
+portfolio.pending.step1.openForDispute=La transaction de dépôt n'est toujours pas confirmée. Vous pouvez attendre plus longtemps ou contacter le médiateur pour obtenir de l'aide.
 
 # suppress inspection "TrailingSpacesInProperty"
 portfolio.pending.step2.confReached=Votre échange a été confirmé au moins une fois par la blockchain.\n(Vous pouvez attendre davantage pour obtenir plus de confirmations - 6 confirmations sont considérés comme très sures.)\n\n
@@ -580,8 +580,8 @@ portfolio.pending.step2_buyer.amountToTransfer=Montant à transférer
 portfolio.pending.step2_buyer.sellersAddress=Adresse {0} du vendeur
 portfolio.pending.step2_buyer.buyerAccount=Votre compte de paiement à utiliser
 portfolio.pending.step2_buyer.paymentStarted=Paiement initié
-portfolio.pending.step2_buyer.warn=You still have not done your {0} payment!\nPlease note that the trade has to be completed by {1}.
-portfolio.pending.step2_buyer.openForDispute=You have not completed your payment!\nThe max. period for the trade has elapsed.Please contact the mediator for assistance.
+portfolio.pending.step2_buyer.warn=Vous n'avez toujours pas effectué votre {0} paiement !\nVeuillez noter que l'échange doit être achevé par {1}.
+portfolio.pending.step2_buyer.openForDispute=Vous n'avez pas effectué votre paiement !\nLe délai maximal alloué pour ce trade est écoulé, veuillez contacter le médiateur pour obtenir de l'aide.
 portfolio.pending.step2_buyer.paperReceipt.headline=Avez-vous envoyé le reçu papier au vendeur de BTC?
 portfolio.pending.step2_buyer.paperReceipt.msg=Rappelez-vous: \nVous devez écrire sur le reçu papier: PAS DE REMBOURSEMENT.\nEnsuite, veuillez le déchirer en 2, faire une photo et l'envoyer à l'adresse email du vendeur.
 portfolio.pending.step2_buyer.moneyGramMTCNInfo.headline=Envoyer le numéro d'autorisation ainsi que le reçu
@@ -599,11 +599,11 @@ portfolio.pending.step2_seller.waitPayment.headline=En attende du paiement
 portfolio.pending.step2_seller.f2fInfo.headline=Coordonnées de l'acheteur
 portfolio.pending.step2_seller.waitPayment.msg=La transaction de dépôt a été vérifiée au moins une fois sur la blockchain\nVous devez attendre que l''acheteur de BTC lance le {0} payment.
 portfolio.pending.step2_seller.warn=L''acheteur de BTC n'a toujours pas effectué le paiement {0}.\nVeuillez attendre qu'il effectue celui-ci.\nSi la transaction n'est pas effectuée le {1}, un arbitre enquêtera.
-portfolio.pending.step2_seller.openForDispute=The BTC buyer has not started their payment!\nThe max. allowed period for the trade has elapsed.\nYou can wait longer and give the trading peer more time or contact the mediator for assistance.
+portfolio.pending.step2_seller.openForDispute=L'acheteur de BTC n'a pas initié son paiement !\nLa période maximale autorisée pour ce trade est écoulée.\nVous pouvez attendre plus longtemps et accorder plus de temps à votre pair de trading ou contacter le médiateur pour obtenir de l'aide.
 
-tradeChat.chatWindowTitle=Chat window for trade with ID ''{0}''
-tradeChat.openChat=Open chat window
-tradeChat.rules=You can communicate with your trade peer to resolve potential problems with this trade.\nIt is not mandatory to reply in the chat.\nIf a trader violates any of the rules below, open a dispute and report it to the mediator or arbitrator.\n\nChat rules:\n\t● Do not send any links (risk of malware). You can send the transaction ID and the name of a block explorer.\n\t● Do not send your seed words, private keys, passwords or other sensitive information!\n\t● Do not encourage trading outside of Bisq (no security).\n\t● Do not engage in any form of social engineering scam attempts.\n\t● If a peer is not responding and prefers to not communicate via chat, respect their decision.\n\t● Keep conversation scope limited to the trade. This chat is not a messenger replacement or troll-box.\n\t● Keep conversation friendly and respectful.
+tradeChat.chatWindowTitle=Fenêtre de discussion pour la transaction avec l'ID ''{0}''
+tradeChat.openChat=Ouvrir une fenêtre de discussion
+tradeChat.rules=Vous pouvez communiquer avec votre pair de trading pour résoudre les problèmes potentiels liés à ce trade.\nIl n'est pas obligatoire de répondre sur le chat.\nSi un trader enfreint l'une des règles ci-dessous, ouvrez un litige et signalez-le au médiateur ou à l'arbitre.\n\nRègles sur le chat:\n\t● N'envoyez pas de liens (risque de malware). Vous pouvez envoyer l'ID de transaction et le nom d'un explorateur de blocs.\n\t● N'envoyez pas les mots de votre seed, clés privées, mots de passe ou autres informations sensibles !\n\t● N'encouragez pas le trading en dehors de Bisq (non sécurisé).\n\t● Ne vous engagez dans aucune forme d'escroquerie d'ingénierie sociale.\n\t● Si un pair ne répond pas et préfère ne pas communiquer par chat, respectez sa décision.\n\t● Limitez la portée de la conversation au trade. Ce chat n'est pas une alternative à messager ou une troll-box.\n\t● Entretenez une conversation amicale et respectueuse.
 
 # suppress inspection "UnusedProperty"
 message.state.UNDEFINED=Indéfini
@@ -612,7 +612,7 @@ message.state.SENT=Message envoyé
 # suppress inspection "UnusedProperty"
 message.state.ARRIVED=Message reçu par le pair
 # suppress inspection "UnusedProperty"
-message.state.STORED_IN_MAILBOX=Message of payment sent but not yet received by peer
+message.state.STORED_IN_MAILBOX=Message de paiement bien envoyé mais pas encore reçu par le pair
 # suppress inspection "UnusedProperty"
 message.state.ACKNOWLEDGED=Le pair a confirmé la réception du message
 # suppress inspection "UnusedProperty"
@@ -623,8 +623,8 @@ portfolio.pending.step3_buyer.wait.info=En attente de la confirmation du vendeur
 portfolio.pending.step3_buyer.wait.msgStateInfo.label=État du message de lancement du paiement
 portfolio.pending.step3_buyer.warn.part1a=sur la {0} blockchain
 portfolio.pending.step3_buyer.warn.part1b=chez votre prestataire de paiement (par ex. banque)
-portfolio.pending.step3_buyer.warn.part2=The BTC seller still has not confirmed your payment. Please check {0} if the payment sending was successful.
-portfolio.pending.step3_buyer.openForDispute=The BTC seller has not confirmed your payment! The max. period for the trade has elapsed. You can wait longer and give the trading peer more time or request assistance from the mediator.
+portfolio.pending.step3_buyer.warn.part2=Le vendeur de BTC n'a toujours pas confirmé votre paiement. . Veuillez vérifier {0} si l'envoi du paiement a bien fonctionné.
+portfolio.pending.step3_buyer.openForDispute=Le vendeur de BTC n'a pas confirmé votre paiement ! Le délai maximal alloué pour ce trade est écoulé. Vous pouvez attendre plus longtemps et accorder plus de temps à votre pair de trading ou contacter le médiateur pour obtenir de l'aide.
 # suppress inspection "TrailingSpacesInProperty"
 portfolio.pending.step3_seller.part=Votre partenaire de trading a confirmé qu''il a initié le paiement {0}.\n
 portfolio.pending.step3_seller.altcoin.explorer=Sur votre explorateur blockchain {0} favori
@@ -638,8 +638,8 @@ portfolio.pending.step3_seller.moneyGram=L'acheteur doit vous envoyer le numéro
 portfolio.pending.step3_seller.westernUnion=L'acheteur doit vous envoyer le MTCN (numéro de suivi) et une photo du reçu par e-mail .\nLe reçu doit faire clairement figurer votre nom complet, votre pays, l'état et le montant. Veuillez s'il vous plaît vérifier si vous avez reçu par e-mail le MTCN.\n\nAprès avoir fermé ce popup vous verrez le nom de l'acheteur de BTC et l'adresse où retirer l'argent depuis Western Union.\n\nN'accusez réception qu'après avoir retiré l'argent avec succès!
 portfolio.pending.step3_seller.halCash=L'acheteur doit vous envoyer le code HalCash par message texte SMS. Par ailleurs, vous recevrez un message de la part d'HalCash avec les informations nécessaires pour retirer les EUR depuis un DAB Bancaire supportant HalCash.\n\nAprès avoir retiré l'argent au DAB, veuillez confirmer ici la réception du paiement !
 
-portfolio.pending.step3_seller.bankCheck=\n\nPlease also verify that the name of the sender specified on the trade contract matches the name that appears on your bank statement:\nSender''s name, per trade contract: {0}\n\nIf the names are not exactly the same, {1}
-portfolio.pending.step3_seller.openDispute=don't confirm payment receipt. Instead, open a dispute by pressing \"alt + o\" or \"option + o\".\n\n
+portfolio.pending.step3_seller.bankCheck=\n\nVeuillez également vérifier que le nom de l'expéditeur indiqué sur le contrat du trade correspond au nom qui apparaît sur votre relevé bancaire:\nNom de l'expéditeur, avec le contrat de trade: {0}\n\nSi les noms ne sont pas exactement identiques, {1}
+portfolio.pending.step3_seller.openDispute=Ne confirmez pas la réception du paiement. Au lieu de cela, ouvrez un litige en appuyant sur \"alt + o\" ou \"option + o\".\n\n
 portfolio.pending.step3_seller.confirmPaymentReceipt=Confirmer la réception du paiement
 portfolio.pending.step3_seller.amountToReceive=Montant à recevoir
 portfolio.pending.step3_seller.yourAddress=Votre adresse {0}
@@ -652,15 +652,15 @@ portfolio.pending.step3_seller.buyerStartedPayment.altcoin=Vérifiez la présenc
 portfolio.pending.step3_seller.buyerStartedPayment.fiat=Vérifiez sur votre compte de trading (par ex. compte bancaire) et confirmez quand vous avez reçu le paiement.
 portfolio.pending.step3_seller.warn.part1a=sur la {0} blockchain
 portfolio.pending.step3_seller.warn.part1b=Auprès de votre prestataire de paiement (par ex. banque)
-portfolio.pending.step3_seller.warn.part2=You still have not confirmed the receipt of the payment. Please check {0} if you have received the payment.
-portfolio.pending.step3_seller.openForDispute=You have not confirmed the receipt of the payment!\nThe max. period for the trade has elapsed.\nPlease confirm or request assistance from the mediator.
+portfolio.pending.step3_seller.warn.part2=Vous n'avez toujours pas confirmé la réception du paiement. Veuillez vérifier {0} si vous avez reçu le paiement.
+portfolio.pending.step3_seller.openForDispute=Vous n'avez pas confirmé la réception du paiement !\nLe délai maximal alloué pour ce trade est écoulé.\nVeuillez confirmer ou demander l'aide du médiateur.
 # suppress inspection "TrailingSpacesInProperty"
 portfolio.pending.step3_seller.onPaymentReceived.part1=Avez-vous reçu le paiement {0} de votre partenaire de trading?\n\n
 # suppress inspection "TrailingSpacesInProperty"
 portfolio.pending.step3_seller.onPaymentReceived.fiat=Le trade ID (\"reason for payment\" text) de la transaction est: \"{0}\"\n\n
 # suppress inspection "TrailingSpacesInProperty"
-portfolio.pending.step3_seller.onPaymentReceived.name=Please also verify that the name of the sender specified on the trade contract matches the name that appears on your bank statement:\nSender''s name, per trade contract: {0}\n\nIf the names are not exactly the same, don''t confirm payment receipt. Instead, open a dispute by pressing \"alt + o\" or \"option + o\".\n\n
-portfolio.pending.step3_seller.onPaymentReceived.note=Please note, that as soon you have confirmed the receipt, the locked trade amount will be released to the BTC buyer and the security deposit will be refunded.\n\n
+portfolio.pending.step3_seller.onPaymentReceived.name=Veuillez également vérifier que le nom de l'expéditeur indiqué sur le contrat du trade correspond au nom qui apparaît sur votre relevé bancaire:\nNom de l'expéditeur, avec le contrat du trade: {0}\n\nSi les noms ne sont pas exactement identiques, ne confirmez pas la réception du paiement. Au lieu de cela, ouvrez un litige en appuyant sur \"alt + o\" ou \"option + o\".\n\n
+portfolio.pending.step3_seller.onPaymentReceived.note=Veuillez noter que dès que vous aurez confirmé la réception, le montant verrouillé pour la transaction sera remis à l'acheteur de BTC et le dépôt de garantie vous sera remboursé.\n
 portfolio.pending.step3_seller.onPaymentReceived.confirm.headline=Confirmez que vous avez bien reçu le paiement
 portfolio.pending.step3_seller.onPaymentReceived.confirm.yes=Oui, j'ai reçu le paiement
 portfolio.pending.step3_seller.onPaymentReceived.signer=IMPORTANT: By confirming receipt of payment, you are also verifying the account of the counterparty and signing it accordingly. Since the account of the counterparty hasn't been signed yet, you should delay confirmation of the payment as long as possible to reduce the risk of a chargeback.
@@ -672,7 +672,6 @@ portfolio.pending.step5_buyer.takersMiningFee=Total des frais de minage
 portfolio.pending.step5_buyer.refunded=Dépôt de garantie remboursé
 portfolio.pending.step5_buyer.withdrawBTC=Retirer vos Bitcoins
 portfolio.pending.step5_buyer.amount=Montant à retirer
-portfolio.pending.step5_buyer.signer=By withdrawing your bitcoins, you verify that the counterparty has acted according to the trade protocol.
 portfolio.pending.step5_buyer.withdrawToAddress=Retirer vers l'adresse
 portfolio.pending.step5_buyer.moveToBisqWallet=Transférer les fonds vers le portefeuille bisq
 portfolio.pending.step5_buyer.withdrawExternal=Retrait vers un portefeuille externe
@@ -700,58 +699,58 @@ portfolio.pending.tradePeriodInfo=Après la première confirmation de la blockch
 portfolio.pending.tradePeriodWarning=Si le délai est dépassé, l'es deux participants du trade peuvent ouvrir un litige.
 portfolio.pending.tradeNotCompleted=Trade inachevé dans le temps imparti (jusqu''à {0})
 portfolio.pending.tradeProcess=Processus de transaction
-portfolio.pending.openAgainDispute.msg=If you are not sure that the message to the mediator or arbitrator arrived (e.g. if you did not get a response after 1 day) feel free to open a dispute again with Cmd/Ctrl+o. You can also ask for additional help on the Bisq forum at https://bisq.community.
+portfolio.pending.openAgainDispute.msg=Si vous n'êtes pas certain que le message au médiateur ou à l'arbitre soit arrivé (par exemple si vous n'avez pas reçu de réponse après 1 jour), n'hésitez pas à ouvrir à nouveau un litige avec Cmd/Ctrl+o. Vous pouvez également demander de l'aide complémentaire sur le forum Bisq à l'adresse https://bisq.community.
 portfolio.pending.openAgainDispute.button=Ouvrir à nouveau le litige
 portfolio.pending.openSupportTicket.headline=Ouvrir un ticket d'assistance
-portfolio.pending.openSupportTicket.msg=Please use this function only in emergency cases if you don't see a \"Open support\" or \"Open dispute\" button.\n\nWhen you open a support ticket the trade will be interrupted and handled by a mediator or arbitrator.
+portfolio.pending.openSupportTicket.msg=S'il vous plaît n'utilisez seulement cette fonction qu'en cas d'urgence si vous ne pouvez pas voir le bouton \"Open support\" ou \"Ouvrir un litige\.\n\nLorsque vous ouvrez un ticket de support, le trade sera interrompu et prise en charge par le médiateur ou par l'arbitre.
 
-portfolio.pending.timeLockNotOver=You have to wait until ≈{0} ({1} more blocks) before you can open an arbitration dispute.
+portfolio.pending.timeLockNotOver=Vous devez patienter jusqu'à ≈{0} ({1} plus de blocs) avant que vous ne puissiez ouvrir un arbitrage pour le litige.
 portfolio.pending.error.depositTxNull=The deposit transaction is null. You cannot open a dispute without a valid deposit transaction. Please go to \"Settings/Network info\" and do a SPV resync.\n\nFor further help please contact the Bisq support channel at the Bisq Keybase team.
-portfolio.pending.mediationResult.error.depositTxNull=The deposit transaction is null. The trade gets moved to the failed trades section.
+portfolio.pending.mediationResult.error.depositTxNull=La transaction de dépôt est nulle. L'échange est déplacé vers la section des échanges en échec.
 portfolio.pending.error.depositTxNotConfirmed=The deposit transaction is not confirmed. You can not open an arbitration dispute with an unconfirmed deposit transaction. Please wait until it is confirmed or go to \"Settings/Network info\" and do a SPV resync.\n\nFor further help please contact the Bisq support channel at the Bisq Keybase team.
 
 portfolio.pending.notification=Notification
 
-portfolio.pending.support.headline.getHelp=Need help?
+portfolio.pending.support.headline.getHelp=Besoin d'aide ?
 portfolio.pending.support.text.getHelp=If you have any problems you can try to contact the trade peer in the trade chat or ask the Bisq community at https://bisq.community. If your issue still isn't resolved, you can request more help from a mediator.
 portfolio.pending.support.text.getHelp.arbitrator=If you have any problems you can try to contact the trade peer in the trade chat or ask the Bisq community at https://bisq.community. If your issue still isn't resolved, you can request more help from an arbitrator.
-portfolio.pending.support.button.getHelp=Get support
+portfolio.pending.support.button.getHelp=Obtenir de l'aide
 portfolio.pending.support.popup.info=If your issue with the trade remains unsolved, you can open a support ticket to request help from a mediator. If you have not received the payment, please wait until the trade period is over.\n\nAre you sure you want to open a support ticket?
 portfolio.pending.support.popup.button=Ouvrir un ticket d'assistance
-portfolio.pending.support.headline.halfPeriodOver=Check payment
-portfolio.pending.support.headline.periodOver=La période d'échange été terminé
+portfolio.pending.support.headline.halfPeriodOver=Vérifier le paiement
+portfolio.pending.support.headline.periodOver=Le délai alloué pour ce trade est écoulé.
 
-portfolio.pending.mediationRequested=Mediation requested
-portfolio.pending.refundRequested=Refund requested
+portfolio.pending.mediationRequested=Médiation demandée
+portfolio.pending.refundRequested=Remboursement demandé
 portfolio.pending.openSupport=Ouvrir un ticket d'assistance
 portfolio.pending.supportTicketOpened=Ticket d'assistance ouvert
 portfolio.pending.requestSupport=Demander de l'aide
-portfolio.pending.error.requestSupport=Please report the problem to your mediator or arbitrator.\n\nThey will forward the information to the developers to investigate the problem.\nAfter the problem has been analyzed you will get back all locked funds.
+portfolio.pending.error.requestSupport=Veuillez signaler le problème à votre médiateur ou à votre arbitre.\n\nIls transmettront l'information aux développeurs pour enquêter sur le problème.\nUne fois le problème analysé, vous récupérerez tous les fonds bloqués.
 portfolio.pending.communicateWithArbitrator=Veuillez communiquer avec l'arbitre depuis l'écran "Support".
-portfolio.pending.communicateWithMediator=Please communicate in the \"Support\" screen with the mediator.
+portfolio.pending.communicateWithMediator=Veuillez communiquer avec le médiateur dans l'onglet \"Support \".
 portfolio.pending.supportTicketOpenedMyUser=Vous avez déjà ouvert un ticket d''assistance.\n{0}
 portfolio.pending.disputeOpenedMyUser=Vous avez déjà ouvert un litige.\n{0}
 portfolio.pending.disputeOpenedByPeer=Votre pair de trading à ouvert un litige\n{0}
 portfolio.pending.supportTicketOpenedByPeer=Votre pair de trading a ouvert un ticket d’assistance.\n{0}
 portfolio.pending.noReceiverAddressDefined=Aucune adresse de destinataire définie
-portfolio.pending.removeFailedTrade=Is this a failed trade? If so, would you like to manually close it, so that it no longer shows as an open trade?
+portfolio.pending.removeFailedTrade=Est-ce un échange en échec ? Si oui, souhaitez-vous le fermer manuellement, de sorte qu'il ne s'affiche plus comme un échange en cours ?
 
-portfolio.pending.mediationResult.headline=Suggested payout from mediation
-portfolio.pending.mediationResult.info.noneAccepted=Complete the trade by accepting the mediator's suggestion for the trade payout.
-portfolio.pending.mediationResult.info.selfAccepted=You have accepted the mediator's suggestion. Waiting for peer to accept as well.
-portfolio.pending.mediationResult.info.peerAccepted=Your trade peer has accepted the mediator's suggestion. Do you accept as well?
-portfolio.pending.mediationResult.button=View proposed resolution
-portfolio.pending.mediationResult.popup.headline=Mediation result for trade with ID: {0}
-portfolio.pending.mediationResult.popup.headline.peerAccepted=Your trade peer has accepted the mediator''s suggestion for trade {0}
-portfolio.pending.mediationResult.popup.info=The mediator has suggested the following payout:\nYou receive: {0}\nYour trading peer receives: {1}\n\nYou can accept or reject this suggested payout.\n\nBy accepting, you sign the proposed payout transaction. If your trading peer also accepts and signs, the payout will be completed, and the trade will be closed.\n\nIf one or both of you reject the suggestion, you will have to wait until {2} (block {3}) to open a second-round dispute with an arbitrator who will investigate the case again and do a payout based on their findings.\n\nThe arbitrator may charge a small fee (fee maximum: the trader''s security deposit) as compensation for their work. Both traders agreeing to the mediator''s suggestion is the happy path—requesting arbitration is meant for exceptional circumstances, such as if a trader is sure the mediator did not make a fair payout suggestion (or if the other peer is unresponsive).\n\nMore details about the new arbitration model:\nhttps://docs.bisq.network/trading-rules.html#arbitration
-portfolio.pending.mediationResult.popup.openArbitration=Reject and request arbitration
-portfolio.pending.mediationResult.popup.alreadyAccepted=You've already accepted
+portfolio.pending.mediationResult.headline=Montant suggéré par la médiation
+portfolio.pending.mediationResult.info.noneAccepted=Terminez la transaction en acceptant la suggestion du médiateur concernant le paiement de la transaction.
+portfolio.pending.mediationResult.info.selfAccepted=Vous avez accepté la suggestion du médiateur. En attente que le pair l'accepte également.
+portfolio.pending.mediationResult.info.peerAccepted=Votre pair de trading a accepté la suggestion du médiateur. L'acceptez-vous également ?
+portfolio.pending.mediationResult.button=Voir la résolution proposée
+portfolio.pending.mediationResult.popup.headline=Résultat de la médiation pour la transaction avec l'ID: {0}
+portfolio.pending.mediationResult.popup.headline.peerAccepted=Votre pair de trading a accepté la suggestion du médiateur pour la transaction {0}
+portfolio.pending.mediationResult.popup.info=Le médiateur a suggéré le paiement suivant:\nVous recevez: {0}\nVotre pair de trading recevra: {1}\n\nVous pouvez accepter ou rejeter cette proposition de paiement.\n\nEn acceptant, vous signez la proposition de transaction de paiement. Si votrepair de trading accepte et signe également, le paiement sera terminé et la transaction sera soldée.\n\nSi l'un d'entre vous ou l'un d'entre vous rejette la proposition, vous devrez attendre jusqu'à {2} (block {3}) pour ouvrir un litige en deuxième instance avec un arbitre qui enquêtera de nouveau sur la situation et effectuera un paiement en fonction de ses conclusions.\n\nL'arbitre peut imputer des frais minimes (frais maximal : le dépôt de garantie du trader) au titre de rémunération pour son travail. Les deux trader acceptant la suggestion du médiateur créant ainsi une résolution heureuse—la demande d'arbitrage est prévue pour des circonstances exceptionnelles, par exemple si un trader est convaincu que le médiateur n'a pas proposé une solution de paiement équitable (ou si l'autre pair ne répond pas).\n\nPlus de détails sur le nouveau modèle d'arbitrage:\nhttps://docs.bisq.network/trading-rules.html#arbitration
+portfolio.pending.mediationResult.popup.openArbitration=Refuser et demander un arbitrage
+portfolio.pending.mediationResult.popup.alreadyAccepted=Vous avez déjà accepté
 
 portfolio.closed.completed=Terminé
-portfolio.closed.ticketClosed=Arbitrated
-portfolio.closed.mediationTicketClosed=Mediated
+portfolio.closed.ticketClosed=Arbitré
+portfolio.closed.mediationTicketClosed=Ayant fait l'objet d'une médiation
 portfolio.closed.canceled=Annulé
-portfolio.failed.Failed=Echec
+portfolio.failed.Failed=Échec
 
 
 ####################################################################
@@ -812,9 +811,9 @@ funds.tx.multiSigDeposit=Dépôt multisig: {0}
 funds.tx.multiSigPayout=Versement  Multisig: {0}
 funds.tx.disputePayout=Versement du litige: {0}
 funds.tx.disputeLost=Cas de litige perdu: {0}
-funds.tx.collateralForRefund=Refund collateral: {0}
+funds.tx.collateralForRefund=Remboursement du dépôt de garantie: {0}
 funds.tx.timeLockedPayoutTx=Time locked payout tx: {0}
-funds.tx.refund=Refund from arbitration: {0}
+funds.tx.refund=Remboursement venant de l'arbitrage: {0}
 funds.tx.unknown=Raison inconnue: {0}
 funds.tx.noFundsFromDispute=Aucun remboursement en cas de litige
 funds.tx.receivedFunds=Fonds reçus
@@ -835,15 +834,15 @@ funds.tx.dustAttackTx.popup=Cette transaction va envoyer un faible montant en BT
 # Support
 ####################################################################
 
-support.tab.mediation.support=Mediation
-support.tab.arbitration.support=Arbitration
-support.tab.legacyArbitration.support=Legacy Arbitration
-support.tab.ArbitratorsSupportTickets={0}'s tickets
+support.tab.mediation.support=Médiation
+support.tab.arbitration.support=Arbitrage
+support.tab.legacyArbitration.support=Conclusion d'arbitrage
+support.tab.ArbitratorsSupportTickets=Tickets de {0}
 support.filter=Liste de filtre
 support.filter.prompt=Saisissez l'ID du trade, la date, l'adresse "onion" ou les données du compte.
 support.noTickets=Il n'y a pas de tickets ouverts
 support.sendingMessage=Envoi du message...
-support.receiverNotOnline=Receiver is not online. Message is saved to their mailbox.
+support.receiverNotOnline=Le destinataire n'est pas en ligne. Le message est enregistré dans leur boîte mail.
 support.sendMessageError=Échec de l''envoi du message. Erreur: {0}
 support.wrongVersion=L''ordre relatif au litige en question a été créé avec une ancienne version de Bisq.\nVous ne pouvez pas clore ce litige avec votre version de l''application.\n\nVeuillez utiliser une version plus ancienne avec la version du protocole {0}
 support.openFile=Ouvrir le fichier à joindre (taille max. du fichier : {0} kb)
@@ -853,7 +852,7 @@ support.attachment=Pièces jointes
 support.tooManyAttachments=Vous ne pouvez envoyer plus de 3 pièces jointes dans un message.
 support.save=Sauvegarder le fichier sur le disque
 support.messages=Messages
-support.input.prompt=Enter message...
+support.input.prompt=Entrer le message...
 support.send=Envoyer
 support.addAttachments=Ajouter des pièces jointes
 support.closeTicket=Fermer le ticket
@@ -873,17 +872,17 @@ support.sellerOfferer=Vendeur BTC/Maker
 support.buyerTaker=Acheteur BTC/Taker
 support.sellerTaker=Vendeur BTC/Taker
 
-support.backgroundInfo=Bisq is not a company, so it handles disputes differently.\n\nTraders can communicate within the application via a secure chat on the open trades screen to attempt solving a dispute on their own. If that is not sufficient, a mediator can step in to help. The mediator will evaluate the situation and give a recommendation for the payout of the trade funds. If both traders accept this suggestion, the payout transaction is completed and the trade is closed. If one or both traders do not agree to the mediator's recommended payout, they can request arbitration.The arbitrator has the third key of the deposit transaction and will make the payout based on their findings.
+support.backgroundInfo=Bisq is not a company, so it handles disputes differently.\n\nTraders can communicate within the application via secure chat on the open trades screen to try solving disputes on their own. If that is not sufficient, a mediator can step in to help. The mediator will evaluate the situation and suggest a payout of trade funds. If both traders accept this suggestion, the payout transaction is completed and the trade is closed. If one or both traders do not agree to the mediator's suggested payout, they can request arbitration.The arbitrator will re-evaluate the situation and, if warranted, personally pay the trader back and request reimbursement for this payment from the Bisq DAO.
 support.initialInfo=Please enter a description of your problem in the text field below. Add as much information as possible to speed up dispute resolution time.\n\nHere is a check list for information you should provide:\n\t● If you are the BTC buyer: Did you make the Fiat or Altcoin transfer? If so, did you click the 'payment started' button in the application?\n\t● If you are the BTC seller: Did you receive the Fiat or Altcoin payment? If so, did you click the 'payment received' button in the application?\n\t● Which version of Bisq are you using?\n\t● Which operating system are you using?\n\t● If you encountered an issue with failed transactions please consider switching to a new data directory.\n\t  Sometimes the data directory gets corrupted and leads to strange bugs. \n\t  See: https://docs.bisq.network/backup-recovery.html#switch-to-a-new-data-directory\n\nPlease make yourself familiar with the basic rules for the dispute process:\n\t● You need to respond to the {0}''s requests within 2 days.\n\t● Mediators respond in between 2 days. Arbitrators respond in between 5 business days.\n\t● The maximum period for a dispute is 14 days.\n\t● You need to cooperate with the {1} and provide the information they request to make your case.\n\t● You accepted the rules outlined in the dispute document in the user agreement when you first started the application.\n\nYou can read more about the dispute process at: {2}
 support.systemMsg=Message du système: {0}
 support.youOpenedTicket=Vous avez ouvert une demande de support.\n\n{0}\n\nBisq version: {1}
 support.youOpenedDispute=Vous avez ouvert une demande de litige.\n\n{0}\n\nBisq version: {1}
-support.youOpenedDisputeForMediation=You requested mediation.\n\n{0}\n\nBisq version: {1}
-support.peerOpenedTicket=Your trading peer has requested support due to technical problems.\n\n{0}\n\nBisq version: {1}
-support.peerOpenedDispute=Your trading peer has requested a dispute.\n\n{0}\n\nBisq version: {1}
-support.peerOpenedDisputeForMediation=Your trading peer has requested mediation.\n\n{0}\n\nBisq version: {1}
-support.mediatorsDisputeSummary=System message:\nMediator''s dispute summary:\n{0}
-support.mediatorsAddress=Mediator''s node address: {0}
+support.youOpenedDisputeForMediation=Vous avez demandé une médiation.\n\n{0}\n\nVersion de Bisq: {1}
+support.peerOpenedTicket=Votre pair de trading a demandé une assistance en raison de problèmes techniques.\n\n{0}\n\nVersion de Bisq: {1}
+support.peerOpenedDispute=Votre partenaire de trading a fait une demande de litige.\n\n{0}\n\nBisq version: {1}
+support.peerOpenedDisputeForMediation=Votre pair de trading a demandé une médiation.\n\n{0}\n\nVersion de Bisq: {1}
+support.mediatorsDisputeSummary=Message du système:\nSynthèse du litige du médiateur:\n{0}
+support.mediatorsAddress=Adresse du nœud du médiateur: {0}
 
 
 ####################################################################
@@ -902,7 +901,7 @@ setting.preferences.txFee=Frais de transaction du retrait (satoshis/byte)
 setting.preferences.useCustomValue=Utiliser une valeur personnalisée
 setting.preferences.txFeeMin=Les frais de transaction doivent être d''au moins {0} satoshis/octet
 setting.preferences.txFeeTooLarge=Votre saisie est supérieure à toute valeur raisonnable (>5000 satoshis/octet). Les frais de transaction sont généralement de l'ordre de 50-400 satoshis/octet.
-setting.preferences.ignorePeers=pairs ignorés [adresse onion:port]
+setting.preferences.ignorePeers=Pairs ignorés [adresse onion:port]
 setting.preferences.refererId=ID de parrainage
 setting.preferences.ignoreDustThreshold=Valeur de l'output considérée comme "non-dust" minimale
 setting.preferences.refererId.prompt=ID de parrainage optionel
@@ -918,7 +917,7 @@ setting.preferences.addAltcoin=Ajouter un altcoin
 setting.preferences.displayOptions=Afficher les options
 setting.preferences.showOwnOffers=Montrer mes ordres dans le livre des ordres
 setting.preferences.useAnimations=Utiliser des animations
-setting.preferences.useDarkMode=Use dark mode (beta)
+setting.preferences.useDarkMode=Utiliser le mode sombre (beta)
 setting.preferences.sortWithNumOffers=Trier les listes de marché avec le nombre d'ordres/de transactions
 setting.preferences.resetAllFlags=Réinitialiser toutes les balises de notification \"Don't show again\"
 setting.preferences.reset=Réinitialiser
@@ -928,7 +927,7 @@ settings.preferences.selectCurrencyNetwork=Sélectionner un réseau
 setting.preferences.daoOptions=Options DAO
 setting.preferences.dao.resync.label=Reconstituer l'état de la DAO à partir du tx genesis
 setting.preferences.dao.resync.button=Resynchronisation
-setting.preferences.dao.resync.popup=After an application restart the Bisq network governance data will be reloaded from the seed nodes and the BSQ consensus state will be rebuilt from the genesis transaction.
+setting.preferences.dao.resync.popup=Après un redémarrage de l'application, les données de gouvernance du réseau P2P Bisq seront retransmises à partir des seed nodes et l'état du consensus BSQ sera récrée depuis la transaction genesis.
 setting.preferences.dao.isDaoFullNode=Exécuter la DAO de Bisq en tant que full node
 setting.preferences.dao.rpcUser=Nom d'utilisateur RPC
 setting.preferences.dao.rpcPw=Mot de passe RPC
@@ -938,7 +937,7 @@ setting.preferences.dao.fullNodeInfo.ok=Ouvrir la page des docs
 setting.preferences.dao.fullNodeInfo.cancel=Non, je m'en tiens au mode lite node
 
 settings.net.btcHeader=Réseau Bitcoin
-settings.net.p2pHeader=Bisq network
+settings.net.p2pHeader=Le réseau Bisq
 settings.net.onionAddressLabel=Mon adresse onion
 settings.net.btcNodesLabel=Utiliser des nœuds Bitcoin Core personnalisés
 settings.net.bitcoinPeersLabel=Pairs connectés
@@ -960,12 +959,12 @@ settings.net.totalTrafficLabel=Traffic total
 settings.net.roundTripTimeColumn=Roundtrip
 settings.net.sentBytesColumn=Envoyé
 settings.net.receivedBytesColumn=Reçu
-settings.net.peerTypeColumn=type de pair
+settings.net.peerTypeColumn=Type de pair
 settings.net.openTorSettingsButton=Ouvrez les paramètres de Tor
 
 settings.net.versionColumn=Version
-settings.net.subVersionColumn=Subversion
-settings.net.heightColumn=Height
+settings.net.subVersionColumn=Sous-version
+settings.net.heightColumn=Hauteur
 
 settings.net.needRestart=Vous devez redémarrer l'application pour appliquer cette modification.\nVous voulez faire cela maintenant?
 settings.net.notKnownYet=Pas encore connu...
@@ -978,7 +977,7 @@ settings.net.inbound=inbound
 settings.net.outbound=outbound
 settings.net.reSyncSPVChainLabel=Resynchronisation de la chaîne SPV
 settings.net.reSyncSPVChainButton=Supprimer le fichier SPV et resynchroniser
-settings.net.reSyncSPVSuccess=The SPV chain file will be deleted on the next startup. You need to restart your application now.\n\nAfter the restart it can take a while to resync with the network and you will only see all transactions once the resync is completed.\n\nDepending on the number of transactions and the age of your wallet the resync can take up to a few hours and consumes 100% of CPU. Do not interrupt the process otherwise you have to repeat it.
+settings.net.reSyncSPVSuccess=Le fichier de la chaîne SPV sera supprimé au prochain démarrage. Vous devez redémarrer votre application maintenant.\n\nAprès le redémarrage, la resynchronisation avec le réseau peut prendre un certain temps, vous serez en mesure de voir toutes les transactions seulement une fois que la resynchronisation sera terminée.\n\nSelon le nombre de transactions et l"ancienneté de votre portefeuille, la resynchronisation peut prendre jusqu"à quelques heures et consomme 100% du CPU. N'interrompez pas le processus, sinon vous devez le recommencer.
 settings.net.reSyncSPVAfterRestart=Le fichier de la chaîne SPV a été supprimé. Veuillez s'il vous plaît patienter. La resynchronisation avec le réseau peut nécessiter un certain temps.
 settings.net.reSyncSPVAfterRestartCompleted=La resynchronisation est maintenant terminée. Veuillez redémarrer l'application.
 settings.net.reSyncSPVFailed=Impossible de supprimer le fichier de la chaîne SPV.\nErreur: {0}
@@ -1007,11 +1006,11 @@ setting.about.subsystems.val=Version du réseau: {0}; version des messages P2P:
 ####################################################################
 
 account.tab.arbitratorRegistration=Enregistrement de l'arbitre
-account.tab.mediatorRegistration=Mediator registration
-account.tab.refundAgentRegistration=Refund agent registration
+account.tab.mediatorRegistration=Enregistrement du médiateur
+account.tab.refundAgentRegistration=Enregistrement de l'agent de remboursement
 account.tab.account=Compte
 account.info.headline=Bienvenue sur votre compte Bisq
-account.info.msg=Here you can add trading accounts for national currencies & altcoins and create a backup of your wallet & account data.\n\nA new Bitcoin wallet was created the first time you started Bisq.\n\nWe strongly recommend that you write down your Bitcoin wallet seed words (see tab on the top) and consider adding a password before funding. Bitcoin deposits and withdrawals are managed in the \"Funds\" section.\n\nPrivacy & security note: because Bisq is a decentralized exchange, all your data is kept on your computer. There are no servers, so we have no access to your personal info, your funds, or even your IP address. Data such as bank account numbers, altcoin & Bitcoin addresses, etc are only shared with your trading partner to fulfill trades you initiate (in case of a dispute the mediator or arbitrator will see the same data as your trading peer).
+account.info.msg=Ici, vous pouvez ajouter des comptes de trading en devises nationales et en altcoins et créer une sauvegarde de votre portefeuille ainsi que des données de votre compte.\n\nUn nouveau portefeuille Bitcoin a été créé un premier lancement de Bisq.\n\nNous vous recommandons vivement d'écrire les mots-clés de votre seed  de portefeuille Bitcoin (voir l'onglet en haut) et d'envisager d'ajouter un mot de passe avant le transfert de fonds. Les dépôts et retraits de Bitcoin sont gérés dans la section \"Fonds\".\n\nNotice de confidentialité et de sécurité : Bisq étant une plateforme d'échange décentralisée, toutes vos données sont conservées sur votre ordinateur. Il n'y a pas de serveurs, nous n'avons donc pas accès à vos informations personnelles, à vos fonds ou même à votre adresse IP. Les données telles que les numéros de compte bancaire, les adresses altcoin & Bitcoin, etc ne sont partagées avec votre partenaire de trading que pour effectuer les transactions que vous initiez (en cas de litige, le médiateur et l’arbitre verront les mêmes données que votre pair de trading).
 
 account.menu.paymentAccount=Comptes en devise nationale
 account.menu.altCoinsAccountView=Compte Altcoins
@@ -1023,31 +1022,31 @@ account.menu.notifications=Notifications
 ## TODO should we rename the following to a gereric name?
 account.arbitratorRegistration.pubKey=Clé publique
 
-account.arbitratorRegistration.register=Register
-account.arbitratorRegistration.registration={0} registration
+account.arbitratorRegistration.register=S'inscrire
+account.arbitratorRegistration.registration={0} Enregistrement
 account.arbitratorRegistration.revoke=Révoquer
-account.arbitratorRegistration.info.msg=Please note that you need to stay available for 15 days after revoking as there might be trades which are using you as {0}. The max. allowed trade period is 8 days and the dispute process might take up to 7 days.
+account.arbitratorRegistration.info.msg=Veuillez noter que vous devez rester disponible pendant 15 jours après la révocation, car il se peut que des transactions qui vous implique comme {0}. Le délai d'échange maximal autorisé est de 8 jours et la procédure de contestation peut prendre jusqu'à 7 jours.
 account.arbitratorRegistration.warn.min1Language=Vous devez définir au moins 1 langue.\nNous avons ajouté la langue par défaut pour vous.
-account.arbitratorRegistration.removedSuccess=You have successfully removed your registration from the Bisq network.
-account.arbitratorRegistration.removedFailed=Could not remove registration.{0}
-account.arbitratorRegistration.registerSuccess=You have successfully registered to the Bisq network.
-account.arbitratorRegistration.registerFailed=Could not complete registration.{0}
+account.arbitratorRegistration.removedSuccess=Vous avez supprimé votre inscription au réseau Bisq avec succès.
+account.arbitratorRegistration.removedFailed=Impossible de supprimer l'enregistrement.{0}
+account.arbitratorRegistration.registerSuccess=Vous vous êtes inscrit au réseau Bisq avec succès.
+account.arbitratorRegistration.registerFailed=Impossible de terminer l'enregistrement.{0}
 
 account.altcoin.yourAltcoinAccounts=Vos comptes altcoin
-account.altcoin.popup.wallet.msg=Please be sure that you follow the requirements for the usage of {0} wallets as described on the {1} web page.\nUsing wallets from centralized exchanges where (a) you don''t control your keys or (b) which don''t use compatible wallet software is risky: it can lead to loss of the traded funds!\nThe mediator or arbitrator is not a {2} specialist and cannot help in such cases.
+account.altcoin.popup.wallet.msg=Veuillez vous assurer que vous respectez les exigences relatives à l''utilisation des {0} portefeuilles, selon les conditions présentées sur la page {1} du site.\nL''utilisation des portefeuilles provenant de plateformes de trading centralisées où (a) vous ne contrôlez pas vos clés ou (b) qui ne disposent pas d''un portefeuille compatible est risquée : cela peut entraîner la perte des fonds échangés!\nLe médiateur et l''arbitre ne sont  pas des spécialistes {2} et ne pourront pas intervenir dans ce cas.
 account.altcoin.popup.wallet.confirm=Je comprends et confirme que je sais quel portefeuille je dois utiliser.
 account.altcoin.popup.upx.msg=Trading UPX on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending UPX, you need to use either the official uPlexa GUI wallet or uPlexa CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nuplexa-wallet-cli (use the command get_tx_key)\nuplexa-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The UPX sender is responsible for providing verification of the UPX transfer to the arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit uPlexa discord channel (https://discord.gg/vhdNSrV) or the uPlexa Telegram Chat (https://t.me/uplexaOfficial) to find more information.
-account.altcoin.popup.arq.msg=Trading ARQ on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending ARQ, you need to use either the official ArQmA GUI wallet or ArQmA CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\narqma-wallet-cli (use the command get_tx_key)\narqma-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the mediator or arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The ARQ sender is responsible for providing verification of the ARQ transfer to the mediator or arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit ArQmA discord channel (https://discord.gg/s9BQpJT) or the ArQmA forum (https://labs.arqma.com) to find more information.
-account.altcoin.popup.xmr.msg=Trading XMR on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending XMR, you need to use either the official Monero GUI wallet or Monero CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nmonero-wallet-cli (use the command get_tx_key)\nmonero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nIn addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\nmonero-wallet-cli : using command (check_tx_key).\nmonero-wallet-gui : on the Advanced > Prove/Check page.\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the mediator or arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The XMR sender is responsible for providing verification of the XMR transfer to the mediator or arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) or the Monero forum (https://forum.getmonero.org) to find more information.
+account.altcoin.popup.arq.msg=Le trading d"ARQ sur Bisq exige que vous compreniez et remplissiez les exigences suivantes:\n\nPour envoyer des ARQ, vous devez utiliser soit le portefeuille officiel ArQmA GUI soit le portefeuille ArQmA CLI avec le drapeau store-tx-info activé (par défaut dans les nouvelles versions). Veuillez vous assurer que vous pouvez accéder à la tx key car cela pourrait être nécessaire en cas de litige.\narqma-wallet-cli (utiliser la commande get_tx_key)\narqma-wallet-gui (allez dans l'onglet historique et cliquez sur le bouton (P) pour accéder à la preuve de paiement)\n\nAvec le mode normal de l'explorateur de bloc le transfert n'est pas vérifiable.\n\nVous devez fournir au médiateur ou à l'arbitre les données suivantes en cas de litige:\n- Le tx de la clé privée\n- Le hash de la transaction\n- L'adresse publique du destinataire\n\nSi vous manquez de communiquer les données ci-dessus ou si vous utilisez un portefeuille incompatible, vous perdez le litige. L'expéditeur des ARQ est responsable de la transmission au médiateur ou à l'arbitre de la vérification du transfert ces informations relatives au litige.\n\nIl n'est pas nécessaire de fournir l"ID de paiement, seulement l'adresse publique normale.\nSi vous n'êtes pas sûr au sujet de cette opération, visitez le canal discord ArQmA (https://discord.gg/s9BQpJT) ou le forum ArQmA (https://labs.arqma.com) pour obtenir plus d'informations.
+account.altcoin.popup.xmr.msg=Trading XMR on Bisq requires that you understand and fulfill the following requirements:\n\nProve payments: since Monero is a private coin, some transaction details aren't publicly available in the blockchain, and, in case of a dispute, the mediator or arbitrator needs them to check if the transaction was really made. In Bisq, the sender of the XMR transaction is the one responsible for providing this information to the mediator or arbitrator in case of a dispute. In order to do that, you must send XMR using a wallet that provides the information required to prove the payment was made, which includes:\n\n- the transaction key (Tx Key, Tx Secret Key or Tx Private Key)\n- the transaction ID (Tx ID or Tx Hash)\n- the destination address (recipient's address)\n\nThis information can be found in the official Monero GUI & CLI wallets, MyMonero, and Exodus (desktop) as well as in Cake Wallet, MyMonero, and Monerujo (mobile), in the following locations:\n\n- Monero GUI: go to Transactions tab\n- Monero CLI: use the command get_tx_key TXID. The flag store-tx-info must be enabled (enabled by default in new versions)\n- Other wallets: go to Transactions history and search for Transaction key (Tx key or Secret key) and the destination address in a sent transaction. Save recipient address option must be enabled in Cake Wallet settings.\n\nIf you are using a wallet different from the mentioned above, please be sure you can access those three pieces of information.Since the transaction key and the destination address are stored in the Monero wallet software, and they cannot be recovered in the Monero blockchain, you should never delete or restore your Monero wallet before a Bisq trade is completed. Failure to provide the above data will result in losing the dispute case.\n\nCheck payments: with those three pieces of information, the verification that a quantity of Monero was sent to a specific address can be accomplished the following way:\n\n- Monero GUI: change wallet to Advanced mode and go to Advanced > Prove/check > Check Transaction\n- Monero CLI: use the command check_tx_key TXID TXKEY ADDRESS\n- XMR checktx tool (https://xmr.llcoins.net/checktx.html)\n- Explore Monero website (https://www.exploremonero.com/receipt)\n\nIf you are still not sure about this process, visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) to find more information or ask a question on the Monero support subreddit (https://www.reddit.com/r/monerosupport/).
 # suppress inspection "TrailingSpacesInProperty"
 account.altcoin.popup.msr.msg=Trading MSR on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending MSR, you need to use either the official Masari GUI wallet, Masari CLI wallet with the store-tx-info flag enabled (enabled by default) or the Masari web wallet (https://wallet.getmasari.org). Please be sure you can access the tx key as that would be required in case of a dispute.\nmasari-wallet-cli (use the command get_tx_key)\nmasari-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nMasari Web Wallet (goto Account -> transaction history and view details on your sent transaction)\n\nVerification can be accomplished in-wallet.\nmasari-wallet-cli : using command (check_tx_key).\nmasari-wallet-gui : on the Advanced > Prove/Check page.\nVerification can be accomplished in the block explorer \nOpen block explorer (https://explorer.getmasari.org), use the search bar to find your transaction hash.\nOnce transaction is found, scroll to bottom to the 'Prove Sending' area and fill in details as needed.\nYou need to provide the mediator or arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The MSR sender is responsible for providing verification of the MSR transfer to the mediator or arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process, ask for help on the Official Masari Discord (https://discord.gg/sMCwMqs).
-account.altcoin.popup.blur.msg=Trading BLUR on Bisq requires that you understand and fulfill the following requirements:\n\nTo send BLUR you must use the Blur Network CLI or GUI Wallet. \n\nIf you are using the CLI wallet, a transaction hash (tx ID) will be displayed after a transfer is sent. You must save this information. Immediately after sending the transfer, you must use the command 'get_tx_key' to retrieve the transaction private key. If you fail to perform this step, you may not be able to retrieve the key later. \n\nIf you are using the Blur Network GUI Wallet, the transaction private key and transaction ID can be found conveniently in the "History" tab.  Immediately after sending, locate the transaction of interest. Click the "?" symbol in the lower-right corner of the box containing the transaction. You must save this information. \n\nIn the event that arbitration is necessary, you must present the following to an mediator or arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address.  The mediator or arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nFailure to provide the required information to the mediator or arbitrator will result in losing the dispute case. In all cases of dispute, the BLUR sender bears 100% of the burden of responsibility in verifying transactions to an mediator or arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW).
+account.altcoin.popup.blur.msg=Le trading de BLUR on Bisq nécessite que vous compreniez et remplissiez les conditions suivantes:\n\nPour envoyer des BLUR vous devez utiliser le réseau Blur CLI ou un portefeuille GUI. \n\nSi vous utilisez le portefeuille CLI, un hash de transaction (tx ID) sera affiché après que le transfert sera effectué. Vous devez sauvegarder cette information. Immédiatement après l'envoi du transfert, vous devez utiliser la command 'get_tx_key' pour récupérer la clé privée de la transaction. Si vous ne procédez pas à cette étape, il se peut que vous ne puissiez pas récupérer la clé ultérieurement. \n\nSi vous utilisez le réseau Blur GUI Wallet, la clé privée de transaction et l"ID de transaction se trouvent facilement dans l'onglet "Historique". Immédiatement après l'envoi, localisez la transaction qui vous intéresse. Cliquez sur le symbole "?" dans le coin inférieur droit de la boîte contenant la transaction. Vous devez sauvegarder ces informations. \n\nSi un arbitrage est nécessaire, vous devrez présenter les informations suivantes au médiateur ou l'arbitre : 1) l'ID de la transaction, 2) la clé privée de la transaction et 3) l'adresse du destinataire. Le médiateur ou l'arbitre vérifiera ensuite le transfert BLUR à l'aide du vérificateur de transactions Blur (https://blur.cash/#tx-viewer).\n\nSi vous omettez de fournir les renseignements requis par le médiateur ou par l"arbitre, votre litige sera rejeté. Dans tous les cas de litige, l'expéditeur des BLUR assume 100 % de la responsabilité de la vérification des transactions par le médiateur ou arbitre. \n\nSi vous ne comprenez pas ces conditions, ne tradez pas Bisq. Tout d'abord, demandez de l'aide sur le Discord Blur Network (https://discord.gg/dMWaqVW).
 account.altcoin.popup.solo.msg=Trading Solo on Bisq requires that you understand and fulfill the following requirements:\n\nTo send Solo you must use the Solo Network CLI Wallet. \n\nIf you are using the CLI wallet, a transaction hash (tx ID) will be displayed after a transfer is sent. You must save this information. Immediately after sending the transfer, you must use the command 'get_tx_key' to retrieve the transaction private key. If you fail to perform this step, you may not be able to retrieve the key later. \n\nIn the event that arbitration is necessary, you must present the following to an mediator or arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address.  The mediator or arbitrator will then verify the Solo transfer using the Solo Block Explorer by searching for the transaction and then using the "Prove sending" function (https://explorer.minesolo.com/).\n\nfailure to provide the required information to the mediator or arbitrator will result in losing the dispute case. In all cases of dispute, the Solo sender bears 100% of the burden of responsibility in verifying transactions to an mediator or arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Solo Network Discord (https://discord.minesolo.com/).
-account.altcoin.popup.cash2.msg=Trading CASH2 on Bisq requires that you understand and fulfill the following requirements:\n\nTo send CASH2 you must use the Cash2 Wallet version 3 or higher. \n\nAfter a transaction is sent, the transaction ID will be displayed. You must save this information. Immediately after sending the transaction, you must use the command 'getTxKey' in simplewallet to retrieve the transaction secret key. \n\nIn the event that arbitration is necessary, you must present the following to an mediator or arbitrator: 1) the transaction ID, 2) the transaction secret key, and 3) the recipient's Cash2 address.  The mediator or arbitrator will then verify the CASH2 transfer using the Cash2 Block Explorer (https://blocks.cash2.org).\n\nFailure to provide the required information to the mediator or arbitrator will result in losing the dispute case. In all cases of dispute, the CASH2 sender bears 100% of the burden of responsibility in verifying transactions to an mediator or arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Cash2 Discord (https://discord.gg/FGfXAYN).
+account.altcoin.popup.cash2.msg=Le trading de CASH2 sur Bisq nécessite que vous compreniez et remplissiez les conditions suivantes :\n\nPour envoyer des CASH2, vous devez utiliser une version de porefeuille Cash2 version 3 ou supérieure.\n\nAprès l'envoi d'une transaction, l'ID de transaction sera affiché. Vous devrez sauvegarder ces informations. Immédiatement après l'envoi de la transaction, vous devez utiliser la commande 'getTxKey' en simplewallet pour récupérer la clé secrète de la transaction.\n\nDans le cas où un arbitrage est nécessaire, vous devez présenter les éléments suivants au médiateur et à l"arbitre : 1) l'ID de transaction, 2) la clé secrète de transaction et 3) l"adresse Cash2 du destinataire. Le médiateur ou l"arbitre vérifiera ensuite le transfert de CASH2 à l'aide du Cash2 Block Explorer (https://blocks.cash2.org).\n\nSi vous omettez de fournir les renseignements requis par le médiateur ou l"'arbitre, votre différend sera rejeté. Dans tous les cas de litige, l"expéditeur de CASH2 supporte 100% de la responsabilité de la vérification des transactions par un arbitre.\n\nSi vous ne comprenez pas ces exigences, ne tradez pas sur Bisq. Tout d'abord, demandez de l"aide sur le Discord de Cash2 (https://discord.gg/FGfXAYN).
 account.altcoin.popup.qwertycoin.msg=Trading Qwertycoin on Bisq requires that you understand and fulfill the following requirements:\n\nTo send QWC you must use the official QWC Wallet version 5.1.3 or higher. \n\nAfter a transaction is sent, the transaction ID will be displayed. You must save this information. Immediately after sending the transaction, you must use the command 'get_Tx_Key' in simplewallet to retrieve the transaction secret key. \n\nIn the event that arbitration is necessary, you must present the following to an mediator or arbitrator: 1) the transaction ID, 2) the transaction secret key, and 3) the recipient's QWC address.  The mediator or arbitrator will then verify the QWC transfer using the QWC Block Explorer (https://explorer.qwertycoin.org).\n\nFailure to provide the required information to the mediator or arbitrator will result in losing the dispute case. In all cases of dispute, the QWC sender bears 100% of the burden of responsibility in verifying transactions to an mediator or arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the QWC Discord (https://discord.gg/rUkfnpC).
 account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides, a transaction is not verifiable on the public blockchain. If required, you can prove your payment through the use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the mediator or arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at (http://drgl.info/#check_txn).\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The Dragonglass sender is responsible for providing verification of the DRGL transfer to the mediator or arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help.
-account.altcoin.popup.ZEC.msg=When using Zcash you can only use the transparent addresses (starting with t), not the z-addresses (private), because the mediator or arbitrator would not be able to verify the transaction with z-addresses.
-account.altcoin.popup.XZC.msg=When using Zcoin you can only use the transparent (traceable) addresses, not the untraceable addresses, because the mediator or arbitrator would not be able to verify the transaction with untraceable addresses at a block explorer.
+account.altcoin.popup.ZEC.msg=Lors de l'utilisation de Zcash, vous ne pouvez utiliser que les adresses transparentes (commençant par t), et non les z-adresses (privées), car le médiateur ou l'arbitre ne seraient pas en mesure de vérifier la transaction avec les z-adresses.
+account.altcoin.popup.XZC.msg=Lors de l'utilisation de Zcoin, vous ne pouvez utiliser que les adresses transparentes (traçables), et non les adresses intraçables, car le médiateur ou l'arbitre ne seraient pas en mesure de vérifier la transaction avec des adresses intraçables dans un explorateur de blocs.
 account.altcoin.popup.grin.msg=GRIN nécessite un échange interactif entre l'émetteur et le récepteur pour créer la transaction. Assurez-vous de suivre les instructions de la page Web du projet GRIN pour envoyer et recevoir des GRIN de façon fiable (le récepteur doit être en ligne au moins pendant un certain temps).\n\nBisq ne supporte que le portefeuille Grinbox (Wallet713) format URL.\n\nL'expéditeur des GRIN doit fournir la preuve qu'il a envoyé les GRIN avec succès. Si le portefeuille ne peut pas fournir cette preuve, un litige potentiel sera résolu en faveur du destinataire des GRIN. Veuillez vous assurer que vous utilisez le dernier logiciel Grinbox qui supporte la preuve de transaction et que vous comprenez le processus de transfert et de réception des GRIN ainsi que la façon de créer la preuve.\n\nVisitez https://github.com/vault713/wallet713/blob/master/docs/usage.md#transaction-proofs-grinbox-only pour plus d'informations sur l'outil de preuve de Grinbox.
 account.altcoin.popup.beam.msg=BEAM nécessite un processus interactif entre l'émetteur et le récepteur pour créer la transaction.\n\nAssurez-vous de suivre les instructions de la page Web du projet BEAM pour envoyer et recevoir les BEAM de façon fiable (le récepteur doit être en ligne pendant au moins un certain temps).\n\nL'expéditeur de BEAM est tenu de fournir la preuve qu'il a envoyé BEAM avec succès. Assurez-vous d'utiliser un portefeuille qui peut produire une telle preuve. Si le portefeuille ne peut fournir la preuve, un litige potentiel sera résolu en faveur du récepteur des BEAM.
 account.altcoin.popup.pars.msg=Trading ParsiCoin on Bisq requires that you understand and fulfill the following requirements:\n\nTo send PARS you must use the official ParsiCoin Wallet version 3.0.0 or higher. \n\nYou can Check your Transaction Hash and Transaction Key on Transactions Section on your GUI Wallet (ParsiPay) You need to right Click on the Transaction and then click on show details. \n\nIn the event that arbitration is necessary, you must present the following to an mediator or arbitrator: 1) the Transaction Hash, 2) the Transaction Key, and 3) the recipient's PARS address.  The mediator or arbitrator will then verify the PARS transfer using the ParsiCoin Block Explorer (http://explorer.parsicoin.net/#check_payment).\n\nFailure to provide the required information to the mediator or arbitrator will result in losing the dispute case. In all cases of dispute, the ParsiCoin sender bears 100% of the burden of responsibility in verifying transactions to an mediator or arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the ParsiCoin Discord (https://discord.gg/c7qmFNh).
@@ -1169,6 +1168,7 @@ dao.lockedForVoteBalance=Utilisé pour le vote
 dao.lockedInBonds=Verrouillé en bonds
 dao.availableNonBsqBalance=Solde disponible non-BSQ (BTC)
 dao.totalBsqBalance=Total du solde BSQ
+dao.reputationBalance=Score de merit (non utilisable)
 
 dao.tx.published.success=Votre transaction a été publiée avec succès.
 dao.proposal.menuItem.make=Faire une proposition
@@ -1296,7 +1296,7 @@ dao.param.BONDED_ROLE_FACTOR=Bonded role unit factor en BSQ
 dao.param.ISSUANCE_LIMIT=Limite d'émission par cycle en BSQ
 
 dao.param.currentValue=Valeur actuelle: {0}
-dao.param.currentAndPastValue=Current value: {0} (Value when proposal was made: {1})
+dao.param.currentAndPastValue=Valeur actuelle: {0} (Valeur au moment de l'offre: {1})
 dao.param.blocks={0} blocs
 
 dao.results.cycle.duration.label=Durée de {0}
@@ -1304,7 +1304,7 @@ dao.results.cycle.duration.value={0} bloc(s)
 dao.results.cycle.value.postFix.isDefaultValue=(valeur par défaut)
 dao.results.cycle.value.postFix.hasChanged=(a été modifié par le vote)
 
-dao.results.invalidVotes=We had invalid votes in that voting cycle. That can happen if a vote was not distributed well in the Bisq network.\n{0}
+dao.results.invalidVotes=Il est fait état de votes invalides au cours de ce cycle de vote. Cela peut arriver si un vote n'a pas été bien distribué sur le réseau Bisq.\n{0}
 
 # suppress inspection "UnusedProperty"
 dao.phase.PHASE_UNDEFINED=Indéfini
@@ -1582,7 +1582,7 @@ dao.proposal.create.publish=Publier la demande
 dao.proposal.create.publishing=La publication de la demande est en cours...
 dao.proposal=Demande
 dao.proposal.display.type=Type de demande
-dao.proposal.display.name=Exact GitHub username
+dao.proposal.display.name=Nom d'utilisateur GitHub exact
 dao.proposal.display.link=Lien vers les informations détaillées
 dao.proposal.display.link.prompt=Lien vers la proposition
 dao.proposal.display.requestedBsq=Montant démandé en BSQ
@@ -1606,8 +1606,8 @@ dao.proposal.table.icon.tooltip.changeVote=Vote actuel: ''{0}'''. Modifier le vo
 dao.proposal.display.myVote.accepted=Accepté
 dao.proposal.display.myVote.rejected=Rejeté
 dao.proposal.display.myVote.ignored=Ignoré
-dao.proposal.display.myVote.unCounted=Vote was not included in result
-dao.proposal.myVote.summary=Voted: {0}; Vote weight: {1} (earned: {2} + stake: {3}) {4}
+dao.proposal.display.myVote.unCounted=Le vote n'a pas été inclus dans le résultat
+dao.proposal.myVote.summary=Voté: {0}; Poids du vote: {1} (gagné: {2} + stake: {3}) {4}
 dao.proposal.myVote.invalid=Le vote n'est pas valide
 
 dao.proposal.voteResult.success=Accepté
@@ -1741,7 +1741,7 @@ dao.monitor.daoState=Etat de la DAO
 dao.monitor.proposals=État des propositions
 dao.monitor.blindVotes=État des votes cachés
 
-dao.monitor.table.peers=pairs
+dao.monitor.table.peers=Pairs
 dao.monitor.table.conflicts=Conflits
 dao.monitor.state=Statut
 dao.monitor.requestAlHashes=Demander tous les hashes
@@ -1760,7 +1760,7 @@ dao.monitor.daoState.utxoConflicts=conflits UTXO
 dao.monitor.daoState.utxoConflicts.blockHeight=Hauteur de bloc: {0}
 dao.monitor.daoState.utxoConflicts.sumUtxo=Somme de tous les UTXO: {0} BSQ
 dao.monitor.daoState.utxoConflicts.sumBsq=Somme de tous les BSQ: {0} BSQ
-dao.monitor.daoState.checkpoint.popup=DAO state is not in sync with the network. After restart the DAO state will resync.
+dao.monitor.daoState.checkpoint.popup=La DAO n'est pas en état de synchronisation avec le réseau. Après redémarrage, la DAO sera resynchronisé.
 
 dao.monitor.proposal.headline=État des propositions
 dao.monitor.proposal.table.headline=Etat du hachage de la chaîne de proposition
@@ -1786,8 +1786,8 @@ dao.factsAndFigures.menuItem.transactions=Transactions BSQ
 
 dao.factsAndFigures.dashboard.marketPrice=Données du marché
 dao.factsAndFigures.dashboard.price=Prix du dernier Trade BSQ/BTC (en Bisq)
-dao.factsAndFigures.dashboard.avgPrice90=90 days average BSQ/BTC trade price
-dao.factsAndFigures.dashboard.avgPrice30=30 days average BSQ/BTC trade price
+dao.factsAndFigures.dashboard.avgPrice90=Moyenne sur 90 jours du prix d'échange BSQ/BTC
+dao.factsAndFigures.dashboard.avgPrice30=Moyenne sur 30 jours du prix d'échange BSQ/BTC
 dao.factsAndFigures.dashboard.marketCap=Capitalisation boursière (basé sur la valeur d'échange)
 dao.factsAndFigures.dashboard.availableAmount=BSQ disponible au total
 
@@ -1872,12 +1872,12 @@ disputeSummaryWindow.summaryNotes=Notes de synthèse
 disputeSummaryWindow.addSummaryNotes=Ajouter des notes de synthèse
 disputeSummaryWindow.close.button=Fermer le ticket
 disputeSummaryWindow.close.msg=Ticket closed on {0}\n\nSummary:\nPayout amount for BTC buyer: {1}\nPayout amount for BTC seller: {2}\n\nSummary notes:\n{3}
-disputeSummaryWindow.close.nextStepsForMediation=\n\nNext steps:\nOpen trade and accept or reject suggestion from mediator
+disputeSummaryWindow.close.nextStepsForMediation=\n\nProchaines étapes:\nOuvrir la transaction et accepter ou rejeter la suggestion du médiateur
 disputeSummaryWindow.close.nextStepsForRefundAgentArbitration=\n\nNext steps:\nNo further action is required from you. If the arbitrator decided in your favor, you'll see a "Refund from arbitration" transaction in Funds/Transactions
 disputeSummaryWindow.close.closePeer=Vous devez également clore le ticket de trading des pairs!
-disputeSummaryWindow.close.txDetails.headline=Publish refund transaction
-disputeSummaryWindow.close.txDetails.buyer=Buyer receives {0} on address: {1}\n
-disputeSummaryWindow.close.txDetails.seller=Seller receives {0} on address: {1}\n
+disputeSummaryWindow.close.txDetails.headline=Publier la transaction de remboursement
+disputeSummaryWindow.close.txDetails.buyer=L'acheteur reçoit {0} à l'adresse: {1}\n
+disputeSummaryWindow.close.txDetails.seller=Le vendeur reçoit {0} à l'adresse: {1}\n
 disputeSummaryWindow.close.txDetails=Spending: {0}\n{1}{2}Transaction fee: {3} ({4} satoshis/byte)\nTransaction size: {5} Kb\n\nAre you sure you want to publish this transaction?
 
 emptyWalletWindow.headline={0} Outil de secours du portefeuille
@@ -1891,7 +1891,7 @@ emptyWalletWindow.openOffers.warn=Vous avez des ordres en cours qui seront suppr
 emptyWalletWindow.openOffers.yes=Oui, j'en suis certain
 emptyWalletWindow.sent.success=Le solde de votre portefeuille a été transféré avec succès.
 
-enterPrivKeyWindow.headline=Enter private key for registration
+enterPrivKeyWindow.headline=Entrer la clé privée pour l'enregistrement
 
 filterWindow.headline=Modifier la liste de filtres
 filterWindow.offers=Ordres filtrés (séparer avec une virgule)
@@ -1900,8 +1900,8 @@ filterWindow.accounts=Données filtrées du compte de trading:\nFormat: séparer
 filterWindow.bannedCurrencies=Codes des devises filtrées (séparer avec une virgule.)
 filterWindow.bannedPaymentMethods=IDs des modes de paiements filtrés (séparer avec une virgule.)
 filterWindow.arbitrators=Arbitres filtrés (adresses onion séparées par une virgule)
-filterWindow.mediators=Filtered mediators (comma sep. onion addresses)
-filterWindow.refundAgents=Filtered refund agents (comma sep. onion addresses)
+filterWindow.mediators=Médiateurs filtrés (adresses onion sep. par une virgule)
+filterWindow.refundAgents=Agents de remboursement filtrés (adresses onion sep. par virgule)
 filterWindow.seedNode=Nœuds de seed filtrés (adresses onion séparées par une virgule)
 filterWindow.priceRelayNode=Nœuds relais avec prix filtrés (adresses onion séparées par une virgule)
 filterWindow.btcNode=Nœuds Bitcoin filtrés (adresses séparées par une virgule + port)
@@ -1961,15 +1961,15 @@ showWalletDataWindow.includePrivKeys=Inclure les clés privées
 tacWindow.headline=Conditions d'utilisation
 tacWindow.agree=Je suis d'accord
 tacWindow.disagree=Je ne suis pas d'accord et je quitte
-tacWindow.arbitrationSystem=Système d'arbitrage
+tacWindow.arbitrationSystem=Règlement du litige
 
 tradeDetailsWindow.headline=Échange
 tradeDetailsWindow.disputedPayoutTxId=ID de la transaction de versement contestée :
 tradeDetailsWindow.tradeDate=Date de l'échange
 tradeDetailsWindow.txFee=Frais de minage
-tradeDetailsWindow.tradingPeersOnion=Adresse onion du pairs de trading
+tradeDetailsWindow.tradingPeersOnion=Adresse onion du pair de trading
 tradeDetailsWindow.tradeState=État du trade
-tradeDetailsWindow.agentAddresses=Arbitrator/Mediator
+tradeDetailsWindow.agentAddresses=Arbitre/Médiateur
 
 walletPasswordWindow.headline=Entrer le mot de passe pour déverouiller
 
@@ -2038,7 +2038,7 @@ popup.warning.tradePeriod.ended=Your trade with ID {0} has reached the max. allo
 popup.warning.noTradingAccountSetup.headline=Vous n'avez pas configuré de compte de trading
 popup.warning.noTradingAccountSetup.msg=Vous devez configurer une devise nationale ou un compte altcoin avant de pouvoir créer un ordre.\nVoulez-vous configurer un compte ?
 popup.warning.noArbitratorsAvailable=Les arbitres ne sont pas disponibles.
-popup.warning.noMediatorsAvailable=There are no mediators available.
+popup.warning.noMediatorsAvailable=Il n'y a pas de médiateurs disponibles.
 popup.warning.notFullyConnected=Vous devez attendre d'être complètement connecté au réseau.\nCela peut prendre jusqu'à 2 minutes au démarrage.
 popup.warning.notSufficientConnectionsToBtcNetwork=Vous devez attendre d''avoir au minimum {0} connexions au réseau Bitcoin.
 popup.warning.downloadNotComplete=Vous devez attendre que le téléchargement des blocs Bitcoin manquants soit terminé.
@@ -2066,14 +2066,14 @@ popup.warning.burnBTC=Cette transaction n''est pas possible, car les frais de mi
 
 popup.warning.openOffer.makerFeeTxRejected=The maker fee transaction for offer with ID {0} was rejected by the Bitcoin network.\nTransaction ID={1}.\nThe offer has been removed to avoid further problems.\nPlease go to \"Settings/Network info\" and do a SPV resync.\nFor further help please contact the Bisq support channel at the Bisq Keybase team.
 
-popup.warning.trade.txRejected.tradeFee=trade fee
-popup.warning.trade.txRejected.deposit=deposit
+popup.warning.trade.txRejected.tradeFee=frais de transaction
+popup.warning.trade.txRejected.deposit=dépôt
 popup.warning.trade.txRejected=The {0} transaction for trade with ID {1} was rejected by the Bitcoin network.\nTransaction ID={2}}\nThe trade has been moved to failed trades.\nPlease go to \"Settings/Network info\" and do a SPV resync.\nFor further help please contact the Bisq support channel at the Bisq Keybase team.
 
 popup.warning.openOfferWithInvalidMakerFeeTx=The maker fee transaction for offer with ID {0} is invalid.\nTransaction ID={1}.\nPlease go to \"Settings/Network info\" and do a SPV resync.\nFor further help please contact the Bisq support channel at the Bisq Keybase team.
 
 popup.warning.trade.depositTxNull=The trade with ID {0} has no deposit transaction set.\nPlease restart the application and if the problem remains move the trade to failed trades and report the problem to the Bisq support channel at the Bisq Keybase team.
-popup.warning.trade.depositTxNull.moveToFailedTrades=Move to failed trades
+popup.warning.trade.depositTxNull.moveToFailedTrades=Déplacer vers les échanges en échec
 
 popup.info.securityDepositInfo=Afin de s'assurer que les deux traders suivent le protocole de trading, les deux traders doivent payer un dépôt de garantie.\n\nCe dépôt est conservé dans votre portefeuille d'échange jusqu'à ce que votre transaction soit terminée avec succès, et ensuite il vous sera restitué.\n\nRemarque : si vous créez un nouvel ordre, Bisq doit être en cours d'exécution pour qu'un autre trader puisse l'accepter. Pour garder vos ordres en ligne, laissez Bisq en marche et assurez-vous que cet ordinateur reste en ligne aussi (pour cela, assurez-vous qu'il ne passe pas en mode veille....le mode veille du moniteur ne pose aucun problème).
 
@@ -2096,32 +2096,32 @@ popup.attention.forTradeWithId=Attention requise la transaction avec l''ID {0}
 popup.info.multiplePaymentAccounts.headline=Comptes de paiement multiples disponibles
 popup.info.multiplePaymentAccounts.msg=Vous disposez de plusieurs comptes de paiement disponibles pour cet ordre. Assurez-vous de choisir le bon.
 
-popup.news.launch.headline=Two Major Updates
-popup.news.launch.accountSigning.headline=ACCOUNT SIGNING
-popup.news.launch.accountSigning.description=Lift 0.01 BTC fiat trading limits by buying BTC from a signed peer.
-popup.news.launch.ntp.headline=NEW TRADE PROTOCOL
+popup.news.launch.headline=Deux mises à jour majeures
+popup.news.launch.accountSigning.headline=SIGNATURE DU COMPTE
+popup.news.launch.accountSigning.description=Lever les limites de trading de 0,01 BTC par fiat en achetant des BTC auprès d'un pair signé.
+popup.news.launch.ntp.headline=NOUVEAU PROTOCOLE D’ÉCHANGE
 popup.news.launch.ntp.description=New 2-level dispute resolution system makes Bisq more secure, scalable, and censorship-resistant.
 
-popup.accountSigning.selectAccounts.headline=Select payment accounts
-popup.accountSigning.selectAccounts.description=Based on the payment method and point of time all payment accounts that are connected to a dispute where a payout to the buyer occurred will be selected for you to sign.
-popup.accountSigning.selectAccounts.signAll=Sign all payment methods
-popup.accountSigning.selectAccounts.datePicker=Select point of time until which accounts will be signed
+popup.accountSigning.selectAccounts.headline=Sélectionner les comptes de paiement
+popup.accountSigning.selectAccounts.description=En fonction du mode de paiement et du moment du paiement, tous les comptes de paiement qui sont liés à un litige où un paiement à l'acheteur a eu lieu seront sélectionnés afin que vous les signiez.
+popup.accountSigning.selectAccounts.signAll=Signer tous les modes de paiement
+popup.accountSigning.selectAccounts.datePicker=Sélectionnez le moment jusqu"auquel les comptes seront signés
 
-popup.accountSigning.confirmSelectedAccounts.headline=Confirm selected payment accounts
-popup.accountSigning.confirmSelectedAccounts.description=Based on your input, {0} payment accounts will be selected.
-popup.accountSigning.confirmSelectedAccounts.button=Confirm payment accounts
-popup.accountSigning.signAccounts.headline=Confirm signing of payment accounts
-popup.accountSigning.signAccounts.description=Based on your selection, {0} payment accounts will be signed.
-popup.accountSigning.signAccounts.button=Sign payment accounts
-popup.accountSigning.signAccounts.ECKey=Enter private arbitrator key
-popup.accountSigning.signAccounts.ECKey.error=Bad arbitrator ECKey
+popup.accountSigning.confirmSelectedAccounts.headline=Confirmer les comptes de paiement sélectionnés
+popup.accountSigning.confirmSelectedAccounts.description=Suite à votre saisie, {0} comptes de paiement seront sélectionnés.
+popup.accountSigning.confirmSelectedAccounts.button=Confirmer les comptes de paiement
+popup.accountSigning.signAccounts.headline=Confirmer la signature des comptes de paiement
+popup.accountSigning.signAccounts.description=Suite à votre sélection, {0} comptes de paiement seront signés.
+popup.accountSigning.signAccounts.button=Signer les comptes de paiement
+popup.accountSigning.signAccounts.ECKey=Entrez la clé privée d'arbitrage
+popup.accountSigning.signAccounts.ECKey.error=Mauvaise ECKey de l'arbitre
 
-popup.accountSigning.success.headline=Congratulations
-popup.accountSigning.success.description=All {0} payment accounts were successfully signed!
-popup.accountSigning.generalInformation=You'll find the signing state of all your accounts in the account section.\n\nFor further information, please visit https://docs.bisq.network/payment-methods#account-signing.
-popup.accountSigning.signedByArbitrator=One of your payment accounts has been verified and signed by an arbitrator. Trading with this account will automatically sign your trading peer''s account after a successful trade.\n\n{0}
+popup.accountSigning.success.headline=Félicitations
+popup.accountSigning.success.description=Tous les {0} comptes de paiement ont été signés avec succès !
+popup.accountSigning.generalInformation=Vous trouverez l'état de signature de tous vos comptes dans la section compte.\nPour obtenir plus d'informations, veuillez consulter le site  https://docs.bisq.network/payment-methods#account-signing.
+popup.accountSigning.signedByArbitrator=Un de vos comptes de paiement a été vérifié et signé par un arbitre. Trader avec ce compte signera automatiquement le compte de votre pair de trading après un échange réussi.\n\n{0}
 popup.accountSigning.signedByPeer=One of your payment accounts has been verified and signed by a trading peer. Your initial trading limit will be lifted and you''ll be able to sign other accounts in {0} days from now.\n\n{1}
-popup.accountSigning.peerLimitLifted=The initial limit for one of your accounts has been lifted.\n\n{0}
+popup.accountSigning.peerLimitLifted=La limite initiale pour l'un de vos comptes a été levée.\n\n{0}
 popup.accountSigning.peerSigner=One of your accounts is mature enough to sign other payment accounts and the initial limit for one of your accounts has been lifted.\n\n{0}
 
 ####################################################################
@@ -2152,7 +2152,7 @@ systemTray.show=Montrer la fenêtre de l'application
 systemTray.hide=Cacher la fenêtre de l'application
 systemTray.info=Informations au sujet de Bisq
 systemTray.exit=Sortir
-systemTray.tooltip=Bisq : Le réseau d'échange décentralisé
+systemTray.tooltip=Bisq  Une plateforme d"échange décentralisée sur le réseau bitcoin
 
 
 ####################################################################
@@ -2188,14 +2188,14 @@ list.currency.editList=Modifier la liste des devises
 
 table.placeholder.noItems=Il y a {0} disponible pour le moment
 table.placeholder.noData=Il n'y a actuellement aucune donnée disponible
-table.placeholder.processingData=Processing data...
+table.placeholder.processingData=Traitement des données en cours...
 
 
 peerInfoIcon.tooltip.tradePeer=Du pair de trading
 peerInfoIcon.tooltip.maker=du maker
 peerInfoIcon.tooltip.trade.traded={0} adresse onion: {1}\nVous avez déjà échangé a {2} reprise(s) avec ce pair\n{3}
 peerInfoIcon.tooltip.trade.notTraded={0} adresse onion: {1}\nvous n''avez pas échangé avec ce pair jusqu''à présent.\n{2}
-peerInfoIcon.tooltip.age=Compte de paiement créé il y a {0} jours.
+peerInfoIcon.tooltip.age=Compte de paiement créé il y a {0}.
 peerInfoIcon.tooltip.unknownAge=Ancienneté du compte de paiement inconnue.
 
 tooltip.openPopupForDetails=Ouvrir le popup pour obtenir des détails
@@ -2212,7 +2212,7 @@ peerInfo.nrOfTrades=Nombre d'opérations effectuées
 peerInfo.notTradedYet=Vous n'avez pas encore échangé avec cet utilisateur.
 peerInfo.setTag=Définir un tag pour ce pair
 peerInfo.age.noRisk=Âge du compte de paiement
-peerInfo.age.chargeBackRisk=Time since signing
+peerInfo.age.chargeBackRisk=Temps depuis la signature
 peerInfo.unknownAge=Âge inconnu
 
 addressTextField.openWallet=Ouvrir votre portefeuille Bitcoin par défaut
@@ -2372,7 +2372,7 @@ payment.accepted.banks=Banques acceptées (ID)
 payment.mobile=N° de téléphone portable
 payment.postal.address=Adresse postale
 payment.national.account.id.AR=Numéro CBU
-shared.accountSigningState=Account signing status
+shared.accountSigningState=État de la signature du compte
 
 #new
 payment.altcoin.address.dyn={0} adresse
@@ -2403,7 +2403,7 @@ payment.clearXchange.info=Veuillez vous assurer que vous remplissez les conditio
 payment.moneyGram.info=Lors de l'utilisation de MoneyGram, l'acheteur de BTC doit envoyer le numéro d'autorisation et une photo du reçu par mail au vendeur de BTC. Le reçu doit clairement mentionner le nom complet du vendeur, le pays, la région et le montant. L'acheteur verra ensuite s'afficher le mail du vendeur pendant le processus de la transaction.
 payment.westernUnion.info=Lors de l'utilisation de Western Union, l'acheteur BTC doit envoyer le MTCN (numéro de suivi) et une photo du reçu par e-mail au vendeur de BTC. Le reçu doit indiquer clairement le nom complet du vendeur, la ville, le pays et le montant. L'acheteur verra ensuite s'afficher le mail du vendeur pendant le processus de la transaction.
 payment.halCash.info=Lors de l'utilisation de HalCash, l'acheteur de BTC doit envoyer au vendeur de BTC le code HalCash par SMS depuis son téléphone portable.\n\nVeuillez vous assurer de ne pas dépasser le montant maximum que votre banque vous permet d'envoyer avec HalCash. Le montant minimum par retrait est de 10 EUR et le montant maximum est de 600 EUR. Pour les retraits récurrents, il est de 3000 EUR par destinataire par jour et 6000 EUR par destinataire par mois. Veuillez vérifier ces limites auprès de votre banque pour vous assurer qu'elles utilisent les mêmes limites que celles indiquées ici.\n\nLe montant du retrait doit être un multiple de 10 EUR car vous ne pouvez pas retirer d'autres montants à un distributeur automatique. Pendant les phases de create-offer et take-offer l'affichage de l'interface utilisateur ajustera le montant en BTC afin que le montant en euros soit correct. Vous ne pouvez pas utiliser le prix basé sur le marché, car le montant en euros varierait en fonction de l'évolution des prix.\n\nEn cas de litige, l'acheteur de BTC doit fournir la preuve qu'il a envoyé la somme en EUR.
-payment.limits.info=Veuillez prendre note que tous les transferts bancaires présentent un risque certain de rétrofacturation.\n\nPour atténuer ce risque, Bisq fixe des limites par opération selon deux critères:\n\n1. Une estimation du niveau de risque de rétrofacturation selon le mode de paiement utilisé\n2. l'ancienneté de votre compte avec ce mode de paiement\n\nLe compte que vous venez de créer est nouveau et son âge est égal à zéro. Au fur et à mesure que votre compte prendra de l'âge sur une période de deux mois, vos limites par opération augmenteront avec lui :\n\n● Au cours du 1er mois, votre limite par transaction sera de {0}.\n● Au cours du 2e mois, votre limite par opération sera de {1}.\n● Après le 2e mois, votre limite par opération sera de {2}.\n\nVeuillez noter qu'il n'y a pas de limite sur le nombre total de transactions que vous pouvez effectuer.
+payment.limits.info=Veuillez prendre note que tous les transferts bancaires présentent un risque certain de rétrofacturation.\n\nPour réduire ce risque, Bisq fixe des limites par opération selon deux critères:\n\n1. Une estimation du niveau de risque de rétrofacturation selon le mode de paiement utilisé\n2. l'ancienneté de votre compte avec ce mode de paiement\n\nLe compte que vous venez de créer est nouveau et son âge est égal à zéro. Au fur et à mesure que votre compte prendra de l'âge sur une période de deux mois, vos limites par opération augmenteront avec lui :\n\n● Au cours du 1er mois, votre limite par transaction sera de {0}.\n● Au cours du 2e mois, votre limite par opération sera de {1}.\n● Après le 2e mois, votre limite par opération sera de {2}.\n\nVeuillez noter qu'il n'y a pas de limite sur le nombre total de transactions que vous pouvez effectuer.
 payment.limits.info.withSigning=To limit chargeback risk, Bisq sets per-trade buy limits based on the following 2 factors:\n\n1. General chargeback risk for the payment method\n2. Account signing status\n\nThis payment account you just created carries some chargeback risk and is not yet signed by an arbitrator or trusted peer, so it is limited to buying {0} per trade. After it is signed, buy limits will increase as follows:\n\n● Before signing, and up to 30 days after signing, your per-trade buy limit will be {0}\n● 30 days after signing, your per-trade buy limit will be {1}\n● 60 days after signing, your per-trade buy limit will be {2}\n\nSell limits are not affected by account signing, and increase merely as account age increases. More information is at https://docs.bisq.network/payment-methods#account-signing.\n\nThere are no limits on the number of trades you can make.
 
 payment.cashDeposit.info=Veuillez confirmer que votre banque vous permet d'envoyer des dépôts en espèces sur le compte d'autres personnes. Par exemple, Bank of America et Wells Fargo n'autorisent plus de tels dépôts.
@@ -2422,11 +2422,11 @@ payment.f2f.extra=Informations complémentaires
 payment.f2f.extra.prompt=Le maker peut définir des " conditions générales " ou ajouter des informations publiques de contact.  Elles seront affichées avec l'ordre.
 payment.f2f.info='Face to Face' trades have different rules and come with different risks than online transactions.\n\nThe main differences are:\n● The trading peers need to exchange information about the meeting location and time by using their provided contact details.\n● The trading peers need to bring their laptops and do the confirmation of 'payment sent' and 'payment received' at the meeting place.\n● If a maker has special 'terms and conditions' they must state those in the 'Additional information' text field in the account.\n● By taking an offer the taker agrees to the maker's stated 'terms and conditions'.\n● In case of a dispute the mediator or arbitrator cannot help much as it is usually hard to get tamper proof evidence of what happened at the meeting. In such cases the BTC funds might get locked indefinitely or until the trading peers come to an agreement.\n\nTo be sure you fully understand the differences with 'Face to Face' trades please read the instructions and recommendations at: 'https://docs.bisq.network/trading-rules.html#f2f-trading'
 payment.f2f.info.openURL=Ouvrir la page web
-payment.f2f.offerbook.tooltip.countryAndCity=Country and city: {0} / {1}
+payment.f2f.offerbook.tooltip.countryAndCity=Pays et ville: {0} / {1}
 payment.f2f.offerbook.tooltip.extra=Informations complémentaires: {0}
 
 payment.japan.bank=Banque
-payment.japan.branch=Branch
+payment.japan.branch=Filiale
 payment.japan.account=Compte
 payment.japan.recipient=Nom
 
@@ -2442,7 +2442,7 @@ CASH_DEPOSIT=Dépôt en espèces
 MONEY_GRAM=MoneyGram
 WESTERN_UNION=Western Union
 F2F=Face à face (en personne)
-JAPAN_BANK=Japan Bank Furikomi
+JAPAN_BANK=Banque Japonaise Furikomi
 
 # suppress inspection "UnusedProperty"
 NATIONAL_BANK_SHORT=Banques nationales
@@ -2461,7 +2461,7 @@ WESTERN_UNION_SHORT=Western Union
 # suppress inspection "UnusedProperty"
 F2F_SHORT=F2F
 # suppress inspection "UnusedProperty"
-JAPAN_BANK_SHORT=Japan Furikomi
+JAPAN_BANK_SHORT=Furikomi Japonais
 
 # Do not translate brand names
 # suppress inspection "UnusedProperty"
@@ -2623,12 +2623,12 @@ validation.pattern=La valeur saisie doit être au format: {0}
 validation.noHexString=La valeur saisie n'est pas au format HEX.
 validation.advancedCash.invalidFormat=Doit être un email valide ou un identifiant de portefeuille de type: X000000000000
 validation.invalidUrl=Ceci n'est pas une URL valide
-validation.mustBeDifferent=Your input must be different from the current value
+validation.mustBeDifferent=Votre saisie doit être différente de la valeur actuelle.
 validation.cannotBeChanged=Le paramètre ne peut pas être modifié
 validation.numberFormatException=Number format exception {0}
 validation.mustNotBeNegative=La saisie ne doit pas être négative
-validation.phone.missingCountryCode=Need two letter country code to validate phone number
-validation.phone.invalidCharacters=Phone number {0} contains invalid characters
-validation.phone.insufficientDigits=Not enough digits in {0} for a valid phone number
-validation.phone.tooManyDigits=Too many digits in {0} to be a valid phone number
+validation.phone.missingCountryCode=Un code pays à deux lettres est nécessaire pour valider le numéro de téléphone
+validation.phone.invalidCharacters=Le numéro de téléphone {0} contient des caractères invalides.
+validation.phone.insufficientDigits=Pas assez de chiffres dans {0} pour un numéro de téléphone valide
+validation.phone.tooManyDigits=Trop de chiffres dans {0} pour un numéro de téléphone valide
 validation.phone.invalidDialingCode=Country dialing code in number {0} is invalid for country {1}.  The correct dialing code is {2}.

core/src/main/resources/i18n/displayStrings_ja.properties

@@ -672,7 +672,6 @@ portfolio.pending.step5_buyer.takersMiningFee=合計マイニング手数料
 portfolio.pending.step5_buyer.refunded=返金されたセキュリティデポジット
 portfolio.pending.step5_buyer.withdrawBTC=ビットコインを出金する
 portfolio.pending.step5_buyer.amount=出金額
-portfolio.pending.step5_buyer.signer=By withdrawing your bitcoins, you verify that the counterparty has acted according to the trade protocol.
 portfolio.pending.step5_buyer.withdrawToAddress=出金先アドレス
 portfolio.pending.step5_buyer.moveToBisqWallet=資金をBisqウォレットに移動する
 portfolio.pending.step5_buyer.withdrawExternal=外部ウォレットに出金する
@@ -873,7 +872,7 @@ support.sellerOfferer=BTC 売り手/メイカー
 support.buyerTaker=BTC 買い手/テイカー
 support.sellerTaker=BTC 売り手/テイカー
 
-support.backgroundInfo=Bisq is not a company, so it handles disputes differently.\n\nTraders can communicate within the application via a secure chat on the open trades screen to attempt solving a dispute on their own. If that is not sufficient, a mediator can step in to help. The mediator will evaluate the situation and give a recommendation for the payout of the trade funds. If both traders accept this suggestion, the payout transaction is completed and the trade is closed. If one or both traders do not agree to the mediator's recommended payout, they can request arbitration.The arbitrator has the third key of the deposit transaction and will make the payout based on their findings.
+support.backgroundInfo=Bisq is not a company, so it handles disputes differently.\n\nTraders can communicate within the application via secure chat on the open trades screen to try solving disputes on their own. If that is not sufficient, a mediator can step in to help. The mediator will evaluate the situation and suggest a payout of trade funds. If both traders accept this suggestion, the payout transaction is completed and the trade is closed. If one or both traders do not agree to the mediator's suggested payout, they can request arbitration.The arbitrator will re-evaluate the situation and, if warranted, personally pay the trader back and request reimbursement for this payment from the Bisq DAO.
 support.initialInfo=Please enter a description of your problem in the text field below. Add as much information as possible to speed up dispute resolution time.\n\nHere is a check list for information you should provide:\n\t● If you are the BTC buyer: Did you make the Fiat or Altcoin transfer? If so, did you click the 'payment started' button in the application?\n\t● If you are the BTC seller: Did you receive the Fiat or Altcoin payment? If so, did you click the 'payment received' button in the application?\n\t● Which version of Bisq are you using?\n\t● Which operating system are you using?\n\t● If you encountered an issue with failed transactions please consider switching to a new data directory.\n\t  Sometimes the data directory gets corrupted and leads to strange bugs. \n\t  See: https://docs.bisq.network/backup-recovery.html#switch-to-a-new-data-directory\n\nPlease make yourself familiar with the basic rules for the dispute process:\n\t● You need to respond to the {0}''s requests within 2 days.\n\t● Mediators respond in between 2 days. Arbitrators respond in between 5 business days.\n\t● The maximum period for a dispute is 14 days.\n\t● You need to cooperate with the {1} and provide the information they request to make your case.\n\t● You accepted the rules outlined in the dispute document in the user agreement when you first started the application.\n\nYou can read more about the dispute process at: {2}
 support.systemMsg=システムメッセージ: {0}
 support.youOpenedTicket=サポートのリクエスト開始しました。\n\n{0}\n\nBisqバージョン: {1}
@@ -1038,7 +1037,7 @@ account.altcoin.popup.wallet.msg=Please be sure that you follow the requirements
 account.altcoin.popup.wallet.confirm=どのウォレットを使うべきか理解しており、承認する
 account.altcoin.popup.upx.msg=Trading UPX on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending UPX, you need to use either the official uPlexa GUI wallet or uPlexa CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nuplexa-wallet-cli (use the command get_tx_key)\nuplexa-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The UPX sender is responsible for providing verification of the UPX transfer to the arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit uPlexa discord channel (https://discord.gg/vhdNSrV) or the uPlexa Telegram Chat (https://t.me/uplexaOfficial) to find more information.
 account.altcoin.popup.arq.msg=Trading ARQ on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending ARQ, you need to use either the official ArQmA GUI wallet or ArQmA CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\narqma-wallet-cli (use the command get_tx_key)\narqma-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the mediator or arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The ARQ sender is responsible for providing verification of the ARQ transfer to the mediator or arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit ArQmA discord channel (https://discord.gg/s9BQpJT) or the ArQmA forum (https://labs.arqma.com) to find more information.
-account.altcoin.popup.xmr.msg=Trading XMR on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending XMR, you need to use either the official Monero GUI wallet or Monero CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nmonero-wallet-cli (use the command get_tx_key)\nmonero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nIn addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\nmonero-wallet-cli : using command (check_tx_key).\nmonero-wallet-gui : on the Advanced > Prove/Check page.\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the mediator or arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The XMR sender is responsible for providing verification of the XMR transfer to the mediator or arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) or the Monero forum (https://forum.getmonero.org) to find more information.
+account.altcoin.popup.xmr.msg=Trading XMR on Bisq requires that you understand and fulfill the following requirements:\n\nProve payments: since Monero is a private coin, some transaction details aren't publicly available in the blockchain, and, in case of a dispute, the mediator or arbitrator needs them to check if the transaction was really made. In Bisq, the sender of the XMR transaction is the one responsible for providing this information to the mediator or arbitrator in case of a dispute. In order to do that, you must send XMR using a wallet that provides the information required to prove the payment was made, which includes:\n\n- the transaction key (Tx Key, Tx Secret Key or Tx Private Key)\n- the transaction ID (Tx ID or Tx Hash)\n- the destination address (recipient's address)\n\nThis information can be found in the official Monero GUI & CLI wallets, MyMonero, and Exodus (desktop) as well as in Cake Wallet, MyMonero, and Monerujo (mobile), in the following locations:\n\n- Monero GUI: go to Transactions tab\n- Monero CLI: use the command get_tx_key TXID. The flag store-tx-info must be enabled (enabled by default in new versions)\n- Other wallets: go to Transactions history and search for Transaction key (Tx key or Secret key) and the destination address in a sent transaction. Save recipient address option must be enabled in Cake Wallet settings.\n\nIf you are using a wallet different from the mentioned above, please be sure you can access those three pieces of information.Since the transaction key and the destination address are stored in the Monero wallet software, and they cannot be recovered in the Monero blockchain, you should never delete or restore your Monero wallet before a Bisq trade is completed. Failure to provide the above data will result in losing the dispute case.\n\nCheck payments: with those three pieces of information, the verification that a quantity of Monero was sent to a specific address can be accomplished the following way:\n\n- Monero GUI: change wallet to Advanced mode and go to Advanced > Prove/check > Check Transaction\n- Monero CLI: use the command check_tx_key TXID TXKEY ADDRESS\n- XMR checktx tool (https://xmr.llcoins.net/checktx.html)\n- Explore Monero website (https://www.exploremonero.com/receipt)\n\nIf you are still not sure about this process, visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) to find more information or ask a question on the Monero support subreddit (https://www.reddit.com/r/monerosupport/).
 # suppress inspection "TrailingSpacesInProperty"
 account.altcoin.popup.msr.msg=Trading MSR on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending MSR, you need to use either the official Masari GUI wallet, Masari CLI wallet with the store-tx-info flag enabled (enabled by default) or the Masari web wallet (https://wallet.getmasari.org). Please be sure you can access the tx key as that would be required in case of a dispute.\nmasari-wallet-cli (use the command get_tx_key)\nmasari-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nMasari Web Wallet (goto Account -> transaction history and view details on your sent transaction)\n\nVerification can be accomplished in-wallet.\nmasari-wallet-cli : using command (check_tx_key).\nmasari-wallet-gui : on the Advanced > Prove/Check page.\nVerification can be accomplished in the block explorer \nOpen block explorer (https://explorer.getmasari.org), use the search bar to find your transaction hash.\nOnce transaction is found, scroll to bottom to the 'Prove Sending' area and fill in details as needed.\nYou need to provide the mediator or arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The MSR sender is responsible for providing verification of the MSR transfer to the mediator or arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process, ask for help on the Official Masari Discord (https://discord.gg/sMCwMqs).
 account.altcoin.popup.blur.msg=Trading BLUR on Bisq requires that you understand and fulfill the following requirements:\n\nTo send BLUR you must use the Blur Network CLI or GUI Wallet. \n\nIf you are using the CLI wallet, a transaction hash (tx ID) will be displayed after a transfer is sent. You must save this information. Immediately after sending the transfer, you must use the command 'get_tx_key' to retrieve the transaction private key. If you fail to perform this step, you may not be able to retrieve the key later. \n\nIf you are using the Blur Network GUI Wallet, the transaction private key and transaction ID can be found conveniently in the "History" tab.  Immediately after sending, locate the transaction of interest. Click the "?" symbol in the lower-right corner of the box containing the transaction. You must save this information. \n\nIn the event that arbitration is necessary, you must present the following to an mediator or arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address.  The mediator or arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nFailure to provide the required information to the mediator or arbitrator will result in losing the dispute case. In all cases of dispute, the BLUR sender bears 100% of the burden of responsibility in verifying transactions to an mediator or arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW).
@@ -1169,6 +1168,7 @@ dao.lockedForVoteBalance=投票に使用済
 dao.lockedInBonds=ロック中の担保
 dao.availableNonBsqBalance=利用可能な非BSQ残高 (BTC)
 dao.totalBsqBalance=合計BSQ残高
+dao.reputationBalance=Merit Value (not spendable)
 
 dao.tx.published.success=トランザクションの発行に成功しました
 dao.proposal.menuItem.make=提案する
@@ -1961,7 +1961,7 @@ showWalletDataWindow.includePrivKeys=プライベートキーを含む
 tacWindow.headline=ユーザー規約
 tacWindow.agree=同意します
 tacWindow.disagree=同意せずにに終了
-tacWindow.arbitrationSystem=調停システム
+tacWindow.arbitrationSystem=Dispute resolution
 
 tradeDetailsWindow.headline=トレード
 tradeDetailsWindow.disputedPayoutTxId=係争中の支払い取引ID:
@@ -2152,7 +2152,7 @@ systemTray.show=アプリケーションウィンドウを表示
 systemTray.hide=アプリケーションウィンドウを隠す
 systemTray.info=Bisqについての情報
 systemTray.exit=終了
-systemTray.tooltip=Bisq: 非中央集権の交換ネットワーク
+systemTray.tooltip=Bisq: A decentralized bitcoin exchange network
 
 
 ####################################################################

core/src/main/resources/i18n/displayStrings_pt-br.properties

@@ -168,7 +168,7 @@ shared.payoutTxId=ID da transação de pagamento
 shared.contractAsJson=Contrato em formato JSON
 shared.viewContractAsJson=Ver contrato em formato JSON
 shared.contract.title=Contrato para negociação com ID: {0}
-shared.paymentDetails=Detalhes do pagamento BTC {0}
+shared.paymentDetails=Detalhes de pagamento do {0} de BTC
 shared.securityDeposit=Depósito de segurança
 shared.yourSecurityDeposit=Seu depósito de segurança
 shared.contract=Contrato
@@ -276,7 +276,7 @@ mainView.walletServiceErrorMsg.connectionError=Não foi possível conectar-se à
 
 mainView.walletServiceErrorMsg.rejectedTxException=Uma transação foi rejeitada pela rede.\n\n{0}
 
-mainView.networkWarning.allConnectionsLost=Você perdeu sua conexão com todos {0} os pontos da rede.\nTalvez você tenha perdido a conexão com a internet ou seu computador estava em modo de espera.
+mainView.networkWarning.allConnectionsLost=Você perdeu sua conexão com todos os pontos da rede {0}.\nTalvez você tenha perdido a conexão com a internet ou seu computador estava em modo de espera.
 mainView.networkWarning.localhostBitcoinLost=Você perdeu a conexão ao nó Bitcoin do localhost.\nPor favor, reinicie o aplicativo Bisq para conectar-se a outros nós Bitcoin ou reinicie o nó Bitcoin do localhost.
 mainView.version.update=(Atualização disponível)
 
@@ -376,10 +376,10 @@ offerbook.warning.noMatchingAccount.msg=Para aceitar essa oferta, é necessário
 
 offerbook.warning.counterpartyTradeRestrictions=Esta oferta não pode ser tomada por restrições de negociação da outra parte
 
-offerbook.warning.newVersionAnnouncement=With this version of the software, trading peers can verify and sign each others' payment accounts to create a network of trusted payment accounts.\n\nAfter successfully trading with a peer with a verified payment account, your payment account will be signed and trading limits will be lifted after a certain time interval (length of this interval is based on the verification method).\n\nFor more information on account signing, please see the documentation at https://docs.bisq.network/payment-methods#account-signing.
+offerbook.warning.newVersionAnnouncement=Com essa versão do software, os pares negociantes podem verificar e assinar as contas de pagamento uns dos outros para criarem uma rede de contas de pagamento confiáveis.\n\nApós realizar uma negociação bem sucedida com um parceiro que tenha uma conta de pagamento verificada, a sua conta de pagamento será assinada e seu limite de negociação será aumentado depois de um certo período de tempo (o tempo de espera depende do método de verificação).\n\nPara mais informações sobre a assinatura de contas, veja por favor a documentação em https://docs.bisq.network/payment-methods#account-signing.
 
-popup.warning.tradeLimitDueAccountAgeRestriction.seller=The allowed trade amount is limited to {0} because of security restrictions based on the following criteria:\n- The buyer''s account has not been signed by an arbitrator or a peer\n- The time since signing of the buyer''s account is not at least 30 days\n- The payment method for this offer is considered risky for bank chargebacks\n\n{1}
-popup.warning.tradeLimitDueAccountAgeRestriction.buyer=The allowed trade amount is limited to {0} because of security restrictions based on the following criteria:\n- Your account has not been signed by an arbitrator or a peer\n- The time since signing of your account is not at least 30 days\n- The payment method for this offer is considered risky for bank chargebacks\n\n{1}
+popup.warning.tradeLimitDueAccountAgeRestriction.seller=A quantia permitida para a negociação está limitada a {0} devido a restrições de segurança baseadas nos seguintes critérios:\n- A conta do comprador não foi assinada por um árbitro ou um par\n- A conta do comprador foi assinada há menos de 30 dias\n- O meio de pagamento para essa oferta é considerado de risco para estornos bancários.\n\n{1}
+popup.warning.tradeLimitDueAccountAgeRestriction.buyer=A quantia permitida para a negociação está limitada a {0} devido a restrições de segurança baseadas nos seguintes critérios:\n- A sua conta não foi assinada por um árbitro ou um par\n- A sua conta foi assinada há menos de 30 dias\n- O meio de pagamento para essa oferta é considerado de risco para estornos bancários.\n\n{1}
 
 offerbook.warning.wrongTradeProtocol=Essa oferta requer uma versão do protocolo diferente da usada em sua versão do software.\n\nVerifique se você possui a versão mais nova instalada, caso contrário o usuário que criou a oferta usou uma versão ultrapassada.\n\nUsuários não podem negociar com uma versão incompatível do protocolo.
 offerbook.warning.userIgnored=Você adicionou o endereço onion à sua lista de endereços ignorados.
@@ -505,7 +505,7 @@ takeOffer.failed.offerTaken=Não foi possível aceitar a oferta, pois ela já fo
 takeOffer.failed.offerRemoved=Não é possível aceitar a oferta pois ela foi removida.
 takeOffer.failed.offererNotOnline=Erro ao aceitar a oferta: o ofertante não está mais online.
 takeOffer.failed.offererOffline=Erro ao aceitar a oferta: o ofertante está offline.
-takeOffer.warning.connectionToPeerLost=You lost connection to the maker.\nThey might have gone offline or has closed the connection to you because of too many open connections.\n\nIf you can still see their offer in the offerbook you can try to take the offer again.
+takeOffer.warning.connectionToPeerLost=Você perdeu a conexão com o ofertante.\nEle pode ter ficado offline ou teve a conexão com você fechada em decorrência de muitas conexões abertas.\n\nSe você ainda pode ver a oferta dele no livro de ofertas você pode tentar aceitá-la novamente.
 
 takeOffer.error.noFundsLost=\n\nA sua carteira ainda não realizou o pagamento.\nPor favor, reinicie o programa e verifique a sua conexão com a internet.
 takeOffer.error.feePaid=\n\nTente reiniciar o programa e verifique sua conexão de rede para ver se o problema foi resolvido.
@@ -580,8 +580,8 @@ portfolio.pending.step2_buyer.amountToTransfer=Quantia a ser transferida
 portfolio.pending.step2_buyer.sellersAddress=Endereço {0} do vendedor
 portfolio.pending.step2_buyer.buyerAccount=A sua conta de pagamento a ser usada
 portfolio.pending.step2_buyer.paymentStarted=Pagamento iniciado
-portfolio.pending.step2_buyer.warn=You still have not done your {0} payment!\nPlease note that the trade has to be completed by {1}.
-portfolio.pending.step2_buyer.openForDispute=You have not completed your payment!\nThe max. period for the trade has elapsed.Please contact the mediator for assistance.
+portfolio.pending.step2_buyer.warn=Você ainda não realizou seu pagamento de {0}!\nEssa negociação deve ser completada até {1}.
+portfolio.pending.step2_buyer.openForDispute=Você ainda não completou o seu pagamento!\nO período máximo para a negociação já passou. Entre em contato com o mediador para pedir assistência.
 portfolio.pending.step2_buyer.paperReceipt.headline=Você enviou o comprovante de depósito para o vendedor de BTC?
 portfolio.pending.step2_buyer.paperReceipt.msg=Lembre-se:\nVocê deve escrever no comprovante de depósito: SEM REEMBOLSO\nA seguir, rasgue-o em duas partes, tire uma foto e envie-a para o e-mail do vendedor de BTC.
 portfolio.pending.step2_buyer.moneyGramMTCNInfo.headline=Enviar o número de autorização e o comprovante de depósito
@@ -599,7 +599,7 @@ portfolio.pending.step2_seller.waitPayment.headline=Aguardar pagamento
 portfolio.pending.step2_seller.f2fInfo.headline=Informações de contato do comprador
 portfolio.pending.step2_seller.waitPayment.msg=A transação de depósito tem pelo menos uma confirmação blockchain do protocolo.\nVocê precisa aguardar até que o comprador de BTC inicie o pagamento de {0}.
 portfolio.pending.step2_seller.warn=O comprador de BTC ainda não fez o pagamento de {0}.\nVocê precisa esperar até que ele inicie o pagamento.\nCaso a negociação não conclua em {1}, o árbitro irá investigar.
-portfolio.pending.step2_seller.openForDispute=The BTC buyer has not started their payment!\nThe max. allowed period for the trade has elapsed.\nYou can wait longer and give the trading peer more time or contact the mediator for assistance.
+portfolio.pending.step2_seller.openForDispute=O comprador de BTC ainda não iniciou o pagamento!\nO período máximo permitido para a negociação expirou.\nVocê pode aguardar mais um pouco, dando mais tempo para o seu parceiro de negociação, ou você pode entrar em contato com o mediador para pedir assistência.
 
 tradeChat.chatWindowTitle=Abrir janela de conversa para a negociação com ID "{0}"
 tradeChat.openChat=Abrir janela de conversa
@@ -652,15 +652,15 @@ portfolio.pending.step3_seller.buyerStartedPayment.altcoin=Verifique as confirma
 portfolio.pending.step3_seller.buyerStartedPayment.fiat=Verifique em sua conta de negociação (ex: sua conta bancária) e confirme que recebeu o pagamento.
 portfolio.pending.step3_seller.warn.part1a=na blockchain {0}
 portfolio.pending.step3_seller.warn.part1b=no seu provedor de pagamentos (ex: banco)
-portfolio.pending.step3_seller.warn.part2=You still have not confirmed the receipt of the payment. Please check {0} if you have received the payment.
-portfolio.pending.step3_seller.openForDispute=You have not confirmed the receipt of the payment!\nThe max. period for the trade has elapsed.\nPlease confirm or request assistance from the mediator.
+portfolio.pending.step3_seller.warn.part2=Você ainda não confirmou o recebimento do pagamento. Por favor,  verifique em {0} se você recebeu o pagamento.
+portfolio.pending.step3_seller.openForDispute=Você ainda não confirmou o recebimento do pagamento!\nO período máximo para a negociação expirou.\nPor favor, confirme o recebimento do pagamento ou entre em contato com o mediador para pedir assistência.
 # suppress inspection "TrailingSpacesInProperty"
 portfolio.pending.step3_seller.onPaymentReceived.part1=Você recebeu o pagamento de {0} do seu parceiro de negociação?\n\n
 # suppress inspection "TrailingSpacesInProperty"
 portfolio.pending.step3_seller.onPaymentReceived.fiat=O ID de negociação (texto \"razão do pagamento\") da transação é: \"{0}\"\n
 # suppress inspection "TrailingSpacesInProperty"
 portfolio.pending.step3_seller.onPaymentReceived.name=Please also verify that the name of the sender specified on the trade contract matches the name that appears on your bank statement:\nSender''s name, per trade contract: {0}\n\nIf the names are not exactly the same, don''t confirm payment receipt. Instead, open a dispute by pressing \"alt + o\" or \"option + o\".\n\n
-portfolio.pending.step3_seller.onPaymentReceived.note=Please note, that as soon you have confirmed the receipt, the locked trade amount will be released to the BTC buyer and the security deposit will be refunded.\n\n
+portfolio.pending.step3_seller.onPaymentReceived.note=Assim que você confirmar o recebimento do pagamento, o valor da transação será liberado para o comprador de BTC e o depósito de segurança será devolvido.\n\n
 portfolio.pending.step3_seller.onPaymentReceived.confirm.headline=Confirmar recebimento do pagamento
 portfolio.pending.step3_seller.onPaymentReceived.confirm.yes=Sim, eu recebi o pagamento
 portfolio.pending.step3_seller.onPaymentReceived.signer=IMPORTANT: By confirming receipt of payment, you are also verifying the account of the counterparty and signing it accordingly. Since the account of the counterparty hasn't been signed yet, you should delay confirmation of the payment as long as possible to reduce the risk of a chargeback.
@@ -672,7 +672,6 @@ portfolio.pending.step5_buyer.takersMiningFee=Total em taxas de mineração
 portfolio.pending.step5_buyer.refunded=Depósito de segurança devolvido
 portfolio.pending.step5_buyer.withdrawBTC=Retirar seus bitcoins
 portfolio.pending.step5_buyer.amount=Quantia a ser retirada
-portfolio.pending.step5_buyer.signer=By withdrawing your bitcoins, you verify that the counterparty has acted according to the trade protocol.
 portfolio.pending.step5_buyer.withdrawToAddress=Enviar para o endereço
 portfolio.pending.step5_buyer.moveToBisqWallet=Mover fundos para carteira Bisq
 portfolio.pending.step5_buyer.withdrawExternal=Retirar para carteira externa
@@ -705,9 +704,9 @@ portfolio.pending.openAgainDispute.button=Abrir disputa novamente
 portfolio.pending.openSupportTicket.headline=Abrir ticket de suporte
 portfolio.pending.openSupportTicket.msg=Please use this function only in emergency cases if you don't see a \"Open support\" or \"Open dispute\" button.\n\nWhen you open a support ticket the trade will be interrupted and handled by a mediator or arbitrator.
 
-portfolio.pending.timeLockNotOver=You have to wait until ≈{0} ({1} more blocks) before you can open an arbitration dispute.
+portfolio.pending.timeLockNotOver=Você precisa aguardar até ≈{0} (mais {1} blocos) para conseguir abrir uma disputa com um árbitro.
 portfolio.pending.error.depositTxNull=The deposit transaction is null. You cannot open a dispute without a valid deposit transaction. Please go to \"Settings/Network info\" and do a SPV resync.\n\nFor further help please contact the Bisq support channel at the Bisq Keybase team.
-portfolio.pending.mediationResult.error.depositTxNull=The deposit transaction is null. The trade gets moved to the failed trades section.
+portfolio.pending.mediationResult.error.depositTxNull=A transação de depósito é nula. A negociação será movida para a seção de negociações com erro.
 portfolio.pending.error.depositTxNotConfirmed=The deposit transaction is not confirmed. You can not open an arbitration dispute with an unconfirmed deposit transaction. Please wait until it is confirmed or go to \"Settings/Network info\" and do a SPV resync.\n\nFor further help please contact the Bisq support channel at the Bisq Keybase team.
 
 portfolio.pending.notification=Notificação
@@ -716,7 +715,7 @@ portfolio.pending.support.headline.getHelp=Precisa de ajuda?
 portfolio.pending.support.text.getHelp=If you have any problems you can try to contact the trade peer in the trade chat or ask the Bisq community at https://bisq.community. If your issue still isn't resolved, you can request more help from a mediator.
 portfolio.pending.support.text.getHelp.arbitrator=If you have any problems you can try to contact the trade peer in the trade chat or ask the Bisq community at https://bisq.community. If your issue still isn't resolved, you can request more help from an arbitrator.
 portfolio.pending.support.button.getHelp=Pedir ajuda
-portfolio.pending.support.popup.info=If your issue with the trade remains unsolved, you can open a support ticket to request help from a mediator. If you have not received the payment, please wait until the trade period is over.\n\nAre you sure you want to open a support ticket?
+portfolio.pending.support.popup.info=Se o seu problema com a negociação ainda não foi resolvido, você pode abrir um ticket de suporte para pedir ajuda a um mediador. Se você não recebeu o pagamento, por favor aguarde até o final do período de negociação.\n\nVocê tem certeza de que quer abrir um ticket de suporte?
 portfolio.pending.support.popup.button=Abrir ticket de suporte
 portfolio.pending.support.headline.halfPeriodOver=Verifique o pagamento
 portfolio.pending.support.headline.periodOver=O período de negociação acabou
@@ -811,7 +810,7 @@ funds.tx.takeOfferFee=Taxa de aceitação e transação: {0}
 funds.tx.multiSigDeposit=Depósito Multisig: {0}
 funds.tx.multiSigPayout=Pagamento Multisig: {0}
 funds.tx.disputePayout=Pagamento de disputa: {0}
-funds.tx.disputeLost=Caso de perda de disputa: {0}
+funds.tx.disputeLost=Caso com disputa perdida: {0}
 funds.tx.collateralForRefund=Refund collateral: {0}
 funds.tx.timeLockedPayoutTx=Time locked payout tx: {0}
 funds.tx.refund=Refund from arbitration: {0}
@@ -843,7 +842,7 @@ support.filter=Lista de filtragem
 support.filter.prompt=Insira ID da negociação. data. endereço onion ou dados da conta
 support.noTickets=Não há tickets de suporte abertos
 support.sendingMessage=Enviando mensagem...
-support.receiverNotOnline=Receiver is not online. Message is saved to their mailbox.
+support.receiverNotOnline=O recipiente não está online. A mensagem será salva na caixa postal dele.
 support.sendMessageError=Erro ao enviar a mensagem: {0}
 support.wrongVersion=A oferta nessa disputa foi criada com uma versão anterior do Bisq.\nVocê não pode fechar aquela disputa com a sua versão atual do programa.\n\nFavor utilizar uma versão mais velha com protocolo versão {0}
 support.openFile=Abrir arquivo para anexar (tamanho máximo: {0} kb)
@@ -873,17 +872,17 @@ support.sellerOfferer=Vendedor de BTC / Ofertante
 support.buyerTaker=Comprador de BTC / Aceitador da oferta
 support.sellerTaker=Vendedor de BTC / Aceitador da oferta
 
-support.backgroundInfo=Bisq is not a company, so it handles disputes differently.\n\nTraders can communicate within the application via a secure chat on the open trades screen to attempt solving a dispute on their own. If that is not sufficient, a mediator can step in to help. The mediator will evaluate the situation and give a recommendation for the payout of the trade funds. If both traders accept this suggestion, the payout transaction is completed and the trade is closed. If one or both traders do not agree to the mediator's recommended payout, they can request arbitration.The arbitrator has the third key of the deposit transaction and will make the payout based on their findings.
+support.backgroundInfo=Bisq is not a company, so it handles disputes differently.\n\nTraders can communicate within the application via secure chat on the open trades screen to try solving disputes on their own. If that is not sufficient, a mediator can step in to help. The mediator will evaluate the situation and suggest a payout of trade funds. If both traders accept this suggestion, the payout transaction is completed and the trade is closed. If one or both traders do not agree to the mediator's suggested payout, they can request arbitration.The arbitrator will re-evaluate the situation and, if warranted, personally pay the trader back and request reimbursement for this payment from the Bisq DAO.
 support.initialInfo=Please enter a description of your problem in the text field below. Add as much information as possible to speed up dispute resolution time.\n\nHere is a check list for information you should provide:\n\t● If you are the BTC buyer: Did you make the Fiat or Altcoin transfer? If so, did you click the 'payment started' button in the application?\n\t● If you are the BTC seller: Did you receive the Fiat or Altcoin payment? If so, did you click the 'payment received' button in the application?\n\t● Which version of Bisq are you using?\n\t● Which operating system are you using?\n\t● If you encountered an issue with failed transactions please consider switching to a new data directory.\n\t  Sometimes the data directory gets corrupted and leads to strange bugs. \n\t  See: https://docs.bisq.network/backup-recovery.html#switch-to-a-new-data-directory\n\nPlease make yourself familiar with the basic rules for the dispute process:\n\t● You need to respond to the {0}''s requests within 2 days.\n\t● Mediators respond in between 2 days. Arbitrators respond in between 5 business days.\n\t● The maximum period for a dispute is 14 days.\n\t● You need to cooperate with the {1} and provide the information they request to make your case.\n\t● You accepted the rules outlined in the dispute document in the user agreement when you first started the application.\n\nYou can read more about the dispute process at: {2}
 support.systemMsg=Mensagem do sistema: {0}
 support.youOpenedTicket=Você abriu um pedido de suporte.\n\n{0}\n\nBisq versão: {1}
 support.youOpenedDispute=Você abriu um pedido para uma disputa.\n\n{0}\n\nBisq versão: {1}
-support.youOpenedDisputeForMediation=You requested mediation.\n\n{0}\n\nBisq version: {1}
-support.peerOpenedTicket=Your trading peer has requested support due to technical problems.\n\n{0}\n\nBisq version: {1}
-support.peerOpenedDispute=Your trading peer has requested a dispute.\n\n{0}\n\nBisq version: {1}
-support.peerOpenedDisputeForMediation=Your trading peer has requested mediation.\n\n{0}\n\nBisq version: {1}
-support.mediatorsDisputeSummary=System message:\nMediator''s dispute summary:\n{0}
-support.mediatorsAddress=Mediator''s node address: {0}
+support.youOpenedDisputeForMediation=Você solicitou mediação.\n\n{0}\n\nVersão do Bisq: {1}
+support.peerOpenedTicket=O seu parceiro de negociação solicitou suporte devido a problemas técnicos.\n\n{0}\n\nVersão do Bisq: {1}
+support.peerOpenedDispute=O seu parceiro de negociação solicitou uma disputa.\n\n{0}\n\nVersão do Bisq: {1}
+support.peerOpenedDisputeForMediation=O seu parceiro de negociação solicitou mediação.\n\n{0}\n\nVersão do Bisq: {1}
+support.mediatorsDisputeSummary=Mensagem do sistema:\nResumo da disputa:\n{0}
+support.mediatorsAddress=Endereço do nó do mediador: {0}
 
 
 ####################################################################
@@ -1007,7 +1006,7 @@ setting.about.subsystems.val=Versão da rede: {0}; Versão de mensagens P2P: {1}
 ####################################################################
 
 account.tab.arbitratorRegistration=Registro de árbitro
-account.tab.mediatorRegistration=Mediator registration
+account.tab.mediatorRegistration=Registro de mediador
 account.tab.refundAgentRegistration=Refund agent registration
 account.tab.account=Conta
 account.info.headline=Bem vindo à sua conta Bisq
@@ -1023,22 +1022,22 @@ account.menu.notifications=Notificações
 ## TODO should we rename the following to a gereric name?
 account.arbitratorRegistration.pubKey=Chave pública
 
-account.arbitratorRegistration.register=Register
-account.arbitratorRegistration.registration={0} registration
+account.arbitratorRegistration.register=Registro
+account.arbitratorRegistration.registration=Registro de {0}
 account.arbitratorRegistration.revoke=Revogar
 account.arbitratorRegistration.info.msg=Please note that you need to stay available for 15 days after revoking as there might be trades which are using you as {0}. The max. allowed trade period is 8 days and the dispute process might take up to 7 days.
 account.arbitratorRegistration.warn.min1Language=Você precisa escolher pelo menos 1 idioma.\nNós adicionamos o idioma padrão para você.
-account.arbitratorRegistration.removedSuccess=You have successfully removed your registration from the Bisq network.
-account.arbitratorRegistration.removedFailed=Could not remove registration.{0}
-account.arbitratorRegistration.registerSuccess=You have successfully registered to the Bisq network.
-account.arbitratorRegistration.registerFailed=Could not complete registration.{0}
+account.arbitratorRegistration.removedSuccess=O seu registro foi removido com sucesso da rede Bisq.
+account.arbitratorRegistration.removedFailed=Não foi possível remover o registro.{0}
+account.arbitratorRegistration.registerSuccess=Você se registrou com sucesso na rede Bisq.
+account.arbitratorRegistration.registerFailed=Não foi possível completar o registro.{0}
 
 account.altcoin.yourAltcoinAccounts=Suas contas de altcoins
 account.altcoin.popup.wallet.msg=Please be sure that you follow the requirements for the usage of {0} wallets as described on the {1} web page.\nUsing wallets from centralized exchanges where (a) you don''t control your keys or (b) which don''t use compatible wallet software is risky: it can lead to loss of the traded funds!\nThe mediator or arbitrator is not a {2} specialist and cannot help in such cases.
 account.altcoin.popup.wallet.confirm=Eu entendo e confirmo que sei qual carteira preciso usar.
 account.altcoin.popup.upx.msg=Trading UPX on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending UPX, you need to use either the official uPlexa GUI wallet or uPlexa CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nuplexa-wallet-cli (use the command get_tx_key)\nuplexa-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The UPX sender is responsible for providing verification of the UPX transfer to the arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit uPlexa discord channel (https://discord.gg/vhdNSrV) or the uPlexa Telegram Chat (https://t.me/uplexaOfficial) to find more information.
 account.altcoin.popup.arq.msg=Trading ARQ on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending ARQ, you need to use either the official ArQmA GUI wallet or ArQmA CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\narqma-wallet-cli (use the command get_tx_key)\narqma-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the mediator or arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The ARQ sender is responsible for providing verification of the ARQ transfer to the mediator or arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit ArQmA discord channel (https://discord.gg/s9BQpJT) or the ArQmA forum (https://labs.arqma.com) to find more information.
-account.altcoin.popup.xmr.msg=Trading XMR on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending XMR, you need to use either the official Monero GUI wallet or Monero CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nmonero-wallet-cli (use the command get_tx_key)\nmonero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nIn addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\nmonero-wallet-cli : using command (check_tx_key).\nmonero-wallet-gui : on the Advanced > Prove/Check page.\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the mediator or arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The XMR sender is responsible for providing verification of the XMR transfer to the mediator or arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) or the Monero forum (https://forum.getmonero.org) to find more information.
+account.altcoin.popup.xmr.msg=Negociar XMR na Bisq requer que você entenda e cumpra os seguintes requisitos:\n\nComprovar pagamentos: como a Monero é uma moeda privada, alguns detalhes da transação não estão disponíveis publicamente na blockchain e, em caso de uma disputa, o mediador ou o árbitro precisará deles para verificar se a transação realmente foi realizada. Na Bisq, o remetente da transação com XMR é a pessoa responsável por fornecer essas informações para o mediador ou o árbitro em caso de uma disputa. Para fazer isso, você precisa enviar XMR usando uma carteira que forneça as informações necessárias para comprovar que o pagamento foi feito, que incluem:\n\n- a chave da transação (Tx Key, Tx Secret Key ou Tx Private Key)\n- o ID da transação (Tx ID ou Tx Hash)\n- o endereço de destino (endereço do recipiente)\n\nEssas informações podem ser encontradas nas carteiras de desktop Monero GUI & CLI, MyMonero e Exodus assim como nas carteiras móveis Cake Wallet, MyMonero e Monerujo, nas seguintes localizações:\n\n- Monero GUI: vá para a aba Transações\n- Monero CLI: use o comando get_tx_key TXID. A flag store-tx-info deve estar habilitada (habilitada por padrão nas versões mais recentes)\n- Outras carteiras: vá para o histórico de Transações e procure pela chave da transação (Tx key ou Secret key) e o endereço destino em uma transação prévia. Se você estiver usando a Cake Wallet, a opção salvar endereço do recipiente deve estar habilitada nas configurações.\n\nSe você estiver usando uma carteira diferente das mencionadas acima, certifique-se de que você consegue acessar essas três informações. Como a chave da transação e o endereço de destino são armazenados no software da carteira Monero, e eles não podem ser recuperados na blockchain do Monero, você jamais deve deletar ou restaurar a sua carteira Monero antes de completar uma negociação na Bisq. Se você não conseguir fornecer as informações necessárias, você perderá a disputa.\n\nVerificando pagamentos: com essas três informações, a verificação de que uma quantia de Monero foi enviada para um endereço específico pode ser realizada da seguinte maneira:\n\n- Monero GUI: mude a carteira para o modo Avançado e vá para Avançado > Provar/verificar > Verificar Transação\n- Monero CLI: use o comando check_tx_key TXID TXKEY ADDRESS\n- XMR checktx tool (https://xmr.llcoins.net/checktx.html)\n- Site Explore Monero (https://www.exploremonero.com/receipt)\n\nSe você ainda tem dúvidas sobre o processo, visite (https://www.getmonero.org/pt-br/resources/user-guides/prove-payment.html) para obter maiores informações ou faça uma pergunta no subreddit do suporte do Monero (https://www.reddit.com/r/monerosupport/).
 # suppress inspection "TrailingSpacesInProperty"
 account.altcoin.popup.msr.msg=Trading MSR on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending MSR, you need to use either the official Masari GUI wallet, Masari CLI wallet with the store-tx-info flag enabled (enabled by default) or the Masari web wallet (https://wallet.getmasari.org). Please be sure you can access the tx key as that would be required in case of a dispute.\nmasari-wallet-cli (use the command get_tx_key)\nmasari-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nMasari Web Wallet (goto Account -> transaction history and view details on your sent transaction)\n\nVerification can be accomplished in-wallet.\nmasari-wallet-cli : using command (check_tx_key).\nmasari-wallet-gui : on the Advanced > Prove/Check page.\nVerification can be accomplished in the block explorer \nOpen block explorer (https://explorer.getmasari.org), use the search bar to find your transaction hash.\nOnce transaction is found, scroll to bottom to the 'Prove Sending' area and fill in details as needed.\nYou need to provide the mediator or arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The MSR sender is responsible for providing verification of the MSR transfer to the mediator or arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process, ask for help on the Official Masari Discord (https://discord.gg/sMCwMqs).
 account.altcoin.popup.blur.msg=Trading BLUR on Bisq requires that you understand and fulfill the following requirements:\n\nTo send BLUR you must use the Blur Network CLI or GUI Wallet. \n\nIf you are using the CLI wallet, a transaction hash (tx ID) will be displayed after a transfer is sent. You must save this information. Immediately after sending the transfer, you must use the command 'get_tx_key' to retrieve the transaction private key. If you fail to perform this step, you may not be able to retrieve the key later. \n\nIf you are using the Blur Network GUI Wallet, the transaction private key and transaction ID can be found conveniently in the "History" tab.  Immediately after sending, locate the transaction of interest. Click the "?" symbol in the lower-right corner of the box containing the transaction. You must save this information. \n\nIn the event that arbitration is necessary, you must present the following to an mediator or arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address.  The mediator or arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nFailure to provide the required information to the mediator or arbitrator will result in losing the dispute case. In all cases of dispute, the BLUR sender bears 100% of the burden of responsibility in verifying transactions to an mediator or arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW).
@@ -1169,6 +1168,7 @@ dao.lockedForVoteBalance=Usado para votação
 dao.lockedInBonds=Bloqueado em vínculos
 dao.availableNonBsqBalance=Saldo não-BSQ disponível (BTC)
 dao.totalBsqBalance=Saldo total de BSQ
+dao.reputationBalance=Merit Value (not spendable)
 
 dao.tx.published.success=Sua transação foi publicada com sucesso.
 dao.proposal.menuItem.make=Fazer proposta
@@ -1582,7 +1582,7 @@ dao.proposal.create.publish=Publicar proposta
 dao.proposal.create.publishing=Publicação de proposta em progresso ...
 dao.proposal=proposta
 dao.proposal.display.type=Tipo de proposta
-dao.proposal.display.name=Exact GitHub username
+dao.proposal.display.name=Usuário no GitHub
 dao.proposal.display.link=Link para mais detalhes
 dao.proposal.display.link.prompt=Link para proposta
 dao.proposal.display.requestedBsq=Quantia requerida em BSQ
@@ -1891,7 +1891,7 @@ emptyWalletWindow.openOffers.warn=Você possui ofertas abertas que serão removi
 emptyWalletWindow.openOffers.yes=Sim, tenho certeza
 emptyWalletWindow.sent.success=O conteúdo da sua carteira foi transferido com sucesso.
 
-enterPrivKeyWindow.headline=Enter private key for registration
+enterPrivKeyWindow.headline=Insira a chave privada para o registro
 
 filterWindow.headline=Editar lista de filtragem
 filterWindow.offers=Ofertas filtradas (sep. por vírgula):
@@ -1961,7 +1961,7 @@ showWalletDataWindow.includePrivKeys=Incluir chaves privadas
 tacWindow.headline=Acordo de usuário
 tacWindow.agree=Eu concordo
 tacWindow.disagree=Eu não concordo e desisto
-tacWindow.arbitrationSystem=Sistema de arbitragem
+tacWindow.arbitrationSystem=Dispute resolution
 
 tradeDetailsWindow.headline=Negociação
 tradeDetailsWindow.disputedPayoutTxId=ID de transação do pagamento disputado:
@@ -2073,13 +2073,13 @@ popup.warning.trade.txRejected=The {0} transaction for trade with ID {1} was rej
 popup.warning.openOfferWithInvalidMakerFeeTx=The maker fee transaction for offer with ID {0} is invalid.\nTransaction ID={1}.\nPlease go to \"Settings/Network info\" and do a SPV resync.\nFor further help please contact the Bisq support channel at the Bisq Keybase team.
 
 popup.warning.trade.depositTxNull=The trade with ID {0} has no deposit transaction set.\nPlease restart the application and if the problem remains move the trade to failed trades and report the problem to the Bisq support channel at the Bisq Keybase team.
-popup.warning.trade.depositTxNull.moveToFailedTrades=Move to failed trades
+popup.warning.trade.depositTxNull.moveToFailedTrades=Mover para negociações com erro
 
 popup.info.securityDepositInfo=Para garantir que ambas as partes sigam o protocolo de negociação, tanto o vendedor quanto o comprador precisam fazer um depósito de segurança.\n\nEste depósito permanecerá em sua carteira local até que a negociação seja concluída com sucesso. Depois, ele será devolvido para você.\n\nAtenção: se você está criando uma nova oferta, é necessário que você mantenha o programa aberto, para que outro usuário possa aceitar a sua oferta. Para manter suas ofertas online, mantenha o Bisq sempre aberto e conectado à internet (por exemplo: verifique-se de que as funções de economia de energia do seu computador estão desativadas).
 
 popup.info.cashDepositInfo=Certifique-se de que você possui uma agência bancária em sua região para poder fazer o depósito em dinheiro.\nO ID (BIC/SWIFT) do banco do vendedor é: {0}.
 popup.info.cashDepositInfo.confirm=Eu confirmo que posso fazer o depósito
-popup.info.shutDownWithOpenOffers=O Bisq está desligando, mas há ofertas abertas.\n\nEstas ofertas não ficaram disponíveis na rede P2P enquanto o Bisq estiver desligado, mas elas serão republicadas na rede assim que você iniciar o programa.\n\nPara manter suas ofertas online, mantenha o Bisq aberto e certifique-se de que o seu computador continua online (ex: certifique-se de que o computador não está entrando em modo de hibernação).\n
+popup.info.shutDownWithOpenOffers=O Bisq está desligando, mas há ofertas abertas.\n\nEstas ofertas não ficarão disponíveis na rede P2P enquanto o Bisq estiver desligado, mas elas serão republicadas na rede assim que você reiniciar o programa.\n\nPara manter suas ofertas online, mantenha o Bisq aberto e certifique-se de que o seu computador continua online (ex: certifique-se de que o computador não está entrando em modo de hibernação).
 
 popup.privateNotification.headline=Notificação privada importante!
 
@@ -2099,10 +2099,10 @@ popup.info.multiplePaymentAccounts.msg=Você tem várias contas de pagamento dis
 popup.news.launch.headline=Duas Atualizações Importantes
 popup.news.launch.accountSigning.headline=ACCOUNT SIGNING
 popup.news.launch.accountSigning.description=Lift 0.01 BTC fiat trading limits by buying BTC from a signed peer.
-popup.news.launch.ntp.headline=NEW TRADE PROTOCOL
+popup.news.launch.ntp.headline=NOVO PROTOCOLO DE NEGOCIAÇÕES
 popup.news.launch.ntp.description=New 2-level dispute resolution system makes Bisq more secure, scalable, and censorship-resistant.
 
-popup.accountSigning.selectAccounts.headline=Select payment accounts
+popup.accountSigning.selectAccounts.headline=Selecionar contas de pagamento
 popup.accountSigning.selectAccounts.description=Based on the payment method and point of time all payment accounts that are connected to a dispute where a payout to the buyer occurred will be selected for you to sign.
 popup.accountSigning.selectAccounts.signAll=Sign all payment methods
 popup.accountSigning.selectAccounts.datePicker=Select point of time until which accounts will be signed
@@ -2152,7 +2152,7 @@ systemTray.show=Mostrar janela do applicativo
 systemTray.hide=Esconder janela do applicativo
 systemTray.info=Informações sobre Bisq
 systemTray.exit=Sair
-systemTray.tooltip=Bisq: A exchange descentralizada
+systemTray.tooltip=Bisq: A decentralized bitcoin exchange network
 
 
 ####################################################################
@@ -2250,7 +2250,7 @@ navigation.dao.wallet.receive=\"DAO/Carteira BSQ/Receber\"
 formatter.formatVolumeLabel={0} quantia{1}
 formatter.makerTaker=Ofertante: {1} de {0} / Aceitador: {3} de {2}
 formatter.youAreAsMaker=Você está {0} {1} como ofertante / Aceitador está {2} {3}
-formatter.youAreAsTaker=Você está {0} {1} como aceitador / Ofertante é {2} {3}
+formatter.youAreAsTaker=Você está {0} {1} como aceitador / Ofertante está {2} {3}
 formatter.youAre=Você está {0} {1} ({2} {3})
 formatter.youAreCreatingAnOffer.fiat=Você está criando uma oferta para {0} {1}
 formatter.youAreCreatingAnOffer.altcoin=Você está criando uma oferta para {0} {1} ({2} {3})
@@ -2398,7 +2398,7 @@ payment.accountType=Tipo de conta
 payment.checking=Conta Corrente
 payment.savings=Poupança
 payment.personalId=Identificação pessoal
-payment.clearXchange.info=Por favor certifique-se de que preenche os requisitos para o uso de Zelle (ClearXchange).\n\n1. Precisa de ter a sua conta Zelle (ClearXchange) verificada na sua plataforma antes de começar um negócio ou criar uma oferta.\n\n2. Precisa de ter uma conta bancária num dos seguintes bancos membros:\n● Bank of America\n● Capital One P2P Payments\n● Chase QuickPay\n● FirstBank Person to Person Transfers\n● Frost Send Money\n● U.S. Bank Send Money\n● TD Bank\n● Citibank\n● Wells Fargo SurePay\n\n3. Precisa de ter certeza de não exceder o limite diário ou mensal de transferência da Zelle (ClearXchange).\n\nPor favor use Zelle (ClearXchange) apenas se preencher todos esses requisitos, caso contrário é bastante provável que a transferência da Zelle (ClearXchange) falhe e o negócio acabe em disputa.\nSe não tiver preenchido todos os requisitos acima mencionados, perderá o depósito de segurança.\n\nPor favor, esteja ciente de um risco maior de estorno ao usar Zelle (ClearXchange).\nPara o vendedor {0}, é altamente recomendado entrar em contato com o comprador {1} usando o endereço de e-mail ou o número de telefone fornecido para confirmar se ele é realmente o proprietário da conta da Zelle (ClearXchange).
+payment.clearXchange.info=Por favor certifique-se de que preenche os requisitos para o uso de Zelle (ClearXchange).\n\n1. Precisa ter a sua conta Zelle (ClearXchange) verificada na sua plataforma antes de começar uma negociação ou criar uma oferta.\n\n2. Precisa ter uma conta bancária num dos seguintes bancos membros:\n● Bank of America\n● Capital One P2P Payments\n● Chase QuickPay\n● FirstBank Person to Person Transfers\n● Frost Send Money\n● U.S. Bank Send Money\n● TD Bank\n● Citibank\n● Wells Fargo SurePay\n\n3. Precisa ter certeza de não exceder o limite diário ou mensal de transferência da Zelle (ClearXchange).\n\nPor favor use Zelle (ClearXchange) apenas se preencher todos esses requisitos, caso contrário é bastante provável que a transferência da Zelle (ClearXchange) falhe e a negociação acabe em disputa.\nSe não tiver preenchido todos os requisitos acima mencionados, perderá o depósito de segurança.\n\nPor favor, esteja ciente de um risco maior de estorno ao usar Zelle (ClearXchange).\nPara o vendedor de {0}, é altamente recomendado entrar em contato com o comprador de {1} usando o endereço de e-mail ou o número de telefone fornecido para confirmar se ele é realmente o proprietário da conta da Zelle (ClearXchange).
 
 payment.moneyGram.info=Ao usar o MoneyGram, o comprador de BTC deve enviar o Número de Autorização e uma foto do recibo por e-mail ao vendedor de BTC. O recibo deve mostrar claramente o nome completo do vendedor, o país, o estado e a quantia. O comprador visualizará o e-mail do vendedor no processo de negócio.
 payment.westernUnion.info=Ao usar o Western Union, o comprador do BTC deve enviar o MTCN (número de rastreamento) e uma foto do recibo por e-mail ao vendedor de BTC. O recibo deve mostrar claramente o nome completo do vendedor, a cidade, o país e a quantia. O comprador visualizará o e-mail do vendedor no processo de negócio.
@@ -2426,7 +2426,7 @@ payment.f2f.offerbook.tooltip.countryAndCity=País e cidade: {0} / {1}
 payment.f2f.offerbook.tooltip.extra=Informações adicionais: {0}
 
 payment.japan.bank=Banco
-payment.japan.branch=Branch
+payment.japan.branch=Ramo
 payment.japan.account=Conta
 payment.japan.recipient=Nome
 
@@ -2435,7 +2435,7 @@ payment.japan.recipient=Nome
 
 # Only translate general terms
 NATIONAL_BANK=Transferência bancária nacional
-SAME_BANK=Tranferência para mesmo banco
+SAME_BANK=Transferência para mesmo banco
 SPECIFIC_BANKS=Transferência com bancos específicos
 US_POSTAL_MONEY_ORDER=US Postal Money Order
 CASH_DEPOSIT=Depósito em dinheiro (cash deposit)

core/src/main/resources/i18n/displayStrings_pt.properties

@@ -168,7 +168,7 @@ shared.payoutTxId=ID de transação de pagamento
 shared.contractAsJson=Contrato em formato JSON
 shared.viewContractAsJson=Ver contrato em formato JSON
 shared.contract.title=Contrato para negócio com ID: {0}
-shared.paymentDetails=Detalhes do pagamento de BTC {0}
+shared.paymentDetails=Detalhes do pagamento do {0} de BTC
 shared.securityDeposit=Depósito de segurança
 shared.yourSecurityDeposit=O seu depósito de segurança
 shared.contract=Contrato
@@ -274,7 +274,7 @@ mainView.p2pNetworkWarnMsg.connectionToP2PFailed=A conexão com a rede do Bisq f
 mainView.walletServiceErrorMsg.timeout=A conexão com a rede Bitcoin falhou por causa de tempo esgotado.
 mainView.walletServiceErrorMsg.connectionError=A conexão com a rede Bitcoin falhou devido ao erro: {0}
 
-mainView.walletServiceErrorMsg.rejectedTxException=A transaction was rejected from the network.\n\n{0}
+mainView.walletServiceErrorMsg.rejectedTxException=Uma transação foi rejeitada pela rede.\n\n{0}
 
 mainView.networkWarning.allConnectionsLost=Você perdeu a conexão com todos os pares de rede de {0} .\nTalvez você tenha perdido sua conexão de internet ou o seu computador estivesse no modo de espera.
 mainView.networkWarning.localhostBitcoinLost=Perdeu a conexão ao nó Bitcoin do localhost.\nPor favor recomeçar o programa do Bisq para conectar à outros nós Bitcoin ou recomeçar o nó Bitcoin do localhost.
@@ -672,7 +672,6 @@ portfolio.pending.step5_buyer.takersMiningFee=Total das taxas de mineração
 portfolio.pending.step5_buyer.refunded=Depósito de segurança reembolsado
 portfolio.pending.step5_buyer.withdrawBTC=Levantar seus bitcoins
 portfolio.pending.step5_buyer.amount=Quantia a levantar
-portfolio.pending.step5_buyer.signer=Ao levantar os seus bitcoins, você verifica se a contraparte agiu de acordo com o protocolo de negócio.
 portfolio.pending.step5_buyer.withdrawToAddress=Levantar para o endereço
 portfolio.pending.step5_buyer.moveToBisqWallet=Mover fundos para carteira Bisq
 portfolio.pending.step5_buyer.withdrawExternal=Levantar para carteira externa
@@ -873,7 +872,7 @@ support.sellerOfferer=Vendedor de BTC/Ofertante
 support.buyerTaker=Comprador de BTC/Aceitador
 support.sellerTaker=Vendedor de BTC/Aceitador
 
-support.backgroundInfo=Bisq não é uma empresa, por isso lida com disputas de maneira diferente.\n\nOs negociadores podem se comunicar dentro do programa através de um chat seguro no ecrã de negócios abertos para tentar resolver uma disputa por conta própria. Se isso não for suficiente, um mediador pode ajudar. O mediador avaliará a situação e fará uma recomendação para o pagamento dos fundos do negócio. Se ambos os negociadores aceitarem essa sugestão, a transação de pagamento será concluída e o negócio será encerrado. Se um ou ambos os negociadores não concordarem com o pagamento recomendado pelo mediador, eles podem solicitar a arbitragem. O árbitro tem a terceira chave da transação de depósito e fará o pagamento com base em suas conclusões.
+support.backgroundInfo=Bisq is not a company, so it handles disputes differently.\n\nTraders can communicate within the application via secure chat on the open trades screen to try solving disputes on their own. If that is not sufficient, a mediator can step in to help. The mediator will evaluate the situation and suggest a payout of trade funds. If both traders accept this suggestion, the payout transaction is completed and the trade is closed. If one or both traders do not agree to the mediator's suggested payout, they can request arbitration.The arbitrator will re-evaluate the situation and, if warranted, personally pay the trader back and request reimbursement for this payment from the Bisq DAO.
 support.initialInfo=Digite uma descrição do seu problema no campo de texto abaixo. Adicione o máximo de informações possível para acelerar o tempo de resolução da disputa.\n\nAqui está uma lista do que você deve fornecer:\n● Se você é o comprador de BTC: Você fez a transferência da Fiat ou Altcoin? Se sim, você clicou no botão 'pagamento iniciado' no programa?\n● Se você é o vendedor de BTC: Você recebeu o pagamento da Fiat ou Altcoin? Se sim, você clicou no botão 'pagamento recebido' no programa?\n\t● Qual versão do Bisq você está usando?\n\t● Qual sistema operacional você está usando?\n\t ● Se você encontrou um problema com transações com falha, considere mudar para um novo diretório de dados.\n\t Às vezes, o diretório de dados é corrompido e leva a erros estranhos.\n\t Consulte: https://docs.bisq.network/backup-recovery.html#switch-to-a-new-data-directory\n\nFamiliarize-se com as regras básicas do processo de disputa:\n\t● Você precisa responder às solicitações do {0} dentro de 2 dias.\n\t● Os mediadores respondem entre 2 dias. Os árbitros respondem dentro de 5 dias úteis.\n\t ● O período máximo para uma disputa é de 14 dias.\n\t ● Você precisa cooperar com o {1} e fornecer as informações solicitadas para justificar o seu caso.\n\t● Você aceitou as regras descritas no documento de disputa no contrato do usuário quando iniciou o programa.\n\nVocê pode ler mais sobre o processo de disputa em: {2}
 support.systemMsg=Mensagem do sistema: {0}
 support.youOpenedTicket=Você abriu um pedido para apoio.\n\n{0}\n\nBisq versão: {1}
@@ -1038,7 +1037,7 @@ account.altcoin.popup.wallet.msg=Certifique-se de seguir os requisitos para o us
 account.altcoin.popup.wallet.confirm=Eu entendo e confirmo que eu sei qual carteira que preciso usar.
 account.altcoin.popup.upx.msg=Negociar UPX no Bisq exige que você entenda e cumpra os seguintes requerimentos:\n\nPara enviar o UPX, você precisa usar a carteira GUI oficial do uPlexa ou a carteira CLI do uPlexa com o sinalizador store-tx-info ativado (padrão em novas versões). Certifique-se de que você pode acessar a chave da tx, pois isso seria necessário em caso de disputa.\nuplexa-wallet-cli (use o comando get_tx_key)\nuplexa-wallet-gui (vá para a aba do histoórico e clique no botão (P) para prova de pagamento)\n\nEm exploradores de blocos normais, a transferência não é verificável.\n\nVocê precisa fornecer ao árbitro os seguintes dados em caso de disputa:\n- A chave privada da tx\n- O hash da transação\n- Endereço público do destinatário\n\nA falha no fornecimento dos dados acima, ou se você usou uma carteira incompatível, resultará na perda do caso da disputa. O remetente de UPX é responsável por fornecer a verificação da transferência de UPX ao árbitro em caso de disputa.\n\nNão é necessário um ID de pagamento, apenas o endereço público normal.\nSe você não tiver certeza sobre esse processo, visite o canal de discord do uPlexa (https://discord.gg/vhdNSrV) ou o chat do Telegram do uPlexa (https://t.me/uplexaOfficial) para encontrar mais informações.
 account.altcoin.popup.arq.msg=Negociar o ARQ no Bisq requer que você entenda e atenda aos seguintes requerimentos:\n\nPara enviar o ARQ, você precisa usar a wallet oficial do ArQmA GUI ou a carteira do ArQmA CLI com o marcador store-tx-info ativado (padrão em novas versões). Por favor, certifique-se que você pode acessar a chave da tx porque isso seria necessário em caso de uma disputa.\narqma-wallet-cli (use o comando get_tx_key)\narqma-wallet-gui (vá para a aba do histórico e clique no botão (P) para comprovar o pagamento)\n\nEm exploradores de blocos normais, a transferência não é verificável.\n\nVocê precisa fornecer ao mediador ou árbitro os seguintes dados em caso de disputa:\n- A chave privada da tx\n- O hash da transação\n- o endereço público do destinatário\n\nA falha em fornecer os dados acima, ou se você usou uma carteira incompatível, resultará na perda do caso de disputa. O remetente do ARQ é responsável por fornecer a verificação da transferência do ARQ ao mediador ou árbitro em caso de disputa.\n\nNão é necessário um código de pagamento, apenas o endereço público normal.\nSe você não tiver certeza sobre esse processo, visite o canal de discord do ArQmA (https://discord.gg/s9BQpJT) ou o fórum do ArQmA (https://labs.arqma.com) para obter mais informações.
-account.altcoin.popup.xmr.msg=Negociar XMR no Bisq requer que você entenda e cumpra os seguintes requerimentos:\n\nPara enviar o XMR, você precisa usar a carteira oficial Monero GUI ou a carteira Monero CLI com o marcador store-tx-info ativado (padrão em novas versões). Por favor, certifique-se que você pode acessar a chave da tx porque isso seria necessário em caso de uma disputa.\nmonero-wallet-cli (use o comando get_tx_key)\nmonero-wallet-gui (vá para a aba do histórico e clique no botão (P) para comprovar o pagamento)\n\nAlém da ferramenta checktx XMR (https://xmr.llcoins.net/checktx.html), a verificação também pode ser realizada na carteira.\nmonero-wallet-cli: usando o comando (check_tx_key).\nmonero-wallet-gui: na página Advanced> Prove / Check.\nEm exploradores de blocos normais, a transferência não é verificável.\n\nVocê precisa fornecer ao mediador ou árbitro os seguintes dados em caso de disputa:\n- A chave privada da tx\n- O hash da transação\n- o endereço público do destinatário\n\nFalha em fornecer os dados acima, ou se você usou uma carteira incompatível, resultará na perda do caso de disputa. O remetente da XMR é responsável por fornecer a verificação da transferência da XMR para o mediador ou o árbitro no caso de uma disputa.\n\nNão é necessário um código de pagamento, apenas o endereço público normal.\nSe você não tem certeza sobre o processo visite (https://www.getmonero.org/resources/user-guides/prove-payment.html) ou o fórum Monero (https://forum.getmonero.org) para encontrar mais informação.
+account.altcoin.popup.xmr.msg=Trading XMR on Bisq requires that you understand and fulfill the following requirements:\n\nProve payments: since Monero is a private coin, some transaction details aren't publicly available in the blockchain, and, in case of a dispute, the mediator or arbitrator needs them to check if the transaction was really made. In Bisq, the sender of the XMR transaction is the one responsible for providing this information to the mediator or arbitrator in case of a dispute. In order to do that, you must send XMR using a wallet that provides the information required to prove the payment was made, which includes:\n\n- the transaction key (Tx Key, Tx Secret Key or Tx Private Key)\n- the transaction ID (Tx ID or Tx Hash)\n- the destination address (recipient's address)\n\nThis information can be found in the official Monero GUI & CLI wallets, MyMonero, and Exodus (desktop) as well as in Cake Wallet, MyMonero, and Monerujo (mobile), in the following locations:\n\n- Monero GUI: go to Transactions tab\n- Monero CLI: use the command get_tx_key TXID. The flag store-tx-info must be enabled (enabled by default in new versions)\n- Other wallets: go to Transactions history and search for Transaction key (Tx key or Secret key) and the destination address in a sent transaction. Save recipient address option must be enabled in Cake Wallet settings.\n\nIf you are using a wallet different from the mentioned above, please be sure you can access those three pieces of information.Since the transaction key and the destination address are stored in the Monero wallet software, and they cannot be recovered in the Monero blockchain, you should never delete or restore your Monero wallet before a Bisq trade is completed. Failure to provide the above data will result in losing the dispute case.\n\nCheck payments: with those three pieces of information, the verification that a quantity of Monero was sent to a specific address can be accomplished the following way:\n\n- Monero GUI: change wallet to Advanced mode and go to Advanced > Prove/check > Check Transaction\n- Monero CLI: use the command check_tx_key TXID TXKEY ADDRESS\n- XMR checktx tool (https://xmr.llcoins.net/checktx.html)\n- Explore Monero website (https://www.exploremonero.com/receipt)\n\nIf you are still not sure about this process, visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) to find more information or ask a question on the Monero support subreddit (https://www.reddit.com/r/monerosupport/).
 # suppress inspection "TrailingSpacesInProperty"
 account.altcoin.popup.msr.msg=Negociar MSR no Bisq requer que você entenda e cumpra os seguintes requerimentos:\n\nPara enviar MSR, você precisa usar a carteira GUI oficial do Masari ou a carteira CLI do Masari com o marcador store-tx-info ativado (ativado por padrão) ou a carteira web do Masari (https://wallet.getmasari.org). Por favor, certifique-se que você pode acessar a chave da tx porque isso seria necessário em caso de uma disputa.\nmasari-wallet-cli (use o comando get_tx_key)\nmasari-wallet-gui (vá para a aba do histórico e clique no botão (P) para comprovar o pagamento)\n\nMasari Web Wallet (vá para Account -> histórico de transação e veja os detalhes da sua transação enviada)\n\nA verificação pode ser realizada na carteira.\nmasari-wallet-cli: usando o comando (check_tx_key).\nmasari-wallet-gui: na aba Advanced > Prove/Check.\nA verificação pode ser realizada no eplorador de blocos\nExplorador de blocos aberto (https://explorer.getmasari.org), use a barra de procurar para encontrar o hash da transação.\nUma que vez que a transação for encontrada, desça até ao baixo da àrea 'Prove Sending' e preencha os detalhes necessários.\nVocê precisa fornecer ao mediador ou ao árbitro os seguintes dados em caso de disputa:\n- A chave privada da tx\n- O hash da transação\n- o endereço público do destinatário\n\nFalha em fornecer os dados acima, ou se você usou uma carteira incompatível, resultará na perda do caso de disputa. O remetente da XMR é responsável por fornecer a verificação da transferência da MSR para o mediador ou o árbitro no caso de uma disputa.\n\nNão é necessário um código de pagamento, apenas o endereço público normal.\nSe você não tem certeza sobre o processo, peça ajuda no Discord official do Masari (https://discord.gg/sMCwMqs).
 account.altcoin.popup.blur.msg=Negociar o BLUR no Bisq requer que você entenda e cumpra os seguintes requerimentos:\n\nPara enviar o BLUR você deve usar a carteira CLI da Blur Network ou a carteira GUI.\n\nSe você estiver usando a carteira CLI, um hash da transação (tx ID) será exibido após uma transferência ser enviada. Você deve guardar esta informação. Imediatamente após o envio da transferência, você deve usar o comando 'get_tx_key' para recuperar a chave privada da transação. Se você não conseguir executar essa etapa, talvez não consiga recuperar a chave mais tarde.\n\nSe você estiver usando a carteira GUI do Blur Network, a chave privada da transação e a ID da transação podem ser encontradas convenientemente na aba "Histórico". Imediatamente após o envio, localize a transação de interesse. Clique no símbolo "?" no canto inferior direito da caixa que contém a transação. Você deve guardar esta informação.\n\nCaso a arbitragem seja necessária, você deve apresentar o seguinte à um mediador ou árbitro: 1.) a ID da transação, 2.) a chave privada da transação e 3.) o endereço do destinatário. O mediador ou árbitro verificará a transferência do BLUR usando o Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nO não fornecimento das informações necessárias ao mediador ou árbitro resultará na perda da disputa. Em todos os casos de disputa, o remetente de BLUR tem 100% de responsabilidade na verificação de transações para um mediador ou árbitro.\n\nSe você não entender esses requerimentos não negocie no Bisq. Primeiro, procure ajuda no Discord da Rede de Blur (https://discord.gg/dMWaqVW).
@@ -1169,6 +1168,7 @@ dao.lockedForVoteBalance=Usado para votação
 dao.lockedInBonds=Bloqueado em vínculos
 dao.availableNonBsqBalance=Balanço não-BSQ disponível (BTC)
 dao.totalBsqBalance=Saldo total de BSQ
+dao.reputationBalance=Merit Value (not spendable)
 
 dao.tx.published.success=Sua transação foi publicada com sucesso.
 dao.proposal.menuItem.make=Criar proposta
@@ -1961,7 +1961,7 @@ showWalletDataWindow.includePrivKeys=Incluir chaves privadas
 tacWindow.headline=Acordo de utilizador
 tacWindow.agree=Eu concordo
 tacWindow.disagree=Eu não concordo e desisto
-tacWindow.arbitrationSystem=Sistema de arbitragem
+tacWindow.arbitrationSystem=Dispute resolution
 
 tradeDetailsWindow.headline=Negócio
 tradeDetailsWindow.disputedPayoutTxId=ID de transação do pagamento disputado:
@@ -2066,8 +2066,8 @@ popup.warning.burnBTC=Esta transação não é possível, pois as taxas de miner
 
 popup.warning.openOffer.makerFeeTxRejected=The maker fee transaction for offer with ID {0} was rejected by the Bitcoin network.\nTransaction ID={1}.\nThe offer has been removed to avoid further problems.\nPlease go to \"Settings/Network info\" and do a SPV resync.\nFor further help please contact the Bisq support channel at the Bisq Keybase team.
 
-popup.warning.trade.txRejected.tradeFee=trade fee
-popup.warning.trade.txRejected.deposit=deposit
+popup.warning.trade.txRejected.tradeFee=taxa de negócio
+popup.warning.trade.txRejected.deposit=depósito
 popup.warning.trade.txRejected=The {0} transaction for trade with ID {1} was rejected by the Bitcoin network.\nTransaction ID={2}}\nThe trade has been moved to failed trades.\nPlease go to \"Settings/Network info\" and do a SPV resync.\nFor further help please contact the Bisq support channel at the Bisq Keybase team.
 
 popup.warning.openOfferWithInvalidMakerFeeTx=The maker fee transaction for offer with ID {0} is invalid.\nTransaction ID={1}.\nPlease go to \"Settings/Network info\" and do a SPV resync.\nFor further help please contact the Bisq support channel at the Bisq Keybase team.
@@ -2152,7 +2152,7 @@ systemTray.show=Mostrar janela do programa
 systemTray.hide=Esconder janela do programa
 systemTray.info=Informação sobre Bisq
 systemTray.exit=Sair
-systemTray.tooltip=Bisq: A rede de mercado de câmbio descentralizada
+systemTray.tooltip=Bisq: A decentralized bitcoin exchange network
 
 
 ####################################################################
@@ -2250,7 +2250,7 @@ navigation.dao.wallet.receive=\"OAD/Carteira BSQ/Receber\"
 formatter.formatVolumeLabel={0} quantia{1}
 formatter.makerTaker=Ofertante como {0} {1} / Aceitador como {2} {3}
 formatter.youAreAsMaker=Você está {0} {1} como ofertante / Aceitador está {2} {3}
-formatter.youAreAsTaker=Você está {0} {1} como aceitador / Ofetante é {2} {3}
+formatter.youAreAsTaker=Você está {0} {1} como aceitador / Ofertante está {2} {3}
 formatter.youAre=Você é {0} {1} ({2} {3})
 formatter.youAreCreatingAnOffer.fiat=Você está criando uma oferta para {0} {1}
 formatter.youAreCreatingAnOffer.altcoin=Você está criando uma oferta para {0} {1} ({2} {3})
@@ -2435,7 +2435,7 @@ payment.japan.recipient=Nome
 
 # Only translate general terms
 NATIONAL_BANK=Transferência bancária nacional
-SAME_BANK=Tranferência para mesmo banco
+SAME_BANK=Transferência para mesmo banco
 SPECIFIC_BANKS=Transferência com banco escpecífico
 US_POSTAL_MONEY_ORDER=US Postal Money Order
 CASH_DEPOSIT=Depósito em dinheiro

core/src/main/resources/i18n/displayStrings_ru.properties

@@ -672,7 +672,6 @@ portfolio.pending.step5_buyer.takersMiningFee=Oбщая комиссия май
 portfolio.pending.step5_buyer.refunded=Сумма возмещённого залога
 portfolio.pending.step5_buyer.withdrawBTC=Вывести биткойны
 portfolio.pending.step5_buyer.amount=Сумма для вывода
-portfolio.pending.step5_buyer.signer=By withdrawing your bitcoins, you verify that the counterparty has acted according to the trade protocol.
 portfolio.pending.step5_buyer.withdrawToAddress=Вывести на адрес
 portfolio.pending.step5_buyer.moveToBisqWallet=Перевести средства в кошелёк Bisq
 portfolio.pending.step5_buyer.withdrawExternal=Вывести на внешний кошелёк
@@ -873,7 +872,7 @@ support.sellerOfferer=Продавец ВТС/мейкер
 support.buyerTaker=Покупатель ВТС/тейкер
 support.sellerTaker=Продавец BTC/тейкер
 
-support.backgroundInfo=Bisq is not a company, so it handles disputes differently.\n\nTraders can communicate within the application via a secure chat on the open trades screen to attempt solving a dispute on their own. If that is not sufficient, a mediator can step in to help. The mediator will evaluate the situation and give a recommendation for the payout of the trade funds. If both traders accept this suggestion, the payout transaction is completed and the trade is closed. If one or both traders do not agree to the mediator's recommended payout, they can request arbitration.The arbitrator has the third key of the deposit transaction and will make the payout based on their findings.
+support.backgroundInfo=Bisq is not a company, so it handles disputes differently.\n\nTraders can communicate within the application via secure chat on the open trades screen to try solving disputes on their own. If that is not sufficient, a mediator can step in to help. The mediator will evaluate the situation and suggest a payout of trade funds. If both traders accept this suggestion, the payout transaction is completed and the trade is closed. If one or both traders do not agree to the mediator's suggested payout, they can request arbitration.The arbitrator will re-evaluate the situation and, if warranted, personally pay the trader back and request reimbursement for this payment from the Bisq DAO.
 support.initialInfo=Please enter a description of your problem in the text field below. Add as much information as possible to speed up dispute resolution time.\n\nHere is a check list for information you should provide:\n\t● If you are the BTC buyer: Did you make the Fiat or Altcoin transfer? If so, did you click the 'payment started' button in the application?\n\t● If you are the BTC seller: Did you receive the Fiat or Altcoin payment? If so, did you click the 'payment received' button in the application?\n\t● Which version of Bisq are you using?\n\t● Which operating system are you using?\n\t● If you encountered an issue with failed transactions please consider switching to a new data directory.\n\t  Sometimes the data directory gets corrupted and leads to strange bugs. \n\t  See: https://docs.bisq.network/backup-recovery.html#switch-to-a-new-data-directory\n\nPlease make yourself familiar with the basic rules for the dispute process:\n\t● You need to respond to the {0}''s requests within 2 days.\n\t● Mediators respond in between 2 days. Arbitrators respond in between 5 business days.\n\t● The maximum period for a dispute is 14 days.\n\t● You need to cooperate with the {1} and provide the information they request to make your case.\n\t● You accepted the rules outlined in the dispute document in the user agreement when you first started the application.\n\nYou can read more about the dispute process at: {2}
 support.systemMsg=Системное сообщение: {0}
 support.youOpenedTicket=Вы запросили поддержку.\n\n{0}\n\nВерсия Bisq: {1}
@@ -1038,7 +1037,7 @@ account.altcoin.popup.wallet.msg=Please be sure that you follow the requirements
 account.altcoin.popup.wallet.confirm=Я понимаю и подтверждаю, что знаю, какой кошелёк нужно использовать.
 account.altcoin.popup.upx.msg=Trading UPX on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending UPX, you need to use either the official uPlexa GUI wallet or uPlexa CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nuplexa-wallet-cli (use the command get_tx_key)\nuplexa-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The UPX sender is responsible for providing verification of the UPX transfer to the arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit uPlexa discord channel (https://discord.gg/vhdNSrV) or the uPlexa Telegram Chat (https://t.me/uplexaOfficial) to find more information.
 account.altcoin.popup.arq.msg=Trading ARQ on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending ARQ, you need to use either the official ArQmA GUI wallet or ArQmA CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\narqma-wallet-cli (use the command get_tx_key)\narqma-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the mediator or arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The ARQ sender is responsible for providing verification of the ARQ transfer to the mediator or arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit ArQmA discord channel (https://discord.gg/s9BQpJT) or the ArQmA forum (https://labs.arqma.com) to find more information.
-account.altcoin.popup.xmr.msg=Trading XMR on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending XMR, you need to use either the official Monero GUI wallet or Monero CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nmonero-wallet-cli (use the command get_tx_key)\nmonero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nIn addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\nmonero-wallet-cli : using command (check_tx_key).\nmonero-wallet-gui : on the Advanced > Prove/Check page.\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the mediator or arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The XMR sender is responsible for providing verification of the XMR transfer to the mediator or arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) or the Monero forum (https://forum.getmonero.org) to find more information.
+account.altcoin.popup.xmr.msg=Trading XMR on Bisq requires that you understand and fulfill the following requirements:\n\nProve payments: since Monero is a private coin, some transaction details aren't publicly available in the blockchain, and, in case of a dispute, the mediator or arbitrator needs them to check if the transaction was really made. In Bisq, the sender of the XMR transaction is the one responsible for providing this information to the mediator or arbitrator in case of a dispute. In order to do that, you must send XMR using a wallet that provides the information required to prove the payment was made, which includes:\n\n- the transaction key (Tx Key, Tx Secret Key or Tx Private Key)\n- the transaction ID (Tx ID or Tx Hash)\n- the destination address (recipient's address)\n\nThis information can be found in the official Monero GUI & CLI wallets, MyMonero, and Exodus (desktop) as well as in Cake Wallet, MyMonero, and Monerujo (mobile), in the following locations:\n\n- Monero GUI: go to Transactions tab\n- Monero CLI: use the command get_tx_key TXID. The flag store-tx-info must be enabled (enabled by default in new versions)\n- Other wallets: go to Transactions history and search for Transaction key (Tx key or Secret key) and the destination address in a sent transaction. Save recipient address option must be enabled in Cake Wallet settings.\n\nIf you are using a wallet different from the mentioned above, please be sure you can access those three pieces of information.Since the transaction key and the destination address are stored in the Monero wallet software, and they cannot be recovered in the Monero blockchain, you should never delete or restore your Monero wallet before a Bisq trade is completed. Failure to provide the above data will result in losing the dispute case.\n\nCheck payments: with those three pieces of information, the verification that a quantity of Monero was sent to a specific address can be accomplished the following way:\n\n- Monero GUI: change wallet to Advanced mode and go to Advanced > Prove/check > Check Transaction\n- Monero CLI: use the command check_tx_key TXID TXKEY ADDRESS\n- XMR checktx tool (https://xmr.llcoins.net/checktx.html)\n- Explore Monero website (https://www.exploremonero.com/receipt)\n\nIf you are still not sure about this process, visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) to find more information or ask a question on the Monero support subreddit (https://www.reddit.com/r/monerosupport/).
 # suppress inspection "TrailingSpacesInProperty"
 account.altcoin.popup.msr.msg=Trading MSR on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending MSR, you need to use either the official Masari GUI wallet, Masari CLI wallet with the store-tx-info flag enabled (enabled by default) or the Masari web wallet (https://wallet.getmasari.org). Please be sure you can access the tx key as that would be required in case of a dispute.\nmasari-wallet-cli (use the command get_tx_key)\nmasari-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nMasari Web Wallet (goto Account -> transaction history and view details on your sent transaction)\n\nVerification can be accomplished in-wallet.\nmasari-wallet-cli : using command (check_tx_key).\nmasari-wallet-gui : on the Advanced > Prove/Check page.\nVerification can be accomplished in the block explorer \nOpen block explorer (https://explorer.getmasari.org), use the search bar to find your transaction hash.\nOnce transaction is found, scroll to bottom to the 'Prove Sending' area and fill in details as needed.\nYou need to provide the mediator or arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The MSR sender is responsible for providing verification of the MSR transfer to the mediator or arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process, ask for help on the Official Masari Discord (https://discord.gg/sMCwMqs).
 account.altcoin.popup.blur.msg=Trading BLUR on Bisq requires that you understand and fulfill the following requirements:\n\nTo send BLUR you must use the Blur Network CLI or GUI Wallet. \n\nIf you are using the CLI wallet, a transaction hash (tx ID) will be displayed after a transfer is sent. You must save this information. Immediately after sending the transfer, you must use the command 'get_tx_key' to retrieve the transaction private key. If you fail to perform this step, you may not be able to retrieve the key later. \n\nIf you are using the Blur Network GUI Wallet, the transaction private key and transaction ID can be found conveniently in the "History" tab.  Immediately after sending, locate the transaction of interest. Click the "?" symbol in the lower-right corner of the box containing the transaction. You must save this information. \n\nIn the event that arbitration is necessary, you must present the following to an mediator or arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address.  The mediator or arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nFailure to provide the required information to the mediator or arbitrator will result in losing the dispute case. In all cases of dispute, the BLUR sender bears 100% of the burden of responsibility in verifying transactions to an mediator or arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW).
@@ -1169,6 +1168,7 @@ dao.lockedForVoteBalance=Использовано для голосования
 dao.lockedInBonds=Заблокировано в гарантийных депозитах
 dao.availableNonBsqBalance=Доступный баланс в ВТС (без учёта BSQ)
 dao.totalBsqBalance=Общий баланс BSQ
+dao.reputationBalance=Merit Value (not spendable)
 
 dao.tx.published.success=Ваша транзакция опубликована.
 dao.proposal.menuItem.make=Выступить с предложением
@@ -1961,7 +1961,7 @@ showWalletDataWindow.includePrivKeys=Добавить приватные клю
 tacWindow.headline=Пользовательское соглашение
 tacWindow.agree=Подтверждаю
 tacWindow.disagree=Не согласен (-сна) и выхожу
-tacWindow.arbitrationSystem=Арбитражная система
+tacWindow.arbitrationSystem=Dispute resolution
 
 tradeDetailsWindow.headline=Сделка
 tradeDetailsWindow.disputedPayoutTxId=Идент. оспоренной транзакции выплаты:
@@ -2152,7 +2152,7 @@ systemTray.show=Показать окно приложения
 systemTray.hide=Скрыть окно приложения
 systemTray.info=Информация о Bisq
 systemTray.exit=Выход
-systemTray.tooltip=Bisq: децентрализованная биржа криптовалюты
+systemTray.tooltip=Bisq: A decentralized bitcoin exchange network
 
 
 ####################################################################

core/src/main/resources/i18n/displayStrings_th.properties

@@ -672,7 +672,6 @@ portfolio.pending.step5_buyer.takersMiningFee=ยอดรวมค่าธร
 portfolio.pending.step5_buyer.refunded=เงินประกันความปลอดภัยที่ถูกคืน
 portfolio.pending.step5_buyer.withdrawBTC=ถอนเงิน bitcoin ของคุณ
 portfolio.pending.step5_buyer.amount=จำนวนเงินที่จะถอน
-portfolio.pending.step5_buyer.signer=By withdrawing your bitcoins, you verify that the counterparty has acted according to the trade protocol.
 portfolio.pending.step5_buyer.withdrawToAddress=ถอนไปยังที่อยู่
 portfolio.pending.step5_buyer.moveToBisqWallet=ย้ายเงินไปที่ Bisq wallet
 portfolio.pending.step5_buyer.withdrawExternal=ถอนไปยัง wallet ภายนอก
@@ -873,7 +872,7 @@ support.sellerOfferer= BTC ผู้ขาย/ ผู้สร้าง
 support.buyerTaker=BTC ผู้ซื้อ / ผู้รับ
 support.sellerTaker=BTC ผู้ขาย / ผู้รับ
 
-support.backgroundInfo=Bisq is not a company, so it handles disputes differently.\n\nTraders can communicate within the application via a secure chat on the open trades screen to attempt solving a dispute on their own. If that is not sufficient, a mediator can step in to help. The mediator will evaluate the situation and give a recommendation for the payout of the trade funds. If both traders accept this suggestion, the payout transaction is completed and the trade is closed. If one or both traders do not agree to the mediator's recommended payout, they can request arbitration.The arbitrator has the third key of the deposit transaction and will make the payout based on their findings.
+support.backgroundInfo=Bisq is not a company, so it handles disputes differently.\n\nTraders can communicate within the application via secure chat on the open trades screen to try solving disputes on their own. If that is not sufficient, a mediator can step in to help. The mediator will evaluate the situation and suggest a payout of trade funds. If both traders accept this suggestion, the payout transaction is completed and the trade is closed. If one or both traders do not agree to the mediator's suggested payout, they can request arbitration.The arbitrator will re-evaluate the situation and, if warranted, personally pay the trader back and request reimbursement for this payment from the Bisq DAO.
 support.initialInfo=Please enter a description of your problem in the text field below. Add as much information as possible to speed up dispute resolution time.\n\nHere is a check list for information you should provide:\n\t● If you are the BTC buyer: Did you make the Fiat or Altcoin transfer? If so, did you click the 'payment started' button in the application?\n\t● If you are the BTC seller: Did you receive the Fiat or Altcoin payment? If so, did you click the 'payment received' button in the application?\n\t● Which version of Bisq are you using?\n\t● Which operating system are you using?\n\t● If you encountered an issue with failed transactions please consider switching to a new data directory.\n\t  Sometimes the data directory gets corrupted and leads to strange bugs. \n\t  See: https://docs.bisq.network/backup-recovery.html#switch-to-a-new-data-directory\n\nPlease make yourself familiar with the basic rules for the dispute process:\n\t● You need to respond to the {0}''s requests within 2 days.\n\t● Mediators respond in between 2 days. Arbitrators respond in between 5 business days.\n\t● The maximum period for a dispute is 14 days.\n\t● You need to cooperate with the {1} and provide the information they request to make your case.\n\t● You accepted the rules outlined in the dispute document in the user agreement when you first started the application.\n\nYou can read more about the dispute process at: {2}
 support.systemMsg=ระบบข้อความ: {0}
 support.youOpenedTicket=You opened a request for support.\n\n{0}\n\nBisq version: {1}
@@ -1038,7 +1037,7 @@ account.altcoin.popup.wallet.msg=Please be sure that you follow the requirements
 account.altcoin.popup.wallet.confirm=ฉันเข้าใจและยืนยันว่าฉันรู้ว่า wallet ใดที่ฉันต้องการใช้
 account.altcoin.popup.upx.msg=Trading UPX on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending UPX, you need to use either the official uPlexa GUI wallet or uPlexa CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nuplexa-wallet-cli (use the command get_tx_key)\nuplexa-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The UPX sender is responsible for providing verification of the UPX transfer to the arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit uPlexa discord channel (https://discord.gg/vhdNSrV) or the uPlexa Telegram Chat (https://t.me/uplexaOfficial) to find more information.
 account.altcoin.popup.arq.msg=Trading ARQ on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending ARQ, you need to use either the official ArQmA GUI wallet or ArQmA CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\narqma-wallet-cli (use the command get_tx_key)\narqma-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the mediator or arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The ARQ sender is responsible for providing verification of the ARQ transfer to the mediator or arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit ArQmA discord channel (https://discord.gg/s9BQpJT) or the ArQmA forum (https://labs.arqma.com) to find more information.
-account.altcoin.popup.xmr.msg=Trading XMR on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending XMR, you need to use either the official Monero GUI wallet or Monero CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nmonero-wallet-cli (use the command get_tx_key)\nmonero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nIn addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\nmonero-wallet-cli : using command (check_tx_key).\nmonero-wallet-gui : on the Advanced > Prove/Check page.\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the mediator or arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The XMR sender is responsible for providing verification of the XMR transfer to the mediator or arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) or the Monero forum (https://forum.getmonero.org) to find more information.
+account.altcoin.popup.xmr.msg=Trading XMR on Bisq requires that you understand and fulfill the following requirements:\n\nProve payments: since Monero is a private coin, some transaction details aren't publicly available in the blockchain, and, in case of a dispute, the mediator or arbitrator needs them to check if the transaction was really made. In Bisq, the sender of the XMR transaction is the one responsible for providing this information to the mediator or arbitrator in case of a dispute. In order to do that, you must send XMR using a wallet that provides the information required to prove the payment was made, which includes:\n\n- the transaction key (Tx Key, Tx Secret Key or Tx Private Key)\n- the transaction ID (Tx ID or Tx Hash)\n- the destination address (recipient's address)\n\nThis information can be found in the official Monero GUI & CLI wallets, MyMonero, and Exodus (desktop) as well as in Cake Wallet, MyMonero, and Monerujo (mobile), in the following locations:\n\n- Monero GUI: go to Transactions tab\n- Monero CLI: use the command get_tx_key TXID. The flag store-tx-info must be enabled (enabled by default in new versions)\n- Other wallets: go to Transactions history and search for Transaction key (Tx key or Secret key) and the destination address in a sent transaction. Save recipient address option must be enabled in Cake Wallet settings.\n\nIf you are using a wallet different from the mentioned above, please be sure you can access those three pieces of information.Since the transaction key and the destination address are stored in the Monero wallet software, and they cannot be recovered in the Monero blockchain, you should never delete or restore your Monero wallet before a Bisq trade is completed. Failure to provide the above data will result in losing the dispute case.\n\nCheck payments: with those three pieces of information, the verification that a quantity of Monero was sent to a specific address can be accomplished the following way:\n\n- Monero GUI: change wallet to Advanced mode and go to Advanced > Prove/check > Check Transaction\n- Monero CLI: use the command check_tx_key TXID TXKEY ADDRESS\n- XMR checktx tool (https://xmr.llcoins.net/checktx.html)\n- Explore Monero website (https://www.exploremonero.com/receipt)\n\nIf you are still not sure about this process, visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) to find more information or ask a question on the Monero support subreddit (https://www.reddit.com/r/monerosupport/).
 # suppress inspection "TrailingSpacesInProperty"
 account.altcoin.popup.msr.msg=Trading MSR on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending MSR, you need to use either the official Masari GUI wallet, Masari CLI wallet with the store-tx-info flag enabled (enabled by default) or the Masari web wallet (https://wallet.getmasari.org). Please be sure you can access the tx key as that would be required in case of a dispute.\nmasari-wallet-cli (use the command get_tx_key)\nmasari-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nMasari Web Wallet (goto Account -> transaction history and view details on your sent transaction)\n\nVerification can be accomplished in-wallet.\nmasari-wallet-cli : using command (check_tx_key).\nmasari-wallet-gui : on the Advanced > Prove/Check page.\nVerification can be accomplished in the block explorer \nOpen block explorer (https://explorer.getmasari.org), use the search bar to find your transaction hash.\nOnce transaction is found, scroll to bottom to the 'Prove Sending' area and fill in details as needed.\nYou need to provide the mediator or arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The MSR sender is responsible for providing verification of the MSR transfer to the mediator or arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process, ask for help on the Official Masari Discord (https://discord.gg/sMCwMqs).
 account.altcoin.popup.blur.msg=Trading BLUR on Bisq requires that you understand and fulfill the following requirements:\n\nTo send BLUR you must use the Blur Network CLI or GUI Wallet. \n\nIf you are using the CLI wallet, a transaction hash (tx ID) will be displayed after a transfer is sent. You must save this information. Immediately after sending the transfer, you must use the command 'get_tx_key' to retrieve the transaction private key. If you fail to perform this step, you may not be able to retrieve the key later. \n\nIf you are using the Blur Network GUI Wallet, the transaction private key and transaction ID can be found conveniently in the "History" tab.  Immediately after sending, locate the transaction of interest. Click the "?" symbol in the lower-right corner of the box containing the transaction. You must save this information. \n\nIn the event that arbitration is necessary, you must present the following to an mediator or arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address.  The mediator or arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nFailure to provide the required information to the mediator or arbitrator will result in losing the dispute case. In all cases of dispute, the BLUR sender bears 100% of the burden of responsibility in verifying transactions to an mediator or arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW).
@@ -1169,6 +1168,7 @@ dao.lockedForVoteBalance=ถูกใช้สำหรับการโหว
 dao.lockedInBonds=ถูกล็อคไว้ในการค้ำประกัน
 dao.availableNonBsqBalance=ยอดคงเหลือที่ไม่ใช่ BSQ (BTC) ซึ่งใช้งานได้
 dao.totalBsqBalance=ยอด BSQ คงเหลือทั้งหมด
+dao.reputationBalance=Merit Value (not spendable)
 
 dao.tx.published.success=การทำธุรกรรมของคุณได้รับการเผยแพร่เรียบร้อยแล้ว
 dao.proposal.menuItem.make=เสนอคำขอ
@@ -1961,7 +1961,7 @@ showWalletDataWindow.includePrivKeys=รวมคีย์ส่วนตัว
 tacWindow.headline=ข้อตกลงการใช้
 tacWindow.agree=ฉันเห็นด้วย
 tacWindow.disagree=ฉันไม่เห็นด้วยและออก
-tacWindow.arbitrationSystem=ระบบอนุญาโตตุลาการ (การไกล่เกลี่ยข้อพิพาท)
+tacWindow.arbitrationSystem=Dispute resolution
 
 tradeDetailsWindow.headline=ซื้อขาย
 tradeDetailsWindow.disputedPayoutTxId=รหัส ID ธุรกรรมการจ่ายเงินที่พิพาท:
@@ -2152,7 +2152,7 @@ systemTray.show=แสดงหน้าต่างแอ็พพลิเค
 systemTray.hide=ซ่อนหน้าต่างแอ็พพลิเคชั่น
 systemTray.info=ข้อมูลเกี่ยวกับ Bisq
 systemTray.exit=ออก
-systemTray.tooltip=Bisq: เครือข่ายการแลกเปลี่ยนแบบกระจายอำนาจ
+systemTray.tooltip=Bisq: A decentralized bitcoin exchange network
 
 
 ####################################################################

core/src/main/resources/i18n/displayStrings_vi.properties

@@ -672,7 +672,6 @@ portfolio.pending.step5_buyer.takersMiningFee=Tổng phí đào
 portfolio.pending.step5_buyer.refunded=tiền gửi đặt cọc được hoàn lại
 portfolio.pending.step5_buyer.withdrawBTC=Rút bitcoin của bạn
 portfolio.pending.step5_buyer.amount=Số tiền được rút
-portfolio.pending.step5_buyer.signer=By withdrawing your bitcoins, you verify that the counterparty has acted according to the trade protocol.
 portfolio.pending.step5_buyer.withdrawToAddress=rút tới địa chỉ
 portfolio.pending.step5_buyer.moveToBisqWallet=Chuyển tiền tới ví Bisq
 portfolio.pending.step5_buyer.withdrawExternal=rút tới ví ngoài
@@ -873,7 +872,7 @@ support.sellerOfferer=Người bán BTC/Người tạo
 support.buyerTaker=Người mua BTC/Người nhận
 support.sellerTaker=Người bán BTC/Người nhận
 
-support.backgroundInfo=Bisq is not a company, so it handles disputes differently.\n\nTraders can communicate within the application via a secure chat on the open trades screen to attempt solving a dispute on their own. If that is not sufficient, a mediator can step in to help. The mediator will evaluate the situation and give a recommendation for the payout of the trade funds. If both traders accept this suggestion, the payout transaction is completed and the trade is closed. If one or both traders do not agree to the mediator's recommended payout, they can request arbitration.The arbitrator has the third key of the deposit transaction and will make the payout based on their findings.
+support.backgroundInfo=Bisq is not a company, so it handles disputes differently.\n\nTraders can communicate within the application via secure chat on the open trades screen to try solving disputes on their own. If that is not sufficient, a mediator can step in to help. The mediator will evaluate the situation and suggest a payout of trade funds. If both traders accept this suggestion, the payout transaction is completed and the trade is closed. If one or both traders do not agree to the mediator's suggested payout, they can request arbitration.The arbitrator will re-evaluate the situation and, if warranted, personally pay the trader back and request reimbursement for this payment from the Bisq DAO.
 support.initialInfo=Please enter a description of your problem in the text field below. Add as much information as possible to speed up dispute resolution time.\n\nHere is a check list for information you should provide:\n\t● If you are the BTC buyer: Did you make the Fiat or Altcoin transfer? If so, did you click the 'payment started' button in the application?\n\t● If you are the BTC seller: Did you receive the Fiat or Altcoin payment? If so, did you click the 'payment received' button in the application?\n\t● Which version of Bisq are you using?\n\t● Which operating system are you using?\n\t● If you encountered an issue with failed transactions please consider switching to a new data directory.\n\t  Sometimes the data directory gets corrupted and leads to strange bugs. \n\t  See: https://docs.bisq.network/backup-recovery.html#switch-to-a-new-data-directory\n\nPlease make yourself familiar with the basic rules for the dispute process:\n\t● You need to respond to the {0}''s requests within 2 days.\n\t● Mediators respond in between 2 days. Arbitrators respond in between 5 business days.\n\t● The maximum period for a dispute is 14 days.\n\t● You need to cooperate with the {1} and provide the information they request to make your case.\n\t● You accepted the rules outlined in the dispute document in the user agreement when you first started the application.\n\nYou can read more about the dispute process at: {2}
 support.systemMsg=Tin nhắn hệ thống: {0}
 support.youOpenedTicket=Bạn đã mở yêu cầu hỗ trợ.\n\n{0}\n\nPhiên bản Bisq: {1}
@@ -1038,7 +1037,7 @@ account.altcoin.popup.wallet.msg=Please be sure that you follow the requirements
 account.altcoin.popup.wallet.confirm=Tôi hiểu và xác nhận rằng tôi đã biết loại ví mình cần sử dụng.
 account.altcoin.popup.upx.msg=Trading UPX on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending UPX, you need to use either the official uPlexa GUI wallet or uPlexa CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nuplexa-wallet-cli (use the command get_tx_key)\nuplexa-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The UPX sender is responsible for providing verification of the UPX transfer to the arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit uPlexa discord channel (https://discord.gg/vhdNSrV) or the uPlexa Telegram Chat (https://t.me/uplexaOfficial) to find more information.
 account.altcoin.popup.arq.msg=Trading ARQ on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending ARQ, you need to use either the official ArQmA GUI wallet or ArQmA CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\narqma-wallet-cli (use the command get_tx_key)\narqma-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the mediator or arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The ARQ sender is responsible for providing verification of the ARQ transfer to the mediator or arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit ArQmA discord channel (https://discord.gg/s9BQpJT) or the ArQmA forum (https://labs.arqma.com) to find more information.
-account.altcoin.popup.xmr.msg=Trading XMR on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending XMR, you need to use either the official Monero GUI wallet or Monero CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nmonero-wallet-cli (use the command get_tx_key)\nmonero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nIn addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\nmonero-wallet-cli : using command (check_tx_key).\nmonero-wallet-gui : on the Advanced > Prove/Check page.\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the mediator or arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The XMR sender is responsible for providing verification of the XMR transfer to the mediator or arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) or the Monero forum (https://forum.getmonero.org) to find more information.
+account.altcoin.popup.xmr.msg=Trading XMR on Bisq requires that you understand and fulfill the following requirements:\n\nProve payments: since Monero is a private coin, some transaction details aren't publicly available in the blockchain, and, in case of a dispute, the mediator or arbitrator needs them to check if the transaction was really made. In Bisq, the sender of the XMR transaction is the one responsible for providing this information to the mediator or arbitrator in case of a dispute. In order to do that, you must send XMR using a wallet that provides the information required to prove the payment was made, which includes:\n\n- the transaction key (Tx Key, Tx Secret Key or Tx Private Key)\n- the transaction ID (Tx ID or Tx Hash)\n- the destination address (recipient's address)\n\nThis information can be found in the official Monero GUI & CLI wallets, MyMonero, and Exodus (desktop) as well as in Cake Wallet, MyMonero, and Monerujo (mobile), in the following locations:\n\n- Monero GUI: go to Transactions tab\n- Monero CLI: use the command get_tx_key TXID. The flag store-tx-info must be enabled (enabled by default in new versions)\n- Other wallets: go to Transactions history and search for Transaction key (Tx key or Secret key) and the destination address in a sent transaction. Save recipient address option must be enabled in Cake Wallet settings.\n\nIf you are using a wallet different from the mentioned above, please be sure you can access those three pieces of information.Since the transaction key and the destination address are stored in the Monero wallet software, and they cannot be recovered in the Monero blockchain, you should never delete or restore your Monero wallet before a Bisq trade is completed. Failure to provide the above data will result in losing the dispute case.\n\nCheck payments: with those three pieces of information, the verification that a quantity of Monero was sent to a specific address can be accomplished the following way:\n\n- Monero GUI: change wallet to Advanced mode and go to Advanced > Prove/check > Check Transaction\n- Monero CLI: use the command check_tx_key TXID TXKEY ADDRESS\n- XMR checktx tool (https://xmr.llcoins.net/checktx.html)\n- Explore Monero website (https://www.exploremonero.com/receipt)\n\nIf you are still not sure about this process, visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) to find more information or ask a question on the Monero support subreddit (https://www.reddit.com/r/monerosupport/).
 # suppress inspection "TrailingSpacesInProperty"
 account.altcoin.popup.msr.msg=Trading MSR on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending MSR, you need to use either the official Masari GUI wallet, Masari CLI wallet with the store-tx-info flag enabled (enabled by default) or the Masari web wallet (https://wallet.getmasari.org). Please be sure you can access the tx key as that would be required in case of a dispute.\nmasari-wallet-cli (use the command get_tx_key)\nmasari-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nMasari Web Wallet (goto Account -> transaction history and view details on your sent transaction)\n\nVerification can be accomplished in-wallet.\nmasari-wallet-cli : using command (check_tx_key).\nmasari-wallet-gui : on the Advanced > Prove/Check page.\nVerification can be accomplished in the block explorer \nOpen block explorer (https://explorer.getmasari.org), use the search bar to find your transaction hash.\nOnce transaction is found, scroll to bottom to the 'Prove Sending' area and fill in details as needed.\nYou need to provide the mediator or arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The MSR sender is responsible for providing verification of the MSR transfer to the mediator or arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process, ask for help on the Official Masari Discord (https://discord.gg/sMCwMqs).
 account.altcoin.popup.blur.msg=Trading BLUR on Bisq requires that you understand and fulfill the following requirements:\n\nTo send BLUR you must use the Blur Network CLI or GUI Wallet. \n\nIf you are using the CLI wallet, a transaction hash (tx ID) will be displayed after a transfer is sent. You must save this information. Immediately after sending the transfer, you must use the command 'get_tx_key' to retrieve the transaction private key. If you fail to perform this step, you may not be able to retrieve the key later. \n\nIf you are using the Blur Network GUI Wallet, the transaction private key and transaction ID can be found conveniently in the "History" tab.  Immediately after sending, locate the transaction of interest. Click the "?" symbol in the lower-right corner of the box containing the transaction. You must save this information. \n\nIn the event that arbitration is necessary, you must present the following to an mediator or arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address.  The mediator or arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nFailure to provide the required information to the mediator or arbitrator will result in losing the dispute case. In all cases of dispute, the BLUR sender bears 100% of the burden of responsibility in verifying transactions to an mediator or arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW).
@@ -1169,6 +1168,7 @@ dao.lockedForVoteBalance=Dùng để bỏ phiếu
 dao.lockedInBonds=Bị khóa trong hợp đồng
 dao.availableNonBsqBalance=Số dư không phải BSQ có sẵn (tính bằng BTC)
 dao.totalBsqBalance=Tổng số dư BSQ
+dao.reputationBalance=Merit Value (not spendable)
 
 dao.tx.published.success=Giao dịch của bạn đã được công bố thành công.
 dao.proposal.menuItem.make=Tạo đề nghị
@@ -1961,7 +1961,7 @@ showWalletDataWindow.includePrivKeys=Bao gồm khóa cá nhân
 tacWindow.headline=Thỏa thuận người dùng
 tacWindow.agree=Tôi đồng ý
 tacWindow.disagree=Tôi không đồng ý và thoát
-tacWindow.arbitrationSystem=Hệ thống trọng tài
+tacWindow.arbitrationSystem=Dispute resolution
 
 tradeDetailsWindow.headline=giao dịch
 tradeDetailsWindow.disputedPayoutTxId=ID giao dịch hoàn tiền khiếu nại:
@@ -2152,7 +2152,7 @@ systemTray.show=Hiển thị cửa sổ ứng dung
 systemTray.hide=Ẩn cửa sổ ứng dụng
 systemTray.info=Thông tin về Bisq
 systemTray.exit=Thoát
-systemTray.tooltip=Bisq: Mạng trao đổi phân quyền
+systemTray.tooltip=Bisq: A decentralized bitcoin exchange network
 
 
 ####################################################################

core/src/main/resources/i18n/displayStrings_zh-hans.properties

@@ -274,7 +274,7 @@ mainView.p2pNetworkWarnMsg.connectionToP2PFailed=连接至 Bisq 网络失败（
 mainView.walletServiceErrorMsg.timeout=比特币网络连接超时。
 mainView.walletServiceErrorMsg.connectionError=错误：{0} 比特币网络连接失败。
 
-mainView.walletServiceErrorMsg.rejectedTxException=A transaction was rejected from the network.\n\n{0}
+mainView.walletServiceErrorMsg.rejectedTxException=交易被网络拒绝。\n\n{0}
 
 mainView.networkWarning.allConnectionsLost=您失去所有与 {0} 网络节点的连接。\n或许您失去互联网连接或您的计算机处于待机状态。
 mainView.networkWarning.localhostBitcoinLost=您丢失了与本地主机比特币节点的连接。\n请重启 Bisq 应用程序连接到其他比特币节点或重新启动主机比特币节点。
@@ -672,7 +672,6 @@ portfolio.pending.step5_buyer.takersMiningFee=总共挖矿手续费
 portfolio.pending.step5_buyer.refunded=退还保证金
 portfolio.pending.step5_buyer.withdrawBTC=提现您的比特币
 portfolio.pending.step5_buyer.amount=提现数量
-portfolio.pending.step5_buyer.signer=通过提取您的比特币，您可以验证交易伙伴是否按照交易协议行事。
 portfolio.pending.step5_buyer.withdrawToAddress=提现地址
 portfolio.pending.step5_buyer.moveToBisqWallet=资金划转到 Bisq 钱包
 portfolio.pending.step5_buyer.withdrawExternal=提现到外部钱包
@@ -706,9 +705,9 @@ portfolio.pending.openSupportTicket.headline=创建帮助话题
 portfolio.pending.openSupportTicket.msg=请仅在紧急情况下使用此功能，如果您没有看到“提交支持”或“提交纠纷”按钮。\n\n当您发出工单时，交易将被中断并由调解员或仲裁员进行处理。
 
 portfolio.pending.timeLockNotOver=你必须等到≈{0}(还需等待{1}个区块)才能提交纠纷。
-portfolio.pending.error.depositTxNull=The deposit transaction is null. You cannot open a dispute without a valid deposit transaction. Please go to \"Settings/Network info\" and do a SPV resync.\n\nFor further help please contact the Bisq support channel at the Bisq Keybase team.
-portfolio.pending.mediationResult.error.depositTxNull=The deposit transaction is null. The trade gets moved to the failed trades section.
-portfolio.pending.error.depositTxNotConfirmed=The deposit transaction is not confirmed. You can not open an arbitration dispute with an unconfirmed deposit transaction. Please wait until it is confirmed or go to \"Settings/Network info\" and do a SPV resync.\n\nFor further help please contact the Bisq support channel at the Bisq Keybase team.
+portfolio.pending.error.depositTxNull=保证金交易无效。没有有效的保证金交易，你使用创建纠纷。请到“设置/网络信息”进行 SPV 重新同步。\n \n如需更多帮助，请联系 Bisq Keybase 团队的 Support 频道。
+portfolio.pending.mediationResult.error.depositTxNull=保证金交易无效。交易被移至失败交易。
+portfolio.pending.error.depositTxNotConfirmed=保证金交易未确认。未经确认的存款交易不能发起纠纷或仲裁请求。请耐心等待，直到它被确认或进入“设置/网络信息”进行 SPV 重新同步。\n\n如需更多帮助，请联系 Bisq Keybase 团队的 Support 频道。
 
 portfolio.pending.notification=通知
 
@@ -873,7 +872,7 @@ support.sellerOfferer=BTC 卖家/挂单者
 support.buyerTaker=BTC 买家/买单者
 support.sellerTaker=BTC 卖家/买单者
 
-support.backgroundInfo=Bisq 不是一家公司，所以它处理纠纷的方式不同。\n\n交易双方可以在应用程序中通过未完成交易页面上的安全聊天进行通信，以尝试自行解决争端。如果这还不够，调解员可以介入帮助。调解员将对情况进行评估，并对交易资金的支出提出建议。如果两个交易者都接受这个建议，那么支付交易就完成了，交易也结束了。如果一方或双方不同意调解员的建议，他们可以要求仲裁。仲裁员有保证金交易的第三个密钥，并将根据他们的调查结果进行收款。
+support.backgroundInfo=Bisq 不是一家公司，所以它处理纠纷的方式不同。\n\n交易双方可以在应用程序中通过未完成交易页面上的安全聊天进行通信，以尝试自行解决争端。如果这还不够，调解员可以介入帮助。调解员将对情况进行评估，并对交易资金的支出提出建议。如果两个交易者都接受这个建议，那么支付交易就完成了，交易也结束了。如果一方或双方不同意调解员的建议，他们可以要求仲裁。仲裁员将重新评估情况，如果有必要，将亲自向交易员付款，并要求 Bisq DAO 对这笔付款进行补偿。
 support.initialInfo=请在下面的文本框中输入您的问题描述。添加尽可能多的信息，以加快解决纠纷的时间。\n\n以下是你应提供的资料核对表：\n\t●如果您是 BTC 买家：您是否使用法定货币或其他加密货币转账？如果是，您是否点击了应用程序中的“支付开始”按钮？\n\t●如果您是 BTC 卖家：您是否收到法定货币或其他加密货币的付款了？如果是，你是否点击了应用程序中的“已收到付款”按钮？\n\t●您使用的是哪个版本的 Bisq？\n\t●您使用的是哪种操作系统？\n\t●如果遇到操作执行失败的问题，请考虑切换到新的数据目录。\n\t有时数据目录会损坏，并导致奇怪的错误。\n详见：https://docs.bisq.network/backup-recovery.html#switch-to-a-new-data-directory\n\n请熟悉纠纷处理的基本规则：\n\t●您需要在2天内答复 {0} 的请求。\n\t●调解员会在2天之内答复，仲裁员会在5天之内答复。\n\t●纠纷的最长期限为14天。\n\t●你需要与仲裁员合作，提供他们为你的案件所要求的信息。\n\t●当您第一次启动应用程序时，您接受了用户协议中争议文档中列出的规则。\n\n您可以通过 {2} 了解有关纠纷处理的更多信息
 support.systemMsg=系统消息：{0}
 support.youOpenedTicket=您创建了帮助请求。\n\n{0}\n\nBisq 版本：{1}
@@ -978,7 +977,7 @@ settings.net.inbound=数据包进入
 settings.net.outbound=数据包出口
 settings.net.reSyncSPVChainLabel=重新同步 SPV 链
 settings.net.reSyncSPVChainButton=删除 SPV 链文件并重新同步
-settings.net.reSyncSPVSuccess=The SPV chain file will be deleted on the next startup. You need to restart your application now.\n\nAfter the restart it can take a while to resync with the network and you will only see all transactions once the resync is completed.\n\nDepending on the number of transactions and the age of your wallet the resync can take up to a few hours and consumes 100% of CPU. Do not interrupt the process otherwise you have to repeat it.
+settings.net.reSyncSPVSuccess=SPV 链文件将在下一次启动时被删除。您现在需要重新启动应用程序。\n\n重新启动后，可能需要一段时间才能与网络重新同步，只有重新同步完成后才会看到所有的交易。\n\n根据交易的数量和钱包账龄，重新同步可能会花费几个小时，并消耗100%的 CPU。不要打断这个过程，否则你会不断地重复它。
 settings.net.reSyncSPVAfterRestart=SPV 链文件已被删除。请耐心等待，与网络重新同步可能需要一段时间。
 settings.net.reSyncSPVAfterRestartCompleted=重新同步刚刚完成，请重启应用程序。
 settings.net.reSyncSPVFailed=无法删除 SPV 链文件。\n错误：{0}
@@ -1038,7 +1037,7 @@ account.altcoin.popup.wallet.msg=请确保您按照 {1} 网页上所述使用 {0
 account.altcoin.popup.wallet.confirm=我了解并确定我知道我需要哪种钱包。
 account.altcoin.popup.upx.msg=在 Bisq 上交易 UPX 需要您了解并满足以下要求：\n\n要发送 UPX ，您需要使用官方的 UPXmA GUI 钱包或启用 store-tx-info 标志的 UPXmA CLI 钱包（在新版本中是默认的）。请确保您可以访问Tx密钥，因为在纠纷状态时需要。\nmonero-wallet-cli（使用get_Tx_key命令）\nmonero-wallet-gui：在高级>证明/检查页面。\n\n在普通的区块链浏览器中，这种交易是不可验证的。\n\n如有纠纷，你须向仲裁员提供下列资料：\n \n- Tx私钥\n- 交易哈希\n- 接收者的公开地址\n\n如未能提供上述资料，或使用不兼容的钱包，将会导致纠纷败诉。如果发生纠纷，UPX 发送方负责向仲裁员提供 UPX 转账的验证。\n\n不需要支付 ID，只需要普通的公共地址。\n \n如果您对该流程不确定，请访问 UPXmA Discord 频道（https://discord.gg/vhdNSrV）或 Telegram 交流群（https://t.me/uplexaOfficial）了解更多信息。\n\n
 account.altcoin.popup.arq.msg=在 Bisq 上交易 ARQ 需要您了解并满足以下要求：\n\n要发送 ARQ ，您需要使用官方的 ArQmA GUI 钱包或启用 store-tx-info 标志的 ArQmA CLI 钱包（在新版本中是默认的）。请确保您可以访问Tx密钥，因为在纠纷状态时需要。\nmonero-wallet-cli（使用get_Tx_key命令）\nmonero-wallet-gui：在高级>证明/检查页面。\n\n在普通的区块链浏览器中，这种交易是不可验证的。\n\n如有纠纷，你须向调解员或仲裁员提供下列资料：\n\n- Tx私钥\n- 交易哈希\n- 接收者的公开地址\n\n如未能提供上述资料，或使用不兼容的钱包，将会导致纠纷败诉。如果发生纠纷，ARQ 发送方负责向调解员或仲裁员提供 ARQ 转账的验证。\n\n不需要交易 ID，只需要普通的公共地址。\n\n如果您对该流程不确定，请访问 ArQmA Discord 频道（https://discord.gg/s9BQpJT）或 ArQmA 论坛（https://labs.arqma.com）了解更多信息。
-account.altcoin.popup.xmr.msg=在 Bisq 上交易 XMR 需要您了解并满足以下要求：\n\n要发送 XMR ，您需要使用官方的 Monero GUI 钱包或 Monero CLI 钱包，并启用 store-tx-info 标志（在新版本中是默认的）。请确保您可以访问Tx密钥，因为如果发生纠纷这是需要的。\nmonero-wallet-cli（使用get_Tx_key命令）\nmonero-wallet-gui：在高级>证明/检查页面。\n\n除了 XMR checktx 工具（https://xmr llcoins.net/checktx.html），还可以在钱包中完成验证。\nmonero-wallet-cli：使用命令（check_tx_key）。\nmonero-wallet-gui：在高级>证明/检查页面\n\n在普通的区块浏览器，这种转移是不可验证的。\n\n如有纠纷，你须向调解员或仲裁员提供下列资料：\n- Tx私钥\n- 交易哈希\n- 接收者的公开地址\n\n如未能提供上述资料，或使用不兼容的钱包，将会导致纠纷败诉。如果发生纠纷，XMR 发送方负责向调解员或仲裁员提供 XMR 转账的验证。\n\n如果您对该流程不确定，请访问（https://www.getmonero.org/resources/user-guides/prove-payment.html）或 Monero 论坛（https://forum.getmonero.org）了解更多信息。
+account.altcoin.popup.xmr.msg=在 Bisq 上交易 XMR 需要你理解并满足以下要求：\n\n付款证明：由于 Monero 是一种高隐私性货币，区块链中不公开一些交易细节，而且，在发生争议时，调解员或仲裁员需要他们检查交易是否真的进行了。在 Bisq 中，XMR 交易的发送方负责在发生争议时向调解员或仲裁员提供此信息。为了做到验证付款，您必须使用钱包发送 XMR ，钱包提供所需的信息来证明付款已经完成，其中包括:\n\n- 交易密钥（Tx 公钥、Tx 密钥或 Tx 私钥)\n- 交易ID（Tx ID 或Tx 哈希）\n- 目的地地址（收款人地址）\n\n这些信息可以在官方的 Monero GUI 和 CLI 钱包、MyMonero 和 Exodus （桌面版）以及 Cake Wallet、MyMonero 和 Monerujo（移动版）中找到，地点如下:\n\n- Monero GUI：转到 交易 标签\n- Monero CLI：使用命令 get_tx_key TXID 。必须启用标记 store-tx-info （在新版本中默认启用）\n- 其他钱包：转到交易历史记录，在发送的交易中搜索交易密钥（Tx密钥或Tx秘密）和目标地址。保存收件人地址选项必须在 Cake Wallet 设置中启用。\n\n如果您使用的钱包与上述不同，请确保您可以访问这三个信息。由于交易密钥和目标地址存储在 Monero 钱包软件中，无法在 Monero 区块链中恢复，所以在 Bisq 交易完成之前，您不应该删除或恢复您的 Monero 钱包。如不提供以上资料，将导致纠纷败诉。\n\n检查付款：有了这三条信息，可以通过以下方式来验证是否有一定数量的 Monero 被发送到特定地址：\n\n- Monero GUI：将钱包切换到高级模式，进入高级>验证/检查>检查交易\n- Monero CLI：使用命令 check_tx_key TXID TXKEY ADDRESS\n- XMR Tx 验证工具（https://xmr.llcoins.net/checktx.html）\n- 浏览 Monero 官网（https://www.exploremonero.com/receipt）\n\n如果您仍然对此有疑问，请访问（https://www.getmonero.org/resources/userguides/prove-payment.html）来查找更多信息或在 Monero Support subreddit 上提问（https://www.reddit.com/r/monerosupport/）。
 # suppress inspection "TrailingSpacesInProperty"
 account.altcoin.popup.msr.msg=区块链浏览器在 Bisq 上交易 XMR 需要您了解并满足以下要求：\n\n发送MSR时，您需要使用官方的 Masari GUI 钱包、启用store-tx-info标记的Masari CLI钱包(默认启用)或Masari 网页钱包(https://wallet.getmasari.org)。请确保您可以访问的 tx 密钥，因为如果发生纠纷这是需要的。\nmonero-wallet-cli（使用get_Tx_key命令）\nmonero-wallet-gui：在高级>证明/检查页面。\n\nMasari 网页钱包（前往 帐户->交易历史和查看您发送的交易细节）\n\n验证可以在钱包中完成。\nmonero-wallet-cli：使用命令（check_tx_key）。\nmonero-wallet-gui：在高级>证明/检查页面\n验证可以在区块浏览器中完成\n打开区块浏览器（https://explorer.getmasari.org），使用搜索栏查找您的事务哈希。\n一旦找到交易，滚动到底部的“证明发送”区域，并填写所需的详细信息。\n如有纠纷，你须向调解员或仲裁员提供下列资料：\n- Tx私钥\n- 交易哈希\n- 接收者的公开地址\n\n不需要交易 ID，只需要正常的公共地址。\n如未能提供上述资料，或使用不兼容的钱包，将会导致纠纷败诉。如果发生纠纷，XMR 发送方负责向调解员或仲裁员提供 XMR 转账的验证。\n\n如果您对该流程不确定，请访问官方的 Masari Discord（https://discord.gg/sMCwMqs）上寻求帮助。
 account.altcoin.popup.blur.msg=在 Bisq 上交易 BLUR 需要你了解并满足以下要求：\n\n要发送匿名信息你必须使用匿名网络 CLI 或 GUI 钱包。\n如果您正在使用 CLI 钱包，在传输发送后将显示交易哈希（tx ID）。您必须保存此信息。在发送传输之后，您必须立即使用“get_tx_key”命令来检索交易私钥。如果未能执行此步骤，以后可能无法检索密钥。\n\n如果您使用 Blur Network GUI 钱包，可以在“历史”选项卡中方便地找到交易私钥和交易 ID。发送后立即定位感兴趣的交易。单击包含交易的框的右下角的“?”符号。您必须保存此信息。\n\n如果仲裁是必要的，您必须向调解员或仲裁员提供以下信息：1.)交易ID，2.)交易私钥，3.)收件人地址。调解或仲裁程序将使用 BLUR 事务查看器（https://blur.cash/#tx-viewer）验证 BLUR 转账。\n\n未能向调解员或仲裁员提供必要的信息将导致败诉。在所有争议的情况下，匿名发送方承担100%的责任来向调解员或仲裁员核实交易。\n\n如果你不了解这些要求，不要在 Bisq 上交易。首先，在 Blur Network Discord 中寻求帮助（https://discord.gg/dMWaqVW）。
@@ -1169,6 +1168,7 @@ dao.lockedForVoteBalance=用于投票
 dao.lockedInBonds=冻结余额
 dao.availableNonBsqBalance=可用的非 BSQ 余额（BTC）
 dao.totalBsqBalance=BSQ 总额
+dao.reputationBalance=声望值（不会花费）
 
 dao.tx.published.success=你的交易已经成功发布
 dao.proposal.menuItem.make=创建要求
@@ -1961,7 +1961,7 @@ showWalletDataWindow.includePrivKeys=包含私钥
 tacWindow.headline=用户协议
 tacWindow.agree=我同意
 tacWindow.disagree=我不同意并退出
-tacWindow.arbitrationSystem=仲裁系统
+tacWindow.arbitrationSystem=纠纷解决方案
 
 tradeDetailsWindow.headline=交易
 tradeDetailsWindow.disputedPayoutTxId=纠纷支付交易 ID：
@@ -2025,8 +2025,8 @@ popup.error.takeOfferRequestFailed=当有人试图接受你的报价时发生了
 
 error.spvFileCorrupted=读取 SPV 链文件时发生错误。\n可能是 SPV 链文件被破坏了。\n\n错误消息：{0}\n\n要删除它并开始重新同步吗？
 error.deleteAddressEntryListFailed=无法删除 AddressEntryList 文件。\n \n错误：{0}
-error.closedTradeWithUnconfirmedDepositTx=The deposit transaction of the closed trade with the trade ID {0} is still unconfirmed.\n\nPlease do a SPV resync at \"Setting/Network info\" to see if the transaction is valid.
-error.closedTradeWithNoDepositTx=The deposit transaction of the closed trade with the trade ID {0} is null.\n\nPlease restart the application to clean up the closed trades list.
+error.closedTradeWithUnconfirmedDepositTx=交易 ID 为 {0} 的已关闭交易的保证金交易仍未确认。\n \n请在“设置/网络信息”进行 SPV 重新同步，以查看交易是否有效。
+error.closedTradeWithNoDepositTx=交易 ID 为 {0} 的保证金交易已被确认。\n\n请重新启动应用程序来清理已关闭的交易列表。
 
 popup.warning.walletNotInitialized=钱包至今未初始化
 popup.warning.wrongVersion=您这台电脑上可能有错误的 Bisq 版本。\n您的电脑的架构是：{0}\n您安装的 Bisq 二进制文件是：{1}\n请关闭并重新安装正确的版本（{2}）。
@@ -2064,16 +2064,16 @@ popup.warning.mandatoryUpdate.dao=请更新到最新的 Bisq 版本。发布了
 popup.warning.disable.dao=Bisq DAO 和 BSQ 被临时禁用的。更多信息请访问 Bisq 论坛。
 popup.warning.burnBTC=这笔交易是不可能的，因为 {0} 的挖矿手续费用会超过 {1} 的转账金额。请等到挖矿手续费再次降低或您积累了更多的 BTC 来转账。
 
-popup.warning.openOffer.makerFeeTxRejected=The maker fee transaction for offer with ID {0} was rejected by the Bitcoin network.\nTransaction ID={1}.\nThe offer has been removed to avoid further problems.\nPlease go to \"Settings/Network info\" and do a SPV resync.\nFor further help please contact the Bisq support channel at the Bisq Keybase team.
+popup.warning.openOffer.makerFeeTxRejected=交易 ID 为 {0} 的挂单费交易被比特币网络拒绝。\n交易 ID = {1}\n交易已被移至失败交易。\n请到“设置/网络信息”进行 SPV 重新同步。\n如需更多帮助，请联系 Bisq Keybase 团队的 Support 频道
 
-popup.warning.trade.txRejected.tradeFee=trade fee
-popup.warning.trade.txRejected.deposit=deposit
-popup.warning.trade.txRejected=The {0} transaction for trade with ID {1} was rejected by the Bitcoin network.\nTransaction ID={2}}\nThe trade has been moved to failed trades.\nPlease go to \"Settings/Network info\" and do a SPV resync.\nFor further help please contact the Bisq support channel at the Bisq Keybase team.
+popup.warning.trade.txRejected.tradeFee=交易手续费
+popup.warning.trade.txRejected.deposit=押金
+popup.warning.trade.txRejected=使用 ID {1} 进行交易的 {0} 交易被比特币网络拒绝。\n交易 ID = {2}}\n交易已被移至失败交易。\n请到“设置/网络信息”进行 SPV 重新同步。\n如需更多帮助，请联系 Bisq Keybase 团队的 Support 频道
 
-popup.warning.openOfferWithInvalidMakerFeeTx=The maker fee transaction for offer with ID {0} is invalid.\nTransaction ID={1}.\nPlease go to \"Settings/Network info\" and do a SPV resync.\nFor further help please contact the Bisq support channel at the Bisq Keybase team.
+popup.warning.openOfferWithInvalidMakerFeeTx=交易 ID 为 {0} 的挂单费交易无效。\n交易 ID = {1}。\n请到“设置/网络信息”进行 SPV 重新同步。\n如需更多帮助，请联系 Bisq Keybase 团队的 Support 频道
 
-popup.warning.trade.depositTxNull=The trade with ID {0} has no deposit transaction set.\nPlease restart the application and if the problem remains move the trade to failed trades and report the problem to the Bisq support channel at the Bisq Keybase team.
-popup.warning.trade.depositTxNull.moveToFailedTrades=Move to failed trades
+popup.warning.trade.depositTxNull=交易 ID 为 {0} 没有设置保证金交易。\n请重新启动应用程序，如果问题仍然存在，将交易移至失败交易，并将问题报告到 Bisq Keybase 团队的 Support 频道。
+popup.warning.trade.depositTxNull.moveToFailedTrades=移至失败交易
 
 popup.info.securityDepositInfo=为了确保双方都遵守交易协议，双方都需要支付保证金。\n\n这笔存款一直保存在您的交易钱包里，直到您的交易成功完成，然后再退还给您。\n\n请注意：如果您正在创建一个新的报价，Bisq 需要运行另一个交易员接受它。为了让您的报价在线，保持 Bisq 运行，并确保这台计算机也在线（即，确保它没有切换到待机模式…显示器可以待机）。
 
@@ -2152,7 +2152,7 @@ systemTray.show=显示应用程序窗口
 systemTray.hide=隐藏应用程序窗口
 systemTray.info=关于 Bisq 信息
 systemTray.exit=退出
-systemTray.tooltip=Bisq：去中心化交易网络
+systemTray.tooltip=Bisq：去中心化比特币交易网络
 
 
 ####################################################################

core/src/main/resources/i18n/displayStrings_zh-hant.properties

@@ -62,17 +62,17 @@ shared.priceWithCur={0} 價格
 shared.priceInCurForCur=1 {1} 的 {0} 價格
 shared.fixedPriceInCurForCur=1 {1} 的 {0} 的固定價格
 shared.amount=數量
-shared.txFee=Transaction Fee
-shared.makerFee=Maker Fee
-shared.buyerSecurityDeposit=Buyer Deposit
-shared.sellerSecurityDeposit=Seller Deposit
+shared.txFee=交易手續費
+shared.makerFee=掛單費
+shared.buyerSecurityDeposit=買家保證金
+shared.sellerSecurityDeposit=賣家保證金
 shared.amountWithCur={0} 數量
 shared.volumeWithCur={0} 量
-shared.currency=貨幣型別
-shared.market=交易專案
+shared.currency=貨幣類型
+shared.market=交易項目
 shared.paymentMethod=付款方式
 shared.tradeCurrency=交易貨幣
-shared.offerType=委託型別
+shared.offerType=委託類型
 shared.details=詳情
 shared.address=地址
 shared.balanceWithCur={0} 餘額
@@ -152,7 +152,7 @@ shared.save=儲存
 shared.onionAddress=匿名地址
 shared.supportTicket=幫助話題
 shared.dispute=糾紛
-shared.mediationCase=mediation case
+shared.mediationCase=介入事件
 shared.seller=賣家
 shared.buyer=買家
 shared.allEuroCountries=所有歐元國家
@@ -207,13 +207,13 @@ shared.votes=投票
 shared.learnMore=瞭解更多
 shared.dismiss=忽略
 shared.selectedArbitrator=選中的仲裁者
-shared.selectedMediator=Selected mediator
+shared.selectedMediator=選擇調解員
 shared.selectedRefundAgent=選中的仲裁者
 shared.mediator=中介
 shared.arbitrator=仲裁員
 shared.refundAgent=仲裁員
-shared.refundAgentForSupportStaff=Refund agent
-shared.delayedPayoutTxId=Refund collateral transaction ID
+shared.refundAgentForSupportStaff=退款助理
+shared.delayedPayoutTxId=退款擔保交易 ID
 
 
 ####################################################################
@@ -224,7 +224,7 @@ shared.delayedPayoutTxId=Refund collateral transaction ID
 # MainView
 ####################################################################
 
-mainView.menu.market=交易專案
+mainView.menu.market=交易項目
 mainView.menu.buyBtc=買入 BTC
 mainView.menu.sellBtc=賣出 BTC
 mainView.menu.portfolio=業務
@@ -256,7 +256,7 @@ mainView.footer.btcInfo.synchronizingWith=正在同步至
 mainView.footer.btcInfo.synchronizedWith=已同步至
 mainView.footer.btcInfo.connectingTo=連線至
 mainView.footer.btcInfo.connectionFailed=連線失敗
-mainView.footer.p2pInfo=Bisq network peers: {0}
+mainView.footer.p2pInfo=Bisq 網路對等點：{0}
 mainView.footer.daoFullNode=DAO 全節點
 
 mainView.bootstrapState.connectionToTorNetwork=(1/4) 連線至 Tor 網路...
@@ -266,15 +266,15 @@ mainView.bootstrapState.initialDataReceived=(4/4) 初始資料已接收
 
 mainView.bootstrapWarning.noSeedNodesAvailable=沒有可用的種子節點
 mainView.bootstrapWarning.noNodesAvailable=沒有可用的種子節點和節點
-mainView.bootstrapWarning.bootstrappingToP2PFailed=Bootstrapping to Bisq network failed
+mainView.bootstrapWarning.bootstrappingToP2PFailed=啟動 Bisq 網路失敗
 
 mainView.p2pNetworkWarnMsg.noNodesAvailable=請求資料沒有可用種子和節點。\n請檢查您的網際網路連線或嘗試重啟應用程式。
-mainView.p2pNetworkWarnMsg.connectionToP2PFailed=Connecting to the Bisq network failed (reported error: {0}).\nPlease check your internet connection or try to restart the application.
+mainView.p2pNetworkWarnMsg.connectionToP2PFailed=連線至 Bisq 網路失敗（錯誤報告：{0}）。\n請檢查您的網際網路連線或嘗試重啟應用程式。
 
 mainView.walletServiceErrorMsg.timeout=比特幣網路連線超時。
 mainView.walletServiceErrorMsg.connectionError=錯誤：{0} 比特幣網路連線失敗。
 
-mainView.walletServiceErrorMsg.rejectedTxException=A transaction was rejected from the network.\n\n{0}
+mainView.walletServiceErrorMsg.rejectedTxException=交易被網路拒絕。\n\n{0}
 
 mainView.networkWarning.allConnectionsLost=您失去所有與 {0} 網路節點的連線。\n或許您失去網際網路連線或您的計算機處於待機狀態。
 mainView.networkWarning.localhostBitcoinLost=您丟失了與本地主機比特幣節點的連線。\n請重啟 Bisq 應用程式連線到其他比特幣節點或重新啟動主機比特幣節點。
@@ -315,7 +315,7 @@ market.trades.tooltip.candle.close=關閉：
 market.trades.tooltip.candle.high=高：
 market.trades.tooltip.candle.low=低：
 market.trades.tooltip.candle.average=平均：
-market.trades.tooltip.candle.median=Median:
+market.trades.tooltip.candle.median=調解員：
 market.trades.tooltip.candle.date=日期：
 
 ####################################################################
@@ -335,20 +335,20 @@ offerbook.offerersAcceptedBankSeats=接受的銀行所在國家（買家）：\n
 offerbook.availableOffers=可用委託
 offerbook.filterByCurrency=以貨幣過濾
 offerbook.filterByPaymentMethod=以支付方式過濾
-offerbook.timeSinceSigning=Time since signing
-offerbook.timeSinceSigning.info=This account was verified and {0}
-offerbook.timeSinceSigning.info.arbitrator=signed by an arbitrator and can sign peer accounts
-offerbook.timeSinceSigning.info.peer=signed by a peer, waiting for limits to be lifted
-offerbook.timeSinceSigning.info.peerLimitLifted=signed by a peer and limits were lifted
-offerbook.timeSinceSigning.info.signer=signed by peer and can sign peer accounts (limits lifted)
+offerbook.timeSinceSigning=自簽字
+offerbook.timeSinceSigning.info=此賬戶已驗證，{0}
+offerbook.timeSinceSigning.info.arbitrator=由仲裁員簽字，並可以簽署夥伴賬戶
+offerbook.timeSinceSigning.info.peer=由夥伴簽名，等待限制被解除
+offerbook.timeSinceSigning.info.peerLimitLifted=由同伴簽署，限制被取消
+offerbook.timeSinceSigning.info.signer=由同伴簽署，並可簽署同伴(限制已取消)
 offerbook.timeSinceSigning.daysSinceSigning={0} 天
-offerbook.timeSinceSigning.daysSinceSigning.long={0} since signing
+offerbook.timeSinceSigning.daysSinceSigning.long=自簽署{0}
 
-offerbook.timeSinceSigning.help=When you successfully complete a trade with a peer who has a signed payment account, your payment account is signed.\n{0} days later, the initial limit of {1} is lifted and your account can sign other peers'' payment accounts.
-offerbook.timeSinceSigning.notSigned=Not signed yet
+offerbook.timeSinceSigning.help=當您成功地完成與擁有已簽字付款帳戶的夥伴交易時，您的付款帳戶已簽字。\n{0} 天后,最初的 {1} 的限制解除以及你的賬戶可以簽署其他夥伴的”付款賬戶。
+offerbook.timeSinceSigning.notSigned=尚未簽字
 offerbook.timeSinceSigning.notSigned.noNeed=N/A
-shared.notSigned=This account hasn't been signed yet
-shared.notSigned.noNeed=This account type doesn't use signing
+shared.notSigned=此賬戶還沒有被簽署
+shared.notSigned.noNeed=此賬戶類型不使用簽名
 
 offerbook.nrOffers=委託數量：{0}
 offerbook.volume={0}（最小 - 最大）
@@ -374,12 +374,12 @@ offerbook.warning.noTradingAccountForCurrency.msg=選擇的貨幣沒有交易賬
 offerbook.warning.noMatchingAccount.headline=沒有匹配的交易賬戶。
 offerbook.warning.noMatchingAccount.msg=為了接受這個報價，你需要用這個付款方式建立一個付款賬戶。\n\n你現在想做這件事嗎？
 
-offerbook.warning.counterpartyTradeRestrictions=This offer cannot be taken due to counterparty trade restrictions
+offerbook.warning.counterpartyTradeRestrictions=由於交易夥伴的交易限制，這個報價不能接受
 
-offerbook.warning.newVersionAnnouncement=With this version of the software, trading peers can verify and sign each others' payment accounts to create a network of trusted payment accounts.\n\nAfter successfully trading with a peer with a verified payment account, your payment account will be signed and trading limits will be lifted after a certain time interval (length of this interval is based on the verification method).\n\nFor more information on account signing, please see the documentation at https://docs.bisq.network/payment-methods#account-signing.
+offerbook.warning.newVersionAnnouncement=使用這個版本的軟體，交易夥伴可以驗證和簽署彼此的支付帳戶，以建立一個可信的支付帳戶網路。\n\n交易成功後，您的支付帳戶將被簽署以及交易限制將在一定時間後解除（此時間基於驗證方法）。\n\n有關簽署帳戶的更多資訊，請參見文件 https://docs.bisq.network/payment-methods#account-signing
 
-popup.warning.tradeLimitDueAccountAgeRestriction.seller=The allowed trade amount is limited to {0} because of security restrictions based on the following criteria:\n- The buyer''s account has not been signed by an arbitrator or a peer\n- The time since signing of the buyer''s account is not at least 30 days\n- The payment method for this offer is considered risky for bank chargebacks\n\n{1}
-popup.warning.tradeLimitDueAccountAgeRestriction.buyer=The allowed trade amount is limited to {0} because of security restrictions based on the following criteria:\n- Your account has not been signed by an arbitrator or a peer\n- The time since signing of your account is not at least 30 days\n- The payment method for this offer is considered risky for bank chargebacks\n\n{1}
+popup.warning.tradeLimitDueAccountAgeRestriction.seller=基於以下標準的安全限制，允許的交易金額限制為 {0}：\n- 買方的帳目沒有由仲裁員或夥伴簽署\n- 買方帳戶自簽署之日起不足30天\n- 本報價的付款方式被認為存在銀行退款的風險\n\n{1}
+popup.warning.tradeLimitDueAccountAgeRestriction.buyer=基於以下標準的安全限制，允許的交易金額限制為{0}：\n- 你的買家帳戶沒有由仲裁員或夥伴簽署\n- 自簽署你的帳戶以來的時間少於30天\n- 本報價的付款方式被認為存在銀行退款的風險\n\n{1}
 
 offerbook.warning.wrongTradeProtocol=該委託要求的軟體版本與您現在執行的版本不一致。\n\n請檢查您是否執行最新版本，否則該委託使用者在使用一箇舊的版本。\n使用者不能與不相容的交易協議版本進行交易。
 offerbook.warning.userIgnored=您已新增該使用者的匿名地址在您的忽略列表裡。
@@ -505,7 +505,7 @@ takeOffer.failed.offerTaken=您不能對該委託下單，因為該委託已經
 takeOffer.failed.offerRemoved=您不能對該委託下單，因為該委託已經在此期間被刪除。
 takeOffer.failed.offererNotOnline=下單失敗，因為賣家已經不線上。
 takeOffer.failed.offererOffline=您不能下單，因為賣家已經下線。
-takeOffer.warning.connectionToPeerLost=You lost connection to the maker.\nThey might have gone offline or has closed the connection to you because of too many open connections.\n\nIf you can still see their offer in the offerbook you can try to take the offer again.
+takeOffer.warning.connectionToPeerLost=您與賣家失去連線。\n因為太多連線，他或許已經下線或者關掉了與您的連線。\n\n如果您還是能在委託列表中看到他的委託，您可以再次嘗試下單。
 
 takeOffer.error.noFundsLost=\n\n你的錢包裡還沒有錢。 \n請嘗試重啟您的應用程式或者檢查您的網路連線。
 takeOffer.error.feePaid=\n\n請嘗試重啟您的應用程式或者檢查您的網路連線。
@@ -543,8 +543,8 @@ portfolio.pending.step3_seller.confirmPaymentReceived=確定收到付款
 portfolio.pending.step5.completed=完成
 
 portfolio.pending.step1.info=存款交易已經發布。\n開始付款之前，{0} 需要等待至少一個塊鏈確認。
-portfolio.pending.step1.warn=The deposit transaction is still not confirmed. This sometimes happens in rare cases when the funding fee of one trader from an external wallet was too low.
-portfolio.pending.step1.openForDispute=The deposit transaction is still not confirmed. You can wait longer or contact the mediator for assistance.
+portfolio.pending.step1.warn=保證金交易仍未得到確認。這種情況可能會發生在外部錢包轉賬時使用的交易手續費用較低造成的。
+portfolio.pending.step1.openForDispute=保證金交易仍未得到確認。請聯絡調解員協助。
 
 # suppress inspection "TrailingSpacesInProperty"
 portfolio.pending.step2.confReached=您的交易已經達到至少一個塊鏈確認。\n（如果需要，您可以等待更多的確認 - 6個確認被認為是非常安全的。）\n\n
@@ -580,8 +580,8 @@ portfolio.pending.step2_buyer.amountToTransfer=劃轉數量
 portfolio.pending.step2_buyer.sellersAddress=賣家的 {0} 地址
 portfolio.pending.step2_buyer.buyerAccount=您的付款帳戶將被使用
 portfolio.pending.step2_buyer.paymentStarted=付款開始
-portfolio.pending.step2_buyer.warn=You still have not done your {0} payment!\nPlease note that the trade has to be completed by {1}.
-portfolio.pending.step2_buyer.openForDispute=You have not completed your payment!\nThe max. period for the trade has elapsed.Please contact the mediator for assistance.
+portfolio.pending.step2_buyer.warn=你還沒有完成你的 {0} 付款！\n請注意，交易必須在 {1} 之前完成。
+portfolio.pending.step2_buyer.openForDispute=您還沒有完成您的付款！\n最大交易期限已過。請聯絡調解員尋求幫助。
 portfolio.pending.step2_buyer.paperReceipt.headline=您是否將紙質收據傳送給 BTC 賣家？
 portfolio.pending.step2_buyer.paperReceipt.msg=請牢記：\n完成付款後在紙質收據上寫下：不退款。\n然後將其撕成2份，拍照片併發送給 BTC 賣家的電子郵件地址。
 portfolio.pending.step2_buyer.moneyGramMTCNInfo.headline=傳送授權編號和收據
@@ -599,11 +599,11 @@ portfolio.pending.step2_seller.waitPayment.headline=等待付款
 portfolio.pending.step2_seller.f2fInfo.headline=買家的合同資訊
 portfolio.pending.step2_seller.waitPayment.msg=存款交易至少有一個區塊鏈確認。\n您需要等到 BTC 買家開始 {0} 付款。
 portfolio.pending.step2_seller.warn=BTC 買家仍然沒有完成 {0} 付款。\n你需要等到他開始付款。\n如果 {1} 交易尚未完成，仲裁員將進行調查。
-portfolio.pending.step2_seller.openForDispute=The BTC buyer has not started their payment!\nThe max. allowed period for the trade has elapsed.\nYou can wait longer and give the trading peer more time or contact the mediator for assistance.
+portfolio.pending.step2_seller.openForDispute=BTC 買家尚未開始付款！\n最大允許的交易期限已經過去了。\n你可以繼續等待給予交易雙方更多時間，或聯絡仲裁員以爭取解決糾紛。
 
-tradeChat.chatWindowTitle=Chat window for trade with ID ''{0}''
-tradeChat.openChat=Open chat window
-tradeChat.rules=You can communicate with your trade peer to resolve potential problems with this trade.\nIt is not mandatory to reply in the chat.\nIf a trader violates any of the rules below, open a dispute and report it to the mediator or arbitrator.\n\nChat rules:\n\t● Do not send any links (risk of malware). You can send the transaction ID and the name of a block explorer.\n\t● Do not send your seed words, private keys, passwords or other sensitive information!\n\t● Do not encourage trading outside of Bisq (no security).\n\t● Do not engage in any form of social engineering scam attempts.\n\t● If a peer is not responding and prefers to not communicate via chat, respect their decision.\n\t● Keep conversation scope limited to the trade. This chat is not a messenger replacement or troll-box.\n\t● Keep conversation friendly and respectful.
+tradeChat.chatWindowTitle=使用 ID “{0}” 進行交易的聊天視窗
+tradeChat.openChat=開啟聊天視窗
+tradeChat.rules=您可以與您的夥伴溝通，以解決該交易的潛在問題。\n在聊天中不強制回覆。\n如果交易員違反了下面的任何規則，開啟糾紛並向調解員或仲裁員報告。\n聊天規則：\n\n\t●不要傳送任何連結（有惡意軟體的風險）。您可以傳送交易 ID 和區塊資源管理器的名稱。\n\t●不要傳送種子詞、私鑰、密碼或其他敏感資訊！\n\t●不鼓勵 Bisq 以外的交易（無安全保障）。\n\t●不要參與任何形式的危害社會安全的計劃。\n\t●如果對方沒有迴應，也不願意通過聊天進行溝通，那就尊重對方的決定。\n\t●將談話範圍限制在行業內。這個聊天不是一個社交軟體替代品或troll-box。\n\t●保持友好和尊重的交談。
 
 # suppress inspection "UnusedProperty"
 message.state.UNDEFINED=未定義
@@ -612,7 +612,7 @@ message.state.SENT=發出資訊
 # suppress inspection "UnusedProperty"
 message.state.ARRIVED=訊息抵達對等點
 # suppress inspection "UnusedProperty"
-message.state.STORED_IN_MAILBOX=Message of payment sent but not yet received by peer
+message.state.STORED_IN_MAILBOX=已傳送但尚未被夥伴接收的付款資訊
 # suppress inspection "UnusedProperty"
 message.state.ACKNOWLEDGED=對等確認訊息接收
 # suppress inspection "UnusedProperty"
@@ -623,8 +623,8 @@ portfolio.pending.step3_buyer.wait.info=等待 BTC 賣家確認收到 {0} 付款
 portfolio.pending.step3_buyer.wait.msgStateInfo.label=支付開始訊息狀態
 portfolio.pending.step3_buyer.warn.part1a=在 {0} 區塊鏈
 portfolio.pending.step3_buyer.warn.part1b=在您的支付供應商（例如：銀行）
-portfolio.pending.step3_buyer.warn.part2=The BTC seller still has not confirmed your payment. Please check {0} if the payment sending was successful.
-portfolio.pending.step3_buyer.openForDispute=The BTC seller has not confirmed your payment! The max. period for the trade has elapsed. You can wait longer and give the trading peer more time or request assistance from the mediator.
+portfolio.pending.step3_buyer.warn.part2=BTC 賣家仍然沒有確認您的付款。如果付款傳送成功，請檢查 {0}。
+portfolio.pending.step3_buyer.openForDispute=BTC賣家還沒有確認你的付款!最大交易期限已過。您可以等待更長時間，並給交易夥伴更多時間或請求調解員的幫助。
 # suppress inspection "TrailingSpacesInProperty"
 portfolio.pending.step3_seller.part=您的交易夥伴已經確認他們已經發起了 {0} 付款。\n\n
 portfolio.pending.step3_seller.altcoin.explorer=在您最喜歡的 {0} 區塊鏈瀏覽器
@@ -638,8 +638,8 @@ portfolio.pending.step3_seller.moneyGram=買方必須傳送授權編碼和一張
 portfolio.pending.step3_seller.westernUnion=買方必須傳送 MTCN（跟蹤號碼）和一張收據的照片。\n收據必須清楚地顯示您的全名、城市、國家、數量。如果您收到 MTCN，請查收郵件。\n\n關閉彈窗後，您將看到 BTC 買家的姓名和在 Western Union 的收款地址。\n\n只有在您成功收到錢之後，再確認收據！
 portfolio.pending.step3_seller.halCash=買方必須將 HalCash程式碼 用簡訊傳送給您。除此之外，您將收到來自 HalCash 的訊息，其中包含從支援 HalCash 的 ATM 中提取歐元所需的資訊\n從 ATM 取款後，請在此確認付款收據！
 
-portfolio.pending.step3_seller.bankCheck=\n\nPlease also verify that the name of the sender specified on the trade contract matches the name that appears on your bank statement:\nSender''s name, per trade contract: {0}\n\nIf the names are not exactly the same, {1}
-portfolio.pending.step3_seller.openDispute=don't confirm payment receipt. Instead, open a dispute by pressing \"alt + o\" or \"option + o\".\n\n
+portfolio.pending.step3_seller.bankCheck=\n\n還請確認您的銀行對帳單中的發件人姓名與委託合同中的發件人姓名相符：\n發件人姓名：{0}\n\n如果名稱與此處顯示的名稱不同，則 {1}
+portfolio.pending.step3_seller.openDispute=請不要確認，而是通過鍵盤組合鍵“alt + o”或“option + o”來開啟糾紛。
 portfolio.pending.step3_seller.confirmPaymentReceipt=確定付款收據
 portfolio.pending.step3_seller.amountToReceive=接收數量：
 portfolio.pending.step3_seller.yourAddress=您的 {0} 地址
@@ -652,18 +652,18 @@ portfolio.pending.step3_seller.buyerStartedPayment.altcoin=檢查您的數字貨
 portfolio.pending.step3_seller.buyerStartedPayment.fiat=檢查您的交易賬戶（例如銀行帳戶），並確認您何時收到付款。
 portfolio.pending.step3_seller.warn.part1a=在 {0} 區塊鏈
 portfolio.pending.step3_seller.warn.part1b=在您的支付供應商（例如：銀行）
-portfolio.pending.step3_seller.warn.part2=You still have not confirmed the receipt of the payment. Please check {0} if you have received the payment.
-portfolio.pending.step3_seller.openForDispute=You have not confirmed the receipt of the payment!\nThe max. period for the trade has elapsed.\nPlease confirm or request assistance from the mediator.
+portfolio.pending.step3_seller.warn.part2=你還沒有確認收到款項。如果您已經收到款項，請檢查 {0}。
+portfolio.pending.step3_seller.openForDispute=您尚未確認付款的收據！\n最大交易期已過\n請確認或請求調解員的協助。
 # suppress inspection "TrailingSpacesInProperty"
 portfolio.pending.step3_seller.onPaymentReceived.part1=您是否收到了您交易夥伴的 {0} 付款？\n\n
 # suppress inspection "TrailingSpacesInProperty"
 portfolio.pending.step3_seller.onPaymentReceived.fiat=交易 ID（“付款理由”文字）是“{0}”\n\n
 # suppress inspection "TrailingSpacesInProperty"
-portfolio.pending.step3_seller.onPaymentReceived.name=Please also verify that the name of the sender specified on the trade contract matches the name that appears on your bank statement:\nSender''s name, per trade contract: {0}\n\nIf the names are not exactly the same, don''t confirm payment receipt. Instead, open a dispute by pressing \"alt + o\" or \"option + o\".\n\n
-portfolio.pending.step3_seller.onPaymentReceived.note=Please note, that as soon you have confirmed the receipt, the locked trade amount will be released to the BTC buyer and the security deposit will be refunded.\n\n
+portfolio.pending.step3_seller.onPaymentReceived.name=還請確認您的銀行對帳單中的發件人姓名與委託合同中的發件人姓名相符：\n每個交易合約的傳送者姓名：{0}\n\n如果名稱與此處顯示的名稱不一致，請不要通過確認付款，而是通過“alt + o”或“option + o”開啟糾紛。\n\n
+portfolio.pending.step3_seller.onPaymentReceived.note=請注意，一旦您確認收到，凍結交易金額將被髮放給 BTC 買家，保證金將被退還。
 portfolio.pending.step3_seller.onPaymentReceived.confirm.headline=確定您已經收到付款
 portfolio.pending.step3_seller.onPaymentReceived.confirm.yes=是的，我已經收到付款。
-portfolio.pending.step3_seller.onPaymentReceived.signer=IMPORTANT: By confirming receipt of payment, you are also verifying the account of the counterparty and signing it accordingly. Since the account of the counterparty hasn't been signed yet, you should delay confirmation of the payment as long as possible to reduce the risk of a chargeback.
+portfolio.pending.step3_seller.onPaymentReceived.signer=重要提示:通過確認收到付款，你也驗證了對方的賬戶，並獲得簽字。因為對方的賬戶還沒有簽字，所以你應該儘可能的延遲付款的確認，以減少退款的風險。
 
 portfolio.pending.step5_buyer.groupTitle=完成交易的概要
 portfolio.pending.step5_buyer.tradeFee=掛單費
@@ -699,56 +699,56 @@ portfolio.pending.tradePeriodInfo=在第一次區塊鏈確認之後，交易週
 portfolio.pending.tradePeriodWarning=如果超過了這個週期，雙方均可以提出糾紛。
 portfolio.pending.tradeNotCompleted=交易不會及時完成（直到 {0} ）
 portfolio.pending.tradeProcess=交易流程
-portfolio.pending.openAgainDispute.msg=If you are not sure that the message to the mediator or arbitrator arrived (e.g. if you did not get a response after 1 day) feel free to open a dispute again with Cmd/Ctrl+o. You can also ask for additional help on the Bisq forum at https://bisq.community.
+portfolio.pending.openAgainDispute.msg=如果您不確定傳送給調解員或仲裁員的訊息是否已送達（例如，如果您在1天后沒有收到回覆），請放心使用 Cmd/Ctrl+o 再次開啟糾紛。你也可以在 Bisq 論壇上尋求額外的幫助，網址是 https://bisq.community。
 portfolio.pending.openAgainDispute.button=再次出現糾紛
 portfolio.pending.openSupportTicket.headline=建立幫助話題
-portfolio.pending.openSupportTicket.msg=Please use this function only in emergency cases if you don't see a \"Open support\" or \"Open dispute\" button.\n\nWhen you open a support ticket the trade will be interrupted and handled by a mediator or arbitrator.
+portfolio.pending.openSupportTicket.msg=請僅在緊急情況下使用此功能，如果您沒有看到“提交支援”或“提交糾紛”按鈕。\n\n當您發出工單時，交易將被中斷並由調解員或仲裁員進行處理。
 
-portfolio.pending.timeLockNotOver=You have to wait until ≈{0} ({1} more blocks) before you can open an arbitration dispute.
-portfolio.pending.error.depositTxNull=The deposit transaction is null. You cannot open a dispute without a valid deposit transaction. Please go to \"Settings/Network info\" and do a SPV resync.\n\nFor further help please contact the Bisq support channel at the Bisq Keybase team.
-portfolio.pending.mediationResult.error.depositTxNull=The deposit transaction is null. The trade gets moved to the failed trades section.
-portfolio.pending.error.depositTxNotConfirmed=The deposit transaction is not confirmed. You can not open an arbitration dispute with an unconfirmed deposit transaction. Please wait until it is confirmed or go to \"Settings/Network info\" and do a SPV resync.\n\nFor further help please contact the Bisq support channel at the Bisq Keybase team.
+portfolio.pending.timeLockNotOver=你必須等到≈{0}(還需等待{1}個區塊)才能提交糾紛。
+portfolio.pending.error.depositTxNull=保證金交易無效。沒有有效的保證金交易，你使用建立糾紛。請到“設定/網路資訊”進行 SPV 重新同步。\n \n如需更多幫助，請聯絡 Bisq Keybase 團隊的 Support 頻道。
+portfolio.pending.mediationResult.error.depositTxNull=保證金交易無效。交易被移至失敗交易。
+portfolio.pending.error.depositTxNotConfirmed=保證金交易未確認。未經確認的存款交易不能發起糾紛或仲裁請求。請耐心等待，直到它被確認或進入“設定/網路資訊”進行 SPV 重新同步。\n\n如需更多幫助，請聯絡 Bisq Keybase 團隊的 Support 頻道。
 
 portfolio.pending.notification=通知
 
-portfolio.pending.support.headline.getHelp=Need help?
-portfolio.pending.support.text.getHelp=If you have any problems you can try to contact the trade peer in the trade chat or ask the Bisq community at https://bisq.community. If your issue still isn't resolved, you can request more help from a mediator.
-portfolio.pending.support.text.getHelp.arbitrator=If you have any problems you can try to contact the trade peer in the trade chat or ask the Bisq community at https://bisq.community. If your issue still isn't resolved, you can request more help from an arbitrator.
-portfolio.pending.support.button.getHelp=Get support
-portfolio.pending.support.popup.info=If your issue with the trade remains unsolved, you can open a support ticket to request help from a mediator. If you have not received the payment, please wait until the trade period is over.\n\nAre you sure you want to open a support ticket?
+portfolio.pending.support.headline.getHelp=需要幫助？
+portfolio.pending.support.text.getHelp=如果您有任何問題，您可以嘗試在交易聊天中聯絡交易夥伴，或在 https://bisq.community 詢問 Bisq 社群。如果您的問題仍然沒有解決，您可以向調解員取得更多的幫助。
+portfolio.pending.support.text.getHelp.arbitrator=如果您有任何問題，您可以嘗試在交易聊天中聯絡交易夥伴，或在 https://bisq.community 詢問 Bisq 社群。如果你的問題仍然沒有解決，你可以向仲裁員取得更多的幫助。
+portfolio.pending.support.button.getHelp=獲取幫助
+portfolio.pending.support.popup.info=如果您與交易的問題仍然沒有解決，您可以提交工單來請求調解員的幫助。如果您還沒有收到付款，請等到交易結束。\n\n您確定要提交工單嗎?
 portfolio.pending.support.popup.button=建立幫助話題
-portfolio.pending.support.headline.halfPeriodOver=Check payment
-portfolio.pending.support.headline.periodOver=Trade period is over
+portfolio.pending.support.headline.halfPeriodOver=確認付款
+portfolio.pending.support.headline.periodOver=交易期結束
 
-portfolio.pending.mediationRequested=Mediation requested
-portfolio.pending.refundRequested=Refund requested
+portfolio.pending.mediationRequested=已請求調解員協助
+portfolio.pending.refundRequested=已請求退款
 portfolio.pending.openSupport=建立幫助話題
 portfolio.pending.supportTicketOpened=幫助話題已經建立
 portfolio.pending.requestSupport=請求幫助
-portfolio.pending.error.requestSupport=Please report the problem to your mediator or arbitrator.\n\nThey will forward the information to the developers to investigate the problem.\nAfter the problem has been analyzed you will get back all locked funds.
+portfolio.pending.error.requestSupport=請將問題報告給您的調解員或仲裁員。\n\n他會將資訊轉交給開發人員調查問題。\n在解決問題後，您將收回所有凍結資金。
 portfolio.pending.communicateWithArbitrator=請在“幫助”介面上與仲裁員聯絡。
-portfolio.pending.communicateWithMediator=Please communicate in the \"Support\" screen with the mediator.
+portfolio.pending.communicateWithMediator=請在“支援”頁面中與調解員進行聯絡。
 portfolio.pending.supportTicketOpenedMyUser=您建立了一個幫助話題。\n{0}
 portfolio.pending.disputeOpenedMyUser=您建立了一個糾紛。\n{0}
 portfolio.pending.disputeOpenedByPeer=您的交易物件建立了一個糾紛。\n{0}
 portfolio.pending.supportTicketOpenedByPeer=您的交易物件建立了一個幫助工單。\n{0}
 portfolio.pending.noReceiverAddressDefined=沒有定義接收地址
-portfolio.pending.removeFailedTrade=Is this a failed trade? If so, would you like to manually close it, so that it no longer shows as an open trade?
+portfolio.pending.removeFailedTrade=這是一筆失敗的交易嗎？如果是，請問你想手動關閉它嗎？使它不再顯示為一個未完成交易。
 
-portfolio.pending.mediationResult.headline=Suggested payout from mediation
-portfolio.pending.mediationResult.info.noneAccepted=Complete the trade by accepting the mediator's suggestion for the trade payout.
-portfolio.pending.mediationResult.info.selfAccepted=You have accepted the mediator's suggestion. Waiting for peer to accept as well.
-portfolio.pending.mediationResult.info.peerAccepted=Your trade peer has accepted the mediator's suggestion. Do you accept as well?
-portfolio.pending.mediationResult.button=View proposed resolution
-portfolio.pending.mediationResult.popup.headline=Mediation result for trade with ID: {0}
-portfolio.pending.mediationResult.popup.headline.peerAccepted=Your trade peer has accepted the mediator''s suggestion for trade {0}
-portfolio.pending.mediationResult.popup.info=The mediator has suggested the following payout:\nYou receive: {0}\nYour trading peer receives: {1}\n\nYou can accept or reject this suggested payout.\n\nBy accepting, you sign the proposed payout transaction. If your trading peer also accepts and signs, the payout will be completed, and the trade will be closed.\n\nIf one or both of you reject the suggestion, you will have to wait until {2} (block {3}) to open a second-round dispute with an arbitrator who will investigate the case again and do a payout based on their findings.\n\nThe arbitrator may charge a small fee (fee maximum: the trader''s security deposit) as compensation for their work. Both traders agreeing to the mediator''s suggestion is the happy path—requesting arbitration is meant for exceptional circumstances, such as if a trader is sure the mediator did not make a fair payout suggestion (or if the other peer is unresponsive).\n\nMore details about the new arbitration model:\nhttps://docs.bisq.network/trading-rules.html#arbitration
-portfolio.pending.mediationResult.popup.openArbitration=Reject and request arbitration
-portfolio.pending.mediationResult.popup.alreadyAccepted=You've already accepted
+portfolio.pending.mediationResult.headline=調解費用的支出
+portfolio.pending.mediationResult.info.noneAccepted=通過接受調解員關於交易的建議的支出來完成交易。
+portfolio.pending.mediationResult.info.selfAccepted=你已經接受了調解員的建議。等待夥伴接受。
+portfolio.pending.mediationResult.info.peerAccepted=你的夥伴已經接受了調解員的建議。你也接受嗎?
+portfolio.pending.mediationResult.button=檢視建議的解決方案
+portfolio.pending.mediationResult.popup.headline=調解員在交易 ID：{0}上的建議
+portfolio.pending.mediationResult.popup.headline.peerAccepted=你的夥伴已經接受了調解員的建議
+portfolio.pending.mediationResult.popup.info=調解員建議的支出如下：\n你將支付：{0}\n你的交易夥伴將支付：{1}\n\n你可以接受或拒絕這筆調解費支出。\n\n通過接受，你簽署了合約的支付交易。如果你的交易夥伴也接受和簽署，支付將完成，交易將關閉。\n\n如果你們其中一人或雙方都拒絕該建議，你將必須等到（2）（{3}區塊）與仲裁員展開第二輪糾紛討論，仲裁員將再次調查該案件，並根據他們的調查結果進行支付。\n\n仲裁員可以收取少量費用（費用上限：交易的保證金）作為其工作的補償。兩個交易者都同意調解員的建議是愉快的路徑請求仲裁是針對特殊情況的，比如如果一個交易者確信調解員沒有提出公平的賠償建議（或者如果另一個同伴沒有迴應）。\n\n關於新的仲裁模型的更多細節：https://docs.bisq.network/trading-rules.html#arbitration
+portfolio.pending.mediationResult.popup.openArbitration=拒絕並請求仲裁
+portfolio.pending.mediationResult.popup.alreadyAccepted=您已經接受了。
 
 portfolio.closed.completed=完成
-portfolio.closed.ticketClosed=Arbitrated
-portfolio.closed.mediationTicketClosed=Mediated
+portfolio.closed.ticketClosed=已仲裁
+portfolio.closed.mediationTicketClosed=已調解
 portfolio.closed.canceled=已取消
 portfolio.failed.Failed=失敗
 
@@ -811,9 +811,9 @@ funds.tx.multiSigDeposit=多重簽名保證金：{0}
 funds.tx.multiSigPayout=多重簽名花費：{0}
 funds.tx.disputePayout=糾紛花費：{0}
 funds.tx.disputeLost=失敗的糾紛案件：{0}
-funds.tx.collateralForRefund=Refund collateral: {0}
-funds.tx.timeLockedPayoutTx=Time locked payout tx: {0}
-funds.tx.refund=Refund from arbitration: {0}
+funds.tx.collateralForRefund=押金退款：{0}
+funds.tx.timeLockedPayoutTx=距鎖定鎖定支付 tx 的時間: {0}
+funds.tx.refund=仲裁退款：{0}
 funds.tx.unknown=未知原因：{0}
 funds.tx.noFundsFromDispute=沒有退款的糾紛
 funds.tx.receivedFunds=收到的資金：
@@ -834,15 +834,15 @@ funds.tx.dustAttackTx.popup=這筆交易是傳送一個非常小的比特幣金
 # Support
 ####################################################################
 
-support.tab.mediation.support=Mediation
-support.tab.arbitration.support=Arbitration
-support.tab.legacyArbitration.support=Legacy Arbitration
-support.tab.ArbitratorsSupportTickets={0}'s tickets
+support.tab.mediation.support=調解
+support.tab.arbitration.support=仲裁
+support.tab.legacyArbitration.support=歷史仲裁
+support.tab.ArbitratorsSupportTickets={0} 的工單
 support.filter=過濾列表
 support.filter.prompt=輸入 交易 ID、日期、洋蔥地址或賬戶資訊
 support.noTickets=沒有建立的話題
 support.sendingMessage=傳送訊息...
-support.receiverNotOnline=Receiver is not online. Message is saved to their mailbox.
+support.receiverNotOnline=收件人未線上。訊息被儲存到他們的郵箱。
 support.sendMessageError=傳送訊息失敗。錯誤：{0}
 support.wrongVersion=糾紛中的訂單創建於一箇舊版本的 Bisq。\n您不能在當前版本關閉這個糾紛。\n\n請您使用一箇舊版本與協議版本 {0}
 support.openFile=開啟附件檔案（檔案最大大小：{0} kb）
@@ -852,7 +852,7 @@ support.attachment=附件
 support.tooManyAttachments=您不能傳送一個訊息裡超過3個附件。
 support.save=儲存檔案到磁碟
 support.messages=訊息
-support.input.prompt=Enter message...
+support.input.prompt=輸入訊息...
 support.send=傳送
 support.addAttachments=新增附件
 support.closeTicket=關閉話題
@@ -872,17 +872,17 @@ support.sellerOfferer=BTC 賣家/掛單者
 support.buyerTaker=BTC 買家/買單者
 support.sellerTaker=BTC 賣家/買單者
 
-support.backgroundInfo=Bisq is not a company, so it handles disputes differently.\n\nTraders can communicate within the application via secure chat on the open trades screen to try solving disputes on their own. If that is not sufficient, a mediator can step in to help. The mediator will evaluate the situation and suggest a payout of trade funds. If both traders accept this suggestion, the payout transaction is completed and the trade is closed. If one or both traders do not agree to the mediator's suggested payout, they can request arbitration.The arbitrator will re-evaluate the situation and, if warranted, personally pay the trader back and request reimbursement for this payment from the Bisq DAO.
-support.initialInfo=Please enter a description of your problem in the text field below. Add as much information as possible to speed up dispute resolution time.\n\nHere is a check list for information you should provide:\n\t● If you are the BTC buyer: Did you make the Fiat or Altcoin transfer? If so, did you click the 'payment started' button in the application?\n\t● If you are the BTC seller: Did you receive the Fiat or Altcoin payment? If so, did you click the 'payment received' button in the application?\n\t● Which version of Bisq are you using?\n\t● Which operating system are you using?\n\t● If you encountered an issue with failed transactions please consider switching to a new data directory.\n\t  Sometimes the data directory gets corrupted and leads to strange bugs. \n\t  See: https://docs.bisq.network/backup-recovery.html#switch-to-a-new-data-directory\n\nPlease make yourself familiar with the basic rules for the dispute process:\n\t● You need to respond to the {0}''s requests within 2 days.\n\t● Mediators respond in between 2 days. Arbitrators respond in between 5 business days.\n\t● The maximum period for a dispute is 14 days.\n\t● You need to cooperate with the {1} and provide the information they request to make your case.\n\t● You accepted the rules outlined in the dispute document in the user agreement when you first started the application.\n\nYou can read more about the dispute process at: {2}
+support.backgroundInfo=Bisq 不是一家公司，所以它處理糾紛的方式不同。\n\n交易雙方可以在應用程式中通過未完成交易頁面上的安全聊天進行通訊，以嘗試自行解決爭端。如果這還不夠，調解員可以介入幫助。調解員將對情況進行評估，並對交易資金的支出提出建議。如果兩個交易者都接受這個建議，那麼支付交易就完成了，交易也結束了。如果一方或雙方不同意調解員的建議，他們可以要求仲裁。仲裁員將重新評估情況，如果有必要，將親自向交易員付款，並要求 Bisq DAO 對這筆付款進行補償。
+support.initialInfo=請在下面的文字框中輸入您的問題描述。新增儘可能多的資訊，以加快解決糾紛的時間。\n\n以下是你應提供的資料核對表：\n\t●如果您是 BTC 買家：您是否使用法定貨幣或其他加密貨幣轉賬？如果是，您是否點選了應用程式中的“支付開始”按鈕？\n\t●如果您是 BTC 賣家：您是否收到法定貨幣或其他加密貨幣的付款了？如果是，你是否點選了應用程式中的“已收到付款”按鈕？\n\t●您使用的是哪個版本的 Bisq？\n\t●您使用的是哪種作業系統？\n\t●如果遇到操作執行失敗的問題，請考慮切換到新的資料目錄。\n\t有時資料目錄會損壞，並導致奇怪的錯誤。\n詳見：https://docs.bisq.network/backup-recovery.html#switch-to-a-new-data-directory\n\n請熟悉糾紛處理的基本規則：\n\t●您需要在2天內答覆 {0} 的請求。\n\t●調解員會在2天之內答覆，仲裁員會在5天之內答覆。\n\t●糾紛的最長期限為14天。\n\t●你需要與仲裁員合作，提供他們為你的案件所要求的資訊。\n\t●當您第一次啟動應用程式時，您接受了使用者協議中爭議文件中列出的規則。\n\n您可以通過 {2} 瞭解有關糾紛處理的更多資訊
 support.systemMsg=系統訊息：{0}
 support.youOpenedTicket=您建立了幫助請求。\n\n{0}\n\nBisq 版本：{1}
 support.youOpenedDispute=您建立了一個糾紛請求。\n\n{0}\n\nBisq 版本：{1}
-support.youOpenedDisputeForMediation=You requested mediation.\n\n{0}\n\nBisq version: {1}
-support.peerOpenedTicket=Your trading peer has requested support due to technical problems.\n\n{0}\n\nBisq version: {1}
-support.peerOpenedDispute=Your trading peer has requested a dispute.\n\n{0}\n\nBisq version: {1}
-support.peerOpenedDisputeForMediation=Your trading peer has requested mediation.\n\n{0}\n\nBisq version: {1}
-support.mediatorsDisputeSummary=System message:\nMediator''s dispute summary:\n{0}
-support.mediatorsAddress=Mediator''s node address: {0}
+support.youOpenedDisputeForMediation=您建立了一個調解請求。\n\n{0}\n\nBisq 版本：{1}
+support.peerOpenedTicket=您的同伴因技術問題獲取幫助。\n\n{0}\n\nBisq 版本：{1}
+support.peerOpenedDispute=您的交易夥伴建立了一個糾紛請求。\n\n{0}\n\nBisq 版本：{1}
+support.peerOpenedDisputeForMediation=您的交易夥伴建立了一個調解請求。\n\n{0}\n\nBisq 版本：{1}
+support.mediatorsDisputeSummary=系統訊息：\n調解糾紛總結：\n{0}
+support.mediatorsAddress=仲裁員的節點地址：{0}
 
 
 ####################################################################
@@ -917,7 +917,7 @@ setting.preferences.addAltcoin=新增數字貨幣
 setting.preferences.displayOptions=顯示選項
 setting.preferences.showOwnOffers=在委託列表中顯示我的委託
 setting.preferences.useAnimations=使用動畫
-setting.preferences.useDarkMode=Use dark mode (beta)
+setting.preferences.useDarkMode=使用夜間模式（beta）
 setting.preferences.sortWithNumOffers=使用“委託ID/交易ID”篩選列表
 setting.preferences.resetAllFlags=重置所有“不再提示”的提示
 setting.preferences.reset=重置
@@ -927,7 +927,7 @@ settings.preferences.selectCurrencyNetwork=選擇網路
 setting.preferences.daoOptions=DAO 選項
 setting.preferences.dao.resync.label=從 genesis tx 重構 DAO 狀態
 setting.preferences.dao.resync.button=重新同步
-setting.preferences.dao.resync.popup=After an application restart the Bisq network governance data will be reloaded from the seed nodes and the BSQ consensus state will be rebuilt from the genesis transaction.
+setting.preferences.dao.resync.popup=應用程式重新啟動後，Bisq 網路治理資料將從種子節點重新載入，而 BSQ 同步狀態將從初始交易中重新構建。
 setting.preferences.dao.isDaoFullNode=以 DAO 全節點執行 Bisq
 setting.preferences.dao.rpcUser=RPC 使用者名稱
 setting.preferences.dao.rpcPw=PRC 密碼
@@ -937,7 +937,7 @@ setting.preferences.dao.fullNodeInfo.ok=開啟文件頁面
 setting.preferences.dao.fullNodeInfo.cancel=不，我堅持使用 lite 節點模式
 
 settings.net.btcHeader=比特幣網路
-settings.net.p2pHeader=Bisq network
+settings.net.p2pHeader=Bisq 網路
 settings.net.onionAddressLabel=我的匿名地址
 settings.net.btcNodesLabel=使用自定義比特幣主節點
 settings.net.bitcoinPeersLabel=已連線節點
@@ -959,12 +959,12 @@ settings.net.totalTrafficLabel=總流量:
 settings.net.roundTripTimeColumn=延遲
 settings.net.sentBytesColumn=傳送
 settings.net.receivedBytesColumn=接收
-settings.net.peerTypeColumn=節點型別
+settings.net.peerTypeColumn=節點類型
 settings.net.openTorSettingsButton=開啟 Tor 設定
 
-settings.net.versionColumn=Version
-settings.net.subVersionColumn=Subversion
-settings.net.heightColumn=Height
+settings.net.versionColumn=版本
+settings.net.subVersionColumn=破壞？
+settings.net.heightColumn=高度
 
 settings.net.needRestart=您需要重啟應用程式以同意這次變更。\n您需要現在重啟嗎？
 settings.net.notKnownYet=至今未知...
@@ -977,17 +977,17 @@ settings.net.inbound=資料包進入
 settings.net.outbound=資料包出口
 settings.net.reSyncSPVChainLabel=重新同步 SPV 鏈
 settings.net.reSyncSPVChainButton=刪除 SPV 鏈檔案並重新同步
-settings.net.reSyncSPVSuccess=The SPV chain file will be deleted on the next startup. You need to restart your application now.\n\nAfter the restart it can take a while to resync with the network and you will only see all transactions once the resync is completed.\n\nDepending on the number of transactions and the age of your wallet the resync can take up to a few hours and consumes 100% of CPU. Do not interrupt the process otherwise you have to repeat it.
+settings.net.reSyncSPVSuccess=SPV 鏈檔案將在下一次啟動時被刪除。您現在需要重新啟動應用程式。\n\n重新啟動後，可能需要一段時間才能與網路重新同步，只有重新同步完成後才會看到所有的交易。\n\n根據交易的數量和錢包賬齡，重新同步可能會花費幾個小時，並消耗100%的 CPU。不要打斷這個過程，否則你會不斷地重複它。
 settings.net.reSyncSPVAfterRestart=SPV 鏈檔案已被刪除。請耐心等待，與網路重新同步可能需要一段時間。
 settings.net.reSyncSPVAfterRestartCompleted=重新同步剛剛完成，請重啟應用程式。
 settings.net.reSyncSPVFailed=無法刪除 SPV 鏈檔案。\n錯誤：{0}
 setting.about.aboutBisq=關於 Bisq
-setting.about.about=Bisq 是一款開源軟體，它通過分散的對等網路促進了比特幣與各國貨幣（以及其他加密貨幣）的交換，以一種強烈保護使用者隱私的方式。請到我們專案的網站閱讀更多關於 Bisq 的資訊。
+setting.about.about=Bisq 是一款開源軟體，它通過分散的對等網路促進了比特幣與各國貨幣（以及其他加密貨幣）的交換，以一種強烈保護使用者隱私的方式。請到我們項目的網站閱讀更多關於 Bisq 的資訊。
 setting.about.web=Bisq 網站
 setting.about.code=原始碼
 setting.about.agpl=AGPL 協議
 setting.about.support=支援 Bisq
-setting.about.def=Bisq 不是一個公司，而是一個社群專案，開放參與。如果您想參與或支援 Bisq，請點選下面連線。
+setting.about.def=Bisq 不是一個公司，而是一個社群項目，開放參與。如果您想參與或支援 Bisq，請點選下面連線。
 setting.about.contribute=貢獻
 setting.about.providers=資料提供商
 setting.about.apisWithFee=Bisq 使用第三方 API 獲取法定貨幣與虛擬幣的市場價以及礦工手續費的估價。
@@ -1006,11 +1006,11 @@ setting.about.subsystems.val=網路版本：{0}；P2P 訊息版本：{1}；本
 ####################################################################
 
 account.tab.arbitratorRegistration=仲裁員註冊
-account.tab.mediatorRegistration=Mediator registration
-account.tab.refundAgentRegistration=Refund agent registration
+account.tab.mediatorRegistration=調解員註冊
+account.tab.refundAgentRegistration=退款助理註冊
 account.tab.account=賬戶
 account.info.headline=歡迎來到 Bisq 賬戶
-account.info.msg=Here you can add trading accounts for national currencies & altcoins and create a backup of your wallet & account data.\n\nA new Bitcoin wallet was created the first time you started Bisq.\n\nWe strongly recommend that you write down your Bitcoin wallet seed words (see tab on the top) and consider adding a password before funding. Bitcoin deposits and withdrawals are managed in the \"Funds\" section.\n\nPrivacy & security note: because Bisq is a decentralized exchange, all your data is kept on your computer. There are no servers, so we have no access to your personal info, your funds, or even your IP address. Data such as bank account numbers, altcoin & Bitcoin addresses, etc are only shared with your trading partner to fulfill trades you initiate (in case of a dispute the mediator or arbitrator will see the same data as your trading peer).
+account.info.msg=在這裡你可以設定交易賬戶的法定貨幣及數字貨幣，選擇仲裁員和備份你的錢包及賬戶資料。\n\n當你開始執行 Bisq 就已經建立了一個空的比特幣錢包。\n\n我們建議你在充值之前寫下你比特幣錢包的還原金鑰（在左邊的列表）和考慮新增密碼。在“資金”選項中管理比特幣存入和提現。\n\n隱私 & 安全：\nBisq 是一個去中心化的交易所 – 意味著您的所有資料都儲存在您的電腦上，沒有伺服器，我們無法訪問您的個人資訊，您的資金，甚至您的 IP 地址。如銀行賬號、數字貨幣、比特幣地址等資料只分享給與您交易的人，以實現您發起的交易（如果有爭議，仲裁員將會看到您的交易資料）。
 
 account.menu.paymentAccount=法定貨幣賬戶
 account.menu.altCoinsAccountView=數字貨幣賬戶
@@ -1022,36 +1022,36 @@ account.menu.notifications=通知
 ## TODO should we rename the following to a gereric name?
 account.arbitratorRegistration.pubKey=公鑰
 
-account.arbitratorRegistration.register=Register
-account.arbitratorRegistration.registration={0} registration
+account.arbitratorRegistration.register=註冊
+account.arbitratorRegistration.registration={0} 註冊
 account.arbitratorRegistration.revoke=撤銷
-account.arbitratorRegistration.info.msg=Please note that you need to stay available for 15 days after revoking as there might be trades which are using you as {0}. The max. allowed trade period is 8 days and the dispute process might take up to 7 days.
+account.arbitratorRegistration.info.msg=請注意，撤銷後需要保留15天，因為可能有交易正在以你作為 {0}。最大允許的交易期限為8天，糾紛過程最多可能需要7天。
 account.arbitratorRegistration.warn.min1Language=您需要設定至少1種語言。\n我們已經為您添加了預設語言。
-account.arbitratorRegistration.removedSuccess=You have successfully removed your registration from the Bisq network.
-account.arbitratorRegistration.removedFailed=Could not remove registration.{0}
-account.arbitratorRegistration.registerSuccess=You have successfully registered to the Bisq network.
-account.arbitratorRegistration.registerFailed=Could not complete registration.{0}
+account.arbitratorRegistration.removedSuccess=您已從 Bisq 網路成功刪除仲裁員註冊資訊。
+account.arbitratorRegistration.removedFailed=無法刪除仲裁員。{0}
+account.arbitratorRegistration.registerSuccess=您已從 Bisq 網路成功註冊您的仲裁員。
+account.arbitratorRegistration.registerFailed=無法註冊仲裁員。{0}
 
 account.altcoin.yourAltcoinAccounts=您的數字貨幣賬戶
-account.altcoin.popup.wallet.msg=Please be sure that you follow the requirements for the usage of {0} wallets as described on the {1} web page.\nUsing wallets from centralized exchanges where (a) you don''t control your keys or (b) which don''t use compatible wallet software is risky: it can lead to loss of the traded funds!\nThe mediator or arbitrator is not a {2} specialist and cannot help in such cases.
+account.altcoin.popup.wallet.msg=請確保您按照 {1} 網頁上所述使用 {0} 錢包的要求。\n使用集中式交易所的錢包，您無法控制金鑰或使用不相容的錢包軟體，可能會導致交易資金的流失！\n調解員或仲裁員不是 {2} 專家，在這種情況下不能幫助。
 account.altcoin.popup.wallet.confirm=我瞭解並確定我知道我需要哪種錢包。
-account.altcoin.popup.upx.msg=Trading UPX on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending UPX, you need to use either the official uPlexa GUI wallet or uPlexa CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nuplexa-wallet-cli (use the command get_tx_key)\nuplexa-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The UPX sender is responsible for providing verification of the UPX transfer to the arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit uPlexa discord channel (https://discord.gg/vhdNSrV) or the uPlexa Telegram Chat (https://t.me/uplexaOfficial) to find more information.
-account.altcoin.popup.arq.msg=Trading ARQ on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending ARQ, you need to use either the official ArQmA GUI wallet or ArQmA CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\narqma-wallet-cli (use the command get_tx_key)\narqma-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the mediator or arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The ARQ sender is responsible for providing verification of the ARQ transfer to the mediator or arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit ArQmA discord channel (https://discord.gg/s9BQpJT) or the ArQmA forum (https://labs.arqma.com) to find more information.
-account.altcoin.popup.xmr.msg=Trading XMR on Bisq requires that you understand and fulfill the following requirements:\n\nProve payments: since Monero is a private coin, some transaction details aren't publicly available in the blockchain, and, in case of a dispute, the mediator or arbitrator needs them to check if the transaction was really made. In Bisq, the sender of the XMR transaction is the one responsible for providing this information to the mediator or arbitrator in case of a dispute. In order to do that, you must send XMR using a wallet that provides the information required to prove the payment was made, which includes:\n\n- the transaction key (Tx Key, Tx Secret Key or Tx Private Key)\n- the transaction ID (Tx ID or Tx Hash)\n- the destination address (recipient's address)\n\nThis information can be found in the official Monero GUI & CLI wallets, MyMonero, and Exodus (desktop) as well as in Cake Wallet, MyMonero, and Monerujo (mobile), in the following locations:\n\n- Monero GUI: go to Transactions tab\n- Monero CLI: use the command get_tx_key TXID. The flag store-tx-info must be enabled (enabled by default in new versions)\n- Other wallets: go to Transactions history and search for Transaction key (Tx key or Secret key) and the destination address in a sent transaction. Save recipient address option must be enabled in Cake Wallet settings.\n\nIf you are using a wallet different from the mentioned above, please be sure you can access those three pieces of information.Since the transaction key and the destination address are stored in the Monero wallet software, and they cannot be recovered in the Monero blockchain, you should never delete or restore your Monero wallet before a Bisq trade is completed. Failure to provide the above data will result in losing the dispute case.\n\nCheck payments: with those three pieces of information, the verification that a quantity of Monero was sent to a specific address can be accomplished the following way:\n\n- Monero GUI: change wallet to Advanced mode and go to Advanced > Prove/check > Check Transaction\n- Monero CLI: use the command check_tx_key TXID TXKEY ADDRESS\n- XMR checktx tool (https://xmr.llcoins.net/checktx.html)\n- Explore Monero website (https://www.exploremonero.com/receipt)\n\nIf you are still not sure about this process, visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) to find more information or ask a question on the Monero support subreddit (https://www.reddit.com/r/monerosupport/).
+account.altcoin.popup.upx.msg=在 Bisq 上交易 UPX 需要您瞭解並滿足以下要求：\n\n要傳送 UPX ，您需要使用官方的 UPXmA GUI 錢包或啟用 store-tx-info 標誌的 UPXmA CLI 錢包（在新版本中是預設的）。請確保您可以訪問Tx金鑰，因為在糾紛狀態時需要。\nmonero-wallet-cli（使用get_Tx_key命令）\nmonero-wallet-gui：在高階>證明/檢查頁面。\n\n在普通的區塊鏈瀏覽器中，這種交易是不可驗證的。\n\n如有糾紛，你須向仲裁員提供下列資料：\n \n- Tx私鑰\n- 交易雜湊\n- 接收者的公開地址\n\n如未能提供上述資料，或使用不相容的錢包，將會導致糾紛敗訴。如果發生糾紛，UPX 傳送方負責向仲裁員提供 UPX 轉賬的驗證。\n\n不需要支付 ID，只需要普通的公共地址。\n \n如果您對該流程不確定，請訪問 UPXmA Discord 頻道（https://discord.gg/vhdNSrV）或 Telegram 交流群（https://t.me/uplexaOfficial）瞭解更多資訊。\n\n
+account.altcoin.popup.arq.msg=在 Bisq 上交易 ARQ 需要您瞭解並滿足以下要求：\n\n要傳送 ARQ ，您需要使用官方的 ArQmA GUI 錢包或啟用 store-tx-info 標誌的 ArQmA CLI 錢包（在新版本中是預設的）。請確保您可以訪問Tx金鑰，因為在糾紛狀態時需要。\nmonero-wallet-cli（使用get_Tx_key命令）\nmonero-wallet-gui：在高階>證明/檢查頁面。\n\n在普通的區塊鏈瀏覽器中，這種交易是不可驗證的。\n\n如有糾紛，你須向調解員或仲裁員提供下列資料：\n\n- Tx私鑰\n- 交易雜湊\n- 接收者的公開地址\n\n如未能提供上述資料，或使用不相容的錢包，將會導致糾紛敗訴。如果發生糾紛，ARQ 傳送方負責向調解員或仲裁員提供 ARQ 轉賬的驗證。\n\n不需要交易 ID，只需要普通的公共地址。\n\n如果您對該流程不確定，請訪問 ArQmA Discord 頻道（https://discord.gg/s9BQpJT）或 ArQmA 論壇（https://labs.arqma.com）瞭解更多資訊。
+account.altcoin.popup.xmr.msg=在 Bisq 上交易 XMR 需要你理解並滿足以下要求：\n\n付款證明：由於 Monero 是一種高隱私性貨幣，區塊鏈中不公開一些交易細節，而且，在發生爭議時，調解員或仲裁員需要他們檢查交易是否真的進行了。在 Bisq 中，XMR 交易的傳送方負責在發生爭議時向調解員或仲裁員提供此資訊。為了做到驗證付款，您必須使用錢包傳送 XMR ，錢包提供所需的資訊來證明付款已經完成，其中包括:\n\n- 交易金鑰（Tx 公鑰、Tx 金鑰或 Tx 私鑰)\n- 交易ID（Tx ID 或Tx 雜湊）\n- 目的地地址（收款人地址）\n\n這些資訊可以在官方的 Monero GUI 和 CLI 錢包、MyMonero 和 Exodus （桌面版）以及 Cake Wallet、MyMonero 和 Monerujo（移動版）中找到，地點如下:\n\n- Monero GUI：轉到 交易 標籤\n- Monero CLI：使用命令 get_tx_key TXID 。必須啟用標記 store-tx-info （在新版本中預設啟用）\n- 其他錢包：轉到交易歷史記錄，在傳送的交易中搜索交易金鑰（Tx金鑰或Tx祕密）和目標地址。儲存收件人地址選項必須在 Cake Wallet 設定中啟用。\n\n如果您使用的錢包與上述不同，請確保您可以訪問這三個資訊。由於交易金鑰和目標地址儲存在 Monero 錢包軟體中，無法在 Monero 區塊鏈中恢復，所以在 Bisq 交易完成之前，您不應該刪除或恢復您的 Monero 錢包。如不提供以上資料，將導致糾紛敗訴。\n\n檢查付款：有了這三條資訊，可以通過以下方式來驗證是否有一定數量的 Monero 被髮送到特定地址：\n\n- Monero GUI：將錢包切換到高階模式，進入高階>驗證/檢查>檢查交易\n- Monero CLI：使用命令 check_tx_key TXID TXKEY ADDRESS\n- XMR Tx 驗證工具（https://xmr.llcoins.net/checktx.html）\n- 瀏覽 Monero 官網（https://www.exploremonero.com/receipt）\n\n如果您仍然對此有疑問，請訪問（https://www.getmonero.org/resources/userguides/prove-payment.html）來查詢更多資訊或在 Monero Support subreddit 上提問（https://www.reddit.com/r/monerosupport/）。
 # suppress inspection "TrailingSpacesInProperty"
-account.altcoin.popup.msr.msg=Trading MSR on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending MSR, you need to use either the official Masari GUI wallet, Masari CLI wallet with the store-tx-info flag enabled (enabled by default) or the Masari web wallet (https://wallet.getmasari.org). Please be sure you can access the tx key as that would be required in case of a dispute.\nmasari-wallet-cli (use the command get_tx_key)\nmasari-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nMasari Web Wallet (goto Account -> transaction history and view details on your sent transaction)\n\nVerification can be accomplished in-wallet.\nmasari-wallet-cli : using command (check_tx_key).\nmasari-wallet-gui : on the Advanced > Prove/Check page.\nVerification can be accomplished in the block explorer \nOpen block explorer (https://explorer.getmasari.org), use the search bar to find your transaction hash.\nOnce transaction is found, scroll to bottom to the 'Prove Sending' area and fill in details as needed.\nYou need to provide the mediator or arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The MSR sender is responsible for providing verification of the MSR transfer to the mediator or arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process, ask for help on the Official Masari Discord (https://discord.gg/sMCwMqs).
-account.altcoin.popup.blur.msg=Trading BLUR on Bisq requires that you understand and fulfill the following requirements:\n\nTo send BLUR you must use the Blur Network CLI or GUI Wallet. \n\nIf you are using the CLI wallet, a transaction hash (tx ID) will be displayed after a transfer is sent. You must save this information. Immediately after sending the transfer, you must use the command 'get_tx_key' to retrieve the transaction private key. If you fail to perform this step, you may not be able to retrieve the key later. \n\nIf you are using the Blur Network GUI Wallet, the transaction private key and transaction ID can be found conveniently in the "History" tab.  Immediately after sending, locate the transaction of interest. Click the "?" symbol in the lower-right corner of the box containing the transaction. You must save this information. \n\nIn the event that arbitration is necessary, you must present the following to an mediator or arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address.  The mediator or arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nFailure to provide the required information to the mediator or arbitrator will result in losing the dispute case. In all cases of dispute, the BLUR sender bears 100% of the burden of responsibility in verifying transactions to an mediator or arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW).
-account.altcoin.popup.solo.msg=Trading Solo on Bisq requires that you understand and fulfill the following requirements:\n\nTo send Solo you must use the Solo Network CLI Wallet. \n\nIf you are using the CLI wallet, a transaction hash (tx ID) will be displayed after a transfer is sent. You must save this information. Immediately after sending the transfer, you must use the command 'get_tx_key' to retrieve the transaction private key. If you fail to perform this step, you may not be able to retrieve the key later. \n\nIn the event that arbitration is necessary, you must present the following to an mediator or arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address.  The mediator or arbitrator will then verify the Solo transfer using the Solo Block Explorer by searching for the transaction and then using the "Prove sending" function (https://explorer.minesolo.com/).\n\nfailure to provide the required information to the mediator or arbitrator will result in losing the dispute case. In all cases of dispute, the Solo sender bears 100% of the burden of responsibility in verifying transactions to an mediator or arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Solo Network Discord (https://discord.minesolo.com/).
-account.altcoin.popup.cash2.msg=Trading CASH2 on Bisq requires that you understand and fulfill the following requirements:\n\nTo send CASH2 you must use the Cash2 Wallet version 3 or higher. \n\nAfter a transaction is sent, the transaction ID will be displayed. You must save this information. Immediately after sending the transaction, you must use the command 'getTxKey' in simplewallet to retrieve the transaction secret key. \n\nIn the event that arbitration is necessary, you must present the following to an mediator or arbitrator: 1) the transaction ID, 2) the transaction secret key, and 3) the recipient's Cash2 address.  The mediator or arbitrator will then verify the CASH2 transfer using the Cash2 Block Explorer (https://blocks.cash2.org).\n\nFailure to provide the required information to the mediator or arbitrator will result in losing the dispute case. In all cases of dispute, the CASH2 sender bears 100% of the burden of responsibility in verifying transactions to an mediator or arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Cash2 Discord (https://discord.gg/FGfXAYN).
-account.altcoin.popup.qwertycoin.msg=Trading Qwertycoin on Bisq requires that you understand and fulfill the following requirements:\n\nTo send QWC you must use the official QWC Wallet version 5.1.3 or higher. \n\nAfter a transaction is sent, the transaction ID will be displayed. You must save this information. Immediately after sending the transaction, you must use the command 'get_Tx_Key' in simplewallet to retrieve the transaction secret key. \n\nIn the event that arbitration is necessary, you must present the following to an mediator or arbitrator: 1) the transaction ID, 2) the transaction secret key, and 3) the recipient's QWC address.  The mediator or arbitrator will then verify the QWC transfer using the QWC Block Explorer (https://explorer.qwertycoin.org).\n\nFailure to provide the required information to the mediator or arbitrator will result in losing the dispute case. In all cases of dispute, the QWC sender bears 100% of the burden of responsibility in verifying transactions to an mediator or arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the QWC Discord (https://discord.gg/rUkfnpC).
-account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides, a transaction is not verifiable on the public blockchain. If required, you can prove your payment through the use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the mediator or arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at (http://drgl.info/#check_txn).\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The Dragonglass sender is responsible for providing verification of the DRGL transfer to the mediator or arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help.
-account.altcoin.popup.ZEC.msg=When using Zcash you can only use the transparent addresses (starting with t), not the z-addresses (private), because the mediator or arbitrator would not be able to verify the transaction with z-addresses.
-account.altcoin.popup.XZC.msg=When using Zcoin you can only use the transparent (traceable) addresses, not the untraceable addresses, because the mediator or arbitrator would not be able to verify the transaction with untraceable addresses at a block explorer.
-account.altcoin.popup.grin.msg=GRIN 需要傳送方和接收方之間的互動過程來建立交易。請確保遵循 GRIN 專案網頁中的說明，以可靠地傳送和接收 GRIN（接收方需要線上，或至少在一定時間內線上）。\n \nBisq 只支援 Grinbox（Wallet713）錢包 URL 格式。\n\nGRIN 傳送者需要提供他們已成功傳送 GRIN 的證明。如果錢包不能提供證明，一個潛在的糾紛將被解決，有利於露齒微笑的接受者。請確保您使用了最新的支援交易證明的 Grinbox 軟體，並且您瞭解傳輸和接收 GRIN 的過程以及如何建立證明。\n請參閱 https://github.com/vault713/wallet713/blob/master/docs/usage.md#transaction-proofs-grinbox-only，以獲得關於 Grinbox 證明工具的更多資訊。\n
-account.altcoin.popup.beam.msg=BEAM 需要傳送方和接收方之間的互動過程來建立交易。\n\n\n確保遵循 BEAM 專案網頁的指示可靠地傳送和接收 BEAM（接收方需要線上，或者至少在一定的時間範圍內線上）。\n\nBEAM 傳送者需要提供他們成功傳送 BEAM 的證明。一定要使用錢包軟體，可以產生這樣的證明。如果錢包不能提供證據，一個潛在的糾紛將得到解決，有利於 BEAM 接收者。
-account.altcoin.popup.pars.msg=Trading ParsiCoin on Bisq requires that you understand and fulfill the following requirements:\n\nTo send PARS you must use the official ParsiCoin Wallet version 3.0.0 or higher. \n\nYou can Check your Transaction Hash and Transaction Key on Transactions Section on your GUI Wallet (ParsiPay) You need to right Click on the Transaction and then click on show details. \n\nIn the event that arbitration is necessary, you must present the following to an mediator or arbitrator: 1) the Transaction Hash, 2) the Transaction Key, and 3) the recipient's PARS address.  The mediator or arbitrator will then verify the PARS transfer using the ParsiCoin Block Explorer (http://explorer.parsicoin.net/#check_payment).\n\nFailure to provide the required information to the mediator or arbitrator will result in losing the dispute case. In all cases of dispute, the ParsiCoin sender bears 100% of the burden of responsibility in verifying transactions to an mediator or arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the ParsiCoin Discord (https://discord.gg/c7qmFNh).
+account.altcoin.popup.msr.msg=區塊鏈瀏覽器在 Bisq 上交易 XMR 需要您瞭解並滿足以下要求：\n\n傳送MSR時，您需要使用官方的 Masari GUI 錢包、啟用store-tx-info標記的Masari CLI錢包(預設啟用)或Masari 網頁錢包(https://wallet.getmasari.org)。請確保您可以訪問的 tx 金鑰，因為如果發生糾紛這是需要的。\nmonero-wallet-cli（使用get_Tx_key命令）\nmonero-wallet-gui：在高階>證明/檢查頁面。\n\nMasari 網頁錢包（前往 帳戶->交易歷史和檢視您傳送的交易細節）\n\n驗證可以在錢包中完成。\nmonero-wallet-cli：使用命令（check_tx_key）。\nmonero-wallet-gui：在高階>證明/檢查頁面\n驗證可以在區塊瀏覽器中完成\n開啟區塊瀏覽器（https://explorer.getmasari.org），使用搜索欄查詢您的事務雜湊。\n一旦找到交易，滾動到底部的“證明發送”區域，並填寫所需的詳細資訊。\n如有糾紛，你須向調解員或仲裁員提供下列資料：\n- Tx私鑰\n- 交易雜湊\n- 接收者的公開地址\n\n不需要交易 ID，只需要正常的公共地址。\n如未能提供上述資料，或使用不相容的錢包，將會導致糾紛敗訴。如果發生糾紛，XMR 傳送方負責向調解員或仲裁員提供 XMR 轉賬的驗證。\n\n如果您對該流程不確定，請訪問官方的 Masari Discord（https://discord.gg/sMCwMqs）上尋求幫助。
+account.altcoin.popup.blur.msg=在 Bisq 上交易 BLUR 需要你瞭解並滿足以下要求：\n\n要傳送匿名資訊你必須使用匿名網路 CLI 或 GUI 錢包。\n如果您正在使用 CLI 錢包，在傳輸傳送後將顯示交易雜湊（tx ID）。您必須儲存此資訊。在傳送傳輸之後，您必須立即使用“get_tx_key”命令來檢索交易私鑰。如果未能執行此步驟，以後可能無法檢索金鑰。\n\n如果您使用 Blur Network GUI 錢包，可以在“歷史”選項卡中方便地找到交易私鑰和交易 ID。傳送後立即定位感興趣的交易。單擊包含交易的框的右下角的“?”符號。您必須儲存此資訊。\n\n如果仲裁是必要的，您必須向調解員或仲裁員提供以下資訊：1.)交易ID，2.)交易私鑰，3.)收件人地址。調解或仲裁程式將使用 BLUR 事務檢視器（https://blur.cash/#tx-viewer）驗證 BLUR 轉賬。\n\n未能向調解員或仲裁員提供必要的資訊將導致敗訴。在所有爭議的情況下，匿名傳送方承擔100%的責任來向調解員或仲裁員核實交易。\n\n如果你不瞭解這些要求，不要在 Bisq 上交易。首先，在 Blur Network Discord 中尋求幫助（https://discord.gg/dMWaqVW）。
+account.altcoin.popup.solo.msg=在 Bisq 上交易 Solo 需要您瞭解並滿足以下要求:\n\n要傳送 Solo，您必須使用 Solo CLI 網路錢包版本 5.1.3 或更高。\n\n如果您使用的是CLI錢包，則在傳送交易之後，將顯示交易ID。您必須儲存此資訊。在傳送交易之後，您必須立即使用'get_tx_key'命令來檢索交易金鑰。如果未能執行此步驟，則以後可能無法檢索金鑰。\n\n如果仲裁是必要的，您必須向調解員或仲裁員提供以下資訊：1)交易 ID,、2)交易金鑰，3)收件人的地址。調解員或仲裁員將使用 Solo 區塊資源管理器（https://explorer.Solo.org）搜尋交易然後使用“傳送證明”功能（https://explorer.minesolo.com/）\n\n未能向調解員或仲裁員提供必要的資訊將導致敗訴。在所有發生爭議的情況下，在向調解員或仲裁員核實交易時，QWC 的傳送方承擔 100% 的責任。\n\n如果你不理解這些要求，不要在 Bisq 上交易。首先，在 Solo Discord 中尋求幫助（https://discord.minesolo.com/）。\n\n
+account.altcoin.popup.cash2.msg=在 Bisq 上交易 CASH2 需要您瞭解並滿足以下要求：\n\n要傳送 CASH2，您必須使用 CASH2 錢包版本 3 或更高。\n\n在傳送交易之後，將顯示交易ID。您必須儲存此資訊。在傳送交易之後，必須立即在 simplewallet 中使用命令“getTxKey”來檢索交易金鑰。\n\n如果仲裁是必要的，您必須向調解員或仲裁員提供以下資訊：1)交易 ID，2)交易金鑰，3)收件人的 CASH2 地址。調解員或仲裁員將使用 CASH2 區塊資源管理器（https://blocks.cash2.org）驗證 CASH2 轉賬。\n\n未能向調解員或仲裁員提供必要的資訊將導致敗訴。在所有發生爭議的情況下，在向調解員或仲裁員核實交易時，CASH2 的傳送方承擔 100% 的責任。\n\n如果你不理解這些要求，不要在 Bisq 上交易。首先，在 Cash2 Discord 中尋求幫助（https://discord.gg/FGfXAYN）。
+account.altcoin.popup.qwertycoin.msg=在 Bisq 上交易 Qwertycoin 需要您瞭解並滿足以下要求:\n\n要傳送 Qwertycoin，您必須使用 Qwertycoin 錢包版本 5.1.3 或更高。\n\n在傳送交易之後，將顯示交易ID。您必須儲存此資訊。在傳送交易之後，必須立即在 simplewallet 中使用命令“get_Tx_Key”來檢索交易金鑰。\n\n如果仲裁是必要的，您必須向調解員或仲裁員提供以下資訊:：1)交易 ID,、2)交易金鑰，3)收件人的 QWC 地址。調解員或仲裁員將使用 QWC 區塊資源管理器（https://explorer.qwertycoin.org）驗證 QWC 轉賬。\n\n未能向調解員或仲裁員提供必要的資訊將導致敗訴。在所有發生爭議的情況下，在向調解員或仲裁員核實交易時，QWC 的傳送方承擔 100% 的責任。\n\n如果你不理解這些要求，不要在 Bisq 上交易。首先，在 QWC Discord 中尋求幫助（https://discord.gg/rUkfnpC）。
+account.altcoin.popup.drgl.msg=在 Bisq 上交易 Dragonglass 需要您瞭解並滿足以下要求：\n\n由於 Dragonglass 提供了隱私保護，所以交易不能在公共區塊鏈上驗證。如果需要，您可以通過使用您的 TXN-Private-Key 來證明您的付款。\nTXN-Private 密匙是自動生成的一次性密匙，用於只能從 DRGL 錢包中訪問的每個交易。\n要麼通過 DRGL-wallet GUI（內部交易細節對話方塊），要麼通過 Dragonglass CLI simplewallet（使用命令“get_tx_key”）。\n\n兩者都需要 DRGL 版本的“Oathkeeper”或更高版本。\n\n如有爭議，你必須向調解員或仲裁員提供下列資料：\n\n- txn-Privite-ket\n- 交易雜湊 \n- 接收者的公開地址\n\n付款驗證可以使用上面的資料作為輸入（http://drgl.info/#check_txn）。\n\n如未能提供上述資料，或使用不相容的錢包，將會導致糾紛敗訴。Dragonglass 傳送方負責在發生爭議時向調解員或仲裁員提供 DRGL 轉賬的驗證。不需要使用付款 ID。\n\n如果您對這個過程的任何部分都不確定，請訪問（http://discord.drgl.info）上的 Dragonglass 尋求幫助。
+account.altcoin.popup.ZEC.msg=當使用 Zcash 時，您只能使用透明地址（以 t 開頭），而不能使用 z 地址（私有），因為調解員或仲裁員無法使用 z 地址驗證交易。
+account.altcoin.popup.XZC.msg=在使用 Zcoin 時，您只能使用透明的（可跟蹤的）地址，而不能使用不可跟蹤的地址，因為調解員或仲裁員無法在區塊資源管理器中使用不可跟蹤的地址驗證交易。
+account.altcoin.popup.grin.msg=GRIN 需要傳送方和接收方之間的互動過程來建立交易。請確保遵循 GRIN 項目網頁中的說明，以可靠地傳送和接收 GRIN（接收方需要線上，或至少在一定時間內線上）。\n \nBisq 只支援 Grinbox（Wallet713）錢包 URL 格式。\n\nGRIN 傳送者需要提供他們已成功傳送 GRIN 的證明。如果錢包不能提供證明，一個潛在的糾紛將被解決，有利於露齒微笑的接受者。請確保您使用了最新的支援交易證明的 Grinbox 軟體，並且您瞭解傳輸和接收 GRIN 的過程以及如何建立證明。\n請參閱 https://github.com/vault713/wallet713/blob/master/docs/usage.md#transaction-proofs-grinbox-only，以獲得關於 Grinbox 證明工具的更多資訊。\n
+account.altcoin.popup.beam.msg=BEAM 需要傳送方和接收方之間的互動過程來建立交易。\n\n\n確保遵循 BEAM 項目網頁的指示可靠地傳送和接收 BEAM（接收方需要線上，或者至少在一定的時間範圍內線上）。\n\nBEAM 傳送者需要提供他們成功傳送 BEAM 的證明。一定要使用錢包軟體，可以產生這樣的證明。如果錢包不能提供證據，一個潛在的糾紛將得到解決，有利於 BEAM 接收者。
+account.altcoin.popup.pars.msg=在 Bisq 上交易 ParsiCoin 需要您瞭解並滿足以下要求：\n\n要傳送 PARS ，您必須使用官方 ParsiCoin Wallet 版本 3.0.0 或更高。\n\n您可以在 GUI 錢包（ParsiPay）的交易部分檢查您的交易雜湊和交易鍵，您需要右鍵單擊“交易”，然後單擊“顯示詳情”。\n\n如果仲裁是 100% 必要的，您必須向調解員或仲裁員提供以下內容：1)交易雜湊，2)交易金鑰，以及3)接收方的 PARS 地址。調解員或仲裁員將使用 ParsiCoin 區塊鏈瀏覽器 （http://explorer.parsicoin.net/#check_payment）驗證 PARS 傳輸。\n\n如果你不瞭解這些要求，不要在 Bisq 上交易。首先，在 ParsiCoin Discord 尋求幫助（https://discord.gg/c7qmFNh）。
 
-account.altcoin.popup.blk-burnt.msg=To trade burnt blackcoins, you need to know the following:\n\nBurnt blackcoins are unspendable. To trade them on Bisq, output scripts need to be in the form: OP_RETURN OP_PUSHDATA, followed by associated data bytes which, after being hex-encoded, constitute addresses. For example, burnt blackcoins with an address 666f6f (“foo” in UTF-8) will have the following script:\n\nOP_RETURN OP_PUSHDATA 666f6f\n\nTo create burnt blackcoins, one may use the “burn” RPC command available in some wallets.\n\nFor possible use cases, one may look at https://ibo.laboratorium.ee .\n\nAs burnt blackcoins are unspendable, they can not be reselled. “Selling” burnt blackcoins means burning ordinary blackcoins (with associated data equal to the destination address).\n\nIn case of a dispute, the BLK seller needs to provide the transaction hash.
+account.altcoin.popup.blk-burnt.msg=要交易燒燬的貨幣，你需要知道以下幾點：\n\n燒燬的貨幣是不能花的。要在 Bisq 上交易它們，輸出指令碼需要採用以下形式：OP_RETURN OP_PUSHDATA，後跟相關的資料位元組，這些位元組經過十六進位制編碼後構成地址。例如，地址為666f6f（在UTF-8中的"foo"）的燒燬的貨幣將有以下指令碼：\n\nOP_RETURN OP_PUSHDATA 666f6f\n\n要建立燒燬的貨幣，您可以使用“燒燬”RPC命令，它在一些錢包可用。\n\n對於可能的情況，可以檢視 https://ibo.laboratorium.ee\n\n因為燒燬的貨幣是不能用的，所以不能重新出售。“出售”燒燬的貨幣意味著焚燒初始的貨幣（與目的地地址相關聯的資料）。\n\n如果發生爭議，BLK 賣方需要提供交易雜湊。
 
 account.fiat.yourFiatAccounts=您的法定貨幣賬戶
 
@@ -1120,7 +1120,7 @@ account.notifications.dispute.message.msg=您收到了一個 ID 為 {0} 的交
 
 account.notifications.marketAlert.title=報價提醒
 account.notifications.marketAlert.selectPaymentAccount=提供匹配的付款帳戶
-account.notifications.marketAlert.offerType.label=我感興趣的報價型別
+account.notifications.marketAlert.offerType.label=我感興趣的報價類型
 account.notifications.marketAlert.offerType.buy=買入報價（我想要出售 BTC ）
 account.notifications.marketAlert.offerType.sell=賣出報價（我想要購買 BTC ）
 account.notifications.marketAlert.trigger=報價距離（%）
@@ -1133,7 +1133,7 @@ account.notifications.marketAlert.manageAlerts.label=報價提醒
 account.notifications.marketAlert.manageAlerts.item=觸發價格 {1} 以及支付賬戶為 {2} 的報價提醒 {0}
 account.notifications.marketAlert.manageAlerts.header.paymentAccount=支付賬戶
 account.notifications.marketAlert.manageAlerts.header.trigger=觸發價格
-account.notifications.marketAlert.manageAlerts.header.offerType=委託型別
+account.notifications.marketAlert.manageAlerts.header.offerType=委託類型
 account.notifications.marketAlert.message.title=報價提醒
 account.notifications.marketAlert.message.msg.below=低於
 account.notifications.marketAlert.message.msg.above=高於
@@ -1168,7 +1168,7 @@ dao.lockedForVoteBalance=用於投票
 dao.lockedInBonds=凍結餘額
 dao.availableNonBsqBalance=可用的非 BSQ 餘額（BTC）
 dao.totalBsqBalance=BSQ 總額
-dao.reputationBalance=Merit Value (not spendable)
+dao.reputationBalance=聲望值（不會花費）
 
 dao.tx.published.success=你的交易已經成功釋出
 dao.proposal.menuItem.make=建立要求
@@ -1251,7 +1251,7 @@ dao.param.QUORUM_COMP_REQUEST=BSQ 要求的報償請求的仲裁人數
 # suppress inspection "UnusedProperty"
 dao.param.QUORUM_REIMBURSEMENT=BSQ 要求的退還提案的仲裁人數
 # suppress inspection "UnusedProperty"
-dao.param.QUORUM_CHANGE_PARAM=BSQ 要求的改變引數的仲裁人數
+dao.param.QUORUM_CHANGE_PARAM=BSQ 要求的改變參數的仲裁人數
 # suppress inspection "UnusedProperty"
 dao.param.QUORUM_REMOVE_ASSET=BSQ 要求的移除資產要求的人數
 # suppress inspection "UnusedProperty"
@@ -1266,7 +1266,7 @@ dao.param.THRESHOLD_COMP_REQUEST=報償請求的要求百分比
 # suppress inspection "UnusedProperty"
 dao.param.THRESHOLD_REIMBURSEMENT=退還請求的要求百分比
 # suppress inspection "UnusedProperty"
-dao.param.THRESHOLD_CHANGE_PARAM=改變引數的要求百分比
+dao.param.THRESHOLD_CHANGE_PARAM=改變參數的要求百分比
 # suppress inspection "UnusedProperty"
 dao.param.THRESHOLD_REMOVE_ASSET=移除資產的要求百分比
 # suppress inspection "UnusedProperty"
@@ -1296,7 +1296,7 @@ dao.param.BONDED_ROLE_FACTOR=擔保角色對 BSQ 的影響
 dao.param.ISSUANCE_LIMIT=每個週期的 BSQ 發行限額
 
 dao.param.currentValue=當前值：{0}
-dao.param.currentAndPastValue=Current value: {0} (Value when proposal was made: {1})
+dao.param.currentAndPastValue=當前餘額：{0}（提案時的餘額：{1}）
 dao.param.blocks={0} 區塊
 
 dao.results.cycle.duration.label={0} 的週期
@@ -1304,7 +1304,7 @@ dao.results.cycle.duration.value={0} 區塊
 dao.results.cycle.value.postFix.isDefaultValue=（預設值）
 dao.results.cycle.value.postFix.hasChanged=（在投票中更改）
 
-dao.results.invalidVotes=We had invalid votes in that voting cycle. That can happen if a vote was not distributed well in the Bisq network.\n{0}
+dao.results.invalidVotes=在那個投票週期中，我們有無效的投票。如果投票沒有在 Bisq 網路中很好地分佈，就會發生這種情況。\n{0}
 
 # suppress inspection "UnusedProperty"
 dao.phase.PHASE_UNDEFINED=未定義
@@ -1364,7 +1364,7 @@ dao.bond.details.blocks={0} 區塊
 
 dao.bond.table.column.name=名稱
 dao.bond.table.column.link=繫結
-dao.bond.table.column.bondType=連線型別
+dao.bond.table.column.bondType=連線類型
 dao.bond.table.column.details=詳情
 dao.bond.table.column.lockupTxId=鎖定 Tx ID
 dao.bond.table.column.bondState=連線狀態
@@ -1533,7 +1533,7 @@ dao.proposal.type.BONDED_ROLE=擔保角色的提案
 # suppress inspection "UnusedProperty"
 dao.proposal.type.REMOVE_ASSET=移除資產提案
 # suppress inspection "UnusedProperty"
-dao.proposal.type.CHANGE_PARAM=修改引數的提議
+dao.proposal.type.CHANGE_PARAM=修改參數的提議
 # suppress inspection "UnusedProperty"
 dao.proposal.type.GENERIC=一般提議
 # suppress inspection "UnusedProperty"
@@ -1550,7 +1550,7 @@ dao.proposal.type.short.BONDED_ROLE=擔保角色
 # suppress inspection "UnusedProperty"
 dao.proposal.type.short.REMOVE_ASSET=移除一個數字貨幣
 # suppress inspection "UnusedProperty"
-dao.proposal.type.short.CHANGE_PARAM=修改引數
+dao.proposal.type.short.CHANGE_PARAM=修改參數
 # suppress inspection "UnusedProperty"
 dao.proposal.type.short.GENERIC=一般提議
 # suppress inspection "UnusedProperty"
@@ -1573,16 +1573,16 @@ dao.proposal.myVote.stake.prompt=在投票中最大可用 Stake：{0}
 dao.proposal.votes.header=設定投票的份額，併發布您的投票
 dao.proposal.myVote.button=釋出投票
 dao.proposal.myVote.setStake.description=在對所有提案進行投票後，您必須鎖定BSQ來設定投票的份額。您鎖定的 BSQ 越多，你的投票權重就越大。\n\n投票會鎖定 BSQ 將在投票顯示階段再次解鎖。
-dao.proposal.create.selectProposalType=選擇提案型別
+dao.proposal.create.selectProposalType=選擇提案類型
 dao.proposal.create.phase.inactive=請等到下一個提案階段
-dao.proposal.create.proposalType=提議型別
+dao.proposal.create.proposalType=提議類型
 dao.proposal.create.new=建立新的賠償要求
 dao.proposal.create.button=建立賠償要求
 dao.proposal.create.publish=釋出提案
 dao.proposal.create.publishing=正在釋出提案中...
 dao.proposal=提案
-dao.proposal.display.type=提議型別
-dao.proposal.display.name=Exact GitHub username
+dao.proposal.display.type=提議類型
+dao.proposal.display.name=確切的 GitHub 的使用者名稱
 dao.proposal.display.link=連線到詳情
 dao.proposal.display.link.prompt=連線到提案
 dao.proposal.display.requestedBsq=被要求的 BSQ 數量
@@ -1591,12 +1591,12 @@ dao.proposal.display.txId=提案交易 ID
 dao.proposal.display.proposalFee=提案手續費
 dao.proposal.display.myVote=我的投票
 dao.proposal.display.voteResult=投票結果總結
-dao.proposal.display.bondedRoleComboBox.label=擔保角色型別
+dao.proposal.display.bondedRoleComboBox.label=擔保角色類型
 dao.proposal.display.requiredBondForRole.label=角色需要的擔保
 dao.proposal.display.tickerSymbol.label=股票代號
 dao.proposal.display.option=選項
 
-dao.proposal.table.header.proposalType=提議型別
+dao.proposal.table.header.proposalType=提議類型
 dao.proposal.table.header.link=繫結
 dao.proposal.table.header.myVote=我的投票
 dao.proposal.table.header.remove=移除
@@ -1606,16 +1606,16 @@ dao.proposal.table.icon.tooltip.changeVote=當前投票：“{0}”。更改投
 dao.proposal.display.myVote.accepted=已接受
 dao.proposal.display.myVote.rejected=已拒絕
 dao.proposal.display.myVote.ignored=已忽略
-dao.proposal.display.myVote.unCounted=Vote was not included in result
-dao.proposal.myVote.summary=Voted: {0}; Vote weight: {1} (earned: {2} + stake: {3}) {4}
+dao.proposal.display.myVote.unCounted=投票結果不包括在內
+dao.proposal.myVote.summary=已投票：{0}；投票權重：{1}（獲得的：{2} + 獎金：{3}）（{4}）
 dao.proposal.myVote.invalid=投票無效
 
 dao.proposal.voteResult.success=已接受
 dao.proposal.voteResult.failed=已拒絕
 dao.proposal.voteResult.summary=結果：{0}；閾值：{1}（要求> {2}）；仲裁人數：{3}（要求> {4}）
 
-dao.proposal.display.paramComboBox.label=選擇需要改變的引數
-dao.proposal.display.paramValue=引數值
+dao.proposal.display.paramComboBox.label=選擇需要改變的參數
+dao.proposal.display.paramValue=參數值
 
 dao.proposal.display.confiscateBondComboBox.label=選擇擔保
 dao.proposal.display.assetComboBox.label=需要移除的資產
@@ -1657,7 +1657,7 @@ dao.wallet.send.sendFunds.headline=確定提現請求
 dao.wallet.send.sendFunds.details=傳送：{0}\n來自：{1}\n要求的交易費：{2}（{3} 聰/byte）\n交易大小：{4} Kb\n\n收件人將收到：{5}\n\n您確定您想要提現這些數量嗎？
 dao.wallet.chainHeightSynced=最新確認區塊：{0}
 dao.wallet.chainHeightSyncing=等待區塊... 已確認{0}/{1}區塊
-dao.wallet.tx.type=型別
+dao.wallet.tx.type=類型
 
 # suppress inspection "UnusedProperty"
 dao.tx.type.enum.UNDEFINED=未定義
@@ -1760,7 +1760,7 @@ dao.monitor.daoState.utxoConflicts=UTXO 衝突
 dao.monitor.daoState.utxoConflicts.blockHeight=區塊高度：{0}
 dao.monitor.daoState.utxoConflicts.sumUtxo=所有 UTXO 的總和：{0} BSQ
 dao.monitor.daoState.utxoConflicts.sumBsq=所有 BSQ 的總和：{0} BSQ
-dao.monitor.daoState.checkpoint.popup=DAO state is not in sync with the network. After restart the DAO state will resync.
+dao.monitor.daoState.checkpoint.popup=DAO 狀態與網路不同步。重啟之後，DAO 狀態將重新同步。
 
 dao.monitor.proposal.headline=提案狀態
 dao.monitor.proposal.table.headline=提案狀態的雜湊鏈
@@ -1786,8 +1786,8 @@ dao.factsAndFigures.menuItem.transactions=BSQ 交易
 
 dao.factsAndFigures.dashboard.marketPrice=市場資料
 dao.factsAndFigures.dashboard.price=最新的 BSQ/BTC 的市場價（在 Bisq）
-dao.factsAndFigures.dashboard.avgPrice90=90 days average BSQ/BTC trade price
-dao.factsAndFigures.dashboard.avgPrice30=30 days average BSQ/BTC trade price
+dao.factsAndFigures.dashboard.avgPrice90=90天平均 BSQ/BTC 交易價格
+dao.factsAndFigures.dashboard.avgPrice30=30天平均 BSQ/BTC 交易價格
 dao.factsAndFigures.dashboard.marketCap=市值（基於市場價）
 dao.factsAndFigures.dashboard.availableAmount=總共可用的 BSQ
 
@@ -1798,7 +1798,7 @@ dao.factsAndFigures.supply.reimbursementAmount=所有有問題的 BSQ 退還申
 
 dao.factsAndFigures.supply.burnt=BSQ 燒燬總量
 
-dao.factsAndFigures.supply.locked=BSQ 全域性鎖定狀態
+dao.factsAndFigures.supply.locked=BSQ 全局鎖定狀態
 dao.factsAndFigures.supply.totalLockedUpAmount=擔保的鎖定
 dao.factsAndFigures.supply.totalUnlockingAmount=正在從擔保解鎖 BSQ
 dao.factsAndFigures.supply.totalUnlockedAmount=已從擔保解鎖 BSQ
@@ -1871,14 +1871,14 @@ disputeSummaryWindow.reason.bank=銀行
 disputeSummaryWindow.summaryNotes=總結說明
 disputeSummaryWindow.addSummaryNotes=新增總結說明
 disputeSummaryWindow.close.button=關閉話題
-disputeSummaryWindow.close.msg=Ticket closed on {0}\n\nSummary:\nPayout amount for BTC buyer: {1}\nPayout amount for BTC seller: {2}\n\nSummary notes:\n{3}
-disputeSummaryWindow.close.nextStepsForMediation=\n\nNext steps:\nOpen trade and accept or reject suggestion from mediator
-disputeSummaryWindow.close.nextStepsForRefundAgentArbitration=\n\nNext steps:\nNo further action is required from you. If the arbitrator decided in your favor, you'll see a "Refund from arbitration" transaction in Funds/Transactions
+disputeSummaryWindow.close.msg=工單已關閉 {0}\n\n摘要：\nBTC 買家的支付金額：{1}\nBTC 賣家的支付金額：{2}\n\n總結說明：\n{3}
+disputeSummaryWindow.close.nextStepsForMediation=\n\n下一個步驟：\n開啟未完成交易，接受或拒絕建議的調解員的建議
+disputeSummaryWindow.close.nextStepsForRefundAgentArbitration=\n\n下一個步驟:\n不需要您採取進一步的行動。如果仲裁員做出了對你有利的裁決，你將在 資金/交易 頁中看到“仲裁退款”交易
 disputeSummaryWindow.close.closePeer=你也需要關閉交易物件的話題！
-disputeSummaryWindow.close.txDetails.headline=Publish refund transaction
-disputeSummaryWindow.close.txDetails.buyer=Buyer receives {0} on address: {1}\n
-disputeSummaryWindow.close.txDetails.seller=Seller receives {0} on address: {1}\n
-disputeSummaryWindow.close.txDetails=Spending: {0}\n{1}{2}Transaction fee: {3} ({4} satoshis/byte)\nTransaction size: {5} Kb\n\nAre you sure you want to publish this transaction?
+disputeSummaryWindow.close.txDetails.headline=釋出交易退款
+disputeSummaryWindow.close.txDetails.buyer=買方收到{0}在地址:{1}
+disputeSummaryWindow.close.txDetails.seller=賣方收到{0}在地址:{1}
+disputeSummaryWindow.close.txDetails=費用：{0}\n{1}{2}交易費：{3}({4}satoshis/byte)\n事務大小：{5} Kb\n\n您確定要釋出此事務嗎？
 
 emptyWalletWindow.headline={0} 錢包急救工具
 emptyWalletWindow.info=請在緊急情況下使用，如果您無法從 UI 中訪問您的資金。\n\n請注意，使用此工具時，所有未結委託將自動關閉。\n\n在使用此工具之前，請備份您的資料目錄。您可以在“帳戶/備份”中執行此操作。\n\n請報告我們您的問題，並在 Github 或 Bisq 論壇上提交錯誤報告，以便我們可以調查導致問題的原因。
@@ -1891,7 +1891,7 @@ emptyWalletWindow.openOffers.warn=您有釋出的委託，如果您清空錢包
 emptyWalletWindow.openOffers.yes=是的，我確定
 emptyWalletWindow.sent.success=您的錢包的餘額已成功轉移。
 
-enterPrivKeyWindow.headline=Enter private key for registration
+enterPrivKeyWindow.headline=輸入金鑰進行註冊
 
 filterWindow.headline=編輯過濾列表
 filterWindow.offers=過濾報價（用逗號“,”隔開）
@@ -1900,8 +1900,8 @@ filterWindow.accounts=過濾交易賬戶資料：\n格式：逗號分割的 [付
 filterWindow.bannedCurrencies=過濾貨幣程式碼（用逗號“,”隔開）
 filterWindow.bannedPaymentMethods=過濾支付方式 ID（用逗號“,”隔開）
 filterWindow.arbitrators=過濾後的仲裁人（用逗號“,”隔開的洋蔥地址）
-filterWindow.mediators=Filtered mediators (comma sep. onion addresses)
-filterWindow.refundAgents=Filtered refund agents (comma sep. onion addresses)
+filterWindow.mediators=過濾後的調解員（用逗號“,”隔開的洋蔥地址）
+filterWindow.refundAgents=過濾後的退款助理（用逗號“,”隔開的洋蔥地址）
 filterWindow.seedNode=過濾後的種子節點（用逗號“,”隔開的洋蔥地址）
 filterWindow.priceRelayNode=過濾後的價格中繼節點（用逗號“,”隔開的洋蔥地址）
 filterWindow.btcNode=過濾後的比特幣節點（用逗號“,”隔開的地址+埠）
@@ -1961,7 +1961,7 @@ showWalletDataWindow.includePrivKeys=包含私鑰
 tacWindow.headline=使用者協議
 tacWindow.agree=我同意
 tacWindow.disagree=我不同意並退出
-tacWindow.arbitrationSystem=Dispute resolution
+tacWindow.arbitrationSystem=糾紛解決方案
 
 tradeDetailsWindow.headline=交易
 tradeDetailsWindow.disputedPayoutTxId=糾紛支付交易 ID：
@@ -1969,7 +1969,7 @@ tradeDetailsWindow.tradeDate=交易時間
 tradeDetailsWindow.txFee=礦工手續費
 tradeDetailsWindow.tradingPeersOnion=交易對手匿名地址
 tradeDetailsWindow.tradeState=交易狀態
-tradeDetailsWindow.agentAddresses=Arbitrator/Mediator
+tradeDetailsWindow.agentAddresses=仲裁員/調解員
 
 walletPasswordWindow.headline=輸入密碼解鎖
 
@@ -1977,7 +1977,7 @@ torNetworkSettingWindow.header=Tor 網路設定
 torNetworkSettingWindow.noBridges=不使用網橋
 torNetworkSettingWindow.providedBridges=連線到提供的網橋
 torNetworkSettingWindow.customBridges=輸入自定義網橋
-torNetworkSettingWindow.transportType=傳輸型別
+torNetworkSettingWindow.transportType=傳輸類型
 torNetworkSettingWindow.obfs3=obfs3
 torNetworkSettingWindow.obfs4=obfs4（推薦）
 torNetworkSettingWindow.meekAmazon=meek-amazon
@@ -2018,15 +2018,15 @@ popup.headline.error=錯誤
 popup.doNotShowAgain=不要再顯示
 popup.reportError.log=開啟日誌檔案
 popup.reportError.gitHub=報告至 Github issue tracker
-popup.reportError={0}\n\n為了幫助我們改進軟體，請在 https://github.com/bisq-network/bisq/issues 上開啟一個新問題來報告這個 bug 。\n\n當您單擊下面任意一個按鈕時，上面的錯誤訊息將被複制到剪貼簿。\n\n如果您通過按下“開啟日誌檔案”，儲存一份副本，並將其附加到 bug 報告中，如果包含 bisq.log 檔案，那麼除錯就會變得更容易。
+popup.reportError={0}\n\n為了幫助我們改進軟體，請在 https://github.com/bisq-network/bisq/issues 上開啟一個新問題來報告這個 bug 。\n\n當您單擊下面任意一個按鈕時，上面的錯誤訊息將被複制到剪貼簿。\n\n如果您通過按下“開啟日誌檔案”，儲存一份副本，並將其附加到 bug 報告中，如果包含 bisq.log 檔案，那麼偵錯就會變得更容易。
 
 popup.error.tryRestart=請嘗試重啟您的應用程式或者檢查您的網路連線。
 popup.error.takeOfferRequestFailed=當有人試圖接受你的報價時發生了一個錯誤：\n{0}
 
 error.spvFileCorrupted=讀取 SPV 鏈檔案時發生錯誤。\n可能是 SPV 鏈檔案被破壞了。\n\n錯誤訊息：{0}\n\n要刪除它並開始重新同步嗎？
 error.deleteAddressEntryListFailed=無法刪除 AddressEntryList 檔案。\n \n錯誤：{0}
-error.closedTradeWithUnconfirmedDepositTx=The deposit transaction of the closed trade with the trade ID {0} is still unconfirmed.\n\nPlease do a SPV resync at \"Setting/Network info\" to see if the transaction is valid.
-error.closedTradeWithNoDepositTx=The deposit transaction of the closed trade with the trade ID {0} is null.\n\nPlease restart the application to clean up the closed trades list.
+error.closedTradeWithUnconfirmedDepositTx=交易 ID 為 {0} 的已關閉交易的保證金交易仍未確認。\n \n請在“設定/網路資訊”進行 SPV 重新同步，以檢視交易是否有效。
+error.closedTradeWithNoDepositTx=交易 ID 為 {0} 的保證金交易已被確認。\n\n請重新啟動應用程式來清理已關閉的交易列表。
 
 popup.warning.walletNotInitialized=錢包至今未初始化
 popup.warning.wrongVersion=您這臺電腦上可能有錯誤的 Bisq 版本。\n您的電腦的架構是：{0}\n您安裝的 Bisq 二進位制檔案是：{1}\n請關閉並重新安裝正確的版本（{2}）。
@@ -2034,11 +2034,11 @@ popup.warning.incompatibleDB=我們檢測到不相容的資料庫檔案！\n\n
 popup.warning.startupFailed.twoInstances=Bisq 已經在執行。 您不能執行兩個 Bisq 例項。
 popup.warning.cryptoTestFailed=看起來你使用自編譯的二進位制檔案，並且沒有遵循 https://github.com/bisq-network/exchange/blob/master/doc/build.md#7-enable-unlimited-strength-for-cryptographic-keys\n\n如果不是這種情況，並且使用官方的 Bisq 二進位制檔案，請向 Github 頁面提交錯誤報告。\n錯誤={0}
 popup.warning.tradePeriod.halfReached=您與 ID {0} 的交易已達到最長交易期的一半，且仍未完成。\n\n交易期結束於 {1}\n\n請檢視“業務/未完成交易”的交易狀態，以獲取更多資訊。
-popup.warning.tradePeriod.ended=Your trade with ID {0} has reached the max. allowed trading period and is not completed.\n\nThe trade period ended on {1}\n\nPlease check your trade at \"Portfolio/Open trades\" for contacting the mediator.
+popup.warning.tradePeriod.ended=您與 ID {0} 的已達到最長交易期，且未完成。\n\n交易期結束於 {1}\n\n請檢視“業務/未完成交易”的交易狀態，以從調解員獲取更多資訊。
 popup.warning.noTradingAccountSetup.headline=您還沒有設定交易賬戶
 popup.warning.noTradingAccountSetup.msg=您需要設定法定貨幣或數字貨幣賬戶才能建立委託。\n您要設定帳戶嗎？
 popup.warning.noArbitratorsAvailable=沒有仲裁員可用。
-popup.warning.noMediatorsAvailable=There are no mediators available.
+popup.warning.noMediatorsAvailable=沒有調解員可用。
 popup.warning.notFullyConnected=您需要等到您完全連線到網路\n在啟動時可能需要2分鐘。
 popup.warning.notSufficientConnectionsToBtcNetwork=你需要等待至少有{0}個與比特幣網路的連線點。
 popup.warning.downloadNotComplete=您需要等待，直到丟失的比特幣區塊被下載完畢。
@@ -2048,13 +2048,13 @@ popup.warning.examplePercentageValue=請輸入百分比數字，如 5.4％ 是
 popup.warning.noPriceFeedAvailable=該貨幣沒有可用的價格。 你不能使用基於百分比的價格。\n請選擇固定價格。
 popup.warning.sendMsgFailed=向您的交易物件傳送訊息失敗。\n請重試，如果繼續失敗報告錯誤。
 popup.warning.insufficientBtcFundsForBsqTx=你沒有足夠的 BTC 資金支付這筆交易的挖礦手續費。\n請充值您的 BTC 錢包。\n缺少的資金：{0}
-popup.warning.bsqChangeBelowDustException=This transaction creates a BSQ change output which is below dust limit (5.46 BSQ) and would be rejected by the Bitcoin network.\n\nYou need to either send a higher amount to avoid the change output (e.g. by adding the dust amount to your sending amount) or add more BSQ funds to your wallet so you avoid to generate a dust output.\n\nThe dust output is {0}.
-popup.warning.btcChangeBelowDustException=This transaction creates a change output which is below dust limit (546 Satoshi) and would be rejected by the Bitcoin network.\n\nYou need to add the dust amount to your sending amount to avoid to generate a dust output.\n\nThe dust output is {0}.
+popup.warning.bsqChangeBelowDustException=該交易產生的 BSQ 變化輸出低於零頭限制（5.46 BSQ），將被比特幣網路拒絕。\n\n您需要傳送更高的金額以避免更改輸出（例如，通過在您的傳送金額中新增零頭），或者向您的錢包中新增更多的 BSQ 資金，以避免生成零頭輸出。\n\n零頭輸出為 {0}。
+popup.warning.btcChangeBelowDustException=該交易建立的更改輸出低於零頭限制（546 聰），將被比特幣網路拒絕。\n\n您需要將零頭新增到傳送量中，以避免生成零頭輸出。\n\n零頭輸出為{0}。
 
 popup.warning.insufficientBsqFundsForBtcFeePayment=您沒有足夠的 BSQ 資金支付 BSQ 的交易費用。您可以在 BTC 支付費用，或者您需要充值您的 BSQ 錢包。你可以在 Bisq 買到 BSQ 。\n\n缺少 BSQ 資金：{0}
 popup.warning.noBsqFundsForBtcFeePayment=您的 BSQ 錢包沒有足夠的資金支付 BSQ 的交易費用。
 popup.warning.messageTooLong=您的資訊超過最大允許的大小。請將其分成多個部分發送，或將其上傳到 https://pastebin.com 之類的伺服器。
-popup.warning.lockedUpFunds=You have locked up funds from a failed trade.\nLocked up balance: {0} \nDeposit tx address: {1}\nTrade ID: {2}.\n\nPlease open a support ticket by selecting the trade in the open trades screen and pressing \"alt + o\" or \"option + o\"."
+popup.warning.lockedUpFunds=你已經從一個失敗的交易中凍結了資金。\n凍結餘額：{0}\n存款tx地址：{1}\n交易單號：{2}\n\n請通過選擇待處理交易介面中的交易並點選“alt + o”或“option+ o”開啟幫助話題。
 
 popup.warning.nodeBanned=其中一個 {0} 節點被禁用。請重新啟動您的應用程式，以確保沒有連線到禁止節點。
 popup.warning.priceRelay=價格傳遞
@@ -2064,16 +2064,16 @@ popup.warning.mandatoryUpdate.dao=請更新到最新的 Bisq 版本。釋出了
 popup.warning.disable.dao=Bisq DAO 和 BSQ 被臨時禁用的。更多資訊請訪問 Bisq 論壇。
 popup.warning.burnBTC=這筆交易是不可能的，因為 {0} 的挖礦手續費用會超過 {1} 的轉賬金額。請等到挖礦手續費再次降低或您積累了更多的 BTC 來轉賬。
 
-popup.warning.openOffer.makerFeeTxRejected=The maker fee transaction for offer with ID {0} was rejected by the Bitcoin network.\nTransaction ID={1}.\nThe offer has been removed to avoid further problems.\nPlease go to \"Settings/Network info\" and do a SPV resync.\nFor further help please contact the Bisq support channel at the Bisq Keybase team.
+popup.warning.openOffer.makerFeeTxRejected=交易 ID 為 {0} 的掛單費交易被比特幣網路拒絕。\n交易 ID = {1}\n交易已被移至失敗交易。\n請到“設定/網路資訊”進行 SPV 重新同步。\n如需更多幫助，請聯絡 Bisq Keybase 團隊的 Support 頻道
 
-popup.warning.trade.txRejected.tradeFee=trade fee
-popup.warning.trade.txRejected.deposit=deposit
-popup.warning.trade.txRejected=The {0} transaction for trade with ID {1} was rejected by the Bitcoin network.\nTransaction ID={2}}\nThe trade has been moved to failed trades.\nPlease go to \"Settings/Network info\" and do a SPV resync.\nFor further help please contact the Bisq support channel at the Bisq Keybase team.
+popup.warning.trade.txRejected.tradeFee=交易手續費
+popup.warning.trade.txRejected.deposit=押金
+popup.warning.trade.txRejected=使用 ID {1} 進行交易的 {0} 交易被比特幣網路拒絕。\n交易 ID = {2}}\n交易已被移至失敗交易。\n請到“設定/網路資訊”進行 SPV 重新同步。\n如需更多幫助，請聯絡 Bisq Keybase 團隊的 Support 頻道
 
-popup.warning.openOfferWithInvalidMakerFeeTx=The maker fee transaction for offer with ID {0} is invalid.\nTransaction ID={1}.\nPlease go to \"Settings/Network info\" and do a SPV resync.\nFor further help please contact the Bisq support channel at the Bisq Keybase team.
+popup.warning.openOfferWithInvalidMakerFeeTx=交易 ID 為 {0} 的掛單費交易無效。\n交易 ID = {1}。\n請到“設定/網路資訊”進行 SPV 重新同步。\n如需更多幫助，請聯絡 Bisq Keybase 團隊的 Support 頻道
 
-popup.warning.trade.depositTxNull=The trade with ID {0} has no deposit transaction set.\nPlease restart the application and if the problem remains move the trade to failed trades and report the problem to the Bisq support channel at the Bisq Keybase team.
-popup.warning.trade.depositTxNull.moveToFailedTrades=Move to failed trades
+popup.warning.trade.depositTxNull=交易 ID 為 {0} 沒有設定保證金交易。\n請重新啟動應用程式，如果問題仍然存在，將交易移至失敗交易，並將問題報告到 Bisq Keybase 團隊的 Support 頻道。
+popup.warning.trade.depositTxNull.moveToFailedTrades=移至失敗交易
 
 popup.info.securityDepositInfo=為了確保雙方都遵守交易協議，雙方都需要支付保證金。\n\n這筆存款一直儲存在您的交易錢包裡，直到您的交易成功完成，然後再退還給您。\n\n請注意：如果您正在建立一個新的報價，Bisq 需要執行另一個交易員接受它。為了讓您的報價線上，保持 Bisq 執行，並確保這臺計算機也線上（即，確保它沒有切換到待機模式…顯示器可以待機）。
 
@@ -2096,33 +2096,33 @@ popup.attention.forTradeWithId=交易 ID {0} 需要注意
 popup.info.multiplePaymentAccounts.headline=多個支付賬戶可用
 popup.info.multiplePaymentAccounts.msg=您有多個支付帳戶在這個報價中可用。請確你做了正確的選擇。
 
-popup.news.launch.headline=Two Major Updates
-popup.news.launch.accountSigning.headline=ACCOUNT SIGNING
-popup.news.launch.accountSigning.description=Lift 0.01 BTC fiat trading limits by buying BTC from a signed peer.
-popup.news.launch.ntp.headline=NEW TRADE PROTOCOL
-popup.news.launch.ntp.description=New 2-level dispute resolution system makes Bisq more secure, scalable, and censorship-resistant.
+popup.news.launch.headline=兩個重要更新
+popup.news.launch.accountSigning.headline=賬戶簽署
+popup.news.launch.accountSigning.description=提高0.01 BTC的法幣交易限制，從簽署夥伴購買 BTC。
+popup.news.launch.ntp.headline=新的交易協議
+popup.news.launch.ntp.description=新的兩級爭端解決系統使 Bisq 更安全，可擴充套件，和審查抵抗。
 
-popup.accountSigning.selectAccounts.headline=Select payment accounts
-popup.accountSigning.selectAccounts.description=Based on the payment method and point of time all payment accounts that are connected to a dispute where a payout to the buyer occurred will be selected for you to sign.
-popup.accountSigning.selectAccounts.signAll=Sign all payment methods
-popup.accountSigning.selectAccounts.datePicker=Select point of time until which accounts will be signed
+popup.accountSigning.selectAccounts.headline=選擇付款賬戶
+popup.accountSigning.selectAccounts.description=根據付款方式和時間點，所有與支付給買方的付款發生的爭議有關的付款帳戶將被選擇讓您簽字。
+popup.accountSigning.selectAccounts.signAll=簽署所有付款方式
+popup.accountSigning.selectAccounts.datePicker=選擇要簽署的帳戶的時間點
 
-popup.accountSigning.confirmSelectedAccounts.headline=Confirm selected payment accounts
-popup.accountSigning.confirmSelectedAccounts.description=Based on your input, {0} payment accounts will be selected.
-popup.accountSigning.confirmSelectedAccounts.button=Confirm payment accounts
-popup.accountSigning.signAccounts.headline=Confirm signing of payment accounts
-popup.accountSigning.signAccounts.description=Based on your selection, {0} payment accounts will be signed.
-popup.accountSigning.signAccounts.button=Sign payment accounts
-popup.accountSigning.signAccounts.ECKey=Enter private arbitrator key
-popup.accountSigning.signAccounts.ECKey.error=Bad arbitrator ECKey
+popup.accountSigning.confirmSelectedAccounts.headline=確認選定的付款帳戶
+popup.accountSigning.confirmSelectedAccounts.description=根據您的輸入，將選擇 {0} 支付帳戶。
+popup.accountSigning.confirmSelectedAccounts.button=確認付款賬戶
+popup.accountSigning.signAccounts.headline=確認簽署付款賬戶
+popup.accountSigning.signAccounts.description=根據您的選擇，{0} 付款帳戶將被簽署。
+popup.accountSigning.signAccounts.button=簽署付款賬戶
+popup.accountSigning.signAccounts.ECKey=輸入仲裁員金鑰
+popup.accountSigning.signAccounts.ECKey.error=不正確的仲裁員 ECKey
 
-popup.accountSigning.success.headline=Congratulations
-popup.accountSigning.success.description=All {0} payment accounts were successfully signed!
-popup.accountSigning.generalInformation=You'll find the signing state of all your accounts in the account section.\n\nFor further information, please visit https://docs.bisq.network/payment-methods#account-signing.
-popup.accountSigning.signedByArbitrator=One of your payment accounts has been verified and signed by an arbitrator. Trading with this account will automatically sign your trading peer''s account after a successful trade.\n\n{0}
-popup.accountSigning.signedByPeer=One of your payment accounts has been verified and signed by a trading peer. Your initial trading limit will be lifted and you''ll be able to sign other accounts in {0} days from now.\n\n{1}
-popup.accountSigning.peerLimitLifted=The initial limit for one of your accounts has been lifted.\n\n{0}
-popup.accountSigning.peerSigner=One of your accounts is mature enough to sign other payment accounts and the initial limit for one of your accounts has been lifted.\n\n{0}
+popup.accountSigning.success.headline=恭喜
+popup.accountSigning.success.description=所有 {0} 支付賬戶已成功簽署！
+popup.accountSigning.generalInformation=您將在帳戶頁面找到所有賬戶的簽名狀態。\n\n更多資訊，請訪問https://docs.bisq.network/payment-methods#account-signing.
+popup.accountSigning.signedByArbitrator=您的一個付款帳戶已被認證以及被仲裁員簽署。交易成功後，使用此帳戶將自動簽署您的交易夥伴的帳戶。\n\n{0}
+popup.accountSigning.signedByPeer=您的一個付款帳戶已經被交易夥伴驗證和簽署。您的初始交易限額將被取消，您將能夠在{0}天后簽署其他帳戶。
+popup.accountSigning.peerLimitLifted=您其中一個帳戶的初始限額已被取消。\n\n{0}
+popup.accountSigning.peerSigner=您的一個帳戶已足夠成熟，可以簽署其他付款帳戶，您的一個帳戶的初始限額已被取消。\n\n{0}
 
 ####################################################################
 # Notifications
@@ -2152,7 +2152,7 @@ systemTray.show=顯示應用程式視窗
 systemTray.hide=隱藏應用程式視窗
 systemTray.info=關於 Bisq 資訊
 systemTray.exit=退出
-systemTray.tooltip=Bisq：去中心化交易網路
+systemTray.tooltip=Bisq: A decentralized bitcoin exchange network
 
 
 ####################################################################
@@ -2188,7 +2188,7 @@ list.currency.editList=編輯幣種列表
 
 table.placeholder.noItems=最近沒有可用的 {0}
 table.placeholder.noData=最近沒有可用資料
-table.placeholder.processingData=Processing data...
+table.placeholder.processingData=處理資料…
 
 
 peerInfoIcon.tooltip.tradePeer=交易夥伴
@@ -2212,7 +2212,7 @@ peerInfo.nrOfTrades=已完成交易數量
 peerInfo.notTradedYet=你還沒有與他交易過。
 peerInfo.setTag=設定該物件的標籤
 peerInfo.age.noRisk=支付賬戶賬齡
-peerInfo.age.chargeBackRisk=Time since signing
+peerInfo.age.chargeBackRisk=自簽字
 peerInfo.unknownAge=賬齡未知
 
 addressTextField.openWallet=開啟您的預設比特幣錢包
@@ -2273,7 +2273,7 @@ BTC_REGTEST=比特幣迴歸測試
 # suppress inspection "UnusedProperty"
 BTC_DAO_TESTNET=比特幣測試網路（棄用）
 # suppress inspection "UnusedProperty"
-BTC_DAO_BETANET=Bisq DAO Betanet (Bitcoin Mainnet)
+BTC_DAO_BETANET=Bisq DAO 測試網路（比特幣主要網路）
 # suppress inspection "UnusedProperty"
 BTC_DAO_REGTEST=比特幣 DAO 迴歸測試
 
@@ -2335,7 +2335,7 @@ payment.bank.country=銀行所在國
 payment.account.name.email=賬戶擁有者姓名/電子郵箱
 payment.account.name.emailAndHolderId=賬戶擁有者姓名/電子郵箱 / {0}
 payment.bank.name=銀行名稱
-payment.select.account=選擇賬戶型別
+payment.select.account=選擇賬戶類型
 payment.select.region=選擇地區
 payment.select.country=選擇國家
 payment.select.bank.country=選擇銀行所在國
@@ -2372,7 +2372,7 @@ payment.accepted.banks=接受的銀行（ID）
 payment.mobile=手機號碼
 payment.postal.address=郵寄地址
 payment.national.account.id.AR=CBU 號碼
-shared.accountSigningState=Account signing status
+shared.accountSigningState=賬戶簽署狀態
 
 #new
 payment.altcoin.address.dyn={0}  地址
@@ -2381,7 +2381,7 @@ payment.accountNr=賬號：
 payment.emailOrMobile=電子郵箱或手機號碼
 payment.useCustomAccountName=使用自定義名稱
 payment.maxPeriod=最大允許交易時限
-payment.maxPeriodAndLimit=Max. trade duration: {0} / Max. buy: {1} / Max. sell: {2} / Account age: {3}
+payment.maxPeriodAndLimit=最大交易時間：{0}/ 最大買入：{1}/ 最大出售：{2}/賬齡：{3}
 payment.maxPeriodAndLimitCrypto=最大交易期限：{0}/最大交易限額：{1}
 payment.currencyWithSymbol=貨幣：{0}
 payment.nameOfAcceptedBank=接受的銀行名稱
@@ -2394,7 +2394,7 @@ payment.bankIdOptional=銀行 ID（BIC/SWIFT）（可選）
 payment.branchNr=分行編碼
 payment.branchNrOptional=分行編碼（可選）
 payment.accountNrLabel=賬號（IBAN）
-payment.accountType=賬戶型別
+payment.accountType=賬戶類型
 payment.checking=檢查
 payment.savings=儲存
 payment.personalId=個人 ID
@@ -2404,13 +2404,13 @@ payment.moneyGram.info=使用 MoneyGram 時，BTC 買方必須將授權號碼和
 payment.westernUnion.info=使用 Western Union 時，BTC 買方必須通過電子郵件將 MTCN（運單號）和收據照片傳送給 BTC 賣方。收據上必須清楚地顯示賣方的全名、城市、國家和金額。買方將在交易過程中顯示賣方的電子郵件。
 payment.halCash.info=使用 HalCash 時，BTC 買方需要通過手機簡訊向 BTC 賣方傳送 HalCash 程式碼。\n\n請確保不要超過銀行允許您用半現金匯款的最高金額。每次取款的最低金額是 10 歐元，最高金額是 10 歐元。金額是 600 歐元。對於重複取款，每天每個接收者 3000 歐元，每月每個接收者 6000 歐元。請與您的銀行核對這些限額，以確保它們使用與此處所述相同的限額。\n\n提現金額必須是 10 歐元的倍數，因為您不能從 ATM 機提取其他金額。 create-offer 和 take-offer 螢幕中的 UI 將調整 BTC 金額，使 EUR 金額正確。你不能使用基於市場的價格，因為歐元的數量會隨著價格的變化而變化。\n
 payment.limits.info=請注意，所有銀行轉賬都有一定的退款風險。\n\n為了降低這一風險，Bisq 基於兩個因素對每筆交易設定了限制：\n\n1. 使用的付款方法的預估退款風險水平\n2. 您的付款方式的賬齡\n\n您現在建立的帳戶是新的，它的賬齡為零。隨著你的賬戶在兩個月的時間裡增長，你的每筆交易限額也會隨之增長：\n\n●在第一個月，您的每筆交易限額為 {0}\n●在第二個月，您的每筆交易限額將為 {1}\n●第二個月後，您的每筆交易限額為 {2}\n\n請注意，您可以交易的總次數沒有限制。
-payment.limits.info.withSigning=To limit chargeback risk, Bisq sets per-trade buy limits based on the following 2 factors:\n\n1. General chargeback risk for the payment method\n2. Account signing status\n\nThis payment account you just created carries some chargeback risk and is not yet signed by an arbitrator or trusted peer, so it is limited to buying {0} per trade. After it is signed, buy limits will increase as follows:\n\n● Before signing, and up to 30 days after signing, your per-trade buy limit will be {0}\n● 30 days after signing, your per-trade buy limit will be {1}\n● 60 days after signing, your per-trade buy limit will be {2}\n\nSell limits are not affected by account signing, and increase merely as account age increases. More information is at https://docs.bisq.network/payment-methods#account-signing.\n\nThere are no limits on the number of trades you can make.
+payment.limits.info.withSigning=為了降低這一風險，Bisq 基於兩個因素對每筆交易設定了限制：\n\n1. 使用的付款方法的預估退款風險水平\n2. 您的付款方式的賬齡\n\n您剛剛建立的這個支付帳戶有一定的退款風險，而且還沒有仲裁員或受信任的夥伴簽署，所以它只能在每筆交易中購買 {0} 。簽署後，購買限額將增加如下:\n\n●在簽署前，以及簽署後30天內，您每筆交易的購買限額將為 {0}\n●在簽署後的第二個月，您的每筆交易限額將為 {1}\n●在簽署後第二個月後，您的每筆交易限額為 {2}\n\n銷售限額不受帳戶簽署的影響，並且僅隨著賬齡的增加而增加。更多資訊請訪問 https://docs.bisq.network/payment-methods#account-signing。\n\n請注意，您可以交易的總次數沒有限制。
 
 payment.cashDeposit.info=請確認您的銀行允許您將現金存款匯入他人賬戶。例如，美國銀行和富國銀行不再允許此類存款。
 
 payment.revolut.info=請確保您用於您的  Revolut 賬戶的電話號碼是註冊在  Revolut 上的，否則 BTC 買家無法將資金髮送給您。
 
-payment.usPostalMoneyOrder.info=Money orders are one of the more private fiat purchase methods available on Bisq.\n\nHowever, please be aware of potentially increased risks associated with their use. Bisq will not bear any responsibility in case a sent money order is stolen, and the mediator or arbitrator will in such cases award the BTC to the sender of the money order, provided they can produce tracking information and receipts. It may be advisable for the sender to write the BTC seller's name on the money order, in order to minimize the risk that the money order is cashed by someone else.
+payment.usPostalMoneyOrder.info=匯款單是 Bisq 上比較私人的法定貨幣購買方式之一。\n\n但是，請注意與它們的使用相關的潛在增加的風險。如果匯款單被盜， Bisq 將不承擔任何責任，在這種情況下，調解員或仲裁員將把 BTC 判給匯款單的傳送方，前提是他們能夠提供跟蹤資訊和收據。寄件人最好在匯款單上寫上賣方的名稱，以減低匯款單被他人兌現的風險。
 
 payment.f2f.contact=聯絡方式
 payment.f2f.contact.prompt=您希望如何與交易夥伴聯絡？（電子郵箱、電話號碼、…）
@@ -2420,13 +2420,13 @@ payment.f2f.optionalExtra=可選的附加資訊
 payment.f2f.extra=附加資訊
 
 payment.f2f.extra.prompt=交易方可以定義“條款和條件”或新增公共聯絡資訊。它將與報價一同顯示。
-payment.f2f.info='Face to Face' trades have different rules and come with different risks than online transactions.\n\nThe main differences are:\n● The trading peers need to exchange information about the meeting location and time by using their provided contact details.\n● The trading peers need to bring their laptops and do the confirmation of 'payment sent' and 'payment received' at the meeting place.\n● If a maker has special 'terms and conditions' they must state those in the 'Additional information' text field in the account.\n● By taking an offer the taker agrees to the maker's stated 'terms and conditions'.\n● In case of a dispute the mediator or arbitrator cannot help much as it is usually hard to get tamper proof evidence of what happened at the meeting. In such cases the BTC funds might get locked indefinitely or until the trading peers come to an agreement.\n\nTo be sure you fully understand the differences with 'Face to Face' trades please read the instructions and recommendations at: 'https://docs.bisq.network/trading-rules.html#f2f-trading'
+payment.f2f.info=與網上交易相比，“面對面”交易有不同的規則，也有不同的風險。\n\n主要區別是：\n●交易夥伴需要使用他們提供的聯絡方式交換關於會面地點和時間的資訊。\n●交易雙方需要攜帶膝上型電腦，在會面地點確認“已傳送付款”和“已收到付款”。\n●如果交易方有特殊的“條款和條件”，他們必須在賬戶的“附加資訊”文字框中聲明這些條款和條件。\n●在發生爭議時，調解員或仲裁員不能提供太多幫助，因為通常很難獲得有關會面上所發生情況的篡改證據。在這種情況下，BTC 資金可能會被無限期鎖定，或者直到交易雙方達成協議。\n\n為確保您完全理解“面對面”交易的不同之處，請閱讀以下說明和建議：“https://docs.bisq.network/trading-rules.html#f2f-trading”
 payment.f2f.info.openURL=開啟網頁
-payment.f2f.offerbook.tooltip.countryAndCity=Country and city: {0} / {1}
+payment.f2f.offerbook.tooltip.countryAndCity=國家/城市：{0} /  {1}
 payment.f2f.offerbook.tooltip.extra=附加資訊：{0}
 
 payment.japan.bank=銀行
-payment.japan.branch=Branch
+payment.japan.branch=分行
 payment.japan.account=賬戶
 payment.japan.recipient=名稱
 
@@ -2623,12 +2623,12 @@ validation.pattern=輸入格式必須為：{0}
 validation.noHexString=輸入不是十六進位制格式。
 validation.advancedCash.invalidFormat=必須是有效的電子郵箱或錢包 ID 的格式為：X000000000000
 validation.invalidUrl=輸入的不是有效 URL 連結。
-validation.mustBeDifferent=Your input must be different from the current value
-validation.cannotBeChanged=引數不能更改
+validation.mustBeDifferent=您輸入的值必須與當前值不同
+validation.cannotBeChanged=參數不能更改
 validation.numberFormatException=數字格式異常 {0}
 validation.mustNotBeNegative=不能輸入負值
-validation.phone.missingCountryCode=Need two letter country code to validate phone number
-validation.phone.invalidCharacters=Phone number {0} contains invalid characters
-validation.phone.insufficientDigits=Not enough digits in {0} for a valid phone number
-validation.phone.tooManyDigits=Too many digits in {0} to be a valid phone number
-validation.phone.invalidDialingCode=Country dialing code in number {0} is invalid for country {1}.  The correct dialing code is {2}.
+validation.phone.missingCountryCode=需要兩個字母的國家程式碼來驗證電話號碼
+validation.phone.invalidCharacters=電話號碼 {0} 包含無效字元
+validation.phone.insufficientDigits={0} 中沒有足夠的數字作為有效的電話號碼
+validation.phone.tooManyDigits={0} 中的數字太多，不是有效的電話號碼
+validation.phone.invalidDialingCode=數字 {0} 中的國家撥號程式碼對於國家 {1} 無效。正確的撥號號碼是 {2} 。

core/src/main/resources/wallet/checkpoints.txt

@@ -1,6 +1,6 @@
 TXT CHECKPOINTS 1
 0
-298
+300
 AAAAAAAAB+EH4QfhAAAH4AEAAABjl7tqvU/FIcDT9gcbVlA4nwtFUbxAtOawZzBpAAAAAKzkcK7NqciBjI/ldojNKncrWleVSgDfBCCn3VRrbSxXaw5/Sf//AB0z8Bkv
 AAAAAAAAD8EPwQ/BAAAPwAEAAADfP83Sx8MZ9RsrnZCvqzAwqB2Ma+ZesNAJrTfwAAAAACwESaNKhvRgz6WuE7UFdFk1xwzfRY/OIdIOPzX5yaAdjnWUSf//AB0GrNq5
 AAAAAAAAF6EXoRehAAAXoAEAAADonWzAaUAKd30XT3NnHKobZMnLOuHdzm/xtehsAAAAAD8cUJA6NBIHHcqPHLc4IrfHw+6mjCGu3e+wRO81EvpnMVqrSf//AB1ffy8G
@@ -299,3 +299,5 @@ CHfrzMTnNH4hN5sYAAkTIAAA/z+HbkJNgw5nAYXntDFX57V72pTVvvZIDAAAAAAAAAAAAIaAZN99p5iv
 CM0W0f4hiP5fWVciAAkbAAAAACD949mnNSIOTWH92aZDY80eG/VA3HF4DwAAAAAAAAAAAHz7539g8IjaBVxv7M2N+/bPcmY6Nik4r0IZMxOPFbbAkSCNXSQPFhcRiJ3V
 CSh7DyaX/kiv4GZrAAki4AAAQCBkJtVoaqbUq7I+EEmnUlsQDTY688BYFQAAAAAAAAAAAN8JpiIqwffNT/xQxjdHpDrq3zyloPsBWmA2IQWQQO0LdzufXVyjFReQWFDz
 CYWm6xCIhvXC3VCXAAkqwAAgACBa35Ut2KFYNsnRSMn44AHqcTe/OkZ2BgAAAAAAAAAAAF4Xg+DOwujvmF1htTEQCwMy9wsWY5yhtvG2eTnKXEEkXcmwXd+OFBc2QzNB
+Cee2T+SyTIWzqlyJAAkyoAAAACAwzYQY7c/FVOgHRQts7iXBTtoSZjkkDgAAAAAAAAAAAMBIbtwe998H0gZ6M6rpIxqKxjCjoZalWQSeOQmxxfDZHKnEXdEgFhcHWk2u
+CkLRjbL/8nH1LHItAAk6gAAAACCOJE0sVbxAPKpdbq8PkiFw5BPrHgL7AgAAAAAAAAAAAOA7TZ33LY2yMqILsv81xDOpnxRn85H3W19iGA2W8G1qpMTWXT6yFRee+RYz

desktop/package/linux/Dockerfile

@@ -8,7 +8,7 @@
 
 # pull base image
 FROM openjdk:8-jdk
-ENV version 1.2.3-SNAPSHOT
+ENV version 1.2.4-SNAPSHOT
 
 RUN apt-get update && apt-get install -y --no-install-recommends openjfx && rm -rf /var/lib/apt/lists/* &&
 apt-get install -y vim fakeroot

desktop/package/linux/package.sh

@@ -6,7 +6,7 @@
 #   - Update version below
 #   - Ensure JAVA_HOME below is pointing to OracleJDK 10 directory
 
-version=1.2.3-SNAPSHOT
+version=1.2.4-SNAPSHOT
 if [ ! -f "$JAVA_HOME/bin/javapackager" ]; then
 	if [ -d "/usr/lib/jvm/jdk-10.0.2" ]; then
     	JAVA_HOME=/usr/lib/jvm/jdk-10.0.2

desktop/package/linux/release.sh

@@ -4,7 +4,7 @@
 # Prior to running this script:
 #   - Update version below
 
-version=1.2.3-SNAPSHOT
+version=1.2.4-SNAPSHOT
 base_dir=$( cd "$(dirname "$0")" ; pwd -P )/../../..
 package_dir=$base_dir/desktop/package
 release_dir=$base_dir/desktop/release/$version

desktop/package/macosx/Info.plist

@@ -5,10 +5,10 @@
         <!-- See: https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html -->
 
         <key>CFBundleVersion</key>
-        <string>1.2.3</string>
+        <string>1.2.4</string>
 
         <key>CFBundleShortVersionString</key>
-        <string>1.2.3</string>
+        <string>1.2.4</string>
 
         <key>CFBundleExecutable</key>
         <string>Bisq</string>

desktop/package/macosx/create_app.sh

@@ -6,7 +6,7 @@ mkdir -p deploy
 
 set -e
 
-version="1.2.3-SNAPSHOT"
+version="1.2.4-SNAPSHOT"
 
 cd ..
 ./gradlew :desktop:build -x test shadowJar

desktop/package/macosx/finalize.sh

@@ -2,7 +2,7 @@
 
 cd ../../
 
-version="1.2.3-SNAPSHOT"
+version="1.2.4-SNAPSHOT"
 
 target_dir="releases/$version"
 

desktop/package/macosx/insert_snapshot_version.sh

@@ -2,7 +2,7 @@
 
 cd $(dirname $0)/../../../
 
-version=1.2.3
+version=1.2.4
 
 find . -type f \( -name "finalize.sh" \
 -o -name "create_app.sh" \

desktop/package/macosx/replace_version_number.sh

@@ -2,8 +2,8 @@
 
 cd $(dirname $0)/../../../
 
-oldVersion=1.2.2
-newVersion=1.2.3
+oldVersion=1.2.3
+newVersion=1.2.4
 
 find . -type f \( -name "finalize.sh" \
 -o -name "create_app.sh" \

desktop/package/windows/package.bat

@@ -8,7 +8,7 @@
 
 @echo off
 
-set version=1.2.3-SNAPSHOT
+set version=1.2.4-SNAPSHOT
 if not exist "%JAVA_HOME%\bin\javapackager.exe" (
     if not exist "%ProgramFiles%\Java\jdk-10.0.2" (
         echo Javapackager not found. Update JAVA_HOME variable to point to OracleJDK.

desktop/package/windows/release.bat

@@ -6,7 +6,7 @@
 
 @echo off
 
-set version=1.2.3-SNAPSHOT
+set version=1.2.4-SNAPSHOT
 set release_dir=%~dp0..\..\..\releases\%version%
 set package_dir=%~dp0..
 

relay/src/main/resources/version.txt

@@ -1 +1 @@
-1.2.3-SNAPSHOT
+1.2.4-SNAPSHOT

seednode/src/main/java/bisq/seednode/SeedNodeMain.java

@@ -34,7 +34,7 @@ import lombok.extern.slf4j.Slf4j;
 
 @Slf4j
 public class SeedNodeMain extends ExecutableForAppWithP2p {
-    private static final String VERSION = "1.2.3";
+    private static final String VERSION = "1.2.4";
     private SeedNode seedNode;
 
     public SeedNodeMain() {