mirror of
https://github.com/bisq-network/bisq.git
synced 2024-11-19 09:52:23 +01:00
Merge pull request #3970 from bisq-network/release/v1.2.6
Release/v1.2.6
This commit is contained in:
sqrrm
GitHub
commit
23c2052fe6
@ -25,6 +25,6 @@ import bisq.asset.RegexAddressValidator;
|
||||
public class LiquidBitcoin extends Coin {
|
||||
|
||||
public LiquidBitcoin() {
|
||||
super("Liquid Bitcoin", "L-BTC", new RegexAddressValidator("^([a-km-zA-HJ-NP-Z1-9]{26,35}|[a-km-zA-HJ-NP-Z1-9]{80}|[a-z]{2,5}1[ac-hj-np-z02-9]{8,87}|[A-Z]{2,5}1[AC-HJ-NP-Z02-9]{8,87})$"));
|
||||
super("Liquid Bitcoin", "L-BTC", new RegexAddressValidator("^([a-km-zA-HJ-NP-Z1-9]{26,35}|[a-km-zA-HJ-NP-Z1-9]{80}|[a-z]{2,5}1[ac-hj-np-z02-9]{8,87}|[A-Z]{2,5}1[AC-HJ-NP-Z02-9]{8,87})$", "validation.altcoin.liquidBitcoin.invalidAddress"));
|
||||
}
|
||||
}
|
||||
|
||||
40
assets/src/test/java/bisq/asset/coins/LiquidBitcoinTest.java
Normal file
40
assets/src/test/java/bisq/asset/coins/LiquidBitcoinTest.java
Normal file
@ -0,0 +1,40 @@
|
||||
/*
|
||||
* This file is part of Bisq.
|
||||
*
|
||||
* Bisq is free software: you can redistribute it and/or modify it
|
||||
* under the terms of the GNU Affero General Public License as published by
|
||||
* the Free Software Foundation, either version 3 of the License, or (at
|
||||
* your option) any later version.
|
||||
*
|
||||
* Bisq is distributed in the hope that it will be useful, but WITHOUT
|
||||
* ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
|
||||
* FITNESS FOR A PARTICULAR PURPOSE. See the GNU Affero General Public
|
||||
* License for more details.
|
||||
*
|
||||
* You should have received a copy of the GNU Affero General Public License
|
||||
* along with Bisq. If not, see <http://www.gnu.org/licenses/>.
|
||||
*/
|
||||
|
||||
package bisq.asset.coins;
|
||||
|
||||
import bisq.asset.AbstractAssetTest;
|
||||
|
||||
public class LiquidBitcoinTest extends AbstractAssetTest {
|
||||
|
||||
|
||||
public LiquidBitcoinTest() {
|
||||
super(new LiquidBitcoin());
|
||||
}
|
||||
|
||||
@Override
|
||||
public void testValidAddresses() {
|
||||
assertValidAddress("VJL6mu5gqT4pRzpd28Y6aXg9murwJpd25EBwMtrnCN82n6z6i5kMLKnN63nyaCgRuJWZu4EFFV7gp9Yb");
|
||||
assertValidAddress("Gq3AeVacy6EUWSJKsV4NScyYKvnM6Gf8We");
|
||||
}
|
||||
|
||||
@Override
|
||||
public void testInvalidAddresses() {
|
||||
assertInvalidAddress("lq1qqgu6g99aa4y7fly26gwj3k69t2kgx8eshn8gqacsul9yhpcgtvweyzuqt6cn3fjawvwaluq6ls6t9qnvg4jgwffyycwmgqh0h"); //no native segwit address support
|
||||
assertInvalidAddress("lq1qqgu6g99aa4y7fly26gwj3k69t2kgx8eshn8gqacsul9yhpcgtvweyzuqt6cn3fjawvwaluq6ls6t9qnvg4jgwffyycwmgqsdf");
|
||||
}
|
||||
}
|
||||
@ -323,7 +323,7 @@ configure(project(':desktop')) {
|
||||
apply plugin: 'witness'
|
||||
apply from: '../gradle/witness/gradle-witness.gradle'
|
||||
|
||||
version = '1.2.5-SNAPSHOT'
|
||||
version = '1.2.6'
|
||||
|
||||
mainClassName = 'bisq.desktop.app.BisqAppMain'
|
||||
|
||||
|
||||
@ -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.5";
|
||||
public static final String VERSION = "1.2.6";
|
||||
|
||||
public static int getMajorVersion(String version) {
|
||||
return getSubVersion(version, 0);
|
||||
|
||||
@ -90,7 +90,7 @@ public class OfferForJson {
|
||||
this.currencyCode = currencyCode;
|
||||
this.minAmount = minAmount.value;
|
||||
this.amount = amount.value;
|
||||
this.price = price != null ? price.getValue() : 0;
|
||||
this.price = price.getValue();
|
||||
this.date = date.getTime();
|
||||
this.id = id;
|
||||
this.useMarketBasedPrice = useMarketBasedPrice;
|
||||
|
||||
@ -3268,6 +3268,7 @@ validation.altcoin.wrongStructure=Address validation failed because it does not
|
||||
validation.altcoin.ltz.zAddressesNotSupported=LTZ address need to start with L. Addresses starting with z are not supported.
|
||||
validation.altcoin.zAddressesNotSupported=ZEC address need to start with t. Addresses starting with z are not supported.
|
||||
validation.altcoin.invalidAddress=Address is not a valid {0} address! {1}
|
||||
validation.altcoin.liquidBitcoin.invalidAddress=Native segwit addresses (those starting with 'lq') are not supported.
|
||||
validation.bic.invalidLength=Input length is neither 8 nor 11
|
||||
validation.bic.letters=Bank and Country code must be letters
|
||||
validation.bic.invalidLocationCode=BIC contains invalid location code
|
||||
@ -3305,3 +3306,4 @@ 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.invalidAddressList=Must be comma separated list of valid addresses
|
||||
validation
|
||||
|
||||
@ -189,14 +189,14 @@ shared.makerTxFee=Ersteller: {0}
|
||||
shared.takerTxFee=Abnehmer: {0}
|
||||
shared.securityDepositBox.description=Kaution für BTC {0}
|
||||
shared.iConfirm=Ich bestätige
|
||||
shared.tradingFeeInBsqInfo=equivalent to {0} used as trading fee
|
||||
shared.tradingFeeInBsqInfo=gleichwertig mit {0} als Trading-Gebühr
|
||||
shared.openURL=Öffne {0}
|
||||
shared.fiat=Fiat
|
||||
shared.crypto=Crypto
|
||||
shared.all=Alle
|
||||
shared.edit=Bearbeiten
|
||||
shared.advancedOptions=Erweiterte Optionen
|
||||
shared.interval=Interval
|
||||
shared.interval=Intervall
|
||||
shared.actions=Aktionen
|
||||
shared.buyerUpperCase=Käufer
|
||||
shared.sellerUpperCase=Verkäufer
|
||||
@ -255,7 +255,7 @@ mainView.footer.bsqInfo.synchronizing=/ Synchronisiere DAO
|
||||
mainView.footer.btcInfo.synchronizingWith=Synchronisiere mit
|
||||
mainView.footer.btcInfo.synchronizedWith=Synchronisiert mit
|
||||
mainView.footer.btcInfo.connectingTo=Verbinde mit
|
||||
mainView.footer.btcInfo.connectionFailed=Verbindung fehlgeschlagen
|
||||
mainView.footer.btcInfo.connectionFailed=Verbindung fehlgeschlagen zu
|
||||
mainView.footer.p2pInfo=Bisq-Netzwerk-Peers: {0}
|
||||
mainView.footer.daoFullNode=DAO Full Node
|
||||
|
||||
@ -461,7 +461,7 @@ createOffer.setDeposit=Kaution des Käufers festlegen (%)
|
||||
createOffer.setDepositAsBuyer=Meine Kaution als Käufer festlegen (%)
|
||||
createOffer.securityDepositInfo=Die Kaution ihres Käufers wird {0}
|
||||
createOffer.securityDepositInfoAsBuyer=Ihre Kaution als Käufer wird {0}
|
||||
createOffer.minSecurityDepositUsed=Min. buyer security deposit is used
|
||||
createOffer.minSecurityDepositUsed=Min. Kaution des Käufers wird verwendet
|
||||
|
||||
|
||||
####################################################################
|
||||
@ -601,7 +601,8 @@ portfolio.pending.step2_seller.f2fInfo.headline=Kontaktinformation des Käufers
|
||||
portfolio.pending.step2_seller.waitPayment.msg=Die Kautionstransaktion hat mindestens eine Blockchain-Bestätigung.\nSie müssen warten bis der BTC-Käufer die {0}-Zahlung beginnt.
|
||||
portfolio.pending.step2_seller.warn=Der BTC-Käufer hat die {0}-Zahlung noch nicht getätigt.\nSie müssen warten bis die Zahlung begonnen wurde.\nWenn der Handel nicht bis {1} abgeschlossen wurde, wird der Vermittler diesen untersuchen.
|
||||
portfolio.pending.step2_seller.openForDispute=Der BTC-Käufer hat seine Zahlung nicht begonnen!\nDie maximal zulässige Frist für den Handel ist abgelaufen.\nSie können länger warten und dem Handelspartner mehr Zeit geben oder den Vermittler um Hilfe bitten.
|
||||
|
||||
portfolio.pending.step2_seller.refresh=Trade-Status aktualisieren
|
||||
portfolio.pending.step2_seller.refreshInfo=Manchmal werden P2P-Netzwerknachrichten, die die Zahlung bestätigen, nicht zugestellt, so dass der Trade ins Stocken gerät. Klicken Sie auf die Schaltfläche unten, damit Ihr Peer die letzte Nachricht erneut senden kann.
|
||||
tradeChat.chatWindowTitle=Chat-Fenster für Trade mit ID ''{0}''
|
||||
tradeChat.openChat=Chat-Fenster öffnen
|
||||
tradeChat.rules=Sie können mit Ihrem Trade-Partner kommunizieren, um mögliche Probleme mit diesem Trade zu lösen.\nEs ist nicht zwingend erforderlich, im Chat zu antworten.\nWenn ein Trader gegen eine der folgenden Regeln verstößt, eröffnen Sie einen Streitfall und melden Sie ihn dem Mediator oder Vermittler.\n\nChat-Regeln:\n\t● Senden Sie keine Links (Risiko von Malware). Sie können die Transaktions-ID und den Namen eines Block-Explorers senden.\n\t● Senden Sie keine Seed-Wörter, Private Keys, Passwörter oder andere sensible Informationen!\n\t● Traden Sie nicht außerhalb von Bisq (keine Sicherheit).\n\t● Beteiligen Sie sich nicht an Betrugsversuchen in Form von Social Engineering.\n\t● Wenn ein Partner nicht antwortet und es vorzieht, nicht über den Chat zu kommunizieren, respektieren Sie seine Entscheidung.\n\t● Beschränken Sie Ihre Kommunikation auf das Traden. Dieser Chat ist kein Messenger-Ersatz oder eine Trollbox.\n\t● Bleiben Sie im Gespräch freundlich und respektvoll.
|
||||
@ -919,7 +920,7 @@ setting.preferences.addAltcoin=Altcoin hinzufügen
|
||||
setting.preferences.displayOptions=Darstellungsoptionen
|
||||
setting.preferences.showOwnOffers=Eigenen Angebote im Angebotsbuch zeigen
|
||||
setting.preferences.useAnimations=Animationen abspielen
|
||||
setting.preferences.useDarkMode=Dark Mode (Beta) verwenden
|
||||
setting.preferences.useDarkMode=Nacht-Modus benutzen
|
||||
setting.preferences.sortWithNumOffers=Marktlisten nach Anzahl der Angebote/Trades sortieren
|
||||
setting.preferences.resetAllFlags=Alle \"Nicht erneut anzeigen\"-Häkchen zurücksetzen
|
||||
setting.preferences.reset=Zurücksetzen
|
||||
@ -952,6 +953,7 @@ settings.net.warn.usePublicNodes=Falls Sie das öffentliche Bitcoin-Netzwerk ver
|
||||
settings.net.warn.usePublicNodes.useProvided=Nein, bereitgestellte Knoten verwenden
|
||||
settings.net.warn.usePublicNodes.usePublic=Ja, öffentliches Netzwerk verwenden
|
||||
settings.net.warn.useCustomNodes.B2XWarning=Bitte stellen Sie sicher, dass Sie sich mit einem vertrauenswürdigen Bitcoin-Core-Knoten verbinden!\n\nWenn Sie sich mit Knoten verbinden, die gegen die Bitcoin Core Konsensus-Regeln verstoßen, kann es zu Problemen in Ihrer Wallet und im Verlauf des Handelsprozesses kommen.\n\nBenutzer die sich zu oben genannten Knoten verbinden, sind für den verursachten Schaden verantwortlich. Dadurch entstandene Konflikte werden zugunsten des anderen Teilnehmers entschieden. Benutzer die unsere Warnungen und Sicherheitsmechanismen ignorieren wird keine technische Unterstützung geleistet!
|
||||
settings.net.warn.invalidBtcConfig=Die Verbindung zum Bitcoin-Netzwerk ist fehlgeschlagen, weil Ihre Konfiguration ungültig ist.\n\nIhre Konfiguration wurde zurückgesetzt, um stattdessen die bereitgestellten Bitcoin-Nodes zu verwenden. Sie müssen die Anwendung neu starten.
|
||||
settings.net.localhostBtcNodeInfo=(Hintergrundinformation: Falls Sie einen lokalen Bitcoin-Knoten einsetzen (localhost) werden Sie nur mit diesem verbunden.)
|
||||
settings.net.p2PPeersLabel=Verbundene Peers
|
||||
settings.net.onionAddressColumn=Onion-Adresse
|
||||
@ -1110,6 +1112,8 @@ account.altcoin.popup.pars.msg=Der Handel mit ParsiCoin auf Bisq setzt voraus, d
|
||||
|
||||
account.altcoin.popup.blk-burnt.msg=Um "Burnt Blackcoins" zu handeln, müssen Sie folgendes wissen:\n\nBurnt Blackcoins können nicht ausgegeben werden. Um sie auf Bisq zu handeln, müssen die Ausgabeskripte in der Form vorliegen: OP_RETURN OP_PUSHDATA, gefolgt von zugehörigen Datenbytes, die nach der Hex-Codierung Adressen darstellen. Beispielsweise haben Burnt Blackcoins mit der Adresse 666f6f ("foo" in UTF-8) das folgende Skript:\n\nOP_RETURN OP_PUSHDATA 666f6f\n\nUm Burnt Blackcoins zu erstellen, kann man den in einigen Wallets verfügbaren RPC-Befehl "burn" verwenden.\n\nFür mögliche Anwendungsfälle kann man einen Blick auf https://ibo.laboratorium.ee werfen.\n\nDa Burnt Blackcoins nicht ausgegeben werden können, können sie nicht wieder verkauft werden. "Verkaufen" von Burnt Blackcoins bedeutet, gewöhnliche Blackcoins zu verbrennen (mit zugehörigen Daten entsprechend der Zieladresse).\n\nIm Konfliktfall hat der BLK-Verkäufer den Transaktionshash zur Verfügung zu stellen.
|
||||
|
||||
account.altcoin.popup.liquidbitcoin.msg=Das Trading mit L-BTC auf Bisq setzt voraus, dass Sie Folgendes verstehen:\n\nWenn Sie L-BTC für einen Trade auf Bisq erhalten, können Sie nicht die mobile Blockstream Green Wallet App oder eine Custodial/Exchange Wallet verwenden. Sie dürfen L-BTC nur in der Liquid Elements Core Wallet oder eine andere L-BTC-Wallet erhalten, die es Ihnen ermöglicht, den Blinding Key für Ihre verdeckte L-BTC-Adresse zu erhalten.\n\nFalls eine Mediation erforderlich ist oder ein Trade-Konflikt entsteht, müssen Sie den Blinding Key für Ihre L-BTC-Empfangsadresse dem Bisq-Mediator oder dem Refund Agent mitteilen, damit dieser die Details Ihrer vertraulichen Transaktion auf seinem eigenen Elements Core Full Node überprüfen kann.\n\nWenn Sie dem Mediator oder Refund Agent die erforderlichen Informationen nicht zur Verfügung stellen, führt dies dazu, dass Sie den Streitfall verlieren. In allen Streitfällen trägt der L-BTC-Empfänger 100 % der Verantwortung für die Bereitstellung kryptographischer Beweise an den Mediator oder den Refund Agent.\n\nWenn Sie diese Anforderungen nicht verstehen, sollten Sie nicht mit L-BTC auf Bisq traden.
|
||||
|
||||
account.fiat.yourFiatAccounts=Ihre Nationalen Währungskonten
|
||||
|
||||
account.backup.title=Backup der Wallet erstellen
|
||||
@ -1212,7 +1216,7 @@ dao.tab.factsAndFigures=Zahlen, Daten & Fakten
|
||||
dao.tab.bsqWallet=BSQ-Wallet
|
||||
dao.tab.proposals=Führung der DAO
|
||||
dao.tab.bonding=Kopplung
|
||||
dao.tab.proofOfBurn=Listungsgebühr für Gut/Nachweis der Verbrennung
|
||||
dao.tab.proofOfBurn=Asset-Listungsgebühr/Nachweis der Verbrennung
|
||||
dao.tab.monitor=Netzwerkmonitor
|
||||
dao.tab.news=Neuigkeiten
|
||||
|
||||
@ -1229,7 +1233,7 @@ dao.reputationBalance=Merit-Wert (nicht ausgabefähig)
|
||||
|
||||
dao.tx.published.success=Ihre Transaktion wurde erfolgreich veröffentlicht.
|
||||
dao.proposal.menuItem.make=Antrag erstellen
|
||||
dao.proposal.menuItem.browse=Offene Vorschläge durchsuchen
|
||||
dao.proposal.menuItem.browse=Offene Vorschläge
|
||||
dao.proposal.menuItem.vote=Für Vorschläge stimmen
|
||||
dao.proposal.menuItem.result=Wahlergebnisse
|
||||
dao.cycle.headline=Wahlzyklus
|
||||
@ -1399,7 +1403,7 @@ dao.bond.dashboard.unlockingAmount=Entsperre Gelder (Warten Sie bis die Sperrzei
|
||||
dao.bond.reputation.header=Ein Pfand für Reputation hinterlegen
|
||||
dao.bond.reputation.table.header=Meine Pfänder für Reputation
|
||||
dao.bond.reputation.amount=Betrag von BSQ zu sperren
|
||||
dao.bond.reputation.time=Entsperrung-Zeit in Blöcken
|
||||
dao.bond.reputation.time=Entsperrzeit in Blöcken
|
||||
dao.bond.reputation.salt=Salt
|
||||
dao.bond.reputation.hash=Hash
|
||||
dao.bond.reputation.lockupButton=Sperren
|
||||
@ -1416,7 +1420,7 @@ dao.bond.bondedRoles=Gekoppelte Rollen
|
||||
dao.bond.details.header=Rollendetails
|
||||
dao.bond.details.role=Rolle
|
||||
dao.bond.details.requiredBond=Benötigt BSQ Kopplung
|
||||
dao.bond.details.unlockTime=Entsperrung-Zeit in Blöcken
|
||||
dao.bond.details.unlockTime=Entsperrzeit in Blöcken
|
||||
dao.bond.details.link=Link zur Rollenbeschreibung
|
||||
dao.bond.details.isSingleton=Kann von mehreren Rollenhalter genommen werden
|
||||
dao.bond.details.blocks={0} Blöcke
|
||||
@ -1427,7 +1431,7 @@ dao.bond.table.column.bondType=Pfand-Typ
|
||||
dao.bond.table.column.details=Details
|
||||
dao.bond.table.column.lockupTxId=Sperrung Tx ID
|
||||
dao.bond.table.column.bondState=Kopplungsstatus
|
||||
dao.bond.table.column.lockTime=Sperrzeit
|
||||
dao.bond.table.column.lockTime=Entsperrzeit
|
||||
dao.bond.table.column.lockupDate=Zeitpunkt der Sperrung
|
||||
|
||||
dao.bond.table.button.lockup=Sperren
|
||||
@ -1508,7 +1512,7 @@ dao.bond.bondedRoleType.BTC_DONATION_ADDRESS_OWNER=BTC Spendenadresse Besitzer
|
||||
dao.burnBsq.assetFee=Gut Listung
|
||||
dao.burnBsq.menuItem.assetFee=Gut Listungsgebühr
|
||||
dao.burnBsq.menuItem.proofOfBurn=Nachweis der Verbrennung
|
||||
dao.burnBsq.header=Listungsgebühr für Gut
|
||||
dao.burnBsq.header=Asset-Listungsgebühr
|
||||
dao.burnBsq.selectAsset=Gut auswählen
|
||||
dao.burnBsq.fee=Gebühr
|
||||
dao.burnBsq.trialPeriod=Probezeit
|
||||
@ -1850,12 +1854,16 @@ dao.factsAndFigures.dashboard.avgPrice30=30 Tage durchschnittlicher BSQ/BTC-Hand
|
||||
dao.factsAndFigures.dashboard.marketCap=Marktkapitalisierung (basierend auf Handelspreis)
|
||||
dao.factsAndFigures.dashboard.availableAmount=Insgesamt verfügbare BSQ
|
||||
|
||||
dao.factsAndFigures.supply.issuedVsBurnt=Ausgestellte BSQ v. verbrannte BSQ
|
||||
|
||||
dao.factsAndFigures.supply.issued=Ausgestellte BSQ
|
||||
dao.factsAndFigures.supply.genesisIssueAmount=Ausgestellte BSQ in Genesis-Transaktion
|
||||
dao.factsAndFigures.supply.compRequestIssueAmount=Ausgestellte BSQ für Entlohnungsanträge
|
||||
dao.factsAndFigures.supply.reimbursementAmount=Ausgestellte BSQ für Rückerstattungsanträge
|
||||
|
||||
dao.factsAndFigures.supply.burnt=Verbrannte BSQ (Gebühren und Proof-of-Burn)
|
||||
dao.factsAndFigures.supply.burntMovingAverage=15-Tage-Gleitender Durchschnitt
|
||||
dao.factsAndFigures.supply.burntZoomToInliers=Zoom zu Inliers
|
||||
|
||||
dao.factsAndFigures.supply.locked=Globaler Zustand der gesperrten BSQ
|
||||
dao.factsAndFigures.supply.totalLockedUpAmount=In Pfänden gesperrt
|
||||
@ -2148,6 +2156,7 @@ popup.securityRecommendation.headline=Wichtige Sicherheitsempfehlung
|
||||
popup.securityRecommendation.msg=Wir würden Sie gerne daran erinnern, sich zu überlegen, den Passwortschutz Ihrer Wallet zu verwenden, falls Sie diesen noch nicht aktiviert haben.\n\nEs wird außerdem dringend empfohlen, dass Sie die Wallet-Seed-Wörter aufschreiben. Diese Seed-Wörter sind wie ein Master-Passwort zum Wiederherstellen ihrer Bitcoin-Wallet.\nIm \"Wallet-Seed\"-Abschnitt finden Sie weitere Informationen.\n\nZusätzlich sollten Sie ein Backup des ganzen Anwendungsdatenordners im \"Backup\"-Abschnitt erstellen.
|
||||
|
||||
popup.bitcoinLocalhostNode.msg=Bisq hat einen lokal laufenden Bitcoin-Core-Knoten entdeckt (bei localhost),\nStellen Sie bitte sicher, dass dieser Knoten vollständig synchronisiert ist, bevor Sie Bisq starten und nicht im pruned Modus läuft.
|
||||
popup.bitcoinLocalhostNode.additionalRequirements=\n\nSeit Bitcoin Core v0.19 müssen Sie die Bloomfilter manuell aktivieren, indem Sie in Ihrer bitcoin.conf Konfigurationsdatei peerbloomfilters=1 setzen.
|
||||
|
||||
popup.shutDownInProgress.headline=Anwendung wird heruntergefahren
|
||||
popup.shutDownInProgress.msg=Das Herunterfahren der Anwendung kann einige Sekunden dauern.\nBitte unterbrechen Sie diesen Vorgang nicht.
|
||||
@ -2237,7 +2246,7 @@ guiUtil.openWebBrowser.warning=Es wird eine Website im Webbrowser Ihres Betriebs
|
||||
guiUtil.openWebBrowser.doOpen=Website öffnen und nicht erneut fragen
|
||||
guiUtil.openWebBrowser.copyUrl=URL kopieren und abbrechen
|
||||
guiUtil.ofTradeAmount=vom Handelsbetrag
|
||||
guiUtil.requiredMinimum=(required minimum)
|
||||
guiUtil.requiredMinimum=(erforderliches Minimum)
|
||||
|
||||
####################################################################
|
||||
# Component specific
|
||||
@ -2693,3 +2702,4 @@ 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
|
||||
validation.phone.invalidDialingCode=Die Ländervorwahl in der Nummer {0} ist für das Land {1} ungültig. Die richtige Vorwahl ist {2}.
|
||||
validation.invalidAddressList=Muss eine kommagetrennte Liste der gültigen Adressen sein
|
||||
|
||||
@ -189,7 +189,7 @@ shared.makerTxFee=Creador: {0}
|
||||
shared.takerTxFee=Tomador: {0}
|
||||
shared.securityDepositBox.description=Depósito de seguridad para BTC {0}
|
||||
shared.iConfirm=Confirmo
|
||||
shared.tradingFeeInBsqInfo=equivalent to {0} used as trading fee
|
||||
shared.tradingFeeInBsqInfo=equivalente a {0} usado como tasa de intercambio
|
||||
shared.openURL=Abrir {0}
|
||||
shared.fiat=Fiat
|
||||
shared.crypto=Cripto
|
||||
@ -255,7 +255,7 @@ mainView.footer.bsqInfo.synchronizing=/ Sincronizando DAO
|
||||
mainView.footer.btcInfo.synchronizingWith=Sincronizando con
|
||||
mainView.footer.btcInfo.synchronizedWith=Sincronizado con
|
||||
mainView.footer.btcInfo.connectingTo=Conectando a
|
||||
mainView.footer.btcInfo.connectionFailed=Conexión fallida
|
||||
mainView.footer.btcInfo.connectionFailed=Conexión fallida a
|
||||
mainView.footer.p2pInfo=Pares de la red Bisq: {0}
|
||||
mainView.footer.daoFullNode=Nodo completo DAO
|
||||
|
||||
@ -341,10 +341,10 @@ offerbook.timeSinceSigning.info.arbitrator=firmada por un árbitro y puede firma
|
||||
offerbook.timeSinceSigning.info.peer=firmado por un par, esperando a que se eleven los límites
|
||||
offerbook.timeSinceSigning.info.peerLimitLifted=firmador por un par y los límites se elevaron
|
||||
offerbook.timeSinceSigning.info.signer=firmado por un par y puede firmar cuentas de pares (límites elevados)
|
||||
offerbook.timeSinceSigning.daysSinceSigning=días {0}
|
||||
offerbook.timeSinceSigning.daysSinceSigning={0} días
|
||||
offerbook.timeSinceSigning.daysSinceSigning.long={0} desde el firmado
|
||||
|
||||
offerbook.timeSinceSigning.help=Cuando complete con éxito un intercambio con un par que tenga una cuenta de pago firmada, su cuenta de pago es firmada.\n][{0} días después, el límite inicial de {1} se eleva y su cuenta puede firmar las cuentas de pago de otros pares.
|
||||
offerbook.timeSinceSigning.help=Cuando complete con éxito un intercambio con un par que tenga una cuenta de pago firmada, su cuenta de pago es firmada.\n{0} días después, el límite inicial de {1} se eleva y su cuenta puede firmar tras cuentas de pago.
|
||||
offerbook.timeSinceSigning.notSigned=No firmada aún
|
||||
offerbook.timeSinceSigning.notSigned.noNeed=No disponible
|
||||
shared.notSigned=Esta cuenta aún no se ha firmado
|
||||
@ -461,7 +461,7 @@ createOffer.setDeposit=Establecer depósito de seguridad para el comprador (%)
|
||||
createOffer.setDepositAsBuyer=Establecer mi depósito de seguridad como comprador (%)
|
||||
createOffer.securityDepositInfo=Su depósito de seguridad como comprador será {0}
|
||||
createOffer.securityDepositInfoAsBuyer=Su depósito de seguridad como comprador será {0}
|
||||
createOffer.minSecurityDepositUsed=Min. buyer security deposit is used
|
||||
createOffer.minSecurityDepositUsed=En uso el depósito de seguridad mínimo
|
||||
|
||||
|
||||
####################################################################
|
||||
@ -601,7 +601,8 @@ portfolio.pending.step2_seller.f2fInfo.headline=Información de contacto del com
|
||||
portfolio.pending.step2_seller.waitPayment.msg=La transacción del depósito tiene al menos una confirmación en la cadena de bloques.\nTiene que esperar hasta que el comprador de BTC comience el pago de {0}.
|
||||
portfolio.pending.step2_seller.warn=El comprador de BTC aún no ha realizado el pago de {0}.\nNecesita esperar hasta que el pago comience.\nSi el intercambio aún no se ha completado el {1} el árbitro procederá a investigar.
|
||||
portfolio.pending.step2_seller.openForDispute=El comprador de BTC no ha comenzado su pago!\nEl periodo máximo permitido ha finalizado.\nPuede esperar más y dar más tiempo a la otra parte o contactar con el mediador para abrir una disputa.
|
||||
|
||||
portfolio.pending.step2_seller.refresh=Refrescar Estado de Intercambio
|
||||
portfolio.pending.step2_seller.refreshInfo=A veces los mensajes de la red P2P que confirman el pago no son entregados, causando que los intercambios queden bloqueados. Pulse el botón inferior para hacer que su par de intercambio reenvíe el último mensaje.
|
||||
tradeChat.chatWindowTitle=Ventana de chat para transacción con ID "{0}"
|
||||
tradeChat.openChat=Abrir ventana de chat
|
||||
tradeChat.rules=Puede comunicarse con su par de intercambio para resolver posibles problemas con este intercambio.\nNo es obligatorio responder en el chat.\nSi un comerciante viola alguna de las reglas de abajo, abra una disputa y repórtelo al mediador o árbitro.\n\nReglas del chat:\n\t● No enviar ningún enlace (riesgo de malware). Puedes enviar el ID de la transacción y el nombre de un explorador de bloques.\n\t● ¡No enviar las palabras semilla, llaves privadas, contraseñas u otra información sensible!\n\t● No alentar a intercambiar fuera de Bisq (sin seguridad).\n\t● No se enfrente a ningún intento de estafa de ingeniería social.\n\t● Si un par no responde y prefiere no comunicarse, respete su decisión.\n\t● Limite el tema de conversación al intercambio. Este chat no es un sustituto del messenger o troll-box.\n\t● Mantenga la conversación amigable y respetuosa.
|
||||
@ -952,6 +953,7 @@ settings.net.warn.usePublicNodes=Si usa la red pública de Bitcoin está expuest
|
||||
settings.net.warn.usePublicNodes.useProvided=No, utilizar nodos proporcionados
|
||||
settings.net.warn.usePublicNodes.usePublic=Sí, utilizar la red pública
|
||||
settings.net.warn.useCustomNodes.B2XWarning=¡Por favor, asegúrese de que su nodo Bitcoin es un nodo de confianza Bitcoin Core!\n\nConectar a nodos que no siguen las reglas de consenso puede causar perjuicios a su cartera y causar problemas en el proceso de intercambio.\n\nLos usuarios que se conecten a los nodos que violan las reglas de consenso son responsables de cualquier daño que estos creen. Las disputas causadas por ello se decidirán en favor del otro participante. No se dará soporte técnico a usuarios que ignoren esta advertencia y los mecanismos de protección!
|
||||
settings.net.warn.invalidBtcConfig=La conexión a la red Bitcoin falló debido a que su configuración es inválida.\n\nSu configuración se ha reestablecido para usar los nodos Bitcoin proporcionados. Necesitará reiniciar la aplicación.
|
||||
settings.net.localhostBtcNodeInfo=(Información complementaria: Si está ejecutando un nodo Bitcoin local (localhost) puede conectarse exclusivamente a él)
|
||||
settings.net.p2PPeersLabel=Pares conectados
|
||||
settings.net.onionAddressColumn=Dirección onion
|
||||
@ -1110,6 +1112,8 @@ account.altcoin.popup.pars.msg=Intercambiar ParsiCoin en Bisq requiere que usted
|
||||
|
||||
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.altcoin.popup.liquidbitcoin.msg=Comerciar L-BTC en Bisq requiere que entienda lo siguiente:\n\nAl recibir L-BTC de un intercambio en Bisq, no puede usar la app de monedero móvil Blockstream Green Wallet o un exchange/monedero que custodie sus fondos. Solo debe recibir L-BTC en el monedero Liquid Elements Core, u otro monedero L-BTC que le permita obtener la clave cegadora para su dirección L-BTC cegada.\n\nEn caso de ser necesaria mediación, o si se lleva a cabo una disputa, debe entregar la clave cegadora para su dirección receptora de L-BTC al mediador o agente de devolución de fondos Bisq para que verifique los detalles de su Transacción Confidencial en su nodo completo Elements Core.\n\nSi no entrega la información requerida al mediador o al agente de devolución de fondos se resolverá en una pérdida del caso en disputa. En todos los casos de disputa, el receptor de L-BTC es responsable del 100% de la carga de aportar la prueba criptográfica al mediador o agente de devolución de fondos.\n\nSi no entiende estos requerimientos, no intercambio L-BTC en Bisq.
|
||||
|
||||
account.fiat.yourFiatAccounts=Sus cuentas de moneda nacional:
|
||||
|
||||
account.backup.title=Copia de seguridad del monedero
|
||||
@ -1256,11 +1260,11 @@ dao.results.cycles.table.header.issuance=Emisión
|
||||
dao.results.results.table.item.cycle=Ciclo {0} comenzó: {1}
|
||||
|
||||
dao.results.proposals.header=Propuestas del ciclo seleccionado
|
||||
dao.results.proposals.table.header.nameLink=Name/link
|
||||
dao.results.proposals.table.header.nameLink=Nombre/enlace
|
||||
dao.results.proposals.table.header.details=Detalles
|
||||
dao.results.proposals.table.header.myVote=Mi voto
|
||||
dao.results.proposals.table.header.result=Resultado de la votación
|
||||
dao.results.proposals.table.header.threshold=Threshold
|
||||
dao.results.proposals.table.header.threshold=Umbral
|
||||
dao.results.proposals.table.header.quorum=Quorum
|
||||
|
||||
dao.results.proposals.voting.detail.header=Resultados de votación para la propuesta seleccionada
|
||||
@ -1427,7 +1431,7 @@ dao.bond.table.column.bondType=Tipo de garantía
|
||||
dao.bond.table.column.details=Detalles
|
||||
dao.bond.table.column.lockupTxId=Tx ID de bloqueo
|
||||
dao.bond.table.column.bondState=Estado de garantía
|
||||
dao.bond.table.column.lockTime=Tiempo de bloqueo
|
||||
dao.bond.table.column.lockTime=Tiempo de desbloqueo
|
||||
dao.bond.table.column.lockupDate=Fecha de bloqueo
|
||||
|
||||
dao.bond.table.button.lockup=Bloquear
|
||||
@ -1520,7 +1524,7 @@ dao.burnBsq.assets.tradeVolume=Volumen de intercambio
|
||||
dao.burnBsq.assets.lookBackPeriod=Periodo de verificación
|
||||
dao.burnBsq.assets.trialFee=Tasa de periodo de prueba
|
||||
dao.burnBsq.assets.totalFee=Comisiones totales pagadas
|
||||
dao.burnBsq.assets.days=días {0}
|
||||
dao.burnBsq.assets.days={0} días
|
||||
dao.burnBsq.assets.toFewDays=La comisión de activo es demasiado baja. La cantidad mínima de días para el periodo de prueba es {0}.
|
||||
|
||||
# suppress inspection "UnusedProperty"
|
||||
@ -1623,7 +1627,7 @@ dao.proposal.active.remove.doRemove=Sí, eliminar mi propuesta
|
||||
dao.proposal.active.remove.failed=No se pudo eliminar la propuesta
|
||||
dao.proposal.myVote.title=Votando
|
||||
dao.proposal.myVote.accept=Aceptar propuesta
|
||||
dao.proposal.myVote.reject=Eliminar propuesta
|
||||
dao.proposal.myVote.reject=Rechazar propuesta
|
||||
dao.proposal.myVote.removeMyVote=Ignorar propuesta
|
||||
dao.proposal.myVote.merit=Peso de voto por BSQ ganados
|
||||
dao.proposal.myVote.stake=Peso de voto desde stake
|
||||
@ -1850,12 +1854,16 @@ dao.factsAndFigures.dashboard.avgPrice30=Medía de 30 días del precio de interc
|
||||
dao.factsAndFigures.dashboard.marketCap=Capitalización de mercado (basado en el precio de intercambio)
|
||||
dao.factsAndFigures.dashboard.availableAmount=BSQ totales disponibles
|
||||
|
||||
dao.factsAndFigures.supply.issuedVsBurnt=BSQ emitidos v. BSQ quemados
|
||||
|
||||
dao.factsAndFigures.supply.issued=BSQ emitidos
|
||||
dao.factsAndFigures.supply.genesisIssueAmount=BSQ emitidos en la transacción génesis
|
||||
dao.factsAndFigures.supply.compRequestIssueAmount=BSQ emitidos para solicitudes de compensación
|
||||
dao.factsAndFigures.supply.reimbursementAmount=BSQ emitidos para solicitudes de reembolso
|
||||
|
||||
dao.factsAndFigures.supply.burnt=BSQ quemados
|
||||
dao.factsAndFigures.supply.burntMovingAverage=media móvil de 15 días
|
||||
dao.factsAndFigures.supply.burntZoomToInliers=Zoom a inliers
|
||||
|
||||
dao.factsAndFigures.supply.locked=Estado global de BSQ bloqueados
|
||||
dao.factsAndFigures.supply.totalLockedUpAmount=Bloqueados en garantías
|
||||
@ -2131,10 +2139,10 @@ popup.warning.trade.txRejected=La transacción {0} para el intercambio con ID {1
|
||||
|
||||
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.\n\nPlease restart the application to see if the problem still exists.\n\nIf it does, please open the trade details popup by clicking on the trade ID. Then click on the transaction IDs for the maker fee transaction and the taker fee transaction to view them on a block explorer. A transaction that cannot be found in a block explorer is probably an invalid transaction.\n\nIf this happens, please report it in the #support channel on the Bisq Keybase (https://keybase.io/team/bisq). If your trade fee transaction is invalid, no funds have left your wallet, you can move the trade to failed trades,and do an SPV resync for your funds to reappear (see how below).\n\nIf your trade fee transaction is valid, the fee amount is lost, and you can make a request for reimbursement on the support repository on GitHub (https://github.com/bisq-network/support/issues).\n\nIn both cases, please do an SPV resync from the ''Settings/Network'' screen to clean your wallet of any lingering issues!
|
||||
popup.warning.trade.depositTxNull=El intercambio con ID "{0}" no tiene transacción de depósito establecida.\n\nPor favor reinicie la aplicación para ver si el problema persiste.\n\nSi fuera así, por favor abra la ventana emergente de detalles de intercambio haciendo click en la ID de intercambio. Luego, haga click en las ID para la transacción de la tasa de tomador y la tasa de creador para verlas en un explorador de bloques. Una transacción que no pueda encontrarse en un explorador de bloques probablemente sea una transacción inválida.\n\nSi eso ocurriera, por favor reportelo en el canal #soporte de Bisq en Keybase (https://keybase.io/team/bisq). Si su tasa de intercambio es inválida, los fondos no han salido de su monedero, con lo que puede mover el intercambio a intercambios fallidos, y hacer una resincronización SPV para que los fondos vuelvan a aparecer (ver cómo abajo).\n\nSi su transacción es válida, la cantidad se ha perdido, y puede hacer una solicitud de reembolso en el repositorio de soporte de Github (https://github.com/bisq-network/support/issues).\n\nEn ambos casos, ¡por favor haga una resincronización SPV desde la pantalla "Configuración/Red" para limpiar su monedero de problemas recurrentes!
|
||||
|
||||
popup.warning.trade.depositTxNull.moveToFailedTrades=Mover a intercambios fallidos
|
||||
popup.warning.trade.depositTxNull.shutDown=Shut down Bisq
|
||||
popup.warning.trade.depositTxNull.shutDown=Cerrar Bisq
|
||||
|
||||
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!)
|
||||
|
||||
@ -2148,6 +2156,7 @@ popup.securityRecommendation.headline=Recomendación de seguridad importante
|
||||
popup.securityRecommendation.msg=Nos gustaría recordarle que considere usar protección por contraseña para su cartera, si no la ha activado ya.\n\nTambién es muy recomendable que escriba en un papel las palabras semilla del monedero. Esas palabras semilla son como una contraseña maestra para recuperar su cartera Bitcoin.\nEn la sección \"Semilla de cartera\" encontrará más información.\n\nAdicionalmente, debería hacer una copia de seguridad completa del directorio de aplicación en la sección \"Copia de seguridad\"
|
||||
|
||||
popup.bitcoinLocalhostNode.msg=Bisq detectó un nodo Bitcoin Core operando localmente (en localhost).\nPor favor asegúrese de que este nodo esté completamente sincronizado antes de iniciar Bisq y el que no esté operando en modo de registro reducido (pruned mode).
|
||||
popup.bitcoinLocalhostNode.additionalRequirements=\n\nDesde la versión de Bitcoin Core 0.19 tiene que habilitar manualmente los filtros bloom configurando peerbloomfilters=1 en su archivo de configuración bitcoin.conf
|
||||
|
||||
popup.shutDownInProgress.headline=Cerrando aplicación...
|
||||
popup.shutDownInProgress.msg=Cerrar la aplicación puede llevar unos segundos.\nPor favor no interrumpa el proceso.
|
||||
@ -2237,7 +2246,7 @@ guiUtil.openWebBrowser.warning=Va a abrir una página web en el navegador de su
|
||||
guiUtil.openWebBrowser.doOpen=Abrir la página web y no preguntar de nuevo
|
||||
guiUtil.openWebBrowser.copyUrl=Copiar URL y cancelar
|
||||
guiUtil.ofTradeAmount=de cantidad de intercambio
|
||||
guiUtil.requiredMinimum=(required minimum)
|
||||
guiUtil.requiredMinimum=(mínimo requerido)
|
||||
|
||||
####################################################################
|
||||
# Component specific
|
||||
@ -2293,7 +2302,7 @@ txIdTextField.blockExplorerIcon.tooltip=Abrir un explorador de bloques con esta
|
||||
|
||||
navigation.account=\"Cuenta\"
|
||||
navigation.account.walletSeed=\"Cuenta/Semilla de cartera\"
|
||||
navigation.funds.availableForWithdrawal=\"Fondear/Enviar fondos\"
|
||||
navigation.funds.availableForWithdrawal=\"Fondos/Enviar fondos\"
|
||||
navigation.portfolio.myOpenOffers=\"Portafolio/Mis ofertas abiertas\"
|
||||
navigation.portfolio.pending=\"Portafolio/Intercambios abiertos\"
|
||||
navigation.portfolio.closedTrades=\"Portafolio/Historial\"
|
||||
@ -2693,3 +2702,4 @@ validation.phone.invalidCharacters=Número de teléfono {0} tiene caracteres inv
|
||||
validation.phone.insufficientDigits=No hay suficientes dígitos en {0} para un número de teléfono válido
|
||||
validation.phone.tooManyDigits=Demasiados dígitos en {0} para ser un número de teléfono válido
|
||||
validation.phone.invalidDialingCode=Código de país en número {0} es inválido para el país {1}. El código correcto es {2}.
|
||||
validation.invalidAddressList=La lista de direcciones válidas debe ser separada por coma
|
||||
|
||||
@ -255,7 +255,7 @@ mainView.footer.bsqInfo.synchronizing=/ همگامسازی DAO
|
||||
mainView.footer.btcInfo.synchronizingWith=در حال همگام شدن با
|
||||
mainView.footer.btcInfo.synchronizedWith=همگام شده با
|
||||
mainView.footer.btcInfo.connectingTo=در حال ایجاد ارتباط با
|
||||
mainView.footer.btcInfo.connectionFailed=ارتباط ناموفق بود
|
||||
mainView.footer.btcInfo.connectionFailed=Connection failed to
|
||||
mainView.footer.p2pInfo=Bisq network peers: {0}
|
||||
mainView.footer.daoFullNode=گره کامل DAO
|
||||
|
||||
@ -601,7 +601,8 @@ portfolio.pending.step2_seller.f2fInfo.headline=اطلاعات تماس خرید
|
||||
portfolio.pending.step2_seller.waitPayment.msg=تراکنش سپرده، حداقل یک تأییدیه بلاکچین دارد.شما\nباید تا آغاز پرداخت {0} از جانب خریدار بیتکوین، صبر نمایید.
|
||||
portfolio.pending.step2_seller.warn=خریدار بیتکوین هنوز پرداخت {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.refresh=Refresh Trade State
|
||||
portfolio.pending.step2_seller.refreshInfo=Sometimes P2P network messages acknowledging payment are not delivered, causing trades to get stuck. Hit the button below to make your peer resend the last message.
|
||||
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.
|
||||
@ -952,6 +953,7 @@ settings.net.warn.usePublicNodes=اگر از شبکه عمومی بیتکوین
|
||||
settings.net.warn.usePublicNodes.useProvided=خیر، از نودهای فراهم شده استفاده کنید.
|
||||
settings.net.warn.usePublicNodes.usePublic=بلی، از شبکه عمومی استفاده کنید.
|
||||
settings.net.warn.useCustomNodes.B2XWarning=لطفا مطمئن شوید که گره بیتکوین شما یک گره مورد اعتماد Bitcoin Core است!\n\nمتصل شدن به گرههایی که از قوانین مورد اجماع موجود در Bitcoin Core پیروی نمیکنند میتواند باعث خراب شدن کیف پول شما شود و در فرآیند معامله مشکلاتی را به وجود بیاورد.\n\nکاربرانی که از گرههای ناقض قوانین مورد اجماع استفاده میکند مسئول هر گونه آسیب ایجاد شده هستند. اگر هر گونه اختلافی به وجود بیاید به نفع دیگر گرههایی که از قوانین مورد اجماع پیروی میکنند درمورد آن تصمیم گیری خواهد شد. به کاربرانی که این هشدار و سازوکار محافظتی را نادیده میگیرند هیچگونه پشتیبانی فنی ارائه نخواهد شد!
|
||||
settings.net.warn.invalidBtcConfig=Connection to the Bitcoin network failed because your configuration is invalid.\n\nYour configuration has been reset to use the provided Bitcoin nodes instead. You will need to restart the application.
|
||||
settings.net.localhostBtcNodeInfo=(اطلاعات پیش زمینه: اگر شما یک گره محلی بیتکوین (localhost) را اجرا میکنید، میتوانید به صورت انحصاری به آن متصل شوید.)
|
||||
settings.net.p2PPeersLabel=همتایان متصل
|
||||
settings.net.onionAddressColumn=آدرس Onion
|
||||
@ -1110,6 +1112,8 @@ account.altcoin.popup.pars.msg=Trading ParsiCoin on Bisq requires that you under
|
||||
|
||||
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.liquidbitcoin.msg=Trading L-BTC on Bisq requires that you understand the following:\n\nWhen receiving L-BTC for a trade on Bisq, you cannot use the mobile Blockstream Green Wallet app or a custodial/exchange wallet. You must only receive L-BTC into the Liquid Elements Core wallet, or another L-BTC wallet which allows you to obtain the blinding key for your blinded L-BTC address.\n\nIn the event mediation is necessary, or if a trade dispute arises, you must disclose the blinding key for your receiving L-BTC address to the Bisq mediator or refund agent so they can verify the details of your Confidential Transaction on their own Elements Core full node.\n\nFailure to provide the required information to the mediator or refund agent will result in losing the dispute case. In all cases of dispute, the L-BTC receiver bears 100% of the burden of responsibility in providing cryptographic proof to the mediator or refund agent.\n\nIf you do not understand these requirements, do not trade L-BTC on Bisq.
|
||||
|
||||
account.fiat.yourFiatAccounts=حسابهای ارزهای ملی شما
|
||||
|
||||
account.backup.title=کیف پول پشتیبان
|
||||
@ -1427,7 +1431,7 @@ dao.bond.table.column.bondType=نوع ضمانت
|
||||
dao.bond.table.column.details=جزئیات
|
||||
dao.bond.table.column.lockupTxId=شناسه تراکنش قفل وجوه
|
||||
dao.bond.table.column.bondState=وضعیت ضمانت
|
||||
dao.bond.table.column.lockTime=زمان قفل شدن
|
||||
dao.bond.table.column.lockTime=Unlock time
|
||||
dao.bond.table.column.lockupDate=تاریخ قفل کردن وجه
|
||||
|
||||
dao.bond.table.button.lockup=قفل کردن
|
||||
@ -1850,12 +1854,16 @@ dao.factsAndFigures.dashboard.avgPrice30=30 days average BSQ/BTC trade price
|
||||
dao.factsAndFigures.dashboard.marketCap=ارزش بازار (بر مبنای قیمت معاملاتی)
|
||||
dao.factsAndFigures.dashboard.availableAmount=مجموع BSQ در دسترس
|
||||
|
||||
dao.factsAndFigures.supply.issuedVsBurnt=BSQ issued v. BSQ burnt
|
||||
|
||||
dao.factsAndFigures.supply.issued=BSQ issued
|
||||
dao.factsAndFigures.supply.genesisIssueAmount=BSQ صادر شده در تراکنش پیدایش
|
||||
dao.factsAndFigures.supply.compRequestIssueAmount=BSQ صادر شده برای درخواستهای مصادره
|
||||
dao.factsAndFigures.supply.reimbursementAmount=BSQ صادر شده برای درخواستهای بازپرداخت
|
||||
|
||||
dao.factsAndFigures.supply.burnt=BSQ burnt
|
||||
dao.factsAndFigures.supply.burntMovingAverage=15-day moving average
|
||||
dao.factsAndFigures.supply.burntZoomToInliers=Zoom to inliers
|
||||
|
||||
dao.factsAndFigures.supply.locked=وضعیت جهانی BSQ های قفل شده
|
||||
dao.factsAndFigures.supply.totalLockedUpAmount=قفل شده در ضمانتها
|
||||
@ -2148,6 +2156,7 @@ popup.securityRecommendation.headline=توصیه امنیتی مهم
|
||||
popup.securityRecommendation.msg=ما می خواهیم به شما یادآوری کنیم که استفاده از رمز محافظت برای کیف پول خود را در نظر بگیرید اگر از قبل آن را فعال نکرده اید.\n\nهمچنین شدیداً توصیه می شود که کلمات رمز خصوصی کیف پول را بنویسید. این کلمات رمز خصوصی مانند یک رمزعبور اصلی برای بازیابی کیف پول بیتکوین شما هستند. \nدر قسمت \"کلمات رمز خصوصی کیف پول\" اطلاعات بیشتری کسب می کنید.\n\n علاوه بر این شما باید از پوشه داده های کامل نرم افزار در بخش \"پشتیبان گیری\" پشتیبان تهیه کنید.
|
||||
|
||||
popup.bitcoinLocalhostNode.msg=Bisq یک گره بیتکوین هسته محلی در حال اجرا را (در لوکا هاست) شناسایی کرد.\n لطفا اطمینان حاصل کنید که این گره قبل از شروع Bisq به طور کامل همگام سازی شده و در حالت هرس شده اجرا نمی شود.
|
||||
popup.bitcoinLocalhostNode.additionalRequirements=\n\nStarting with Bitcoin Core v0.19 you have to manually enable bloom filters by setting peerbloomfilters=1 in your bitcoin.conf configuration file.
|
||||
|
||||
popup.shutDownInProgress.headline=خاموش شدن در حال انجام است
|
||||
popup.shutDownInProgress.msg=خاتمه دادن به برنامه می تواند چند ثانیه طول بکشد.\n لطفا این روند را قطع نکنید.
|
||||
@ -2693,3 +2702,4 @@ 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.invalidAddressList=Must be comma separated list of valid addresses
|
||||
|
||||
@ -189,7 +189,7 @@ shared.makerTxFee=Maker: {0}
|
||||
shared.takerTxFee=Taker: {0}
|
||||
shared.securityDepositBox.description=Dépôt de garantie pour BTC {0}
|
||||
shared.iConfirm=Je confirme
|
||||
shared.tradingFeeInBsqInfo=equivalent to {0} used as trading fee
|
||||
shared.tradingFeeInBsqInfo=Équivalent à {0} utilisé en frais de transaction
|
||||
shared.openURL=Ouvert {0}
|
||||
shared.fiat=Fiat
|
||||
shared.crypto=Crypto
|
||||
@ -255,7 +255,7 @@ mainView.footer.bsqInfo.synchronizing=/ Synchronisation DAO en cours
|
||||
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.btcInfo.connectionFailed=Connection failed to
|
||||
mainView.footer.p2pInfo=Pairs du réseau Bisq: {0}
|
||||
mainView.footer.daoFullNode=DAO full node
|
||||
|
||||
@ -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} . Votre limite de trading est basée sur l'âge du compte et n'est pas suffisante pour cette offre.\n\nVotre limite de trading est : {1}\nLe montant minimum de l'offre est de : {2}.\n\nVous ne pouvez pas accepter cette offre pour le moment. Une fois que votre compte aura plus de 2 mois, cette restriction sera levée.
|
||||
offerbook.warning.tradeLimitNotMatching=Votre compte de paiement a été créé il y a {0} . Votre limite de trading est basée sur l''âge du compte et n'est pas suffisante pour cette offre.\n\nVotre limite de trading est: {1}\nLe montant minimum de l'offre est de: {2}.\n\nVous ne pouvez pas accepter cette offre pour le moment. Une fois que votre compte aura plus de 2 mois, cette restriction sera levée.
|
||||
|
||||
|
||||
offerbook.info.sellAtMarketPrice=Vous vendrez au prix du marché (mis à jour chaque minute).
|
||||
@ -461,7 +461,7 @@ createOffer.setDeposit=Etablir le dépôt de garantie de l'acheteur (%)
|
||||
createOffer.setDepositAsBuyer=Définir mon dépôt de garantie en tant qu'acheteur (%)
|
||||
createOffer.securityDepositInfo=Le dépôt de garantie de votre acheteur sera de {0}
|
||||
createOffer.securityDepositInfoAsBuyer=Votre dépôt de garantie en tant qu''acheteur sera de {0}
|
||||
createOffer.minSecurityDepositUsed=Min. buyer security deposit is used
|
||||
createOffer.minSecurityDepositUsed=Le minimum de dépôt de garantie de l'acheteur est utilisé
|
||||
|
||||
|
||||
####################################################################
|
||||
@ -601,7 +601,8 @@ 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=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.
|
||||
|
||||
portfolio.pending.step2_seller.refresh=Refresh Trade State
|
||||
portfolio.pending.step2_seller.refreshInfo=Sometimes P2P network messages acknowledging payment are not delivered, causing trades to get stuck. Hit the button below to make your peer resend the last message.
|
||||
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 à cet échange.\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 autre information sensible !\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 à l'échange en cours. Ce chat n'est pas une alternative à messenger ou une troll-box.\n\t● Entretenez une conversation amicale et respectueuse.
|
||||
@ -706,14 +707,14 @@ portfolio.pending.openSupportTicket.headline=Ouvrir un ticket d'assistance
|
||||
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, l'échange sera interrompu et pris en charge par le médiateur ou par l'arbitre.
|
||||
|
||||
portfolio.pending.timeLockNotOver=Vous devez patienter jusqu''au ≈{0} ({1} blocs de plus) avant de pouvoir ouvrir ouvrir un arbitrage pour le litige.
|
||||
portfolio.pending.error.depositTxNull=La transaction de dépôt est nulle. Vous ne pouvez pas ouvrir un litige sans une transaction de dépôt valide. Allez dans \"Paramètres/Info sur le réseau\" et faites une resynchronisation SPV.\n\nPour obtenir de l'aide, le canal support de l'équipe Bisq est à disposition sur Keybase.
|
||||
portfolio.pending.error.depositTxNull=La transaction de dépôt est nulle. Vous ne pouvez pas ouvrir un litige sans une transaction de dépôt valide. Allez dans \"Paramètres/Info sur le réseau\" et faites une resynchronisation SPV.\n\nPour obtenir de l'aide, le canal support de l'équipe Bisq est disponible sur Keybase.
|
||||
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=La transaction de dépôt n'est pas confirmée. Vous ne pouvez pas ouvrir un arbitrage pour le litige avec une transaction de dépôt non confirmée. Veuillez patienter jusqu'à ce qu'elle soit confirmée ou allez à \"Paramètres/Info sur le réseau réseau\" et faites une resynchronisation SPV.\n\nPour obtenir de l'aide, le canal support de l'équipe Bisq est à disposition sur Keybase.
|
||||
portfolio.pending.error.depositTxNotConfirmed=La transaction de dépôt n'est pas confirmée. Vous ne pouvez pas ouvrir un arbitrage pour le litige avec une transaction de dépôt non confirmée. Veuillez patienter jusqu'à ce qu'elle soit confirmée ou allez à \"Paramètres/Info sur le réseau réseau\" et faites une resynchronisation SPV.\n\nPour obtenir de l'aide, le canal support de l'équipe Bisq est disponible sur Keybase.
|
||||
|
||||
portfolio.pending.notification=Notification
|
||||
|
||||
portfolio.pending.support.headline.getHelp=Besoin d'aide ?
|
||||
portfolio.pending.support.text.getHelp=Si vous rencontrez des problèmes, vous pouvez essayer de contacter votre pair de trading dans le chat de l'échange ou demander à la communauté Bisq sur https://bisq.community Si votre problème n'est toujours pas résolu, vous pouvez demander l'aide d'un médiateur.
|
||||
portfolio.pending.support.text.getHelp=Si vous rencontrez des problèmes, vous pouvez essayer de contacter votre pair de trading dans le chat de l'échange ou demander à la communauté Bisq sur https://bisq.community. Si votre problème n'est toujours pas résolu, vous pouvez demander l'aide d'un médiateur.
|
||||
portfolio.pending.support.text.getHelp.arbitrator=Si vous rencontrez des problèmes, vous pouvez essayer de contacter votre pair de trading dans le chat de l'échange ou demander à la communauté Bisq sur https://bisq.community Si votre problème n'est toujours pas résolu, vous pouvez demander l'aide d'un arbitre.
|
||||
portfolio.pending.support.button.getHelp=Obtenir de l'aide
|
||||
portfolio.pending.support.popup.info=Si votre problème avec l'échange n'est toujours pas résolu, vous pouvez ouvrir un ticket de support pour demander l'aide d'un médiateur. Si vous n'avez pas reçu le paiement, veuillez attendre la fin de la période d'échange.\n\nÊtes-vous sûr de vouloir ouvrir un ticket support ?
|
||||
@ -813,7 +814,7 @@ funds.tx.multiSigPayout=Versement Multisig: {0}
|
||||
funds.tx.disputePayout=Versement du litige: {0}
|
||||
funds.tx.disputeLost=Cas de litige perdu: {0}
|
||||
funds.tx.collateralForRefund=Remboursement du dépôt de garantie: {0}
|
||||
funds.tx.timeLockedPayoutTx=Tx de paiement verrouillée dans le temps : {0}
|
||||
funds.tx.timeLockedPayoutTx=Tx de paiement verrouillée dans le temps: {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
|
||||
@ -882,7 +883,7 @@ support.youOpenedDisputeForMediation=Vous avez demandé une médiation.\n\n{0}\n
|
||||
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 pair 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 par le médiateur:\n{0}
|
||||
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}
|
||||
|
||||
|
||||
@ -952,6 +953,7 @@ settings.net.warn.usePublicNodes=Si vous utilisez le réseau public Bitcoin, vou
|
||||
settings.net.warn.usePublicNodes.useProvided=Non, utiliser les nœuds fournis.
|
||||
settings.net.warn.usePublicNodes.usePublic=Oui, utiliser un réseau public
|
||||
settings.net.warn.useCustomNodes.B2XWarning=Veuillez vous assurer que votre nœud Bitcoin est un nœud Bitcoin Core de confiance !\n\nLa connexion à des nœuds qui ne respectent pas les règles du consensus de Bitcoin Core peut corrompre votre portefeuille et causer des problèmes dans le processus de trading.\n\nLes utilisateurs qui se connectent à des nœuds qui ne respectent pas les règles du consensus sont responsables des dommages qui en résultent. Tout litige qui en résulte sera tranché en faveur de l'autre pair. Aucune assistance technique ne sera apportée aux utilisateurs qui ignorent ces mécanismes d'alertes et de protections !
|
||||
settings.net.warn.invalidBtcConfig=Connection to the Bitcoin network failed because your configuration is invalid.\n\nYour configuration has been reset to use the provided Bitcoin nodes instead. You will need to restart the application.
|
||||
settings.net.localhostBtcNodeInfo=( Informations générales : Si vous utilisez un noeud Bitcoin en local (localhost), vous pouvez uniquement vous y connecter.)
|
||||
settings.net.p2PPeersLabel=Pairs connectés
|
||||
settings.net.onionAddressColumn=Adresse onion
|
||||
@ -1006,7 +1008,7 @@ setting.about.shortcuts=Raccourcis
|
||||
setting.about.shortcuts.ctrlOrAltOrCmd=''Ctrl + {0}'' ou ''alt + {0}'' ou ''cmd + {0}''
|
||||
|
||||
setting.about.shortcuts.menuNav=Naviguer dans le menu principal
|
||||
setting.about.shortcuts.menuNav.value=Pour naviguer dans le menu principal, appuyez sur : 'Ctrl' ou 'alt' ou 'cmd' avec une touche numérique entre '1-9'.
|
||||
setting.about.shortcuts.menuNav.value=Pour naviguer dans le menu principal, appuyez sur: 'Ctrl' ou 'alt' ou 'cmd' avec une touche numérique entre '1-9'.
|
||||
|
||||
setting.about.shortcuts.close=Fermer Bisq
|
||||
setting.about.shortcuts.close.value=''Ctrl + {0}'' ou ''cmd + {0}'' ou ''Ctrl + {1}'' ou ''cmd + {1}''
|
||||
@ -1015,12 +1017,12 @@ setting.about.shortcuts.closePopup=Fermer le popup ou la fenêtre de dialogue
|
||||
setting.about.shortcuts.closePopup.value=Touche 'ECHAP'
|
||||
|
||||
setting.about.shortcuts.chatSendMsg=Envoyer un message chat au trader
|
||||
setting.about.shortcuts.chatSendMsg.value=''Ctrl + ENTREE'' ou ''alt + ENTREE'' ou ''cmd + ENTREE''
|
||||
setting.about.shortcuts.chatSendMsg.value=''Ctrl + ENTRÉE'' ou ''alt + ENTREE'' ou ''cmd + ENTRÉE''
|
||||
|
||||
setting.about.shortcuts.openDispute=Litige ouvert
|
||||
setting.about.shortcuts.openDispute.value=Sélectionnez l''échange en cours et cliquez sur : {0}
|
||||
setting.about.shortcuts.openDispute=Ouvrir un litige
|
||||
setting.about.shortcuts.openDispute.value=Sélectionnez l''échange en cours et cliquez sur: {0}
|
||||
|
||||
setting.about.shortcuts.walletDetails=Ouvrir la fenêtre de détails du portefeuille
|
||||
setting.about.shortcuts.walletDetails=Ouvrir la fenêtre avec les détails sur le portefeuille
|
||||
|
||||
setting.about.shortcuts.openEmergencyBtcWalletTool=Ouvrir l'outil de portefeuille d'urgence pour BTC
|
||||
|
||||
@ -1029,33 +1031,33 @@ setting.about.shortcuts.openEmergencyBsqWalletTool=Ouvrir l'outil de portefeuill
|
||||
setting.about.shortcuts.showTorLogs=Basculer le niveau de log pour les messages Tor entre DEBUG et WARN
|
||||
|
||||
setting.about.shortcuts.showDisputeStatistics=Afficher le résumé de tous les litiges
|
||||
setting.about.shortcuts.showDisputeStatistics.value=Naviguez vers la vue des litiges et appuyez sur : {0}
|
||||
setting.about.shortcuts.showDisputeStatistics.value=Naviguez vers la vue des litiges et appuyez sur: {0}
|
||||
|
||||
setting.about.shortcuts.manualPayoutTxWindow=Ouvrir la fenêtre pour le paiement manuel à partir de la tx de dépôt Multisig 2of2
|
||||
setting.about.shortcuts.manualPayoutTxWindow=Ouvrir la fenêtre pour le paiement manuel à partir du tx de dépôt Multisig 2of2
|
||||
|
||||
setting.about.shortcuts.reRepublishAllGovernanceData=Publier à nouveau les données sur la gouvernance de la DAO (propositions, votes)
|
||||
|
||||
setting.about.shortcuts.removeStuckTrade=Ouvrez le popup pour déplacer l'échange bloqué vers l'onglet des échanges en echec (à utiliser uniquement si vous êtes sûr)
|
||||
setting.about.shortcuts.removeStuckTrade.value=Sélectionnez l'échange en cours et appuyez sur : {0}
|
||||
setting.about.shortcuts.removeStuckTrade=Ouvrez le popup pour déplacer l'échange bloqué vers l'onglet des échanges en échec (à utiliser uniquement si vous êtes sûr)
|
||||
setting.about.shortcuts.removeStuckTrade.value=Sélectionnez l'échange en cours et appuyez sur: {0}
|
||||
|
||||
setting.about.shortcuts.registerArbitrator=Inscrire l'arbitre (médiateur/arbitre seulement)
|
||||
setting.about.shortcuts.registerArbitrator.value=Naviguez jusqu'au compte et appuyez sur : {0}
|
||||
setting.about.shortcuts.registerArbitrator.value=Naviguez jusqu'au compte et appuyez sur: {0}
|
||||
|
||||
setting.about.shortcuts.registerMediator=Inscrire le médiateur (médiateur/arbitre seulement)
|
||||
setting.about.shortcuts.registerMediator.value=Naviguez jusqu'au compte et appuyez sur : {0}
|
||||
setting.about.shortcuts.registerMediator.value=Naviguez jusqu'au compte et appuyez sur: {0}
|
||||
|
||||
setting.about.shortcuts.reOpenDispute=Réouverture d'un litige déjà clos (médiateur/arbitre seulement)
|
||||
setting.about.shortcuts.reOpenDispute.value=Sélectionnez le litige fermé et appuyez sur : {0}
|
||||
setting.about.shortcuts.reOpenDispute.value=Sélectionnez le litige fermé et appuyez sur: {0}
|
||||
|
||||
setting.about.shortcuts.openSignPaymentAccountsWindow=Ouvrir la fenêtre pour la signature de l'âge du compte (anciens arbitres seulement)
|
||||
setting.about.shortcuts.openSignPaymentAccountsWindow.value=Naviguer vers l''ancienne vue de l''arbitre et appuyer sur : {0}
|
||||
setting.about.shortcuts.openSignPaymentAccountsWindow.value=Naviguer vers l''ancienne vue de l''arbitre et appuyer sur: {0}
|
||||
|
||||
setting.about.shortcuts.sendAlertMsg=Envoyer un message d'alerte ou de mise à jour (activité privilégiée)
|
||||
|
||||
setting.about.shortcuts.sendFilter=Définir le filtre (activité privilégiée)
|
||||
|
||||
setting.about.shortcuts.sendPrivateNotification=Envoyer une notification privée à un pair (activité privilégiée)
|
||||
setting.about.shortcuts.sendPrivateNotification.value=Ouvrez l''information du pair via l''avatar ou le litige et pressez : {0}
|
||||
setting.about.shortcuts.sendPrivateNotification.value=Ouvrez l''information du pair via l''avatar ou le litige et pressez: {0}
|
||||
|
||||
|
||||
####################################################################
|
||||
@ -1093,8 +1095,8 @@ account.altcoin.yourAltcoinAccounts=Vos comptes altcoin
|
||||
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=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 flag 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 un l'explorateur de bloc normal, 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 perdrez 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 de ce processus, 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=Le trading de XMR sur Bisq exige que vous compreniez et remplissiez les conditions suivantes :\n\nProuver les paiements : comme Monero est une cryptomonnaie privée, certains détails de la transaction ne sont pas disponibles publiquement dans la blockchain. En cas de litige, le médiateur ou l'arbitre ont besoin de vérifier si la transaction a vraiment été effectuée. Dans le cas de Bisq, l'expéditeur de la transaction XMR est celui qui doit fournir ces renseignements au médiateur ou à l'arbitre en cas de littige. Pour ce faire, vous devez envoyer des XMR en utilisant un porte-monnaie qui fournit les renseignements nécessaires pour prouver que le paiement a été effectué, ce qui comprend :\n\n- la clé de transaction (Tx Key, Tx Secret Key ou Tx Private Key)\n- l'ID de la transaction (Tx ID ou Tx Hash)\n- l'adresse de destination (recipient's address)\n\nCes informations se trouvent dans les portefeuilles officiels de Monero GUI & CLI, MyMonero, et Exodus (bureau) ainsi que dans Cake Wallet, MyMonero, et Monerujo (mobile), dans les endroits suivants :\n\n- Monero GUI : allez à l'onglet Transactions\n- Monero CLI : utilisez la commande get_tx_key TXID. Le flag store-tx-info doit être activé (activé par défaut dans les nouvelles versions)\n- Autres portefeuilles : allez dans l'historique des transactions et recherchez la clé de transaction (Tx key ou Secret key) et l'adresse de destination dans une transaction envoyée. L'option "Enregistrer l'adresse du destinataire" doit être activée dans les paramètres de Cake Wallet.\n\nSi vous utilisez un portefeuille différent de celui mentionné ci-dessus, assurez-vous de pouvoir accéder à ces trois informations. Puisque la clé de transaction et l'adresse de destination sont stockées dans le logiciel de portefeuille Monero et qu'elles ne peuvent pas être récupérées dans la blockchain Monero, vous ne devez jamais supprimer ou restaurer votre portefeuille Monero avant qu'une transaction Bisq ne soit effectuée. Ne pas fournir les données ci-dessus entraînera la perte du litige.\n\nPaiements par chèque : avec ces trois informations, la vérification qu'une quantité de Monero a été envoyée à une adresse spécifique peut être effectuée de la manière suivante :\n\n- Monero GUI : changez le portefeuille en mode Avancé et allez à Avancé > Prouver/vérifier > Vérifier la transaction\n- Monero CLI : utiliser la commande check_tx_key TXID TXKEY ADDRESS\n- L'outil XMR checktx (https://xmr.llcoins.net/checktx.html)\n- Explorez le site web de Monero (https://www.exploremonero.com/receipt)\n\nSi vous ne comprenez toujours pas ce processus, visitez (https://www.getmonero.org/resources/user-guides/prove-payment.html) pour trouver plus d'informations ou poser une question sur le sous-reddit de support Monero (https://www.reddit.com/r/monerosupport/).
|
||||
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 flag 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 un l'explorateur de bloc normal, 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 perdrez 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 du paiement, seulement l'adresse publique normale.\nSi vous n'êtes pas sûr de ce processus, 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=Le trading de XMR sur Bisq exige que vous compreniez et remplissiez les conditions suivantes:\n\nProuver les paiements : comme Monero est une cryptomonnaie privée, certains détails de la transaction ne sont pas disponibles publiquement dans la blockchain. En cas de litige, le médiateur ou l'arbitre ont besoin de vérifier si la transaction a vraiment été effectuée. Dans le cas de Bisq, l'expéditeur de la transaction XMR est celui qui doit fournir ces renseignements au médiateur ou à l'arbitre en cas de littige. Pour ce faire, vous devez envoyer des XMR en utilisant un porte-monnaie qui fournit les renseignements nécessaires pour prouver que le paiement a été effectué, ce qui comprend:\n\n- la clé de transaction (Tx Key, Tx Secret Key ou Tx Private Key)\n- l'ID de la transaction (Tx ID ou Tx Hash)\n- l'adresse de destination (recipient's address)\n\nCes informations se trouvent dans les portefeuilles officiels de Monero GUI & CLI, MyMonero, et Exodus (bureau) ainsi que dans Cake Wallet, MyMonero, et Monerujo (mobile), dans les endroits suivants:\n\n- Monero GUI : allez à l'onglet Transactions\n- Monero CLI : utilisez la commande get_tx_key TXID. Le flag store-tx-info doit être activé (activé par défaut dans les nouvelles versions)\n- Autres portefeuilles : allez dans l'historique des transactions et recherchez la clé de transaction (Tx key ou Secret key) et l'adresse de destination dans une transaction envoyée. L'option "Enregistrer l'adresse du destinataire" doit être activée dans les paramètres de Cake Wallet.\n\nSi vous utilisez un portefeuille différent de celui mentionné ci-dessus, assurez-vous de pouvoir accéder à ces trois informations. Puisque la clé de transaction et l'adresse de destination sont stockées dans le logiciel de portefeuille Monero et qu'elles ne peuvent pas être récupérées dans la blockchain Monero, vous ne devez jamais supprimer ou restaurer votre portefeuille Monero avant qu'une transaction Bisq ne soit effectuée. Ne pas fournir les données ci-dessus entraînera la perte du litige.\n\nPaiements par chèque : avec ces trois informations, la vérification qu'une quantité de Monero a été envoyée à une adresse spécifique peut être effectuée de la manière suivante:\n\n- Monero GUI : changez le portefeuille en mode Avancé et allez à Avancé > Prouver/vérifier > Vérifier la transaction\n- Monero CLI : utiliser la commande check_tx_key TXID TXKEY ADDRESS\n- L'outil XMR checktx (https://xmr.llcoins.net/checktx.html)\n- Explorez le site web de Monero (https://www.exploremonero.com/receipt)\n\nSi vous ne comprenez toujours pas ce processus, visitez (https://www.getmonero.org/resources/user-guides/prove-payment.html) pour trouver plus d'informations ou poser une question sur le sous-reddit de support 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).
|
||||
@ -1110,6 +1112,8 @@ account.altcoin.popup.pars.msg=Trading ParsiCoin on Bisq requires that you under
|
||||
|
||||
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.liquidbitcoin.msg=Trading L-BTC on Bisq requires that you understand the following:\n\nWhen receiving L-BTC for a trade on Bisq, you cannot use the mobile Blockstream Green Wallet app or a custodial/exchange wallet. You must only receive L-BTC into the Liquid Elements Core wallet, or another L-BTC wallet which allows you to obtain the blinding key for your blinded L-BTC address.\n\nIn the event mediation is necessary, or if a trade dispute arises, you must disclose the blinding key for your receiving L-BTC address to the Bisq mediator or refund agent so they can verify the details of your Confidential Transaction on their own Elements Core full node.\n\nFailure to provide the required information to the mediator or refund agent will result in losing the dispute case. In all cases of dispute, the L-BTC receiver bears 100% of the burden of responsibility in providing cryptographic proof to the mediator or refund agent.\n\nIf you do not understand these requirements, do not trade L-BTC on Bisq.
|
||||
|
||||
account.fiat.yourFiatAccounts=Vos comptes en devise nationale
|
||||
|
||||
account.backup.title=Sauvegarder le portefeuille
|
||||
@ -1427,7 +1431,7 @@ dao.bond.table.column.bondType=Type de Bond
|
||||
dao.bond.table.column.details=Détails
|
||||
dao.bond.table.column.lockupTxId=Verrouiller le Tx de l'ID
|
||||
dao.bond.table.column.bondState=État du bond
|
||||
dao.bond.table.column.lockTime=Période de verrouillage
|
||||
dao.bond.table.column.lockTime=Unlock time
|
||||
dao.bond.table.column.lockupDate=Date de verrouillage
|
||||
|
||||
dao.bond.table.button.lockup=Vérrouillage
|
||||
@ -1850,12 +1854,16 @@ dao.factsAndFigures.dashboard.avgPrice30=Moyenne sur 30 jours du prix d'échange
|
||||
dao.factsAndFigures.dashboard.marketCap=Capitalisation boursière (basé sur la valeur d'échange)
|
||||
dao.factsAndFigures.dashboard.availableAmount=BSQ disponible au total
|
||||
|
||||
dao.factsAndFigures.supply.issuedVsBurnt=BSQ issued v. BSQ burnt
|
||||
|
||||
dao.factsAndFigures.supply.issued=BSQ émis
|
||||
dao.factsAndFigures.supply.genesisIssueAmount=BSQ émis lors de la transaction genesis
|
||||
dao.factsAndFigures.supply.compRequestIssueAmount=BSQ émis pour les demandes de compensation
|
||||
dao.factsAndFigures.supply.reimbursementAmount=BSQ émis pour les demandes de remboursement
|
||||
|
||||
dao.factsAndFigures.supply.burnt=BSQ précédemment burn
|
||||
dao.factsAndFigures.supply.burntMovingAverage=15-day moving average
|
||||
dao.factsAndFigures.supply.burntZoomToInliers=Zoom to inliers
|
||||
|
||||
dao.factsAndFigures.supply.locked=État global des BSQ verrouillés
|
||||
dao.factsAndFigures.supply.totalLockedUpAmount=Verrouillé dans les bonds
|
||||
@ -1930,14 +1938,14 @@ disputeSummaryWindow.reason.bank=Banque
|
||||
disputeSummaryWindow.summaryNotes=Notes de synthèse
|
||||
disputeSummaryWindow.addSummaryNotes=Ajouter des notes de synthèse
|
||||
disputeSummaryWindow.close.button=Fermer le ticket
|
||||
disputeSummaryWindow.close.msg=Ticket fermé le {0}\n\nRésumé :\nMontant du paiement pour l''acheteur BTC : {1}\nMontant du paiement pour le vendeur BTC : {2}\n\nNotes de synthèse :\n{3}
|
||||
disputeSummaryWindow.close.msg=Ticket fermé le {0}\n\nRésumé:\nMontant du paiement pour l''acheteur BTC: {1}\nMontant du paiement pour le vendeur BTC: {2}\n\nNotes de synthèse:\n{3}
|
||||
disputeSummaryWindow.close.nextStepsForMediation=\n\nProchaines étapes:\nOuvrir la transaction et accepter ou rejeter la suggestion du médiateur
|
||||
disputeSummaryWindow.close.nextStepsForRefundAgentArbitration=\n\nProchaines étapes :\nAucune autre action n'est requise de votre part. Si l'arbitre a rendu une décision en votre faveur, vous verrez une opération de " Remboursement à la suite de l'arbitrage " dans Fonds/Transactions
|
||||
disputeSummaryWindow.close.nextStepsForRefundAgentArbitration=\n\nProchaines étapes:\nAucune autre action n'est requise de votre part. Si l'arbitre a rendu une décision en votre faveur, vous verrez une opération de " Remboursement à la suite de l'arbitrage " dans Fonds/Transactions
|
||||
disputeSummaryWindow.close.closePeer=Vous devez également clore le ticket des pairs de trading !
|
||||
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=Dépenser : {0}\n{1}{2}Frais de transaction : {3} ({4} satoshis/octet)\nTaille de la transaction : {5} Kb\n\nÊtes-vous sûr de vouloir publier cette transaction ?
|
||||
disputeSummaryWindow.close.txDetails=Dépenser: {0}\n{1}{2}Frais de transaction: {3} ({4} satoshis/octet)\nTaille de la transaction: {5} Kb\n\nÊtes-vous sûr de vouloir publier cette transaction ?
|
||||
|
||||
emptyWalletWindow.headline={0} Outil de secours du portefeuille
|
||||
emptyWalletWindow.info=Veuillez utiliser ceci qu'en cas d'urgence si vous ne pouvez pas accéder à vos fonds à partir de l'interface utilisateur.\n\nVeuillez remarquer que touts les ordres en attente seront automatiquement fermés lors de l'utilisation de cet outil.\n\nAvant d'utiliser cet outil, veuillez sauvegarder votre répertoire de données. Vous pouvez le faire sur \"Compte/sauvegarde\".\n\nVeuillez nous signaler votre problème et déposer un rapport de bug sur GitHub ou sur le forum Bisq afin que nous puissions enquêter sur la source du problème.
|
||||
@ -2113,7 +2121,7 @@ popup.warning.btcChangeBelowDustException=Cette transaction crée une change out
|
||||
popup.warning.insufficientBsqFundsForBtcFeePayment=Vous ne disposez pas de suffisamment de fonds en BSQ pour payer les frais de transaction en BSQ. Vous pouvez payer les frais en BTC ou vous aurez besoin de provisionner votre portefeuille BSQ. Vous pouvez acheter des BSQ sur Bisq.\n\nFonds BSQ manquants: {0}
|
||||
popup.warning.noBsqFundsForBtcFeePayment=Votre portefeuille BSQ ne dispose pas de suffisamment de fonds pour payer les frais de transaction en BSQ.
|
||||
popup.warning.messageTooLong=Votre message dépasse la taille maximale autorisée. Veuillez l'envoyer en plusieurs parties ou le télécharger depuis un service comme https://pastebin.com.
|
||||
popup.warning.lockedUpFunds=Vous avez des fonds bloqués d''une transaction qui a échoué.\nSolde bloqué : {0}\nAdresse de la tx de dépôt : {1}\nID de l''échange : {2}.\n\nVeuillez ouvrir un ticket de support en sélectionnant la transaction dans l'écran des transactions ouvertes et en appuyant sur \"alt + o\" ou \"option + o\".
|
||||
popup.warning.lockedUpFunds=Vous avez des fonds bloqués d''une transaction qui a échoué.\nSolde bloqué: {0}\nAdresse de la tx de dépôt: {1}\nID de l''échange: {2}.\n\nVeuillez ouvrir un ticket de support en sélectionnant la transaction dans l'écran des transactions ouvertes et en appuyant sur \"alt + o\" ou \"option + o\".
|
||||
|
||||
popup.warning.nodeBanned=Un des nœuds {0} a été banni. Veuillez redémarrer votre application pour vous assurer de ne pas être connecté au nœud banni.
|
||||
popup.warning.priceRelay=Relais de prix
|
||||
@ -2123,18 +2131,18 @@ popup.warning.mandatoryUpdate.dao=Veuillez faire une mise à jour vers la derni
|
||||
popup.warning.disable.dao=La DAO de Bisq et BSQ sont désactivés temporairement. Veuillez consulter le Forum Bisq pour obtenir plus d'informations.
|
||||
popup.warning.burnBTC=Cette transaction n''est pas possible, car les frais de minage de {0} dépasseraient le montant à transférer de {1}. Veuillez patienter jusqu''à ce que les frais de minage soient de nouveau bas ou jusqu''à ce que vous ayez accumulé plus de BTC à transférer.
|
||||
|
||||
popup.warning.openOffer.makerFeeTxRejected=La transaction de frais de maker pour l''offre avec ID {0} a été rejetée par le réseau Bitcoin.\nID de transaction={1}.\nL''offre a été retirée pour éviter d''autres problèmes.\nAllez dans \"Paramètres/Info sur le réseau réseau\" et faites une resynchronisation SPV.\nPour obtenir de l''aide, le canal support de l''équipe Bisq est à disposition sur Keybase.
|
||||
popup.warning.openOffer.makerFeeTxRejected=La transaction de frais de maker pour l''offre avec ID {0} a été rejetée par le réseau Bitcoin.\nID de transaction={1}.\nL''offre a été retirée pour éviter d''autres problèmes.\nAllez dans \"Paramètres/Info sur le réseau réseau\" et faites une resynchronisation SPV.\nPour obtenir de l''aide, le canal support de l''équipe Bisq disposible sur Keybase.
|
||||
|
||||
popup.warning.trade.txRejected.tradeFee=frais de transaction
|
||||
popup.warning.trade.txRejected.deposit=dépôt
|
||||
popup.warning.trade.txRejected=La transaction {0} pour l''échange avec ID {1} a été rejetée par le réseau Bitcoin.\nID de transaction={2}.\nL''échange a été déplacé vers les échanges en échec.\nAllez dans \"Paramètres/Info sur le réseau réseau\" et faites une resynchronisation SPV.\nPour obtenir de l''aide, le canal support de l''équipe Bisq est à disposition sur Keybase.
|
||||
popup.warning.trade.txRejected=La transaction {0} pour l''échange avec ID {1} a été rejetée par le réseau Bitcoin.\nID de transaction={2}.\nL''échange a été déplacé vers les échanges en échec.\nAllez dans \"Paramètres/Info sur le réseau réseau\" et faites une resynchronisation SPV.\nPour obtenir de l''aide, le canal support de l''équipe Bisq est disponible sur Keybase.
|
||||
|
||||
popup.warning.openOfferWithInvalidMakerFeeTx=La transaction de frais de maker pour l''offre avec ID {0} n''est pas valide.\nID de transaction={1}.\nAllez dans \"Paramètres/Info sur le réseau réseau\" et faites une resynchronisation SPV.\nPour obtenir de l''aide, le canal support de l''équipe Bisq est à disposition sur Keybase.
|
||||
popup.warning.openOfferWithInvalidMakerFeeTx=La transaction de frais de maker pour l''offre avec ID {0} n''est pas valide.\nID de transaction={1}.\nAllez dans \"Paramètres/Info sur le réseau réseau\" et faites une resynchronisation SPV.\nPour obtenir de l''aide, le canal support de l''équipe Bisq est disponible sur Keybase.
|
||||
|
||||
popup.warning.trade.depositTxNull=The trade with ID ''{0}'' has no deposit transaction set.\n\nPlease restart the application to see if the problem still exists.\n\nIf it does, please open the trade details popup by clicking on the trade ID. Then click on the transaction IDs for the maker fee transaction and the taker fee transaction to view them on a block explorer. A transaction that cannot be found in a block explorer is probably an invalid transaction.\n\nIf this happens, please report it in the #support channel on the Bisq Keybase (https://keybase.io/team/bisq). If your trade fee transaction is invalid, no funds have left your wallet, you can move the trade to failed trades,and do an SPV resync for your funds to reappear (see how below).\n\nIf your trade fee transaction is valid, the fee amount is lost, and you can make a request for reimbursement on the support repository on GitHub (https://github.com/bisq-network/support/issues).\n\nIn both cases, please do an SPV resync from the ''Settings/Network'' screen to clean your wallet of any lingering issues!
|
||||
|
||||
popup.warning.trade.depositTxNull.moveToFailedTrades=Déplacer vers les échanges en échec
|
||||
popup.warning.trade.depositTxNull.shutDown=Shut down Bisq
|
||||
popup.warning.trade.depositTxNull.shutDown=Éteindre Bisq
|
||||
|
||||
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).
|
||||
|
||||
@ -2148,6 +2156,7 @@ popup.securityRecommendation.headline=Recommendation de sécurité importante
|
||||
popup.securityRecommendation.msg=Nous vous rappelons d'envisager d'utiliser la protection par mot de passe pour votre portefeuille si vous ne l'avez pas déjà activé.\n\nIl est également fortement recommandé d'écrire les mots de la seed de portefeuille. Ces mots de la seed sont comme un mot de passe principal pour récupérer votre portefeuille Bitcoin.\nVous trouverez plus d'informations à ce sujet dans l'onglet \"seed du portefeuille\".\n\nDe plus, il est recommandé de sauvegarder le dossier complet des données de l'application dans l'onglet \"Sauvegarde".
|
||||
|
||||
popup.bitcoinLocalhostNode.msg=Bisq a détecté un noeud Bitcoin Core fonctionnant localement (sur localhost).\nVeuillez vous assurer que ce nœud est entièrement synchronisé avant de lancer Bisq et qu'il ne fonctionne pas en mode restreint.
|
||||
popup.bitcoinLocalhostNode.additionalRequirements=\n\nStarting with Bitcoin Core v0.19 you have to manually enable bloom filters by setting peerbloomfilters=1 in your bitcoin.conf configuration file.
|
||||
|
||||
popup.shutDownInProgress.headline=Fermeture en cours
|
||||
popup.shutDownInProgress.msg=La fermeture de l'application nécessite quelques secondes.\nVeuillez ne pas interrompre ce processus.
|
||||
@ -2237,7 +2246,7 @@ guiUtil.openWebBrowser.warning=Vous allez ouvrir une page Web dans le navigateur
|
||||
guiUtil.openWebBrowser.doOpen=Ouvrir la page web et ne plus me le demander
|
||||
guiUtil.openWebBrowser.copyUrl=Copier l'URL et annuler
|
||||
guiUtil.ofTradeAmount=du montant du trade
|
||||
guiUtil.requiredMinimum=(required minimum)
|
||||
guiUtil.requiredMinimum=(minimum requis)
|
||||
|
||||
####################################################################
|
||||
# Component specific
|
||||
@ -2442,7 +2451,7 @@ payment.accountNr=Numéro de compte
|
||||
payment.emailOrMobile=Email ou numéro de portable
|
||||
payment.useCustomAccountName=Utiliser un nom de compte personnalisé
|
||||
payment.maxPeriod=Durée d'échange max. autorisée
|
||||
payment.maxPeriodAndLimit=Durée maximale de l''échange : {0} / Achat maximum : {1} / Vente maximum : {2} / Age du compte : {3}
|
||||
payment.maxPeriodAndLimit=Durée maximale de l''échange : {0} / Achat maximum : {1} / Vente maximum : {2} / Âge du compte : {3}
|
||||
payment.maxPeriodAndLimitCrypto=Durée maximale de trade: {0} / Limite maximale de trading {1}
|
||||
payment.currencyWithSymbol=Devise: {0}
|
||||
payment.nameOfAcceptedBank=Nom de la banque acceptée
|
||||
@ -2465,7 +2474,7 @@ payment.moneyGram.info=Lors de l'utilisation de MoneyGram, l'acheteur de BTC doi
|
||||
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 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=Pour limiter le risque de rétrofacturation des achats, Bisq fixe des limites d''achat par transaction en fonction des 2 facteurs suivants :\n\n1. Risque général de rétrofacturation pour le mode de paiement\n2. Statut de signature du compte\n\nCe compte de paiement que vous venez de créer comporte un certain risque de rétrofacturation et n''est pas encore signé par un arbitre ou un pair de confiance, il est donc limité à l''achat de {0} par transaction. Après sa signature, les limites d''achat augmenteront comme suit :\n\n● Avant la signature, et jusqu''à 30 jours après la signature, votre limite d''achat par transaction sera de {0}\n● 30 jours après la signature, votre limite d''achat par transaction sera de {1}\n● 60 jours après la signature, votre limite d''achat par transaction sera de {2}\n\nLes limites de vente ne sont pas affectées par la signature du compte, et augmentent simplement au fur et à mesure que l''âge du compte augmente. Pour plus d''informations, consultez le site https://docs.bisq.network/payment-methods#account-signing.\n\nIl n''y a pas de limite au nombre de transactions que vous pouvez effectuer.
|
||||
payment.limits.info.withSigning=Afin de limiter le risque de rétrofacturation des achats, Bisq fixe des limites d''achat par transaction en fonction des 2 facteurs suivants :\n\n1. Risque général de rétrofacturation pour le mode de paiement\n2. Statut de signature du compte\n\nCe compte de paiement que vous venez de créer comporte un certain risque de rétrofacturation et n''est pas encore signé par un arbitre ou un pair de confiance, il est donc limité à l''achat de {0} par transaction. Après sa signature, les limites d''achat augmenteront comme suit :\n\n● Avant la signature, et jusqu''à 30 jours après la signature, votre limite d''achat par transaction sera de {0}\n● 30 jours après la signature, votre limite d''achat par transaction sera de {1}\n● 60 jours après la signature, votre limite d''achat par transaction sera de {2}\n\nLes limites de vente ne sont pas affectées par la signature du compte, et augmentent simplement au fur et à mesure que l''âge du compte augmente. Pour plus d''informations, consultez le site https://docs.bisq.network/payment-methods#account-signing.\n\nIl n''y a pas de limite au nombre de transactions que vous pouvez effectuer.
|
||||
|
||||
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.
|
||||
|
||||
@ -2481,7 +2490,7 @@ payment.f2f.optionalExtra=Informations complémentaires facultatives
|
||||
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=Les transactions en 'face à face' ont des règles différentes et comportent des risques différents de ceux des transactions en ligne.\n\nLes principales différences sont les suivantes :\n● Les pairs de trading doivent échanger des informations sur le lieu et l'heure de la réunion en utilisant les coordonnées qu'ils ont fournies.\n● Les pairs de trading doivent apporter leur ordinateur portable et faire la confirmation du 'paiement envoyé' et du 'paiement reçu' sur le lieu de la réunion.\n● Si un maker a des 'modalités' spéciales, il doit les indiquer dans le champ 'Informations supplémentaires' du compte.\n● En acceptant une offre, le taker accepte les 'modalités' du maker.\n● En cas de litige, le médiateur ou l'arbitre ne peut pas beaucoup aider car il est généralement difficile d'obtenir des preuves de ce qui s'est passé lors de la réunion. Dans ce cas, les fonds des BTC peuvent être bloqués indéfiniment ou jusqu'à ce que les pairs parviennent à un accord.\n\nPour vous assurer de bien comprendre les spécificités des transactions 'face à face', veuillez lire les instructions et les recommandations à l'adresse https://docs.bisq.network/trading-rules.html#f2f-trading
|
||||
payment.f2f.info=Les transactions en 'face à face' ont des règles différentes et comportent des risques différents de ceux des transactions en ligne.\n\nLes principales différences sont les suivantes:\n● Les pairs de trading doivent échanger des informations sur le lieu et l'heure de la réunion en utilisant les coordonnées qu'ils ont fournies.\n● Les pairs de trading doivent apporter leur ordinateur portable et faire la confirmation du 'paiement envoyé' et du 'paiement reçu' sur le lieu de la réunion.\n● Si un maker a des 'modalités' spéciales, il doit les indiquer dans le champ 'Informations supplémentaires' du compte.\n● En acceptant une offre, le taker accepte les 'modalités' du maker.\n● En cas de litige, le médiateur ou l'arbitre ne peut pas beaucoup aider car il est généralement difficile d'obtenir des preuves de ce qui s'est passé lors de la réunion. Dans ce cas, les fonds des BTC peuvent être bloqués indéfiniment ou jusqu'à ce que les pairs parviennent à un accord.\n\nPour vous assurer de bien comprendre les spécificités des transactions 'face à face', veuillez lire les instructions et les recommandations à l'adresse https://docs.bisq.network/trading-rules.html#f2f-trading
|
||||
payment.f2f.info.openURL=Ouvrir la page web
|
||||
payment.f2f.offerbook.tooltip.countryAndCity=Pays et ville: {0} / {1}
|
||||
payment.f2f.offerbook.tooltip.extra=Informations complémentaires: {0}
|
||||
@ -2693,3 +2702,4 @@ validation.phone.invalidCharacters=Le numéro de téléphone {0} contient des ca
|
||||
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=L''indicatif de pays du numéro {0} n'est pas valable pour le pays {1}. Le bon indicatif est est {2}.
|
||||
validation.invalidAddressList=Must be comma separated list of valid addresses
|
||||
|
||||
@ -255,7 +255,7 @@ mainView.footer.bsqInfo.synchronizing=/ DAOと同期中
|
||||
mainView.footer.btcInfo.synchronizingWith=同期中
|
||||
mainView.footer.btcInfo.synchronizedWith=同期されています:
|
||||
mainView.footer.btcInfo.connectingTo=接続中:
|
||||
mainView.footer.btcInfo.connectionFailed=接続失敗
|
||||
mainView.footer.btcInfo.connectionFailed=Connection failed to
|
||||
mainView.footer.p2pInfo=Bisq network peers: {0}
|
||||
mainView.footer.daoFullNode=DAOのフルノード
|
||||
|
||||
@ -601,7 +601,8 @@ portfolio.pending.step2_seller.f2fInfo.headline=買い手の連絡先
|
||||
portfolio.pending.step2_seller.waitPayment.msg=デポジットトランザクションには、少なくとも1つのブロックチェーン承認があります。\nBTCの買い手が{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.refresh=Refresh Trade State
|
||||
portfolio.pending.step2_seller.refreshInfo=Sometimes P2P network messages acknowledging payment are not delivered, causing trades to get stuck. Hit the button below to make your peer resend the last message.
|
||||
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.
|
||||
@ -952,6 +953,7 @@ settings.net.warn.usePublicNodes=パブリックなビットコインネット
|
||||
settings.net.warn.usePublicNodes.useProvided=いいえ、提供されたノードを使用します
|
||||
settings.net.warn.usePublicNodes.usePublic=はい、公共ネットワークを使います
|
||||
settings.net.warn.useCustomNodes.B2XWarning=あなたのBitcoinノードが信頼できるBitcoin Coreノードであることを確認してください！\n\nBitcoin Coreのコンセンサスルールに従わないノードに接続すると、ウォレットが破損し、トレードプロセスに問題が生じる可能性があります。\n\nコンセンサスルールに違反するノードへ接続したユーザーは、引き起こされるいかなる損害に対しても責任を負います。 結果として生じる係争は、他のピアによって決定されます。この警告と保護のメカニズムを無視しているユーザーには、テクニカルサポートは提供されません！
|
||||
settings.net.warn.invalidBtcConfig=Connection to the Bitcoin network failed because your configuration is invalid.\n\nYour configuration has been reset to use the provided Bitcoin nodes instead. You will need to restart the application.
|
||||
settings.net.localhostBtcNodeInfo=（バックグラウンド情報：ローカルのBitcoinノード（ローカルホスト）を実行している場合は、そこへ排他的に接続できます。）
|
||||
settings.net.p2PPeersLabel=接続されたピア
|
||||
settings.net.onionAddressColumn=Onionアドレス
|
||||
@ -1110,6 +1112,8 @@ account.altcoin.popup.pars.msg=Trading ParsiCoin on Bisq requires that you under
|
||||
|
||||
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.liquidbitcoin.msg=Trading L-BTC on Bisq requires that you understand the following:\n\nWhen receiving L-BTC for a trade on Bisq, you cannot use the mobile Blockstream Green Wallet app or a custodial/exchange wallet. You must only receive L-BTC into the Liquid Elements Core wallet, or another L-BTC wallet which allows you to obtain the blinding key for your blinded L-BTC address.\n\nIn the event mediation is necessary, or if a trade dispute arises, you must disclose the blinding key for your receiving L-BTC address to the Bisq mediator or refund agent so they can verify the details of your Confidential Transaction on their own Elements Core full node.\n\nFailure to provide the required information to the mediator or refund agent will result in losing the dispute case. In all cases of dispute, the L-BTC receiver bears 100% of the burden of responsibility in providing cryptographic proof to the mediator or refund agent.\n\nIf you do not understand these requirements, do not trade L-BTC on Bisq.
|
||||
|
||||
account.fiat.yourFiatAccounts=あなたの各国通貨口座
|
||||
|
||||
account.backup.title=ウォレットのバックアップ
|
||||
@ -1427,7 +1431,7 @@ dao.bond.table.column.bondType=担保タイプ
|
||||
dao.bond.table.column.details=詳細
|
||||
dao.bond.table.column.lockupTxId=ロック Tx ID
|
||||
dao.bond.table.column.bondState=担保状態
|
||||
dao.bond.table.column.lockTime=ロック時間
|
||||
dao.bond.table.column.lockTime=Unlock time
|
||||
dao.bond.table.column.lockupDate=ロック日
|
||||
|
||||
dao.bond.table.button.lockup=ロック
|
||||
@ -1850,12 +1854,16 @@ dao.factsAndFigures.dashboard.avgPrice30=30 days average BSQ/BTC trade price
|
||||
dao.factsAndFigures.dashboard.marketCap=時価総額（トレード価格に基づく）
|
||||
dao.factsAndFigures.dashboard.availableAmount=合計利用可能BSQ
|
||||
|
||||
dao.factsAndFigures.supply.issuedVsBurnt=BSQ issued v. BSQ burnt
|
||||
|
||||
dao.factsAndFigures.supply.issued=発行されたBSQ
|
||||
dao.factsAndFigures.supply.genesisIssueAmount=ジェネシストランザクションで発行されたBSQ
|
||||
dao.factsAndFigures.supply.compRequestIssueAmount=報酬リクエストの為に発行されたBSQ
|
||||
dao.factsAndFigures.supply.reimbursementAmount=払い戻しリクエストの為に発行されたBSQ
|
||||
|
||||
dao.factsAndFigures.supply.burnt=バーン済BSQ
|
||||
dao.factsAndFigures.supply.burntMovingAverage=15-day moving average
|
||||
dao.factsAndFigures.supply.burntZoomToInliers=Zoom to inliers
|
||||
|
||||
dao.factsAndFigures.supply.locked=ロックされたBSQのグローバル状態
|
||||
dao.factsAndFigures.supply.totalLockedUpAmount=担保でロックされている
|
||||
@ -2148,6 +2156,7 @@ popup.securityRecommendation.headline=重要なセキュリティ勧告
|
||||
popup.securityRecommendation.msg=ウォレットのパスワード保護をまだ有効にしてない場合は、使用することを検討してください。\n\nウォレットシードワードを書き留めることも強くお勧めします。 これらのシードワードは、あなたのビットコインウォレットを復元するためのマスターパスワードのようなものです。\n「ウォレットシード」セクションにてより詳細な情報を確認できます。\n\nまた、「バックアップ」セクションのアプリケーションデータフォルダ全体をバックアップするべきでしょう。
|
||||
|
||||
popup.bitcoinLocalhostNode.msg=Bisqはローカルで動作するBitcoin Coreノード（ローカルホスト）を検出しました。Bisqを起動する前にこのノードが完全に同期されていることと、プルーニングモードで実行されていないことを確認してください。
|
||||
popup.bitcoinLocalhostNode.additionalRequirements=\n\nStarting with Bitcoin Core v0.19 you have to manually enable bloom filters by setting peerbloomfilters=1 in your bitcoin.conf configuration file.
|
||||
|
||||
popup.shutDownInProgress.headline=シャットダウン中
|
||||
popup.shutDownInProgress.msg=アプリケーションのシャットダウンには数秒かかることがあります。\nこのプロセスを中断しないでください。
|
||||
@ -2693,3 +2702,4 @@ 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.invalidAddressList=Must be comma separated list of valid addresses
|
||||
|
||||
@ -255,7 +255,7 @@ mainView.footer.bsqInfo.synchronizing=/ Sincronizando DAO
|
||||
mainView.footer.btcInfo.synchronizingWith=Sincronizando com
|
||||
mainView.footer.btcInfo.synchronizedWith=Sincronizado com
|
||||
mainView.footer.btcInfo.connectingTo=Conectando-se a
|
||||
mainView.footer.btcInfo.connectionFailed=falha na conexão
|
||||
mainView.footer.btcInfo.connectionFailed=Connection failed to
|
||||
mainView.footer.p2pInfo=Pares na rede Bisq: {0}
|
||||
mainView.footer.daoFullNode=Full node da DAO
|
||||
|
||||
@ -601,7 +601,8 @@ portfolio.pending.step2_seller.f2fInfo.headline=Informações de contato do comp
|
||||
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=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.
|
||||
|
||||
portfolio.pending.step2_seller.refresh=Refresh Trade State
|
||||
portfolio.pending.step2_seller.refreshInfo=Sometimes P2P network messages acknowledging payment are not delivered, causing trades to get stuck. Hit the button below to make your peer resend the last message.
|
||||
tradeChat.chatWindowTitle=Abrir janela de conversa para a negociação com ID "{0}"
|
||||
tradeChat.openChat=Abrir janela de conversa
|
||||
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.
|
||||
@ -919,7 +920,7 @@ setting.preferences.addAltcoin=Adicionar altcoin
|
||||
setting.preferences.displayOptions=Opções de exibição
|
||||
setting.preferences.showOwnOffers=Exibir minhas ofertas no livro de ofertas
|
||||
setting.preferences.useAnimations=Usar animações
|
||||
setting.preferences.useDarkMode=Usar tema escuro
|
||||
setting.preferences.useDarkMode=Use dark mode
|
||||
setting.preferences.sortWithNumOffers=Ordenar pelo nº de ofertas/negociações
|
||||
setting.preferences.resetAllFlags=Esquecer marcações \"Não exibir novamente\"
|
||||
setting.preferences.reset=Resetar
|
||||
@ -952,6 +953,7 @@ settings.net.warn.usePublicNodes=Ao usar a rede pública do Bitcoin, você estar
|
||||
settings.net.warn.usePublicNodes.useProvided=Não, usar os nodos fornecidos
|
||||
settings.net.warn.usePublicNodes.usePublic=Sim, usar rede pública
|
||||
settings.net.warn.useCustomNodes.B2XWarning=Certifique-se de que o seu nodo Bitcoin é um nodo Bitcoin Core confiável!\n\nAo se conectar a nodos que não estão seguindo as regras de consenso do Bitcoin Core, você pode corromper a sua carteira e causar problemas no processo de negociação.\n\nOs usuários que se conectam a nodos que violam as regras de consenso são responsáveis pelos danos que forem criados por isso. As disputas causadas por esse motivo serão decididas a favor do outro negociante. Nenhum suporte técnico será fornecido para os usuários que ignorarem esse aviso e os mecanismos de proteção!
|
||||
settings.net.warn.invalidBtcConfig=Connection to the Bitcoin network failed because your configuration is invalid.\n\nYour configuration has been reset to use the provided Bitcoin nodes instead. You will need to restart the application.
|
||||
settings.net.localhostBtcNodeInfo=(Nota: se você estiver rodando um nodo Bitcoin local (localhost), você pode conectar-se exclusivamente a ele.)
|
||||
settings.net.p2PPeersLabel=Pares conectados
|
||||
settings.net.onionAddressColumn=Endereço onion
|
||||
@ -1110,6 +1112,8 @@ account.altcoin.popup.pars.msg=Trading ParsiCoin on Bisq requires that you under
|
||||
|
||||
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.liquidbitcoin.msg=Trading L-BTC on Bisq requires that you understand the following:\n\nWhen receiving L-BTC for a trade on Bisq, you cannot use the mobile Blockstream Green Wallet app or a custodial/exchange wallet. You must only receive L-BTC into the Liquid Elements Core wallet, or another L-BTC wallet which allows you to obtain the blinding key for your blinded L-BTC address.\n\nIn the event mediation is necessary, or if a trade dispute arises, you must disclose the blinding key for your receiving L-BTC address to the Bisq mediator or refund agent so they can verify the details of your Confidential Transaction on their own Elements Core full node.\n\nFailure to provide the required information to the mediator or refund agent will result in losing the dispute case. In all cases of dispute, the L-BTC receiver bears 100% of the burden of responsibility in providing cryptographic proof to the mediator or refund agent.\n\nIf you do not understand these requirements, do not trade L-BTC on Bisq.
|
||||
|
||||
account.fiat.yourFiatAccounts=Suas contas de moeda nacional
|
||||
|
||||
account.backup.title=Backup da carteira
|
||||
@ -1427,7 +1431,7 @@ dao.bond.table.column.bondType=Tipo de vínculo
|
||||
dao.bond.table.column.details=Detalhes
|
||||
dao.bond.table.column.lockupTxId=ID da tx de bloqueio
|
||||
dao.bond.table.column.bondState=Estado do vínculo
|
||||
dao.bond.table.column.lockTime=Tempo de bloqueio
|
||||
dao.bond.table.column.lockTime=Unlock time
|
||||
dao.bond.table.column.lockupDate=Travado em
|
||||
|
||||
dao.bond.table.button.lockup=Travar
|
||||
@ -1850,12 +1854,16 @@ dao.factsAndFigures.dashboard.avgPrice30=30 days average BSQ/BTC trade price
|
||||
dao.factsAndFigures.dashboard.marketCap=Capitalização do mercado (com base no preço de negociação)
|
||||
dao.factsAndFigures.dashboard.availableAmount=Total de BSQ disponível
|
||||
|
||||
dao.factsAndFigures.supply.issuedVsBurnt=BSQ issued v. BSQ burnt
|
||||
|
||||
dao.factsAndFigures.supply.issued=BSQ emitido
|
||||
dao.factsAndFigures.supply.genesisIssueAmount=BSQ emitido na transação genesis
|
||||
dao.factsAndFigures.supply.compRequestIssueAmount=BDQ emitido para pedidos de compensação
|
||||
dao.factsAndFigures.supply.reimbursementAmount=BSQ emitido para pedidos de reembolso
|
||||
|
||||
dao.factsAndFigures.supply.burnt=BSQ destruído
|
||||
dao.factsAndFigures.supply.burntMovingAverage=15-day moving average
|
||||
dao.factsAndFigures.supply.burntZoomToInliers=Zoom to inliers
|
||||
|
||||
dao.factsAndFigures.supply.locked=Estado global de BSQ bloqueado
|
||||
dao.factsAndFigures.supply.totalLockedUpAmount=Bloqueado em vínculos
|
||||
@ -2148,6 +2156,7 @@ popup.securityRecommendation.headline=Recomendação de segurança importante
|
||||
popup.securityRecommendation.msg=Lembre-se de proteger a sua carteira com uma senha, caso você já não tenha criado uma.\n\nRecomendamos que você escreva num papel as palavras da semente de sua carteira. Essas palavras funcionam como uma senha mestra para recuperar a sua carteira Bitcoin, caso o seu computador apresente algum problema.\nVocê irá encontrar mais informações na seção \"Semente da carteira\".\n\nTambém aconselhamos que você faça um backup completo da pasta de dados do programa na seção \"Backup\".
|
||||
|
||||
popup.bitcoinLocalhostNode.msg=O Bisq detectou um node do Bitcoin Core em execução no ambiente local (localhost).\nPor favor, certifique-se de que este node esteja totalmente sincronizado antes de iniciar o Bisq e que ele não esteja em execução em pruned mode.
|
||||
popup.bitcoinLocalhostNode.additionalRequirements=\n\nStarting with Bitcoin Core v0.19 you have to manually enable bloom filters by setting peerbloomfilters=1 in your bitcoin.conf configuration file.
|
||||
|
||||
popup.shutDownInProgress.headline=Desligando
|
||||
popup.shutDownInProgress.msg=O desligamento do programa pode levar alguns segundos.\nPor favor, não interrompa este processo.
|
||||
@ -2693,3 +2702,4 @@ validation.phone.invalidCharacters=O número de telefone {0} contém caracteres
|
||||
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.invalidAddressList=Must be comma separated list of valid addresses
|
||||
|
||||
@ -189,7 +189,7 @@ shared.makerTxFee=Ofertante: {0}
|
||||
shared.takerTxFee=Aceitador: {0}
|
||||
shared.securityDepositBox.description=Depósito de segurança para BTC {0}
|
||||
shared.iConfirm=Eu confirmo
|
||||
shared.tradingFeeInBsqInfo=equivalent to {0} used as trading fee
|
||||
shared.tradingFeeInBsqInfo=equivalente à {0} utilizado como taxa de negociação
|
||||
shared.openURL=Abrir {0}
|
||||
shared.fiat=Moeda fiduciária
|
||||
shared.crypto=Cripto
|
||||
@ -255,7 +255,7 @@ mainView.footer.bsqInfo.synchronizing=/ Sincronizando a OAD
|
||||
mainView.footer.btcInfo.synchronizingWith=Sincronizando com
|
||||
mainView.footer.btcInfo.synchronizedWith=Sincronizado com
|
||||
mainView.footer.btcInfo.connectingTo=Conectando à
|
||||
mainView.footer.btcInfo.connectionFailed=falha na conexão
|
||||
mainView.footer.btcInfo.connectionFailed=Connection failed to
|
||||
mainView.footer.p2pInfo=Pares na rede do Bisq: {0}
|
||||
mainView.footer.daoFullNode=Nó completo da OAD
|
||||
|
||||
@ -388,7 +388,7 @@ offerbook.warning.currencyBanned=A moeda usada nessa oferta foi bloqueada pelos
|
||||
offerbook.warning.paymentMethodBanned=O método de pagamento usado nessa oferta foi bloqueado pelos desenvolvedores do Bisq.\nPor favor, visite o Fórum Bisq para mais informações.
|
||||
offerbook.warning.nodeBlocked=O endereço onion desse negociador foi bloqueado pelos desenvolvedores do Bisq.\nProvavelmente, há um erro não tratado causando problemas ao aceitar ofertas desse negociador.
|
||||
offerbook.warning.requireUpdateToNewVersion=A sua versão do Bisq deixou de ser compatível para negociação.\nAtualize para a versão mais recente do Bisq em https://bisq.network/downloads.
|
||||
offerbook.warning.tradeLimitNotMatching=Your payment account has been created {0} ago. Your trade limit is based on the account age and is not sufficient for that offer.\n\nYour trade limit is: {1}\nThe min. trade amount of the offer is: {2}.\n\nYou cannot take that offer at the moment. Once your account is older than 2 months this restriction gets removed.
|
||||
offerbook.warning.tradeLimitNotMatching=A sua conta de pagamento foi criada há {0}. O seu limite de negócio é baseado na idade da conta e não é suficiente para essa oferta.\n\nO seu limite de negócio é de: {1}\nA mín. quantia de negócio da oferta é de: {2}.\n\nVocê não pode aceitar essa oferta agora. Assim que a sua conta tiver mais de 2 meses esta restrição será removida.
|
||||
|
||||
|
||||
offerbook.info.sellAtMarketPrice=Venderá ao preço de mercado (atualizado à cada minuto).
|
||||
@ -461,7 +461,7 @@ createOffer.setDeposit=Definir o depósito de segurança do comprador (%)
|
||||
createOffer.setDepositAsBuyer=Definir o meu depósito de segurança enquanto comprador (%)
|
||||
createOffer.securityDepositInfo=O depósito de segurança do seu comprador será {0}
|
||||
createOffer.securityDepositInfoAsBuyer=O seu depósito de segurança enquanto comprador será {0}
|
||||
createOffer.minSecurityDepositUsed=Min. buyer security deposit is used
|
||||
createOffer.minSecurityDepositUsed=O mín. depósito de segurança para o comprador é utilizado
|
||||
|
||||
|
||||
####################################################################
|
||||
@ -601,7 +601,8 @@ portfolio.pending.step2_seller.f2fInfo.headline=Informação do contacto do comp
|
||||
portfolio.pending.step2_seller.waitPayment.msg=A transação de depósito tem pelo menos uma confirmação da blockchain.\nVocê precisa esperar até que o comprador de BTC inicie o pagamento {0}.
|
||||
portfolio.pending.step2_seller.warn=O comprador do BTC ainda não efetuou o pagamento de {0}.\nVocê precisa esperar até que eles tenham iniciado o pagamento.\nSe o negócio não for concluído em {1}, o árbitro irá investigar.
|
||||
portfolio.pending.step2_seller.openForDispute=O comprador de BTC não iniciou o seu pagamento!\nO período máx. permitido para o negócio acabou.\nVocê pode esperar e dar mais tempo ao seu par de negociação ou entrar em contacto com o mediador para assistência.
|
||||
|
||||
portfolio.pending.step2_seller.refresh=Atualizar o Estado do Negócio
|
||||
portfolio.pending.step2_seller.refreshInfo=Às vezes, as mensagens da rede P2P que reconhecem o pagamento não são entregues, causando falhas no negócio. Clique no botão abaixo para que o seu par reenvie a última mensagem.
|
||||
tradeChat.chatWindowTitle=Janela de chat para o negócio com o ID ''{0}''
|
||||
tradeChat.openChat=Abrir janela de chat
|
||||
tradeChat.rules=Você pode comunicar com o seu par de negociação para resolver problemas com este negócio.\nNão é obrigatório responder no chat.\nSe algum negociante infringir alguma das regras abaixo, abra uma disputa e reporte-o ao mediador ou ao árbitro.\n\nRegras do chat:\n\t● Não envie nenhum link (risco de malware). Você pode enviar o ID da transação e o nome de um explorador de blocos.\n\t● Não envie as suas palavras-semente, chaves privadas, senhas ou outra informação sensitiva!\n\t● Não encoraje negócios fora do Bisq (sem segurança).\n\t● Não engaje em nenhuma forma de scams de engenharia social.\n\t● Se um par não responde e prefere não comunicar pelo chat, respeite a sua decisão.\n\t● Mantenha o âmbito da conversa limitado ao negócio. Este chat não é um substituto para o messenger ou uma caixa para trolls.\n\t● Mantenha a conversa amigável e respeitosa.
|
||||
@ -706,9 +707,9 @@ portfolio.pending.openSupportTicket.headline=Abrir bilhete de apoio
|
||||
portfolio.pending.openSupportTicket.msg=Por favor, use esta função apenas em casos de emergência, se você não vir o botão \"Abrir apoio\" ou \"Abrir disputa\".\n\nQuando você abre um bilhete de apoio, o negócio será interrompido e tratado por um mediador ou árbitro.
|
||||
|
||||
portfolio.pending.timeLockNotOver=Você deve esperar ≈{0} (mais {1} blocos) antes que você possa abrir uma disputa de arbitragem.
|
||||
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=A transação de depósito é null. Você não pode abrir a disputa sem uma transação de depósito válida. Por favor vá à \"Definições/Informação da Rede\" e re-sincronize o ficheiro SPV.\n\nPara mais ajuda por favor contacte o canal de apoio do Bisq na equipa Keybase do Bisq.
|
||||
portfolio.pending.mediationResult.error.depositTxNull=A transação de depósito é null. O negócio foi movido para a secção de negócios falhados.
|
||||
portfolio.pending.error.depositTxNotConfirmed=A transação de depósito não foi confirmada. Você pode abrir uma disputa de arbitragem com uma transação de depósito não confirmada. Por favor espere até que seja confirmada ou vá à \"Definições/Informação da Rede\" e re-sincronize o ficheiro SPV.\n\nPara mais ajuda por favor contacte o canal de apoio do Bisq na equipa Keybase do Bisq.
|
||||
|
||||
portfolio.pending.notification=Notificação
|
||||
|
||||
@ -873,7 +874,7 @@ support.sellerOfferer=Vendedor de BTC/Ofertante
|
||||
support.buyerTaker=Comprador de BTC/Aceitador
|
||||
support.sellerTaker=Vendedor de BTC/Aceitador
|
||||
|
||||
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.backgroundInfo=O Bisq não é uma empresa, por isso as disputas são tratadas diferentemente.\n\nOs negociadores podem se comunicar dentro do programa via chat seguro no ecrã de negócios abertos para tentar resolver disputas por conta própria. Se isso não for suficiente, um mediador pode ajudar. O mediador avaliará a situação e sugerirá um pagamento dos fundos de 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 sugerido pelo mediador, eles podem solicitar a arbitragem. O árbitro reavaliará a situação e, se justificado, pagará pessoalmente o comerciante de volta e solicitará reembolso à OAD do Bisq.
|
||||
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}
|
||||
@ -895,7 +896,7 @@ settings.tab.about=Sobre
|
||||
|
||||
setting.preferences.general=Preferências gerais
|
||||
setting.preferences.explorer=Explorador de blocos de Bitcoin
|
||||
setting.preferences.explorer.bsq=BSQ block explorer
|
||||
setting.preferences.explorer.bsq=Explorador de blocos de BSQ
|
||||
setting.preferences.deviation=Máx. desvio do preço de mercado
|
||||
setting.preferences.avoidStandbyMode=Evite o modo espera
|
||||
setting.preferences.deviationToLarge=Valores acima de {0}% não são permitidos.
|
||||
@ -919,12 +920,12 @@ setting.preferences.addAltcoin=Adicionar altcoin
|
||||
setting.preferences.displayOptions=Mostrar opções
|
||||
setting.preferences.showOwnOffers=Mostrar as minhas próprias ofertas no livro de ofertas
|
||||
setting.preferences.useAnimations=Usar animações
|
||||
setting.preferences.useDarkMode=Usar o mod escuro
|
||||
setting.preferences.useDarkMode=Usar o modo escuro
|
||||
setting.preferences.sortWithNumOffers=Ordenar listas de mercado por nº de ofertas/negociações:
|
||||
setting.preferences.resetAllFlags=Reiniciar todos os marcadores \"Não mostrar novamente\"
|
||||
setting.preferences.reset=Limpar
|
||||
settings.preferences.languageChange=Para aplicar a mudança de língua em todas os ecrãs requer uma reinicialização.
|
||||
settings.preferences.supportLanguageWarning=In case of a dispute, please note that mediation is handled in {0} and arbitration in {1}.
|
||||
settings.preferences.supportLanguageWarning=Em caso de disputa, por favor saiba que a mediação será tratada em {0} e a arbitragem em {1}.
|
||||
settings.preferences.selectCurrencyNetwork=Selecionar rede
|
||||
setting.preferences.daoOptions=Opções da OAD
|
||||
setting.preferences.dao.resync.label=Reconstruir o estado da OAD à partir da tx genesis
|
||||
@ -952,6 +953,7 @@ settings.net.warn.usePublicNodes=Se você usa a rede pública Bitcoin, você est
|
||||
settings.net.warn.usePublicNodes.useProvided=Não, usar nós providenciados
|
||||
settings.net.warn.usePublicNodes.usePublic=Sim, usar a rede pública
|
||||
settings.net.warn.useCustomNodes.B2XWarning=Por favor, certifique-se de que seu nó Bitcoin é um nó confiável do Bitcoin Core!\n\nConectar-se a nós que não seguem as regras de consenso do Bitcoin Core pode corromper a sua carteira e causar problemas no processo de negócio.\n\nOs usuários que se conectam a nós que violam regras de consenso são responsáveis por qualquer dano resultante. Quaisquer disputas resultantes serão decididas em favor do outro par. Nenhum suporte técnico será dado aos usuários que ignorarem esses alertas e mecanismos de proteção!
|
||||
settings.net.warn.invalidBtcConfig=A conexão à rede Bitcoin falhou porque sua configuração é inválida.\n\nA sua configuração foi redefinida para usar os nós de Bitcoin fornecidos. Você precisará reiniciar o programa.
|
||||
settings.net.localhostBtcNodeInfo=(Informação de segundo plano: Se você está a executar um nó local de Bitcoin (localhost), você pode-se conetar exclusivamente à ele.)
|
||||
settings.net.p2PPeersLabel=Pares conectados
|
||||
settings.net.onionAddressColumn=Endereço onion
|
||||
@ -979,7 +981,7 @@ settings.net.inbound=entrante
|
||||
settings.net.outbound=sainte
|
||||
settings.net.reSyncSPVChainLabel=Re-sincronizar corrente SPV
|
||||
settings.net.reSyncSPVChainButton=Remover ficheiro SPV e re-sincronizar
|
||||
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=O ficheiro da corrente SPV será apagado na próxima inicialização. Você precisa reiniciar o seu programa agora.\n\nApós a reinicialização, pode demorar um pouco para ressincronizar com a rede e você verá todas as transações apenas quando a ressincronização for concluída.\n\nDependendo do número de transações e da idade da sua carteira, a ressincronização pode levar algumas horas e consumir 100% do CPU. Não interrompa o processo, caso contrário você precisará repeti-lo.
|
||||
settings.net.reSyncSPVAfterRestart=O ficheiro da corrente SPV foi apagado. Por favor, seja paciente. Pode demorar um pouco para re-sincronizar com a rede.
|
||||
settings.net.reSyncSPVAfterRestartCompleted=A resincronização concluiu. Por favor reiniciar o programa.
|
||||
settings.net.reSyncSPVFailed=Não foi possível remover o ficherio da corrente SPV\nErro: {0}
|
||||
@ -1002,60 +1004,60 @@ setting.about.version=Versão do programa
|
||||
setting.about.subsystems.label=Versão de subsistemas
|
||||
setting.about.subsystems.val=Versão da rede: {0}; Versão de mensagem P2P: {1}; Versão da base de dados local: {2}; Versão do protocolo de negócio: {3}
|
||||
|
||||
setting.about.shortcuts=Short cuts
|
||||
setting.about.shortcuts.ctrlOrAltOrCmd=''Ctrl + {0}'' or ''alt + {0}'' or ''cmd + {0}''
|
||||
setting.about.shortcuts=Atalhos
|
||||
setting.about.shortcuts.ctrlOrAltOrCmd=''Ctrl + {0}'' ou ''alt + {0}'' ou ''cmd + {0}''
|
||||
|
||||
setting.about.shortcuts.menuNav=Navigate main menu
|
||||
setting.about.shortcuts.menuNav.value=To navigate the main menu press: 'Ctrl' or 'alt' or 'cmd' with a numeric key between '1-9'
|
||||
setting.about.shortcuts.menuNav=Navigar o menu principal
|
||||
setting.about.shortcuts.menuNav.value=Para navigar o menu principal pressione:: 'Ctrl' ou 'alt' ou 'cmd' juntamente com uma tecla numérica entre '1-9'
|
||||
|
||||
setting.about.shortcuts.close=Close Bisq
|
||||
setting.about.shortcuts.close.value=''Ctrl + {0}'' or ''cmd + {0}'' or ''Ctrl + {1}'' or ''cmd + {1}''
|
||||
setting.about.shortcuts.close=Fechar o Bisq
|
||||
setting.about.shortcuts.close.value=''Ctrl + {0}'' ou ''cmd + {0}'' ou ''Ctrl + {1}'' ou ''cmd + {1}''
|
||||
|
||||
setting.about.shortcuts.closePopup=Close popup or dialog window
|
||||
setting.about.shortcuts.closePopup.value='ESCAPE' key
|
||||
setting.about.shortcuts.closePopup=Fechar popup ou janela de diálogo
|
||||
setting.about.shortcuts.closePopup.value=Tecla "ESCAPE"
|
||||
|
||||
setting.about.shortcuts.chatSendMsg=Send trader chat message
|
||||
setting.about.shortcuts.chatSendMsg.value=''Ctrl + ENTER'' or ''alt + ENTER'' or ''cmd + ENTER''
|
||||
setting.about.shortcuts.chatSendMsg=Enviar uma mensagem ao negociador
|
||||
setting.about.shortcuts.chatSendMsg.value=''Ctrl + ENTER'' ou ''alt + ENTER'' ou ''cmd + ENTER''
|
||||
|
||||
setting.about.shortcuts.openDispute=Open dispute
|
||||
setting.about.shortcuts.openDispute.value=Select pending trade and click: {0}
|
||||
setting.about.shortcuts.openDispute=Abrir disputa
|
||||
setting.about.shortcuts.openDispute.value=Selecionar negócio pendente e clicar: {0}
|
||||
|
||||
setting.about.shortcuts.walletDetails=Open wallet details window
|
||||
setting.about.shortcuts.walletDetails=Abrir janela de detalhes da carteira
|
||||
|
||||
setting.about.shortcuts.openEmergencyBtcWalletTool=Open emergency wallet tool for BTC wallet
|
||||
setting.about.shortcuts.openEmergencyBtcWalletTool=Abrir ferramenta e emergência da carteira para a carteira de BTC
|
||||
|
||||
setting.about.shortcuts.openEmergencyBsqWalletTool=Open emergency wallet tool for BSQ wallet
|
||||
setting.about.shortcuts.openEmergencyBsqWalletTool=Abrir ferramenta e emergência da carteira para a carteira de BSQ
|
||||
|
||||
setting.about.shortcuts.showTorLogs=Toggle log level for Tor messages between DEBUG and WARN
|
||||
setting.about.shortcuts.showTorLogs=Escolher o nível de log para mensagens Tor entre DEBUG e WARN
|
||||
|
||||
setting.about.shortcuts.showDisputeStatistics=Show summary of all disputes
|
||||
setting.about.shortcuts.showDisputeStatistics.value=Navigate to disputes view and press: {0}
|
||||
setting.about.shortcuts.showDisputeStatistics=Mostrar resumo de todas as disputas
|
||||
setting.about.shortcuts.showDisputeStatistics.value=Navigar para o ecrã de disputas e pressionar: {0}
|
||||
|
||||
setting.about.shortcuts.manualPayoutTxWindow=Open window for manual payout from 2of2 Multisig deposit tx
|
||||
setting.about.shortcuts.manualPayoutTxWindow=Abrir janela para pagamento manual da tx de depósito multi-assinatura 2de2
|
||||
|
||||
setting.about.shortcuts.reRepublishAllGovernanceData=Republish DAO governance data (proposals, votes)
|
||||
setting.about.shortcuts.reRepublishAllGovernanceData=Republicar informação da governação da OAD (propostas, votos)
|
||||
|
||||
setting.about.shortcuts.removeStuckTrade=Open popup to move stuck trade to failed trades tab (only use if you are sure)
|
||||
setting.about.shortcuts.removeStuckTrade.value=Select pending trade and press: {0}
|
||||
setting.about.shortcuts.removeStuckTrade=Abrir popup para mover negócios presos para a aba de negócios falhados (apenas usar se tiver certeza)
|
||||
setting.about.shortcuts.removeStuckTrade.value=Selecionar negócios pendentes e pressionar: {0}
|
||||
|
||||
setting.about.shortcuts.registerArbitrator=Register arbitrator (mediator/arbitrator only)
|
||||
setting.about.shortcuts.registerArbitrator.value=Navigate to account and press: {0}
|
||||
setting.about.shortcuts.registerArbitrator=Registrar árbitro (apenas mediador/árbitro)
|
||||
setting.about.shortcuts.registerArbitrator.value=Navigar para conta e pressionar: {0}
|
||||
|
||||
setting.about.shortcuts.registerMediator=Register mediator (mediator/arbitrator only)
|
||||
setting.about.shortcuts.registerMediator.value=Navigate to account and press: {0}
|
||||
setting.about.shortcuts.registerMediator=Registar mediador (apenas medidor/árbitro)
|
||||
setting.about.shortcuts.registerMediator.value=Navigar para conta e pressionar: {0}
|
||||
|
||||
setting.about.shortcuts.reOpenDispute=Re-open already closed dispute (mediator/arbitrator only)
|
||||
setting.about.shortcuts.reOpenDispute.value=Select closed dispute and press: {0}
|
||||
setting.about.shortcuts.reOpenDispute=Re-abrir disputas fechadas (apenas mediador/árbitro)
|
||||
setting.about.shortcuts.reOpenDispute.value=Selecionar disputas fechadas e pressionar: {0}
|
||||
|
||||
setting.about.shortcuts.openSignPaymentAccountsWindow=Open window for account age signing (legacy arbitrators only)
|
||||
setting.about.shortcuts.openSignPaymentAccountsWindow.value=Navigate to legacy arbitrator view and press: {0}
|
||||
setting.about.shortcuts.openSignPaymentAccountsWindow=Abrir janela para assinatura de idade da conta (apenas árbitros legacy)
|
||||
setting.about.shortcuts.openSignPaymentAccountsWindow.value=Navigar para o ecrã de árbitro legacy e pressionar: {0}
|
||||
|
||||
setting.about.shortcuts.sendAlertMsg=Send alert or update message (privileged activity)
|
||||
setting.about.shortcuts.sendAlertMsg=Enviar alerta ou mensagem de atualização (atividade privilegiada)
|
||||
|
||||
setting.about.shortcuts.sendFilter=Set Filter (privileged activity)
|
||||
setting.about.shortcuts.sendFilter=Definir Filtro (atividade privilegiada)
|
||||
|
||||
setting.about.shortcuts.sendPrivateNotification=Send private notification to peer (privileged activity)
|
||||
setting.about.shortcuts.sendPrivateNotification.value=Open peer info at avatar or dispute and press: {0}
|
||||
setting.about.shortcuts.sendPrivateNotification=Enviar notificação privada ao par (atividade privilegiada)
|
||||
setting.about.shortcuts.sendPrivateNotification.value=Abrir informação do par no avatar ou na disputa e pressionar: {0}
|
||||
|
||||
|
||||
####################################################################
|
||||
@ -1094,7 +1096,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=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.xmr.msg=A negociação de XMR no Bisq exige que você entenda e cumpra os seguintes requerimentos:\n\nProvar pagamentos: como o Monero é uma moeda privada, alguns detalhes da transação não estão disponíveis publicamente na blockchain e, em caso de disputa, o mediador ou o árbitro precisa deles para verificar se a transação foi realmente feita. No Bisq, o remetente da transação XMR é o responsável por fornecer essas informações ao mediador ou árbitro no caso de uma disputa. Para fazer isso, você deve enviar o XMR usando uma carteira que forneça as informações necessárias para provar que o pagamento foi feito, o que inclui:\n\n- a chave da transação (chave TX, chave secreta TX ou chave privada TX)\n- o ID da transação (Tx ID ou Tx Hash)\n- o endereço de destino (endereço do destinatário)\n\nEssas informações podem ser encontradas nas carteiras oficiais Monero GUI & CLI, MyMonero e Exodus (desktop), bem como em Cake Wallet, MyMonero e Monerujo (mobile), nos seguintes locais:\n\n- GUI do Monero: vá para a aba Transações\n- CLI do Monero: use o comando get_tx_key TXID. O sinalizador store-tx-info deve estar ativado (ativado por padrão em novas versões)\n- Outras carteiras: acesse o histórico de transações e procure a chave de transação (chave Tx ou chave secreta) e o endereço de destino numa transação enviada. A opção Salvar endereço do destinatário deve estar ativada nas configurações da Cake Wallet.\n\nSe você estiver usando uma carteira diferente da mencionada acima, verifique se pode acessar essas três informações. Como a chave da transação e o endereço de destino estão armazenados no software da carteira Monero e não podem ser recuperados na blockchain Monero, você nunca deve excluir ou restaurar sua carteira Monero antes que um negócio do Bisq seja concluída. O não fornecimento dos dados acima resultará na perda do caso de disputa.\n\nVerificar pagamentos: com essas três informações, a verificação de que uma quantidade de Monero foi enviada para um endereço específico pode ser realizada da seguinte maneira:\n\n- Monero GUI: altere a carteira para o modo Avançado e vá para Avançado> Prove/check> Verificar transação\n- CLI Monero: use o comando check_tx_key TXID TXKEY ADDRESS\n- Ferramenta XMR checktx (https://xmr.llcoins.net/checktx.html)\n- Explore o site Monero (https://www.exploremonero.com/receipt)\n\nSe você ainda não tiver certeza sobre esse processo, visite (https://www.getmonero.org/resources/user-guides/prove-payment.html) para encontrar mais informações ou pergunte no subreddit de suporte do Monero (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).
|
||||
@ -1110,6 +1112,8 @@ account.altcoin.popup.pars.msg=A negociação de ParsiCoin no Bisq exige que voc
|
||||
|
||||
account.altcoin.popup.blk-burnt.msg=Para negociar blackcoins queimados, você precisa saber o seguinte:\n\nBlackcoins queimados não podem ser gastos. Para os negociar no Bisq, os output scripts precisam estar na forma: OP_RETURN OP_PUSHDATA, seguido pelos data bytes que, após serem codificados em hex, constituem endereços. Por exemplo, blackcoins queimados com um endereço 666f6f (“foo” em UTF-8) terá o seguinte script:\n\nOP_RETURN OP_PUSHDATA 666f6f\n\nPara criar blackcoins queimados, deve-se usar o comando RPC “burn” disponível em algumas carteiras.\n\nPara casos possíveis, confira https://ibo.laboratorium.ee .\n\nComo os blackcoins queimados não podem ser gastos, eles não podem voltar a ser vendidos. “Vender” blackcoins queimados significa queimar blackcoins comuns (com os dados associados iguais ao endereço de destino).\n\nEm caso de disputa, o vendedor de BLK precisa providenciar o hash da transação.
|
||||
|
||||
account.altcoin.popup.liquidbitcoin.msg=A negociação de L-BTC no Bisq exige que você entenda o seguinte:\n\nAo receber L-BTC para um negócio no Bisq, você não pode usar a aplicação móvel Blockstream Green Wallet ou uma carteira de custódia / exchange. Você só deve receber o L-BTC na carteira Liquid Elements Core ou em outra carteira L-BTC que permita obter a chave ofuscante para o seu endereço L-BTC cego.\n\nNo caso de ser necessária mediação, ou se surgir uma disputa de negócio, você deve divulgar a chave ofuscante do seu endereço L-BTC de recebimento ao mediador ou agente de reembolso Bisq, para que eles possam verificar os detalhes da sua Transação Confidencial no seu próprio Elements Core full node.\n\nO não fornecimento das informações necessárias ao mediador ou ao agente de reembolso resultará na perda do caso de disputa. Em todos os casos de disputa, o recipiente de L-BTC suporta 100% da responsabilidade ao fornecer prova criptográfica ao mediador ou ao agente de reembolso.\n\nSe você não entender esses requerimentos, não negocie o L-BTC no Bisq.
|
||||
|
||||
account.fiat.yourFiatAccounts=A sua conta de moeda nacional
|
||||
|
||||
account.backup.title=Carteira de backup
|
||||
@ -1225,7 +1229,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.reputationBalance=Valor de Mérito (não gastável)
|
||||
|
||||
dao.tx.published.success=Sua transação foi publicada com sucesso.
|
||||
dao.proposal.menuItem.make=Criar proposta
|
||||
@ -1256,12 +1260,12 @@ dao.results.cycles.table.header.issuance=Emissão
|
||||
dao.results.results.table.item.cycle=Ciclo {0} começou: {1}
|
||||
|
||||
dao.results.proposals.header=Propostas do ciclo selecionado
|
||||
dao.results.proposals.table.header.nameLink=Name/link
|
||||
dao.results.proposals.table.header.nameLink=Nome/link
|
||||
dao.results.proposals.table.header.details=Detalhes
|
||||
dao.results.proposals.table.header.myVote=O meu voto
|
||||
dao.results.proposals.table.header.result=Resultado da votação
|
||||
dao.results.proposals.table.header.threshold=Threshold
|
||||
dao.results.proposals.table.header.quorum=Quorum
|
||||
dao.results.proposals.table.header.threshold=Limite
|
||||
dao.results.proposals.table.header.quorum=Quórum
|
||||
|
||||
dao.results.proposals.voting.detail.header=Resultado dos votos para a proposta selecionada
|
||||
|
||||
@ -1427,7 +1431,7 @@ dao.bond.table.column.bondType=Tipo de vínculo
|
||||
dao.bond.table.column.details=Detalhes
|
||||
dao.bond.table.column.lockupTxId=ID da tx de bloqueio
|
||||
dao.bond.table.column.bondState=Estado de vínculo
|
||||
dao.bond.table.column.lockTime=Tempo de bloqueio
|
||||
dao.bond.table.column.lockTime=Unlock time
|
||||
dao.bond.table.column.lockupDate=Data de bloqueio
|
||||
|
||||
dao.bond.table.button.lockup=Bloqueio
|
||||
@ -1850,12 +1854,16 @@ dao.factsAndFigures.dashboard.avgPrice30=Média de 30 dias do preço de negócio
|
||||
dao.factsAndFigures.dashboard.marketCap=Capitalização do mercado (com base no preço de negócio)
|
||||
dao.factsAndFigures.dashboard.availableAmount=Total BSQ disponível
|
||||
|
||||
dao.factsAndFigures.supply.issuedVsBurnt=BSQ emitido v. BSQ queimado
|
||||
|
||||
dao.factsAndFigures.supply.issued=BSQ emitido
|
||||
dao.factsAndFigures.supply.genesisIssueAmount=BSQ emitido na transação genesis
|
||||
dao.factsAndFigures.supply.compRequestIssueAmount=BDQ emitido para pedidos de compensação
|
||||
dao.factsAndFigures.supply.reimbursementAmount=BSQ emitido para pedidos de reembolso
|
||||
|
||||
dao.factsAndFigures.supply.burnt=BSQ destruído
|
||||
dao.factsAndFigures.supply.burntMovingAverage=Média móvel de 15 dias
|
||||
dao.factsAndFigures.supply.burntZoomToInliers=Zoom para inliers
|
||||
|
||||
dao.factsAndFigures.supply.locked=Estado global do BSQ bloqueado
|
||||
dao.factsAndFigures.supply.totalLockedUpAmount=Bloqueado em vínculos
|
||||
@ -2020,7 +2028,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=Dispute resolution
|
||||
tacWindow.arbitrationSystem=Resolução da disputa
|
||||
|
||||
tradeDetailsWindow.headline=Negócio
|
||||
tradeDetailsWindow.disputedPayoutTxId=ID de transação do pagamento disputado:
|
||||
@ -2084,8 +2092,8 @@ popup.error.takeOfferRequestFailed=Ocorreu um erro quando alguém tentou aceitar
|
||||
|
||||
error.spvFileCorrupted=Ocorreu um erro ao ler o ficheiro da corrente SPV .\nPode ser que o ficheiro da corrente SPV esteja corrompido.\n\nMensagem de erro: {0}\n\nVocê deseja apagá-lo e iniciar uma resincronização?
|
||||
error.deleteAddressEntryListFailed=Não foi possível apagar o ficheiro AddressEntryList.\nErro: {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=A transação de depósito do negócio fechado com o ID de negócio {0} ainda não foi confirmada.\n\nPor favor re-sinronize o ficheiro SPV em \"Definições/Informação da Rede\" para ver se a transação é inválida.
|
||||
error.closedTradeWithNoDepositTx=A transação de depósito do negócio fechado com o ID de negócio {0} é null.\n\nPor favor reinicie o programa para limpar a lista de negócios fechados.
|
||||
|
||||
popup.warning.walletNotInitialized=A carteira ainda não foi inicializada
|
||||
popup.warning.wrongVersion=Você provavelmente tem a versão errada do Bisq para este computador.\nA arquitetura do seu computador é: {0}.\nO binário Bisq que você instalou é: {1}.\nPor favor, desligue e reinstale a versão correta ({2}).
|
||||
@ -2123,18 +2131,18 @@ popup.warning.mandatoryUpdate.dao=Por favor, atualize para a versão mais recent
|
||||
popup.warning.disable.dao=A OAD do Bisq e BSQ foram temporariamente desativados. Por favor, confira o Fórum Bisq para mais informações.
|
||||
popup.warning.burnBTC=Esta transação não é possível, pois as taxas de mineração de {0} excederia o montante a transferir de {1}. Aguarde até que as taxas de mineração estejam novamente baixas ou até você ter acumulado mais 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=A transação da taxa de ofertante para a oferta com o ID {0} foi rejeitada pela rede do Bitcoin.\nID da transação={1}.\nA oferta foi removida para evitar futuros problemas.\nPor favor vá à \"Definições/Informação da Rede\" e re-sincronize o ficheiro SPV.\nPara mais ajuda por favor contacte o canal de apoio do Bisq na equipa Keybase do Bisq.
|
||||
|
||||
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.trade.txRejected=A transação de {0} para o negócio com o ID {1} foi rejeitada pela rede do Bitcoin.\nID da transação={2}}\nO negócio foi movido para negócios falahados.\nPor favor vá à \"Definições/Informação da Rede\" e re-sincronize o ficheiro SPV.\nPara mais ajuda por favor contacte o canal de apoio do Bisq na equipa Keybase do Bisq.
|
||||
|
||||
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=A transação de taxa de ofertante para a oferta com o ID {0} é inválida\nID da transação={1}.\nPor favor vá à \"Definições/Informação da Rede\" e re-sincronize o ficheiro SPV.\nPara mais ajuda por favor contacte o canal de apoio do Bisq na equipa Keybase do Bisq.
|
||||
|
||||
popup.warning.trade.depositTxNull=The trade with ID ''{0}'' has no deposit transaction set.\n\nPlease restart the application to see if the problem still exists.\n\nIf it does, please open the trade details popup by clicking on the trade ID. Then click on the transaction IDs for the maker fee transaction and the taker fee transaction to view them on a block explorer. A transaction that cannot be found in a block explorer is probably an invalid transaction.\n\nIf this happens, please report it in the #support channel on the Bisq Keybase (https://keybase.io/team/bisq). If your trade fee transaction is invalid, no funds have left your wallet, you can move the trade to failed trades,and do an SPV resync for your funds to reappear (see how below).\n\nIf your trade fee transaction is valid, the fee amount is lost, and you can make a request for reimbursement on the support repository on GitHub (https://github.com/bisq-network/support/issues).\n\nIn both cases, please do an SPV resync from the ''Settings/Network'' screen to clean your wallet of any lingering issues!
|
||||
popup.warning.trade.depositTxNull=O negócio com o ID ''{0}'' não tem transação de depósito definida.\n\nPor favor reinicie o programa para ver se o problema continua.\n\nSe continuar, por favor abra o popup de detalhes do negócio clicando no ID de negócio. De seguida, clique nos IDs da transação para a transação da taxa de ofertante e para a transação da taxa de aceitador para vê-las num explorador de blocos. Uma transação que não possa ser encontrada num explorador de blocos é provavelmente uma transação inválida.\n\nSe isto acontecer, por favor reporte-o no canal #support no Keybase do Bisq (https://keybase.io/team/bisq). Se a sua transação da taxa de negócio for inválida, nenhum dos fundos saiu da sua carteira. Você pode mover o negócio para negócios falhados e resincronizar o ficheiro SPV para que os seus fundos re-apareçam (veja como em baixo).\n\nSe a sua transação da taxa de negócio for válida, a quantia da taxa foi perdida e você pode fazer um pedido para reembolso no repositório de apoio no GitHub (https://github.com/bisq-network/support/issues).\n\nEm ambos os casos, por favor re-sincronize o ficheiro SPV na aba ''Definições/Informação da rede' para limbar a sua carteira de qualquer problema que reste!
|
||||
|
||||
popup.warning.trade.depositTxNull.moveToFailedTrades=Move to failed trades
|
||||
popup.warning.trade.depositTxNull.shutDown=Shut down Bisq
|
||||
popup.warning.trade.depositTxNull.moveToFailedTrades=Mover para negócios falhados
|
||||
popup.warning.trade.depositTxNull.shutDown=Desligar o Bisq
|
||||
|
||||
popup.info.securityDepositInfo=Para garantir que ambos os negociadores seguem o protocolo de negócio, ambos os negociadores precisam pagar um depósito de segurança.\n\nEsse depósito é mantido na sua carteira de negócio até que o seu negócio seja concluído com sucesso, e então lhe será reembolsado.\n\nPor favor note: se você está criando uma nova oferta, o Bisq precisa estar em execução para que um outro negociador a aceite. Para manter suas ofertas online, mantenha o Bisq em execução e certifique-se de que este computador permaneça online também (ou seja, certifique-se de que ele não alterne para o modo de espera... o modo de espera do monitor não causa problema).
|
||||
|
||||
@ -2148,6 +2156,7 @@ popup.securityRecommendation.headline=Recomendação de segurança importante
|
||||
popup.securityRecommendation.msg=Gostaríamos de lembrá-lo de considerar a possibilidade de usar a proteção por senha para sua carteira, caso você ainda não tenha ativado isso.\n\nTambém é altamente recomendável anotar as palavras-semente da carteira. Essas palavras-semente são como uma senha mestre para recuperar sua carteira Bitcoin.\nNa secção \"Semente da Carteira\", você encontrará mais informações.\n\nAlém disso, você deve fazer o backup da pasta completa de dados do programa na secção \"Backup\".
|
||||
|
||||
popup.bitcoinLocalhostNode.msg=O Bisq detectou um nó do Bitcoin Core em execução localmente (no localhost).\nPor favor, certifique-se de que este nó esteja totalmente sincronizado antes de iniciar o Bisq e que ele não esteja em execução no pruned mode.
|
||||
popup.bitcoinLocalhostNode.additionalRequirements=\n\nA partir do Bitcoin Core v0.19 você terá de ativar bloom filters manualmente adicionando peerbloomfilters=1 ao seu ficheiro de configuração bitcoin.conf.
|
||||
|
||||
popup.shutDownInProgress.headline=Desligando
|
||||
popup.shutDownInProgress.msg=Desligar o programa pode demorar alguns segundos.\nPor favor não interrompa este processo.
|
||||
@ -2213,7 +2222,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 decentralized bitcoin exchange network
|
||||
systemTray.tooltip=Bisq: Uma rede de echange de bitcoin descentralizada
|
||||
|
||||
|
||||
####################################################################
|
||||
@ -2237,7 +2246,7 @@ guiUtil.openWebBrowser.warning=Você vai abrir uma página web no navegador da w
|
||||
guiUtil.openWebBrowser.doOpen=Abrir a página web e não perguntar novamente
|
||||
guiUtil.openWebBrowser.copyUrl=Copiar URL e cancelar
|
||||
guiUtil.ofTradeAmount=da quantia de negócio
|
||||
guiUtil.requiredMinimum=(required minimum)
|
||||
guiUtil.requiredMinimum=(mínimo requerido)
|
||||
|
||||
####################################################################
|
||||
# Component specific
|
||||
@ -2693,3 +2702,4 @@ validation.phone.invalidCharacters=O número de telfone {0} contém carácteres
|
||||
validation.phone.insufficientDigits=Faltam algarismos em {0} para um número de telefone válido
|
||||
validation.phone.tooManyDigits=Demasiados algarismos em {0} para ser um número de telefone válido
|
||||
validation.phone.invalidDialingCode=O código de discagem do país no número {0} é inválido para o país {1}. O correcto código de discagem é {2}.
|
||||
validation.invalidAddressList=Deve ser um lista de endereços válidos separados por vírgulas
|
||||
|
||||
@ -255,7 +255,7 @@ mainView.footer.bsqInfo.synchronizing=/ Синхронизация ДАО
|
||||
mainView.footer.btcInfo.synchronizingWith=Синхронизация с
|
||||
mainView.footer.btcInfo.synchronizedWith=Синхронизировано с
|
||||
mainView.footer.btcInfo.connectingTo=Подключение к
|
||||
mainView.footer.btcInfo.connectionFailed=соединение не удалось
|
||||
mainView.footer.btcInfo.connectionFailed=Connection failed to
|
||||
mainView.footer.p2pInfo=Bisq network peers: {0}
|
||||
mainView.footer.daoFullNode=Полный узел ДАО
|
||||
|
||||
@ -601,7 +601,8 @@ portfolio.pending.step2_seller.f2fInfo.headline=Контактная инфор
|
||||
portfolio.pending.step2_seller.waitPayment.msg=Депозитная транзакция подтверждена в блокчейне не менее одного раза.\nДождитесь начала платежа в {0} покупателем BTC.
|
||||
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.refresh=Refresh Trade State
|
||||
portfolio.pending.step2_seller.refreshInfo=Sometimes P2P network messages acknowledging payment are not delivered, causing trades to get stuck. Hit the button below to make your peer resend the last message.
|
||||
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.
|
||||
@ -952,6 +953,7 @@ settings.net.warn.usePublicNodes=Если вы используете общед
|
||||
settings.net.warn.usePublicNodes.useProvided=Нет, использовать предоставленные узлы
|
||||
settings.net.warn.usePublicNodes.usePublic=Да, использовать общедоступную сеть
|
||||
settings.net.warn.useCustomNodes.B2XWarning=Убедитесь, что ваш узел Биткойн является доверенным узлом Bitcoin Core! \n\nПодключение к узлам, не следующим правилам консенсуса Bitcoin Core, может повредить ваш кошелек и вызвать проблемы в процессе торговли.\n\nПользователи, подключающиеся к узлам, нарушающим правила консенсуса, несут ответственность за любой причиненный ущерб. Любые споры в таком случае будут решаться в пользу вашего контрагента. Пользователям, игнорирующим это предупреждение и механизмы защиты, техническая поддержка предоставляться не будет!
|
||||
settings.net.warn.invalidBtcConfig=Connection to the Bitcoin network failed because your configuration is invalid.\n\nYour configuration has been reset to use the provided Bitcoin nodes instead. You will need to restart the application.
|
||||
settings.net.localhostBtcNodeInfo=(Если вы используете локальный узел Биткойн (localhost), вы можете подключаться исключительно к нему.)
|
||||
settings.net.p2PPeersLabel=Подключенные пиры
|
||||
settings.net.onionAddressColumn=Onion-адрес
|
||||
@ -1110,6 +1112,8 @@ account.altcoin.popup.pars.msg=Trading ParsiCoin on Bisq requires that you under
|
||||
|
||||
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.liquidbitcoin.msg=Trading L-BTC on Bisq requires that you understand the following:\n\nWhen receiving L-BTC for a trade on Bisq, you cannot use the mobile Blockstream Green Wallet app or a custodial/exchange wallet. You must only receive L-BTC into the Liquid Elements Core wallet, or another L-BTC wallet which allows you to obtain the blinding key for your blinded L-BTC address.\n\nIn the event mediation is necessary, or if a trade dispute arises, you must disclose the blinding key for your receiving L-BTC address to the Bisq mediator or refund agent so they can verify the details of your Confidential Transaction on their own Elements Core full node.\n\nFailure to provide the required information to the mediator or refund agent will result in losing the dispute case. In all cases of dispute, the L-BTC receiver bears 100% of the burden of responsibility in providing cryptographic proof to the mediator or refund agent.\n\nIf you do not understand these requirements, do not trade L-BTC on Bisq.
|
||||
|
||||
account.fiat.yourFiatAccounts=Ваши счета в нац. валюте
|
||||
|
||||
account.backup.title=Резервный кошелёк
|
||||
@ -1427,7 +1431,7 @@ dao.bond.table.column.bondType=Тип гарант. депозита
|
||||
dao.bond.table.column.details=Подробности
|
||||
dao.bond.table.column.lockupTxId=Идент. транз. блокировки
|
||||
dao.bond.table.column.bondState=Состояние гарант. депозита
|
||||
dao.bond.table.column.lockTime=Время блокировки
|
||||
dao.bond.table.column.lockTime=Unlock time
|
||||
dao.bond.table.column.lockupDate=Дата блокировки
|
||||
|
||||
dao.bond.table.button.lockup=Заблокировать
|
||||
@ -1850,12 +1854,16 @@ dao.factsAndFigures.dashboard.avgPrice30=30 days average BSQ/BTC trade price
|
||||
dao.factsAndFigures.dashboard.marketCap=Рыночная капитализация (на основе цены последней сделки)
|
||||
dao.factsAndFigures.dashboard.availableAmount=Доступное количество BSQ
|
||||
|
||||
dao.factsAndFigures.supply.issuedVsBurnt=BSQ issued v. BSQ burnt
|
||||
|
||||
dao.factsAndFigures.supply.issued=Эмиссия BSQ
|
||||
dao.factsAndFigures.supply.genesisIssueAmount=Эмиссия BSQ в первичной транзакции
|
||||
dao.factsAndFigures.supply.compRequestIssueAmount=Эмиссия BSQ в качестве компенсации
|
||||
dao.factsAndFigures.supply.reimbursementAmount=Эмиссия BSQ в качестве возмещения затрат
|
||||
|
||||
dao.factsAndFigures.supply.burnt=Выведено из обращения BSQ
|
||||
dao.factsAndFigures.supply.burntMovingAverage=15-day moving average
|
||||
dao.factsAndFigures.supply.burntZoomToInliers=Zoom to inliers
|
||||
|
||||
dao.factsAndFigures.supply.locked=Глобальное состояние заблокированных BSQ
|
||||
dao.factsAndFigures.supply.totalLockedUpAmount=Заблокировано в гарантийных депозитах
|
||||
@ -2148,6 +2156,7 @@ popup.securityRecommendation.headline=Важная рекомендация по
|
||||
popup.securityRecommendation.msg=Рекомендуем вам защитить свой кошелёк паролем, если вы ещё этого не сделали.\n\nТакже убедительно рекомендуем записать вашу мнемоническую фразу. Она поможет восстановить ваш кошелёк Биткойн.\nДополнительная информация указана в разделе \«Мнемоническая фраза\».\n\nВам также следует сохранить копию папки со всеми данными программы в разделе \«Резервное копирование\».
|
||||
|
||||
popup.bitcoinLocalhostNode.msg=Bisq обнаружил локальный узел Bitcoin Core.\nПеред запуском Bisq убедитесь, что этот узел полностью синхронизирован с сетью Биткойн и не работает в режиме обрезки данных (pruned mode).
|
||||
popup.bitcoinLocalhostNode.additionalRequirements=\n\nStarting with Bitcoin Core v0.19 you have to manually enable bloom filters by setting peerbloomfilters=1 in your bitcoin.conf configuration file.
|
||||
|
||||
popup.shutDownInProgress.headline=Завершение работы
|
||||
popup.shutDownInProgress.msg=Завершение работы приложения может занять несколько секунд.\nПросьба не прерывать этот процесс.
|
||||
@ -2693,3 +2702,4 @@ 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.invalidAddressList=Must be comma separated list of valid addresses
|
||||
|
||||
@ -255,7 +255,7 @@ mainView.footer.bsqInfo.synchronizing=/ Synchronizing DAO
|
||||
mainView.footer.btcInfo.synchronizingWith=Synchronizing with
|
||||
mainView.footer.btcInfo.synchronizedWith=Synchronized with
|
||||
mainView.footer.btcInfo.connectingTo=Connecting to
|
||||
mainView.footer.btcInfo.connectionFailed=การเชื่อมต่อล้มเหลว
|
||||
mainView.footer.btcInfo.connectionFailed=Connection failed to
|
||||
mainView.footer.p2pInfo=Bisq network peers: {0}
|
||||
mainView.footer.daoFullNode=DAO full node
|
||||
|
||||
@ -601,7 +601,8 @@ 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.refresh=Refresh Trade State
|
||||
portfolio.pending.step2_seller.refreshInfo=Sometimes P2P network messages acknowledging payment are not delivered, causing trades to get stuck. Hit the button below to make your peer resend the last message.
|
||||
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.
|
||||
@ -952,6 +953,7 @@ settings.net.warn.usePublicNodes=หากคุณใช้เครือข
|
||||
settings.net.warn.usePublicNodes.useProvided=ไม่ ใช้โหนดที่ให้มา
|
||||
settings.net.warn.usePublicNodes.usePublic=ใช่ ใช้เครือข่ายสาธารณะ
|
||||
settings.net.warn.useCustomNodes.B2XWarning=โปรดตรวจสอบว่าโหนด Bitcoin ของคุณเป็นโหนด Bitcoin Core ที่เชื่อถือได้!\n\nการเชื่อมต่อกับโหนดที่ไม่ปฏิบัติตามกฎกติกาการยินยอมของ Bitcoin Core อาจทำให้ wallet ของคุณเกิดปัญหาในกระบวนการทางการซื้อขายได้\n\nผู้ใช้ที่เชื่อมต่อกับโหนดที่ละเมิดกฎเป็นเอกฉันท์นั้นจำเป็นต้องรับผิดชอบต่อความเสียหายที่สร้างขึ้น ข้อพิพาทที่เกิดจากการที่จะได้รับการตัดสินใจจาก เน็ตกเวิร์ก Peer คนอื่น ๆ จะไม่มีการสนับสนุนด้านเทคนิคแก่ผู้ใช้ที่ไม่สนใจคำเตือนและกลไกการป้องกันของเรา!
|
||||
settings.net.warn.invalidBtcConfig=Connection to the Bitcoin network failed because your configuration is invalid.\n\nYour configuration has been reset to use the provided Bitcoin nodes instead. You will need to restart the application.
|
||||
settings.net.localhostBtcNodeInfo=(ข้อมูลพื้นหลัง: ถ้าคุณใช้โหนด Bitcoin ท้องถิ่น (localhost) คุณจะเชื่อมต่อกับที่นี้เท่านั้น)
|
||||
settings.net.p2PPeersLabel=เชื่อมต่อกับเน็ตเวิร์ก peers แล้ว
|
||||
settings.net.onionAddressColumn=ที่อยู่ Onion
|
||||
@ -1110,6 +1112,8 @@ account.altcoin.popup.pars.msg=Trading ParsiCoin on Bisq requires that you under
|
||||
|
||||
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.liquidbitcoin.msg=Trading L-BTC on Bisq requires that you understand the following:\n\nWhen receiving L-BTC for a trade on Bisq, you cannot use the mobile Blockstream Green Wallet app or a custodial/exchange wallet. You must only receive L-BTC into the Liquid Elements Core wallet, or another L-BTC wallet which allows you to obtain the blinding key for your blinded L-BTC address.\n\nIn the event mediation is necessary, or if a trade dispute arises, you must disclose the blinding key for your receiving L-BTC address to the Bisq mediator or refund agent so they can verify the details of your Confidential Transaction on their own Elements Core full node.\n\nFailure to provide the required information to the mediator or refund agent will result in losing the dispute case. In all cases of dispute, the L-BTC receiver bears 100% of the burden of responsibility in providing cryptographic proof to the mediator or refund agent.\n\nIf you do not understand these requirements, do not trade L-BTC on Bisq.
|
||||
|
||||
account.fiat.yourFiatAccounts=บัญชีสกุลเงินของคุณ
|
||||
|
||||
account.backup.title=สำรองข้อมูล wallet
|
||||
@ -1427,7 +1431,7 @@ dao.bond.table.column.bondType=ประเภทของการประก
|
||||
dao.bond.table.column.details=รายละเอียด
|
||||
dao.bond.table.column.lockupTxId=ล็อคการทำธุรกรรม ID
|
||||
dao.bond.table.column.bondState=สถานะการประกัน
|
||||
dao.bond.table.column.lockTime=ล็อคเวลา
|
||||
dao.bond.table.column.lockTime=Unlock time
|
||||
dao.bond.table.column.lockupDate=ล็อควันที่
|
||||
|
||||
dao.bond.table.button.lockup=ล็อค
|
||||
@ -1850,12 +1854,16 @@ dao.factsAndFigures.dashboard.avgPrice30=30 days average BSQ/BTC trade price
|
||||
dao.factsAndFigures.dashboard.marketCap=โครงสร้างเงินทุนในตลาด (ขึ้นอยู่กับราคาเทรด)
|
||||
dao.factsAndFigures.dashboard.availableAmount=BSQ ที่ใช้งานได้ทั้งหมด
|
||||
|
||||
dao.factsAndFigures.supply.issuedVsBurnt=BSQ issued v. BSQ burnt
|
||||
|
||||
dao.factsAndFigures.supply.issued=BSQ issued
|
||||
dao.factsAndFigures.supply.genesisIssueAmount=BSQ ที่ได้ดำเนินการในส่วนธุรกรรมทั่วไป
|
||||
dao.factsAndFigures.supply.compRequestIssueAmount=BSQ ที่ได้ดำเนินการสำหรับการเรียกร้องค่าชดเชย
|
||||
dao.factsAndFigures.supply.reimbursementAmount=BSQ ที่ได้ดำเนินการสำหรับการเรียกร้องการชำระเงินคืน
|
||||
|
||||
dao.factsAndFigures.supply.burnt=BSQ burnt
|
||||
dao.factsAndFigures.supply.burntMovingAverage=15-day moving average
|
||||
dao.factsAndFigures.supply.burntZoomToInliers=Zoom to inliers
|
||||
|
||||
dao.factsAndFigures.supply.locked=สถานะทั่วโลกของ BSQ ที่ล็อกไว้
|
||||
dao.factsAndFigures.supply.totalLockedUpAmount=ถูกล็อคไว้ในการประกัน
|
||||
@ -2148,6 +2156,7 @@ popup.securityRecommendation.headline=ข้อเสนอแนะด้าน
|
||||
popup.securityRecommendation.msg=เราขอแจ้งเตือนให้คุณพิจารณาใช้การป้องกันด้วยรหัสผ่านสำหรับ wallet ของคุณ หากยังไม่ได้เปิดใช้งาน\n\nขอแนะนำให้เขียนรหัสลับป้องกัน wallet รหัสลับเหล่านี้เหมือนกับรหัสผ่านหลักสำหรับการกู้คืน Bitcoin wallet ของคุณ\nไปที่ \"กระเป๋าสตางค์ \" คุณจะพบข้อมูลเพิ่มเติม\n\nนอกจากนี้คุณควรสำรองโฟลเดอร์ข้อมูลแอ็พพลิเคชั่นทั้งหมดไว้ที่ส่วน \"สำรองข้อมูล \"
|
||||
|
||||
popup.bitcoinLocalhostNode.msg=Bisq ตรวจพบเฉพาะบิตโหนดหลักของ Bitcoin ที่ใช้งานอยู่ (ที่ localhost)\nโปรดตรวจสอบว่าโหนดนี้ได้รับการซิงค์อย่างสมบูรณ์ก่อนที่คุณจะเริ่ม Bisq และไม่ได้ทำงานในโหมด pruned
|
||||
popup.bitcoinLocalhostNode.additionalRequirements=\n\nStarting with Bitcoin Core v0.19 you have to manually enable bloom filters by setting peerbloomfilters=1 in your bitcoin.conf configuration file.
|
||||
|
||||
popup.shutDownInProgress.headline=การปิดระบบอยู่ระหว่างดำเนินการ
|
||||
popup.shutDownInProgress.msg=การปิดแอพพลิเคชั่นอาจใช้เวลาสักครู่\nโปรดอย่าขัดจังหวะกระบวนการนี้
|
||||
@ -2693,3 +2702,4 @@ 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.invalidAddressList=Must be comma separated list of valid addresses
|
||||
|
||||
@ -255,7 +255,7 @@ mainView.footer.bsqInfo.synchronizing=/ Đang đồng bộ hóa DAO
|
||||
mainView.footer.btcInfo.synchronizingWith=Synchronizing with
|
||||
mainView.footer.btcInfo.synchronizedWith=Đã đồng bộ hóa với
|
||||
mainView.footer.btcInfo.connectingTo=Đang kết nối với
|
||||
mainView.footer.btcInfo.connectionFailed=không kết nối được
|
||||
mainView.footer.btcInfo.connectionFailed=Connection failed to
|
||||
mainView.footer.p2pInfo=Bisq network peers: {0}
|
||||
mainView.footer.daoFullNode=Full node DAO
|
||||
|
||||
@ -601,7 +601,8 @@ portfolio.pending.step2_seller.f2fInfo.headline=Thông tin liên lạc của ng
|
||||
portfolio.pending.step2_seller.waitPayment.msg=Giao dịch đặt cọc có ít nhất một xác nhận blockchain.\nBạn cần phải đợi cho đến khi người mua BTC bắt đầu thanh toán {0}.
|
||||
portfolio.pending.step2_seller.warn=Người mua BTC vẫn chưa thanh toán {0}.\nBạn cần phải đợi cho đến khi người mua bắt đầu thanh toán.\nNếu giao dịch không được hoàn thành vào {1} trọng tài sẽ điều tra.
|
||||
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.refresh=Refresh Trade State
|
||||
portfolio.pending.step2_seller.refreshInfo=Sometimes P2P network messages acknowledging payment are not delivered, causing trades to get stuck. Hit the button below to make your peer resend the last message.
|
||||
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.
|
||||
@ -952,6 +953,7 @@ settings.net.warn.usePublicNodes=Nếu bạn sử dụng mạng Bitcoin công c
|
||||
settings.net.warn.usePublicNodes.useProvided=Không, sử dụng nút được cung cấp
|
||||
settings.net.warn.usePublicNodes.usePublic=Vâng, sử dụng nút công cộng
|
||||
settings.net.warn.useCustomNodes.B2XWarning=Vui lòng chắc chắn rằng nút Bitcoin của bạn là nút Bitcoin Core đáng tin cậy!\n\nKết nối với nút không tuân thủ nguyên tắc đồng thuận Bitcoin Core có thể làm hỏng ví của bạn và gây ra các vấn đề trong quá trình giao dịch.\n\nNgười dùng kết nối với nút vi phạm nguyên tắc đồng thuận chịu trách nhiệm đối với các thiệt hại mà việc này gây ra. Các khiếu nại do điều này gây ra sẽ được quyết định theo hướng có lợi cho đối tác bên kia. Sẽ không có hỗ trợ về mặt kỹ thuật nào cho người dùng không tuân thủ cơ chế cảnh báo và bảo vệ của chúng tôi!
|
||||
settings.net.warn.invalidBtcConfig=Connection to the Bitcoin network failed because your configuration is invalid.\n\nYour configuration has been reset to use the provided Bitcoin nodes instead. You will need to restart the application.
|
||||
settings.net.localhostBtcNodeInfo=(Thông tin cơ sở: Nếu bạn đang chạy nút Bitcoin nội bộ (máy chủ nội bộ) bạn có thể kết nối độc quyền với nút này.)
|
||||
settings.net.p2PPeersLabel=Các đối tác được kết nối
|
||||
settings.net.onionAddressColumn=Địa chỉ onion
|
||||
@ -1110,6 +1112,8 @@ account.altcoin.popup.pars.msg=Trading ParsiCoin on Bisq requires that you under
|
||||
|
||||
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.liquidbitcoin.msg=Trading L-BTC on Bisq requires that you understand the following:\n\nWhen receiving L-BTC for a trade on Bisq, you cannot use the mobile Blockstream Green Wallet app or a custodial/exchange wallet. You must only receive L-BTC into the Liquid Elements Core wallet, or another L-BTC wallet which allows you to obtain the blinding key for your blinded L-BTC address.\n\nIn the event mediation is necessary, or if a trade dispute arises, you must disclose the blinding key for your receiving L-BTC address to the Bisq mediator or refund agent so they can verify the details of your Confidential Transaction on their own Elements Core full node.\n\nFailure to provide the required information to the mediator or refund agent will result in losing the dispute case. In all cases of dispute, the L-BTC receiver bears 100% of the burden of responsibility in providing cryptographic proof to the mediator or refund agent.\n\nIf you do not understand these requirements, do not trade L-BTC on Bisq.
|
||||
|
||||
account.fiat.yourFiatAccounts=Các tài khoản tiền tệ quốc gia của bạn
|
||||
|
||||
account.backup.title=Ví dự phòng
|
||||
@ -1427,7 +1431,7 @@ dao.bond.table.column.bondType=Loại tài sản đảm bảo
|
||||
dao.bond.table.column.details=Thông tin chi tiết
|
||||
dao.bond.table.column.lockupTxId=Mã giao dịch khóa
|
||||
dao.bond.table.column.bondState=Trạng thái tài sản đảm bảo
|
||||
dao.bond.table.column.lockTime=Thời gian khóa
|
||||
dao.bond.table.column.lockTime=Unlock time
|
||||
dao.bond.table.column.lockupDate=Ngày khóa
|
||||
|
||||
dao.bond.table.button.lockup=Khóa
|
||||
@ -1850,12 +1854,16 @@ dao.factsAndFigures.dashboard.avgPrice30=30 days average BSQ/BTC trade price
|
||||
dao.factsAndFigures.dashboard.marketCap=Vốn hóa thị trường (dựa trên giá giao dịch)
|
||||
dao.factsAndFigures.dashboard.availableAmount=Tổng lượng BSQ hiện có
|
||||
|
||||
dao.factsAndFigures.supply.issuedVsBurnt=BSQ issued v. BSQ burnt
|
||||
|
||||
dao.factsAndFigures.supply.issued=BSQ đã phát hành
|
||||
dao.factsAndFigures.supply.genesisIssueAmount=Lượng BSQ phát hành tại giao dịch Genesis
|
||||
dao.factsAndFigures.supply.compRequestIssueAmount=Lượng BSQ phát hành dành cho yêu cầu bồi thường
|
||||
dao.factsAndFigures.supply.reimbursementAmount=Lượng BSQ phát hành dành cho yêu cầu bồi hoàn
|
||||
|
||||
dao.factsAndFigures.supply.burnt=BSQ đã đốt
|
||||
dao.factsAndFigures.supply.burntMovingAverage=15-day moving average
|
||||
dao.factsAndFigures.supply.burntZoomToInliers=Zoom to inliers
|
||||
|
||||
dao.factsAndFigures.supply.locked=Trạng thái toàn cầu của BSQ đã khóa
|
||||
dao.factsAndFigures.supply.totalLockedUpAmount=Bị khóa làm tải sản đảm bảo
|
||||
@ -2148,6 +2156,7 @@ popup.securityRecommendation.headline=Khuyến cáo an ninh quan trọng
|
||||
popup.securityRecommendation.msg=Chúng tôi muốn nhắc nhở bạn sử dụng bảo vệ bằng mật khẩu cho ví của bạn nếu bạn vẫn chưa sử dụng.\n\nChúng tôi cũng khuyên bạn nên viết Seed words ví của bạn ra giấy. Các Seed words này như là mật khẩu chủ để khôi phục ví Bitcoin của bạn.\nBạn có thể xem thông tin ở mục \"Wallet Seed\".\n\nNgoài ra bạn nên sao lưu dự phòng folder dữ liệu ứng dụng đầy đủ ở mục \"Backup\".
|
||||
|
||||
popup.bitcoinLocalhostNode.msg=Bisq phát hiện Node Bitcoin Core đang chạy (ở máy chủ cục bộ).\nHãy chắc chắn rằng Node này đã được đồng bộ hóa hoàn toàn trước khi bạn khởi động Bisq và không chạy trong chế độ pruning.
|
||||
popup.bitcoinLocalhostNode.additionalRequirements=\n\nStarting with Bitcoin Core v0.19 you have to manually enable bloom filters by setting peerbloomfilters=1 in your bitcoin.conf configuration file.
|
||||
|
||||
popup.shutDownInProgress.headline=Đang tắt ứng dụng
|
||||
popup.shutDownInProgress.msg=Tắt ứng dụng sẽ mất vài giây.\nVui lòng không gián đoạn quá trình này.
|
||||
@ -2693,3 +2702,4 @@ 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.invalidAddressList=Must be comma separated list of valid addresses
|
||||
|
||||
@ -255,7 +255,7 @@ mainView.footer.bsqInfo.synchronizing=正在同步 DAO
|
||||
mainView.footer.btcInfo.synchronizingWith=正在同步至
|
||||
mainView.footer.btcInfo.synchronizedWith=已同步至
|
||||
mainView.footer.btcInfo.connectingTo=连接至
|
||||
mainView.footer.btcInfo.connectionFailed=连接失败
|
||||
mainView.footer.btcInfo.connectionFailed=Connection failed to
|
||||
mainView.footer.p2pInfo=Bisq 网络对等点：{0}
|
||||
mainView.footer.daoFullNode=DAO 全节点
|
||||
|
||||
@ -601,7 +601,8 @@ 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=BTC 买家尚未开始付款！\n最大允许的交易期限已经过去了。\n你可以继续等待给予交易双方更多时间，或联系仲裁员以争取解决纠纷。
|
||||
|
||||
portfolio.pending.step2_seller.refresh=Refresh Trade State
|
||||
portfolio.pending.step2_seller.refreshInfo=Sometimes P2P network messages acknowledging payment are not delivered, causing trades to get stuck. Hit the button below to make your peer resend the last message.
|
||||
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●保持友好和尊重的交谈。
|
||||
@ -919,7 +920,7 @@ setting.preferences.addAltcoin=添加数字货币
|
||||
setting.preferences.displayOptions=显示选项
|
||||
setting.preferences.showOwnOffers=在委托列表中显示我的委托
|
||||
setting.preferences.useAnimations=使用动画
|
||||
setting.preferences.useDarkMode=使用夜间模式（beta）
|
||||
setting.preferences.useDarkMode=Use dark mode
|
||||
setting.preferences.sortWithNumOffers=使用“委托ID/交易ID”筛选列表
|
||||
setting.preferences.resetAllFlags=重置所有“不再提示”的提示
|
||||
setting.preferences.reset=重置
|
||||
@ -952,6 +953,7 @@ settings.net.warn.usePublicNodes=如果你使用公共比特币网络，你就
|
||||
settings.net.warn.usePublicNodes.useProvided=不，使用给定的节点
|
||||
settings.net.warn.usePublicNodes.usePublic=使用公共网络
|
||||
settings.net.warn.useCustomNodes.B2XWarning=请确保您的比特币节点是一个可信的比特币核心节点！\n\n连接到不遵循比特币核心共识规则的节点可能会损坏您的钱包，并在交易过程中造成问题。\n\n连接到违反共识规则的节点的用户应对任何由此造成的损害负责。任何由此产生的纠纷都将有利于另一方。对于忽略此警告和保护机制的用户，不提供任何技术支持！
|
||||
settings.net.warn.invalidBtcConfig=Connection to the Bitcoin network failed because your configuration is invalid.\n\nYour configuration has been reset to use the provided Bitcoin nodes instead. You will need to restart the application.
|
||||
settings.net.localhostBtcNodeInfo=（背景信息：如果您正在运行一个本地比特币节点（本地主机），您可以只连接到它。）
|
||||
settings.net.p2PPeersLabel=已连接节点
|
||||
settings.net.onionAddressColumn=匿名地址
|
||||
@ -1110,6 +1112,8 @@ account.altcoin.popup.pars.msg=在 Bisq 上交易 ParsiCoin 需要您了解并
|
||||
|
||||
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.altcoin.popup.liquidbitcoin.msg=Trading L-BTC on Bisq requires that you understand the following:\n\nWhen receiving L-BTC for a trade on Bisq, you cannot use the mobile Blockstream Green Wallet app or a custodial/exchange wallet. You must only receive L-BTC into the Liquid Elements Core wallet, or another L-BTC wallet which allows you to obtain the blinding key for your blinded L-BTC address.\n\nIn the event mediation is necessary, or if a trade dispute arises, you must disclose the blinding key for your receiving L-BTC address to the Bisq mediator or refund agent so they can verify the details of your Confidential Transaction on their own Elements Core full node.\n\nFailure to provide the required information to the mediator or refund agent will result in losing the dispute case. In all cases of dispute, the L-BTC receiver bears 100% of the burden of responsibility in providing cryptographic proof to the mediator or refund agent.\n\nIf you do not understand these requirements, do not trade L-BTC on Bisq.
|
||||
|
||||
account.fiat.yourFiatAccounts=您的法定货币账户
|
||||
|
||||
account.backup.title=备份钱包
|
||||
@ -1427,7 +1431,7 @@ dao.bond.table.column.bondType=连接类型
|
||||
dao.bond.table.column.details=详情
|
||||
dao.bond.table.column.lockupTxId=锁定 Tx ID
|
||||
dao.bond.table.column.bondState=连接状态
|
||||
dao.bond.table.column.lockTime=锁定时间
|
||||
dao.bond.table.column.lockTime=Unlock time
|
||||
dao.bond.table.column.lockupDate=锁定日期
|
||||
|
||||
dao.bond.table.button.lockup=锁定
|
||||
@ -1850,12 +1854,16 @@ dao.factsAndFigures.dashboard.avgPrice30=30天平均 BSQ/BTC 交易价格
|
||||
dao.factsAndFigures.dashboard.marketCap=市值（基于市场价）
|
||||
dao.factsAndFigures.dashboard.availableAmount=总共可用的 BSQ
|
||||
|
||||
dao.factsAndFigures.supply.issuedVsBurnt=BSQ issued v. BSQ burnt
|
||||
|
||||
dao.factsAndFigures.supply.issued=有问题的 BSQ
|
||||
dao.factsAndFigures.supply.genesisIssueAmount=在初始交易中心有问题的 BSQ
|
||||
dao.factsAndFigures.supply.compRequestIssueAmount=所有有问题的 BSQ 报偿请求
|
||||
dao.factsAndFigures.supply.reimbursementAmount=所有有问题的 BSQ 退还申请
|
||||
|
||||
dao.factsAndFigures.supply.burnt=BSQ 烧毁总量
|
||||
dao.factsAndFigures.supply.burntMovingAverage=15-day moving average
|
||||
dao.factsAndFigures.supply.burntZoomToInliers=Zoom to inliers
|
||||
|
||||
dao.factsAndFigures.supply.locked=BSQ 全局锁定状态
|
||||
dao.factsAndFigures.supply.totalLockedUpAmount=担保的锁定
|
||||
@ -2148,6 +2156,7 @@ popup.securityRecommendation.headline=重要安全建议
|
||||
popup.securityRecommendation.msg=如果您还没有启用，我们想提醒您考虑为您的钱包使用密码保护。\n\n强烈建议你写下钱包还原密钥。 那些还原密钥就是恢复你的比特币钱包的主密码。\n在“钱包密钥”部分，您可以找到更多信息\n\n此外，您应该在“备份”界面备份完整的应用程序数据文件夹。
|
||||
|
||||
popup.bitcoinLocalhostNode.msg=Bisq 检测到一个本地运行的比特币核心节点（在本地主机）。\n在启动 Bisq 之前，请确保此节点已完全同步，并且没有在删除模式下运行。
|
||||
popup.bitcoinLocalhostNode.additionalRequirements=\n\nStarting with Bitcoin Core v0.19 you have to manually enable bloom filters by setting peerbloomfilters=1 in your bitcoin.conf configuration file.
|
||||
|
||||
popup.shutDownInProgress.headline=正在关闭
|
||||
popup.shutDownInProgress.msg=关闭应用可能会花一点时间。\n请不要打断关闭过程。
|
||||
@ -2693,3 +2702,4 @@ validation.phone.invalidCharacters=电话号码 {0} 包含无效字符
|
||||
validation.phone.insufficientDigits={0} 中没有足够的数字作为有效的电话号码
|
||||
validation.phone.tooManyDigits={0} 中的数字太多，不是有效的电话号码
|
||||
validation.phone.invalidDialingCode=数字 {0} 中的国际拨号代码对于 {1} 无效。正确的拨号号码是 {2} 。
|
||||
validation.invalidAddressList=Must be comma separated list of valid addresses
|
||||
|
||||
@ -255,7 +255,7 @@ mainView.footer.bsqInfo.synchronizing=正在同步 DAO
|
||||
mainView.footer.btcInfo.synchronizingWith=正在同步至
|
||||
mainView.footer.btcInfo.synchronizedWith=已同步至
|
||||
mainView.footer.btcInfo.connectingTo=連線至
|
||||
mainView.footer.btcInfo.connectionFailed=連線失敗
|
||||
mainView.footer.btcInfo.connectionFailed=Connection failed to
|
||||
mainView.footer.p2pInfo=Bisq 網路對等點：{0}
|
||||
mainView.footer.daoFullNode=DAO 全節點
|
||||
|
||||
@ -601,7 +601,8 @@ 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=BTC 買家尚未開始付款！\n最大允許的交易期限已經過去了。\n你可以繼續等待給予交易雙方更多時間，或聯絡仲裁員以爭取解決糾紛。
|
||||
|
||||
portfolio.pending.step2_seller.refresh=Refresh Trade State
|
||||
portfolio.pending.step2_seller.refreshInfo=Sometimes P2P network messages acknowledging payment are not delivered, causing trades to get stuck. Hit the button below to make your peer resend the last message.
|
||||
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●保持友好和尊重的交談。
|
||||
@ -919,7 +920,7 @@ setting.preferences.addAltcoin=新增數字貨幣
|
||||
setting.preferences.displayOptions=顯示選項
|
||||
setting.preferences.showOwnOffers=在委託列表中顯示我的委託
|
||||
setting.preferences.useAnimations=使用動畫
|
||||
setting.preferences.useDarkMode=使用夜間模式（beta）
|
||||
setting.preferences.useDarkMode=Use dark mode
|
||||
setting.preferences.sortWithNumOffers=使用“委託ID/交易ID”篩選列表
|
||||
setting.preferences.resetAllFlags=重置所有“不再提示”的提示
|
||||
setting.preferences.reset=重置
|
||||
@ -952,6 +953,7 @@ settings.net.warn.usePublicNodes=如果你使用公共比特幣網路，你就
|
||||
settings.net.warn.usePublicNodes.useProvided=不，使用給定的節點
|
||||
settings.net.warn.usePublicNodes.usePublic=使用公共網路
|
||||
settings.net.warn.useCustomNodes.B2XWarning=請確保您的比特幣節點是一個可信的比特幣核心節點！\n\n連線到不遵循比特幣核心共識規則的節點可能會損壞您的錢包，並在交易過程中造成問題。\n\n連線到違反共識規則的節點的使用者應對任何由此造成的損害負責。任何由此產生的糾紛都將有利於另一方。對於忽略此警告和保護機制的使用者，不提供任何技術支援！
|
||||
settings.net.warn.invalidBtcConfig=Connection to the Bitcoin network failed because your configuration is invalid.\n\nYour configuration has been reset to use the provided Bitcoin nodes instead. You will need to restart the application.
|
||||
settings.net.localhostBtcNodeInfo=（背景資訊：如果您正在執行一個本地比特幣節點（本地主機），您可以只連線到它。）
|
||||
settings.net.p2PPeersLabel=已連線節點
|
||||
settings.net.onionAddressColumn=匿名地址
|
||||
@ -1110,6 +1112,8 @@ account.altcoin.popup.pars.msg=在 Bisq 上交易 ParsiCoin 需要您瞭解並
|
||||
|
||||
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.altcoin.popup.liquidbitcoin.msg=Trading L-BTC on Bisq requires that you understand the following:\n\nWhen receiving L-BTC for a trade on Bisq, you cannot use the mobile Blockstream Green Wallet app or a custodial/exchange wallet. You must only receive L-BTC into the Liquid Elements Core wallet, or another L-BTC wallet which allows you to obtain the blinding key for your blinded L-BTC address.\n\nIn the event mediation is necessary, or if a trade dispute arises, you must disclose the blinding key for your receiving L-BTC address to the Bisq mediator or refund agent so they can verify the details of your Confidential Transaction on their own Elements Core full node.\n\nFailure to provide the required information to the mediator or refund agent will result in losing the dispute case. In all cases of dispute, the L-BTC receiver bears 100% of the burden of responsibility in providing cryptographic proof to the mediator or refund agent.\n\nIf you do not understand these requirements, do not trade L-BTC on Bisq.
|
||||
|
||||
account.fiat.yourFiatAccounts=您的法定貨幣賬戶
|
||||
|
||||
account.backup.title=備份錢包
|
||||
@ -1427,7 +1431,7 @@ dao.bond.table.column.bondType=連線類型
|
||||
dao.bond.table.column.details=詳情
|
||||
dao.bond.table.column.lockupTxId=鎖定 Tx ID
|
||||
dao.bond.table.column.bondState=連線狀態
|
||||
dao.bond.table.column.lockTime=鎖定時間
|
||||
dao.bond.table.column.lockTime=Unlock time
|
||||
dao.bond.table.column.lockupDate=鎖定日期
|
||||
|
||||
dao.bond.table.button.lockup=鎖定
|
||||
@ -1850,12 +1854,16 @@ dao.factsAndFigures.dashboard.avgPrice30=30天平均 BSQ/BTC 交易價格
|
||||
dao.factsAndFigures.dashboard.marketCap=市值（基於市場價）
|
||||
dao.factsAndFigures.dashboard.availableAmount=總共可用的 BSQ
|
||||
|
||||
dao.factsAndFigures.supply.issuedVsBurnt=BSQ issued v. BSQ burnt
|
||||
|
||||
dao.factsAndFigures.supply.issued=有問題的 BSQ
|
||||
dao.factsAndFigures.supply.genesisIssueAmount=在初始交易中心有問題的 BSQ
|
||||
dao.factsAndFigures.supply.compRequestIssueAmount=所有有問題的 BSQ 報償請求
|
||||
dao.factsAndFigures.supply.reimbursementAmount=所有有問題的 BSQ 退還申請
|
||||
|
||||
dao.factsAndFigures.supply.burnt=BSQ 燒燬總量
|
||||
dao.factsAndFigures.supply.burntMovingAverage=15-day moving average
|
||||
dao.factsAndFigures.supply.burntZoomToInliers=Zoom to inliers
|
||||
|
||||
dao.factsAndFigures.supply.locked=BSQ 全局鎖定狀態
|
||||
dao.factsAndFigures.supply.totalLockedUpAmount=擔保的鎖定
|
||||
@ -2148,6 +2156,7 @@ popup.securityRecommendation.headline=重要安全建議
|
||||
popup.securityRecommendation.msg=如果您還沒有啟用，我們想提醒您考慮為您的錢包使用密碼保護。\n\n強烈建議你寫下錢包還原金鑰。 那些還原金鑰就是恢復你的比特幣錢包的主密碼。\n在“錢包金鑰”部分，您可以找到更多資訊\n\n此外，您應該在“備份”介面備份完整的應用程式資料資料夾。
|
||||
|
||||
popup.bitcoinLocalhostNode.msg=Bisq 檢測到一個本地執行的比特幣核心節點（在本地主機）。\n在啟動 Bisq 之前，請確保此節點已完全同步，並且沒有在刪除模式下執行。
|
||||
popup.bitcoinLocalhostNode.additionalRequirements=\n\nStarting with Bitcoin Core v0.19 you have to manually enable bloom filters by setting peerbloomfilters=1 in your bitcoin.conf configuration file.
|
||||
|
||||
popup.shutDownInProgress.headline=正在關閉
|
||||
popup.shutDownInProgress.msg=關閉應用可能會花一點時間。\n請不要打斷關閉過程。
|
||||
@ -2693,3 +2702,4 @@ validation.phone.invalidCharacters=電話號碼 {0} 包含無效字元
|
||||
validation.phone.insufficientDigits={0} 中沒有足夠的數字作為有效的電話號碼
|
||||
validation.phone.tooManyDigits={0} 中的數字太多，不是有效的電話號碼
|
||||
validation.phone.invalidDialingCode=數字 {0} 中的國家或地區撥號程式碼對於 {1} 無效。正確的撥號號碼是 {2} 。
|
||||
validation.invalidAddressList=Must be comma separated list of valid addresses
|
||||
|
||||
@ -8,7 +8,7 @@
|
||||
|
||||
# pull base image
|
||||
FROM openjdk:8-jdk
|
||||
ENV version 1.2.5-SNAPSHOT
|
||||
ENV version 1.2.6
|
||||
|
||||
RUN apt-get update && apt-get install -y --no-install-recommends openjfx && rm -rf /var/lib/apt/lists/* &&
|
||||
apt-get install -y vim fakeroot
|
||||
|
||||
@ -6,7 +6,7 @@
|
||||
# - Update version below
|
||||
# - Ensure JAVA_HOME below is pointing to OracleJDK 10 directory
|
||||
|
||||
version=1.2.5-SNAPSHOT
|
||||
version=1.2.6
|
||||
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
|
||||
|
||||
@ -4,7 +4,7 @@
|
||||
# Prior to running this script:
|
||||
# - Update version below
|
||||
|
||||
version=1.2.5-SNAPSHOT
|
||||
version=1.2.6
|
||||
base_dir=$( cd "$(dirname "$0")" ; pwd -P )/../../..
|
||||
package_dir=$base_dir/desktop/package
|
||||
release_dir=$base_dir/desktop/release/$version
|
||||
|
||||
@ -5,10 +5,10 @@
|
||||
<!-- See: https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html -->
|
||||
|
||||
<key>CFBundleVersion</key>
|
||||
<string>1.2.5</string>
|
||||
<string>1.2.6</string>
|
||||
|
||||
<key>CFBundleShortVersionString</key>
|
||||
<string>1.2.5</string>
|
||||
<string>1.2.6</string>
|
||||
|
||||
<key>CFBundleExecutable</key>
|
||||
<string>Bisq</string>
|
||||
|
||||
@ -6,7 +6,7 @@ mkdir -p deploy
|
||||
|
||||
set -e
|
||||
|
||||
version="1.2.5-SNAPSHOT"
|
||||
version="1.2.6"
|
||||
|
||||
cd ..
|
||||
./gradlew :desktop:build -x test shadowJar
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
|
||||
cd ../../
|
||||
|
||||
version="1.2.5-SNAPSHOT"
|
||||
version="1.2.6"
|
||||
|
||||
target_dir="releases/$version"
|
||||
|
||||
|
||||
@ -2,8 +2,8 @@
|
||||
|
||||
cd $(dirname $0)/../../../
|
||||
|
||||
oldVersion=1.2.4
|
||||
newVersion=1.2.5
|
||||
oldVersion=1.2.5
|
||||
newVersion=1.2.6
|
||||
|
||||
find . -type f \( -name "finalize.sh" \
|
||||
-o -name "create_app.sh" \
|
||||
|
||||
@ -11,7 +11,7 @@
|
||||
|
||||
@echo off
|
||||
|
||||
set version=1.2.5-SNAPSHOT
|
||||
set version=1.2.6
|
||||
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.
|
||||
@ -119,7 +119,7 @@ if not exist "%package_dir%\windows\Bisq-%version%.exe" (
|
||||
)
|
||||
|
||||
echo Signing executable with default Code Signing Certificate
|
||||
call "C:\Program Files (x86)\Windows Kits\10\App Certification Kit\signtool.exe" sign /v /fd SHA256 /a "Bisq-%version%.exe"
|
||||
call "C:\Program Files (x86)\Windows Kits\10\App Certification Kit\signtool.exe" sign /v /fd SHA256 /a "%package_dir%\windows\Bisq-%version%.exe"
|
||||
|
||||
echo SHA256 of %package_dir%\windows\Bisq-%version%.exe:
|
||||
for /F "delims=" %%h in ('certutil -hashfile "%package_dir%\windows\Bisq-%version%.exe" SHA256 ^| findstr -i -v "SHA256" ^| findstr -i -v "certutil"') do (set hash=%%h)
|
||||
|
||||
@ -6,7 +6,7 @@
|
||||
|
||||
@echo off
|
||||
|
||||
set version=1.2.5-SNAPSHOT
|
||||
set version=1.2.6
|
||||
set release_dir=%~dp0..\..\..\releases\%version%
|
||||
set package_dir=%~dp0..
|
||||
|
||||
|
||||
@ -1 +1 @@
|
||||
1.2.5-SNAPSHOT
|
||||
1.2.6
|
||||
|
||||
@ -26,13 +26,11 @@ import bisq.common.app.Capabilities;
|
||||
import bisq.common.app.Capability;
|
||||
import bisq.common.setup.CommonSetup;
|
||||
|
||||
import joptsimple.OptionSet;
|
||||
|
||||
import lombok.extern.slf4j.Slf4j;
|
||||
|
||||
@Slf4j
|
||||
public class SeedNodeMain extends ExecutableForAppWithP2p {
|
||||
private static final String VERSION = "1.2.5";
|
||||
private static final String VERSION = "1.2.6";
|
||||
private SeedNode seedNode;
|
||||
|
||||
public SeedNodeMain() {
|
||||
|
||||
Loading…
Reference in New Issue
Block a user