mirrors/bisq
1
0
Fork 0
mirror of https://github.com/bisq-network/bisq.git synced 2025-02-23 23:06:39 +01:00
Code Issues Projects Releases Packages Wiki Activity

Merge branch 'master' of https://github.com/bisq-network/bisq into rpm-package

Browse source 
# Conflicts:
#	desktop/package/linux/package.sh
#	desktop/package/linux/rpm.sh
This commit is contained in:
Devin Bileck 2019-01-08 09:26:43 -08:00
commit 24ecbcdfb3
No known key found for this signature in database
GPG key ID: 38750B26EA8B8C93
52 changed files with 1574 additions and 1242 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

106
assets/src/main/java/bisq/asset/GrinAddressValidator.java Normal file
View file

@ -0,0 +1,106 @@
/*
* 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;
/**
* The supported "address" (better wallet URL) format is IP:port or the grinbox format.
*
* Here is the information from a conversation with the Grinbox developer regarding the Grinbox address format.
*
A Grinbox address is of the format: grinbox://<key>@domain.com:port where everything besides <key> is optional.
If no domain is specified, the default relay grinbox.io will be used.
The <key> is a base58check encoded value (like in Bitcoin). For Grin mainnet, the first 2 bytes will be [1, 11] and
the following 33 bytes should be a valid secp256k1 compressed public key.
Some examples of valid addresses are:
gVvRNiuopubvxPrs1BzJdQjVdFAxmkLzMqiVJzUZ7ubznhdtNTGB
gVvUcSafSTD3YTSqgNf9ojEYWkz3zMZNfsjdpdb9en5mxc6gmja6
gVvk7rLBg3r3qoWYL3VsREnBbooT7nynxx5HtDvUWCJUaNCnddvY
grinbox://gVtWzX5NTLCBkyNV19QVdnLXue13heAVRD36sfkGD6xpqy7k7e4a
gVw9TWimGFXRjoDXWhWxeNQbu84ZpLkvnenkKvA5aJeDo31eM5tC@somerelay.com
grinbox://gVwjSsYW5vvHpK4AunJ5piKhhQTV6V3Jb818Uqs6PdC3SsB36AsA@somerelay.com:1220
Some examples of invalid addresses are:
gVuBJDKcWkhueMfBLAbFwV4ax55YXPeinWXdRME1Zi3eiC6sFNye (invalid checksum)
geWGCMQjxZMHG3EtTaRbR7rH9rE4DsmLfpm1iiZEa7HFKjjkgpf2 (wrong version bytes)
gVvddC2jYAfxTxnikcbTEQKLjhJZpqpBg39tXkwAKnD2Pys2mWiK (invalid public key)
We only add the basic validation without checksum, version byte and pubkey validation as that would require much more
effort. Any Grin developer is welcome to add that though!
*/
public class GrinAddressValidator implements AddressValidator {
// A Grin Wallet URL (address is not the correct term) can be in the form IP:port or a grinbox format.
// The grinbox has the format grinbox://<key>@domain.com:port where everything beside the key is optional.
// Regex for IP validation borrowed from https://stackoverflow.com/questions/53497/regular-expression-that-matches-valid-ipv6-addresses
private static final String IPV4 = "((25[0-5]|(2[0-4]|1{0,1}[0-9]){0,1}[0-9])\\.){3,3}(25[0-5]|(2[0-4]|1{0,1}[0-9]){0,1}[0-9])";
private static final String PORT = "((6553[0-5])|(655[0-2][0-9])|(65[0-4][0-9]{2})|(6[0-4][0-9]{3})|([1-5][0-9]{4})|([0-5]{0,5})|([0-9]{1,4}))$";
private static final String DOMAIN = "[a-zA-Z0-9][a-zA-Z0-9-]{1,61}[a-zA-Z0-9]\\.[a-zA-Z]{2,}$";
private static final String KEY = "[a-km-zA-HJ-NP-Z1-9]{52}$";
public GrinAddressValidator() {
}
@Override
public AddressValidationResult validate(String address) {
if (address == null || address.length() == 0)
return AddressValidationResult.invalidAddress("Address may not be empty");
if (address.matches("^" + IPV4 + ":" + PORT))
return AddressValidationResult.validAddress();
// We might have a grinbox address
String key;
String domain = null;
String port = null;
address = address.replace("grinbox://", "");
if (address.contains("@")) {
String[] keyAndDomain = address.split("@");
key = keyAndDomain[0];
if (keyAndDomain.length > 1) {
domain = keyAndDomain[1];
if (domain.contains(":")) {
String[] domainAndPort = domain.split(":");
domain = domainAndPort[0];
if (domainAndPort.length > 1)
port = domainAndPort[1];
}
}
} else {
key = address;
}
if (!key.matches("^" + KEY))
return AddressValidationResult.invalidAddress("Invalid key");
if (domain != null && !domain.matches("^" + DOMAIN))
return AddressValidationResult.invalidAddress("Invalid domain");
if (port != null && !port.matches("^" + PORT))
return AddressValidationResult.invalidAddress("Invalid port");
return AddressValidationResult.validAddress();
}
}

37
assets/src/main/java/bisq/asset/coins/Beam.java Normal file
View file

@ -0,0 +1,37 @@
/*
* 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.Coin;
import bisq.asset.RegexAddressValidator;
/**
* Here is info from a Beam developer regarding validation.
*
* Well, unfortunately the range length is quite large. The BbsChannel is 64 bit = 8 bytes, the pubkey is 32 bytes.
* So, the length may be up to 80 chars. The minimum length "theoretically" can also drop to a small length, if the
* channel==0, and the pubkey starts with many zeroes (very unlikely, but possible). So, besides being up to 80 chars
* lower-case hex there's not much can be tested. A more robust test would also check if the pubkey is indeed valid,
* but it's a more complex test, requiring cryptographic code.
*
*/
public class Beam extends Coin {
public Beam() {
super("Beam", "BEAM", new RegexAddressValidator("^([0-9a-f]{1,80})$"));
}
}

8
assets/src/main/java/bisq/asset/coins/BitcoinClashic.java → assets/src/main/java/bisq/asset/coins/Grin.java
View file

@ -17,12 +17,12 @@
package bisq.asset.coins;
import bisq.asset.Base58BitcoinAddressValidator;
import bisq.asset.Coin;
import bisq.asset.GrinAddressValidator;
public class BitcoinClashic extends Coin {
public class Grin extends Coin {
public BitcoinClashic() {
super("Bitcoin Clashic", "BCHC", new Base58BitcoinAddressValidator());
public Grin() {
super("Grin", "GRIN", new GrinAddressValidator());
}
}

3
assets/src/main/resources/META-INF/services/bisq.asset.Asset
View file

@ -4,7 +4,7 @@
# See https://bisq.network/list-asset for complete instructions.
bisq.asset.coins.Actinium
bisq.asset.coins.Aeon
bisq.asset.coins.BitcoinClashic
bisq.asset.coins.Beam
bisq.asset.coins.BitcoinRhodium
bisq.asset.coins.Bitcoin$Mainnet
bisq.asset.coins.Bitcoin$Regtest
@ -26,6 +26,7 @@ bisq.asset.coins.Dragonglass
bisq.asset.coins.Ether
bisq.asset.coins.EtherClassic
bisq.asset.coins.GambleCoin
bisq.asset.coins.Grin
bisq.asset.coins.FourtyTwo
bisq.asset.coins.Gridcoin
bisq.asset.coins.Horizen

16
assets/src/test/java/bisq/asset/coins/BitcoinClashicTest.java → assets/src/test/java/bisq/asset/coins/BeamTest.java
View file

@ -21,23 +21,21 @@ import bisq.asset.AbstractAssetTest;
import org.junit.Test;
public class BitcoinClashicTest extends AbstractAssetTest {
public class BeamTest extends AbstractAssetTest {
public BitcoinClashicTest() {
super(new BitcoinClashic());
public BeamTest() {
super(new Beam());
}
@Test
public void testValidAddresses() {
assertValidAddress("1HQQgsvLTgN9xD9hNmAgAreakzVzQUSLSH");
assertValidAddress("1MEbUJ5v5MdDEqFJGz4SZp58KkaLdmXZ85");
assertValidAddress("34dvotXMg5Gxc37TBVV2e5GUAfCFu7Ms4g");
assertValidAddress("4a0e54b24d5fdf06891a8eaa57b4b3ac16731e932a64da8ec768083495d624f1");
assertValidAddress("c7776e6d3fd3d9cc66f9e61b943e6d99473b16418ee93f3d5f6b70824cdb7f0a9");
}
@Test
public void testInvalidAddresses() {
assertInvalidAddress("21HQQgsvLTgN9xD9hNmAgAreakzVzQUSLSHa");
assertInvalidAddress("1HQQgsvLTgN9xD9hNmAgAreakzVzQUSLSHs");
assertInvalidAddress("1HQQgsvLTgN9xD9hNmAgAreakzVzQUSLSH#");
assertInvalidAddress("");
assertInvalidAddress("114a0e54b24d5fdf06891a8eaa57b4b3ac16731e932a64da8ec768083495d624f1111111111111111");
}
}

76
assets/src/test/java/bisq/asset/coins/GrinTest.java Normal file
View file

@ -0,0 +1,76 @@
/*
* 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;
import org.junit.Test;
public class GrinTest extends AbstractAssetTest {
public GrinTest() {
super(new Grin());
}
@Test
public void testValidAddresses() {
assertValidAddress("0.0.0.0:8080");
assertValidAddress("173.194.34.134:8080");
assertValidAddress("127.0.0.1:8080");
assertValidAddress("192.168.0.1:8080");
assertValidAddress("18.101.25.153:8080");
assertValidAddress("173.194.34.134:1");
assertValidAddress("173.194.34.134:11");
assertValidAddress("173.194.34.134:1111");
assertValidAddress("173.194.34.134:65535");
// grinbox
assertValidAddress("gVvk7rLBg3r3qoWYL3VsREnBbooT7nynxx5HtDvUWCJUaNCnddvY");
assertValidAddress("grinbox://gVtWzX5NTLCBkyNV19QVdnLXue13heAVRD36sfkGD6xpqy7k7e4a");
assertValidAddress("gVw9TWimGFXRjoDXWhWxeNQbu84ZpLkvnenkKvA5aJeDo31eM5tC@somerelay.com");
assertValidAddress("gVw9TWimGFXRjoDXWhWxeNQbu84ZpLkvnenkKvA5aJeDo31eM5tC@somerelay.com:1220");
assertValidAddress("grinbox://gVwjSsYW5vvHpK4AunJ5piKhhQTV6V3Jb818Uqs6PdC3SsB36AsA@somerelay.com");
assertValidAddress("grinbox://gVwjSsYW5vvHpK4AunJ5piKhhQTV6V3Jb818Uqs6PdC3SsB36AsA@somerelay.com:1220");
}
@Test
public void testInvalidAddresses() {
assertInvalidAddress("google.com");
assertInvalidAddress("100.100.100.100");
assertInvalidAddress(".100.100.100.100:1222");
assertInvalidAddress("100..100.100.100:1222.");
assertInvalidAddress("100.100.100.100.:1222");
assertInvalidAddress("999.999.999.999:1222");
assertInvalidAddress("256.256.256.256:1222");
assertInvalidAddress("256.100.100.100.100:1222");
assertInvalidAddress("123.123.123:1222");
assertInvalidAddress("http://123.123.123:1222");
assertInvalidAddress("1000.2.3.4:1222");
assertInvalidAddress("999.2.3.4:1222");
// too large port
assertInvalidAddress("173.194.34.134:65536");
assertInvalidAddress("gVvk7rLBg3r3qoWYL3VsREnBbooT7nynxx5HtDvUWCJUaNCnddvY1111");
assertInvalidAddress("grinbox:/gVtWzX5NTLCBkyNV19QVdnLXue13heAVRD36sfkGD6xpqy7k7e4a");
assertInvalidAddress("gVw9TWimGFXRjoDXWhWxeNQbu84ZpLkvnenkKvA5aJeDo31eM5tC@somerelay.com.");
assertInvalidAddress("gVw9TWimGFXRjoDXWhWxeNQbu84ZpLkvnenkKvA5aJeDo31eM5tC@somerelay.com:1220a");
assertInvalidAddress("grinbox://gVwjSsYW5vvHpK4AunJ5piKhhQTV6V3Jb818Uqs6PdC3SsB36AsAsomerelay.com");
assertInvalidAddress("grinbox://gVwjSsYW5vvHpK4AunJ5piKhhQTV6V3Jb818Uqs6PdC3SsB36AsA@somerelay.com1220");
}
}

2
build.gradle
View file

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

2
common/src/main/java/bisq/common/app/Version.java
View file

@ -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 = "0.9.1";
public static final String VERSION = "0.9.2";
public static int getMajorVersion(String version) {
return getSubVersion(version, 0);

2
core/src/main/java/bisq/core/dao/governance/asset/FeePayment.java
View file

@ -35,7 +35,7 @@ public class FeePayment {
}
public long daysCoveredByFee(long bsqFeePerDay) {
return fee / bsqFeePerDay;
return bsqFeePerDay > 0 ? fee / bsqFeePerDay : 0;
}
public Optional<Integer> getPassedDays(DaoStateService daoStateService) {

3
core/src/main/java/bisq/core/dao/governance/voteresult/VoteResultService.java
View file

@ -290,6 +290,8 @@ public class VoteResultService implements DaoStateListener, DaoSetupService {
BallotList ballotList = createBallotList(voteWithProposalTxIdList);
byte[] hashOfBlindVoteList = VoteResultConsensus.getHashOfBlindVoteList(opReturnData);
long blindVoteStake = blindVoteStakeOutput.getValue();
log.info("Add entry to decryptedBallotsWithMeritsSet: blindVoteTxId={}, voteRevealTxId={}, blindVoteStake={}, ballotList={}",
blindVoteTxId, voteRevealTxId, blindVoteStake, ballotList);
return new DecryptedBallotsWithMerits(hashOfBlindVoteList, blindVoteTxId, voteRevealTxId, blindVoteStake, ballotList, meritList);
} catch (VoteResultException.MissingBallotException missingBallotException) {
log.warn("We are missing proposals to create the vote result: " + missingBallotException.toString());
@ -537,6 +539,7 @@ public class VoteResultService implements DaoStateListener, DaoSetupService {
decryptedBallotsWithMerits.getMeritList(), daoStateService);
VoteWithStake voteWithStake = new VoteWithStake(ballot.getVote(), decryptedBallotsWithMerits.getStake(), sumOfAllMerits);
voteWithStakeList.add(voteWithStake);
log.info("Add entry to voteWithStakeListByProposalMap: proposalTxId={}, voteWithStake={} ", proposal.getTxId(), voteWithStake);
});
});
return voteWithStakeByProposalMap;

1
core/src/main/java/bisq/core/dao/state/DaoStateService.java
View file

@ -585,6 +585,7 @@ public class DaoStateService implements DaoSetupService {
public void addNonBsqTxOutput(TxOutput txOutput) {
checkArgument(txOutput.getTxOutputType() == TxOutputType.ISSUANCE_CANDIDATE_OUTPUT,
"txOutput must be type ISSUANCE_CANDIDATE_OUTPUT");
log.info("addNonBsqTxOutput: txOutput={}", txOutput);
daoState.getNonBsqTxOutputMap().put(txOutput.getKey(), txOutput);
}

2
core/src/main/java/bisq/core/dao/state/model/DaoState.java
View file

@ -163,7 +163,7 @@ public class DaoState implements PersistablePayload {
.addAllCycles(cycles.stream().map(Cycle::toProtoMessage).collect(Collectors.toList()))
.putAllUnspentTxOutputMap(unspentTxOutputMap.entrySet().stream()
.collect(Collectors.toMap(e -> e.getKey().toString(), e -> e.getValue().toProtoMessage())))
.putAllUnspentTxOutputMap(nonBsqTxOutputMap.entrySet().stream()
.putAllNonBsqTxOutputMap(nonBsqTxOutputMap.entrySet().stream()
.collect(Collectors.toMap(e -> e.getKey().toString(), e -> e.getValue().toProtoMessage())))
.putAllSpentInfoMap(spentInfoMap.entrySet().stream()
.collect(Collectors.toMap(e -> e.getKey().toString(), entry -> entry.getValue().toProtoMessage())))

7
core/src/main/java/bisq/core/dao/state/model/governance/Ballot.java
View file

@ -112,4 +112,11 @@ public final class Ballot implements PersistablePayload, ConsensusCritical, Immu
",\n vote=" + vote +
"\n}";
}
public String info() {
return "Ballot{" +
"\n proposalTxId=" + proposal.getTxId() +
",\n vote=" + vote +
"\n}";
}
}

4
core/src/main/java/bisq/core/dao/state/model/governance/BallotList.java
View file

@ -72,8 +72,8 @@ public class BallotList extends PersistableList<Ballot> implements ConsensusCrit
@Override
public String toString() {
return "List of UID's in BallotList: " + getList().stream()
.map(Ballot::getTxId)
return "BallotList: " + getList().stream()
.map(Ballot::info)
.collect(Collectors.toList());
}
}

21
core/src/main/java/bisq/core/locale/CurrencyUtil.java
View file

@ -20,6 +20,7 @@ package bisq.core.locale;
import bisq.core.app.BisqEnvironment;
import bisq.core.btc.BaseCurrencyNetwork;
import bisq.core.dao.governance.asset.AssetService;
import bisq.core.filter.FilterManager;
import bisq.asset.Asset;
import bisq.asset.AssetRegistry;
@ -122,24 +123,21 @@ public class CurrencyUtil {
public static List<CryptoCurrency> getMainCryptoCurrencies() {
final List<CryptoCurrency> result = new ArrayList<>();
result.add(new CryptoCurrency("XRC", "Bitcoin Rhodium"));
if (DevEnv.isDaoTradingActivated())
result.add(new CryptoCurrency("BSQ", "BSQ"));
if (!baseCurrencyCode.equals("BTC"))
result.add(new CryptoCurrency("BTC", "Bitcoin"));
if (!baseCurrencyCode.equals("DASH"))
result.add(new CryptoCurrency("DASH", "Dash"));
result.add(new CryptoCurrency("BEAM", "Beam"));
result.add(new CryptoCurrency("DASH", "Dash"));
result.add(new CryptoCurrency("DCR", "Decred"));
result.add(new CryptoCurrency("ETH", "Ether"));
result.add(new CryptoCurrency("ETC", "Ether Classic"));
result.add(new CryptoCurrency("GRC", "Gridcoin"));
if (!baseCurrencyCode.equals("LTC"))
result.add(new CryptoCurrency("LTC", "Litecoin"));
result.add(new CryptoCurrency("GRIN", "Grin"));
result.add(new CryptoCurrency("LTC", "Litecoin"));
result.add(new CryptoCurrency("XMR", "Monero"));
result.add(new CryptoCurrency("MT", "Mycelium Token", true));
result.add(new CryptoCurrency("NMC", "Namecoin"));
result.add(new CryptoCurrency("SC", "Siacoin"));
result.add(new CryptoCurrency("SF", "Siafund"));
result.add(new CryptoCurrency("UNO", "Unobtanium"));
result.add(new CryptoCurrency("ZEC", "Zcash"));
result.sort(TradeCurrency::compareTo);
@ -492,9 +490,10 @@ public class CurrencyUtil {
}
// Excludes all assets which got removed by DAO voting
public static List<CryptoCurrency> getActiveSortedCryptoCurrencies(AssetService assetService) {
public static List<CryptoCurrency> getActiveSortedCryptoCurrencies(AssetService assetService, FilterManager filterManager) {
return getAllSortedCryptoCurrencies().stream()
.filter(e -> e.getCode().equals("BSQ") || assetService.isActive(e.getCode()))
.filter(e -> !filterManager.isCurrencyBanned(e.getCode()))
.collect(Collectors.toList());
}
}

4
core/src/main/java/bisq/core/locale/LanguageUtil.java
View file

@ -41,10 +41,10 @@ public class LanguageUtil {
"ru", // Russian
"fr", // French
"vi", // Vietnamese
"th" // Thai
"th", // Thai
"fa" // Persian
/*
// not translated yet
"fa" // Persian --> waiting for third review
"tr" // Turkish
"it", // Italian
"ja", // Japanese

15
core/src/main/java/bisq/core/trade/statistics/AssetTradeActivityCheck.java
View file

@ -18,6 +18,7 @@
package bisq.core.trade.statistics;
import bisq.core.dao.governance.asset.AssetService;
import bisq.core.filter.FilterManager;
import bisq.core.locale.CryptoCurrency;
import bisq.core.locale.CurrencyUtil;
@ -52,11 +53,13 @@ import lombok.extern.slf4j.Slf4j;
public class AssetTradeActivityCheck {
private final AssetService assetService;
private final TradeStatisticsManager tradeStatisticsManager;
private final FilterManager filterManager;
@Inject
public AssetTradeActivityCheck(AssetService assetService, TradeStatisticsManager tradeStatisticsManager) {
public AssetTradeActivityCheck(AssetService assetService, TradeStatisticsManager tradeStatisticsManager, FilterManager filterManager) {
this.assetService = assetService;
this.tradeStatisticsManager = tradeStatisticsManager;
this.filterManager = filterManager;
}
public void onAllServicesInitialized() {
@ -80,7 +83,7 @@ public class AssetTradeActivityCheck {
StringBuilder sufficientlyTraded = new StringBuilder("\nSufficiently traded assets:");
StringBuilder insufficientlyTraded = new StringBuilder("\nInsufficiently traded assets:");
StringBuilder notTraded = new StringBuilder("\nNot traded assets:");
List<CryptoCurrency> whiteListedSortedCryptoCurrencies = CurrencyUtil.getActiveSortedCryptoCurrencies(assetService);
List<CryptoCurrency> whiteListedSortedCryptoCurrencies = CurrencyUtil.getActiveSortedCryptoCurrencies(assetService, filterManager);
Set<CryptoCurrency> assetsToRemove = new HashSet<>(whiteListedSortedCryptoCurrencies);
whiteListedSortedCryptoCurrencies.forEach(e -> {
String code = e.getCode();
@ -170,12 +173,15 @@ public class AssetTradeActivityCheck {
newlyAdded.add("ZER");
newlyAdded.add("XRC");
// v0.9.1 or v0.9.2
// v0.9.2 (Jan 8 2019)
newlyAdded.add("AEON");
newlyAdded.add("BEAM");
newlyAdded.add("BTM");
newlyAdded.add("DXO");
newlyAdded.add("GMCN");
newlyAdded.add("FRTY");
newlyAdded.add("GMCN");
newlyAdded.add("GRIN");
newlyAdded.add("ZEN");
newlyAdded.add("IDA");
newlyAdded.add("IRD");
newlyAdded.add("NOR");
@ -186,6 +192,7 @@ public class AssetTradeActivityCheck {
newlyAdded.add("SPACE");
newlyAdded.add("UCC");
newlyAdded.add("WEB");
newlyAdded.add("WRKZ");
return newlyAdded.contains(code);
}

85
core/src/main/resources/i18n/displayStrings_de.properties
View file

@ -82,7 +82,7 @@ shared.tradeId=Handels-ID
shared.offerId=Angebots-ID
shared.bankName=Bankname
shared.acceptedBanks=Akzeptierte Banken
shared.amountMinMax=Betrag (min - max)
shared.amountMinMax=Betrag (min - max)
shared.amountHelp=Wurde für ein Angebot ein minimaler und maximaler Betrag gesetzt, können Sie jeden Betrag innerhalb dieses Bereiches handeln.
shared.remove=Entfernen
shared.goTo=Zu {0} gehen
@ -193,9 +193,9 @@ shared.all=Alle
shared.edit=Bearbeiten
shared.advancedOptions=Erweiterte Optionen
shared.interval=Interval
shared.actions=Actions
shared.buyerUpperCase=Buyer
shared.sellerUpperCase=Seller
shared.actions=Aktionen
shared.buyerUpperCase=Käufer
shared.sellerUpperCase=Verkäufer
####################################################################
# UI views
@ -299,6 +299,8 @@ market.trades.tooltip.candle.date=Datum:
offerbook.createOffer=Angebot erstellen
offerbook.takeOffer=Angebot annehmen
offerbook.takeOfferToBuy=Take offer to buy {0}
offerbook.takeOfferToSell=Take offer to sell {0}
offerbook.trader=Händler
offerbook.offerersBankId=Bankkennung des Erstellers (BIC/SWIFT): {0}
offerbook.offerersBankName=Bankname des Erstellers: {0}
@ -536,7 +538,7 @@ portfolio.pending.step2_buyer.confirmStart.yes=Ja, ich habe die Zahlung begonnen
portfolio.pending.step2_seller.waitPayment.headline=Auf Zahlung warten
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=The BTC buyer still has not done the {0} payment.\nYou need to wait until they have started the payment.\nIf the trade has not been completed on {1} the arbitrator will investigate.
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 noch nicht begonnen!\nDie maximale Handelsdauer wurde überschritten.\nSie können länger warten um dem Handelspartner mehr Zeit zu geben oder den Vermittler kontaktieren, um einen Konflikt zu öffnen.
# suppress inspection "UnusedProperty"
@ -565,8 +567,8 @@ portfolio.pending.step3_seller.altcoin.explorer=in ihrem bevorzugten {0} Blockch
portfolio.pending.step3_seller.altcoin.wallet=in ihrer {0} Brieftasche
portfolio.pending.step3_seller.altcoin={0}Bitte überprüfen Sie mit Ihrem bevorzugten {1}-Blockchain-Explorer, ob die Transaktion zu Ihrer Empfangsadresse\n{2}\nschon genug Blockchain-Bestätigungen hat.\nDer Zahlungsbetrag muss {3} sein\n\nSie können Ihre {4}-Adresse vom Hauptbildschirm kopieren und woanders einfügen, nachdem dieser Dialog geschlossen wurde.
portfolio.pending.step3_seller.postal={0}Bitte überprüfen Sie, ob Sie {1} per \"US Postal Money Order\" vom BTC-Käufer erhalten haben.\n\nDie Handels-ID (\"Verwendungszweck\") der Transaktion ist: \"{2}\"
portfolio.pending.step3_seller.bank=Ihr Handelspartner hat den Beginn der {0}-Zahlung bestätigt.\n\nBitte gehen Sie auf Ihre Online-Banking-Website und überprüfen Sie, ob Sie {1} vom BTC-Käufer erhalten haben.\n\nDie Handels-ID (\"Verwendungszweck\") der Transaktion ist: \"{2}\"\n
portfolio.pending.step3_seller.cash=Because the payment is done via Cash Deposit the BTC buyer has to write \"NO REFUND\" on the paper receipt, tear it in 2 parts and send you a photo by email.\n\nTo avoid chargeback risk, only confirm if you received the email and if you are sure the paper receipt is valid.\nIf you are not sure, {0}
portfolio.pending.step3_seller.bank=Ihr Handelspartner hat den Beginn der {0}-Zahlung bestätigt.\n\nBitte gehen Sie auf Ihre Online-Banking-Website und überprüfen Sie, ob Sie {1} vom BTC-Käufer erhalten haben.\n\nDie Handels-ID (\"Verwendungszweck\") der Transaktion ist: \"{2}\"\n\n
portfolio.pending.step3_seller.cash=Da die Zahlung per Cash Deposit ausgeführt wurde, muss der BTC-Käufer \"NO REFUND\" auf die Quittung schreiben, diese in 2 Teile reißen und Ihnen ein Foto per E-Mail schicken.\n\nUm die Gefahr einer Rückbuchung zu vermeiden bestätigen Sie nur, wenn Sie die E-Mail erhalten haben und Sie sicher sind, dass die Quittung gültig ist.\nWenn Sie nicht sicher sind, {0}
portfolio.pending.step3_seller.moneyGram=Der Käufer muss Ihnen die Authorisierungs-Nummer und ein Foto der Quittung per E-Mail zusenden.\nDie Quittung muss deutlich Ihren vollständigen Namen, Ihr Land, Ihr Bundesland und den Betrag enthalten. Bitte überprüfen Sie Ihre E-Mail, wenn Sie die Authorisierungs-Nummer erhalten haben.\n\nNach dem Schließen dieses Pop-ups sehen Sie den Namen und die Adresse des BTC-Käufers, um das Geld von MoneyGram abzuholen.\n\nBestätigen Sie den Erhalt erst, nachdem Sie das Geld erfolgreich abgeholt haben!
portfolio.pending.step3_seller.westernUnion=Der Käufer muss Ihnen die MTCN (Sendungsnummer) und ein Foto der Quittung per E-Mail zusenden.\nDie Quittung muss deutlich Ihren vollständigen Namen, Ihre Stadt, Ihr Land und den Betrag enthalten. Bitte überprüfen Sie Ihre E-Mail, wenn Sie die MTCN erhalten haben.\n\nNach dem Schließen dieses Pop-ups sehen Sie den Namen und die Adresse des BTC-Käufers, um das Geld von Western Union abzuholen.\n\nBestätigen Sie den Erhalt erst, nachdem Sie das Geld erfolgreich abgeholt haben!
portfolio.pending.step3_seller.halCash=Der Käufer muss Ihnen den HalCash-Code als SMS zusenden. Außerdem erhalten Sie eine Nachricht von HalCash mit den erforderlichen Informationen, um EUR an einem HalCash-fähigen Geldautomaten abzuheben.\n\nNachdem Sie das Geld am Geldautomaten abgeholt haben, bestätigen Sie bitte hier den Zahlungseingang!
@ -721,7 +723,7 @@ funds.tx.noTxAvailable=Keine Transaktionen verfügbar
funds.tx.revert=Umkehren
funds.tx.txSent=Transaktion erfolgreich zu einer neuen Adresse in der lokalen Bisq-Brieftasche gesendet.
funds.tx.direction.self=An Sie selbst senden
funds.tx.daoTxFee=Miner fee for DAO tx
funds.tx.daoTxFee=Mining-Gebühr für DAO Tx
funds.tx.reimbursementRequestTxFee=Rückerstattungsantrag
funds.tx.compensationRequestTxFee=Entlohnungsanfrage
@ -765,9 +767,9 @@ support.buyerOfferer=BTC-Käufer/Ersteller
support.sellerOfferer=BTC-Verkäufer/Ersteller
support.buyerTaker=BTC-Käufer/Abnehmer
support.sellerTaker=BTC-Verkäufer/Abnehmer
support.backgroundInfo=Bisq is not a company, so it handles disputes differently.\n\nIf there are disputes in the trade process (e.g. one trader does not follow the trade protocol) the application will display an \"Open dispute\" button after the trade period is over for contacting the arbitrator.\n\nIf there is an issue with the application, the software will try to detect it and, if possible, display an \"Open support ticket\" button to contact the arbitrator who will forward the issue to the developers.\n\nIf you are having an issue and did not see the \"Open support ticket\" button, you can open a support ticket manually by selecting the trade causing issues under \"Portfolio/Open trades\" and hitting \"alt + o\" or \"option + o\". Please use this method only if you are sure that the software is not working as expected. If you have problems or questions, please review the FAQ on the bisq.network web page or post in the Bisq forum in the Support section.
support.backgroundInfo=Bisq ist keine Firma und betreibt keine Form von Kundendienst.\n\nFalls es während des Handelsprozess (z.B. ein Händler befolgt nicht das Handelsprotokoll) zu Konflikten kommen sollte, wird die Anwendung nach der Handelsdauer eine \"Konflikt öffnen\"-Schaltfläche anzeigen, um den Vermittler zu kontaktieren.\n\nIm Falle von Softwarefehlern oder anderen Problemen, die von der Anwendung entdeckt werden, wird eine \"Support-Ticket öffnen\" Schaltfläche angezeigt, um den Vermittler zu kontaktieren, der die Probleme an die Entwickler weiterleitet.\n\nFalls Sie ein Problem haben, aber die \"Support-Ticket öffnen\"-Schaltfläche nicht angezeigt wird, können Sie manuell ein Support-Ticket öffnen indem Sie den Probleme bereitende Handel unter \"Mappe/Offene Händel\" wählen und die Tastenkombination \"alt + o\" oder \"option + o\" drücken.. Bitte nutzen Sie diese nur, wenn Sie sicher sind, dass sich die Software nicht wie erwartet verhält. Falls Sie nicht wissen wie man Bisq verwendet oder andere Fragen haben, überprüfen Sie bitte die FAQ auf der bisq.io-Website oder erstellen Sie einen Post im Support-Abschnitt des Bisq-Forums.
support.initialInfo=Please note the basic rules for the dispute process:\n1. You need to respond to the arbitrator's requests within 2 days.\n2. The maximum period for a dispute is 14 days.\n3. You need to cooperate with the arbitrator and provide the information they request to make your case.\n4. You accepted the rules outlined in the wiki in the user agreement when you first started the application.\n\nPlease read more about the dispute process in our wiki:\nhttps://github.com/bisq-network/exchange/wiki/Arbitration-system
support.initialInfo=Bitte beachten Sie die grundlegenden Regeln für den Konfliktprozess:\n1. Sie müssen innerhalb von zwei Tagen auf die Anfrage des Vermittlers reagieren.\n2. Die maximale Dauer des Konflikts ist 14 Tage.\n3. Sie müssen befolgen, was der Vermittler von Ihnen verlangt, um Beweise für ihren Fall zu liefern.\n4. Sie haben beim ersten Start dieser Anwendung die Regeln akzeptiert, die im Wiki in den Nutzungsbedingungen zusammengefasst wurden.\n\nErfahren Sie mehr über den Konfliktprozess in unserem Wiki:\nhttps://github.com/bisq-network/exchange/wiki/Arbitration-system
support.systemMsg=Systemnachricht: {0}
support.youOpenedTicket=Sie haben eine Anfrage für Support geöffnet.
support.youOpenedDispute=Sie haben eine Anfrage für einen Konflikt geöffnet.\n\n{0}
@ -836,8 +838,8 @@ settings.net.useCustomNodesRadio=Spezifische Bitcoin-Core-Knoten verwenden
settings.net.warn.usePublicNodes=Falls Sie das öffentliche Bitcoin-Netzwerk verwenden sind Sie einem schwerwiegenden Datenschutzproblem ausgesetzt durch das fehlerhafte Design und Implementierung des Bloom Filters in SPV-Brieftaschen wie BitcoinJ (verwendet in Bisq). Jeder verbundene Bitcoin-Core-Knoten könnte herausfinden, dass alle Ihre Brieftaschen-Adressen einer Person gehören.\n\nBitte informieren Sie sich dazu auf folgender Seite: https://bisq.network/blog/privacy-in-bitsquare.\n\nSind Sie sicher, dass Sie öffentliche Knoten verwenden möchten?
settings.net.warn.usePublicNodes.useProvided=Nein, bereitgestellte Knoten verwenden
settings.net.warn.usePublicNodes.usePublic=Ja, öffentliches Netzwerk verwenden
settings.net.warn.useCustomNodes.B2XWarning=Please be sure that your Bitcoin node is a trusted Bitcoin Core node!\n\nConnecting to nodes which do not follow the Bitcoin Core consensus rules could corrupt your wallet and cause problems in the trade process.\n\nUsers who connect to nodes that violate consensus rules are responsible for any resulting damage. Any resulting disputes will be decided in favor of the other peer. No technical support will be given to users who ignore this warning and protection mechanisms!
settings.net.localhostBtcNodeInfo=(Background information: If you are running a local Bitcoin node (localhost) you can connect exclusively to it.)
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 Brieftasche 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.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
settings.net.creationDateColumn=Eingerichtet
@ -860,17 +862,17 @@ settings.net.inbound=eingehend
settings.net.outbound=ausgehend
settings.net.reSyncSPVChainLabel=SPV-Kette neu synchronisieren
settings.net.reSyncSPVChainButton=SPV-Datei löschen und neu synchronisieren
settings.net.reSyncSPVSuccess=The SPV chain file will be deleted on the next startup. You need to restart your application now.\n\nAfter the restart it can take a while to resync with the network and you will only see all transactions once the resync is completed.\n\nPlease restart again after the resync has completed because there are sometimes inconsistencies that result in incorrect balances to display.
settings.net.reSyncSPVAfterRestart=The SPV chain file has been deleted. Please be patient. It can take a while to resync with the network.
settings.net.reSyncSPVSuccess=Die SPV-Kettendatei wird beim nächsten Start gelöscht. Sie müssen Ihre Anwendung jetzt neu starten.\n\nNach dem Neustart kann es eine Weile dauern bis alles mit dem Netzwerk synchronisiert wurde. Sie sehen alle Transaktionen erst, wenn fertig synchronisiert wurde.\n\nBitte starten Sie Ihre Anwendung nach Abschluss der Synchronisation neu, da es manchmal Inkonsistenzen gibt, die zum Anzeigen falscher Guthaben führen.
settings.net.reSyncSPVAfterRestart=Die SPV-Kettendatei wurde gelöscht. Haben Sie bitte Geduld, es kann eine Weile dauern mit dem Netzwerk neu zu synchronisieren.
settings.net.reSyncSPVAfterRestartCompleted=Die erneute Synchronisation ist jetzt abgeschlossen. Bitte starten Sie die Anwendung neu.
settings.net.reSyncSPVFailed=Konnte SPV-Kettendatei nicht löschen.\nFehler: {0}
setting.about.aboutBisq=Über Bisq
setting.about.about=Bisq is open-source software which facilitates the exchange of bitcoin with national currencies (and other cryptocurrencies) through a decentralized peer-to-peer network in a way that strongly protects user privacy. Learn more about Bisq on our project web page.
setting.about.about=Bisq ist ein Open-Source-Projekt und ein dezentrales Netzwerk von Nutzern, die Bitcoins gegen nationale Währungen oder alternative Cryptowährungen auf einem Weg tauschen wollen, der die Privatsphäre schützt. Lernen Sie auf unser Projektwebsite mehr über Bisq.
setting.about.web=Bisq-Website
setting.about.code=Quellcode
setting.about.agpl=AGPL-Lizenz
setting.about.support=Bisq unterstützen
setting.about.def=Bisq is not a company—it is a project open to the community. If you want to participate or support Bisq please follow the links below.
setting.about.def=Bisq ist keine Firma, sondern ein Gemeinschaftsprojekt, das offen für Mitwirken ist. Wenn Sie an Bisq mitwirken oder das Projekt unterstützen wollen, folgen Sie bitte den unten stehenden Links.
setting.about.contribute=Mitwirken
setting.about.donate=Spenden
setting.about.providers=Datenanbieter
@ -892,7 +894,7 @@ setting.about.subsystems.val=Netzwerkversion: {0}; P2P-Nachrichtenversion: {1};
account.tab.arbitratorRegistration=Vermittler-Registrierung
account.tab.account=Konto
account.info.headline=Willkommen in Ihrem Bisq-Konto
account.info.msg=Here you can add trading accounts for national currencies & altcoins, select arbitrators, and create a backup of your wallet & account data.\n\nA new Bitcoin wallet was created the first time you started Bisq.\n\nWe strongly recommend that you write down your Bitcoin wallet seed words (see tab on the top) and consider adding a password before funding. Bitcoin deposits and withdrawals are managed in the \"Funds\" section.\n\nPrivacy & security note: because Bisq is a decentralized exchange, all your data is kept on your computer. There are no servers, so we have no access to your personal info, your funds, or even your IP address. Data such as bank account numbers, altcoin & Bitcoin addresses, etc are only shared with your trading partner to fulfill trades you initiate (in case of a dispute the arbitrator will see the same data as your trading peer).
account.info.msg=Hier können Sie Handelskonten für nationale Währungen & Altcoins konfigurieren, Vermittler auswählen und Backups für Ihre Wallets & Kontodaten erstellen.\n\nEine leere Bitcoinwallet wurde erstellt, als Sie das erste Mal Bisq gestartet haben.\nWir empfehlen, dass Sie Ihre Bitcoin-Wallet-Keimwörter aufschreiben (siehe Schaltfläche links) und sich überlegen ein Passwort hinzuzufügen, bevor Sie einzahlen. Bitcoin-Kautionen und Abhebungen werden unter \"Gelder\" verwaltet.\n\nPrivatsphäre & Sicherheit:\nBisq ist ein dezentralisierte Börse, was bedeutet, dass all Ihre Daten auf ihrem Computer bleiben. Es gibt keine Server und wir haben keinen Zugriff auf Ihre persönlichen Informationen, Ihre Gelder oder selbst Ihre IP Adresse. Daten wie Bankkontonummern, Altcoin- & Bitcoinadressen, etc werden nur mit Ihrem Handelspartner geteilt, um Händel abzuschließen, die Sie gestartet haben (im Falle eines Konflikts wird der Vermittler die selben Daten sehen wie Ihr Handelspartner).
account.menu.paymentAccount=Nationale Währungskonten
account.menu.altCoinsAccountView=Altcoin-Konten
@ -905,7 +907,7 @@ account.arbitratorRegistration.pubKey=Öffentlicher Schlüssel
account.arbitratorRegistration.register=Vermittler registrieren
account.arbitratorRegistration.revoke=Registrierung widerrufen
account.arbitratorRegistration.info.msg=Please note that you need to stay available for 15 days after revoking as there might be trades which are using you as arbitrator. The max. allowed trade period is 8 days and the dispute process might take up to 7 days.
account.arbitratorRegistration.info.msg=Beachten Sie bitte, dass Sie nach dem Widerrufen für 15 Tage verfügbar bleiben müssen, da es Händel geben kann, die Sie als Vermittler nutzen. Die maximal erlaubte Handelsdauer ist 8 Tage und der Konfliktprozess kann bis zu 7 Tage dauern.
account.arbitratorRegistration.warn.min1Language=Sie müssen wenigstens eine Sprache festlegen.\nWir haben Ihre Standardsprache für Sie hinzugefügt.
account.arbitratorRegistration.removedSuccess=Sie haben Ihren Vermittler erfolgreich aus dem P2P-Netzwerk entfernt.
account.arbitratorRegistration.removedFailed=Der Vermittler konnte nicht entfernt werden.{0}
@ -924,14 +926,14 @@ account.arbitratorSelection.noLang=Sie können nur Vermittler wählen, die wenig
account.arbitratorSelection.minOne=Sie müssen wenigstens einen Vermittler auswählen.
account.altcoin.yourAltcoinAccounts=Ihre Altcoin-Konten
account.altcoin.popup.wallet.msg=Please be sure that you follow the requirements for the usage of {0} wallets as described on the {1} web page.\nUsing wallets from centralized exchanges where (a) you don''t control your keys or (b) which don''t use compatible wallet software is risky: it can lead to loss of the traded funds!\nThe arbitrator is not a {2} specialist and cannot help in such cases.
account.altcoin.popup.wallet.msg=Bitte stellen Sie sicher, dass Sie die Anforderungen für die Nutzung von {0}-Brieftaschen befolgen, die auf der {1}-Website beschrieben werden.\nDie Verwendung von Brieftaschen zentraler Börsen, bei denen Sie (a) Ihre Schlüssel nicht selber verwalten, oder (b) das Nutzen inkompatibler Brieftasche-Software können zum Verlust der gehandelten Gelder führen!\nDer Vermittler ist kein {2}-Spezialist und kann Ihnen in einem solchen Fall nicht helfen.
account.altcoin.popup.wallet.confirm=Ich verstehe und bestätige, dass ich weiß, welche Brieftasche ich benutzen muss.
account.altcoin.popup.xmr.msg=Wenn Sie XMR auf Bisq handeln wollen, stellen Sie bitte sicher, dass Sie die folgenden Bedingungen verstehen und erfüllen:\n\nUm XMR zu senden, brauchen Sie entweder die offizielle Monero GUI Wallet oder die einfache Monero CLI Wallet mit aktivierter store-tx-info (Standard in neuen Versionen).\nStellen Sie bitte sicher, dass Sie auf den Tx-Schlüssel zugreifen können.\nmonero-wallet-cli: (nutzen Sie das get_tx_key Kommando)\nmonero-wallet-gui: (gehen sie zum Verlauf Tab und klicken Sie die (P) Schaltfläche um die Zahlungsbestätigung anzuzeigen)\n\nZusätzlich zum XMR checktx Werkzeug (https://xmr.llcoins.net/checktx.html) kann die Überprüfung auch innerhalb der Brieftasche durchgeführt werden. \nmonero-wallet-cli: verwenden Sie den Befehl (check_tx_key)\nmonero-wallet-gui: gehen Sie zur Erweitert > Beweisen/Prüfen-Seite\n\nIn normalen Blockexplorern ist die Übertragung nicht überprüfbar.\n\nIm Fall eines Konflikts müssen Sie dem Vermittler folgende Daten übergeben:\n- Den privaten Tx-Schlüssel\n- Den Transaktionshash\n- Die öffentliche Adresse des Empfängers\n\nSollten Sie die Daten nicht übergeben können oder eine inkompatible Wallet verwendet haben, werden Sie den Konflikt verlieren. Der XMR Sender ist in der Verantwortung die Übertragung der XMR gegenüber dem Vermittler im Falle eines Konflikts zu beweisen.\n\nEs wird keine Zahlungskennung benötigt, nur eine normale öffentliche Adresse.\n\nFalls Sie sich über diesen Prozess im Unklaren sind, besuchen Sie (https://www.getmonero.org/resources/user-guides/prove-payment.html) oder das Moneroforum (https://forum.getmonero.org) um weitere Informationen zu finden.
account.altcoin.popup.blur.msg=If you want to trade BLUR on Bisq please be sure 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 arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nIf you cannot provide the required information to the arbitrator, you will lose the dispute. In all cases of dispute, the BLUR sender bears 100% of the burden of responsiblity in verifying transactions to an arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW).
account.altcoin.popup.blur.msg=Stellen Sie sicher, die folgenden Bedingungen verstanden zu haben, falls Sie BLUR auf Bisq handeln möchten:\n\nUm BLUR zu senden, müssen sie die Blur CLI Brieftasche (blur-wallte-cli) nutzen.\n\nNachdem dem Senden der Zahlung, wird die Brieftasche den Transaktions-Hash (tx ID). Diese müssen Sie speichern. Sie müssen auch das 'get_tx_key' Kommando ausführen um den privaten Transaktionschlüssel zu erhalten. Sie müssen beides im Falle eines Konflikts haben.\nIn diesem Fall müssen Sie beides mit der öffentlichen Adresse des Empfängers dem Vermittler geben,\nder dann die BLUR Übertragung mi dem Blur Transaction Viewer (https://blur.cash/#tx-viewer) bestätigt.\n\nSollten Sie die benötigten Daten nicht bereitstellen, verlieren Sie den Konflikt.\nDer BLUR Sender ist verantwortlich den BLUR Transfer dem Vermittler, im Falle eines Konflikts, zu beweisen.\n\nSollten Sie diese Bedingungen nicht verstehen, suchen Sie Hilfe im Blur Network Discord (https://discord.gg/dMWaqVW).
account.altcoin.popup.ccx.msg=Stellen Sie sicher, die folgenden Bedingungen verstanden zu haben, falls Sie CCX auf Bisq handeln möchten:\n\nUm CCX zu senden, müssen sie eine offizielle Conceal Brieftasche nutzen, Cli oder GUI. Nachdem dem Senden\nder Zahlung, wird die Brieftasche den Transaktions-Hash (ID) und geheimen Schlüssel anzeigen. Sie müssen beides im Falle eines Konflikts haben.\nIn diesem Fall müssen Sie beides mit der öffentlichen Adresse des Empfängers dem Vermittler geben,\nder dann die CCX Übertragung mi dem Conceal Transaction Viewer (https://explorer.conceal.network/txviewer) bestätigt.\nWeil Conceal ein Privatsphären Coin ist, kann ein Blockforscher den Transfer nicht bestätigen.\n\nSollten Sie die benötigten Daten nicht bereitstellen können, verlieren Sie den Konflikt.\nWenn Sie den geheimen Schlüssel nicht sofort nach der CCX Transaktion speichern, kann dieser nicht wiederhergestellt werden.\nSollten Sie diese Bedingungen nicht verstehen, suchen Sie Hilfe im Conceal Discord (http://discord.conceal.network).
account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides a transaction is not verifyable on the public blockchain. If required you can prove your payment thru use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at \ (http://drgl.info/#check_txn).\n\nIf you cannot provide the above data or if you used an incompatible wallet it would result in losing the dispute case. The Dragonglass sender is responsible to be able to verify the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help.
account.altcoin.popup.ZEC.msg=Wenn Sie {0} verwenden, können Sie nur die transparenten Adressen verwenden (diese beginnen mit t), nicht die z-Adressen (privat), da der Vermittler die Transaktionen mit z-Adressen nicht überprüfen könnte.
account.altcoin.popup.XZC.msg=Wenn Sie {0} verwenden, können Sie nur die transparenten (verfolgbaren) Adressen verwenden, nicht die unverfolgbaren, da der Vermittler Transaktionen mit unverfolgbaren Adressen in einem Blockforscher nicht überprüfen könnte.
account.altcoin.popup.XZC.msg=Wenn Sie {0} verwenden, können Sie nur die transparenten (verfolgbaren) Adressen verwenden, nicht die unverfolgbaren, da der Vermittler Transaktionen mit unverfolgbaren Adressen in einem Blockforscher nicht überprüfen könnte.
account.altcoin.popup.bch=Bitcoin Cash und Bitcoin Clashic leiden unter Replay-Protection. Wenn Sie diese Coins benutzen, stellen Sie sicher, dass Sie ausreichend vorsorgen und die Konsequenzen verstehen. Sie können Verluste erleiden, wenn Sie einen Coin senden und ungewollt die gleichen Gelder in einer anderen Blockkette senden. Weil diese "airdrop coins" den gleichen Verlauf wie die Bitcoin Blockkette haben, gibt es auch Sicherheitsrisiken und beachtliche Risiken für die Privatsphären.\n\nLesen Sie bitte mehr über das Thema im Bisq-Forum: https://forum.bisq.io/t/airdrop-coins-information-thread-bch-btg-bchc
account.altcoin.popup.btg=Weil Bitcoin Gold den Verlauf wie die Bitcoin Blockkette hat, kommt damit ein gewissen Sicherheitsrisiken und beachtlichen Risiken für die Privatsphäre. Wenn Sie Bitcoin Gold benutzen, stellen Sie sicher, dass Sie ausreichend vorsorgen und die Konsequenzen verstehen.\n\n\nLesen Sie bitte mehr über das Thema im Bisq-Forum: https://forum.bisq.io/t/airdrop-coins-information-thread-bch-btg-bchc
@ -952,14 +954,14 @@ account.password.removePw.button=Passwort entfernen
account.password.removePw.headline=Passwortschutz Ihrer Brieftasche entfernen
account.password.setPw.button=Passwort festlegen
account.password.setPw.headline=Passwortschutz Ihrer Brieftasche einrichten
account.password.info=With password protection you'll need to enter your password at application startup, when withdrawing bitcoin out of your wallet, and when restoring your wallet from seed words.
account.password.info=Mit Passwortschutz müssen Sie Ihr Passwort eingeben, sowohl wenn Sie Bitcoins aus Ihrer Brieftasche abheben, wenn Sie Ihre Brieftasche einsehen oder aus den Seed-Wörtern wiederherstellen wollen, als auch beim Start der Anwendung.
account.seed.backup.title=Backup der Seed-Wörter Ihrer Brieftasche erstellen
account.seed.info=Please write down both wallet seed words and the date! You can recover your wallet any time with seed words and the date.\nThe same seed words are used for the BTC and BSQ wallet.\n\nYou should write down the seed words on a sheet of paper. Do not save them on your computer.\n\nPlease note that the seed words are NOT a replacement for a backup.\nYou need to create a backup of the whole application directory from the \"Account/Backup\" screen to recover application state and data.\nImporting seed words is only recommended for emergency cases. The application will not be functional without a proper backup of the database files and keys!
account.seed.info=Bitte schreiben Sie die sowohl Seed-Wörter als auch das Datum auf! Mit diesen Seed-Wörtern und dem Datum können Sie Ihre Brieftasche jederzeit wiederherstellen.\nDie Seed-Wörter werden für die BTC- und BSQ-Brieftasche genutzt.\n\nSchreiben Sie die Seed-Wörter auf ein Blatt Papier schreiben und speichern Sie sie nicht auf Ihrem Computer.\n\nBitte beachten Sie, dass die Seed-Wörter KEIN Ersatz für ein Backup sind.\nSie müssen ein Backup des gesamten Anwendungsverzeichnisses unter \"Konto/Backup\" erstellen, um den ursprünglichen Zustand der Anwendung wiederherstellen zu können.\nDas Importieren der Seed-Wörter wird nur für Notfälle empfohlen. Die Anwendung wird ohne richtiges Backup der Datenbankdateien und Schlüssel nicht funktionieren!
account.seed.warn.noPw.msg=Sie haben kein Brieftasche-Passwort festgelegt, was das Anzeigen der Seed-Wörter schützen würde.\n\nMöchten Sie die Seed-Wörter jetzt anzeigen?
account.seed.warn.noPw.yes=Ja, und nicht erneut fragen
account.seed.enterPw=Geben Sie Ihr Passwort ein um die Seed-Wörter zu sehen
account.seed.restore.info=Please make a backup before applying restore from seed words. Be aware that wallet restore is only for emergency cases and might cause problems with the internal wallet database.\nIt is not a way for applying a backup! Please use a backup from the application data directory for restoring a previous application state.
account.seed.restore.info=Erstellen Sie vor dem Wiederherstellen der Keimwörter eine Sicherung!\nBeachten Sie auch, dass Brieftasche-Wiederherstellung nur für Notfälle ist und Probleme mit der internen Brieftasche-Datenbank verursachen kann.\nEs ist kein Weg ein Backup anzuwenden! Bitte nutzen Sie ein Backup aus dem Anwendungsdatenordner um eine vorherigen Zustand wiederherzustellen.
account.seed.restore.ok=Ok, ich verstehe und möchte wiederherstellen
@ -1274,7 +1276,7 @@ dao.bond.bondedRoleType.FORUM_OPERATOR=Betreiber des Forums
# suppress inspection "UnusedProperty"
dao.bond.bondedRoleType.SEED_NODE_OPERATOR=Seed-Knoten Betreiber
# suppress inspection "UnusedProperty"
dao.bond.bondedRoleType.PRICE_NODE_OPERATOR=Preis-Netzknoten Betreiber
dao.bond.bondedRoleType.PRICE_NODE_OPERATOR=Preis-Netzknoten Betreiber
# suppress inspection "UnusedProperty"
dao.bond.bondedRoleType.BTC_NODE_OPERATOR=BTC Netzknoten Betreiber
# suppress inspection "UnusedProperty"
@ -1322,7 +1324,7 @@ dao.assetState.REMOVED_BY_VOTING=Durch Abstimmung entfernt
dao.proofOfBurn.header=Nachweis der Verbrennung
dao.proofOfBurn.amount=Betrag
dao.proofOfBurn.preImage=Vorabbild
dao.proofOfVerbrennen.burn=Verbrennen
dao.proofOfBurn.burn=Verbrennen
dao.proofOfBurn.allTxs=Alle Transaktionen zum Nachweis der Verbrennung
dao.proofOfBurn.myItems=Meine Transaktionen zum Nachweis der Verbrennung
dao.proofOfBurn.date=Datum
@ -1330,7 +1332,7 @@ dao.proofOfBurn.hash=Hash
dao.proofOfBurn.txs=Transaktionen
dao.proofOfBurn.pubKey=Pubkey
dao.proofOfBurn.signature.window.title=Nachricht mit Schlüssel vom Nachweis der Verbrennung unterzeichnen
dao.proofOfBurn.verify.window.title=Verify a message with key from proof or burn transaction
dao.proofOfBurn.verify.window.title=Verifizieren Sie eine Nachricht mit dem Schlüssel der Proof-Of-Burn Transaktion
dao.proofOfBurn.copySig=Signatur in Zwischenablage kopieren
dao.proofOfBurn.sign=Unterzeichnen
dao.proofOfBurn.message=Nachricht
@ -1506,8 +1508,8 @@ dao.wallet.send.send=BSQ-Gelder senden
dao.wallet.send.sendBtc=BTC-Gelder senden
dao.wallet.send.sendFunds.headline=Abhebeanfrage bestätigen
dao.wallet.send.sendFunds.details=Sende: {0}\nAn Empfangsadresse: {1}\nBenötigte Transaktionsgebühr ist: {2} ({3} Satoshis/Byte)\nTransaktionsgröße: {4} Kb\n\nDer Empfänger erhält: {5}\n\nSind Sie sicher, dass Sie diesen Betrag abheben wollen?
dao.wallet.chainHeightSynced=Latest verified block: {0}
dao.wallet.chainHeightSyncing=Awaiting blocks... Verified {0} blocks out of {1}
dao.wallet.chainHeightSynced=Synchronisiert bis Block: {0}
dao.wallet.chainHeightSyncing=Empfange Blöcke... Synchronisiere Block: {0} (letzter Block: {1})
dao.wallet.tx.type=Typ
# suppress inspection "UnusedProperty"
@ -1578,13 +1580,13 @@ displayUpdateDownloadWindow.button.downloadLater=Später herunterladen
displayUpdateDownloadWindow.button.ignoreDownload=Diese Version ignorieren
displayUpdateDownloadWindow.headline=Ein neues Bisq-Update ist verfügbar!
displayUpdateDownloadWindow.download.failed.headline=Download fehlgeschlagen
displayUpdateDownloadWindow.download.failed=Download fehlgeschlagen.\nBitte laden sie manuell von https://bisq.network/downloads herunter und überprüfen die Datei
displayUpdateDownloadWindow.installer.failed=Nicht möglich den korrekten Installer zu bestimmen. Bitte laden sie manuell von https://bisq.network/downloads herunter und überprüfen die Datei
displayUpdateDownloadWindow.verify.failed=Überprüfung fehlgeschlagen.\nBitte laden sie manuell von https://bisq.network/downloads herunter und Überprüfen die Datei
displayUpdateDownloadWindow.download.failed=Download fehlgeschlagen.\nBitte laden sie die Datei manuell von https://bisq.network/downloads herunter und überprüfen sie sie.
displayUpdateDownloadWindow.installer.failed=Der gewünschte Installer wurde nicht gefunden. Bitte laden sie die Datei manuell von https://bisq.network/downloads herunter und überprüfen sie sie.
displayUpdateDownloadWindow.verify.failed=Überprüfung fehlgeschlagen.\nBitte laden sie die Datei manuell von https://bisq.network/downloads herunter und überprüfen Sie sie.
displayUpdateDownloadWindow.success=Die neue Version wurde erfolgreich heruntergeladen und die Signatur überprüft.\n\nBitte öffnen Sie das Downloadverzeichnis, schließen die Anwendung und installieren die neue Version.
displayUpdateDownloadWindow.download.openDir=Downloadverzeichnis öffnen
disputeZusammenfassungWindow.title=Zusammenfassung
disputeSummaryWindow.title=Zusammenfassung
disputeSummaryWindow.openDate=Erstellungsdatum des Tickets
disputeSummaryWindow.role=Rolle des Händlers
disputeSummaryWindow.evidence=Beweis
@ -1659,7 +1661,7 @@ offerDetailsWindow.makersOnion=Onion-Adresse des Erstellers
qRCodeWindow.headline=QR-Code
qRCodeWindow.msg=Bitte nutzen Sie diesen QR-Code zum Finanzieren Ihrer Bisq-Brieftasche von einer externen Brieftasche.
qRCodeWindow.request=Payment request:\n{0}
qRCodeWindow.request=Zahlungsanfrage:\n{0}
selectDepositTxWindow.headline=Kautionstransaktion für Konflikt auswählen
selectDepositTxWindow.msg=Die Kautionstransaktion wurde nicht im Handel gespeichert.\nBitte wählen Sie die existierenden MultiSig-Transaktionen aus Ihrer Brieftasche, die die Kautionstransaktion für den fehlgeschlagenen Handel war.\n\nSie können die korrekte Transaktion finden, indem Sie das Handelsdetail-Fenster öffnen (klicken Sie auf die Handels-ID in der Liste) und dem Transaktions-Output der Handelsgebührenzahlung zur nächsten Transaktion folgen, wo Sie die MultiSig-Kautionstransaktion sehen (die Adresse beginnt mit einer 3). Diese Transaktions-ID sollte in der dargestellten Liste auftauchen. Sobald Sie die korrekte Transaktion gefunden haben, wählen Sie diese Transaktion hier aus und fahren fort.\n\nEntschuldigen Sie die Unannehmlichkeiten, aber dieser Fehler sollte sehr selten auftreten und wir werden in Zukunft versuchen bessere Wege zu finden, ihn zu lösen.
@ -1746,7 +1748,7 @@ popup.headline.error=Fehler
popup.doNotShowAgain=Nicht erneut anzeigen
popup.reportError.log=Protokolldatei öffnen
popup.reportError.gitHub=Auf GitHub-Issue-Tracker melden
popup.reportError={0}\n\nTo help us to improve the software please report the bug on our issue tracker on GitHub (https://github.com/bisq-network/bisq-desktop/issues).\nThe error message will be copied to the clipboard when you click a button below.\nIt will make debugging easier if you can attach the bisq.log file as well.
popup.reportError={0}\n\nUm uns bei der Verbesserung der Software zu helfen, erstellen Sie bitte einen Fehlerbericht auf unserem Issue-Tracker auf GitHub (https://github.com/bisq-network/bisq/issues).\nDie Fehlermeldung wird in die Zwischenablage kopiert, wenn Sie auf die Schaltflächen unten klicken.\nEs wird das Debuggen einfacher machen, wenn Sie die bisq.log Datei anfügen.
popup.error.tryRestart=Versuchen Sie bitte Ihre Anwendung neu zu starten und überprüfen Sie Ihre Netzwerkverbindung um zu sehen, ob Sie das Problem beheben können.
popup.error.takeOfferRequestFailed=Es ist ein Fehler aufgetreten, als jemand versuchte eins Ihrer Angebote anzunehmen:\n{0}
@ -1781,9 +1783,9 @@ popup.warning.lockedUpFunds=Sie haben eingesperrte Gelder von einem fehlgeschlag
popup.warning.nodeBanned=Einer der {0} Knoten wurde gebannt. Bitte starten Sie die Anwendung neu, um sicher zu sein, nicht mit gebannten Knoten verbunden zu werden.
popup.warning.priceRelay=Preisrelais
popup.warning.Seed=Seed
popup.warning.seed=Seed
popup.info.securityDepositInfo=To ensure both traders follow the trade protocol, both traders need to pay a security deposit.\n\nThis deposit is kept in your trade wallet until your trade has been successfully completed, and then it's refunded to you.\n\nPlease note: if you're creating a new offer, Bisq needs to be running for another trader to take it. To keep your offers online, keep Bisq running and make sure this computer remains online too (i.e., make sure it doesn't switch to standby mode...monitor standby is fine).
popup.info.securityDepositInfo=Um sicherzustellen, dass beide Händler dem Handelsprotokoll folgen, müssen diese eine Kaution zahlen.\n\nDie Kaution bleibt in Ihrer lokalen Brieftasche, bis das Angebot von einem anderen Händler angenommen wurde.\nSie wird Ihnen zurückerstattet, nachdem der Handel erfolgreich abgeschlossen wurde.\n\nBitte beachten Sie, dass Sie die Anwendung laufen lassen müssen, wenn Sie ein offenes Angebot haben.\nWenn ein anderer Händler Ihr Angebot annehmen möchte ist es notwendig, dass Ihre Anwendung online ist und reagieren kann.\nStellen Sie sicher, dass Sie den Ruhezustand deaktiviert haben, da dieser Ihren Client vom Netzwerk trennen würde (Der Ruhezustand des Monitors ist kein Problem).
popup.info.cashDepositInfo=Stellen Sie sicher, dass eine Bank-Filiale in Ihrer Nähe befindet, um die Bargeld Kaution zu zahlen.\nDie Bankkennung (BIC/SWIFT) der Bank des Verkäufers ist: {0}.
popup.info.cashDepositInfo.confirm=Ich bestätige, dass ich die Kaution zahlen kann
@ -1805,6 +1807,9 @@ popup.attention.forTradeWithId=Der Handel mit der ID {0} benötigt Ihre Aufmerks
popup.roundedFiatValues.headline=Neues Privatsphären Feature: Gerundete fiat Beträge
popup.roundedFiatValues.msg=Um die Privatsphäre Ihres Handels zu erhöhen, wurde der {0} Betrag gerundet.\n\nAbhängig von der Version des Clients, werden Sie Beträge mit Nachkommastellen oder gerundet erhalten.\n\nBeide Beträge erfüllen von nun an das Handelsprotokoll.\n\nBeachten Sie auch, dass die BTC Beträge automatisch angepasst werden, um dem gerundeten fiat Betrag so genau wie möglich übereinzustimmen.
popup.info.multiplePaymentAccounts.headline=Multiple payment accounts available
popup.info.multiplePaymentAccounts.msg=You have multiple payment accounts available for this offer. Please make sure you've picked the right one.
####################################################################
# Notifications
@ -2059,7 +2064,7 @@ payment.national.account.id.AR=CBU Nummer
#new
payment.altcoin.address.dyn={0} Adresse
payment.altcoin.receiver.address=Receiver's altcoin address
payment.altcoin.receiver.address=Altcoin Adresse des Empfängers
payment.accountNr=Kontonummer
payment.emailOrMobile=E-Mail oder Telefonnr.
payment.useCustomAccountName=Spezifischen Kontonamen nutzen
@ -2085,7 +2090,7 @@ payment.clearXchange.info=\tStellen Sie bitte sicher, dass Sie die Voraussetzung
payment.moneyGram.info=Wenn MoneyGram verwendet wird, muss der BTC Käufer die MoneyGram und ein Foto der Quittung per E-Mail an den BTC-Verkäufer senden. Die Quittung muss den vollständigen Namen, das Land, das Bundesland des Verkäufers und den Betrag deutlich zeigen. Der Käufer bekommt die E-Mail-Adresse des Verkäufers im Handelsprozess angezeigt.
payment.westernUnion.info=Wenn Western Union verwendet wird, muss der BTC Käufer die MTCN (Tracking-Nummer) und ein Foto der Quittung per E-Mail an den BTC-Verkäufer senden. Die Quittung muss den vollständigen Namen, die Stadt, das Land des Verkäufers und den Betrag deutlich zeigen. Der Käufer bekommt die E-Mail-Adresse des Verkäufers im Handelsprozess angezeigt.
payment.halCash.info=Bei Verwendung von HalCash muss der BTC-Käufer dem BTC-Verkäufer den HalCash-Code per SMS vom Mobiltelefon senden.\n\nBitte achten Sie darauf, dass Sie den maximalen Betrag, den Sie bei Ihrer Bank mit HalCash versenden dürfen, nicht überschreiten. Der Mindestbetrag pro Auszahlung beträgt 10 EUR und der Höchstbetrag 600 EUR. Bei wiederholten Abhebungen sind es 3000 EUR pro Empfänger pro Tag und 6000 EUR pro Empfänger pro Monat. Bitte überprüfen Sie diese Limits bei Ihrer Bank, um sicherzustellen, dass sie die gleichen Limits wie hier angegeben verwenden.\n\nDer Auszahlungsbetrag muss ein Vielfaches von 10 EUR betragen, da Sie keine anderen Beträge an einem Geldautomaten abheben können. Die Benutzeroberfläche beim Erstellen und Annehmen eines Angebots passt den BTC-Betrag so an, dass der EUR-Betrag korrekt ist. Sie können keinen marktbasierten Preis verwenden, da sich der EUR-Betrag bei sich ändernden Preisen ändern würde.\n\n\nIm Streitfall muss der BTC-Käufer den Nachweis erbringen, dass er die EUR geschickt hat.
payment.halCash.info=Bei Verwendung von HalCash muss der BTC-Käufer dem BTC-Verkäufer den HalCash-Code per SMS vom Mobiltelefon senden.\n\nBitte achten Sie darauf, dass Sie den maximalen Betrag, den Sie bei Ihrer Bank mit HalCash versenden dürfen, nicht überschreiten. Der Mindestbetrag pro Auszahlung beträgt 10 EUR und der Höchstbetrag 600 EUR. Bei wiederholten Abhebungen sind es 3000 EUR pro Empfänger pro Tag und 6000 EUR pro Empfänger pro Monat. Bitte überprüfen Sie diese Limits bei Ihrer Bank, um sicherzustellen, dass sie die gleichen Limits wie hier angegeben verwenden.\n\nDer Auszahlungsbetrag muss ein Vielfaches von 10 EUR betragen, da Sie keine anderen Beträge an einem Geldautomaten abheben können. Die Benutzeroberfläche beim Erstellen und Annehmen eines Angebots passt den BTC-Betrag so an, dass der EUR-Betrag korrekt ist. Sie können keinen marktbasierten Preis verwenden, da sich der EUR-Betrag bei sich ändernden Preisen ändern würde.\n\nIm Streitfall muss der BTC-Käufer den Nachweis erbringen, dass er die EUR geschickt hat.
payment.limits.info=Beachten Sie bitte, dass alle Banküberweisungen ein gewisses Rückbuchungsrisiko mitbringen.\n\nUm diese Risiko zu minimieren, setzt Bisq vor-Handel Grenzen basierend auf zwei Faktoren:\n\n1. Das erwartete Rückbuchungsrisiko für die genutzte Zahlungsmethode\n2. Das Alter des Kontos für diese Zahlungsmethode\n\nDas Konto, das Sie jetzt erstellen, ist neu und sein Alter ist null. So wie Ihr Konto über zwei Monate altert, wächst auch Ihre vor-Handel Grenze:\n\n● Während des 1sten Monats, ist Ihre vor-Handel Grenze {0}\n● Während des 2ten Monats, ist Ihre vor-Handel Grenze {1}\n● Nach dem 2ten Monat, ist Ihre vor-Handel Grenze {2}\n\nBeachten Sie bitte, dass es keine Grenze, wie oft Sie handeln können.
payment.cashDeposit.info=Bitte bestätigen Sie, dass Ihre Bank Bareinzahlungen in Konten von anderen Personen erlaubt. Zum Beispiel werden diese Einzahlungen bei der Bank of America und Wells Fargo nicht mehr erlaubt.
@ -2280,4 +2285,4 @@ validation.amountBelowDust=Beträge unter dem Dust-Limit von {0} sind nicht erl
validation.length=Die Länge muss zwischen {0} und {1} sein
validation.pattern=Die Eingabe muss im Format {0} sein
validation.noHexString=Die Eingabe ist nicht im HEX-Format.
validation.advancedCash.invalidFormat=Must be a valid email or wallet id of format: X000000000000
validation.advancedCash.invalidFormat=Gültige E-Mail-Adresse oder Brieftaschen ID vom Format "X000000000000" benötigt

39
core/src/main/resources/i18n/displayStrings_el.properties
View file

@ -221,7 +221,7 @@ mainView.marketPriceWithProvider.label=Market price by {0}
mainView.marketPrice.bisqInternalPrice=Τιμή τελευταίας συναλλαγής Bisq
mainView.marketPrice.tooltip.bisqInternalPrice=Δεν υπάρχει διαθέσιμη τιμή αγοράς από εξωτερική πηγή.\nΗ εμφανιζόμενη τιμή είναι η τελευταία τιμή συναλλαγής αυτού του νομίσματος στο Bisq.
mainView.marketPrice.tooltip=Η τιμή αγοράς παρέχεται από το {0}{1}\nΤελευταία ενημέρωση: {2}\nΚόμβος URL παρόχου τιμής: {3}
mainView.marketPrice.tooltip.altcoinExtra=Εάν το altcoin δεν διατίθεται στο Poloniex, χρησιμοποιούμε το https://coinmarketcap.com
mainView.marketPrice.tooltip.altcoinExtra=Εάν το altcoin δεν διατίθεται στο Poloniex, χρησιμοποιούμε το https://coinmarketcap.com
mainView.balance.available=Διαθέσιμο υπόλοιπο
mainView.balance.reserved=Δεσμευμένα σε προσφορές
mainView.balance.locked=Κλειδωμένα σε συναλλαγές
@ -299,6 +299,8 @@ market.trades.tooltip.candle.date=Ημερομηνία:
offerbook.createOffer=Δημιουργία προσφοράς
offerbook.takeOffer=Αποδοχή προσφοράς
offerbook.takeOfferToBuy=Take offer to buy {0}
offerbook.takeOfferToSell=Take offer to sell {0}
offerbook.trader=Συναλλασσόμενος
offerbook.offerersBankId=Ταυτότητα τράπεζας Maker (BIC/SWIFT): {0}
offerbook.offerersBankName=Όνομα τράπεζας Maker: {0}
@ -365,7 +367,7 @@ createOffer.fundsBox.title=Χρηματοδότησε την προσφορά σ
createOffer.fundsBox.offerFee=Προμήθεια συναλλαγής
createOffer.fundsBox.networkFee=Mining fee
createOffer.fundsBox.placeOfferSpinnerInfo=Κοινοποίηση προσφοράς σε εξέλιξη...
createOffer.fundsBox.paymentLabel=Συναλλαγή Bisq με ταυτότητα {0}
createOffer.fundsBox.paymentLabel=Συναλλαγή Bisq με ταυτότητα {0}
createOffer.fundsBox.fundsStructure=({0} ποσό εγγύησης, {1} προμήθεια συναλλαγής, {2} αμοιβή εξόρυξης)
createOffer.success.headline=Η προσφορά σου έχει κοινοποιηθεί
createOffer.success.info=Μπορείς να διαχειριστείς τις ανοιχτές προσφορές σου στο \"Χαρτοφυλάκιο/Οι τρέχουσες προσφορές μου\".
@ -424,7 +426,7 @@ takeOffer.fundsBox.tradeAmount=Amount to sell
takeOffer.fundsBox.offerFee=Προμήθεια συναλλαγής
takeOffer.fundsBox.networkFee=Total mining fees
takeOffer.fundsBox.takeOfferSpinnerInfo=Αποδοχή προσφοράς σε εξέλιξη...
takeOffer.fundsBox.paymentLabel=Συναλλαγή Bisq με ταυτότητα {0}
takeOffer.fundsBox.paymentLabel=Συναλλαγή Bisq με ταυτότητα {0}
takeOffer.fundsBox.fundsStructure=({0} ποσό εγγύησης, {1} προμήθεια συναλλαγής, {2} αμοιβή εξόρυξης)
takeOffer.success.headline=Αποδέχτηκες επιτυχώς μία προσφορά.
takeOffer.success.info=Μπορείς να δεις την κατάσταση της συναλλαγής στο \"Χαρτοφυλάκιο/Τρέχουσες συναλλαγές\".
@ -553,19 +555,19 @@ message.state.ACKNOWLEDGED=Ο συναλλασσόμενος επιβεβαίω
message.state.FAILED=Αποτυχία αποστολής μηνύματος
portfolio.pending.step3_buyer.wait.headline=Αναμονή για την επιβεβαίωση της πληρωμής από τον πωλητή BTC
portfolio.pending.step3_buyer.wait.info=Αναμονή για την επιβεβαίωση της απόδειξης της πληρωμής {0} από τον πωλητή BTC.
portfolio.pending.step3_buyer.wait.info=Αναμονή για την επιβεβαίωση της απόδειξης της πληρωμής {0} από τον πωλητή BTC.
portfolio.pending.step3_buyer.wait.msgStateInfo.label=Payment started message status
portfolio.pending.step3_buyer.warn.part1a=στο blockchain {0}
portfolio.pending.step3_buyer.warn.part1b=στον πάροχο υπηρεσιών πληρωμής (π.χ. τράπεζα)
portfolio.pending.step3_buyer.warn.part2=Ο πωλητής BTC δεν έχει επιβεβαιώσει ακόμα την πληρωμή σου!\nΈλεγξε {0} αν υπήρξε επιτυχής πληρωμή.\nΑν ο πωλητής BTC δεν επιβεβαιώσει την απόδειξη της πληρωμής σου μέχρι την {1}, η συναλλαγή θα διερευνηθεί από τον διαμεσολαβητή.
portfolio.pending.step3_buyer.openForDispute=Ο πωλητής BTC δεν επιβεβαίωσε την πληρωμή σου!\nΗ μέγιστη χρονική περίοδος συναλλαγής παρήλθε.\nΜπορείς να περιμένεις περισσότερο και να δώσεις επιπλέον χρόνο στον έτερο συναλλασσόμενο ή μπορείς να επικοινωνήσεις με τον διαμεσολαβητή και να ξεκινήσεις επίλυση διένεξης.
# suppress inspection "TrailingSpacesInProperty"
portfolio.pending.step3_seller.part=Ο συναλλασσόμενος επιβεβαίωσε πως ξεκίνησε την πληρωμή {0}.\n\n
portfolio.pending.step3_seller.part=Your trading partner has confirmed that they have initiated the {0} payment.\n\n
portfolio.pending.step3_seller.altcoin.explorer=on your favorite {0} blockchain explorer
portfolio.pending.step3_seller.altcoin.wallet=at your {0} wallet
portfolio.pending.step3_seller.altcoin={0}Please check {1} if the transaction to your receiving address\n{2}\nhas already sufficient blockchain confirmations.\nThe payment amount has to be {3}\n\nYou can copy & paste your {4} address from the main screen after closing that popup.
portfolio.pending.step3_seller.postal={0}Έλεγξε αν παρέλαβες {1} μέσω \"US Postal Money Order\" από τον αγοραστή BTC.\n\nΗ ταυτότητα (ID) συναλλαγής (πεδίο \"reason for payment\") είναι: \"{2}\"
portfolio.pending.step3_seller.bank=Ο έτερος συναλλασσόμενος επιβεβαίωσε την έναρξη της πληρωμής {0}.\n\nΣυνδέσου στον e-banking λογαριασμό σου και έλεγξε αν έχεις παραλάβει {1} από τον αγοραστή BTC.\n\nΗ ταυτότητα συναλλαγής (πεδίο \"reason for payment\") στη συναλλαγή είναι: \"{2}\"\n
portfolio.pending.step3_seller.bank=Your trading partner has confirmed that they have initiated the {0} payment.\n\nPlease go to your online banking web page and check if you have received {1} from the BTC buyer.\n\nThe trade ID (\"reason for payment\" text) of the transaction is: \"{2}\"\n\n
portfolio.pending.step3_seller.cash=Because the payment is done via Cash Deposit the BTC buyer has to write \"NO REFUND\" on the paper receipt, tear it in 2 parts and send you a photo by email.\n\nTo avoid chargeback risk, only confirm if you received the email and if you are sure the paper receipt is valid.\nIf you are not sure, {0}
portfolio.pending.step3_seller.moneyGram=Ο αγοραστής θα πρέπει να σου στείλει τον αριθμό Έγκρισης (Authorisation) και μία φωτογραφία της απόδειξης μέσω email.\nΣτην απόδειξη θα πρέπει να διακρίνεται καθαρά το πλήρες όνομά σου, η χώρα, η πόλη και το ποσό. Έλεγξε αν στα email σου έχεις λάβει τον αριθμό Έγκρισης.\n\nΑφού κλείσεις αυτό το αναδυόμενο παράθυρο θα δεις το όνομα και τη διεύθυνση του αγοραστή BTC, ώστε να λάβεις τα χρήματα από την MoneyGram.\n\nΕπιβεβαίωσε την απόδειξη μονάχα αφού εισπράξεις τα χρήματα!
portfolio.pending.step3_seller.westernUnion=Ο αγοραστής θα πρέπει να σου στείλει τον αριθμό MTCN (αριθμός εντοπισμού) και μία φωτογραφία της απόδειξης μέσω email.\nΣτην απόδειξη θα πρέπει να διακρίνεται καθαρά το πλήρες όνομά σου, η πόλη, η χώρα και το ποσό. Έλεγξε αν στα email σου έχεις λάβει το MTCN.\n\nΑφού κλείσεις αυτό το αναδυόμενο παράθυρο θα δεις το όνομα και τη διεύθυνση του αγοραστή BTC, ώστε να λάβεις τα χρήματα από την Western Union.\n\nΕπιβεβαίωσε την απόδειξη μονάχα αφού εισπράξεις τα χρήματα!
@ -685,7 +687,7 @@ funds.withdrawal.feeExcluded=Το ποσό δεν περιλαμβάνει τη
funds.withdrawal.feeIncluded=Το ποσό περιλαμβάνει την αμοιβή εξόρυξης
funds.withdrawal.fromLabel=Withdraw from address
funds.withdrawal.toLabel=Withdraw to address
funds.withdrawal.withdrawButton=Επιλέχθηκε η ανάληψη
funds.withdrawal.withdrawButton=Επιλέχθηκε η ανάληψη
funds.withdrawal.noFundsAvailable=Δεν υπάρχουν διαθέσιμα κεφάλαια προς ανάληψη
funds.withdrawal.confirmWithdrawalRequest=Επιβεβαίωση αίτησης ανάληψης
funds.withdrawal.withdrawMultipleAddresses=Ανάληψη από πολλαπλές διευθύνσεις ({0})
@ -859,7 +861,7 @@ settings.net.peer=Peer
settings.net.inbound=εισερχόμενα
settings.net.outbound=εξερχόμενα
settings.net.reSyncSPVChainLabel=Επανασυγχρονισμός αλυσίδας SPV
settings.net.reSyncSPVChainButton=Διάγραψε το αρχείο SPV και επανασυγχρονίσου
settings.net.reSyncSPVChainButton=Διάγραψε το αρχείο SPV και επανασυγχρονίσου
settings.net.reSyncSPVSuccess=The SPV chain file will be deleted on the next startup. You need to restart your application now.\n\nAfter the restart it can take a while to resync with the network and you will only see all transactions once the resync is completed.\n\nPlease restart again after the resync has completed because there are sometimes inconsistencies that result in incorrect balances to display.
settings.net.reSyncSPVAfterRestart=The SPV chain file has been deleted. Please be patient. It can take a while to resync with the network.
settings.net.reSyncSPVAfterRestartCompleted=Ο επανασυγχρονισμός ολοκληρώθηκε. Επανεκκίνησε την εφαρμογή.
@ -926,10 +928,10 @@ account.arbitratorSelection.minOne=Πρέπει να επιλέξεις τουλ
account.altcoin.yourAltcoinAccounts=Your altcoin accounts
account.altcoin.popup.wallet.msg=Please be sure that you follow the requirements for the usage of {0} wallets as described on the {1} web page.\nUsing wallets from centralized exchanges where (a) you don''t control your keys or (b) which don''t use compatible wallet software is risky: it can lead to loss of the traded funds!\nThe arbitrator is not a {2} specialist and cannot help in such cases.
account.altcoin.popup.wallet.confirm=Κατανοώ και επιβεβαιώνω πως γνωρίζω ποιο πορτοφόλι πρέπει να χρησιμοποιήσω.
account.altcoin.popup.xmr.msg=If you want to trade XMR on Bisq please be sure you understand and fulfill the following requirements:\n\nFor sending XMR you need to use either the official Monero GUI wallet or Monero CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nmonero-wallet-cli (use the command get_tx_key)\nmonero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nIn addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\nmonero-wallet-cli : using command (check_tx_key).\nmonero-wallet-gui : on the Advanced > Prove/Check page.\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the 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\nIf you cannot provide the above data or if you used an incompatible wallet it would result in losing the dispute case. The XMR sender is responsible to be able to verify the XMR 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 (https://www.getmonero.org/resources/user-guides/prove-payment.html) or the Monero forum (https://forum.getmonero.org) to find more information.
account.altcoin.popup.blur.msg=If you want to trade BLUR on Bisq please be sure 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 arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nIf you cannot provide the required information to the arbitrator, you will lose the dispute. In all cases of dispute, the BLUR sender bears 100% of the burden of responsiblity in verifying transactions to an arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW).
account.altcoin.popup.ccx.msg=If you want to trade CCX on Bisq please be sure you understand the following requirements:\n\nTo send CCX you must use an official Conceal wallet, either CLI or GUI. After sending a transfer payment, the wallets\ndisplay the transaction secret key. You must save it along with the transaction hash (ID) and the recipient's public\naddress in case arbitration is necessary. In such a case, you must give all three to the arbitrator, who will then\nverify the CCX transfer using the Conceal Transaction Viewer (https://explorer.conceal.network/txviewer).\nBecause Conceal is a privacy coin, block explorers cannot verify transfers.\n\nIf you cannot provide the required data to the arbitrator, you will lose the dispute case.\nIf you do not save the transaction secret key immediately after transferring CCX, it cannot be recovered later.\nIf you do not understand these requirements, seek help at the Conceal discord (http://discord.conceal.network).
account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides a transaction is not verifyable on the public blockchain. If required you can prove your payment thru use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at \ (http://drgl.info/#check_txn).\n\nIf you cannot provide the above data or if you used an incompatible wallet it would result in losing the dispute case. The Dragonglass sender is responsible to be able to verify the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help.
account.altcoin.popup.xmr.msg=Trading XMR on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending XMR, you need to use either the official Monero GUI wallet or Monero CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nmonero-wallet-cli (use the command get_tx_key)\nmonero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nIn addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\nmonero-wallet-cli : using command (check_tx_key).\nmonero-wallet-gui : on the Advanced > Prove/Check page.\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The XMR sender is responsible for providing verification of the XMR transfer to the arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) or the Monero forum (https://forum.getmonero.org) to find more information.
account.altcoin.popup.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 arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The 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 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 arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW).
account.altcoin.popup.ccx.msg=Trading CCX on Bisq requires that you understand the following requirements:\n\nTo send CCX you must use an official Conceal wallet, either CLI or GUI. After sending a transfer payment, the wallets\ndisplay the transaction secret key. You must save it along with the transaction hash (ID) and the recipient's public\naddress in case arbitration is necessary. In such a case, you must give all three to the arbitrator, who will then\nverify the CCX transfer using the Conceal Transaction Viewer (https://explorer.conceal.network/txviewer).\nBecause Conceal is a privacy coin, block explorers cannot verify transfers.\n\nFailure to provide the required data to the arbitrator will result in losing the dispute case.\nIf you do not save the transaction secret key immediately after transferring CCX, it cannot be recovered later.\nIf you do not understand these requirements, seek help at the Conceal discord (http://discord.conceal.network).
account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides, a transaction is not verifiable on the public blockchain. If required, you can prove your payment through the use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at (http://drgl.info/#check_txn).\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The Dragonglass sender is responsible for providing verification of the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help.
account.altcoin.popup.ZEC.msg=Όταν χρησιμοποιείς {0} μπορείς να χρησιμοποιήσεις μονάχα τη διάφανη διεύθυνση (ξεκινά με t), και όχι την z διεύθυνση (ιδιωτική), καθώς ο διαμεσολαβητής δεν θα μπορεί να επαληθεύσει τη συναλλαγή μέσω της z διεύθυνσης.
account.altcoin.popup.XZC.msg=Όταν χρησιμοποιείς {0} μπορείς να χρησιμοποιήσεις μονάχα τη διάφανη (ανιχνεύσιμη) διεύθυνση, και όχι τη μη ανιχνεύσιμη διεύθυνση, καθώς ο διαμεσολαβητής δεν θα μπορεί να επαληθεύσει τη συναλλαγή με μη ανιχνεύσιμες διευθύνσεις στον block explorer.
account.altcoin.popup.bch=Τα Bitcoin Cash και Bitcoin Clashic δεν διαθέτουν προστασία επανάληψης (replay protection). Αν χρησιμοποιείς αυτά τα νομίσματα απαιτείται να λάβεις επαρκείς προφυλάξεις και να κατανοείς όλες τις πιθανές επιπτώσεις. Η ακούσια αποστολή σε άλλο blockchain κατά την μετακίνηση νομισμάτων, ενδέχεται να οδηγήσει σε απώλειες κεφαλαίων. Καθώς αυτά τα νομίσματα μοιράζονται το ίδιο ιστορικό με το blockchain του Bitcoin, εμπεριέχουν κινδύνους ασφαλείας και απώλειας εχεμύθειας.\n\nΔιάβασε περισσότερα στο φόρουμ του Bisq: https://forum.bisq.io/t/airdrop-coins-information-thread-bch-btg-bchc
@ -1306,7 +1308,7 @@ dao.burnBsq.assets.lookBackPeriod=Verification period
dao.burnBsq.assets.trialFee=Fee for trial period
dao.burnBsq.assets.totalFee=Total fees paid
dao.burnBsq.assets.days={0} days
dao.burnBsq.assets.toFewDays=The asset fee is too low. The min. amount of days for the trial perios is {0}.
dao.burnBsq.assets.toFewDays=The asset fee is too low. The min. amount of days for the trial period is {0}.
# suppress inspection "UnusedProperty"
dao.assetState.UNDEFINED=Ακαθόριστο
@ -1584,7 +1586,7 @@ displayUpdateDownloadWindow.verify.failed=Αποτυχία επαλήθευση
displayUpdateDownloadWindow.success=Η νέα έκδοση αποθηκεύτηκε επιτυχώς και η υπογραφή επαληθεύτηκε.\n\nΆνοιξε το φάκελο αποθήκευσης, κλείσε την εφαρμογή και εγκατάστησε τη νέα έκδοση.
displayUpdateDownloadWindow.download.openDir=Άνοιγμα καταλόγου λήψης
disputeΠερίληψηWindow.title=Περίληψη
disputeSummaryWindow.title=Περίληψη
disputeSummaryWindow.openDate=Ticket opening date
disputeSummaryWindow.role=Trader's role
disputeSummaryWindow.evidence=Evidence
@ -1746,7 +1748,7 @@ popup.headline.error=Σφάλμα
popup.doNotShowAgain=Ακύρωση επανεμφάνισης
popup.reportError.log=Άνοιγμα αρχείου log
popup.reportError.gitHub=Ανάφερε στο GitHub issue tracker
popup.reportError={0}\n\nTo help us to improve the software please report the bug on our issue tracker on GitHub (https://github.com/bisq-network/bisq-desktop/issues).\nThe error message will be copied to the clipboard when you click a button below.\nIt will make debugging easier if you can attach the bisq.log file as well.
popup.reportError={0}\n\nTo help us to improve the software please report this bug by opening a new issue at https://github.com/bisq-network/bisq/issues.\nThe above error message will be copied to the clipboard when you click either of the buttons below.\nIt will make debugging easier if you include the bisq.log file by pressing "Open log file", saving a copy, and attaching it to your bug report.
popup.error.tryRestart=Επανεκκίνησε την εφαρμογή και έλεγξε τη σύνδεση δικτύου, ώστε να επιλυθεί το πρόβλημα.
popup.error.takeOfferRequestFailed=Προέκυψε σφάλμα κατά την αποδοχή της προσφοράς σου.\n\n{0}
@ -1805,6 +1807,9 @@ popup.attention.forTradeWithId=Απαιτείται προσοχή σχετικ
popup.roundedFiatValues.headline=New privacy feature: Rounded fiat values
popup.roundedFiatValues.msg=To increase privacy of your trade the {0} amount was rounded.\n\nDepending on the client version you''ll pay or receive either values with decimals or rounded ones.\n\nBoth values do comply from now on with the trade protocol.\n\nAlso be aware that BTC values are changed automatically to match the rounded fiat amount as close as possible.
popup.info.multiplePaymentAccounts.headline=Multiple payment accounts available
popup.info.multiplePaymentAccounts.msg=You have multiple payment accounts available for this offer. Please make sure you've picked the right one.
####################################################################
# Notifications
@ -2085,7 +2090,7 @@ payment.clearXchange.info=Please be sure that you fulfill the requirements for t
payment.moneyGram.info=Όταν χρησιμοποιείς MoneyGram, ο αγοραστής BTC πρέπει να στείλει μέσω email αριθμό Έγκρισης (Authorisation) και φωτογραφία της απόδειξης στον πωλητή. Στην απόδειξη θα πρέπει να διακρίνεται καθαρά Στην απόδειξη θα πρέπει να διακρίνεται καθαρά το πλήρες όνομα του πωλητή, η χώρα, η πόλη και το ποσό. Το email του πωλητή θα δοθεί στον αγοραστή κατά τη διαδικασία συναλλαγής.
payment.westernUnion.info=Όταν χρησιμοποιείς Western Union, ο αγοραστής BTC πρέπει να στείλει μέσω email το MTCN (αριθμός εντοπισμού) και φωτογραφία της απόδειξης στον πωλητή. Στην απόδειξη θα πρέπει να διακρίνεται καθαρά Στην απόδειξη θα πρέπει να διακρίνεται καθαρά το πλήρες όνομα του πωλητή, η χώρα, η πόλη και το ποσό. Το email του πωλητή θα δοθεί στον αγοραστή κατά τη διαδικασία συναλλαγής.
payment.halCash.info=When using HalCash the BTC buyer need to send the BTC seller the HalCash code via a text message from the mobile phone.\n\nPlease make sure to not exceed the maximum amount your bank allows you to send with HalCash. The min. amount per withdrawal is 10 EUR and the max. amount is 600 EUR. For repeated withdrawals it is 3000 EUR per receiver per day and 6000 EUR per receiver per month. Please cross check those limits with your bank to be sure they use the same limits as stated here.\n\nThe withdrawal amount must be a multiple of 10 EUR as you cannot withdraw other amounts from an ATM. The UI in the create-offer and take-offer screen will adjust the BTC amount so that the EUR amount is correct. You cannot use market based price as the EUR amount would be changing with changing prices.\n\nIn case of a dispute the BTC buyer need to provide the proof that he sent the EUR.
payment.halCash.info=When using HalCash the BTC buyer needs to send the BTC seller the HalCash code via a text message from their mobile phone.\n\nPlease make sure to not exceed the maximum amount your bank allows you to send with HalCash. The min. amount per withdrawal is 10 EUR and the max. amount is 600 EUR. For repeated withdrawals it is 3000 EUR per receiver per day and 6000 EUR per receiver per month. Please cross check those limits with your bank to be sure they use the same limits as stated here.\n\nThe withdrawal amount must be a multiple of 10 EUR as you cannot withdraw other amounts from an ATM. The UI in the create-offer and take-offer screen will adjust the BTC amount so that the EUR amount is correct. You cannot use market based price as the EUR amount would be changing with changing prices.\n\nIn case of a dispute the BTC buyer needs to provide the proof that they sent the EUR.
payment.limits.info=Λάβε υπόψιν πως όλες οι συναλλαγές μέσω τραπεζών περιέχουν ρίσκο αντιλογισμού χρέωσης.\n\nΓια να μετριάσει το ρίσκο, το Bisq θέτει όρια ανά συναλλαγή βασισμένα σε δύο παράγοντες:\n\n1. Τις πιθανότητες να συμβεί αντιλογισμός χρέωσης για τη μέθοδο πληρωμής που χρησιμοποιείται\n2. Την ηλικία λογαριασμού για αυτή τη μέθοδο πληρωμής.\n\nΟ λογαριασμός που δημιουργείς τώρα είναι καινούργιος και η ηλικία του είναι μηδέν. Καθώς η ηλικία του λογαριασμού σου θα μεγαλώνει, τα όρια ανά συναλλαγή θα αυξάνονται ως εξής:\n\n● Κατά τον 1ο μήνα το όριο ανά συναλλαγή θα είναι {0}\n● Κατά το 2ο μήνα το όριο ανά συναλλαγή θα είναι {1}\n● Μετά το 2ο μήνα το όριο ανά συναλλαγή θα είναι {2}\n\nΣημείωσε πως δεν υπάρχει όριο στο συνολικό πλήθος συναλλαγών.
payment.cashDeposit.info=Please confirm your bank allows you to send cash deposits into other peoples' accounts. For example, Bank of America and Wells Fargo no longer allow such deposits.
@ -2098,7 +2103,7 @@ payment.f2f.optionalExtra=Προαιρετικές πρόσθετες πληρο
payment.f2f.extra=Πρόσθετες πληροφορίες
payment.f2f.extra.prompt=Ο maker μπορεί να ορίσει "όρους και προϋποθέσεις" ή να συμπεριλάβει κάποια πληροφορία επαφής. Αυτά θα εμφανιστούν στην προσφορά.
payment.f2f.info="Κατά πρόσωπο" συναλλαγές διέπονται από διαφορετικούς κανόνες και ενέχουν διαφορετικούς κινδύνους από διαδικτυακές συναλλαγές.\n\nΟι βασικές διαφορές είναι:\n\n● Οι συναλλασσόμενοι απαιτείται να ανταλλάξουν πληροφορίες σχετικές με το σημείο και την ώρα συνάντησης μέσω των παρεχόμενων στοιχείων επικοινωνίας.\n● Οι συναλλασσόμενοι απαιτείται να φέρουν τους φορητούς τους υπολογιστές και να προβούν σε επιβεβαίωση της αποστολής και λήψης πληρωμής στο σημείο συνάντησης.\n● Αν ο maker έχει ειδικούς "όρους και προϋποθέσεις", απαιτείται να τους δηλώσει στο πεδίο "Πρόσθετες πληροφορίες" του λογαριασμού.\n● Αποδεχόμενος μια προσφορά ο taker συμφωνεί με τους δηλωμένους "όρους και προϋποθέσεις" του maker.\n● Σε περίπτωση διένεξης ο διαμεσολαβητής δεν μπορεί να βοηθήσει σημαντικά, καθώς είναι δύσκολο να λάβει αδιάσειστα στοιχεία του τι συνέβη κατά τη συνάντηση. Σε αυτές τις περιπτώσεις τα κεφάλαια BTC ίσως κλειδωθούν δια παντός ή έως ότου οι συναλλασσόμενοι έρθουν σε συμφωνία.\n\nΣιγουρέψου πως κατανοείς πλήρως τις διαφορές των "κατά πρόσωπο" συναλλαγών μέσω των οδηγιών και των προτάσεων στο: 'https://docs.bisq.network/trading-rules.html#f2f-trading'
payment.f2f.info='Face to Face' trades have different rules and come with different risks than online transactions.\n\nThe main differences are:\n● The trading peers need to exchange information about the meeting location and time by using their provided contact details.\n● The trading peers need to bring their laptops and do the confirmation of 'payment sent' and 'payment received' at the meeting place.\n● If a maker has special 'terms and conditions' they must state those in the 'Additional information' text field in the account.\n● By taking an offer the taker agrees to the maker's stated 'terms and conditions'.\n● In case of a dispute the arbitrator cannot help much as it is usually hard to get tamper proof evidence of what happened at the meeting. In such cases the BTC funds might get locked indefinitely or until the trading peers come to an agreement.\n\nTo be sure you fully understand the differences with 'Face to Face' trades please read the instructions and recommendations at: 'https://docs.bisq.network/trading-rules.html#f2f-trading'
payment.f2f.info.openURL=Άνοιγμα ιστοσελίδας
payment.f2f.offerbook.tooltip.countryAndCity=Νομός και πόλη: {0} / {1}
payment.f2f.offerbook.tooltip.extra=Πρόσθετες πληροφορίες: {0}

89
core/src/main/resources/i18n/displayStrings_es.properties
View file

@ -46,7 +46,7 @@ shared.buyingCurrency=comprando {0} (Vendiendo BTC)
shared.sellingCurrency=Vendiendo {0} (comprando BTC)
shared.buy=comprar
shared.sell=vender
shared.buying=Comprando
shared.buying=Comprando
shared.selling=Vendiendo
shared.P2P=P2P
shared.oneOffer=oferta
@ -73,11 +73,11 @@ shared.details=Detalles
shared.address=Dirección
shared.balanceWithCur=Balance en {0}
shared.txId=ID de la transacción
shared.confirmations=Confirmaciones
shared.confirmations=Confirmaciones
shared.revert=Revertir Tx
shared.select=Seleccionar
shared.usage=Uso
shared.state=Estado
shared.state=Estado
shared.tradeId=ID de intercambio
shared.offerId=ID de oferta
shared.bankName=Nombre del banco
@ -106,7 +106,7 @@ shared.enterPercentageValue=Introduzca valor %
shared.OR=ó
shared.notEnoughFunds=No tiene suficientes fondos en su monedero Bisq.\nNecesita {0} pero tiene sólo {1} en su monedero Bisq.\n\nPor favor deposite desde un monedero Bitcoin externo o agregue fondos a su monedero Bisq en \"Fondos/Depositar fondos\".
shared.waitingForFunds=Esperando fondos...
shared.depositTransactionId=ID deposito de la transacción
shared.depositTransactionId=ID deposito de la transacción
shared.TheBTCBuyer=El comprador de BTC
shared.You=Usted
shared.reasonForPayment=Concepto de pago
@ -193,9 +193,9 @@ shared.all=Todos
shared.edit=Editar
shared.advancedOptions=Opciones avanzadas
shared.interval=Intervalo
shared.actions=Actions
shared.buyerUpperCase=Buyer
shared.sellerUpperCase=Seller
shared.actions=Acciones
shared.buyerUpperCase=Comprador
shared.sellerUpperCase=Vendedor
####################################################################
# UI views
@ -233,7 +233,7 @@ mainView.footer.localhostBitcoinNode=(localhost)
mainView.footer.btcInfo=Pares de red Bitcoin: {0} / {1} {2}
mainView.footer.btcInfo.initializing=Iniciando
mainView.footer.btcInfo.synchronizedWith=Sincronizado con
mainView.footer.btcInfo.connectingTo=Conectando a
mainView.footer.btcInfo.connectingTo=Conectando a
mainView.footer.btcInfo.connectionFailed=Conexión fallida
mainView.footer.p2pInfo=Pares de red P2P: {0}
@ -299,6 +299,8 @@ market.trades.tooltip.candle.date=Fecha:
offerbook.createOffer=Crear oferta
offerbook.takeOffer=Tomar oferta
offerbook.takeOfferToBuy=Take offer to buy {0}
offerbook.takeOfferToSell=Take offer to sell {0}
offerbook.trader=Trader
offerbook.offerersBankId=ID del banco del creador (BIC/SWIFT): {0}
offerbook.offerersBankName=Nombre del banco del creador: {0}
@ -400,7 +402,7 @@ createOffer.resetToDefault=No, restablecer al valor por defecto
createOffer.useLowerValue=Sí, usar mi valor más bajo
createOffer.priceOutSideOfDeviation=El precio que ha introducido está fuera de la máxima desviación permitida en relación al precio de mercado.\nLa desviación máxima permitida es {0} y puede ajustarse en las preferencias.
createOffer.changePrice=Cambiar precio
createOffer.tac=Al colocar esta oferta estoy de acuerdo en comerciar con cualquier comerciante que cumpla con las condiciones definidas anteriormente.
createOffer.tac=Al colocar esta oferta estoy de acuerdo en comerciar con cualquier comerciante que cumpla con las condiciones definidas anteriormente.
createOffer.currencyForFee=Tasa de transacción
createOffer.setDeposit=Establecer depósito de seguridad del comprador
@ -531,12 +533,12 @@ portfolio.pending.step2_buyer.halCashInfo.msg=Necesita enviar un mensaje de text
portfolio.pending.step2_buyer.fasterPaymentsHolderNameInfo=Algunos bancos pueden requerir el nombre del receptor. El sort code de UK y el número de cuenta es suficiente para una transferecnia Faster Payment y el nombre del receptor no es verificado por ninguno de los bancos.
portfolio.pending.step2_buyer.confirmStart.headline=Confirme que ha comenzado el pago.
portfolio.pending.step2_buyer.confirmStart.msg=Ha iniciado el pago de {0} a su par de intercambio?
portfolio.pending.step2_buyer.confirmStart.yes=Sí, lo he iniciado.
portfolio.pending.step2_buyer.confirmStart.yes=Sí, lo he iniciado.
portfolio.pending.step2_seller.waitPayment.headline=Esperar al pago.
portfolio.pending.step2_seller.f2fInfo.headline=Información de contacto del comprador
portfolio.pending.step2_seller.waitPayment.msg=La transacción del depósito tiene al menos una confirmación en la cadena de bloques.\nTien que esperar hasta que el comprador de BTC comience el pago de {0}.
portfolio.pending.step2_seller.warn=The BTC buyer still has not done the {0} payment.\nYou need to wait until they have started the payment.\nIf the trade has not been completed on {1} the arbitrator will investigate.
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 árbitro para abrir una disputa.
# suppress inspection "UnusedProperty"
@ -565,7 +567,7 @@ portfolio.pending.step3_seller.altcoin.explorer=en su explorador de cadena de bl
portfolio.pending.step3_seller.altcoin.wallet=en su monedero {0}
portfolio.pending.step3_seller.altcoin={0}Por favor compruebe {1} si la transacción a su dirección de recepción\n{2}\ntiene suficientes confirmaciones en la cadena de bloques.\nLa cantidad a pagar tiene que ser {3}\n\nPuede copiar y pegar su dirección {4} desde la pantalla principal después de cerrar este popup.
portfolio.pending.step3_seller.postal={0}Por favor, compruebe si ha recibido {1} con \"US Postal Money Order\"desde el comprador de BTC.\n\nLa ID de intercambio (el texto \"reason for payment\") de la transacción es: \"{2}\"
portfolio.pending.step3_seller.bank=Su compañero en intercambio ha confirmado que inició el pago de {0}.\n\nPor favor vaya a su página web de banco en línea y verifique si recibió {1} del comprador de BTC.\n\nEl ID de transacción (\"reason for payment\" text) es: \"{2}\"\n
portfolio.pending.step3_seller.bank=Su par de intercambio ha confirmado haber iniciado el pago de {0}.\n\nPor favor, vaya a la web de su banco y compruebe si ha recibido {1} desde la cuenta del comprador de BTC.\nLa ID de intercambio (texto \"razón de pago\") de la transacción es: \"{2}\"
portfolio.pending.step3_seller.cash=Debido a que el pago se hecho vía depósito en efectivo el comprador de BTC tiene que escribir \"SIN REEMBOLSO\" en el recibo de papel, dividirlo en 2 partes y enviarte una foto por e-mail.\n\nPara impedir el riesgo de chargeback, confirme que todo está bien sólo si ha recibido el e-mail y si está seguro de que el recibo es válido.\nSi no está seguro, {0}
portfolio.pending.step3_seller.moneyGram=El comprador tiene que enviarle el número de autorización y una foto del recibo por correo electrónico.\n\nEl recibo debe mostrar claramente el monto, asi como su nombre completo, país y demarcación (departamento,estado, etc.). Por favor revise su correo electrónico si recibió el número de autorización.\n\nDespués de cerrar esa ventana emergente (popup), verá el nombre y la dirección del comprador de BTC para retirar el dinero de MoneyGram.\n\n¡Solo confirme el recibo de transacción después de haber obtenido el dinero con éxito!
portfolio.pending.step3_seller.westernUnion=El comprador htiene que enviarle el MTCN (número de seguimiento) y una foto de el recibo por email.\nEl recibo debe mostrar claramente su nombre completo, ciudad, país y la cantidad. Por favor compruebe su email y si ha recibido el MTCN.\n\nDespués de cerrar ese popup verá el nombre del comprador de BTC y la dirección para recoger el dinero de Western Union.\n\nConfirme el recibo después de haber recogido satisfactoriamente el dinero!
@ -721,7 +723,7 @@ funds.tx.noTxAvailable=Sin transacciones disponibles
funds.tx.revert=Revertir
funds.tx.txSent=La transacción se ha enviado exitosamente a una nueva dirección en la billetera Bisq local.
funds.tx.direction.self=Enviado a usted mismo
funds.tx.daoTxFee=Miner fee for DAO tx
funds.tx.daoTxFee=Tasa de minaod para la tx DAO
funds.tx.reimbursementRequestTxFee=Requerimiento de reembolso
funds.tx.compensationRequestTxFee=Petición de compensación
@ -765,9 +767,9 @@ support.buyerOfferer= comprador/creador BTC
support.sellerOfferer=vendedor/creador BTC
support.buyerTaker=comprador/Tomador BTC
support.sellerTaker=vendedor/Tomador BTC
support.backgroundInfo=Bisq is not a company, so it handles disputes differently.\n\nIf there are disputes in the trade process (e.g. one trader does not follow the trade protocol) the application will display an \"Open dispute\" button after the trade period is over for contacting the arbitrator.\n\nIf there is an issue with the application, the software will try to detect it and, if possible, display an \"Open support ticket\" button to contact the arbitrator who will forward the issue to the developers.\n\nIf you are having an issue and did not see the \"Open support ticket\" button, you can open a support ticket manually by selecting the trade causing issues under \"Portfolio/Open trades\" and hitting \"alt + o\" or \"option + o\". Please use this method only if you are sure that the software is not working as expected. If you have problems or questions, please review the FAQ on the bisq.network web page or post in the Bisq forum in the Support section.
support.backgroundInfo=Bisq no es una compañía, con lo que maneja las disputas de una forma diferente.\n\nSi hay disputas en el proceso de intercambio (v.g. un trader no sigue el protocolo de intercambio) la aplicación mostrará un botón de \"Abrir disputa\" después de que el periodo de intecambio haya finalizado para contactar con el árbitro.\n\nSi hay algún problema con la aplicación, el software intentará detectarlo y, si es posible, mostrará el botón \"Abrir ticket de soporte\" para contactar con el árbitro, que enviará el problema a los desarrolladores.\n\nSi tiene algún problema y no ve el botón \"Abrir ticket de soporte\" puede abrir un ticket de soporte manualmente seleccionando el intercambio causante de problemas en \"Portafolio/Intercambios Abiertos\" y pulsando \"alt + o\" o \"option + o\". Por favor use este método solo si está muy seguro de que el software no está funcionando como debería. Si tiene problemas o preguntas, por favor consulte las FAQ en la web bisq.network o postee en el forum Bisq en la sección de Soporte.
support.initialInfo=Please note the basic rules for the dispute process:\n1. You need to respond to the arbitrator's requests within 2 days.\n2. The maximum period for a dispute is 14 days.\n3. You need to cooperate with the arbitrator and provide the information they request to make your case.\n4. You accepted the rules outlined in the wiki in the user agreement when you first started the application.\n\nPlease read more about the dispute process in our wiki:\nhttps://github.com/bisq-network/exchange/wiki/Arbitration-system
support.initialInfo="Por favor, tenga en cuenta las reglas básicas del proceso de disputa:\n1. Necesita responder a los requerimientos del árbitro en 2 días.\n2. El periodo máximo para la disputa es de 14 días.\n3. Necesita cooperar con el árbitro y entregar la información que pueda requerir para su caso.\n4. Acepta las reglas mostradas en la wiki de acuerdo de usuario cuando inició la aplicación por primera vez.\n\nPor favor lea más en detalle acerca del proceso de disputa en nuestra wiki:\nhttps://github.com/bisq-network/exchange/wiki/Arbitration-system
support.systemMsg=Mensaje de sistema: {0}
support.youOpenedTicket=Ha abierto una solicitud de soporte.
support.youOpenedDispute=Ha abierto una solicitud de disputa.\n\n{0}
@ -836,8 +838,8 @@ settings.net.useCustomNodesRadio=Utilizar nodos Bitcoin Core personalizados
settings.net.warn.usePublicNodes=Si usa una red pública de Bitcoin está expuesto a problemas de seguridad causados por el fallo en el diseño y la implementación del filtro bloom que se utiliza para carteras SPV como BitcoinJ (usado en Bisq). Cualquier nodo completo al que esté conectado podría conocer que todas las direcciones del monedero pertenecen a una entidad.\n\nPor favor, lea más sobre los detalles en: https://bisq.network/blog/privacy-in-bitsquare.\n\n¿Está seguro de que quiere utilizar los nodos públicos?
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=Please be sure that your Bitcoin node is a trusted Bitcoin Core node!\n\nConnecting to nodes which do not follow the Bitcoin Core consensus rules could corrupt your wallet and cause problems in the trade process.\n\nUsers who connect to nodes that violate consensus rules are responsible for any resulting damage. Any resulting disputes will be decided in favor of the other peer. No technical support will be given to users who ignore this warning and protection mechanisms!
settings.net.localhostBtcNodeInfo=(Background information: If you are running a local Bitcoin node (localhost) you can connect exclusively to it.)
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.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
settings.net.creationDateColumn=Establecido
@ -860,17 +862,17 @@ settings.net.inbound=entrante
settings.net.outbound=saliente
settings.net.reSyncSPVChainLabel=Resincronizar cadena SPV
settings.net.reSyncSPVChainButton=Borrar archivo SPV y resincronizar
settings.net.reSyncSPVSuccess=The SPV chain file will be deleted on the next startup. You need to restart your application now.\n\nAfter the restart it can take a while to resync with the network and you will only see all transactions once the resync is completed.\n\nPlease restart again after the resync has completed because there are sometimes inconsistencies that result in incorrect balances to display.
settings.net.reSyncSPVAfterRestart=The SPV chain file has been deleted. Please be patient. It can take a while to resync with the network.
settings.net.reSyncSPVSuccess=El archivo de cadena SPV se borrará en el siguiente inicio. Puede reiniciar la aplicación ahora.\n\nDespués del reinicio puede llevar un rato resincronizar con la red y verá todas las transacciones una vez completada la resincronización.\n\nPor favor haga otro reinicio después de resincronizar porque a veces hay inconsistencias que llevan a un balance mostrado incorrecto.
settings.net.reSyncSPVAfterRestart=La cadena SPV ha sido borrada. Por favor, sea paciente. Puede llevar un tiempo resincronizar con la red.
settings.net.reSyncSPVAfterRestartCompleted=La resincronización se ha completado. Por favor, reinicie la aplicación.
settings.net.reSyncSPVFailed=No se pudo borrar el archivo de cadena SPV\nError: {0}
setting.about.aboutBisq=Acerca de Bisq
setting.about.about=Bisq is open-source software which facilitates the exchange of bitcoin with national currencies (and other cryptocurrencies) through a decentralized peer-to-peer network in a way that strongly protects user privacy. Learn more about Bisq on our project web page.
setting.about.about=Bisq es un software open-source que facilita el intercambio de bitcoin y monedas nacionales (y otras criptomonedas) a través de una red decentralizada peer-to-peer de modo que se proteja fuertemente la privacidad del usuario. Aprenda más acerca de Bisq en la página web del proyecto.
setting.about.web=Página web de Bisq
setting.about.code=código fuente
setting.about.agpl=Licencia AGPL
setting.about.support=Apoye Bisq
setting.about.def=Bisq is not a company—it is a project open to the community. If you want to participate or support Bisq please follow the links below.
setting.about.def=bisq no es una compañía, sino un proyecto abierto a la comunidad. Si quiere participar o ayudar a Bisq por favor siga los links de abajo.
setting.about.contribute=Contribuir
setting.about.donate=Donar
setting.about.providers=Proveedores de datos
@ -892,7 +894,7 @@ setting.about.subsystems.val=Versión de red: {0}; Versión de mensajes P2P: {1}
account.tab.arbitratorRegistration=Registro de árbitro
account.tab.account=Cuenta
account.info.headline=Bienvenido a su cuenta Bisq
account.info.msg=Here you can add trading accounts for national currencies & altcoins, select arbitrators, and create a backup of your wallet & account data.\n\nA new Bitcoin wallet was created the first time you started Bisq.\n\nWe strongly recommend that you write down your Bitcoin wallet seed words (see tab on the top) and consider adding a password before funding. Bitcoin deposits and withdrawals are managed in the \"Funds\" section.\n\nPrivacy & security note: because Bisq is a decentralized exchange, all your data is kept on your computer. There are no servers, so we have no access to your personal info, your funds, or even your IP address. Data such as bank account numbers, altcoin & Bitcoin addresses, etc are only shared with your trading partner to fulfill trades you initiate (in case of a dispute the arbitrator will see the same data as your trading peer).
account.info.msg=Aquí puede añadir cuentas de intercambio para monedas nacionales y altcoins, seleccionar árbitros y crear una copia de seguridad de la cartera y datos de cuenta.\n\nSe ha creado una cartera vacía de Bitcoin la primera vez que inició Bisq.\n\nRecomendamos encarecidamente que anote las palabras semilla de la cartera (ver botón superior) y considere añadir una contraseña antes de enviar fondos. Los depósitos y retiros de Bitcoin se controlan en la sección \"Fondos\".\n\nPrivacidad y Seguridad:\nComo Bisq es un exchange descentralizado, todos los datos se mantienen en su ordenador. No hay servidores y no tenemos acceso a su información personal, sus fondos ni su dirección IP. Datos como números de cuenta bancaria, direcciones Bitcoin y altcoin, etc sólo se comparten con el par de intercambio para completar los intercambios iniciados (en caso de disputa, el árbitro verá los mismos datos que el par de intercambio).
account.menu.paymentAccount=Cuentas de moneda nacional
account.menu.altCoinsAccountView=Cuentas de altcoi
@ -905,7 +907,7 @@ account.arbitratorRegistration.pubKey=Clave pública
account.arbitratorRegistration.register=Registro de árbitro
account.arbitratorRegistration.revoke=Revocar registro
account.arbitratorRegistration.info.msg=Please note that you need to stay available for 15 days after revoking as there might be trades which are using you as arbitrator. The max. allowed trade period is 8 days and the dispute process might take up to 7 days.
account.arbitratorRegistration.info.msg=Por favor, tenga en cuenta que necesita estar disponible durante 15 días después de la revocación porque podría haber intercambios en los que esté envuelto como árbitro. El periodo máximo de intercambio es de 8 días y el proceso de disputa puede llevar hasta 7 días.
account.arbitratorRegistration.warn.min1Language=Necesita introducir al menos 1 idioma.\nHemos añadido el idioma por defecto para usted.
account.arbitratorRegistration.removedSuccess=Ha eliminado su árbitro de la red P2P satisfactoriamente.
account.arbitratorRegistration.removedFailed=No se pudo eliminar el árbitro. {0}
@ -924,12 +926,12 @@ account.arbitratorSelection.noLang=Puede seleccionar solamente árbitros que hab
account.arbitratorSelection.minOne=Necesita tener al menos un árbitro seleccionado.
account.altcoin.yourAltcoinAccounts=Sus cuentas de altcoin
account.altcoin.popup.wallet.msg=Please be sure that you follow the requirements for the usage of {0} wallets as described on the {1} web page.\nUsing wallets from centralized exchanges where (a) you don''t control your keys or (b) which don''t use compatible wallet software is risky: it can lead to loss of the traded funds!\nThe arbitrator is not a {2} specialist and cannot help in such cases.
account.altcoin.popup.wallet.msg=Por favor, asegúrese de que sigue los requerimientos para el uso de carteras {0} tal como se describe en la página web {1}.\n¡Usar carteras desde casas de cambio centralizadas donde (a) no tiene control sobre las claves o (b) no usan un compatible es arriesgado: puede llevar a la pérdida de los fondos intercambiados!\nEl árbitro no es un especialista {2} y no puede ayudar en tales casos.
account.altcoin.popup.wallet.confirm=Entiendo y confirmo que sé qué monedero tengo que utilizar.
account.altcoin.popup.xmr.msg=Si quiere comerciar XMR en Bisq, por favor asegúrese de que entiende y cumple todos los requerimientos.\n\nPara enviar XMR necesita usar o el monedero oficial Monero GUI o el monedero Monero simple con la bandera store-tx-info habilitada (por defecto en las nuevas versiones).\nPor favor asegúrese de que puede acceder a la tx key (usar el comando get_tx_key en simplewallet) porque podría requerirse en caso de disputa.\n\nmonero-wallet-cli (use el comando get_tx_key)\nmonero-wallet-gui (vaya a la pestaña de historia y clique en el botón (P) para prueba de pago)\n\nAdemás de la herramienta XMR checktx (https://xmr.llcoins.net/checktx.html) la verificación también se puede cumplir dentro del monedero.\nmonero-wallet-cli : usando el comando (check_tx_key).\nmonero-wallet-gui : en Avanzado > Probar/Comprobar página.\nEn exploradores de bloque normales la transferencia no es verificable.\n\nNecesita entregar al árbitro la siguiente información en caso de disputa:\n- La clave privada de transacción (tx private key).\n- El hash de transacción.\n- La dirección pública del receptor.\n\nSi no puede proveer la información o si ha usado un monedero incompatible resultaría en la pérdida del caso de disputa. El emisor de XMR es responsable de ser capaz de verificar la transacción XMR a el árbitro en caso de disputa.\n\nNo se requiere la ID de pago, sólo la dirección pública normal.\n\nSi no está seguro del proceso visite (https://www.getmonero.org/resources/user-guides/prove-payment.html) o el foro Monero (https://forum.getmonero.org) para más información.
account.altcoin.popup.blur.msg=If you want to trade BLUR on Bisq please be sure 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 arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nIf you cannot provide the required information to the arbitrator, you will lose the dispute. In all cases of dispute, the BLUR sender bears 100% of the burden of responsiblity in verifying transactions to an arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW).
account.altcoin.popup.ccx.msg=Si quiere intercambiar CCX en Bisq poar favor asegúrese de que entiende los siguientes requerimientos:\n\nPara enviar CCX debe usar un monedero ofcial Conceal, ya sea CLI o GUI. Después de enviar el pago, los monederos\nmuestran la clave secreta de la transacción. Debe guardarla junto con el hash de la transacción (ID) y la dirección\npública en caso de que sea necesario arbitraje. En tal caso, debe dar las tres al árbitro, quien\nverificará la transferencia CCX usando el Visor de Transacciones Conceal (https://explorer.conceal.network/txviewer).\nDebido a que Conceal es una moneda de privacidad, los exploradores de bloques no pueden verificar transferencias.\n\nSi no puede entregar los datos requeridos al árbitro, perderá el caso de disputa.\nSi no guarda la clave secreta de la transacción inmediatamente después de transferir CCX, no se podrá recuperar luego.\nSi no entiende estos requerimientos, busque ayuda en el discord Conceal (http://discord.conceal.network).
account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides a transaction is not verifyable on the public blockchain. If required you can prove your payment thru use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at \ (http://drgl.info/#check_txn).\n\nIf you cannot provide the above data or if you used an incompatible wallet it would result in losing the dispute case. The Dragonglass sender is responsible to be able to verify the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help.
account.altcoin.popup.xmr.msg=Intercambiar XMR en Bisq, requiere entender y cumplir los siguientes requisitos\n\nPara enviar XMR necesita usar o el monedero oficial Monero GUI o el monedero Monero simple con la bandera store-tx-info habilitada (por defecto en las nuevas versiones). Por favor asegúrese de que puede acceder a la tx key (usar el comando get_tx_key en simplewallet) porque podría requerirse en caso de disputa.\nmonero-wallet-cli (use el comando get_tx_key)\nmonero-wallet-gui (vaya a la pestaña de historia y clique en el botón (P) para prueba de pago)\n\nAdemás de la herramienta XMR checktx (https://xmr.llcoins.net/checktx.html) la verificación también se puede cumplir dentro del monedero.\nmonero-wallet-cli : usando el comando (check_tx_key).\nmonero-wallet-gui : en Avanzado > Probar/Comprobar página.\nEn exploradores de bloque normales la transferencia no es verificable.\n\nNecesita entregar al árbitro la siguiente información en caso de disputa:\n- La clave privada de transacción (tx private key).\n- El hash de transacción.\n- La dirección pública del receptor.\n\nSi no puede proveer la información o si ha usado un monedero incompatible resultaría en la pérdida del caso de disputa. El emisor de XMR es responsable de ser capaz de verificar la transacción XMR a el árbitro en caso de disputa.\n\nNo se requiere la ID de pago, sólo la dirección pública normal.\nSi no está seguro del proceso visite (https://www.getmonero.org/resources/user-guides/prove-payment.html) o el foro Monero (https://forum.getmonero.org) para más información.
account.altcoin.popup.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 arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The 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 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 arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW).
account.altcoin.popup.ccx.msg=Trading CCX on Bisq requires that you understand the following requirements:\n\nTo send CCX you must use an official Conceal wallet, either CLI or GUI. After sending a transfer payment, the wallets\ndisplay the transaction secret key. You must save it along with the transaction hash (ID) and the recipient's public\naddress in case arbitration is necessary. In such a case, you must give all three to the arbitrator, who will then\nverify the CCX transfer using the Conceal Transaction Viewer (https://explorer.conceal.network/txviewer).\nBecause Conceal is a privacy coin, block explorers cannot verify transfers.\n\nFailure to provide the required data to the arbitrator will result in losing the dispute case.\nIf you do not save the transaction secret key immediately after transferring CCX, it cannot be recovered later.\nIf you do not understand these requirements, seek help at the Conceal discord (http://discord.conceal.network).
account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides, a transaction is not verifiable on the public blockchain. If required, you can prove your payment through the use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at (http://drgl.info/#check_txn).\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The Dragonglass sender is responsible for providing verification of the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help.
account.altcoin.popup.ZEC.msg=Cuando use {0} sólo puede usar direcciones transparentes (que empiecen por t) y no las direcciones-z (privadas), porque el árbitro no sería capaz de verificar la transacción con direcciones-z.
account.altcoin.popup.XZC.msg=Al usar {0} puede solamente usar direcciones transparentes (trazables), porque el árbitro no sería capaz de verificar la transacciones no trazables en el explorador de bloques.
account.altcoin.popup.bch=Bitcoin cash and Bitcoin Clashic sufren de replay protection. Si usa una de estas monedes aseguŕese de que toma suficientes precauciones y entiende las implicaciones. Puede sufrir pérdidas enviando una moneda sin querer enviar las mismas monedeas a la otra cadena de bloques. Debido a que estos "airdrops" comparten la misma historia con la cadena de bloques de Bitcoin hay también riesgos de seguridad y un riesgo considerable de pérdida de privacidad.\n\nPor favor lea en el foro Bisq más acerca de este tema: https://forum.bisq.io/t/airdrop-coins-information-thread-bch-btg-bch
@ -952,14 +954,14 @@ account.password.removePw.button=Eliminar password
account.password.removePw.headline=Eliminar protección por password del monedero
account.password.setPw.button=Establecer password
account.password.setPw.headline=Establecer protección por password del monedero
account.password.info=With password protection you'll need to enter your password at application startup, when withdrawing bitcoin out of your wallet, and when restoring your wallet from seed words.
account.password.info=Con protección por password necesitará introducir su password en el arranque de la aplicación, cuando retire bitcoin de su monedero, y cuando restaure su monedero desde las palabras semilla.
account.seed.backup.title=Copia de seguridad de palabras semilla del monedero
account.seed.info=Please write down both wallet seed words and the date! You can recover your wallet any time with seed words and the date.\nThe same seed words are used for the BTC and BSQ wallet.\n\nYou should write down the seed words on a sheet of paper. Do not save them on your computer.\n\nPlease note that the seed words are NOT a replacement for a backup.\nYou need to create a backup of the whole application directory from the \"Account/Backup\" screen to recover application state and data.\nImporting seed words is only recommended for emergency cases. The application will not be functional without a proper backup of the database files and keys!
account.seed.info=Por favor apunte en un papel tanto las palabras semilla del monedero como la fecha! Puede recuperar su monedero en cualquier momento con las palabras semilla y la fecha.\nLas mismas palabras semilla se usan para el monedero BTC como BSQ\n\nDebe apuntar las palabras semillas en una hoja de papel. No la guarde en su computadora.\n\nPor favor, tenga en cuenta que las palabras semilla no son un sustituto de la copia de seguridad.\nNecesita hacer la copia de seguridad de todo el directorio de aplicación en la pantalla \"Cuenta/Copia de Seguridad\" para recuperar un estado de aplicación válido y los datos.\nImportar las palabras semilla solo se recomienda para casos de emergencia. La aplicación no será funcional sin una buena copia de seguridad de los archivos de la base de datos y las claves!
account.seed.warn.noPw.msg=No ha establecido una contraseña de cartera que proteja la visualización de las palabras semilla.\n\n¿Quiere que se muestren las palabras semilla?
account.seed.warn.noPw.yes=Sí, y no preguntar de nuevo
account.seed.enterPw=Introducir password para ver las palabras semilla
account.seed.restore.info=Please make a backup before applying restore from seed words. Be aware that wallet restore is only for emergency cases and might cause problems with the internal wallet database.\nIt is not a way for applying a backup! Please use a backup from the application data directory for restoring a previous application state.
account.seed.restore.info=Por favor haga una copia de seguridad antes de aplicar la restauración desde las palabras semilla. Tenga en cuenta que la restauración de cartera solo es para casos de emergencia y puede causar problemas con la base de datos interna del monedero.\nNo es el modo de aplicar una restauración de copia de seguridad! Por favor use una copia de seguridad desde el archivo de directorio de la aplicación para restaurar un estado de aplicación anterior.
account.seed.restore.ok=Ok, entiendo y quiero restaurar
@ -1322,7 +1324,7 @@ dao.assetState.REMOVED_BY_VOTING=Eliminados por votación
dao.proofOfBurn.header=Prueba de quemado
dao.proofOfBurn.amount=Cantidad
dao.proofOfBurn.preImage=Pre-imagen
dao.proofOfQuemar.burn=Quemar
dao.proofOfBurn.burn=Quemar
dao.proofOfBurn.allTxs=Todas las transacciones de prueba de quemado
dao.proofOfBurn.myItems=Mis transacciones de prueba de quemado
dao.proofOfBurn.date=Fecha
@ -1483,8 +1485,8 @@ dao.wallet.dashboard.totalUnlockingAmount=Desbloqueando BSQ de bonos
dao.wallet.dashboard.totalUnlockedAmount=BSQ desbloqueados de bonos
dao.wallet.dashboard.totalConfiscatedAmount=BSQ confiscados de bonos
dao.wallet.dashboard.allTx=Número de todas las transacciones BSQ
dao.wallet.dashboard.utxo=Número de todos los outputs de transacciones no gastadas
dao.wallet.dashboard.compensationIssuanceTx=Número de todas las transacciones emitidas de solicitudes de compensación
dao.wallet.dashboard.utxo=Número de todos los outputs de transacciones no gastadas
dao.wallet.dashboard.compensationIssuanceTx=Número de todas las transacciones emitidas de solicitudes de compensación
dao.wallet.dashboard.reimbursementIssuanceTx=Número de todas las transacciones emitidas de solicitud de reembolso
dao.wallet.dashboard.burntTx=Número de todas las transacciones de tasa de pago
dao.wallet.dashboard.price=Último precio intercambio BSQ/BTC (en Bisq)
@ -1506,8 +1508,8 @@ dao.wallet.send.send=Enviar fondos BSQ
dao.wallet.send.sendBtc=Enviar fondos BTC
dao.wallet.send.sendFunds.headline=Confirme la petición de retiro
dao.wallet.send.sendFunds.details=Enviando: {0}\nA la dirección receptora: {1}.\nLa tasa de transacción requerida es: {2} ({3} Satoshis/byte)\nTamaño de la transacción: {4} Kb\n\nEl receptor recibirá: {5}\n\nSeguro que quiere retirar esta cantidad?
dao.wallet.chainHeightSynced=Latest verified block: {0}
dao.wallet.chainHeightSyncing=Awaiting blocks... Verified {0} blocks out of {1}
dao.wallet.chainHeightSynced=Último bloque verificado: {0}
dao.wallet.chainHeightSyncing=Esperando bloques... {0} bloques verificados de {1}
dao.wallet.tx.type=Tipo
# suppress inspection "UnusedProperty"
@ -1584,7 +1586,7 @@ displayUpdateDownloadWindow.verify.failed=Verificación fallida./nPor favor desc
displayUpdateDownloadWindow.success=La nueva versión ha sido descargada con éxito y la firma verificada./n/nPor favor abra el directorio de descargas, cierre la aplicación e instale la nueva versión.
displayUpdateDownloadWindow.download.openDir=Abrir directorio de descargas
disputeResumenWindow.title=Resumen
disputeSummaryWindow.title=Resumen
disputeSummaryWindow.openDate=Fecha de apertura de ticket
disputeSummaryWindow.role=Rol del trader
disputeSummaryWindow.evidence=Evidencia
@ -1746,7 +1748,7 @@ popup.headline.error=Error
popup.doNotShowAgain=No mostrar de nuevo
popup.reportError.log=Abrir archivo de registro
popup.reportError.gitHub=Reportar al rastreador de problemas de Github
popup.reportError={0}\n\nTo help us to improve the software please report the bug on our issue tracker on GitHub (https://github.com/bisq-network/bisq-desktop/issues).\nThe error message will be copied to the clipboard when you click a button below.\nIt will make debugging easier if you can attach the bisq.log file as well.
popup.reportError={0}\n\nTo help us to improve the software please report this bug by opening a new issue at https://github.com/bisq-network/bisq/issues.\nThe above error message will be copied to the clipboard when you click either of the buttons below.\nIt will make debugging easier if you include the bisq.log file by pressing "Open log file", saving a copy, and attaching it to your bug report.
popup.error.tryRestart=Por favor pruebe a reiniciar la aplicación y comprobar su conexión a la red para ver si puede resolver el problema.
popup.error.takeOfferRequestFailed=Un error ocurrió cuando alguien intentó tomar una de sus ofertas:/n{0}
@ -1783,7 +1785,7 @@ popup.warning.nodeBanned=Uno de los nodos {0} ha sido baneado. Por favor reinici
popup.warning.priceRelay=retransmisión de precios
popup.warning.seed=Semilla
popup.info.securityDepositInfo=To ensure both traders follow the trade protocol, both traders need to pay a security deposit.\n\nThis deposit is kept in your trade wallet until your trade has been successfully completed, and then it's refunded to you.\n\nPlease note: if you're creating a new offer, Bisq needs to be running for another trader to take it. To keep your offers online, keep Bisq running and make sure this computer remains online too (i.e., make sure it doesn't switch to standby mode...monitor standby is fine).
popup.info.securityDepositInfo=Para asegurarse de que ambos comerciantes siguen el protocolo de intercambio, necesitan pagar un depósito de seguridad.\n\nEl depósito se guarda en el monedor 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 online, mantenga Bisq funcionando y asegúrese de que su computadora está online también (v.g. asegúrese de que no pasa a modo standby...el monitor en standby no es problema!)
popup.info.cashDepositInfo=Por favor asegúrese de que tiene una oficina bancaria donde pueda hacer el depósito de efectivo.\nEl banco con ID (BIC/SWIFT) de el banco del vendedor es: {0}
popup.info.cashDepositInfo.confirm=Confirmo que puedo hacer el depósito
@ -1805,6 +1807,9 @@ popup.attention.forTradeWithId=Se requiere atención para el intercambio con ID
popup.roundedFiatValues.headline=Nueva característica de privacidad: Valores redondeados a fiat
popup.roundedFiatValues.msg=Para incrementar la privacidad de sus intercambios la cantidad de {0} se redondeó.\n\nDependiendo de la versión del cliente pagará o recibirá valores con decimales o redondeados.\n\nAmbos valores serán cumplirán con el protocolo de intercambio.\n\nTambién tenga en cuenta que los valores BTC cambian automáticamente para igualar la cantidad fiat redondeada tan ajustada como sea posible.
popup.info.multiplePaymentAccounts.headline=Multiple payment accounts available
popup.info.multiplePaymentAccounts.msg=You have multiple payment accounts available for this offer. Please make sure you've picked the right one.
####################################################################
# Notifications
@ -2085,7 +2090,7 @@ payment.clearXchange.info=Por favor asegúrese de que cumple los requisitos para
payment.moneyGram.info=Al utilizar MoneyGram, el comprador de BTC tiene que enviar el número de autorización y una foto del recibo al vendedor de BTC por correo electrónico. El recibo debe mostrar claramente el monto, asi como el nombre completo, país y demarcación (departamento,estado, etc.) del vendedor. Al comprador se le mostrará el correo electrónico del vendedor en el proceso de transacción.
payment.westernUnion.info=Al utilizar Western Union, el comprador de BTC tiene que enviar el número de autorización y una foto del recibo al vendedor de BTC por correo electrónico. El recibo debe mostrar claramente el monto, asi como el nombre completo, país y demarcación (departamento,estado, etc.) del vendedor. Al comprador se le mostrará el correo electrónico del vendedor en el proceso de transacción.
payment.halCash.info=Al usar HalCash el comprador de BTC necesita enviar al vendedor de BTC el código HalCash a través de un mensaje de texto desde el teléfono móvil.\n\nPor favor asegúrese de que no excede la cantidad máxima que su banco le permite enviar con HalCash. La cantidad mínima por retirada es de 10 EUR y el máximo son 600 EUR. Para retiros frecuentes es 3000 por receptor al día y 6000 por receptor al mes. Por favor compruebe estos límites con su banco y asegúrese que son los mismos que aquí expuestos.\n\nLa cantidad de retir debe ser un múltiplo de 10 EUR ya que no se puede retirar otras cantidades desde el cajero automático. La Interfaz de Usuario en la pantalla crear oferta y tomar oferta ajustará la cantidad de BTC para que la cantidad de EUR sea correcta. No puede usar precios basados en el mercado ya que la cantidad de EUR cambiaría con el cambio de precios.\n\nEn caso de disputa el comprador de BTC necesita proveer la prueba de que ha enviado EUR.
payment.halCash.info=Al usar HalCash el comprador de BTC necesita enviar al vendedor de BTC el código HalCash a través de un mensaje de texto desde el teléfono móvil.\n\nPor favor asegúrese de que no excede la cantidad máxima que su banco le permite enviar con HalCash. La cantidad mínima por retirada es de 10 EUR y el máximo son 600 EUR. Para retiros frecuentes es 3000 por receptor al día y 6000 por receptor al mes. Por favor compruebe estos límites con su banco y asegúrese que son los mismos que aquí expuestos.\n\nLa cantidad de retiro debe ser un múltiplo de 10 EUR ya que no se puede retirar otras cantidades desde el cajero automático. La Interfaz de Usuario en la pantalla crear oferta y tomar oferta ajustará la cantidad de BTC para que la cantidad de EUR sea correcta. No puede usar precios basados en el mercado ya que la cantidad de EUR cambiaría con el cambio de precios.\n\nEn caso de disputa el comprador de BTC necesita proveer la prueba de que ha enviado EUR.
payment.limits.info=Por favor, tenga en cuenta que todas las transferencias bancarias tienen cierto riesgo de chargeback.\n\nPara disminuir este riesgo, Bisq establece límites por intecambio basándose en dos factores:\n\n1. El nivel estimado de riesgo de chargeback para el método de pago usado\n2. La edad de su cuenta para ese método de pago\n\nLa cuenta que está creando ahora es nueva y su edad es cero. A medida que su cuenta gane edad en un periodo de dos meses, también aumentará el límite por transacción.\n\n● Durante el primer mes, el límite será {0}\n● Durante el segundo mes, el límite será {1}\n● Después del segundo mes, el límite será {2}\n\nTenga en cuenta que no hay límites en el total de transacciones que puede realizar.
payment.cashDeposit.info=por favor confirme que su banco permite enviar depósitos de efectivo a cuentas de otras personas. Por ejemplo, Bank of America y Wells Fargo ya no permiten estos depósitos.
@ -2098,7 +2103,7 @@ payment.f2f.optionalExtra=Información adicional opcional
payment.f2f.extra=Información adicional
payment.f2f.extra.prompt=El creador puede definir los 'términos y condiciones' o añadir información de contacto pública. Será mostrada junto con la oferta.
payment.f2f.info=Los intercambios 'Cara a Cara' (F2F) tienen diferentes reglas y riesgos que las transacciones online.\n\nLas principales diferencias son:\n● Los pares de intercambio necesitan intercambiar información acerca del punto de reunión y la hora usando los detalles de contacto proporcionados.\n● Los pares de intercambio tienen que traer sus portátiles y hacer la confirmación de 'pago enviado' y 'pago recibido' en el lugar de reunión.\nSi un creador tiene 'términos y condiciones' especiales necesita declararlos en el campo de texto 'información adicional' en la cuenta.\n● Tomando una oferta el tomador está de acuerdo con los 'términos y condiciones' declarados por el creador.\n● En caso de disputa el árbitro no puede ayudar mucho ya que normalmente es complicado obtener evidencias no manipulables de lo que ha pasado en una reunión. En estos casos los fondos BTC pueden bloquearse indefinidamente o hasta que los pares lleguen a un acuerdo.\n\nPara asegurarse de que comprende las diferencias con los intercambios 'Cara a Cara' por favor lea las instrucciones y recomendaciones en: 'https://docs.bisq.network/trading-rules.html#f2f-trading'
payment.f2f.info=Los intercambios 'Cara a Cara' (F2F) tienen diferentes reglas y riesgos que las transacciones online.\n\nLas principales diferencias son:\n● Los pares de intercambio necesitan intercambiar información acerca del punto de reunión y la hora usando los detalles de contacto proporcionados.\n● Los pares de intercambio tienen que traer sus portátiles y hacer la confirmación de 'pago enviado' y 'pago recibido' en el lugar de reunión.\n● Si un creador tiene 'términos y condiciones' especiales necesita declararlos en el campo de texto 'información adicional' en la cuenta.\n● Tomando una oferta el tomador está de acuerdo con los 'términos y condiciones' declarados por el creador.\n● En caso de disputa el árbitro no puede ayudar mucho ya que normalmente es complicado obtener evidencias no manipulables de lo que ha pasado en una reunión. En estos casos los fondos BTC pueden bloquearse indefinidamente o hasta que los pares lleguen a un acuerdo.\n\nPara asegurarse de que comprende las diferencias con los intercambios 'Cara a Cara' por favor lea las instrucciones y recomendaciones en: 'https://docs.bisq.network/trading-rules.html#f2f-trading'
payment.f2f.info.openURL=Abrir paǵina web
payment.f2f.offerbook.tooltip.countryAndCity=Provincia y ciudad: {0} / {1}
payment.f2f.offerbook.tooltip.extra=Información adicional: {0}
@ -2227,7 +2232,7 @@ ADVANCED_CASH_SHORT=Advanced Cash
validation.empty=No se permiten entradas vacías
validation.NaN=El valor introducido no es válido
validation.notAnInteger=El valor introducido no es entero
validation.notAnInteger=El valor introducido no es entero
validation.zero=El 0 no es un valor permitido.
validation.negative=No se permiten entradas negativas.
validation.fiat.toSmall=No se permite introducir un valor menor que el mínimo posible

1131
core/src/main/resources/i18n/displayStrings_fa.properties
View file

File diff suppressed because it is too large Load diff

207
core/src/main/resources/i18n/displayStrings_fr.properties
View file

@ -299,6 +299,8 @@ market.trades.tooltip.candle.date=Date:
offerbook.createOffer=Créer une offre
offerbook.takeOffer=Prendre une offre
offerbook.takeOfferToBuy=Take offer to buy {0}
offerbook.takeOfferToSell=Take offer to sell {0}
offerbook.trader=Trader
offerbook.offerersBankId=ID de la banque du maker (BIC/SWIFT): {0}
offerbook.offerersBankName=Nom de la banque du maker : {0}
@ -503,97 +505,97 @@ portfolio.pending.step2_buyer.altcoin=Merci de transférer de votre portefeuille
# suppress inspection "TrailingSpacesInProperty"
portfolio.pending.step2_buyer.cash=Rendez vous à une banque et payer {0} au vendeur de BTC.\n\n
portfolio.pending.step2_buyer.cash.extra=CRITÈRES IMPORTANTS: \nAprès avoir effectuer le paiement veuillez écrire sur le reçu papier : PAS DE REMBOURSEMENT.\nPuis déchirer le en 2, prenez en une photo et envoyer le à l'adresse email du vendeur de BTC.
portfolio.pending.step2_buyer.moneyGram=Please pay {0} to the BTC seller by using MoneyGram.\n\n
portfolio.pending.step2_buyer.moneyGram.extra=IMPORTANT REQUIREMENT:\nAfter you have done the payment send the Authorisation number and a photo of the receipt by email to the BTC seller.\nThe receipt must clearly show the seller''s full name, country, state and the amount. The seller''s email is: {0}.
portfolio.pending.step2_buyer.westernUnion=Please pay {0} to the BTC seller by using Western Union.\n\n
portfolio.pending.step2_buyer.westernUnion.extra=IMPORTANT REQUIREMENT:\nAfter you have done the payment send the MTCN (tracking number) and a photo of the receipt by email to the BTC seller.\nThe receipt must clearly show the seller''s full name, city, country and the amount. The seller''s email is: {0}.
portfolio.pending.step2_buyer.moneyGram=Veuillez s'il vous plaît payer {0} au vendeur de BTC en utilisant MoneyGram.\n\n
portfolio.pending.step2_buyer.moneyGram.extra=CONDITION REQUISE IMPORTANTE:\nAprès avoir effectué le paiement envoyez le numéro d'Autorisation et une photo du reçu par e-mail au vendeur de BTC.\nLe reçu doit faire clairement figurer le nom complet du vendeur, son pays, son état et le montant. L'e-mail du vendeur est: {0}.
portfolio.pending.step2_buyer.westernUnion=Veuillez s'il vous plaît payer {0} au vendeur de BTC en utilisant Western Union.\n\n
portfolio.pending.step2_buyer.westernUnion.extra=CONDITION REQUISE IMPORTANTE:\nAprès avoir effectué le paiement envoyez le MTCN (numéro de suivi) et une photo du reçu par e-mail au vendeur de BTC.\nLe reçu doit faire clairement figurer le nom complet du vendeur, son pays, son état et le montant. L'e-mail du vendeur est: {0}.
# suppress inspection "TrailingSpacesInProperty"
portfolio.pending.step2_buyer.postal=Merci d'envoyer {0} par \"US Postal Money Order\" au vendeur de BTC.\n\n
# suppress inspection "TrailingSpacesInProperty"
portfolio.pending.step2_buyer.bank=Merci de vous rendre sur votre site de banque en ligne et payer {0} au vendeur de BTC.\n\n
portfolio.pending.step2_buyer.f2f=Please contact the BTC seller by the provided contact and arrange a meeting to pay {0}.\n\n
portfolio.pending.step2_buyer.f2f=Veuillez s'il vous plaît contacter le vendeur de BTC avec le moyen de contact fourni, et planifier une entrevue pour payer {0}.\n\n
portfolio.pending.step2_buyer.startPaymentUsing=Initier le paiement en utilisant {0}
portfolio.pending.step2_buyer.amountToTransfer=Amount to transfer
portfolio.pending.step2_buyer.sellersAddress=Seller''s {0} address
portfolio.pending.step2_buyer.buyerAccount=Your payment account to be used
portfolio.pending.step2_buyer.amountToTransfer=Montant à transférer
portfolio.pending.step2_buyer.sellersAddress=Adresse {0} du vendeur
portfolio.pending.step2_buyer.buyerAccount=Votre compte de paiement à utiliser
portfolio.pending.step2_buyer.paymentStarted=Paiement initié
portfolio.pending.step2_buyer.warn=Vous n'avez toujours pas effectué votre paiement {0}!\nVeuillez noter que cette transaction doit être effectuée avant {1} sinon la transaction sera inspectée par un arbitre.
portfolio.pending.step2_buyer.openForDispute=Vous n'avez toujours pas effectué votre paiement!\nLa période max pour cette transaction est terminée.\n\nMerci de contacter l'arbitre afin d'ouvrir une dispute.
portfolio.pending.step2_buyer.paperReceipt.headline=Avez-vous envoyé le preuve d'achat au vendeur de BTC?
portfolio.pending.step2_buyer.paperReceipt.msg=Rappelez-vous: \nVous devez écrire sur le reçu papier: PAS DE REMBOURSEMENT.\nEnsuite, le déchirer en deux, faire une photo et l'envoyer à l'adresse email du vendeur.
portfolio.pending.step2_buyer.moneyGramMTCNInfo.headline=Send Authorisation number and receipt
portfolio.pending.step2_buyer.moneyGramMTCNInfo.msg=You need to send the Authorisation number and a photo of the receipt by email to the BTC seller.\nThe receipt must clearly show the seller''s full name, country, state and the amount. The seller''s email is: {0}.\n\nDid you send the Authorisation number and contract to the seller?
portfolio.pending.step2_buyer.westernUnionMTCNInfo.headline=Send MTCN and receipt
portfolio.pending.step2_buyer.westernUnionMTCNInfo.msg=You need to send the MTCN (tracking number) and a photo of the receipt by email to the BTC seller.\nThe receipt must clearly show the seller''s full name, city, country and the amount. The seller''s email is: {0}.\n\nDid you send the MTCN and contract to the seller?
portfolio.pending.step2_buyer.halCashInfo.headline=Send HalCash code
portfolio.pending.step2_buyer.halCashInfo.msg=You need to send a text message with the HalCash code as well as the trade ID ({0}) to the BTC seller.\nThe seller''s mobile nr. is {1}.\n\nDid you send the code to the seller?
portfolio.pending.step2_buyer.fasterPaymentsHolderNameInfo=Some banks might require the receiver's name. The UK sort code and account number is sufficient for a Faster Payment transfer and the receivers name is not verified by any of the banks.
portfolio.pending.step2_buyer.moneyGramMTCNInfo.headline=Envoyer numéro d'Autorisation et reçu
portfolio.pending.step2_buyer.moneyGramMTCNInfo.msg=Vous devez envoyez le numéro d'Autorisation et une photo du reçu par e-mail au vendeur de BTC.\nLe reçu doit faire clairement figurer le nom complet du vendeur, son pays, son état et le montant. L'e-mail du vendeur est: {0}.\n\nAvez-vous envoyé le numéro d'Autorisation et le contrat au vendeur ?
portfolio.pending.step2_buyer.westernUnionMTCNInfo.headline=Envoyer MTCN et reçu
portfolio.pending.step2_buyer.westernUnionMTCNInfo.msg=Vous devez envoyez le MTCN (numéro de suivi) et une photo du reçu par e-mail au vendeur de BTC.\nLe reçu doit faire clairement figurer le nom complet du vendeur, son pays, son état et le montant. L'e-mail du vendeur est: {0}.\n\nAvez-vous envoyé le MTCN et le contrat au vendeur ?
portfolio.pending.step2_buyer.halCashInfo.headline=Envoyer le code HalCash
portfolio.pending.step2_buyer.halCashInfo.msg=Vous devez envoyez un message texte avec le code HalCash ainsi que l'ID de la transaction ({0}) au vendeur de BTC.\nLe numéro de mobile du vendeur est {1}.\n\nAvez-vous envoyé le code au vendeur ?
portfolio.pending.step2_buyer.fasterPaymentsHolderNameInfo=Certaines banques peuvent exiger le nom du bénéficiaire. Au Royaume-Uni, le sort code avec le numéro de compte est suffisant pour un transfert Faster Payment et le nom du bénéficiaire n'est vérifié par aucune banque.
portfolio.pending.step2_buyer.confirmStart.headline=Confirmez que vous avez initié le paiement
portfolio.pending.step2_buyer.confirmStart.msg=Avez-vous initié le {0} paiement à votre partenaire commercial?
portfolio.pending.step2_buyer.confirmStart.yes=Oui, j'ai initié le paiement
portfolio.pending.step2_seller.waitPayment.headline=En attente du paiement
portfolio.pending.step2_seller.f2fInfo.headline=Buyer's contact information
portfolio.pending.step2_seller.f2fInfo.headline=Fiche de contact acheteur
portfolio.pending.step2_seller.waitPayment.msg=La transaction de dépôt a au moins une confirmation de la blockchain.\nVous devez attendre que l'acheteur de BTC débute le {0} payment.
portfolio.pending.step2_seller.warn=The BTC buyer still has not done the {0} payment.\nYou need to wait until they have started the payment.\nIf the trade has not been completed on {1} the arbitrator will investigate.
portfolio.pending.step2_seller.openForDispute=The BTC buyer has not started his payment!\nThe max. allowed period for the trade has elapsed.\nYou can wait longer and give the trading peer more time or contact the arbitrator for opening a dispute.
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 démarré son paiement!\nLe temps max. alloué pour la transaction est écoulé.\nVous pouvez attendre encore pour laisser plus de temps à l'autre participant, ou contacter l'arbitre pour ouvrir une dispute.
# suppress inspection "UnusedProperty"
message.state.UNDEFINED=Undefined
message.state.UNDEFINED=Indéfini
# suppress inspection "UnusedProperty"
message.state.SENT=Message sent
message.state.SENT=Message envoyé
# suppress inspection "UnusedProperty"
message.state.ARRIVED=Message arrived at peer
message.state.ARRIVED=Message reçu par le destinataire
# suppress inspection "UnusedProperty"
message.state.STORED_IN_MAILBOX=Message stored in mailbox
message.state.STORED_IN_MAILBOX=Message stocké dans la boîte de réception
# suppress inspection "UnusedProperty"
message.state.ACKNOWLEDGED=Peer confirmed message receipt
message.state.ACKNOWLEDGED=Le destinataire a accusé réception du message
# suppress inspection "UnusedProperty"
message.state.FAILED=Sending message failed
message.state.FAILED=Echec de l'envoi du message
portfolio.pending.step3_buyer.wait.headline=En attente de la confirmation de paiement du vendeur BTC
portfolio.pending.step3_buyer.wait.info=Nous attendons que le vendeur confirme le preuve d'achat du paiement {0} .
portfolio.pending.step3_buyer.wait.msgStateInfo.label=Payment started message status
portfolio.pending.step3_buyer.wait.msgStateInfo.label=Statut du message de paiement initié
portfolio.pending.step3_buyer.warn.part1a=sur la {0} blockchain
portfolio.pending.step3_buyer.warn.part1b=chez votre fournisseur de services bancaires
portfolio.pending.step3_buyer.warn.part2=Le vendeur de BTC n'a toujours pas confirmé votre paiement!\nVeuillez vérifier {0} si l'envoi du paiement a été effectuer.\nSi le vendeur ne confirme pas la réception du paiement avant {1} la transaction fera l'objet d'une enquête par l'arbitre.
portfolio.pending.step3_buyer.openForDispute=The BTC seller has not confirmed your payment!\nThe max. period for the trade has elapsed.\nYou can wait longer and give the trading peer more time or contact the arbitrator for opening a dispute.
portfolio.pending.step3_buyer.openForDispute=Le vendeur de BTC n'a pas confirmé votre paiement!\nLe temps max. alloué pour la transaction est écoulé.\nVous pouvez attendre encore pour laisser plus de temps à l'autre participant, ou contacter l'arbitre pour ouvrir une dispute.
# suppress inspection "TrailingSpacesInProperty"
portfolio.pending.step3_seller.part=Votre partenaire d'échange a confirmé qu'il a commencé à vous payer {0}.\n
portfolio.pending.step3_seller.altcoin.explorer=on your favorite {0} blockchain explorer
portfolio.pending.step3_seller.altcoin.wallet=at your {0} wallet
portfolio.pending.step3_seller.altcoin={0}Please check {1} if the transaction to your receiving address\n{2}\nhas already sufficient blockchain confirmations.\nThe payment amount has to be {3}\n\nYou can copy & paste your {4} address from the main screen after closing that popup.
portfolio.pending.step3_seller.postal={0}Please check if you have received {1} with \"US Postal Money Order\" from the BTC buyer.\n\nThe trade ID (\"reason for payment\" text) of the transaction is: \"{2}\"
portfolio.pending.step3_seller.bank=Your trading partner has confirmed that he initiated the {0} payment.\n\nPlease go to your online banking web page and check if you have received {1} from the BTC buyer.\n\nThe trade ID (\"reason for payment\" text) of the transaction is: \"{2}\"\n\n
portfolio.pending.step3_seller.cash=Because the payment is done via Cash Deposit the BTC buyer has to write \"NO REFUND\" on the paper receipt, tear it in 2 parts and send you a photo by email.\n\nTo avoid chargeback risk, only confirm if you received the email and if you are sure the paper receipt is valid.\nIf you are not sure, {0}
portfolio.pending.step3_seller.moneyGram=The buyer has to send you the Authorisation number and a photo of the receipt by email.\nThe receipt must clearly show your full name, country, state and the amount. Please check your email if you received the Authorisation number.\n\nAfter closing that popup you will see the BTC buyer's name and address for picking up the money from MoneyGram.\n\nOnly confirm receipt after you have successfully picked up the money!
portfolio.pending.step3_seller.westernUnion=The buyer has to send you the MTCN (tracking number) and a photo of the receipt by email.\nThe receipt must clearly show your full name, city, country and the amount. Please check your email if you received the MTCN.\n\nAfter closing that popup you will see the BTC buyer's name and address for picking up the money from Western Union.\n\nOnly confirm receipt after you have successfully picked up the money!
portfolio.pending.step3_seller.halCash=The buyer has to send you the HalCash code as text message. Beside that you will receive a message from HalCash with the required information to withdraw the EUR from a HalCash supporting ATM.\n\nAfter you have picked up the money from the ATM please confirm here the receipt of the payment!
portfolio.pending.step3_seller.part=Your trading partner has confirmed that they have initiated the {0} payment.\n\n
portfolio.pending.step3_seller.altcoin.explorer=dans votre explorateur de blockchain {0} favorite
portfolio.pending.step3_seller.altcoin.wallet=à votre portefeuille {0}
portfolio.pending.step3_seller.altcoin={0}Veuillez s'il vous plaît vérifier {1} si la transaction vers votre adresse de réception\n{2}\na suffisament de confirmations pour la blockchain.\nLe montant du paiment doit être {3}\n\nVous pouver copier & coller votre adresse {4} à partir de l'écran principal après avoir fermé ce popup.
portfolio.pending.step3_seller.postal={0}Veuillez s'il vous plaît vérifier si vous avez reçu {1} avec \"US Postal Money Order\" de la part de l'acheteur de BTC.\n\nL'ID de la transaction (indiqué dans \"reason for payment\") est: \"{2}\"
portfolio.pending.step3_seller.bank=Your trading partner has confirmed that they have initiated the {0} payment.\n\nPlease go to your online banking web page and check if you have received {1} from the BTC buyer.\n\nThe trade ID (\"reason for payment\" text) of the transaction is: \"{2}\"\n\n
portfolio.pending.step3_seller.cash=Comme le paiement est réalisé via Cash Deposit l'acheteur de BTC doit inscrire \"NO REFUND\" sur le reçu papier, le déchirer en 2 parties et vous envoyer une photo par e-mail.\n\nPour éviter un risque de rétrofacturation, ne confirmez que si vous recevez le mail et que vous êtes sûr que le reçu papier est valide.\nSi vous n'êtes pas sûr, {0}
portfolio.pending.step3_seller.moneyGram=L'acheteur doit vous envoyer le numéro d'Autorisation et une photo du reçu par e-mail .\nLe reçu doit faire clairement figurer votre nom complet, votre pays, votre état et le montant. Veuillez s'il vous plaît vérifier si vous avez reçu par e-mail le numéro d'Autorisation.\n\nAprès avoir fermé ce popup vous verrez le nom de l'acheteur de BTC et l'adresse où retirer l'argent depuis MoneyGram.\n\nN'accusez réception qu'après avoir retiré l'argent avec succès!
portfolio.pending.step3_seller.westernUnion=L'acheteur doit vous envoyer le MTCN (numéro de suivi) et une photo du reçu par e-mail .\nLe reçu doit faire clairement figurer votre nom complet, votre pays, votre état et le montant. Veuillez s'il vous plaît vérifier si vous avez reçu par e-mail le MTCN.\n\nAprès avoir fermé ce popup vous verrez le nom de l'acheteur de BTC et l'adresse où retirer l'argent depuis Western Union.\n\nN'accusez réception qu'après avoir retiré l'argent avec succès!
portfolio.pending.step3_seller.halCash=L'acheteur doit vous envoyer le code HalCash en message texte. Par ailleurs, vous recevrez un message de la part d'HalCash avec les informations nécessaires pour retirer les EUR depuis un Guichet Automatique Bancaire supportant HalCash.\n\nAprès avoir retiré l'argent du guichet, veuillez ici s'il vous plaît accuser réception du paiement!
portfolio.pending.step3_seller.bankCheck=\n\nPlease also verify that the sender's name in your bank statement matches that one from the trade contract:\nSender's name: {0}\n\nIf the name is not the same as the one displayed here, {1}
portfolio.pending.step3_seller.openDispute=please don't confirm but open a dispute by entering \"alt + o\" or \"option + o\".
portfolio.pending.step3_seller.bankCheck=\n\nVérifiez aussi s'il vous plaît que le nom de l'émetteur sur votre récapitulatif bancaire correspond à celui du contrat de la transaction:\nNom de l'émetteur: {0}\n\nSi le nom n'est pas le même que celui indiqué ici, {1}
portfolio.pending.step3_seller.openDispute=ne confirmez pas s'il vous plaît, mais entamez plutôt une dispute en tapant \"alt + o\" ou \"option + o\".
portfolio.pending.step3_seller.confirmPaymentReceipt=Confirmez le preuve d'achat
portfolio.pending.step3_seller.amountToReceive=Amount to receive
portfolio.pending.step3_seller.yourAddress=Your {0} address
portfolio.pending.step3_seller.buyersAddress=Buyers {0} address
portfolio.pending.step3_seller.yourAccount=Your trading account
portfolio.pending.step3_seller.buyersAccount=Buyers trading account
portfolio.pending.step3_seller.amountToReceive=Montant à recevoir
portfolio.pending.step3_seller.yourAddress=Votre adresse {0}
portfolio.pending.step3_seller.buyersAddress=Adresse {0} de l'acheteur
portfolio.pending.step3_seller.yourAccount=Votre compte de transaction
portfolio.pending.step3_seller.buyersAccount=Compte de transaction de l'acheteur
portfolio.pending.step3_seller.confirmReceipt=Confirmez le preuve d'achat
portfolio.pending.step3_seller.buyerStartedPayment=L'acheteur BTC a commencé le {0} paiement.\n{1}
portfolio.pending.step3_seller.buyerStartedPayment.altcoin=Check for blockchain confirmations at your altcoin wallet or block explorer and confirm the payment when you have sufficient blockchain confirmations.
portfolio.pending.step3_seller.buyerStartedPayment.fiat=Check at your trading account (e.g. bank account) and confirm when you have received the payment.
portfolio.pending.step3_seller.buyerStartedPayment.altcoin=Surveillez les confirmations de la blockchain depuis votre portefeuille altcoin ou depuis un explorateur de blocs, et confirmez le paiement quand vous aurez suffisamment de confirmations de la blockchain.
portfolio.pending.step3_seller.buyerStartedPayment.fiat=Surveillez votre compte de transaction (par exemple votre compte bancaire) et confirmez quand vous aurez reçu le paiement.
portfolio.pending.step3_seller.warn.part1a=sur la {0} blockchain
portfolio.pending.step3_seller.warn.part1b=chez votre fournisseur de services bancaires
portfolio.pending.step3_seller.warn.part2=You still have not confirmed the receipt of the payment!\nPlease check {0} if you have received the payment.\nIf you don''t confirm receipt by {1} the trade will be investigated by the arbitrator.
portfolio.pending.step3_seller.openForDispute=You have not confirmed the receipt of the payment!\nThe max. period for the trade has elapsed.\nPlease confirm or contact the arbitrator for opening a dispute.
portfolio.pending.step3_seller.warn.part2=Vous n'avez toujours pas accusé réception du paiement!\nVeuillez vérifier {0} si vous avez reçu le paiement.\nSi vous n'accusez pas réception avant {1} la transaction fera l'objet d'une enquête par l'arbitre.
portfolio.pending.step3_seller.openForDispute=Vous n'avez pas accusé réception du paiement!\nLe temps max. alloué pour la transaction est écoulé.\nVeuillez s'il vous plaît confirmer ou contacter l'arbitre pour ouvrir une dispute.
# suppress inspection "TrailingSpacesInProperty"
portfolio.pending.step3_seller.onPaymentReceived.part1=Avez-vous reçu le paiement {0} de votre partenaire d'échange?\n\n
# suppress inspection "TrailingSpacesInProperty"
portfolio.pending.step3_seller.onPaymentReceived.fiat=The trade ID (\"reason for payment\" text) of the transaction is: \"{0}\"\n\n
portfolio.pending.step3_seller.onPaymentReceived.fiat=L'ID de la transaction (le texte \"reason for payment\") est: \"{0}\"\n\n
# suppress inspection "TrailingSpacesInProperty"
portfolio.pending.step3_seller.onPaymentReceived.name=Please also verify that the sender's name in your bank statement matches that one from the trade contract:\nSender's name: {0}\n\nIf the name is not the same as the one displayed here, please don't confirm but open a dispute by entering \"alt + o\" or \"option + o\".\n\n
portfolio.pending.step3_seller.onPaymentReceived.note=Please note, that as soon you have confirmed the receipt, the locked trade amount will be released to the BTC buyer and the security deposit will be refunded.
portfolio.pending.step3_seller.onPaymentReceived.name=Vérifiez aussi s'il vous plaît que le nom de l'émetteur sur votre récapitulatif bancaire correspond à celui du contrat de la transaction:\nNom de l'émetteur: {0}\n\nSi le nom n'est pas le même que celui indiqué ici, veuillez s'il vous plaît ne pas confirmer et ouvrez une dispute en tapant \"alt + o\" ou \"option + o\".\n\n
portfolio.pending.step3_seller.onPaymentReceived.note=Tenez s'il vous plaît compte du fait que, aussitôt que vous accusez réception, le montant bloqué de la transaction sera transmis à l'acheteur de BTC et que le dépôt de garantie sera remboursé.
portfolio.pending.step3_seller.onPaymentReceived.confirm.headline=Confirmez que vous avez reçu le paiement
portfolio.pending.step3_seller.onPaymentReceived.confirm.yes=Oui, j'ai reçu le paiement
@ -601,40 +603,40 @@ portfolio.pending.step5_buyer.groupTitle=Résumé de l'échange complet
portfolio.pending.step5_buyer.tradeFee=Frais de transaction
portfolio.pending.step5_buyer.makersMiningFee=Frais de minage
portfolio.pending.step5_buyer.takersMiningFee=Total des frais de minage
portfolio.pending.step5_buyer.refunded=Refunded security deposit
portfolio.pending.step5_buyer.refunded=Dépôt de garantie remboursé
portfolio.pending.step5_buyer.withdrawBTC=Retirer vos bitcoins
portfolio.pending.step5_buyer.amount=Amount to withdraw
portfolio.pending.step5_buyer.withdrawToAddress=Withdraw to address
portfolio.pending.step5_buyer.amount=Montant à retirer
portfolio.pending.step5_buyer.withdrawToAddress=Retirer à l'adresse
portfolio.pending.step5_buyer.moveToBisqWallet=Transférer les fonds au portefeuille bisq
portfolio.pending.step5_buyer.withdrawExternal=Retrait à un portefeuille externe
portfolio.pending.step5_buyer.alreadyWithdrawn=Vos fonds ont déjà été retirés. Merci de vérifier votre historique de transactions.
portfolio.pending.step5_buyer.confirmWithdrawal=Confirmer la demande de retrait
portfolio.pending.step5_buyer.amountTooLow=The amount to transfer is lower than the transaction fee and the min. possible tx value (dust).
portfolio.pending.step5_buyer.amountTooLow=Le montant à transférer est plus bas que les frais de transaction et que la valeur min. possible pour une tx (poussière).
portfolio.pending.step5_buyer.withdrawalCompleted.headline=Retrait effectué
portfolio.pending.step5_buyer.withdrawalCompleted.msg=Your completed trades are stored under \"Portfolio/History\".\nYou can review all your bitcoin transactions under \"Funds/Transactions\"
portfolio.pending.step5_buyer.bought=You have bought
portfolio.pending.step5_buyer.paid=You have paid
portfolio.pending.step5_buyer.withdrawalCompleted.msg=Vos transactions effectuées sont stockées dans /"Historique du portefeuille\".\nVous pouvez retrouver toutes vos transactions de bitcoin dans \"Transactions de fonds\"
portfolio.pending.step5_buyer.bought=Vous avez acheté
portfolio.pending.step5_buyer.paid=Vous avez payé
portfolio.pending.step5_seller.sold=You have sold
portfolio.pending.step5_seller.received=You have received
portfolio.pending.step5_seller.sold=Vous avez vendu
portfolio.pending.step5_seller.received=Vous avez reçu
tradeFeedbackWindow.title=Congratulations on completing your trade
tradeFeedbackWindow.msg.part1=We'd love to hear back from you about your experience. It'll help us to improve the software and to smooth out any rough edges. If you'd like to provide feedback, please fill out this short survey (no registration required) at:
tradeFeedbackWindow.msg.part2=If you have any questions, or experienced any problems, please get in touch with other users and contributors via the Bisq forum at:
tradeFeedbackWindow.msg.part3=Thanks for using Bisq!
tradeFeedbackWindow.title=Félicitations pour avoir achevé votre transaction
tradeFeedbackWindow.msg.part1=Nous aimerions votre retour à propos de votre expérience. Cela nous aiderait à améliorer le logiciel et éventuellement à arrondir les angles. Si vous souhaitez transmettre une réaction, remplissez s'il vous plaît ce rapide questionnaire (pas d'inscription nécessaire) à:
tradeFeedbackWindow.msg.part2=Si vous avez la moindre question, ou rencontrez le moindre problème, veuillez s'il vous plaît vous mettre en relation avec les autres utilisateurs et contributeurs via le Bisq forum à:
tradeFeedbackWindow.msg.part3=Merci d'utiliser Bisq!
portfolio.pending.role=Mon rôle
portfolio.pending.tradeInformation=Information de l'échange
portfolio.pending.remainingTime=Temps restant
portfolio.pending.remainingTimeDetail={0} (until {1})
portfolio.pending.tradePeriodInfo=After the first blockchain confirmation, the trade period starts. Based on the payment method used, a different maximum allowed trade period is applied.
portfolio.pending.tradePeriodWarning=If the period is exceeded both traders can open a dispute.
portfolio.pending.remainingTimeDetail={0} (jusqu'au {1})
portfolio.pending.tradePeriodInfo=Après la première confirmation de la blockchain, la période de transaction débute. Selon la méthode de paiement utilisée, une période maximum allouée à la transaction est appliquée.
portfolio.pending.tradePeriodWarning=Si la période est écoulée, l'un ou l'autre des participants de la transaction peut ouvrir une dispute.
portfolio.pending.tradeNotCompleted=Le trade n'est pas terminé à temps (jusqu'à {0})
portfolio.pending.tradeProcess=Processus de transaction
portfolio.pending.openAgainDispute.msg=If you are not sure that the message to the arbitrator arrived (e.g. if you did not get a response after 1 day) feel free to open a dispute again.
portfolio.pending.openAgainDispute.msg=Si vous n'êtes pas sûr que le message adressé à l'arbitre soit arrivé (par exemple si vous n'avez pas reçu de réponse au bout d'1 journée) n'hésitez pas à ouvrir une dispute à nouveau.
portfolio.pending.openAgainDispute.button=Rouvrir la dispute
portfolio.pending.openSupportTicket.headline=Ouvrir un ticket d'assistance
portfolio.pending.openSupportTicket.msg=Please use that only in emergency case if you don't get displayed a \"Open support\" or \"Open dispute\" button.\n\nWhen you open a support ticket the trade will be interrupted and handled by the arbitrator
portfolio.pending.openSupportTicket.msg=Merci de ne procéder à cela qu'en cas d'urgence si les boutons \"Obtenir un soutien\" ou \"Ouvrir une dispute\" ne s'affichent pas.\n\nQuand vous ouvrez un ticket de soutien la transaction est interrompue et prise en charge par l'arbitre
portfolio.pending.notification=Notification
portfolio.pending.openDispute=Déclencher une dispute
portfolio.pending.disputeOpened=Dispute ouverte
@ -648,7 +650,7 @@ portfolio.pending.disputeOpenedMyUser=Vous avez déjà ouvert une dispute.\n{0}
portfolio.pending.disputeOpenedByPeer=L'autre trader a ouvert une dispute\n{0}
portfolio.pending.supportTicketOpenedByPeer=L'autre trader a ouvert un ticket d'assistance.\n{0}
portfolio.pending.noReceiverAddressDefined=Aucune adresse de destinataire définie
portfolio.pending.removeFailedTrade=If the arbitrator could not close that trade you can move it yourself to the failed trades screen.\nDo you want to remove that failed trade from the Pending trades screen?
portfolio.pending.removeFailedTrade=Si l'arbitre ne peut clore la transaction, vous pouvez vous-même la déplacer dans le panneau des transactions échouées.\nVoulez-vous supprimer cette transaction échouée du panneau des transactions en attente ?
portfolio.closed.completed=Terminé
portfolio.closed.ticketClosed=Ticket fermé
portfolio.closed.canceled=Annulé
@ -670,8 +672,8 @@ funds.deposit.usedInTx=Utilisé dans {0} transaction(s)
funds.deposit.fundBisqWallet=Alimenter votre portefeuille
funds.deposit.noAddresses=Aucune adresse de dépôt n'a encore été générée
funds.deposit.fundWallet=Alimenter votre portefeuille
funds.deposit.withdrawFromWallet=Send funds from wallet
funds.deposit.amount=Amount in BTC (optional)
funds.deposit.withdrawFromWallet=Transférer des fonds depuis le portefeuille
funds.deposit.amount=Montant en BTC (optionnel)
funds.deposit.generateAddress=Générer une nouvelle adresse
funds.deposit.selectUnused=Merci de sélectionner une adresse inutilisée dans le tableau ci-dessus plutôt que d'en générer une nouvelle.
@ -681,10 +683,10 @@ funds.withdrawal.useAllInputs=Utilisez toutes les entrées disponibles
funds.withdrawal.useCustomInputs=Utiliser des entrées personnalisées
funds.withdrawal.receiverAmount=Montant du destinataire
funds.withdrawal.senderAmount=Montant de l'expéditeur
funds.withdrawal.feeExcluded=Amount excludes mining fee
funds.withdrawal.feeIncluded=Amount includes mining fee
funds.withdrawal.fromLabel=Withdraw from address
funds.withdrawal.toLabel=Withdraw to address
funds.withdrawal.feeExcluded=Montant hormis frais de minage
funds.withdrawal.feeIncluded=Montant incluant frais de minage
funds.withdrawal.fromLabel=Retirer depuis l'adresse
funds.withdrawal.toLabel=Retirer vers l'adresse
funds.withdrawal.withdrawButton=Envoyer les fonds
funds.withdrawal.noFundsAvailable=Aucun fond disponible à retirer
funds.withdrawal.confirmWithdrawalRequest=Confirmer la requête de retrait
@ -695,22 +697,22 @@ funds.withdrawal.selectAddress=Sélectionnez une adresse source depuis le tablea
funds.withdrawal.setAmount=Définir le montant à retirer
funds.withdrawal.fillDestAddress=Complétez votre adresse de destination
funds.withdrawal.warn.noSourceAddressSelected=Vous devez sélectionner une adresse source dans le tableau ci-dessus.
funds.withdrawal.warn.amountExceeds=You don't have sufficient funds available from the selected address.\nConsider to select multiple addresses in the table above or change the fee toggle to include the miner fee.
funds.withdrawal.warn.amountExceeds=Vous ne disposez pas de suffisamment de fonds aux adresses selectionnées.\nConsidérez une multiple sélection d'adresses dans la table ci-dessus ou changez la position de la bascule de frais de manière à inclure les frais de minage.
funds.reserved.noFunds=Aucun fonds n'est utilisé dans des offres.
funds.reserved.reserved=Bloqué dans votre portefeuille local pour l'offre avec l'ID : {0}
funds.locked.noFunds=Aucun fonds n'est bloqué dans des transactions.
funds.locked.locked=Locked in multisig for trade with ID: {0}
funds.locked.locked=Vérouillés en multisig pour la transaction d'ID: {0}
funds.tx.direction.sentTo=Envoyer à:
funds.tx.direction.receivedWith=Recevoir avec:
funds.tx.direction.genesisTx=From Genesis tx:
funds.tx.txFeePaymentForBsqTx=Miner fee for BSQ tx
funds.tx.direction.genesisTx=Genesis tx référente:
funds.tx.txFeePaymentForBsqTx=Frais de minage pour la tx BSQ
funds.tx.createOfferFee=Frais maker et réseau : {0}
funds.tx.takeOfferFee=Frais taker et réseau : {0}
funds.tx.multiSigDeposit=Multisig deposit: {0}
funds.tx.multiSigPayout=Multisig payout: {0}
funds.tx.multiSigDeposit=Dépôt multisig: {0}
funds.tx.multiSigPayout=Paiement multisig: {0}
funds.tx.disputePayout=Remboursement dispute: {0}
funds.tx.disputeLost=Dossier de dispute perdus: {0}
funds.tx.unknown=Raison inconnue: {0}
@ -720,9 +722,9 @@ funds.tx.withdrawnFromWallet=Retiré depuis le portefeuille
funds.tx.noTxAvailable=Aucune transaction disponible
funds.tx.revert=Défaire
funds.tx.txSent=Transaction envoyée avec succès à la nouvelle adresse dans le portefeuille local bisq.
funds.tx.direction.self=Sent to yourself
funds.tx.daoTxFee=Miner fee for DAO tx
funds.tx.reimbursementRequestTxFee=Reimbursement request
funds.tx.direction.self=Envoyés à vous-même
funds.tx.daoTxFee=Frais de mineur pour la tx DAO
funds.tx.reimbursementRequestTxFee=Demande de remboursement
funds.tx.compensationRequestTxFee=Requête de compensation
@ -733,11 +735,11 @@ funds.tx.compensationRequestTxFee=Requête de compensation
support.tab.support=Tickets d'assistance
support.tab.ArbitratorsSupportTickets=Ticket de support arbitre
support.tab.TradersSupportTickets=Ticket de support Trader
support.filter=Filter list
support.filter=Liste de filtre
support.noTickets=Il n'y a aucun ticket ouvert
support.sendingMessage=Envoi du message...
support.receiverNotOnline=Le destinataire n'est pas connecté. Le message est envoyé à sa boîte de réception.
support.sendMessageError=Sending message failed. Error: {0}
support.sendMessageError=Échec de l'envoi du message. Erreur: {0}
support.wrongVersion=The offer in that dispute has been created with an older version of Bisq.\nYou cannot close that dispute with your version of the application.\n\nPlease use an older version with protocol version {0}
support.openFile=Open file to attach (max. file size: {0} kb)
support.attachmentTooLarge=The total size of your attachments is {0} kb and is exceeding the max. allowed message size of {1} kB.
@ -926,10 +928,10 @@ account.arbitratorSelection.minOne=Vous devez sélectionner un arbitre.
account.altcoin.yourAltcoinAccounts=Your altcoin accounts
account.altcoin.popup.wallet.msg=Please be sure that you follow the requirements for the usage of {0} wallets as described on the {1} web page.\nUsing wallets from centralized exchanges where (a) you don''t control your keys or (b) which don''t use compatible wallet software is risky: it can lead to loss of the traded funds!\nThe arbitrator is not a {2} specialist and cannot help in such cases.
account.altcoin.popup.wallet.confirm=Je comprends et confirme que je sais quel portefeuille je dois utiliser.
account.altcoin.popup.xmr.msg=If you want to trade XMR on Bisq please be sure you understand and fulfill the following requirements:\n\nFor sending XMR you need to use either the official Monero GUI wallet or Monero CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nmonero-wallet-cli (use the command get_tx_key)\nmonero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nIn addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\nmonero-wallet-cli : using command (check_tx_key).\nmonero-wallet-gui : on the Advanced > Prove/Check page.\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the 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\nIf you cannot provide the above data or if you used an incompatible wallet it would result in losing the dispute case. The XMR sender is responsible to be able to verify the XMR 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 (https://www.getmonero.org/resources/user-guides/prove-payment.html) or the Monero forum (https://forum.getmonero.org) to find more information.
account.altcoin.popup.blur.msg=If you want to trade BLUR on Bisq please be sure 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 arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nIf you cannot provide the required information to the arbitrator, you will lose the dispute. In all cases of dispute, the BLUR sender bears 100% of the burden of responsiblity in verifying transactions to an arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW).
account.altcoin.popup.ccx.msg=If you want to trade CCX on Bisq please be sure you understand the following requirements:\n\nTo send CCX you must use an official Conceal wallet, either CLI or GUI. After sending a transfer payment, the wallets\ndisplay the transaction secret key. You must save it along with the transaction hash (ID) and the recipient's public\naddress in case arbitration is necessary. In such a case, you must give all three to the arbitrator, who will then\nverify the CCX transfer using the Conceal Transaction Viewer (https://explorer.conceal.network/txviewer).\nBecause Conceal is a privacy coin, block explorers cannot verify transfers.\n\nIf you cannot provide the required data to the arbitrator, you will lose the dispute case.\nIf you do not save the transaction secret key immediately after transferring CCX, it cannot be recovered later.\nIf you do not understand these requirements, seek help at the Conceal discord (http://discord.conceal.network).
account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides a transaction is not verifyable on the public blockchain. If required you can prove your payment thru use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at \ (http://drgl.info/#check_txn).\n\nIf you cannot provide the above data or if you used an incompatible wallet it would result in losing the dispute case. The Dragonglass sender is responsible to be able to verify the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help.
account.altcoin.popup.xmr.msg=Trading XMR on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending XMR, you need to use either the official Monero GUI wallet or Monero CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nmonero-wallet-cli (use the command get_tx_key)\nmonero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nIn addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\nmonero-wallet-cli : using command (check_tx_key).\nmonero-wallet-gui : on the Advanced > Prove/Check page.\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The XMR sender is responsible for providing verification of the XMR transfer to the arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) or the Monero forum (https://forum.getmonero.org) to find more information.
account.altcoin.popup.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 arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The 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 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 arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW).
account.altcoin.popup.ccx.msg=Trading CCX on Bisq requires that you understand the following requirements:\n\nTo send CCX you must use an official Conceal wallet, either CLI or GUI. After sending a transfer payment, the wallets\ndisplay the transaction secret key. You must save it along with the transaction hash (ID) and the recipient's public\naddress in case arbitration is necessary. In such a case, you must give all three to the arbitrator, who will then\nverify the CCX transfer using the Conceal Transaction Viewer (https://explorer.conceal.network/txviewer).\nBecause Conceal is a privacy coin, block explorers cannot verify transfers.\n\nFailure to provide the required data to the arbitrator will result in losing the dispute case.\nIf you do not save the transaction secret key immediately after transferring CCX, it cannot be recovered later.\nIf you do not understand these requirements, seek help at the Conceal discord (http://discord.conceal.network).
account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides, a transaction is not verifiable on the public blockchain. If required, you can prove your payment through the use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at (http://drgl.info/#check_txn).\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The Dragonglass sender is responsible for providing verification of the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help.
account.altcoin.popup.ZEC.msg=When using {0} you can only use the transparent addresses (starting with t) not the z-addresses (private), because the arbitrator would not be able to verify the transaction with z-addresses.
account.altcoin.popup.XZC.msg=When using {0} you can only use the transparent (traceable) addresses not the untraceable addresses, because the arbitrator would not be able to verify the transaction with untraceable addresses at a block explorer.
account.altcoin.popup.bch=Bitcoin Cash and Bitcoin Clashic suffer from replay protection. If you use those coins be sure you take sufficient precautions and understand all implications.You can suffer losses by sending one coin and unintentionally send the same coins on the other block chain.Because those "airdrop coins" share the same history with the Bitcoin blockchain there are also security risks and a considerable risk for losing privacy.\n\nPlease read at the Bisq Forum more about that topic: https://forum.bisq.io/t/airdrop-coins-information-thread-bch-btg-bchc
@ -1079,7 +1081,7 @@ dao.results.proposals.table.header.result=Vote result
dao.results.proposals.voting.detail.header=Vote results for selected proposal
# suppress inspection "UnusedProperty"
dao.param.UNDEFINED=Undefined
dao.param.UNDEFINED=Indéfini
# suppress inspection "UnusedProperty"
dao.param.DEFAULT_MAKER_FEE_BSQ=BSQ maker fee
@ -1165,7 +1167,7 @@ dao.results.cycle.value.postFix.isDefaultValue=(default value)
dao.results.cycle.value.postFix.hasChanged=(has been changed in voting)
# suppress inspection "UnusedProperty"
dao.phase.PHASE_UNDEFINED=Undefined
dao.phase.PHASE_UNDEFINED=Indéfini
# suppress inspection "UnusedProperty"
dao.phase.PHASE_PROPOSAL=Proposal phase
# suppress inspection "UnusedProperty"
@ -1306,10 +1308,10 @@ dao.burnBsq.assets.lookBackPeriod=Verification period
dao.burnBsq.assets.trialFee=Fee for trial period
dao.burnBsq.assets.totalFee=Total fees paid
dao.burnBsq.assets.days={0} days
dao.burnBsq.assets.toFewDays=The asset fee is too low. The min. amount of days for the trial perios is {0}.
dao.burnBsq.assets.toFewDays=The asset fee is too low. The min. amount of days for the trial period is {0}.
# suppress inspection "UnusedProperty"
dao.assetState.UNDEFINED=Undefined
dao.assetState.UNDEFINED=Indéfini
# suppress inspection "UnusedProperty"
dao.assetState.IN_TRIAL_PERIOD=In trial period
# suppress inspection "UnusedProperty"
@ -1341,7 +1343,7 @@ dao.proofOfBurn.verificationResult.ok=Verification succeeded
dao.proofOfBurn.verificationResult.failed=Verification failed
# suppress inspection "UnusedProperty"
dao.phase.UNDEFINED=Undefined
dao.phase.UNDEFINED=Indéfini
# suppress inspection "UnusedProperty"
dao.phase.PROPOSAL=Proposal phase
# suppress inspection "UnusedProperty"
@ -1369,7 +1371,7 @@ dao.phase.separatedPhaseBar.RESULT=Vote result
# suppress inspection "UnusedProperty"
dao.proposal.type.COMPENSATION_REQUEST=Requête de compensation
# suppress inspection "UnusedProperty"
dao.proposal.type.REIMBURSEMENT_REQUEST=Reimbursement request
dao.proposal.type.REIMBURSEMENT_REQUEST=Demande de remboursement
# suppress inspection "UnusedProperty"
dao.proposal.type.BONDED_ROLE=Proposal for a bonded role
# suppress inspection "UnusedProperty"
@ -1384,7 +1386,7 @@ dao.proposal.type.CONFISCATE_BOND=Proposal for confiscating a bond
# suppress inspection "UnusedProperty"
dao.proposal.type.short.COMPENSATION_REQUEST=Requête de compensation
# suppress inspection "UnusedProperty"
dao.proposal.type.short.REIMBURSEMENT_REQUEST=Reimbursement request
dao.proposal.type.short.REIMBURSEMENT_REQUEST=Demande de remboursement
# suppress inspection "UnusedProperty"
dao.proposal.type.short.BONDED_ROLE=Bonded role
# suppress inspection "UnusedProperty"
@ -1584,7 +1586,7 @@ displayUpdateDownloadWindow.verify.failed=Verification failed.\nPlease download
displayUpdateDownloadWindow.success=The new version has been successfully downloaded and the signature verified.\n\nPlease open the download directory, shut down the application and install the new version.
displayUpdateDownloadWindow.download.openDir=Open download directory
disputeRésuméWindow.title=Résumé
disputeSummaryWindow.title=Résumé
disputeSummaryWindow.openDate=Ticket opening date
disputeSummaryWindow.role=Trader's role
disputeSummaryWindow.evidence=Evidence
@ -1746,7 +1748,7 @@ popup.headline.error=Erreur
popup.doNotShowAgain=Ne plus me montrer
popup.reportError.log=Open log file
popup.reportError.gitHub=Report to GitHub issue tracker
popup.reportError={0}\n\nTo help us to improve the software please report the bug on our issue tracker on GitHub (https://github.com/bisq-network/bisq-desktop/issues).\nThe error message will be copied to the clipboard when you click a button below.\nIt will make debugging easier if you can attach the bisq.log file as well.
popup.reportError={0}\n\nTo help us to improve the software please report this bug by opening a new issue at https://github.com/bisq-network/bisq/issues.\nThe above error message will be copied to the clipboard when you click either of the buttons below.\nIt will make debugging easier if you include the bisq.log file by pressing "Open log file", saving a copy, and attaching it to your bug report.
popup.error.tryRestart=Please try to restart your application and check your network connection to see if you can resolve the issue.
popup.error.takeOfferRequestFailed=An error occurred when someone tried to take one of your offers:\n{0}
@ -1805,6 +1807,9 @@ popup.attention.forTradeWithId=Veuillez consulter votre échange ID {0}
popup.roundedFiatValues.headline=New privacy feature: Rounded fiat values
popup.roundedFiatValues.msg=To increase privacy of your trade the {0} amount was rounded.\n\nDepending on the client version you''ll pay or receive either values with decimals or rounded ones.\n\nBoth values do comply from now on with the trade protocol.\n\nAlso be aware that BTC values are changed automatically to match the rounded fiat amount as close as possible.
popup.info.multiplePaymentAccounts.headline=Multiple payment accounts available
popup.info.multiplePaymentAccounts.msg=You have multiple payment accounts available for this offer. Please make sure you've picked the right one.
####################################################################
# Notifications
@ -2085,7 +2090,7 @@ payment.clearXchange.info=Please be sure that you fulfill the requirements for t
payment.moneyGram.info=When using MoneyGram the BTC buyer has to send the Authorisation number and a photo of the receipt by email to the BTC seller. The receipt must clearly show the seller's full name, country, state and the amount. The buyer will get displayed the seller's email in the trade process.
payment.westernUnion.info=When using Western Union the BTC buyer has to send the MTCN (tracking number) and a photo of the receipt by email to the BTC seller. The receipt must clearly show the seller's full name, city, country and the amount. The buyer will get displayed the seller's email in the trade process.
payment.halCash.info=When using HalCash the BTC buyer need to send the BTC seller the HalCash code via a text message from the mobile phone.\n\nPlease make sure to not exceed the maximum amount your bank allows you to send with HalCash. The min. amount per withdrawal is 10 EUR and the max. amount is 600 EUR. For repeated withdrawals it is 3000 EUR per receiver per day and 6000 EUR per receiver per month. Please cross check those limits with your bank to be sure they use the same limits as stated here.\n\nThe withdrawal amount must be a multiple of 10 EUR as you cannot withdraw other amounts from an ATM. The UI in the create-offer and take-offer screen will adjust the BTC amount so that the EUR amount is correct. You cannot use market based price as the EUR amount would be changing with changing prices.\n\nIn case of a dispute the BTC buyer need to provide the proof that he sent the EUR.
payment.halCash.info=When using HalCash the BTC buyer needs to send the BTC seller the HalCash code via a text message from their mobile phone.\n\nPlease make sure to not exceed the maximum amount your bank allows you to send with HalCash. The min. amount per withdrawal is 10 EUR and the max. amount is 600 EUR. For repeated withdrawals it is 3000 EUR per receiver per day and 6000 EUR per receiver per month. Please cross check those limits with your bank to be sure they use the same limits as stated here.\n\nThe withdrawal amount must be a multiple of 10 EUR as you cannot withdraw other amounts from an ATM. The UI in the create-offer and take-offer screen will adjust the BTC amount so that the EUR amount is correct. You cannot use market based price as the EUR amount would be changing with changing prices.\n\nIn case of a dispute the BTC buyer needs to provide the proof that they sent the EUR.
payment.limits.info=Please be aware that all bank transfers carry a certain amount of chargeback risk.\n\nTo mitigate this risk, Bisq sets per-trade limits based on two factors:\n\n1. The estimated level of chargeback risk for the payment method used\n2. The age of your account for that payment method\n\nThe account you are creating now is new and its age is zero. As your account grows in age over a two-month period, your per-trade limits will grow along with it:\n\n● During the 1st month, your per-trade limit will be {0}\n● During the 2nd month, your per-trade limit will be {1}\n● After the 2nd month, your per-trade limit will be {2}\n\nPlease note that there are no limits on the total number of times you can trade.
payment.cashDeposit.info=Please confirm your bank allows you to send cash deposits into other peoples' accounts. For example, Bank of America and Wells Fargo no longer allow such deposits.
@ -2098,7 +2103,7 @@ payment.f2f.optionalExtra=Optional additional information
payment.f2f.extra=Additional information
payment.f2f.extra.prompt=The maker can define 'terms and conditions' or add a public contact information. It will be displayed with the offer.
payment.f2f.info='Face to Face' trades have different rules and come with different risks than online transactions.\n\nThe main differences are:\n● The trading peers need to exchange information about the meeting location and time by using their provided contact details.\n● The trading peers need to bring their laptops and do the confirmation of 'payment sent' and 'payment received' at the meeting place.\n● If a maker has special 'terms and conditions' he needs to state those in the 'Addition information' text field in the account.\n● By taking an offer the taker agrees to the maker's stated 'terms and conditions'.\n● In case of a dispute the arbitrator cannot help much as it is usually hard to get tamper proof evidence of what happened at the meeting. In such cases the BTC funds might get locked indefinitely or until the trading peers come to an agreement.\n\nTo be sure you fully understand the differences with 'Face to Face' trades please read the instructions and recommendations at: 'https://docs.bisq.network/trading-rules.html#f2f-trading'
payment.f2f.info='Face to Face' trades have different rules and come with different risks than online transactions.\n\nThe main differences are:\n● The trading peers need to exchange information about the meeting location and time by using their provided contact details.\n● The trading peers need to bring their laptops and do the confirmation of 'payment sent' and 'payment received' at the meeting place.\n● If a maker has special 'terms and conditions' they must state those in the 'Additional information' text field in the account.\n● By taking an offer the taker agrees to the maker's stated 'terms and conditions'.\n● In case of a dispute the arbitrator cannot help much as it is usually hard to get tamper proof evidence of what happened at the meeting. In such cases the BTC funds might get locked indefinitely or until the trading peers come to an agreement.\n\nTo be sure you fully understand the differences with 'Face to Face' trades please read the instructions and recommendations at: 'https://docs.bisq.network/trading-rules.html#f2f-trading'
payment.f2f.info.openURL=Open web page
payment.f2f.offerbook.tooltip.countryAndCity=County and city: {0} / {1}
payment.f2f.offerbook.tooltip.extra=Additional information: {0}

29
core/src/main/resources/i18n/displayStrings_hu.properties
View file

@ -299,6 +299,8 @@ market.trades.tooltip.candle.date=Dátum:
offerbook.createOffer=Ajánlat létrehozása
offerbook.takeOffer=Ajánlatot elfogadása
offerbook.takeOfferToBuy=Take offer to buy {0}
offerbook.takeOfferToSell=Take offer to sell {0}
offerbook.trader=Kereskedő
offerbook.offerersBankId=Ajánló bankazonosítója: {0}
offerbook.offerersBankName=Ajánló bank neve: {0}
@ -560,12 +562,12 @@ portfolio.pending.step3_buyer.warn.part1b=a fizetési szolgáltatódnál (péld
portfolio.pending.step3_buyer.warn.part2=A BTC eladó még mindig nem konfirmálta kifizetését!\nKérjük ellenőrizze ha a {0} átutálása sikeres volt.\nHa a BTC eladó nem igazolja a kifizetés beérkezését {1}-ig, a tranzakció a bíróhoz kerül vizsgálatra.
portfolio.pending.step3_buyer.openForDispute=A BTC vevő még nem konfirmálta fizetését!\nA tranzakció maximális megengedett időtartama lejárt.\nVárakozhat hosszabb ideig, ezennel több időt adhatna váltótársának vagy kapcsolatba léphet a bíróval egy vita megnyitásához.
# suppress inspection "TrailingSpacesInProperty"
portfolio.pending.step3_seller.part=Váltótársa visszaigazolta, hogy kezdeményezte a {0} kifizetést.\n\n
portfolio.pending.step3_seller.part=Your trading partner has confirmed that they have initiated the {0} payment.\n\n
portfolio.pending.step3_seller.altcoin.explorer=on your favorite {0} blockchain explorer
portfolio.pending.step3_seller.altcoin.wallet=at your {0} wallet
portfolio.pending.step3_seller.altcoin={0}Please check {1} if the transaction to your receiving address\n{2}\nhas already sufficient blockchain confirmations.\nThe payment amount has to be {3}\n\nYou can copy & paste your {4} address from the main screen after closing that popup.
portfolio.pending.step3_seller.postal={0}Kérjük ellenőrizze, hogy megkapta-e a {1} \"US Posta Pénz Rendeléssen\" keresztül a BTC vevőjétől.\n\nA tranzakció azonosítója (\"fizetés indoka\" szövege): \"{2}\"
portfolio.pending.step3_seller.bank=Your trading partner has confirmed that he initiated the {0} payment.\n\nPlease go to your online banking web page and check if you have received {1} from the BTC buyer.\n\nThe trade ID (\"reason for payment\" text) of the transaction is: \"{2}\"\n\n
portfolio.pending.step3_seller.bank=Your trading partner has confirmed that they have initiated the {0} payment.\n\nPlease go to your online banking web page and check if you have received {1} from the BTC buyer.\n\nThe trade ID (\"reason for payment\" text) of the transaction is: \"{2}\"\n\n
portfolio.pending.step3_seller.cash=Because the payment is done via Cash Deposit the BTC buyer has to write \"NO REFUND\" on the paper receipt, tear it in 2 parts and send you a photo by email.\n\nTo avoid chargeback risk, only confirm if you received the email and if you are sure the paper receipt is valid.\nIf you are not sure, {0}
portfolio.pending.step3_seller.moneyGram=The buyer has to send you the Authorisation number and a photo of the receipt by email.\nThe receipt must clearly show your full name, country, state and the amount. Please check your email if you received the Authorisation number.\n\nAfter closing that popup you will see the BTC buyer's name and address for picking up the money from MoneyGram.\n\nOnly confirm receipt after you have successfully picked up the money!
portfolio.pending.step3_seller.westernUnion=A vevőnek el kell küldenie az MTCN-t (nyomon követési számot) és egy átvételről készült fényképet e-mailen keresztül.\nAz átvételi elismervényen egyértelműen meg kell jelennie a teljes neve, városa, országa illetve az összeg. Kérjük ellenőrizze e-mailjét, hogy megkapta-e az MTCN-t.\n\nMiután lezárta a felugró ablakot, látni fogja a BTC vásárló nevét és címét, hogy felemelhesse Western Uniótól a pénzt.\n\nCsak azután fogadja el a kézhezvételt, miután sikeresen felemelte a pénzt!
@ -926,10 +928,10 @@ account.arbitratorSelection.minOne=Legalább egy bírót kell választania.
account.altcoin.yourAltcoinAccounts=Your altcoin accounts
account.altcoin.popup.wallet.msg=Please be sure that you follow the requirements for the usage of {0} wallets as described on the {1} web page.\nUsing wallets from centralized exchanges where (a) you don''t control your keys or (b) which don''t use compatible wallet software is risky: it can lead to loss of the traded funds!\nThe arbitrator is not a {2} specialist and cannot help in such cases.
account.altcoin.popup.wallet.confirm=Megértem és alátámasztom, hogy tudom, melyik pénztárcát kell használnom.
account.altcoin.popup.xmr.msg=If you want to trade XMR on Bisq please be sure you understand and fulfill the following requirements:\n\nFor sending XMR you need to use either the official Monero GUI wallet or Monero CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nmonero-wallet-cli (use the command get_tx_key)\nmonero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nIn addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\nmonero-wallet-cli : using command (check_tx_key).\nmonero-wallet-gui : on the Advanced > Prove/Check page.\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the 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\nIf you cannot provide the above data or if you used an incompatible wallet it would result in losing the dispute case. The XMR sender is responsible to be able to verify the XMR 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 (https://www.getmonero.org/resources/user-guides/prove-payment.html) or the Monero forum (https://forum.getmonero.org) to find more information.
account.altcoin.popup.blur.msg=If you want to trade BLUR on Bisq please be sure 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 arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nIf you cannot provide the required information to the arbitrator, you will lose the dispute. In all cases of dispute, the BLUR sender bears 100% of the burden of responsiblity in verifying transactions to an arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW).
account.altcoin.popup.ccx.msg=If you want to trade CCX on Bisq please be sure you understand the following requirements:\n\nTo send CCX you must use an official Conceal wallet, either CLI or GUI. After sending a transfer payment, the wallets\ndisplay the transaction secret key. You must save it along with the transaction hash (ID) and the recipient's public\naddress in case arbitration is necessary. In such a case, you must give all three to the arbitrator, who will then\nverify the CCX transfer using the Conceal Transaction Viewer (https://explorer.conceal.network/txviewer).\nBecause Conceal is a privacy coin, block explorers cannot verify transfers.\n\nIf you cannot provide the required data to the arbitrator, you will lose the dispute case.\nIf you do not save the transaction secret key immediately after transferring CCX, it cannot be recovered later.\nIf you do not understand these requirements, seek help at the Conceal discord (http://discord.conceal.network).
account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides a transaction is not verifyable on the public blockchain. If required you can prove your payment thru use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at \ (http://drgl.info/#check_txn).\n\nIf you cannot provide the above data or if you used an incompatible wallet it would result in losing the dispute case. The Dragonglass sender is responsible to be able to verify the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help.
account.altcoin.popup.xmr.msg=Trading XMR on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending XMR, you need to use either the official Monero GUI wallet or Monero CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nmonero-wallet-cli (use the command get_tx_key)\nmonero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nIn addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\nmonero-wallet-cli : using command (check_tx_key).\nmonero-wallet-gui : on the Advanced > Prove/Check page.\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The XMR sender is responsible for providing verification of the XMR transfer to the arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) or the Monero forum (https://forum.getmonero.org) to find more information.
account.altcoin.popup.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 arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The 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 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 arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW).
account.altcoin.popup.ccx.msg=Trading CCX on Bisq requires that you understand the following requirements:\n\nTo send CCX you must use an official Conceal wallet, either CLI or GUI. After sending a transfer payment, the wallets\ndisplay the transaction secret key. You must save it along with the transaction hash (ID) and the recipient's public\naddress in case arbitration is necessary. In such a case, you must give all three to the arbitrator, who will then\nverify the CCX transfer using the Conceal Transaction Viewer (https://explorer.conceal.network/txviewer).\nBecause Conceal is a privacy coin, block explorers cannot verify transfers.\n\nFailure to provide the required data to the arbitrator will result in losing the dispute case.\nIf you do not save the transaction secret key immediately after transferring CCX, it cannot be recovered later.\nIf you do not understand these requirements, seek help at the Conceal discord (http://discord.conceal.network).
account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides, a transaction is not verifiable on the public blockchain. If required, you can prove your payment through the use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at (http://drgl.info/#check_txn).\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The Dragonglass sender is responsible for providing verification of the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help.
account.altcoin.popup.ZEC.msg=A {0} használatakor csak átlátható címeket használhat (t-vel kezdődve) nem pedig a z-címeket (privát), mivel hogy a bíró nem tudja ellenőrizni a z-címekkel kezdődő tranzakciókat.
account.altcoin.popup.XZC.msg=A {0} használatakor csak átlátható (nyomon követhető) címeket használhat, nem pedig lenyomozhatatlan címeket, mivel hogy a bíró nem tudja ellenőrizni a tranzakciót lenyomozhatatlan címmel a blokkböngészőben.
account.altcoin.popup.bch=Bitcoin Cash és Bitcoin Clashic ismételt védelemben részesül. Ha ezeket az érméket használja, győződjön meg róla, hogy elegendő óvintézkedést és minden következtetést megért. Veszteségeket szenvedhet úgy, hogy egy érmét küld és szándék nélkül ugyanazokat az érméket küldi a másik blokkláncon. Mivel ezek a "légpénzes érmék" ugyanazt a történelmet osztják a Bitcoin blokkhálózattal, szintén vannak biztonsági kockázatok és jelentős rizikót jelent a magánélet elvesztését illetően.\n\nKérjük olvasson többet erről a témáról a Bisq fórumon: https://forum.bisq.io/t/airdrop-coins-information-thread-bch-btg-bchc
@ -1306,7 +1308,7 @@ dao.burnBsq.assets.lookBackPeriod=Verification period
dao.burnBsq.assets.trialFee=Fee for trial period
dao.burnBsq.assets.totalFee=Total fees paid
dao.burnBsq.assets.days={0} days
dao.burnBsq.assets.toFewDays=The asset fee is too low. The min. amount of days for the trial perios is {0}.
dao.burnBsq.assets.toFewDays=The asset fee is too low. The min. amount of days for the trial period is {0}.
# suppress inspection "UnusedProperty"
dao.assetState.UNDEFINED=Határozatlan
@ -1584,7 +1586,7 @@ displayUpdateDownloadWindow.verify.failed=Sikertelen ellenőrzés.\nKérjük tö
displayUpdateDownloadWindow.success=Az új verziót sikeresen letöltötték és az aláírást ellenőrizték.\n\nKérjük nyissa meg a letöltési könyvtárat, állítsa le az alkalmazást és telepítse az új verziót.
displayUpdateDownloadWindow.download.openDir=Letöltési könyvtár megnyitása
disputeÖsszefoglóWindow.title=Összefogló
disputeSummaryWindow.title=Összefogló
disputeSummaryWindow.openDate=Ticket opening date
disputeSummaryWindow.role=Trader's role
disputeSummaryWindow.evidence=Evidence
@ -1746,7 +1748,7 @@ popup.headline.error=Hiba
popup.doNotShowAgain=Ne mutasd ezt újra
popup.reportError.log=Naplófájl nyitása
popup.reportError.gitHub=Jelentés a Github kibocsátás-követőhöz
popup.reportError={0}\n\nTo help us to improve the software please report the bug on our issue tracker on GitHub (https://github.com/bisq-network/bisq-desktop/issues).\nThe error message will be copied to the clipboard when you click a button below.\nIt will make debugging easier if you can attach the bisq.log file as well.
popup.reportError={0}\n\nTo help us to improve the software please report this bug by opening a new issue at https://github.com/bisq-network/bisq/issues.\nThe above error message will be copied to the clipboard when you click either of the buttons below.\nIt will make debugging easier if you include the bisq.log file by pressing "Open log file", saving a copy, and attaching it to your bug report.
popup.error.tryRestart=Próbálja meg újraindítani az alkalmazást, és ellenőrizze a hálózati kapcsolatot, hogy meg tudja-e oldani a problémát.
popup.error.takeOfferRequestFailed=Hiba történt amikor valaki megpróbálta felvenni ajánlatát:\n{0}
@ -1805,6 +1807,9 @@ popup.attention.forTradeWithId=Figyelem szükséges a {0} azonosítóval rendelk
popup.roundedFiatValues.headline=New privacy feature: Rounded fiat values
popup.roundedFiatValues.msg=To increase privacy of your trade the {0} amount was rounded.\n\nDepending on the client version you''ll pay or receive either values with decimals or rounded ones.\n\nBoth values do comply from now on with the trade protocol.\n\nAlso be aware that BTC values are changed automatically to match the rounded fiat amount as close as possible.
popup.info.multiplePaymentAccounts.headline=Multiple payment accounts available
popup.info.multiplePaymentAccounts.msg=You have multiple payment accounts available for this offer. Please make sure you've picked the right one.
####################################################################
# Notifications
@ -1875,7 +1880,7 @@ table.placeholder.noData=Jelenleg nincs adat
peerInfoIcon.tooltip.tradePeer=Váltótársak
peerInfoIcon.tooltip.maker=Ajánló
peerInfoIcon.tooltip.trade.traded={0} Onion cím: {1}\nMár {2} alkalommal üzletelt ezzel a felhasználóval\n{3}
peerInfoIcon.tooltip.trade.notTraded={0} Onion cím: {1}\nMég nem üzletelt eddig ezzel a felhasználóval.\n{3}
peerInfoIcon.tooltip.trade.notTraded={0} Onion cím: {1}\nMég nem üzletelt eddig ezzel a felhasználóval.\n{2}
peerInfoIcon.tooltip.age=Fizetési fiók létrehozva {0} ezelőtt.
peerInfoIcon.tooltip.unknownAge=Fizetési számla kora nem ismert.
@ -2085,7 +2090,7 @@ payment.clearXchange.info=Please be sure that you fulfill the requirements for t
payment.moneyGram.info=When using MoneyGram the BTC buyer has to send the Authorisation number and a photo of the receipt by email to the BTC seller. The receipt must clearly show the seller's full name, country, state and the amount. The buyer will get displayed the seller's email in the trade process.
payment.westernUnion.info=When using Western Union the BTC buyer has to send the MTCN (tracking number) and a photo of the receipt by email to the BTC seller. The receipt must clearly show the seller's full name, city, country and the amount. The buyer will get displayed the seller's email in the trade process.
payment.halCash.info=When using HalCash the BTC buyer need to send the BTC seller the HalCash code via a text message from the mobile phone.\n\nPlease make sure to not exceed the maximum amount your bank allows you to send with HalCash. The min. amount per withdrawal is 10 EUR and the max. amount is 600 EUR. For repeated withdrawals it is 3000 EUR per receiver per day and 6000 EUR per receiver per month. Please cross check those limits with your bank to be sure they use the same limits as stated here.\n\nThe withdrawal amount must be a multiple of 10 EUR as you cannot withdraw other amounts from an ATM. The UI in the create-offer and take-offer screen will adjust the BTC amount so that the EUR amount is correct. You cannot use market based price as the EUR amount would be changing with changing prices.\n\nIn case of a dispute the BTC buyer need to provide the proof that he sent the EUR.
payment.halCash.info=When using HalCash the BTC buyer needs to send the BTC seller the HalCash code via a text message from their mobile phone.\n\nPlease make sure to not exceed the maximum amount your bank allows you to send with HalCash. The min. amount per withdrawal is 10 EUR and the max. amount is 600 EUR. For repeated withdrawals it is 3000 EUR per receiver per day and 6000 EUR per receiver per month. Please cross check those limits with your bank to be sure they use the same limits as stated here.\n\nThe withdrawal amount must be a multiple of 10 EUR as you cannot withdraw other amounts from an ATM. The UI in the create-offer and take-offer screen will adjust the BTC amount so that the EUR amount is correct. You cannot use market based price as the EUR amount would be changing with changing prices.\n\nIn case of a dispute the BTC buyer needs to provide the proof that they sent the EUR.
payment.limits.info=Kérjük vegye figyelembe, hogy minden banki átutalás bizonyos mértékű visszaterhelési kockázatot hordoz.\n\nE kockázat enyhítése érdekében Bisq két tényező alapján határozza meg a tranzakciók korlátozását:\n\n1. Az alkalmazott fizetési módra vonatkozó visszavásárlási kockázat becsült szintje\n2. Fiókja kora az adott fizetési mód esetében\n\nA most létrehozott fiókja új és kora nulla. Mivel fiókja egy két hónapos időszakon keresztül növekszik, a tranzakciós korlátaival együtt fog növekedni:\n\n● Az első hónap folyamán a tranzakció korláta {0}\n● A második hónapban folyamán a tranzakció korláta {1}\n● A második hónap elmúltja után a tranzakció korláta {2}\n\nKérjük vegye figyelembe, hogy nincs korlátozás az összes tranzakcióra vonatkozóan.
payment.cashDeposit.info=Please confirm your bank allows you to send cash deposits into other peoples' accounts. For example, Bank of America and Wells Fargo no longer allow such deposits.
@ -2098,7 +2103,7 @@ payment.f2f.optionalExtra=Optional additional information
payment.f2f.extra=Additional information
payment.f2f.extra.prompt=The maker can define 'terms and conditions' or add a public contact information. It will be displayed with the offer.
payment.f2f.info='Face to Face' trades have different rules and come with different risks than online transactions.\n\nThe main differences are:\n● The trading peers need to exchange information about the meeting location and time by using their provided contact details.\n● The trading peers need to bring their laptops and do the confirmation of 'payment sent' and 'payment received' at the meeting place.\n● If a maker has special 'terms and conditions' he needs to state those in the 'Addition information' text field in the account.\n● By taking an offer the taker agrees to the maker's stated 'terms and conditions'.\n● In case of a dispute the arbitrator cannot help much as it is usually hard to get tamper proof evidence of what happened at the meeting. In such cases the BTC funds might get locked indefinitely or until the trading peers come to an agreement.\n\nTo be sure you fully understand the differences with 'Face to Face' trades please read the instructions and recommendations at: 'https://docs.bisq.network/trading-rules.html#f2f-trading'
payment.f2f.info='Face to Face' trades have different rules and come with different risks than online transactions.\n\nThe main differences are:\n● The trading peers need to exchange information about the meeting location and time by using their provided contact details.\n● The trading peers need to bring their laptops and do the confirmation of 'payment sent' and 'payment received' at the meeting place.\n● If a maker has special 'terms and conditions' they must state those in the 'Additional information' text field in the account.\n● By taking an offer the taker agrees to the maker's stated 'terms and conditions'.\n● In case of a dispute the arbitrator cannot help much as it is usually hard to get tamper proof evidence of what happened at the meeting. In such cases the BTC funds might get locked indefinitely or until the trading peers come to an agreement.\n\nTo be sure you fully understand the differences with 'Face to Face' trades please read the instructions and recommendations at: 'https://docs.bisq.network/trading-rules.html#f2f-trading'
payment.f2f.info.openURL=Open web page
payment.f2f.offerbook.tooltip.countryAndCity=County and city: {0} / {1}
payment.f2f.offerbook.tooltip.extra=Additional information: {0}

47
core/src/main/resources/i18n/displayStrings_pt.properties
View file

@ -299,6 +299,8 @@ market.trades.tooltip.candle.date=Data:
offerbook.createOffer=Criar oferta
offerbook.takeOffer=Aceitar
offerbook.takeOfferToBuy=Take offer to buy {0}
offerbook.takeOfferToSell=Take offer to sell {0}
offerbook.trader=Trader
offerbook.offerersBankId=ID do banco do ofertante (BIC/SWIFT): {0}
offerbook.offerersBankName=Nome do banco do ofertante: {0}
@ -346,7 +348,7 @@ offerbook.info.sellAboveMarketPrice=Você irá receber {0} a mais do que o atual
offerbook.info.buyBelowMarketPrice=Você irá pagar {0} a menos do que o atual preço de mercado (atualizado a cada minuto).
offerbook.info.buyAtFixedPrice=Você irá comprar nesse preço fixo.
offerbook.info.sellAtFixedPrice=Você irá vender neste preço fixo.
offerbook.info.noArbitrationInUserLanguage=O idioma do Bisq atualmente está definido para {1}. No entanto, em caso de disputa, a arbitragem para essa oferta será realizada em {0}.
offerbook.info.noArbitrationInUserLanguage=O idioma do Bisq atualmente está definido para {1}. No entanto, em caso de disputa, a arbitragem para essa oferta será realizada em {0}.
offerbook.info.roundedFiatVolume=O montante foi arredondado para aumentar a privacidade do seu comércio.
####################################################################
@ -506,7 +508,7 @@ portfolio.pending.step2_buyer.cash.extra=REQUESITO IMPORTANTE:\nApós executar o
portfolio.pending.step2_buyer.moneyGram=Por favor, pague {0} ao vendedor de BTC usando MoneyGram.\n\n
portfolio.pending.step2_buyer.moneyGram.extra=IMPORTANTE:\nApós você ter feito o pagamento, envie o número de autorização e uma foto do recibo por e-mail para o vendedor de BTC.\nO recibo deve exibir claramente o nome completo, o país e o estado do vendedor, assim como a quantia. O e-mail do vendedor é: {0}.
portfolio.pending.step2_buyer.westernUnion=Por favor, pague {0} ao vendedor de BTC através da Western Union.\n\n
portfolio.pending.step2_buyer.westernUnion.extra=IMPORTANT REQUIREMENT:\nAfter you have done the payment send the MTCN (tracking number) and a photo of the receipt by email to the BTC seller.\nThe receipt must clearly show the seller''s full name, city, country and the amount. The seller''s email is: {0}.
portfolio.pending.step2_buyer.westernUnion.extra=IMPORTANTE:\nApós você ter feito o pagamento, envie o número de rastreamento (MTCN) e uma foto do recibo por e-mail para o vendedor de BTC.\nO recibo deve exibir claramente o nome completo, o país e o estado do vendedor, assim como a quantia. O e-mail do vendedor é: {0}.
# suppress inspection "TrailingSpacesInProperty"
portfolio.pending.step2_buyer.postal=Envie {0} através de \"US Postal Money Order\" para o vendedor de BTC.\n\n
@ -560,12 +562,12 @@ portfolio.pending.step3_buyer.warn.part1b=com seu provedor de pagamentos (por ex
portfolio.pending.step3_buyer.warn.part2=O vendedor de BTC ainda não confirmou o pagamento!\nPor favor, verifique em {0} se o pagamento foi enviado com sucesso.\nCaso o vendedor não confirme o recebimento do pagamento até {1}, a negociação será investigada pelo árbitro.
portfolio.pending.step3_buyer.openForDispute=O vendedor de BTC não confirmou o seu pagamento!\nO período máximo para essa 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 um árbitro para abrir uma disputa.
# suppress inspection "TrailingSpacesInProperty"
portfolio.pending.step3_seller.part=Seu parceiro de negociação confirmou que iniciou o pagamento de {0}.\n\n
portfolio.pending.step3_seller.part=Your trading partner has confirmed that they have initiated the {0} payment.\n\n
portfolio.pending.step3_seller.altcoin.explorer=em seu explorador preferido da blockchain do {0}
portfolio.pending.step3_seller.altcoin.wallet=em sua carteira {0}
portfolio.pending.step3_seller.altcoin={0}Verifique em {1} se a transação para o seu endereço de recebimento\n{2}\njá tem confirmações suficientes na blockchain.\nA quantia do pagamento deve ser {3}\n\nVocê pode copiar e colar seu endereço {4} na janela principal, após fechar aquele popup.
portfolio.pending.step3_seller.postal={0}Por gentileza verifique se recebeu {1} como \"US Postal Money Order\" do comprador de BTC.\n\nO ID de negociação (texto \"razão do pagamento\") da transação é: \"{2}\"
portfolio.pending.step3_seller.bank=Seu parceiro de negociação confirmou que ele já iniciou o pagamento de {0}.\n\nAcesse sua conta bancária online e verifique se você recebeu {1} do comprador de BTC.\n\nO ID de negociação (texto \"razão do pagamento\") da transação é: \"{2}\"
portfolio.pending.step3_seller.bank=Your trading partner has confirmed that they have initiated the {0} payment.\n\nPlease go to your online banking web page and check if you have received {1} from the BTC buyer.\n\nThe trade ID (\"reason for payment\" text) of the transaction is: \"{2}\"\n\n
portfolio.pending.step3_seller.cash=\n\nComo o pagamento é realizado através de depósito de dinheiro, o comprador de BTC deve escrever \"SEM RESTITUIÇÃO\" no recibo de papel, rasgá-lo em duas partes e enviar uma foto do recibo para você por e-mail.\n\nPara evitar risco de restituição, apenas confirme caso você tenha recebido o e-mail e tem certeza de que o recibo é válido.\nSe não tiver certeza, {0}
portfolio.pending.step3_seller.moneyGram=The buyer has to send you the Authorisation number and a photo of the receipt by email.\nThe receipt must clearly show your full name, country, state and the amount. Please check your email if you received the Authorisation number.\n\nAfter closing that popup you will see the BTC buyer's name and address for picking up the money from MoneyGram.\n\nOnly confirm receipt after you have successfully picked up the money!
portfolio.pending.step3_seller.westernUnion=The buyer has to send you the MTCN (tracking number) and a photo of the receipt by email.\nThe receipt must clearly show your full name, city, country and the amount. Please check your email if you received the MTCN.\n\nAfter closing that popup you will see the BTC buyer's name and address for picking up the money from Western Union.\n\nOnly confirm receipt after you have successfully picked up the money!
@ -667,7 +669,7 @@ funds.tab.transactions=Transações
funds.deposit.unused=Não utilizado
funds.deposit.usedInTx=Utilizado em {0} transações
funds.deposit.fundBisqWallet=Depósito em carteira Bisq
funds.deposit.fundBisqWallet=Deposito em carteira Bisq
funds.deposit.noAddresses=Nenhum endereço de depósito foi gerado ainda
funds.deposit.fundWallet=Financiar sua carteira
funds.deposit.withdrawFromWallet=Enviar fundos da carteira
@ -858,10 +860,10 @@ settings.net.directPeer=Par (direto)
settings.net.peer=Par
settings.net.inbound=entrante
settings.net.outbound=sainte
settings.net.reSyncSPVChainLabel=Resincronizar SPV chain
settings.net.reSyncSPVChainButton=Remover arquivo SPV e resincronizar
settings.net.reSyncSPVSuccess=The SPV chain file will be deleted at the next startup. You need to restart your application now.\n\nAfter the restart it can take a while for resyncing with the network and you will only see all transactions once the resync is completed.\n\nPlease make another restart after the resync has completed because there are sometimes inconsistencies leading to incorrect balance display.
settings.net.reSyncSPVAfterRestart=O arquivo SPV chain foi removido. Favor tenha paciencia, pois pode demorar para resincronizar à rede.
settings.net.reSyncSPVChainLabel=Ressincronizar SPV chain
settings.net.reSyncSPVChainButton=Remover arquivo SPV e ressincronizar
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\nPlease restart again after the resync has completed because there are sometimes inconsistencies that result in incorrect balances to display.
settings.net.reSyncSPVAfterRestart=The SPV chain file has been deleted. Please be patient. It can take a while to resync with the network.
settings.net.reSyncSPVAfterRestartCompleted=A resincronização concluiu. Favor reiniciar o programa.
settings.net.reSyncSPVFailed=Não foi possível apagar o arquivo da SPV chain.\nErro: {0}
setting.about.aboutBisq=Sobre Bisq
@ -926,10 +928,10 @@ account.arbitratorSelection.minOne=Você precisa selecionar ao menos um árbitro
account.altcoin.yourAltcoinAccounts=Suas contas de altcoins
account.altcoin.popup.wallet.msg=Please be sure that you follow the requirements for the usage of {0} wallets as described on the {1} web page.\nUsing wallets from centralized exchanges where (a) you don''t control your keys or (b) which don''t use compatible wallet software is risky: it can lead to loss of the traded funds!\nThe arbitrator is not a {2} specialist and cannot help in such cases.
account.altcoin.popup.wallet.confirm=Eu entendo e confirmo que eu sei qual carteira que preciso usar.
account.altcoin.popup.xmr.msg=Para negociar XMR no Bisq, certifique-se de que você entende e satisfaz os seguintes requisitos:\n\nPara enviar XMR você precisa usar uma carteira oficial do Monero (a carteira GUI ou a carteira CLI) com a flag store-tx-info habilitada (esta flag já vem habilitada por padrão nas novas versões). Certifique-se de que você consegue acessar a chave de transação (tx key), pois ela será necessária caso alguma disputa seja aberta.\nCarteira CLI (linha de comando): use o comando get_tx_key\nCarteira GUI: entre na aba Histórico e clique no botão (P) para provar um pagamento\n\nVocê pode conferir/verificar a transação através da ferramenta XMR checktx tool (https://xmr.llcoins.net/checktx.html) ou através da própria carteira.\nCarteira CLI: usando o comando (check_tx_key).\nCarteira GUI: na aba Avançado > Provar/Conferir.\nNormalmente as transferências não podem ser verificadas nos sites exploradores da blockchain do Monero\n\nCaso surja uma disputa, você precisará prover ao árbitro os seguintes dados:\n- A chave privada da transação\n- O hash da transação\n- O endereço público do recipiente\n\nSe você não conseguir prover os dados acima para o árbitro, ou se tiver usado uma carteira que não fornece estes dados, você irá perder a disputa. Nas negociações de Monero no Bisq, o remetente de XMR é a pessoa que é responsável por conseguir verificar a transferência de XMR para o árbitro em caso de disputa.\n\nO ID do pagamento não é necessário.\nSe você ainda tiver dúvidas sobre como funciona o processo, visite (https://www.getmonero.org/resources/user-guides/prove-payment.html) ou o fórum do Monero (https://forum.getmonero.org) para obter maiores informações.
account.altcoin.popup.blur.msg=If you want to trade BLUR on Bisq please be sure 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 arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nIf you cannot provide the required information to the arbitrator, you will lose the dispute. In all cases of dispute, the BLUR sender bears 100% of the burden of responsiblity in verifying transactions to an arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW).
account.altcoin.popup.ccx.msg=If you want to trade CCX on Bisq please be sure you understand the following requirements:\n\nTo send CCX you must use an official Conceal wallet, either CLI or GUI. After sending a transfer payment, the wallets\ndisplay the transaction secret key. You must save it along with the transaction hash (ID) and the recipient's public\naddress in case arbitration is necessary. In such a case, you must give all three to the arbitrator, who will then\nverify the CCX transfer using the Conceal Transaction Viewer (https://explorer.conceal.network/txviewer).\nBecause Conceal is a privacy coin, block explorers cannot verify transfers.\n\nIf you cannot provide the required data to the arbitrator, you will lose the dispute case.\nIf you do not save the transaction secret key immediately after transferring CCX, it cannot be recovered later.\nIf you do not understand these requirements, seek help at the Conceal discord (http://discord.conceal.network).
account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides a transaction is not verifyable on the public blockchain. If required you can prove your payment thru use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at \ (http://drgl.info/#check_txn).\n\nIf you cannot provide the above data or if you used an incompatible wallet it would result in losing the dispute case. The Dragonglass sender is responsible to be able to verify the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help.
account.altcoin.popup.xmr.msg=Trading XMR on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending XMR, you need to use either the official Monero GUI wallet or Monero CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nmonero-wallet-cli (use the command get_tx_key)\nmonero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nIn addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\nmonero-wallet-cli : using command (check_tx_key).\nmonero-wallet-gui : on the Advanced > Prove/Check page.\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The XMR sender is responsible for providing verification of the XMR transfer to the arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) or the Monero forum (https://forum.getmonero.org) to find more information.
account.altcoin.popup.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 arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The 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 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 arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW).
account.altcoin.popup.ccx.msg=Trading CCX on Bisq requires that you understand the following requirements:\n\nTo send CCX you must use an official Conceal wallet, either CLI or GUI. After sending a transfer payment, the wallets\ndisplay the transaction secret key. You must save it along with the transaction hash (ID) and the recipient's public\naddress in case arbitration is necessary. In such a case, you must give all three to the arbitrator, who will then\nverify the CCX transfer using the Conceal Transaction Viewer (https://explorer.conceal.network/txviewer).\nBecause Conceal is a privacy coin, block explorers cannot verify transfers.\n\nFailure to provide the required data to the arbitrator will result in losing the dispute case.\nIf you do not save the transaction secret key immediately after transferring CCX, it cannot be recovered later.\nIf you do not understand these requirements, seek help at the Conceal discord (http://discord.conceal.network).
account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides, a transaction is not verifiable on the public blockchain. If required, you can prove your payment through the use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at (http://drgl.info/#check_txn).\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The Dragonglass sender is responsible for providing verification of the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help.
account.altcoin.popup.ZEC.msg=Quando usar {0} você pode apenas utilizar endereços transparentes (começando com t) não os endereços z (privados), pois o árbitro não conseguiria verificar a transação com endereços z.
account.altcoin.popup.XZC.msg=Ao usar {0}, você obrigatoriamente precisa usar endereços transparentes (rastreáveis), caso contrário o árbitro não conseguiria verificar em um explorador de blocos uma transação com endereço privado (irrastreável).
account.altcoin.popup.bch=Bitcoin Cash and Bitcoin Clashic suffer from replay protection. If you use those coins be sure you take sufficient precautions and understand all implications.You can suffer losses by sending one coin and unintentionally send the same coins on the other block chain.Because those "airdrop coins" share the same history with the Bitcoin blockchain there are also security risks and a considerable risk for losing privacy.\n\nPlease read at the Bisq Forum more about that topic: https://forum.bisq.io/t/airdrop-coins-information-thread-bch-btg-bchc
@ -1019,7 +1021,7 @@ account.notifications.marketAlert.manageAlerts.header.offerType=Tipo de oferta
account.notifications.marketAlert.message.title=Alerta de oferta
account.notifications.marketAlert.message.msg.below=abaixo
account.notifications.marketAlert.message.msg.above=acima
account.notifications.marketAlert.message.msg=A new ''{0} {1}'' offer with price {2} ({3} {4} market price) and payment method ''{5}'' was published to the Bisq offerbook.\nOffer ID: {6}.
account.notifications.marketAlert.message.msg=Uma nova ''{0} {1}'' oferta com preço {2} ({3} {4} preço de mercado) e com o método de pagamento ''{5}'' foi publicada no livro de ofertas do Bisq.\nID da oferta: {6}.
account.notifications.priceAlert.message.title=Alerta de preço para {0}
account.notifications.priceAlert.message.msg=O seu preço de alerta foi atingido. O preço atual da {0} é {1} {2}
account.notifications.noWebCamFound.warning=Nenhuma webcam foi encontrada.\n\nPor favor, use a opção e-mail para enviar o token e a chave de criptografia do seu celular para o Bisq
@ -1306,7 +1308,7 @@ dao.burnBsq.assets.lookBackPeriod=Verification period
dao.burnBsq.assets.trialFee=Fee for trial period
dao.burnBsq.assets.totalFee=Total de taxas pagas
dao.burnBsq.assets.days={0} dias
dao.burnBsq.assets.toFewDays=The asset fee is too low. The min. amount of days for the trial perios is {0}.
dao.burnBsq.assets.toFewDays=The asset fee is too low. The min. amount of days for the trial period is {0}.
# suppress inspection "UnusedProperty"
dao.assetState.UNDEFINED=Indefinido
@ -1322,7 +1324,7 @@ dao.assetState.REMOVED_BY_VOTING=Removed by voting
dao.proofOfBurn.header=Proof of burn
dao.proofOfBurn.amount=Quantia
dao.proofOfBurn.preImage=Pre-image
dao.proofOfQueimar.burn=Queimar
dao.proofOfBurn.burn=Queimar
dao.proofOfBurn.allTxs=All proof of burn transactions
dao.proofOfBurn.myItems=My proof of burn transactions
dao.proofOfBurn.date=Data
@ -1584,7 +1586,7 @@ displayUpdateDownloadWindow.verify.failed=Falha durante a verificação.\nPor fa
displayUpdateDownloadWindow.success=A nova versão foi baixada com sucesso e teve a sua assinatura verificada.\n\nPara usá-la, abra a pasta de downloads, feche o programa e instale a nova versão.
displayUpdateDownloadWindow.download.openDir=Abrir pasta de download
disputeResumoWindow.title=Resumo
disputeSummaryWindow.title=Resumo
disputeSummaryWindow.openDate=Data da abertura do ticket
disputeSummaryWindow.role=Trader's role
disputeSummaryWindow.evidence=Evidence
@ -1746,7 +1748,7 @@ popup.headline.error=Erro
popup.doNotShowAgain=Não mostrar novamente
popup.reportError.log=Abrir arquivo de log
popup.reportError.gitHub=Relatar à lista de problemas do GitHub
popup.reportError={0}\n\nTo help us to improve the software please report the bug on our issue tracker on GitHub (https://github.com/bisq-network/bisq-desktop/issues).\nThe error message will be copied to the clipboard when you click a button below.\nIt will make debugging easier if you can attach the bisq.log file as well.
popup.reportError={0}\n\nTo help us to improve the software please report this bug by opening a new issue at https://github.com/bisq-network/bisq/issues.\nThe above error message will be copied to the clipboard when you click either of the buttons below.\nIt will make debugging easier if you include the bisq.log file by pressing "Open log file", saving a copy, and attaching it to your bug report.
popup.error.tryRestart=Por favor, reinicie o aplicativo e verifique sua conexão de Internet para ver se o problema foi resolvido.
popup.error.takeOfferRequestFailed=Um erro ocorreu quando alguém tentou aceitar uma de suas ofertas:\n{0}
@ -1805,6 +1807,9 @@ popup.attention.forTradeWithId=Atenção para a negociação com ID {0}
popup.roundedFiatValues.headline=Nova funcionalidade de privacidade: valores arredondados em moeda fiduciária
popup.roundedFiatValues.msg=Para aumentar a privacidade da sua transação, a quantia {0} foi arredondada.\n\nDependendo da versão do cliente, você irá pagar ou receber valores com decimais ou valores arredondados.\n\nAmbos os valores se enquadram no protocolo de negociação.\n\nPerceba também que os valores em BTC são modificados automaticamente para corresponder o mais próximo possível à quantia em fiat arredondada.
popup.info.multiplePaymentAccounts.headline=Multiple payment accounts available
popup.info.multiplePaymentAccounts.msg=You have multiple payment accounts available for this offer. Please make sure you've picked the right one.
####################################################################
# Notifications
@ -1817,7 +1822,7 @@ notification.trade.accepted=Sua oferta foi aceita por um {0} BTC.
notification.trade.confirmed=Sua negociação tem ao menos uma confirmação da blockchain.\nVocê pode iniciar o pagamento agora.
notification.trade.paymentStarted=O comprador BTC iniciou o pagamento
notification.trade.selectTrade=Selecionar negociação
notification.trade.peerOpenedDispute=Seu parceiro de negociação
notification.trade.peerOpenedDispute=Seu parceiro de negociação abriu um {0}.
notification.trade.disputeClosed=A {0} foi fechada.
notification.walletUpdate.headline=Update da carteira de negociação
notification.walletUpdate.msg=Sua carteira Bisq tem saldo suficiente.\nQuantia: {0}
@ -2085,7 +2090,7 @@ payment.clearXchange.info=Please be sure that you fulfill the requirements for t
payment.moneyGram.info=When using MoneyGram the BTC buyer has to send the Authorisation number and a photo of the receipt by email to the BTC seller. The receipt must clearly show the seller's full name, country, state and the amount. The buyer will get displayed the seller's email in the trade process.
payment.westernUnion.info=When using Western Union the BTC buyer has to send the MTCN (tracking number) and a photo of the receipt by email to the BTC seller. The receipt must clearly show the seller's full name, city, country and the amount. The buyer will get displayed the seller's email in the trade process.
payment.halCash.info=When using HalCash the BTC buyer need to send the BTC seller the HalCash code via a text message from the mobile phone.\n\nPlease make sure to not exceed the maximum amount your bank allows you to send with HalCash. The min. amount per withdrawal is 10 EUR and the max. amount is 600 EUR. For repeated withdrawals it is 3000 EUR per receiver per day and 6000 EUR per receiver per month. Please cross check those limits with your bank to be sure they use the same limits as stated here.\n\nThe withdrawal amount must be a multiple of 10 EUR as you cannot withdraw other amounts from an ATM. The UI in the create-offer and take-offer screen will adjust the BTC amount so that the EUR amount is correct. You cannot use market based price as the EUR amount would be changing with changing prices.\n\nIn case of a dispute the BTC buyer need to provide the proof that he sent the EUR.
payment.halCash.info=When using HalCash the BTC buyer needs to send the BTC seller the HalCash code via a text message from their mobile phone.\n\nPlease make sure to not exceed the maximum amount your bank allows you to send with HalCash. The min. amount per withdrawal is 10 EUR and the max. amount is 600 EUR. For repeated withdrawals it is 3000 EUR per receiver per day and 6000 EUR per receiver per month. Please cross check those limits with your bank to be sure they use the same limits as stated here.\n\nThe withdrawal amount must be a multiple of 10 EUR as you cannot withdraw other amounts from an ATM. The UI in the create-offer and take-offer screen will adjust the BTC amount so that the EUR amount is correct. You cannot use market based price as the EUR amount would be changing with changing prices.\n\nIn case of a dispute the BTC buyer needs to provide the proof that they sent the EUR.
payment.limits.info=Por favor, esteja ciente de que todas as transferências bancárias possuem um certo risco de serem estornadas.\n\nPara reduzir esse risco, o Bisq definite limites por transação, que são baseados em dois fatores:\n\n1. O nível estimado de risco de estorno para o método de pagamento utilizado\n2. A idade da sua conta para aquele método de pagamento\n\nA conta que você está criando agora é considerada nova, e portanto tem uma idade de zero. À medida que a idade da sua conta for aumentando, os seus limites também irão aumentar:\n\n● Durante o 1º mês, o seu limite por negociação será de {0}\n● Durante o 2º mês, o seu limite por negociação será de {1}\n● Após o 2º mês, o seu limite por negociação será de {2}\n\nNote que esses limites são para cada negociação. Não existem limites no número total de negociações que você pode realizar.
payment.cashDeposit.info=Certifique-se de que o seu banco permite a realização de depósitos em espécie na conta de terceiros.
@ -2098,7 +2103,7 @@ payment.f2f.optionalExtra=Informações adicionais opcionais
payment.f2f.extra=Informações adicionais
payment.f2f.extra.prompt=The maker can define 'terms and conditions' or add a public contact information. It will be displayed with the offer.
payment.f2f.info='Face to Face' trades have different rules and come with different risks than online transactions.\n\nThe main differences are:\n● The trading peers need to exchange information about the meeting location and time by using their provided contact details.\n● The trading peers need to bring their laptops and do the confirmation of 'payment sent' and 'payment received' at the meeting place.\n● If a maker has special 'terms and conditions' he needs to state those in the 'Addition information' text field in the account.\n● By taking an offer the taker agrees to the maker's stated 'terms and conditions'.\n● In case of a dispute the arbitrator cannot help much as it is usually hard to get tamper proof evidence of what happened at the meeting. In such cases the BTC funds might get locked indefinitely or until the trading peers come to an agreement.\n\nTo be sure you fully understand the differences with 'Face to Face' trades please read the instructions and recommendations at: 'https://docs.bisq.network/trading-rules.html#f2f-trading'
payment.f2f.info='Face to Face' trades have different rules and come with different risks than online transactions.\n\nThe main differences are:\n● The trading peers need to exchange information about the meeting location and time by using their provided contact details.\n● The trading peers need to bring their laptops and do the confirmation of 'payment sent' and 'payment received' at the meeting place.\n● If a maker has special 'terms and conditions' they must state those in the 'Additional information' text field in the account.\n● By taking an offer the taker agrees to the maker's stated 'terms and conditions'.\n● In case of a dispute the arbitrator cannot help much as it is usually hard to get tamper proof evidence of what happened at the meeting. In such cases the BTC funds might get locked indefinitely or until the trading peers come to an agreement.\n\nTo be sure you fully understand the differences with 'Face to Face' trades please read the instructions and recommendations at: 'https://docs.bisq.network/trading-rules.html#f2f-trading'
payment.f2f.info.openURL=Abrir site
payment.f2f.offerbook.tooltip.countryAndCity=Estado e cidade: {0} / {1}
payment.f2f.offerbook.tooltip.extra=Informações adicionais: {0}

27
core/src/main/resources/i18n/displayStrings_ro.properties
View file

@ -299,6 +299,8 @@ market.trades.tooltip.candle.date=Data:
offerbook.createOffer=Creează oferta:
offerbook.takeOffer=Acceptă oferta:
offerbook.takeOfferToBuy=Take offer to buy {0}
offerbook.takeOfferToSell=Take offer to sell {0}
offerbook.trader=Comerciant
offerbook.offerersBankId=Codul băncii ofertantului: {0}
offerbook.offerersBankName=Numele băncii ofertantului: {0}
@ -560,12 +562,12 @@ portfolio.pending.step3_buyer.warn.part1b=la furnizorul tău de plăți (ex: ban
portfolio.pending.step3_buyer.warn.part2=Vânzătorul de BTC încă nu ți-a confirmat plata!\nVerifică {0} dacă plata a fost executată cu succes.\nDacă vânzătorul de BTC nu confirmă primirea plății până la data de {1} tranzacția va fi investigată de arbitru.
portfolio.pending.step3_buyer.openForDispute=Vânzătorul de BTC înca nu ți-a confirmat plata!\nPerioada maximă de timp pentru tranzacționare a expirat.\nPoți aștepta mai mult astfel acordând mai mult timp partenerului de tranzacționare sau poți contacta arbitrul în vederea deschiderii unei dispute.
# suppress inspection "TrailingSpacesInProperty"
portfolio.pending.step3_seller.part=Partenerul tău de tranzacționare a confirmat că a inițiat plata {0}.\n\n
portfolio.pending.step3_seller.part=Your trading partner has confirmed that they have initiated the {0} payment.\n\n
portfolio.pending.step3_seller.altcoin.explorer=on your favorite {0} blockchain explorer
portfolio.pending.step3_seller.altcoin.wallet=at your {0} wallet
portfolio.pending.step3_seller.altcoin={0}Please check {1} if the transaction to your receiving address\n{2}\nhas already sufficient blockchain confirmations.\nThe payment amount has to be {3}\n\nYou can copy & paste your {4} address from the main screen after closing that popup.
portfolio.pending.step3_seller.postal={0}Verifică dacă ai primit {1} prin \"Ordin de plată poștală SUA\" de la cumpărătorul BTC.\n\nCodul tranzacției (\"motivul plății\") este: \"{2}\"
portfolio.pending.step3_seller.bank=Your trading partner has confirmed that he initiated the {0} payment.\n\nPlease go to your online banking web page and check if you have received {1} from the BTC buyer.\n\nThe trade ID (\"reason for payment\" text) of the transaction is: \"{2}\"\n\n
portfolio.pending.step3_seller.bank=Your trading partner has confirmed that they have initiated the {0} payment.\n\nPlease go to your online banking web page and check if you have received {1} from the BTC buyer.\n\nThe trade ID (\"reason for payment\" text) of the transaction is: \"{2}\"\n\n
portfolio.pending.step3_seller.cash=Because the payment is done via Cash Deposit the BTC buyer has to write \"NO REFUND\" on the paper receipt, tear it in 2 parts and send you a photo by email.\n\nTo avoid chargeback risk, only confirm if you received the email and if you are sure the paper receipt is valid.\nIf you are not sure, {0}
portfolio.pending.step3_seller.moneyGram=The buyer has to send you the Authorisation number and a photo of the receipt by email.\nThe receipt must clearly show your full name, country, state and the amount. Please check your email if you received the Authorisation number.\n\nAfter closing that popup you will see the BTC buyer's name and address for picking up the money from MoneyGram.\n\nOnly confirm receipt after you have successfully picked up the money!
portfolio.pending.step3_seller.westernUnion=Cumpărătorul trebuie să îți trimită numărul MTCN (numărul de urmărire) și o fotografie a chitanței prin e-mail.\nPe chitanță trebuie să apară în mod clar numele tău complet, orașul, țara și suma. Verifică-ți adresa de e-mail dacă primești MTCN-ul.\n\nDupă închiderea acestei ferestre vei vedea numele și adresa cumpărătorului de BTC pentru a ridica banii prin Western Union.\n\nConfirmă primirea numai după ce ai ridicat banii!
@ -926,10 +928,10 @@ account.arbitratorSelection.minOne=Trebuie să ai ales cel puțin un arbitru.
account.altcoin.yourAltcoinAccounts=Your altcoin accounts
account.altcoin.popup.wallet.msg=Please be sure that you follow the requirements for the usage of {0} wallets as described on the {1} web page.\nUsing wallets from centralized exchanges where (a) you don''t control your keys or (b) which don''t use compatible wallet software is risky: it can lead to loss of the traded funds!\nThe arbitrator is not a {2} specialist and cannot help in such cases.
account.altcoin.popup.wallet.confirm=Înțeleg și confirm că știu ce portofel trebuie să folosesc.
account.altcoin.popup.xmr.msg=If you want to trade XMR on Bisq please be sure you understand and fulfill the following requirements:\n\nFor sending XMR you need to use either the official Monero GUI wallet or Monero CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nmonero-wallet-cli (use the command get_tx_key)\nmonero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nIn addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\nmonero-wallet-cli : using command (check_tx_key).\nmonero-wallet-gui : on the Advanced > Prove/Check page.\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the 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\nIf you cannot provide the above data or if you used an incompatible wallet it would result in losing the dispute case. The XMR sender is responsible to be able to verify the XMR 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 (https://www.getmonero.org/resources/user-guides/prove-payment.html) or the Monero forum (https://forum.getmonero.org) to find more information.
account.altcoin.popup.blur.msg=If you want to trade BLUR on Bisq please be sure 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 arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nIf you cannot provide the required information to the arbitrator, you will lose the dispute. In all cases of dispute, the BLUR sender bears 100% of the burden of responsiblity in verifying transactions to an arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW).
account.altcoin.popup.ccx.msg=If you want to trade CCX on Bisq please be sure you understand the following requirements:\n\nTo send CCX you must use an official Conceal wallet, either CLI or GUI. After sending a transfer payment, the wallets\ndisplay the transaction secret key. You must save it along with the transaction hash (ID) and the recipient's public\naddress in case arbitration is necessary. In such a case, you must give all three to the arbitrator, who will then\nverify the CCX transfer using the Conceal Transaction Viewer (https://explorer.conceal.network/txviewer).\nBecause Conceal is a privacy coin, block explorers cannot verify transfers.\n\nIf you cannot provide the required data to the arbitrator, you will lose the dispute case.\nIf you do not save the transaction secret key immediately after transferring CCX, it cannot be recovered later.\nIf you do not understand these requirements, seek help at the Conceal discord (http://discord.conceal.network).
account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides a transaction is not verifyable on the public blockchain. If required you can prove your payment thru use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at \ (http://drgl.info/#check_txn).\n\nIf you cannot provide the above data or if you used an incompatible wallet it would result in losing the dispute case. The Dragonglass sender is responsible to be able to verify the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help.
account.altcoin.popup.xmr.msg=Trading XMR on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending XMR, you need to use either the official Monero GUI wallet or Monero CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nmonero-wallet-cli (use the command get_tx_key)\nmonero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nIn addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\nmonero-wallet-cli : using command (check_tx_key).\nmonero-wallet-gui : on the Advanced > Prove/Check page.\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The XMR sender is responsible for providing verification of the XMR transfer to the arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) or the Monero forum (https://forum.getmonero.org) to find more information.
account.altcoin.popup.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 arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The 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 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 arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW).
account.altcoin.popup.ccx.msg=Trading CCX on Bisq requires that you understand the following requirements:\n\nTo send CCX you must use an official Conceal wallet, either CLI or GUI. After sending a transfer payment, the wallets\ndisplay the transaction secret key. You must save it along with the transaction hash (ID) and the recipient's public\naddress in case arbitration is necessary. In such a case, you must give all three to the arbitrator, who will then\nverify the CCX transfer using the Conceal Transaction Viewer (https://explorer.conceal.network/txviewer).\nBecause Conceal is a privacy coin, block explorers cannot verify transfers.\n\nFailure to provide the required data to the arbitrator will result in losing the dispute case.\nIf you do not save the transaction secret key immediately after transferring CCX, it cannot be recovered later.\nIf you do not understand these requirements, seek help at the Conceal discord (http://discord.conceal.network).
account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides, a transaction is not verifiable on the public blockchain. If required, you can prove your payment through the use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at (http://drgl.info/#check_txn).\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The Dragonglass sender is responsible for providing verification of the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help.
account.altcoin.popup.ZEC.msg=Atunci când folosești {0}, poți utiliza doar adresele transparente (începând cu t) nu adresele z (private), deoarece arbitrul nu va putea verifica tranzacția cu adrese z.
account.altcoin.popup.XZC.msg=Când folosești {0}, poți folosi numai adresele transparente (ce pot fi urmărite), nu adresele indetectabile, deoarece arbitrul nu va putea verifica tranzacția executată cu adrese ce nu pot fi citite de către un explorator de bloc.
account.altcoin.popup.bch=Bitcoin Cash și Bitcoin Clashic suferă de protecție împotriva reluării. Dacă folosești aceste monede, asigură-te că ai luat măsurile necesare de precauție și înțelegi toate implicațiile. Poți suferi pierderi prin trimiterea unei monezi și neintenționat să trimiți aceeași monedă pe celălalt blockchain. Deoarece acele "monede airdrop" au aceeași istorie cu blockchainul Bitcoin există și riscuri de securitate cât și un risc considerabil în pierderea confidențialității.\n\nTe invităm să citești mai multe despre acest subiect pe forumul Bisq: https://forum.bisq.io/t/airdrop-coins-information-thread-bch-btg-bchc
@ -1306,7 +1308,7 @@ dao.burnBsq.assets.lookBackPeriod=Verification period
dao.burnBsq.assets.trialFee=Fee for trial period
dao.burnBsq.assets.totalFee=Total fees paid
dao.burnBsq.assets.days={0} days
dao.burnBsq.assets.toFewDays=The asset fee is too low. The min. amount of days for the trial perios is {0}.
dao.burnBsq.assets.toFewDays=The asset fee is too low. The min. amount of days for the trial period is {0}.
# suppress inspection "UnusedProperty"
dao.assetState.UNDEFINED=Nedefinit
@ -1584,7 +1586,7 @@ displayUpdateDownloadWindow.verify.failed=Verficare eșuată.\nTe rugăm descarc
displayUpdateDownloadWindow.success=Noua versiune a fost descărcată cu succes iar semnătura a fost verificată.\n\nDeschide directorul de descărcare, închide aplicația și instalează noua versiune.
displayUpdateDownloadWindow.download.openDir=Deschide directorul descărcărilor
disputeRezumatWindow.title=Rezumat
disputeSummaryWindow.title=Rezumat
disputeSummaryWindow.openDate=Ticket opening date
disputeSummaryWindow.role=Trader's role
disputeSummaryWindow.evidence=Evidence
@ -1746,7 +1748,7 @@ popup.headline.error=Eroare
popup.doNotShowAgain=Nu arăta din nou
popup.reportError.log=Deschide fișierul jurnal
popup.reportError.gitHub=Reclamare către Github
popup.reportError={0}\n\nTo help us to improve the software please report the bug on our issue tracker on GitHub (https://github.com/bisq-network/bisq-desktop/issues).\nThe error message will be copied to the clipboard when you click a button below.\nIt will make debugging easier if you can attach the bisq.log file as well.
popup.reportError={0}\n\nTo help us to improve the software please report this bug by opening a new issue at https://github.com/bisq-network/bisq/issues.\nThe above error message will be copied to the clipboard when you click either of the buttons below.\nIt will make debugging easier if you include the bisq.log file by pressing "Open log file", saving a copy, and attaching it to your bug report.
popup.error.tryRestart=Încearcă să repornești aplicația și să verifici conexiunea la rețea pentru a vedea dacă poți remedia astfel problema.
popup.error.takeOfferRequestFailed=A intervenit o eroare când cineva a încercat să îți preia una din oferte:\n{0}
@ -1805,6 +1807,9 @@ popup.attention.forTradeWithId=Atenție solicitată pentru tranzacția cu codul
popup.roundedFiatValues.headline=New privacy feature: Rounded fiat values
popup.roundedFiatValues.msg=To increase privacy of your trade the {0} amount was rounded.\n\nDepending on the client version you''ll pay or receive either values with decimals or rounded ones.\n\nBoth values do comply from now on with the trade protocol.\n\nAlso be aware that BTC values are changed automatically to match the rounded fiat amount as close as possible.
popup.info.multiplePaymentAccounts.headline=Multiple payment accounts available
popup.info.multiplePaymentAccounts.msg=You have multiple payment accounts available for this offer. Please make sure you've picked the right one.
####################################################################
# Notifications
@ -2085,7 +2090,7 @@ payment.clearXchange.info=Please be sure that you fulfill the requirements for t
payment.moneyGram.info=When using MoneyGram the BTC buyer has to send the Authorisation number and a photo of the receipt by email to the BTC seller. The receipt must clearly show the seller's full name, country, state and the amount. The buyer will get displayed the seller's email in the trade process.
payment.westernUnion.info=When using Western Union the BTC buyer has to send the MTCN (tracking number) and a photo of the receipt by email to the BTC seller. The receipt must clearly show the seller's full name, city, country and the amount. The buyer will get displayed the seller's email in the trade process.
payment.halCash.info=When using HalCash the BTC buyer need to send the BTC seller the HalCash code via a text message from the mobile phone.\n\nPlease make sure to not exceed the maximum amount your bank allows you to send with HalCash. The min. amount per withdrawal is 10 EUR and the max. amount is 600 EUR. For repeated withdrawals it is 3000 EUR per receiver per day and 6000 EUR per receiver per month. Please cross check those limits with your bank to be sure they use the same limits as stated here.\n\nThe withdrawal amount must be a multiple of 10 EUR as you cannot withdraw other amounts from an ATM. The UI in the create-offer and take-offer screen will adjust the BTC amount so that the EUR amount is correct. You cannot use market based price as the EUR amount would be changing with changing prices.\n\nIn case of a dispute the BTC buyer need to provide the proof that he sent the EUR.
payment.halCash.info=When using HalCash the BTC buyer needs to send the BTC seller the HalCash code via a text message from their mobile phone.\n\nPlease make sure to not exceed the maximum amount your bank allows you to send with HalCash. The min. amount per withdrawal is 10 EUR and the max. amount is 600 EUR. For repeated withdrawals it is 3000 EUR per receiver per day and 6000 EUR per receiver per month. Please cross check those limits with your bank to be sure they use the same limits as stated here.\n\nThe withdrawal amount must be a multiple of 10 EUR as you cannot withdraw other amounts from an ATM. The UI in the create-offer and take-offer screen will adjust the BTC amount so that the EUR amount is correct. You cannot use market based price as the EUR amount would be changing with changing prices.\n\nIn case of a dispute the BTC buyer needs to provide the proof that they sent the EUR.
payment.limits.info=Rețineți că toate transferurile bancare au un anumit risc de rambursare.\n\nPentru a diminua acest risc, Bisq stabilește limite de tranzacționare bazate pe doi factori:\n\n1. Nivelul estimat al riscului de rambursare pentru metoda de plată utilizată\n2. Vechimea contului tău pentru metodă de plată aleasă\n\nContul pe care îl creezi acum este nou iar vechimea acestuia este zero. Pe măsură ce contul tău avansează în vechime pe parcursul unei perioade de două luni, limitele per-tranzacție vor crește împreună cu vechimea:\n\n● În prima lună, limita ta per-tranzacție va fi {0}\n● În cea de-a doua lună, limita ta per-tranzacție va fi {1}\n● După cea de-a doua lună, limita ta per-tranzacție va fi {2}\n\nReține că nu sunt impuse limite privind numărul total de ocazii în care poți tranzacționa.
payment.cashDeposit.info=Please confirm your bank allows you to send cash deposits into other peoples' accounts. For example, Bank of America and Wells Fargo no longer allow such deposits.
@ -2098,7 +2103,7 @@ payment.f2f.optionalExtra=Optional additional information
payment.f2f.extra=Additional information
payment.f2f.extra.prompt=The maker can define 'terms and conditions' or add a public contact information. It will be displayed with the offer.
payment.f2f.info='Face to Face' trades have different rules and come with different risks than online transactions.\n\nThe main differences are:\n● The trading peers need to exchange information about the meeting location and time by using their provided contact details.\n● The trading peers need to bring their laptops and do the confirmation of 'payment sent' and 'payment received' at the meeting place.\n● If a maker has special 'terms and conditions' he needs to state those in the 'Addition information' text field in the account.\n● By taking an offer the taker agrees to the maker's stated 'terms and conditions'.\n● In case of a dispute the arbitrator cannot help much as it is usually hard to get tamper proof evidence of what happened at the meeting. In such cases the BTC funds might get locked indefinitely or until the trading peers come to an agreement.\n\nTo be sure you fully understand the differences with 'Face to Face' trades please read the instructions and recommendations at: 'https://docs.bisq.network/trading-rules.html#f2f-trading'
payment.f2f.info='Face to Face' trades have different rules and come with different risks than online transactions.\n\nThe main differences are:\n● The trading peers need to exchange information about the meeting location and time by using their provided contact details.\n● The trading peers need to bring their laptops and do the confirmation of 'payment sent' and 'payment received' at the meeting place.\n● If a maker has special 'terms and conditions' they must state those in the 'Additional information' text field in the account.\n● By taking an offer the taker agrees to the maker's stated 'terms and conditions'.\n● In case of a dispute the arbitrator cannot help much as it is usually hard to get tamper proof evidence of what happened at the meeting. In such cases the BTC funds might get locked indefinitely or until the trading peers come to an agreement.\n\nTo be sure you fully understand the differences with 'Face to Face' trades please read the instructions and recommendations at: 'https://docs.bisq.network/trading-rules.html#f2f-trading'
payment.f2f.info.openURL=Open web page
payment.f2f.offerbook.tooltip.countryAndCity=County and city: {0} / {1}
payment.f2f.offerbook.tooltip.extra=Additional information: {0}

163
core/src/main/resources/i18n/displayStrings_ru.properties
View file

@ -299,9 +299,11 @@ market.trades.tooltip.candle.date=Дата:
offerbook.createOffer=Создать предложение
offerbook.takeOffer=Принять предложение
offerbook.takeOfferToBuy=Take offer to buy {0}
offerbook.takeOfferToSell=Take offer to sell {0}
offerbook.trader=Трейдер
offerbook.offerersBankId=Идентификатор(BIC/SWIFT) банка создателя предложения: {0}
offerbook.offerersBankName=Название банка создателя предложения: {0}
offerbook.offerersBankId=Идент. банка (BIC/SWIFT) создателя: {0}
offerbook.offerersBankName=Название банка создателя: {0}
offerbook.offerersBankSeat=Местоположение банка создателя предложения: {0}
offerbook.offerersAcceptedBankSeatsEuro=Признанные страны банков (получателя): Все страны Еврозоны
offerbook.offerersAcceptedBankSeats=Признанные страны банков (получателя):\n {0}
@ -357,7 +359,7 @@ createOffer.amount.prompt=Введите сумму в ВТС
createOffer.price.prompt=Введите курс
createOffer.volume.prompt=Введите сумму в {0}
createOffer.amountPriceBox.amountDescription=Количество BTC {0}
createOffer.amountPriceBox.buy.volumeDescription=Сумма расхода в {0}
createOffer.amountPriceBox.buy.volumeDescription=Сумма расхода в {0}
createOffer.amountPriceBox.sell.volumeDescription=Сумма поступления в {0}
createOffer.amountPriceBox.minAmountDescription=Мин. количество ВТС
createOffer.securityDeposit.prompt=Залоговый депозит в ВТС
@ -376,7 +378,7 @@ createOffer.info.buyBelowMarketPrice=Вы всегда заплатите {0}%
createOffer.warning.sellBelowMarketPrice=Вы всегда получите {0}% меньше текущей рыночной цены, так как курс вашего предложения будет постоянно обновляться.
createOffer.warning.buyAboveMarketPrice=Вы всегда заплатите {0}% больше текущей рыночной цены, так как курс вашего предложения будет постоянно обновляться.
createOffer.tradeFee.descriptionBTCOnly=Торговый сбор
createOffer.tradeFee.descriptionBSQEnabled=Выбрать валюту сбора
createOffer.tradeFee.descriptionBSQEnabled=Выбрать валюту сбора за сделку
createOffer.tradeFee.fiatAndPercent=≈ {0} / {1} от суммы сделки
# new entries
@ -385,7 +387,7 @@ createOffer.alreadyFunded=Вы уже обеспечили это предлож
createOffer.createOfferFundWalletInfo.headline=Обеспечить своё предложение
# suppress inspection "TrailingSpacesInProperty"
createOffer.createOfferFundWalletInfo.tradeAmount=- Сумма сделки: {0} \n
createOffer.createOfferFundWalletInfo.msg=Вы должны внести {0} для обеспечения этого предложения.\n\nЭти средства выделяются в Вашем локальном кошельке, и будут заперты в депозитном адресе multisig, когда кто-то примет Ваше предложение.\n\nСумма состоит из:\n{1}- Вашего залогового депозита: {2}\n- Торгового сбора: {3}\n- Общей комиссии майнера: {4}\n\n\nВы можете выбрать один из двух вариантов обеспечения сделки:\n - Использовать свой Bisq кошелёк (удобо, но связь между сделками может быть вычислена посторонними) ИЛИ\n - Перевод с внешнего кошелька (потенциально более анонимно)\n\nВы увидите все варианты обеспечения и подробности после закрытия этого окна.
createOffer.createOfferFundWalletInfo.msg=Вы должны внести {0} для обеспечения этого предложения.\n\nЭти средства зарезервированы в Вашем локальном кошельке, и будут заперты в депозитном адресе multisig, когда кто-то примет Ваше предложение.\n\nСумма состоит из:\n{1}- Вашего залогового депозита: {2}\n- Торгового сбора: {3}\n- Общей комиссии майнера: {4}\n\nВы можете выбрать один из двух вариантов финасирования сделки:\n - Использовать свой Bisq кошелёк (удобно, но связь между сделками может быть вычислена посторонними) ИЛИ\n - Перевести из внешнего кошелька (потенциально более анонимно)\n\nВы увидите все варианты обеспечения и подробности после закрытия этого окна.
# only first part "An error occurred when placing the offer:" has been used before. We added now the rest (need update in existing translations!)
createOffer.amountPriceBox.error.message=Сбой создания предложения:\n\n{0}\n\nВаши средства остались в кошельке.\nПросьба перезагрузить приложение и проверить связь с интернет.
@ -400,7 +402,7 @@ createOffer.resetToDefault=Нет, сбросить до значения по
createOffer.useLowerValue=Да, использовать моё низшее значение
createOffer.priceOutSideOfDeviation=Введенный курс превышает максимальное отклонение от рыночного.\nМаксимально дозволенное отклонение {0} и регулируется в настройках.
createOffer.changePrice=Изменить курс
createOffer.tac=Опубликовав предложение, я согласен торговать с любым трейдером, совместимым по условиям обозначенным на экране.
createOffer.tac=Опубликовав предложение, я согласен торговать с любым трейдером, совместимым по условиям обозначенным на экране.
createOffer.currencyForFee=Оплата сделки
createOffer.setDeposit=Установить залоговый депозит покупателя
@ -437,7 +439,7 @@ takeOffer.alreadyFunded.movedFunds=Вы уже обеспечили это пр
takeOffer.takeOfferFundWalletInfo.headline=Обеспечить Вашу сделку
# suppress inspection "TrailingSpacesInProperty"
takeOffer.takeOfferFundWalletInfo.tradeAmount=- Сумма сделки: {0} \n
takeOffer.takeOfferFundWalletInfo.msg=Для принятия этого предложения необходимо внести депозит {0}.\n\nДепозит является суммой:\n{1}\n- Вашего залогового депозита: {2}\n- Торгового сбора: {3}\n- Общей комиссии майнера: {4}\n\nВам можно выбрать из двух вариантов финансирования сделки:\n- Использовать свой Bisq кошелёк (удобно, но связь между сделками может быть вычислена посторонними) ИЛИ\n- Перевод из внешнего кошелька (потенциально более анонимно)\n\nВы увидите все варианты финансирования и подробности после закрытия этого окна.
takeOffer.takeOfferFundWalletInfo.msg=Для принятия этого предложения необходимо внести депозит {0}.\n\nДепозит является суммой:\n{1}- Вашего залогового депозита: {2}\n- Торгового сбора: {3}\n- Общей комиссии майнера: {4}\n\nВам можно выбрать из двух вариантов финансирования сделки:\n- Использовать свой Bisq кошелёк (удобно, но связь между сделками может быть вычислена посторонними) ИЛИ\n- Перевести из внешнего кошелька (потенциально более анонимно)\n\nВы увидите все варианты финансирования и подробности после закрытия этого окна.
takeOffer.alreadyPaidInFunds=Если Вы уже внесли средства, их можно снять в разделе \"Средства/Отправить средства\".
takeOffer.paymentInfo=Информация о платеже
takeOffer.setAmountPrice=Задайте сумму
@ -527,7 +529,7 @@ portfolio.pending.step2_buyer.moneyGramMTCNInfo.msg=Вам необходимо
portfolio.pending.step2_buyer.westernUnionMTCNInfo.headline=Отправить MTCN и квитанцию
portfolio.pending.step2_buyer.westernUnionMTCNInfo.msg=Вам необходимо отправить по э-почте продавцу BTC MTCN (номер отслеживания) и фотографию квитанции.\nВ квитанции должно быть четко указано полное имя продавца, город, страна и сумма. Адрес э-почты продавца: {0}. \n\nВы отправили MTCN и контракт продавцу?
portfolio.pending.step2_buyer.halCashInfo.headline=Послать код HalCash
portfolio.pending.step2_buyer.halCashInfo.msg=Отклонение в процентах от рыночной цены (например, 2.50%, -0.50% и т. д.)
portfolio.pending.step2_buyer.halCashInfo.msg=Вам нужно отправить сообщение с кодом HalCash и идентификатором сделки ({0}) к торговцу BTC.\nНомер мобильного тел. торговца {1}\n\nВы отправили код торговцу?
portfolio.pending.step2_buyer.fasterPaymentsHolderNameInfo=Некоторые банки требуют имя получателя. Код сортировки Великобритании и номер счета достаточны для перевода Faster Payment, и имя получателя не проверяется ни одним из банков.
portfolio.pending.step2_buyer.confirmStart.headline=Подтвердите начало платежа
portfolio.pending.step2_buyer.confirmStart.msg=Вы начали {0} оплату Вашему контрагенту?
@ -535,7 +537,7 @@ portfolio.pending.step2_buyer.confirmStart.yes=Да, я начал оплату
portfolio.pending.step2_seller.waitPayment.headline=Ожидайте платеж
portfolio.pending.step2_seller.f2fInfo.headline=Контактная информация покупателя
portfolio.pending.step2_seller.waitPayment.msg=Поступило как минимум одно подтверждение депозита.\nВам необходимо ждать до тех пор когда покупатель BTC начнет оплату {0}.
portfolio.pending.step2_seller.waitPayment.msg=Поступило как минимум одно подтверждение транзакции депозита.\nВам необходимо ждать до тех пор когда покупатель BTC начнет оплату {0}.
portfolio.pending.step2_seller.warn=Покупатель BTC все еще не завершил оплату {0}.\nВам необходимо ждать начала оплаты.\nЕсли сделка не завершилась {1}, арбитр начнет расследование.
portfolio.pending.step2_seller.openForDispute=Покупатель BTC не приступил к оплате!\nМаксимальный срок сделки истёк.\nВы в праве подождать, и дать контрагенту больше времени, или связаться с арбитром и начать спор.
@ -562,11 +564,11 @@ portfolio.pending.step3_buyer.openForDispute=Продавец BTC не подт
# suppress inspection "TrailingSpacesInProperty"
portfolio.pending.step3_seller.part=Ваш контрагент подтвердил начало {0} оплаты.\n\n
portfolio.pending.step3_seller.altcoin.explorer=на Вашем любимом обозревателе блокцепи {0}
portfolio.pending.step3_seller.altcoin.wallet=в Вашем кошельке {0}
portfolio.pending.step3_seller.altcoin={0}Проверьте {1} получила ли транзакция на Ваш адрес\n{2}\nдостаточно подтверждений блокципи.\nНеобходимая сумма платежа {3}\n\n Вы можете скопировать и вставить свой адрес {4} из главного окна после закрытия этого окна.
portfolio.pending.step3_seller.altcoin.wallet=в Вашем кошельке {0}
portfolio.pending.step3_seller.altcoin={0}Проверьте {1} получила ли транзакция на Ваш адрес\n{2}\nдостаточно подтверждений блокцепи.\nНеобходимая сумма платежа должна быть {3}\n\n Вы можете скопировать и вставить свой адрес {4} из главного окна после закрытия этого окна.
portfolio.pending.step3_seller.postal={0}Просьба проверить, получили ли Вы {1} \"Почтового чека США\" от покупателя BTC.\n\nИдентификатор сделки (\"Назначение платежа\" текст) транзакции: \"{2}\"
portfolio.pending.step3_seller.bank=Ваш контрагент подтвердил, что начат платеж {0}.\n\nПросьба зайти на веб-страницу Вашего интернет-банка и проверить, получили ли Вы {1} от покупателя BTC.\n\nИдентификатор сделки (\"причина платежа \" текст) транзакции: \"{2}\"\n\n
portfolio.pending.step3_seller.cash=Так как оплата осуществляется наличными на счёт, покупатель BTC должен написать \"НЕ ПОДЛЕЖИТ ВОЗВРАТУ\" на квитанции, разорвать на 2 части, и послать Вам фото квитанции по э-почте.\n\nЧтоб исключить возвратный платёж, подтверждайте его только получив это фото, и если Вы уверенны, что квитанция действительна.\nЕсли Вы не уверенны, {0}
portfolio.pending.step3_seller.bank=Ваш контрагент подтвердил, что начат платеж {0}.\n\nПросьба зайти на веб-страницу Вашего интернет-банка и проверить, получили ли Вы {1} от покупателя BTC.\n\nИдентификатор сделки (\"причина платежа\" текст) транзакции: \"{2}\"\n\n
portfolio.pending.step3_seller.cash=Так как оплата осуществляется наличными на счёт, покупатель BTC должен написать \"НЕ ПОДЛЕЖИТ ВОЗВРАТУ\" на квитанции, разорвать на 2 части, и послать Вам фото квитанции по э-почте.\n\nЧтобы избежать возвратный платёж, подтверждайте его только получив это фото, и если Вы уверены, что квитанция действительна.\nЕсли Вы не уверены, {0}
portfolio.pending.step3_seller.moneyGram=Покупатель обязан отправить Вам по электронной почте номер авторизации и фотографию квитанции.\nВ квитанции должно быть четко указано Ваше полное имя, страна, штат и сумма. Пожалуйста, проверьте свою электронную почту, и получение номера авторизации. \n\nПосле закрытия этого всплывающего окна Вы увидите имя и адрес покупателя BTC для получения денег от MoneyGram.\n\nПодтверждайте получение только после того как Вы успешно забрали деньги!
portfolio.pending.step3_seller.westernUnion=Покупатель обязан отправить Вам по электронной почте MTCN (номер отслеживания) и фотографию квитанции.\nВ квитанции должно быть четко указано Ваше полное имя, город, страна и сумма. Пожалуйста, проверьте свою электронную почту, и получение MTCN.\n\nПосле закрытия этого всплывающего окна Вы увидите имя и адрес покупателя BTC для получения денег от Western Union. \n\nПодтверждайте получение только после того как Вы успешно забрали деньги!
portfolio.pending.step3_seller.halCash=Покупатель должен отправить Вам код HalCash в текстовом сообщении. Кроме этого, Вы получите сообщение от HalCash с информацией, необходимой для снятия EUR в банкомате, поддерживающем HalCash.\n\nПосле того, как Вы забрали деньги из банкомата, просьба подтвердить здесь квитанцию об оплате!
@ -595,7 +597,7 @@ portfolio.pending.step3_seller.onPaymentReceived.fiat=Идентификатор
portfolio.pending.step3_seller.onPaymentReceived.name=Просьба, удостоверьтесь, что имя отправителя в Вашем банковском отчете соответствует имени Вашего контрагента в сделке.:\nИмя отправителя: {0}\n\nЕсли имя не соответствует указанному здесь, просьба не подтверждать, а открыть спор, нажав "alt + o\" или \"option + o\".\n\n
portfolio.pending.step3_seller.onPaymentReceived.note=Учтите, что как только Вы подтвердите получение оплаты, запертая сумма сделки будет отпущена покупателю BTC и залоговая сумма будет возвращена.
portfolio.pending.step3_seller.onPaymentReceived.confirm.headline=Подтвердите, что вы получили платеж
portfolio.pending.step3_seller.onPaymentReceived.confirm.yes=Да, я получил платёж
portfolio.pending.step3_seller.onPaymentReceived.confirm.yes=Да, я получил(а) платёж
portfolio.pending.step5_buyer.groupTitle=Итоги завершённой сделки
portfolio.pending.step5_buyer.tradeFee=Торговый сбор
@ -676,7 +678,7 @@ funds.deposit.generateAddress=Создать новый адрес
funds.deposit.selectUnused=Просьба выбрать неиспользованный адрес из таблицы выше, вместо создания нового.
funds.withdrawal.arbitrationFee=Комиссия арбитра
funds.withdrawal.inputs=Выбор ресурсов
funds.withdrawal.inputs=Выбор ресурсов
funds.withdrawal.useAllInputs=Использовать все доступные ресурсы
funds.withdrawal.useCustomInputs=Использовать выбранные ресурсы
funds.withdrawal.receiverAmount=Сумма получателя
@ -718,7 +720,7 @@ funds.tx.noFundsFromDispute=Без возмещения от спора
funds.tx.receivedFunds=Полученные средства
funds.tx.withdrawnFromWallet=Выведено из кошелька
funds.tx.noTxAvailable=Транзакции недоступны
funds.tx.revert=Возврат
funds.tx.revert=Возвратить
funds.tx.txSent=Транзакция успешно отправлена на новый адрес локального кошелька Bisq.
funds.tx.direction.self=Транзакция внутри кошелька
funds.tx.daoTxFee=Комиссия майнера за трансакцию DAO
@ -765,9 +767,9 @@ support.buyerOfferer=Покупатель ВТС/Создатель
support.sellerOfferer=Продавец ВТС/Создатель
support.buyerTaker=Покупатель ВТС/Получатель
support.sellerTaker=Продавец BTC/Получатель
support.backgroundInfo=Bisq is not a company, so it handles disputes differently.\n\nIf there are disputes in the trade process (e.g. one trader does not follow the trade protocol) the application will display an \"Open dispute\" button after the trade period is over for contacting the arbitrator.\n\nIf there is an issue with the application, the software will try to detect it and, if possible, display an \"Open support ticket\" button to contact the arbitrator who will forward the issue to the developers.\n\nIf you are having an issue and did not see the \"Open support ticket\" button, you can open a support ticket manually by selecting the trade causing issues under \"Portfolio/Open trades\" and hitting \"alt + o\" or \"option + o\". Please use this method only if you are sure that the software is not working as expected. If you have problems or questions, please review the FAQ on the bisq.network web page or post in the Bisq forum in the Support section.
support.backgroundInfo=Bisq не является компанией, и поэтому справляется со спорами по другому.\n\n Если в процессе торговли возникают споры (напр. трейдер не соблюдает торговый протокол) приложение покажет кнопку \"Открыть спор\" для обращения к арбитру после окончания торгового срока.\n\nВ случае неполадок с приложением, оно попытается их обнаружить, и если это возможно, покажет кнопку \"Открыть билет поддержки\" чтобы связаться с арбитром который передаст проблему разработчикам. \n\nЕсли у Вас возникли проблемы и не появилась кнопка \"Открыть билет поддержки\", откройте его вручную выбрав данную сделку в разделе \"Папка/Текущие сделки\" и нажав \"alt + o\" или \"option + o\". Просьба использовать это только если Вы уверены что приложение не работает как следует. Если у Вас возникли проблемы или вопросы, просьба пересмотреть Часто Задаваемые Вопросы на странице bisq.network или спросить на Bisq форуме в разделе поддержки.
support.initialInfo=Учтите основные правила процесса рассмотрения спора:\n1. Вы обязаны ответитть на запросы арбитра в течении 2 дней.\n2. Максимальный срок отведенный на спор 14 дней.\n3. Вы обязаны содействовать арбитру, и предоставлять запрашиваемую информацию по Вашему делу.\n4. Вы согласились с правилами указанными в wiki в соглашении пользователя, когда первый раз запускали приложение.\n\nПросьба прочесть детали процесса спора в нашем wiki:\nhttps://github.com/bisq-network/exchange/wiki/Arbitration-system
support.initialInfo=Учтите основные правила процесса рассмотрения спора:\n1. Вы обязаны ответитть на запросы арбитра в течении 2 дней.\n2. Максимальный срок отведенный на спор: 14 дней.\n3. Вы обязаны содействовать арбитру, и предоставлять запрашиваемую информацию по Вашему делу.\n4. Вы согласились с правилами указанными в wiki в соглашении пользователя, когда первый раз запускали приложение.\n\nПросьба прочесть детали процесса спора в нашем wiki:\nhttps://github.com/bisq-network/exchange/wiki/Arbitration-system
support.systemMsg=Системное сообщение: {0}
support.youOpenedTicket=Вы открыли запрос поддержки.
support.youOpenedDispute=Вы запросили начать спор.\n\n{0}
@ -790,7 +792,7 @@ setting.preferences.deviationToLarge=Значения выше 30 % не раз
setting.preferences.txFee=Комиссия за снятие средств (сатоши/байт)
setting.preferences.useCustomValue=Задать своё значение
setting.preferences.txFeeMin=Комиссия транзакции должна быть хотя бы {0} сатоши/байт
setting.preferences.txFeeTooLarge=Введённый параметр слишком высок (>5000 сатоши/байт). Комиссия транзакции обычно намного ниже.
setting.preferences.txFeeTooLarge=Введённый параметр слишком высок (>5000 сатоши/байт). Комиссия транзакции обычно намного ниже, в пределе 50-400 сатоши/байт.
setting.preferences.ignorePeers=Игнорировать трейдеров с onion-адресами (через запят.)
setting.preferences.refererId=Реферальный идентификатор
setting.preferences.refererId.prompt=Дополнительный реферальный идентификатор
@ -825,18 +827,18 @@ setting.preferences.dao.fullNodeInfo.cancel=Нет, останусь в режи
settings.net.btcHeader=Сеть Биткойн
settings.net.p2pHeader=Сеть Р2Р
settings.net.onionAddressLabel=Мой onion(Tor) адрес
settings.net.onionAddressLabel=Мой onion (Tor) адрес
settings.net.btcNodesLabel=Использовать особые узлы Bitcoin Core
settings.net.bitcoinPeersLabel=Подключенные пэры
settings.net.useTorForBtcJLabel=Использовать Tor для сети Биткойн
settings.net.bitcoinNodesLabel=Подключиться к узлам Bitcoin Core
settings.net.bitcoinNodesLabel=Узлы Bitcoin Core для подключения
settings.net.useProvidedNodesRadio=Использовать предоставленные узлы Bitcoin Core
settings.net.usePublicNodesRadio=Использовать общедоступную сеть Bitcoin
settings.net.useCustomNodesRadio=Использовать особые узлы Bitcoin Core
settings.net.warn.usePublicNodes=Если Вы используете общедоступную сеть Bitcoin, Вы подвергаетесь серьезной угрозе конфиденциальности, вызванной несовершенным дизайном и реализацией фильтра bloom, который используется в кошельках SPV, таких как BitcoinJ (который используется в Bisq). Любой самостоятельный узел, к которому Вы подключены, может вычислить, что все Ваши адреса кошельков принадлежат одному лицу.\n\nПросьба осведомиться о подробностях на: https://bisq.network/blog/privacy-in-bitsquare.\n\nИспользовать общедоступные узлы?
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.useCustomNodes.B2XWarning=Просьба убедиться, что Ваш Биткойн узел является доверенным Bitcoin Core узлом! \n\nПодключение к узлам не следующим правилам консенсуса Bitcoin Core может повредить Ваш кошелек и вызвать проблемы в процессе торговли.\n\nПользователи подключающиеся к узлам, нарушающим правила консенсуса, несут ответственность за любой причиненный ущерб. Вытекающие споры будут решаться в пользу контрагента. Никакая техническая поддержка не будет предоставлена пользователям, которые игнорируют это предупреждения и механизмы защиты!
settings.net.localhostBtcNodeInfo=(Справка: если Вы используете локальный узел Биткойн (localhost), Вы можете подключаться исключительно к нему.)
settings.net.p2PPeersLabel=Подключенные пэры
settings.net.onionAddressColumn=Onion/Tor адрес
@ -859,8 +861,8 @@ settings.net.peer=Пэр
settings.net.inbound=входящий
settings.net.outbound=выходящий
settings.net.reSyncSPVChainLabel=Синхронизировать цепь SPV заново
settings.net.reSyncSPVChainButton=Удалить файл SPV и синхронизировать повторно
settings.net.reSyncSPVSuccess=Файл цепи SPV удалится при перезагрузке. Необходимо перезапустить приложение.\n\nПосле перезагрузки, потребуется некоторое время для повторной синхронизации с сетью и Вы увидите все транзакции только после её завершения.\n\nПросьба повторить перезагрузку после завершения повторной синхронизации, поскольку иногда возникают несоответствия, ведущие к неверному балансу.
settings.net.reSyncSPVChainButton=Удалить файл SPV и синхронизировать повторно
settings.net.reSyncSPVSuccess=Файл цепи SPV удалится при перезагрузке. Необходимо перезапустить приложение сейчас.\n\nПосле перезагрузки, потребуется некоторое время для повторной синхронизации с сетью и Вы увидите все транзакции только после её завершения.\n\nПросьба повторить перезагрузку после завершения повторной синхронизации, поскольку иногда возникают несоответствия, ведущие к неверному балансу.
settings.net.reSyncSPVAfterRestart=Файл цепи SPV удален. Просьба потерпеть. Повторная синхронизации с сетью может занять некоторое время.
settings.net.reSyncSPVAfterRestartCompleted=Повторная синхронизация завершена. Просьба перезагрузить приложение.
settings.net.reSyncSPVFailed=Не удалось удалить файл цепи SPV.\nСбой: {0}
@ -892,7 +894,7 @@ setting.about.subsystems.val=Версия сети: {0}; Версия P2P соо
account.tab.arbitratorRegistration=Регистрация арбитра
account.tab.account=Счёт
account.info.headline=Добро пожаловать в Ваш Bisq Счёт
account.info.msg=Here you can add trading accounts for national currencies & altcoins, select arbitrators, and create a backup of your wallet & account data.\n\nA new Bitcoin wallet was created the first time you started Bisq.\n\nWe strongly recommend that you write down your Bitcoin wallet seed words (see tab on the top) and consider adding a password before funding. Bitcoin deposits and withdrawals are managed in the \"Funds\" section.\n\nPrivacy & security note: because Bisq is a decentralized exchange, all your data is kept on your computer. There are no servers, so we have no access to your personal info, your funds, or even your IP address. Data such as bank account numbers, altcoin & Bitcoin addresses, etc are only shared with your trading partner to fulfill trades you initiate (in case of a dispute the arbitrator will see the same data as your trading peer).
account.info.msg=Здесь можно добавить свои торговые счета для нац. валют и алткойнов, выбрать арбитров, создать резервные копии своего кошелька и данных счетов.\n\nНовый кошелёк Биткойн был создан, когда Вы впервые запустили Bisq.\nНастоятельно рекомендуем Вам записать кодовые слова кошелька (смотрите вкладку вверху) и добавить пароль до ввода средств. Ввод и вывод биткойнов проводят в разделе \"Средства\".\n\nО безопасности и конфиденциальности:\nТак как Bisq - децентрализованный обменник, Ваши данные хранятся только на Вашем компьютере. Серверов нет, и нам не доступы Ваши личные данные, средства и даже IP адрес. Данные, как номера банковских счетов, адреса электронных кошельков, итп, сообщаются только Вашему контрагенту для обеспечения Ваших сделок (в случае спора, арбитр увидит те же данные, что и контрагент).
account.menu.paymentAccount=Счета в нац. валюте
account.menu.altCoinsAccountView=Алткойн-счета
@ -926,10 +928,10 @@ account.arbitratorSelection.minOne=Необходимо выбрать хотя
account.altcoin.yourAltcoinAccounts=Ваши алткойн-счета
account.altcoin.popup.wallet.msg=Убедитесь, что соблюдаете требования пользования кошельками {0}, описанных на веб-странице {1}.\nИспользование кошельков централизованных обменников рискованно, где (а) Ваши ключи не под Вашим контролем, или (б) используют несовместимый кошелёк; может привести к потере Ваших торговых средств!\nАрбитр не является специалистом {2} и не может помочь в таких случаях.
account.altcoin.popup.wallet.confirm=Я понимаю и подтверждаю, что знаю какой кошелёк нужно использовать.
account.altcoin.popup.xmr.msg=Для обмена XMR на Bisq, просьба понять и следовать следующим правилам:\n\nДля отправления XMR необходимы кошельки официальный Monero GUI или Monero CLI с включённым флажком store-tx-info (в новейших версиях по умолчанию). Удостоверьтесь, что доступен ключ транзакций необходимый в случае спора.\nmonero-wallet-cli (используйте команду get_tx_key)\nmonero-wallet-gui (перейдите в раздел history и нажмите на кнопку (P) для подтверждения оплаты)\n\n В дополнение к инструменту проверки XMR (https://xmr.llcoins.net/checktx.html), верификация также может быть выполнена в кошельке.\nmonero-wallet-cli: используя команду (check_tx_key).\nmonero-wallet-gui: разделе Advanced > Prove/Check.\nОбычным исследователем блоков переводы не проверяются.\n\nЕсли возникнет спора, арбитру потребуются от Вас следующие данные:\n- Ключ транзакции\n- Хэш(hash) транзакции\n- Публичный адрес получателя\n\nЕсли Вы не предоставите эти данные, либо используете несоответствующие кошельки, Вы проиграете спор. Посылающий XMR ответственен перед арбитром за подтверждение перевода XMR в случае спора.\n\nИдентификатор оплаты не нужен - только нормальный публичный адрес.\nЕсли Вам не знаком этот процесс, посетите (https://www.getmonero.org/resources/user-guides/prove-payment.html) или осведомитесь на форуме Monero (https://forum.getmonero.org).
account.altcoin.popup.blur.msg=Если вы хотите торговать BLUR на Bisq, вам нужно понять и выполнить следующие требования:\n\nЧтобы послать BLUR, вы должны использовать кошелёк Blur Network CLI или кошелёк GUI.\n\nЕсли вы используете кошелёк CLI, хэш сделки (tx ID) будет показан после отправки перевoда. Вы должны сохранить эту информацию. Немедленно после отправки перевода, используйте команду 'get_tx_key' для получения секретного ключа сделки. Если вы не выполните этот акт, вы не сможете получить ключ позже.\n\nЕсли вы используете кошелёк Blur Network GUI, вы можете найти частный ключ и идентификацию (ID) сделки во вкладке "История". Немедленно после отправки, найдите интересуемую сделку. Нажмите на символ "?" в нижне-правом углу окна содержащего сделку. Вы должны сохранить эту информацию.\n\nВ случае необходимости арбитража, вы должны предоставить следующее арбитру: 1.) идентификацию (ID) сделки, 2.) частный ключ сделки, и 3.) адрес получателя. Арбитр затем проверит перевод BLUR пользуясь Просмотрщиком сделок Blur или Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nЕсли вы не сможете предоставить требованную информацию арбитру, вы проиграете спор. Во всех случаях спора, отправитель несёт 100% ответственности за подтверждение сделок арбитру.\n\nЕсли вы не понимаете эти требования, не торгуйте на Bisq. Сначала, ищите помощь в Споре Сети Blur или Blur Network Discord (https://discord.gg/dMWaqVW).
account.altcoin.popup.ccx.msg=Если Вы хотите торговать CCX на Bisq, просьба убедиться, что Вы понимаете следующие требования:\n\nДля отправки ccx вы должны использовать официальный кошелек - либо CLI, либо GUI. После отправки перевода, кошельки\nпоказывают секретный ключ транзакции. Вы должны сохранить его вместе с хэшем транзакции (ID) и общедоступным\nадресом получателя на случай возникновения спора. В таком случае Вы должны предоставить все три арбитру,\nдля проверки перевода CCX с помощью Обозревателя Скрытых Транзакций (https://explorer.скрывать.network/txviewer).\nТак как Conceal монета конфиденциальности, блок обозреватели не могут проверить переводы.\n\nЕсли Вы не сможете предоставить необходимые данные арбитру, Вы проиграете спор.\nЕсли Вы не сохраните секретный ключ транзакции сразу после передачи CCX, его нельзя будет восстановить позже.\nЕсли Вы не понимаете этих требований, обратитесь за помощью в Conceal discord (http://discord.conceal.network).
account.altcoin.popup.drgl.msg=\nЧтобы торговать Dragonglass на Bisq, вы должны понять и выполнить следующие треобования:\n\nТак как Dragonglass предоставляет конфиденциальность, сделку невозможно подтвердить в общественном блокчейне. Вам необходимо доказать вашу оплату пользуясь вашим частным ключом TXN (TXN-Private-Key).\nЧастный ключ TXN - это одноразовый ключ который автоматически создан при каждой сделке и только доступен изнутри вашего кошелька DRGL.\nИли через GUI (графический интерфейс пользователя) кошелька DRGL (внутри диалога деталей сделок) или через Dragonglass CLI simplewallet (пользуясь командой "get_tx_key").\n\nДля обоих НЕОБХОДИМЫ версия DRGL "Oathkeeper" и новее.\n\nВ случае спора, вы должны предоставить следующую информацию арбитру: \n- Частный ключ TXN\n- Хэш сделки\n- Публичный адрес получателя\n\nПодтверждение оплаты может быть выполнено используя приведённые выше данные в качестве входных данных в (http://drgl.info/#check_txn). \n\nЕсли вы не можете предоставить приведённые выше данные или вы использовали несовместимый кошелёк, это приведёт к потере спора. Отправитель Dragonglass имеет ответственность за подтвердение перевода DRGL арбитру в случае спора. Использование PaymentID не требуется.\n\nЕсли вы не уверены в какой-либо части этого процесса, посетите Dragonglass о споре (http://discord.drgl.info) для услуг.
account.altcoin.popup.xmr.msg=Для торговли XMR на Bisq, Вам необходимо понять и следовать следующим требованиям:\n\nДля отправления XMR, необходимы официальные кошельки Monero GUI или Monero CLI с включённым флажком store-tx-info (включено в новых версиях). Удостоверьтесь, что Вам доступен ключ транзакций, необходимый в случае спора.\nmonero-wallet-cli (используйте команду get_tx_key)\nmonero-wallet-gui (перейдите в раздел history и нажмите на кнопку (P) для подтверждения оплаты)\n\n В дополнение к инструменту проверки XMR (https://xmr.llcoins.net/checktx.html), верификация также может быть выполнена в кошельке.\nmonero-wallet-cli: используя команду (check_tx_key).\nmonero-wallet-gui: разделе Advanced > Prove/Check.\nПереводы не проверяются обычными исследователями блоков.\n\nЕсли возникнет спор, арбитру потребуются от Вас следующие данные:\n- Личный ключ транзакции\n- Хеш(hash) транзакции\n- Публичный адрес получателя\n\nЕсли Вы не предоставите эти данные, либо используете несоответствующие кошельки, Вы проиграете спор. Посылающий XMR ответственен перед арбитром за подтверждение перевода XMR в случае спора.\n\nИдентификатор оплаты не нужен - только обычный публичный адрес.\nЕсли Вам не знаком этот процесс, посетите (https://www.getmonero.org/resources/user-guides/prove-payment.html) или осведомитесь на форуме Monero (https://forum.getmonero.org).
account.altcoin.popup.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 arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The 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 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 arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW).
account.altcoin.popup.ccx.msg=Trading CCX on Bisq requires that you understand the following requirements:\n\nTo send CCX you must use an official Conceal wallet, either CLI or GUI. After sending a transfer payment, the wallets\ndisplay the transaction secret key. You must save it along with the transaction hash (ID) and the recipient's public\naddress in case arbitration is necessary. In such a case, you must give all three to the arbitrator, who will then\nverify the CCX transfer using the Conceal Transaction Viewer (https://explorer.conceal.network/txviewer).\nBecause Conceal is a privacy coin, block explorers cannot verify transfers.\n\nFailure to provide the required data to the arbitrator will result in losing the dispute case.\nIf you do not save the transaction secret key immediately after transferring CCX, it cannot be recovered later.\nIf you do not understand these requirements, seek help at the Conceal discord (http://discord.conceal.network).
account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides, a transaction is not verifiable on the public blockchain. If required, you can prove your payment through the use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at (http://drgl.info/#check_txn).\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The Dragonglass sender is responsible for providing verification of the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help.
account.altcoin.popup.ZEC.msg=При использовании {0} допустимо использовать только прозрачные адреса (начиная с t) а не z-адреса (личные), потому что арбитр не сможет проверить транзакцию с z-адресами.
account.altcoin.popup.XZC.msg=При использовании {0} можно использовать только прозрачные (отслеживаемые) адреса, а не неотслеживаемые адреса, поскольку арбитр не сможет проверить транзакцию с неотслеживаемыми адресами в обозревателе блоков цепи / вlockchain.
account.altcoin.popup.bch=Bitcoin Cash и Bitcoin Classic страдают отсутствием защиты воспроизведения. Если вы используете эти монеты, убедитесь, что вы принимаете достаточные меры предосторожности и понимаете все последствия. Возможно понести убытки, отправив одну монету и непреднамеренно отправить те же монеты на другую блокцепь. Поскольку эти монеты были выпущены процессом "airdrop" и разделяют исторические данные с блокчейном Биткойн, существует также риск безопасности и значительный риск потери конфиденциальности. \n\nПросьба прочесть подробнее на форуме Bisq: https://forum.bisq.io/t/airdrop-coins-information-thread-bch-btg-bchc
@ -1006,8 +1008,8 @@ account.notifications.marketAlert.offerType.label=Тип предложения
account.notifications.marketAlert.offerType.buy=Предложения купить (хочу продать BTC)
account.notifications.marketAlert.offerType.sell=Предложения продать (хочу купить BTC)
account.notifications.marketAlert.trigger=Отклонение курса предложения (%)
account.notifications.marketAlert.trigger.info=Если задано отклонение от цены, Вы получите оповещение только когда предложение соответствует (или превышает) Вашим требованиям. Пример: Вы хотите продать BTC, но только с надбавкой 2% к текущей рыночной цене. Указав 2% в этом поле, Вы получите оповещение только от предложений с ценами, которые на 2% (или более) выше текущей рыночной цены.
account.notifications.marketAlert.trigger.prompt=Отклонение в процентах от рыночной цены (например, 2.50%, -0.50% и т. д.)
account.notifications.marketAlert.trigger.info=Если задано отклонение от цены, Вы получите оповещение только когда предложение соответствует (или превышает) Вашим требованиям. Пример: Вы хотите продать BTC, но только с надбавкой 2% к текущей рыночной цене. Указав 2% в этом поле, Вы получите оповещение только от предложений с ценами, которые на 2% (или более) выше текущей рыночной цены.
account.notifications.marketAlert.trigger.prompt=Отклонение в процентах от рыночной цены (напр. 2.50%, -0.50% и т. д.)
account.notifications.marketAlert.addButton=Добавить оповещение о предложении
account.notifications.marketAlert.manageAlertsButton=Управление оповещениями о предложениях
account.notifications.marketAlert.manageAlerts.title=Управление оповещениями о предложениях
@ -1021,7 +1023,7 @@ account.notifications.marketAlert.message.msg.below=ниже
account.notifications.marketAlert.message.msg.above=выше
account.notifications.marketAlert.message.msg=Новое предложение "{0} {1} " с ценой {2} ({3} {4} рыночная цена) и способом оплаты "{5}" было опубликовано в книге предложений Bisq.\nИдент. предложения: {6}.
account.notifications.priceAlert.message.title=Оповещение о цене для {0}
account.notifications.priceAlert.message.msg=Ваше оповещение о цене сработало. Текущая цена {0} {1} {2}
account.notifications.priceAlert.message.msg=Ваше оповещение о цене сработало. Текущая {0} цена {1} {2}
account.notifications.noWebCamFound.warning=Веб-камера не найдена.\n\nПросьба применить э-почту для отправки токена и ключа шифрования с Вашего мобильного телефона на приложение Bisq.
account.notifications.priceAlert.warning.highPriceTooLow=Более высокая цена должна быть больше чем более низкая цена.
account.notifications.priceAlert.warning.lowerPriceTooHigh=Нижняя цена должна быть ниже чем более высокая цена.
@ -1059,7 +1061,7 @@ dao.cycle.proposal=Этап предложения
dao.cycle.blindVote=Этап слепого голосования
dao.cycle.voteReveal=Этап выявления голосов
dao.cycle.voteResult=Результат голосования
dao.cycle.phaseDuration={0} блока (≈{1}); Блок {2} - {3} (≈{4} - ≈{5})
dao.cycle.phaseDuration={0} блоков (≈{1}); Блок {2} - {3} (≈{4} - ≈{5})
dao.results.cycles.header=Цыклы
dao.results.cycles.table.header.cycle=Цыкл
@ -1106,11 +1108,11 @@ dao.param.PROPOSAL_FEE=Сбор BSQ за предложение
dao.param.BLIND_VOTE_FEE=Сбор BSQ за голосование
# suppress inspection "UnusedProperty"
dao.param.COMPENSATION_REQUEST_MIN_AMOUNT=Мин. сумма запроса BSQ компенсации
dao.param.COMPENSATION_REQUEST_MIN_AMOUNT=Мин. сумма запроса BSQ компенсации
# suppress inspection "UnusedProperty"
dao.param.COMPENSATION_REQUEST_MAX_AMOUNT=Макс. сумма запроса BSQ компенсации
dao.param.COMPENSATION_REQUEST_MAX_AMOUNT=Макс. сумма запроса BSQ компенсации
# suppress inspection "UnusedProperty"
dao.param.REIMBURSEMENT_MIN_AMOUNT=Мин. сумма запроса BSQ возмещения
dao.param.REIMBURSEMENT_MIN_AMOUNT=Мин. сумма запроса BSQ возмещения
# suppress inspection "UnusedProperty"
dao.param.REIMBURSEMENT_MAX_AMOUNT=Макс. сумма запроса BSQ возмещения
@ -1200,7 +1202,7 @@ dao.bond.reputation.table.header=Мои залоговые депозиты ре
dao.bond.reputation.amount=Запереть BSQ на сумму
dao.bond.reputation.time=Срок разблокировки в блоках
dao.bond.reputation.salt=Соль
dao.bond.reputation.hash=Хэш
dao.bond.reputation.hash=Хеш
dao.bond.reputation.lockupButton=Запереть
dao.bond.reputation.lockup.headline=Подтвердить транзакцию блокировки
dao.bond.reputation.lockup.details=Запереть сумму: {0}\nВремя блокировки: {1} блок(ов) \n\nДействительно желаете продолжить?
@ -1224,7 +1226,7 @@ dao.bond.table.column.name=Имя
dao.bond.table.column.link=Ссылка
dao.bond.table.column.bondType=Тип гарантийного депозита
dao.bond.table.column.details=Подробности
dao.bond.table.column.lockupTxId=Транз. идент. блокировки
dao.bond.table.column.lockupTxId=Идент. транз. блокировки
dao.bond.table.column.bondState=Состояние гарантийного депозита
dao.bond.table.column.lockTime=Время блокировки
dao.bond.table.column.lockupDate=Дата блокировки
@ -1290,10 +1292,10 @@ dao.bond.bondedRoleType.MEDIATOR=Посредник
# suppress inspection "UnusedProperty"
dao.bond.bondedRoleType.ARBITRATOR=Арбитр
dao.burnBsq.assetFee=Сбор за листинг астива
dao.burnBsq.menuItem.assetFee=Сбор за листинг астива
dao.burnBsq.assetFee=Сбор за листинг актива
dao.burnBsq.menuItem.assetFee=Сбор за листинг актива
dao.burnBsq.menuItem.proofOfBurn=Proof of burn
dao.burnBsq.header=Сбор за листинг астива
dao.burnBsq.header=Сбор за листинг актива
dao.burnBsq.selectAsset=Выбрать актив
dao.burnBsq.fee=Сбор
dao.burnBsq.trialPeriod=Испытательный срок
@ -1306,7 +1308,7 @@ dao.burnBsq.assets.lookBackPeriod=Период проверки
dao.burnBsq.assets.trialFee=Сбор за испытательный срок
dao.burnBsq.assets.totalFee=Итого уплачен сбор
dao.burnBsq.assets.days={0} дней
dao.burnBsq.assets.toFewDays=Сбор за актив слишком низок. Мин. количество дней пробного периода {0}.
dao.burnBsq.assets.toFewDays=Взнос за актив слишком низок. Мин. количество дней пробного периода {0}.
# suppress inspection "UnusedProperty"
dao.assetState.UNDEFINED=Неопределено
@ -1322,11 +1324,11 @@ dao.assetState.REMOVED_BY_VOTING=Удалён голосованием
dao.proofOfBurn.header=Proof of burn
dao.proofOfBurn.amount=Количество
dao.proofOfBurn.preImage=Pre-image
dao.proofOfСжечь.burn=Сжечь
dao.proofOfBurn.burn=Сжечь
dao.proofOfBurn.allTxs=Все транзакции proof of burn
dao.proofOfBurn.myItems=Мои транзакции proof of burn
dao.proofOfBurn.date=Дата
dao.proofOfBurn.hash=Хэш
dao.proofOfBurn.hash=Хеш
dao.proofOfBurn.txs=Транзакции
dao.proofOfBurn.pubKey=Общедоступный ключ
dao.proofOfBurn.signature.window.title=Подписать сообщение ключом из транзакции proof or burn
@ -1362,7 +1364,7 @@ dao.phase.separatedPhaseBar.PROPOSAL=Этап предложения
# suppress inspection "UnusedProperty"
dao.phase.separatedPhaseBar.BLIND_VOTE=Слепое голосование
# suppress inspection "UnusedProperty"
dao.phase.separatedPhaseBar.VOTE_REVEAL=Показать голосование
dao.phase.separatedPhaseBar.VOTE_REVEAL=Показать голосование
# suppress inspection "UnusedProperty"
dao.phase.separatedPhaseBar.RESULT=Результат голосования
@ -1408,8 +1410,8 @@ dao.proposal.myVote.reject=Отклонить предложение
dao.proposal.myVote.removeMyVote=Игнорировать предложение
dao.proposal.myVote.merit=Вес голоса от заслуженного BSQ
dao.proposal.myVote.stake=Вес голоса от доли
dao.proposal.myVote.blindVoteTxId=Транз. идент. слепого голосования
dao.proposal.myVote.revealTxId=Транз. идент. выявления голоса
dao.proposal.myVote.blindVoteTxId=Идент. транзакции слепого голосования
dao.proposal.myVote.revealTxId=Идент. транзакции выявления голоса
dao.proposal.myVote.stake.prompt=Макс. доступный баланс для голосования: {0}
dao.proposal.votes.header=Голосование по всем предложениям
dao.proposal.votes.header.voted=Мой голос
@ -1423,16 +1425,16 @@ dao.proposal.display.type=Тип предложения
dao.proposal.display.name=Имя/ник
dao.proposal.display.link=Ссылка на подробности
dao.proposal.display.link.prompt=Ссылка о неисправности на Github
dao.proposal.display.requestedBsq=Запрос средств в BSQ
dao.proposal.display.requestedBsq=Запрашиваемая сумма в BSQ
dao.proposal.display.bsqAddress=BSQ-адрес
dao.proposal.display.txId= Идент. транз. предложения
dao.proposal.display.txId=Идент. транзакции предложения
dao.proposal.display.proposalFee=Сбор за предложение
dao.proposal.display.myVote=Мой голос
dao.proposal.display.voteResult=Сводка итогов голосования
dao.proposal.display.bondedRoleComboBox.label=Тип обеспеченной роли
dao.proposal.display.requiredBondForRole.label=Необходимый гарантийный депозит роли
dao.proposal.display.tickerSymbol.label=Тикер
dao.proposal.display.option=Параметр
dao.proposal.display.option=Вариант
dao.proposal.table.header.proposalType=Тип предложения
dao.proposal.table.header.link=Ссылка
@ -1459,7 +1461,7 @@ dao.proposal.display.assetComboBox.label=Актив для удаления
dao.blindVote=слепое голосование
dao.blindVote.startPublishing=Транзакция слепого голосования публикуется...
dao.blindVote.success=Ваша транзакция слепого голосования успешно опубликована.
dao.blindVote.success=Ваш слепой голос успешно опубликован.
dao.wallet.menuItem.send=Послать
dao.wallet.menuItem.receive=Получить
@ -1469,11 +1471,11 @@ dao.wallet.dashboard.myBalance=Баланс моего кошелька
dao.wallet.dashboard.distribution=Распределение всего BSQ
dao.wallet.dashboard.locked=Глобальное состояние запертого BSQ
dao.wallet.dashboard.market=Данные рынка
dao.wallet.dashboard.genesis=Genesis транзакция
dao.wallet.dashboard.genesis=Исходная транзакция
dao.wallet.dashboard.txDetails=Статистика транзакций BSQ
dao.wallet.dashboard.genesisBlockHeight=Номер исходного блока
dao.wallet.dashboard.genesisTxId=Идент. исходной транзакции
dao.wallet.dashboard.genesisIssueAmount=BSQ выданные в исходной транзакции
dao.wallet.dashboard.genesisIssueAmount=BSQ выданные в исходной транзакции
dao.wallet.dashboard.compRequestIssueAmount=BSQ выданные на запросы компенсации
dao.wallet.dashboard.reimbursementAmount=BSQ выданные на запросы возмещения
dao.wallet.dashboard.availableAmount=Итого доступных BSQ
@ -1482,7 +1484,7 @@ dao.wallet.dashboard.totalLockedUpAmount=Заперто в гарантийны
dao.wallet.dashboard.totalUnlockingAmount=Разблокировка BSQ из гарантийных депозитов
dao.wallet.dashboard.totalUnlockedAmount=BSQ разблокировано из гарантийных депозитов
dao.wallet.dashboard.totalConfiscatedAmount=BSQ конфисковано из гарантийных депозитов
dao.wallet.dashboard.allTx=Общее число транзакции BSQ
dao.wallet.dashboard.allTx=Общее количество транзакций BSQ
dao.wallet.dashboard.utxo=Общее кол-во неизрасходованных (UTXO)
dao.wallet.dashboard.compensationIssuanceTx=Общее кол-во транзакций выдачи запроса компенсации
dao.wallet.dashboard.reimbursementIssuanceTx=Общее кол-во транзакций выдачи запроса возмещения
@ -1535,13 +1537,13 @@ dao.tx.type.enum.PROPOSAL=Сбор за предложение
# suppress inspection "UnusedProperty"
dao.tx.type.enum.BLIND_VOTE=Сбор за голосование вслепую
# suppress inspection "UnusedProperty"
dao.tx.type.enum.VOTE_REVEAL=Показать голосование
dao.tx.type.enum.VOTE_REVEAL=Показать голосование
# suppress inspection "UnusedProperty"
dao.tx.type.enum.LOCKUP=Запереть гарантийный депозит
# suppress inspection "UnusedProperty"
dao.tx.type.enum.UNLOCK=Отпереть гарантийный депозит
# suppress inspection "UnusedProperty"
dao.tx.type.enum.ASSET_LISTING_FEE=Сбор за листинг астива
dao.tx.type.enum.ASSET_LISTING_FEE=Сбор за листинг актива
# suppress inspection "UnusedProperty"
dao.tx.type.enum.PROOF_OF_BURN=Proof of burn
@ -1582,9 +1584,9 @@ displayUpdateDownloadWindow.download.failed=Сбой загрузки.\nПожа
displayUpdateDownloadWindow.installer.failed=Не удалось определить правильный установщик. Пожалуйста, скачайте и проверьте вручную на https://bisq.network/downloads
displayUpdateDownloadWindow.verify.failed=Проверка не удалась.\nПожалуйста, скачайте и проверьте вручную на https://bisq.network/downloads
displayUpdateDownloadWindow.success=Новая версия успешно скачалась и подпись проверена.\n\nПожалуйста, откройте директорию загрузки, закройте приложение и установите новую версию.
displayUpdateDownloadWindow.download.openDir=Открыть директорию для загрузки
displayUpdateDownloadWindow.download.openDir=Открыть директорию для загрузки
disputeСводкаWindow.title=Сводка
disputeSummaryWindow.title=Сводка
disputeSummaryWindow.openDate=Дата открытия билета поддержки
disputeSummaryWindow.role=Роль трейдера
disputeSummaryWindow.evidence=Доказательство
@ -1592,8 +1594,8 @@ disputeSummaryWindow.evidence.tamperProof=Подтверждение доказ
disputeSummaryWindow.evidence.id=Проверка идентификации
disputeSummaryWindow.evidence.video=Видео/Экранная демонстрация
disputeSummaryWindow.payout=Выплата суммы сделки
disputeSummaryWindow.payout.getsTradeAmount=BTC {0} получение выплаты суммы сделки
disputeSummaryWindow.payout.getsAll=BTC {0} Получить всё
disputeSummaryWindow.payout.getsTradeAmount=BTC {0} получит выплату суммы сделки
disputeSummaryWindow.payout.getsAll=BTC {0} получит всё
disputeSummaryWindow.payout.custom=Пользовательская выплата
disputeSummaryWindow.payout.adjustAmount=Введенная сумма превышает доступное количество {0}. \nМы введём максимально возможное значение.
disputeSummaryWindow.payoutAmount.buyer=Сумма выплаты покупателю
@ -1610,7 +1612,7 @@ disputeSummaryWindow.reason.bank=Банк
disputeSummaryWindow.summaryNotes=Краткие заметки
disputeSummaryWindow.addSummaryNotes=Добавить краткие заметки
disputeSummaryWindow.close.button=Закрыть билет поддержки
disputeSummaryWindow.close.msg=Билет поддержки закрыт {0}\n\nИтог:\n{1} представил защищённое от подделки доказательство: {2}\n{3} подтвердил личность: {4}\n{5} сделал видео или скринкаст: {6}\nСумма выплаты покупателю BTC: {7}\nСумма выплаты продавцу BTC {8}\n\nЗаметки:\n{9}
disputeSummaryWindow.close.msg=Билет поддержки закрыт {0}\n\nИтог:\n{1} предoставил(a) защищённое от подделки доказательство: {2}\n{3} подтвердил(a) личность: {4}\n{5} сделал(a) видео или скринкаст: {6}\nСумма выплаты покупателю BTC: {7}\nСумма выплаты продавцу BTC {8}\n\nЗаметки:\n{9}
disputeSummaryWindow.close.closePeer=Вам необходимо также закрыть билет контрагента!
emptyWalletWindow.headline={0} аварийный инструмент кошелька
@ -1663,7 +1665,7 @@ qRCodeWindow.request=Запрос платежа:\n{0}
selectDepositTxWindow.headline=Выберите транзакцию ввода средств для включения в спор
selectDepositTxWindow.msg=Транзакция перевода на счет не сохраненилась в сделке.\nВыберите в своём кошельке одну из существующих транзакций типа multisig перевода на счет, использованной в неудавшейся сделке.\n\nМожно найти правильную транзакцию, открыв окно сведений о сделке (щелкните на идентификаторе торговли в списке) и после вывода транзакции с оплатой сделки на следующую транзакцию, где вы увидите мультиподписную транзакцию перевода на счет (адрес начинается с 3). Этот идентификатор транзакции должен быть виден в представленном здесь списке. После того, как найдёте правильную транзакцию, выберите эту транзакцию тут и продолжайте.\n\nИзвините за неудобство. Такие сбои редки, и мы попытаемся улучшить способы решения.
selectDepositTxWindow.select=Выберите транзакцию положить на счёт
selectDepositTxWindow.select=Выберите транзакцию депозита
selectBaseCurrencyWindow.headline=Выбор рынка
selectBaseCurrencyWindow.msg=Выбранный рынок по умолчанию - {0}.\n\nЕсли желаете изменить базовую валюту, выберите её в раскрывающемся списке.\nТакже возможно изменить базовую валюту в разделе \"Настройки/Информация сети\".
@ -1683,7 +1685,7 @@ sendPrivateNotificationWindow.enterNotification=Введите уведомле
sendPrivateNotificationWindow.send=Отправить личное уведомление
showWalletDataWindow.walletData=Данные кошелька
showWalletDataWindow.includePrivKeys=Добавить личные ключи
showWalletDataWindow.includePrivKeys=Включить личные ключи
# We do not translate the tac because of the legal nature. We would need translations checked by lawyers
# in each language which is too expensive atm.
@ -1720,7 +1722,7 @@ torNetworkSettingWindow.deleteFiles.button=Удалить устаревшие
torNetworkSettingWindow.deleteFiles.progress=Tor завершает работу
torNetworkSettingWindow.deleteFiles.success=Устаревшие файлы Tor успешно удалены. Пожалуйста, перезапустите приложение.
torNetworkSettingWindow.bridges.header=Tor сеть заблокирована?
torNetworkSettingWindow.bridges.info=Если Tor заблокирована Вашим интернет-провайдером или страной, попробуйте использовать Tor bridges.\nПосетите веб-страницу Tor по адресу: https://bridges.torproject.org/bridges чтобы узнать больше о bridges и pluggable transports.
torNetworkSettingWindow.bridges.info=Если Tor заблокирован Вашим интернет-провайдером или страной, попробуйте использовать мосты Tor (bridges).\nПосетите веб-страницу Tor по адресу: https://bridges.torproject.org/bridges чтобы узнать больше о мостах и подключаемых транспортах.
feeOptionWindow.headline=Выберите валюту для оплаты торгового сбора
feeOptionWindow.info=Вы можете оплатить торговый сбор в BSQ или BTC. Если Вы выбираете BSQ, то увеличиваете уценку торгового сбора.
@ -1746,7 +1748,7 @@ popup.headline.error=Ошибка
popup.doNotShowAgain=Не показывать снова
popup.reportError.log=Открыть файл журнала
popup.reportError.gitHub=Сообщить проблему на Github в раздел 'issues'
popup.reportError={0}\n\nчтобы помочь нам улучшить приложение, просьба сообщить о неисправности на нашем баг-трекере на GitHub (https://github.com/bisq-network/bisq-desktop/issues).\nСообщение о неисправности будет скопировано в буфер обмена при нажатии кнопки ниже.\nНам облегчит отладку, если Вы прикрепите также bisq.log файл.
popup.reportError={0}\n\nЧтобы помочь нам улучшить приложение, просьба сообщить о неисправности, открыв новую тему на https://github.com/bisq-network/bisq/issues. \nСообщение о неисправности будет скопировано в буфер обмена при нажатии любой из кнопок ниже.\nНам облегчит отладку, если Вы включите bisq.log файл журнала, нажав "открыть файл журнала", сохраните копию и прикрепите ее к отчету о неисправности.
popup.error.tryRestart=Пожалуйста, попробуйте перезагрузить ваше приложение и проверьте подключение к сети, чтобы узнать, можете ли вы решить проблему.
popup.error.takeOfferRequestFailed=Произошёл сбой, когда контрагент попытался принять одно из Ваших предложений:\n{0}
@ -1756,14 +1758,14 @@ error.deleteAddressEntryListFailed=Не удалось удалить AddressEnt
popup.warning.walletNotInitialized=Кошелёк ещё не инициализирован
popup.warning.wrongVersion=У Вас вероятно установлена не та версия Bisq.\nАрхитектура Вашего компьютера: {0}.\nУстановленные у Вас файлы: {1}.\nПожалуйста переустановите соответствующую версию ({2}).
popup.warning.incompatibleDB=Обнаружены несовместимые файлы базы данных!\nБазы данных этого файла(ов) несовместимы с нашей текущей базой кода:\n{0}\n\nМы сделали резервную копию поврежденного файла(ов) и применили значения по умолчанию к новой версии базы данных.\n\nРезервная копия находится по адресу:\n{1}/db/backup_of_corrupted_data.\n\nПроверьте, установлена ли новейшая версия Bisq.\nВы можете скачать ее по адресу:\nhttps://bisq.network/downloads\n\nПросьба перезагрузить приложение.
popup.warning.incompatibleDB=Обнаружены несовместимые файлы базы данных!\nБазы данных этих файлов несовместимы с нашей текущей базой кода:\n{0}\n\nМы сделали резервную копию поврежденных файлов и применили значения по умолчанию к новой версии базы данных.\n\nРезервная копия находится по адресу:\n{1}/db/backup_of_corrupted_data.\n\nПроверьте, установлена ли новейшая версия Bisq.\nВы можете скачать ее по адресу:\nhttps://bisq.network/downloads\n\nПросьба перезапустить приложение.
popup.warning.startupFailed.twoInstances=Bisq уже запущен. Нельзя запустить два экземпляра Bisq.
popup.warning.cryptoTestFailed=Кажется, Вы используете самокомпилированный двоичный файл, и не следуете инструкциям сборки в https://github.com/bisq-network/exchange/blob/master/doc/build.md#7-enable-unlimited-strength-for-cryptographic-keys.\n\nЕсли это не так, и Вы используете официальный бинарный Bisq, просьба отправить отчет о сбое на страницу Github.\nСбой={0}
popup.warning.tradePeriod.halfReached=Ваша сделка с идентификатором {0} достигла половины макс. допустимого торгового периода, и до сих пор не завершена.\n\nТекущий период заканчивается {1}\n\nПросьба просмотреть дополнительную информацию о состоянии сделки в разделе \"Папка/Текущие сделки\" .
popup.warning.tradePeriod.ended=Ваша сделка с идентификатором {0} достигла макс. допустимого торгового срока и не завершилась.\n\nТорговый период закончился {1}\n\nПросьба просмотреть свою сделку в разделе \"Папка/Текущие сделки\" для обращения к арбитру.
popup.warning.noTradingAccountSetup.headline=Вы не настроили торговый счёт
popup.warning.noTradingAccountSetup.msg=Прежде чем создать предложение, следует настроить счета национальной валюты или алткойна. \nЖелаете настроить счёт?
popup.warning.noArbitratorsAvailable= Нет доступных арбитров.
popup.warning.noArbitratorsAvailable=Нет доступных арбитров.
popup.warning.notFullyConnected=Необходимо подождать, пока завершается подключение к сети.\nЭто может занять до 2 минут при запуске.
popup.warning.notSufficientConnectionsToBtcNetwork=Необходимо подождать, пока образуется по меньшей мере {0} соединений с сетью Биткойн.
popup.warning.downloadNotComplete=Необходимо подождать до завершения загрузки недостающих блоков цепи Биткойн.
@ -1772,18 +1774,18 @@ popup.warning.tooLargePercentageValue=Нельзя установить проц
popup.warning.examplePercentageValue=Введите процентное число, например \"5.4\" для 5.4%
popup.warning.noPriceFeedAvailable=Источник рыночного курса этой валюты отсутствует. Невозможно использовать процентный курс.\nПросьба указать фиксированный курс.
popup.warning.sendMsgFailed=Не удалось отправить сообщение Вашему контрагенту .\nПопробуйте еще раз, и если неисправность повторится, сообщите о ней.
popup.warning.insufficientBtcFundsForBsqTx=У вас недостаточно средств BTC для оплаты комиссии майнера этой транзакции.\nПросьба пополнить свой кошелек BTC.\nНедостаёт средств: {0}
popup.warning.insufficientBtcFundsForBsqTx=У вас недостаточно средств BTC для оплаты комиссии майнера за этy транзакцию.\nПросьба пополнить свой кошелек BTC.\nНедостаёт средств: {0}
popup.warning.insufficientBsqFundsForBtcFeePayment=У Вас недостаточно BSQ для оплаты торг. сбора в BSQ. Вы можете заплатить в BTC, или Вам необходимо пополнить свой кошелёк BSQ. BSQ можно купить в Bisq.\nНедостаёт BSQ: {0}
popup.warning.noBsqFundsForBtcFeePayment=В Вашем кошельке BSQ недостаточно средств для оплаты торг. сбора в BSQ.
popup.warning.messageTooLong=Ваше сообщение превышает макс. Разрешенный размер. Пожалуйста, отправьте его в нескольких частях или загрузите в службу, например https://pastebin.com.
popup.warning.messageTooLong=Ваше сообщение превышает макс. разрешенный размер. Пожалуйста, отправьте его в нескольких частях или загрузите в службу, например https://pastebin.com.
popup.warning.lockedUpFunds=У Вас есть запертые средства от неудачной сделки.\nЗапертый баланс: {0}\nАдрес транзакции депозита: {1}\nИдентификатор сделки {2}.\nПросьба создать билет поддержки, выбрав сделку в разделе незавершенных сделок и нажав \"alt + o\" или \"option + o\"."
popup.warning.nodeBanned=Один из узлов {0} был запрещен/забанен. Перезапустите приложение, чтобы убедиться, что оно не подключено к запрещенному узлу.
popup.warning.priceRelay=ретранслятор курса
popup.warning.seed=кодовые слова
popup.info.securityDepositInfo=Чтобы гарантировать следование торговому протоколу трейдерами, необходим залоговый депозит.\n\nОн поступит на Ваш счёт и останется в Вашем торговом кошельке до успешного завершения сделки, и затем будет возвращен Вам.\n\nУчтите, что если Вы создаёте новое предложение, Bisq должно быть подключено к сети для принятия предложения другими трейдерами. Чтобы Ваши предложения были доступны в сети, компьютер и Bisq должны быть включёны и подключены к сети. (т. е. убедитесь, что компьютер не впал в режим ожидания...монитор в режиме ожидания не проблема).
popup.info.securityDepositInfo=Чтобы гарантировать следование торговому протоколу трейдерами, обоим необходимо заплатить залоговый депозит.\n\nДепозит остаётся в Вашем торговом кошельке до успешного завершения сделки, и затем будет возвращен Вам.\n\nУчтите, что если Вы создаёте новое предложение, Bisq должен быть подключён к сети для принятия предложения другими трейдерами. Чтобы Ваши предложения были доступны в сети, компьютер и Bisq должны быть включёны и подключены к сети. (т. е. убедитесь, что компьютер не впал в режим ожидания...монитор в режиме ожидания не проблема).
popup.info.cashDepositInfo=Просьба убедиться, что в Вашем районе существует отделение банка, где возможно внести депозит наличными.\nИдентификатор (BIC/SWIFT) банка продавца: {0}.
popup.info.cashDepositInfo.confirm=Я подтверждаю, что могу внести депозит
@ -1797,7 +1799,7 @@ popup.securityRecommendation.msg=Напоминаем и рекомендуем
popup.bitcoinLocalhostNode.msg=Bisq обнаружил локально работающий узел Bitcoin Core (на локальном узле).\nПеред запуском Биск убедитесь, что этот узел полностью синхронизирован с сетью Биткойн и не работает в режиме обрезки данных "pruning".
popup.shutDownInProgress.headline=Работа завершается
popup.shutDownInProgress.headline=Работа завершается
popup.shutDownInProgress.msg=Завершение работы приложения может занять несколько секунд.\nПросьба не прерывать этот процесс.
popup.attention.forTradeWithId=Обратите внимание на сделку с идентификатором {0}
@ -1805,6 +1807,9 @@ popup.attention.forTradeWithId=Обратите внимание на сделк
popup.roundedFiatValues.headline=Новая функция конфиденциальности: Округленные значения нац. валют
popup.roundedFiatValues.msg=Для повышения конфиденциальности Вашей сделки, сумма {0} была округлена.\n\nВ зависимости от версии приложения, Вы заплатите или получите либо значения с десятичными знаками, либо округленные.\n\nОтныне, оба значения соответствуют торговому протоколу.\n\nТакже имейте в виду, что значения BTC изменяются автоматически, чтобы предельно соответствовать округленной сумме нац. валюты.
popup.info.multiplePaymentAccounts.headline=Multiple payment accounts available
popup.info.multiplePaymentAccounts.msg=You have multiple payment accounts available for this offer. Please make sure you've picked the right one.
####################################################################
# Notifications
@ -1874,7 +1879,7 @@ table.placeholder.noData=Сейчас данные недоступны
peerInfoIcon.tooltip.tradePeer=контрагента
peerInfoIcon.tooltip.maker=Создателя
peerInfoIcon.tooltip.trade.traded=Onion/Tor адрес {0}: {1}\nВы уже торговали {2} раз(a) с данным трейдером\n{3}
peerInfoIcon.tooltip.trade.traded=Onion/Tor адрес {0}: {1}\nВы уже торговали {2} раз(a) с данным трейдером\n{3}
peerInfoIcon.tooltip.trade.notTraded=Onion/Tor адрес {0}: {1}\nВы ещё не торговали с этим трейдером.\n {2}
peerInfoIcon.tooltip.age=Платёжный счёт создан {0} назад.
peerInfoIcon.tooltip.unknownAge=Срок существования платёжного счёта неизвестен.
@ -2048,7 +2053,7 @@ payment.promptPay.promptPayId=Удостовер. гражданства / на
payment.supportedCurrencies=Поддерживаемые валюты
payment.limitations=Ограничения
payment.salt=Модификатор/Соль для подтверждения срока существования счёта
payment.error.noHexSalt=Соль должна быть в HEX/шестнадцатеричном формате.\nРекомендуется редактировать поле соль, только при переносе её из старого счёта, чтобы сохранить его срок существования. Срок проверяется с помощью соли и опознающих данных счёта (напр. IBAN).
payment.error.noHexSalt=Соль должна быть в HEX/шестнадцатеричном формате.\nРекомендуется редактировать поле соли только при переносе её из старого счёта, чтобы сохранить его срок существования. Срок проверяется с помощью соли и опознающих данных счёта (напр. IBAN).
payment.accept.euro=Принять сделки из этих стран ЕUR
payment.accept.nonEuro=Принять сделки из этих не-ЕUR стран
payment.accepted.countries=Приемлемые страны
@ -2085,20 +2090,20 @@ payment.clearXchange.info=Убедитесь, что выполняете тре
payment.moneyGram.info=При использовании MoneyGram покупатель BTC должен отправить по э-почте продавцу BTC номер авторизации и фотографию квитанции. В квитанции должно быть четко указано полное имя продавца, страна, штат и сумма. В процессе сделки, покупателю будет показан адрес э-почты продавца.
payment.westernUnion.info=При использовании Western Union покупатель BTC обязан отправить продавцу BTC по э-почте MTCN (номер отслеживания) и фотографию квитанции. В квитанции должно быть четко указано полное имя продавца, город, страна и сумма. В процессе сделки, покупателю будет показан адрес э-почты продавца.
payment.halCash.info=Используя HalCash, покупатель BTC обязан отправить продавцу BTC код HalCash через СМС с мобильного телефона.\n\nПросьба убедиться, что не превышена макс. сумма, которую Ваш банк позволяет отправить с HalCash. Мин. сумма каждого вывода составляет 10 EUR, и макс. 600 EUR. При повторном выводе - 3000 EUR на получателя в день и 6000 EUR на получателя в месяц. Просьба сверить эти лимиты с Вашим банком, и убедиться, что используются те же.\n\nСумма должна быть кратна 10 EUR, так как невозможно снять другие суммы с банкомата. В приложении, диалог "создать-предложение" и "принять-предложение" отрегулирует правильную сумму BTC. Нельзя использовать рыночную цену, так как сумма в EUR будет меняться с курсом.\n\nВ случае спора, покупателю BTC необходимо предоставить доказательство отправки EUR.
payment.halCash.info=Используя HalCash, покупатель BTC обязан отправить продавцу BTC код HalCash через СМС с мобильного телефона.\n\nПросьба убедиться, что не превышена макс. сумма, которую Ваш банк позволяет отправить с HalCash. Мин. сумма каждого вывода составляет 10 EUR, и макс. 600 EUR. При повторном выводе - 3000 EUR на получателя в день и 6000 EUR на получателя в месяц. Просьба сверить эти лимиты с Вашим банком, и убедиться, что используются те же.\n\nСумма должна быть кратна 10 EUR, так как невозможно снять другие суммы с банкомата. В приложении, диалог "создать-предложение" и "принять-предложение" отрегулирует правильную сумму BTC. Нельзя использовать рыночный курс, так как сумма в EUR будет меняться с курсом.\n\nВ случае спора, покупателю BTC необходимо предоставить доказательство отправки EUR.
payment.limits.info=Учтите, что все банковские переводы несут определенный риск возвратного платежа.\n\nЧтобы снизить этот риск, Bisq ограничивает суммы сделок, на основе двух факторов: \n\n1. Расчёт уровня риска возвратного платежа данного метода оплаты \n2. Срок существования Вашего счета, созданного Вами в Bisq для этого метода оплаты\n\nСрок существования нового счёта создаваемый Вами сейчас равен нулю. С ростом этого срока в течении двух месяцев, предел сумм сделок будет расти:\n\n● В течении 1-го месяца, предел каждой сделки будет {0}\n● В течении 2-го месяца, предел будет {1}\n● После 2-го месяца, предел будет {2}\n\nУчтите, что нет никаких ограничений на общее количество Ваших сделок.
payment.cashDeposit.info=Просьба удостовериться, что Ваш банк позволяет отправлять денежные депозиты на счета других. Например, Bank of America и Wells Fargo больше не разрешают такие депозиты.
payment.f2f.contact=Контактная информация
payment.f2f.contact.prompt=Как Вы хотите связаться с контрагентом? (адрес электронной почты, номер телефона...)
payment.f2f.city=Город для встречи "лицом к лицу"
payment.f2f.city=Город для встречи "лицом к лицу"
payment.f2f.city.prompt=Город будет назван в предложении
payment.f2f.optionalExtra=Дополнительная необязательная информация
payment.f2f.extra=Дополнительная информация
payment.f2f.extra.prompt=Создатель в праве определить "условия", или добавить общедоступную контактную информацию. Это будет показано в предложении.
payment.f2f.info=В сделках F2F 'лицом к лицу' особые правила и риск, в отличии от транзакций онлайн. \n\nОсновные различия:\n● Контрагенты вынуждены обмениваться информацией о месте и времени встречи, используя предоставленные ими контактные данные.\n● Контрагенты вынуждены приносить свои ноутбуки, и подтверждать отправку и получение платежа при встрече.\n● Если создатель определяет особые 'условия', он обязан указать их в поле 'Дополнительная информация' при создании счёта.\n● Принимая предложение, получатель соглашается с заявленными создателем 'условиями'.\n● В случае возникновения спора, арбитр не способен помочь, так как затруднительно получить неопровержимые доказательства того, что произошло при встрече. В таких случаях BTC могут быть заперты навсегда, или до тех пор, пока контрагенты не достигнут согласия.\n\nДля полной уверенности, что Вы понимаете особенности сделок 'лицом к лицу', просьба прочесть инструкции и рекомендации по ссылке: 'https://docs.bisq.network/trading-rules.html#f2f-trading'
payment.f2f.info=В сделках F2F 'лицом к лицу' есть особые правила и риски, в отличии от транзакций онлайн. \n\nОсновные различия:\n● Контрагентам нужно обмениваться информацией о месте и времени встречи, используя предоставленные ими контактные данные.\n● Контрагентам нужно принести свои ноутбуки, и подтвердить отправку и получение платежа при встрече.\n● Если создатель определяет особые 'условия', он обязан указать их в поле 'Дополнительная информация' при создании счёта.\n● Принимая предложение, получатель соглашается с заявленными создателем 'условиями'.\n● В случае возникновения спора, арбитр не способен помочь, так как затруднительно получить неопровержимые доказательства того, что произошло при встрече. В таких случаях BTC могут быть заперты навсегда, или до тех пор, когда контрагенты достигнут согласия.\n\nДля полной уверенности, что Вы понимаете особенности сделок 'лицом к лицу', просьба прочесть инструкции и рекомендации на ссылке: 'https://docs.bisq.network/trading-rules.html#f2f-trading'
payment.f2f.info.openURL=Открыть веб-страницу
payment.f2f.offerbook.tooltip.countryAndCity=Страна и город: {0} / {1}
payment.f2f.offerbook.tooltip.extra=Дополнительная информация: {0}
@ -2132,7 +2137,7 @@ MONEY_GRAM_SHORT=MoneyGram
# suppress inspection "UnusedProperty"
WESTERN_UNION_SHORT=Western Union
# suppress inspection "UnusedProperty"
F2F_SHORT=Лицом к лицу
F2F_SHORT=Лицом к лицу
# Do not translate brand names
# suppress inspection "UnusedProperty"
@ -2273,11 +2278,11 @@ validation.iban.invalidLength=Номер должен быть от 15 до 34
validation.interacETransfer.invalidAreaCode=Код не Канадского региона
validation.interacETransfer.invalidPhone=Неверный формат номера телефона или адрес электронной почты
validation.interacETransfer.invalidQuestion=Должно содержать только буквы, цифры, пробелы и/или символы ' _ , . ? -
validation.interacETransfer.invalidAnswer=Необходимо одно слово, содержащее только буквы, цифры и символ -
validation.interacETransfer.invalidAnswer=Должно быть одно слово, содержащее только буквы, цифры и/или символ -
validation.inputTooLarge=Данные должны быть не более {0}
validation.inputTooSmall=Данные должны быть более {0}
validation.amountBelowDust=Сумма ниже предела ("пыли") {0} не допускается.
validation.length=Длина должна быть между {0} и {1}
validation.pattern=Данные должны быть в формате: {0}
validation.noHexString=Данные не в шестнадцатеричном формате.
validation.advancedCash.invalidFormat=Необходим действительный идент. э-почты или кошелька в формате: x000000000000
validation.advancedCash.invalidFormat=Должен быть действительный идент. э-почты или кошелька в формате: x000000000000

27
core/src/main/resources/i18n/displayStrings_sr.properties
View file

@ -299,6 +299,8 @@ market.trades.tooltip.candle.date=Datum:
offerbook.createOffer=Napravite ponudu
offerbook.takeOffer=Prihvatite ponudu
offerbook.takeOfferToBuy=Take offer to buy {0}
offerbook.takeOfferToSell=Take offer to sell {0}
offerbook.trader=Trgovac
offerbook.offerersBankId=ID banke tvorca ponude: {0}
offerbook.offerersBankName=Ime banke tvorca ponude: {0}
@ -560,12 +562,12 @@ portfolio.pending.step3_buyer.warn.part1b=kod vašeg platnog provajdera (npr. ba
portfolio.pending.step3_buyer.warn.part2=The BTC seller still has not confirmed your payment!\nPlease check {0} if the payment sending was successful.\nIf the BTC seller does not confirm the receipt of your payment until {1} the trade will be investigated by the arbitrator.
portfolio.pending.step3_buyer.openForDispute=The BTC seller has not confirmed your payment!\nThe max. period for the trade has elapsed.\nPlease contact the arbitrator for opening a dispute.
# suppress inspection "TrailingSpacesInProperty"
portfolio.pending.step3_seller.part=Your trading partner has confirmed that he initiated the {0} payment.\n\n
portfolio.pending.step3_seller.part=Your trading partner has confirmed that they have initiated the {0} payment.\n\n
portfolio.pending.step3_seller.altcoin.explorer=on your favorite {0} blockchain explorer
portfolio.pending.step3_seller.altcoin.wallet=at your {0} wallet
portfolio.pending.step3_seller.altcoin={0}Please check {1} if the transaction to your receiving address\n{2}\nhas already sufficient blockchain confirmations.\nThe payment amount has to be {3}\n\nYou can copy & paste your {4} address from the main screen after closing that popup.
portfolio.pending.step3_seller.postal={0}Please check if you have received {1} with \"US Postal Money Order\" from the BTC buyer.\n\nThe trade ID (\"reason for payment\" text) of the transaction is: \"{2}\"
portfolio.pending.step3_seller.bank=Your trading partner has confirmed that he initiated the {0} payment.\n\nPlease go to your online banking web page and check if you have received {1} from the BTC buyer.\n\nThe trade ID (\"reason for payment\" text) of the transaction is: \"{2}\"\n\n
portfolio.pending.step3_seller.bank=Your trading partner has confirmed that they have initiated the {0} payment.\n\nPlease go to your online banking web page and check if you have received {1} from the BTC buyer.\n\nThe trade ID (\"reason for payment\" text) of the transaction is: \"{2}\"\n\n
portfolio.pending.step3_seller.cash=Because the payment is done via Cash Deposit the BTC buyer has to write \"NO REFUND\" on the paper receipt, tear it in 2 parts and send you a photo by email.\n\nTo avoid chargeback risk, only confirm if you received the email and if you are sure the paper receipt is valid.\nIf you are not sure, {0}
portfolio.pending.step3_seller.moneyGram=The buyer has to send you the Authorisation number and a photo of the receipt by email.\nThe receipt must clearly show your full name, country, state and the amount. Please check your email if you received the Authorisation number.\n\nAfter closing that popup you will see the BTC buyer's name and address for picking up the money from MoneyGram.\n\nOnly confirm receipt after you have successfully picked up the money!
portfolio.pending.step3_seller.westernUnion=The buyer has to send you the MTCN (tracking number) and a photo of the receipt by email.\nThe receipt must clearly show your full name, city, country and the amount. Please check your email if you received the MTCN.\n\nAfter closing that popup you will see the BTC buyer's name and address for picking up the money from Western Union.\n\nOnly confirm receipt after you have successfully picked up the money!
@ -926,10 +928,10 @@ account.arbitratorSelection.minOne=Potrebno je da imate bar jednog arbitra izabr
account.altcoin.yourAltcoinAccounts=Your altcoin accounts
account.altcoin.popup.wallet.msg=Please be sure that you follow the requirements for the usage of {0} wallets as described on the {1} web page.\nUsing wallets from centralized exchanges where (a) you don''t control your keys or (b) which don''t use compatible wallet software is risky: it can lead to loss of the traded funds!\nThe arbitrator is not a {2} specialist and cannot help in such cases.
account.altcoin.popup.wallet.confirm=Razumem i potvrđujem da znam koji novčanik trebam da koristim.
account.altcoin.popup.xmr.msg=If you want to trade XMR on Bisq please be sure you understand and fulfill the following requirements:\n\nFor sending XMR you need to use either the official Monero GUI wallet or Monero CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nmonero-wallet-cli (use the command get_tx_key)\nmonero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nIn addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\nmonero-wallet-cli : using command (check_tx_key).\nmonero-wallet-gui : on the Advanced > Prove/Check page.\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the 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\nIf you cannot provide the above data or if you used an incompatible wallet it would result in losing the dispute case. The XMR sender is responsible to be able to verify the XMR 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 (https://www.getmonero.org/resources/user-guides/prove-payment.html) or the Monero forum (https://forum.getmonero.org) to find more information.
account.altcoin.popup.blur.msg=If you want to trade BLUR on Bisq please be sure 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 arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nIf you cannot provide the required information to the arbitrator, you will lose the dispute. In all cases of dispute, the BLUR sender bears 100% of the burden of responsiblity in verifying transactions to an arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW).
account.altcoin.popup.ccx.msg=If you want to trade CCX on Bisq please be sure you understand the following requirements:\n\nTo send CCX you must use an official Conceal wallet, either CLI or GUI. After sending a transfer payment, the wallets\ndisplay the transaction secret key. You must save it along with the transaction hash (ID) and the recipient's public\naddress in case arbitration is necessary. In such a case, you must give all three to the arbitrator, who will then\nverify the CCX transfer using the Conceal Transaction Viewer (https://explorer.conceal.network/txviewer).\nBecause Conceal is a privacy coin, block explorers cannot verify transfers.\n\nIf you cannot provide the required data to the arbitrator, you will lose the dispute case.\nIf you do not save the transaction secret key immediately after transferring CCX, it cannot be recovered later.\nIf you do not understand these requirements, seek help at the Conceal discord (http://discord.conceal.network).
account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides a transaction is not verifyable on the public blockchain. If required you can prove your payment thru use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at \ (http://drgl.info/#check_txn).\n\nIf you cannot provide the above data or if you used an incompatible wallet it would result in losing the dispute case. The Dragonglass sender is responsible to be able to verify the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help.
account.altcoin.popup.xmr.msg=Trading XMR on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending XMR, you need to use either the official Monero GUI wallet or Monero CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nmonero-wallet-cli (use the command get_tx_key)\nmonero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nIn addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\nmonero-wallet-cli : using command (check_tx_key).\nmonero-wallet-gui : on the Advanced > Prove/Check page.\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The XMR sender is responsible for providing verification of the XMR transfer to the arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) or the Monero forum (https://forum.getmonero.org) to find more information.
account.altcoin.popup.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 arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The 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 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 arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW).
account.altcoin.popup.ccx.msg=Trading CCX on Bisq requires that you understand the following requirements:\n\nTo send CCX you must use an official Conceal wallet, either CLI or GUI. After sending a transfer payment, the wallets\ndisplay the transaction secret key. You must save it along with the transaction hash (ID) and the recipient's public\naddress in case arbitration is necessary. In such a case, you must give all three to the arbitrator, who will then\nverify the CCX transfer using the Conceal Transaction Viewer (https://explorer.conceal.network/txviewer).\nBecause Conceal is a privacy coin, block explorers cannot verify transfers.\n\nFailure to provide the required data to the arbitrator will result in losing the dispute case.\nIf you do not save the transaction secret key immediately after transferring CCX, it cannot be recovered later.\nIf you do not understand these requirements, seek help at the Conceal discord (http://discord.conceal.network).
account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides, a transaction is not verifiable on the public blockchain. If required, you can prove your payment through the use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at (http://drgl.info/#check_txn).\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The Dragonglass sender is responsible for providing verification of the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help.
account.altcoin.popup.ZEC.msg=Tokom korišćenja {0} možete koristiti samo transparentne adrese (počinju sa t) a ne z-adrese (privatne), jer arbitar ne bi bio u stanju da proveri transakciju sa z-adresom.
account.altcoin.popup.XZC.msg=When using {0} you can only use the transparent (traceable) addresses not the untraceable addresses, because the arbitrator would not be able to verify the transaction with untraceable addresses at a block explorer.
account.altcoin.popup.bch=Bitcoin Cash and Bitcoin Clashic suffer from replay protection. If you use those coins be sure you take sufficient precautions and understand all implications.You can suffer losses by sending one coin and unintentionally send the same coins on the other block chain.Because those "airdrop coins" share the same history with the Bitcoin blockchain there are also security risks and a considerable risk for losing privacy.\n\nPlease read at the Bisq Forum more about that topic: https://forum.bisq.io/t/airdrop-coins-information-thread-bch-btg-bchc
@ -1306,7 +1308,7 @@ dao.burnBsq.assets.lookBackPeriod=Verification period
dao.burnBsq.assets.trialFee=Fee for trial period
dao.burnBsq.assets.totalFee=Total fees paid
dao.burnBsq.assets.days={0} days
dao.burnBsq.assets.toFewDays=The asset fee is too low. The min. amount of days for the trial perios is {0}.
dao.burnBsq.assets.toFewDays=The asset fee is too low. The min. amount of days for the trial period is {0}.
# suppress inspection "UnusedProperty"
dao.assetState.UNDEFINED=Undefined
@ -1584,7 +1586,7 @@ displayUpdateDownloadWindow.verify.failed=Verification failed.\nPlease download
displayUpdateDownloadWindow.success=The new version has been successfully downloaded and the signature(s) verified.\n\nPlease open the download directory, shut down the application and install the new version.
displayUpdateDownloadWindow.download.openDir=Open download directory
disputeRezimeWindow.title=Rezime
disputeSummaryWindow.title=Rezime
disputeSummaryWindow.openDate=Ticket opening date
disputeSummaryWindow.role=Trader's role
disputeSummaryWindow.evidence=Evidence
@ -1746,7 +1748,7 @@ popup.headline.error=Greška
popup.doNotShowAgain=Ne prikazuj opet
popup.reportError.log=Open log file
popup.reportError.gitHub=Prijavi Github pratiocu problema
popup.reportError={0}\n\nTo help us to improve the software please report the bug on our issue tracker on GitHub (https://github.com/bisq-network/bisq-desktop/issues).\nThe error message will be copied to the clipboard when you click a button below.\nIt will make debugging easier if you can attach the bisq.log file as well.
popup.reportError={0}\n\nTo help us to improve the software please report this bug by opening a new issue at https://github.com/bisq-network/bisq/issues.\nThe above error message will be copied to the clipboard when you click either of the buttons below.\nIt will make debugging easier if you include the bisq.log file by pressing "Open log file", saving a copy, and attaching it to your bug report.
popup.error.tryRestart=Molimo pokušajte da ponovo pokrenete vašu aplikaciju i proverite vašu mrežnu konekciju da vidite da li možete da rešite problem.
popup.error.takeOfferRequestFailed=An error occurred when someone tried to take one of your offers:\n{0}
@ -1805,6 +1807,9 @@ popup.attention.forTradeWithId=Potrebna pažnja za trgovinu sa ID {0}
popup.roundedFiatValues.headline=New privacy feature: Rounded fiat values
popup.roundedFiatValues.msg=To increase privacy of your trade the {0} amount was rounded.\n\nDepending on the client version you''ll pay or receive either values with decimals or rounded ones.\n\nBoth values do comply from now on with the trade protocol.\n\nAlso be aware that BTC values are changed automatically to match the rounded fiat amount as close as possible.
popup.info.multiplePaymentAccounts.headline=Multiple payment accounts available
popup.info.multiplePaymentAccounts.msg=You have multiple payment accounts available for this offer. Please make sure you've picked the right one.
####################################################################
# Notifications
@ -2085,7 +2090,7 @@ payment.clearXchange.info=Please be sure that you fulfill the requirements for t
payment.moneyGram.info=When using MoneyGram the BTC buyer has to send the Authorisation number and a photo of the receipt by email to the BTC seller. The receipt must clearly show the seller's full name, country, state and the amount. The buyer will get displayed the seller's email in the trade process.
payment.westernUnion.info=When using Western Union the BTC buyer has to send the MTCN (tracking number) and a photo of the receipt by email to the BTC seller. The receipt must clearly show the seller's full name, city, country and the amount. The buyer will get displayed the seller's email in the trade process.
payment.halCash.info=When using HalCash the BTC buyer need to send the BTC seller the HalCash code via a text message from the mobile phone.\n\nPlease make sure to not exceed the maximum amount your bank allows you to send with HalCash. The min. amount per withdrawal is 10 EUR and the max. amount is 600 EUR. For repeated withdrawals it is 3000 EUR per receiver per day and 6000 EUR per receiver per month. Please cross check those limits with your bank to be sure they use the same limits as stated here.\n\nThe withdrawal amount must be a multiple of 10 EUR as you cannot withdraw other amounts from an ATM. The UI in the create-offer and take-offer screen will adjust the BTC amount so that the EUR amount is correct. You cannot use market based price as the EUR amount would be changing with changing prices.\n\nIn case of a dispute the BTC buyer need to provide the proof that he sent the EUR.
payment.halCash.info=When using HalCash the BTC buyer needs to send the BTC seller the HalCash code via a text message from their mobile phone.\n\nPlease make sure to not exceed the maximum amount your bank allows you to send with HalCash. The min. amount per withdrawal is 10 EUR and the max. amount is 600 EUR. For repeated withdrawals it is 3000 EUR per receiver per day and 6000 EUR per receiver per month. Please cross check those limits with your bank to be sure they use the same limits as stated here.\n\nThe withdrawal amount must be a multiple of 10 EUR as you cannot withdraw other amounts from an ATM. The UI in the create-offer and take-offer screen will adjust the BTC amount so that the EUR amount is correct. You cannot use market based price as the EUR amount would be changing with changing prices.\n\nIn case of a dispute the BTC buyer needs to provide the proof that they sent the EUR.
payment.limits.info=Please be aware that all bank transfers carry a certain amount of chargeback risk.\n\nTo mitigate this risk, Bisq sets per-trade limits based on two factors:\n\n1. The estimated level of chargeback risk for the payment method used\n2. The age of your account for that payment method\n\nThe account you are creating now is new and its age is zero. As your account grows in age over a two-month period, your per-trade limits will grow along with it:\n\n● During the 1st month, your per-trade limit will be {0}\n● During the 2nd month, your per-trade limit will be {1}\n● After the 2nd month, your per-trade limit will be {2}\n\nPlease note that there are no limits on the total number of times you can trade.
payment.cashDeposit.info=Please confirm your bank allows you to send cash deposits into other peoples' accounts. For example, Bank of America and Wells Fargo no longer allow such deposits.
@ -2098,7 +2103,7 @@ payment.f2f.optionalExtra=Optional additional information
payment.f2f.extra=Additional information
payment.f2f.extra.prompt=The maker can define 'terms and conditions' or add a public contact information. It will be displayed with the offer.
payment.f2f.info='Face to Face' trades have different rules and come with different risks than online transactions.\n\nThe main differences are:\n● The trading peers need to exchange information about the meeting location and time by using their provided contact details.\n● The trading peers need to bring their laptops and do the confirmation of 'payment sent' and 'payment received' at the meeting place.\n● If a maker has special 'terms and conditions' he needs to state those in the 'Addition information' text field in the account.\n● By taking an offer the taker agrees to the maker's stated 'terms and conditions'.\n● In case of a dispute the arbitrator cannot help much as it is usually hard to get tamper proof evidence of what happened at the meeting. In such cases the BTC funds might get locked indefinitely or until the trading peers come to an agreement.\n\nTo be sure you fully understand the differences with 'Face to Face' trades please read the instructions and recommendations at: 'https://docs.bisq.network/trading-rules.html#f2f-trading'
payment.f2f.info='Face to Face' trades have different rules and come with different risks than online transactions.\n\nThe main differences are:\n● The trading peers need to exchange information about the meeting location and time by using their provided contact details.\n● The trading peers need to bring their laptops and do the confirmation of 'payment sent' and 'payment received' at the meeting place.\n● If a maker has special 'terms and conditions' they must state those in the 'Additional information' text field in the account.\n● By taking an offer the taker agrees to the maker's stated 'terms and conditions'.\n● In case of a dispute the arbitrator cannot help much as it is usually hard to get tamper proof evidence of what happened at the meeting. In such cases the BTC funds might get locked indefinitely or until the trading peers come to an agreement.\n\nTo be sure you fully understand the differences with 'Face to Face' trades please read the instructions and recommendations at: 'https://docs.bisq.network/trading-rules.html#f2f-trading'
payment.f2f.info.openURL=Open web page
payment.f2f.offerbook.tooltip.countryAndCity=County and city: {0} / {1}
payment.f2f.offerbook.tooltip.extra=Additional information: {0}

509
core/src/main/resources/i18n/displayStrings_th.properties
View file

File diff suppressed because it is too large Load diff

47
core/src/main/resources/i18n/displayStrings_vi.properties
View file

@ -217,7 +217,7 @@ mainView.menu.dao=DAO
mainView.marketPrice.provider=Giá theo
mainView.marketPrice.label=Giá thị trường
mainView.marketPriceWithProvider.label=Giá thị trường theo {0}
mainView.marketPriceWithProvider.label=Giá thị trường theo {0}
mainView.marketPrice.bisqInternalPrice=Giá giao dịch Bisq gần nhất
mainView.marketPrice.tooltip.bisqInternalPrice=Không có giá thị trường từ nhà cung cấp bên ngoài.\nGiá hiển thị là giá giao dịch Bisq gần nhất với đồng tiền này.
mainView.marketPrice.tooltip=Giá thị trường được cung cấp bởi {0}{1}\nCập nhật mới nhất: {2}\nURL nút nhà cung cấp: {3}
@ -299,6 +299,8 @@ market.trades.tooltip.candle.date=Ngày:
offerbook.createOffer=Tạo chào giá
offerbook.takeOffer=Nhận chào giá
offerbook.takeOfferToBuy=Take offer to buy {0}
offerbook.takeOfferToSell=Take offer to sell {0}
offerbook.trader=Trader
offerbook.offerersBankId=ID ngân hàng của người tạo (BIC/SWIFT): {0}
offerbook.offerersBankName=Tên ngân hàng của người tạo: {0}
@ -441,7 +443,7 @@ takeOffer.takeOfferFundWalletInfo.msg=Bạn cần nộp {0} để nhận báo gi
takeOffer.alreadyPaidInFunds=Bạn đã thanh toán, bạn có thể rút số tiền này tại màn hình \"Vốn/Gửi vốn\".
takeOffer.paymentInfo=Thông tin thanh toán
takeOffer.setAmountPrice=Cài đặt số tiền
takeOffer.alreadyFunded.askCancel=Bạn đã nộp tiền cho chào giá này.\nNếu bạn hủy bây giờ, số tiền của bạn sẽ được chuyển sang ví Bisq nội bộ của bạn và sẵn sàng để rút tại màn hình \Màn hình "Vốn/Gửi vốn\".\nBạn có chắc muốn hủy?
takeOffer.alreadyFunded.askCancel=Bạn đã nộp tiền cho chào giá này.\nNếu bạn hủy bây giờ, số tiền của bạn sẽ được chuyển sang ví Bisq nội bộ của bạn và sẵn sàng để rút tại màn hình Màn hình \"Vốn/Gửi vốn\".\nBạn có chắc muốn hủy?
takeOffer.failed.offerNotAvailable=Nhận yêu cầu chào giá không thành công do chào giá không còn tồn tại. Có thể trong lúc chờ đợi, Thương gia khác đã nhận chào giá này.
takeOffer.failed.offerTaken=Bạn không thể nhận chào giá này vì đã được nhận bởi Thương gia khác.
takeOffer.failed.offerRemoved=Bạn không thể nhận chào giá này vì trong lúc chời đợi, chào giá này đã bị gỡ bỏ.
@ -528,7 +530,7 @@ portfolio.pending.step2_buyer.westernUnionMTCNInfo.headline=Gửi MTCN và biên
portfolio.pending.step2_buyer.westernUnionMTCNInfo.msg=Bạn cần phải gửi MTCN (số theo dõi) và ảnh chụp giấy biên nhận bằng email cho người bán BTC.\nGiấy biên nhận phải nêu rõ họ tên, thành phố, quốc gia của người bán và số tiền. Địa chỉ email của người bán là: {0}.\n\nBạn đã gửi MTCN và hợp đồng cho người bán chưa?
portfolio.pending.step2_buyer.halCashInfo.headline=Gửi mã HalCash
portfolio.pending.step2_buyer.halCashInfo.msg=Bạn cần nhắn tin mã HalCash và mã giao dịch ({0}) tới người bán BTC. \nSố điện thoại của người bán là {1}.\n\nBạn đã gửi mã tới người bán chưa?
portfolio.pending.step2_buyer.fasterPaymentsHolderNameInfo=Một số ngân hàng có thể yêu cầu tên người nhận. Mã phân loại của Vương Quốc Anh và số tài khoản là đủ cho một giao dịch Chuyển Tiền Nhanh và tên người nhận không được ngân hàng nào xác minh.
portfolio.pending.step2_buyer.fasterPaymentsHolderNameInfo=Một số ngân hàng có thể yêu cầu tên người nhận. Mã phân loại của Vương Quốc Anh và số tài khoản là đủ cho một giao dịch Chuyển Tiền Nhanh và tên người nhận không được ngân hàng nào xác minh.
portfolio.pending.step2_buyer.confirmStart.headline=Xác nhận rằng bạn đã bắt đầu thanh toán
portfolio.pending.step2_buyer.confirmStart.msg=Bạn đã kích hoạt thanh toán {0} cho Đối tác giao dịch của bạn chưa?
portfolio.pending.step2_buyer.confirmStart.yes=Có, tôi đã bắt đầu thanh toán
@ -560,12 +562,12 @@ portfolio.pending.step3_buyer.warn.part1b=tại nhà cung cấp thanh toán củ
portfolio.pending.step3_buyer.warn.part2=Người bán BTC vẫn chưa xác nhận thanh toán của bạn!\nHãy kiểm tra xem {0} việc gửi thanh toán đi đã thành công chưa.\nNếu người bán BTC không xác nhận là đã nhận thanh toán của bạn trước {1} giao dịch sẽ bị điều tra bởi trọng tài.
portfolio.pending.step3_buyer.openForDispute=Người bán BTC vẫn chưa xác nhận thanh toán của bạn!\nThời gian tối đa cho giao dịch đã hết.\nBạn có thể đợi lâu hơn và cho đối tác giao dịch thêm thời gian hoặc liên hệ trọng tài để mở khiếu nại.
# suppress inspection "TrailingSpacesInProperty"
portfolio.pending.step3_seller.part=Đối tác giao dịch của bạn đã xác nhận rằng đã kích hoạt thanh toán {0}.\n\n
portfolio.pending.step3_seller.part=Your trading partner has confirmed that they have initiated the {0} payment.\n\n
portfolio.pending.step3_seller.altcoin.explorer=Trên trình duyệt blockchain explorer {0} ưa thích của bạn
portfolio.pending.step3_seller.altcoin.wallet=Trên ví {0} của bạn
portfolio.pending.step3_seller.altcoin={0}Vui lòng kiểm tra {1} xem giao dịch tới địa chỉ nhận của bạn \n{2}\nđã nhận được đủ xác nhận blockchain hay chưa.\nSố tiền thanh toán phải là {3}\n\nBạn có thể copy & paste địa chỉ {4} của bạn từ màn hình chính sau khi đóng cửa sổ này.
portfolio.pending.step3_seller.postal={0}Hãy kiểm tra xem bạn đã nhận được {1} \"Thư chuyển tiền US\" từ người mua BTC chưa.\n\nID giao dịch (nội dung \"lý do thanh toán\") của giao dịch là: \"{2}\"
portfolio.pending.step3_seller.bank=Đối tác giao dịch của bạn đã xác nhận rằng đã kích hoạt thanh toán {0}.\n\nHãy truy cập trang web ngân hàng online và kiểm tra xem bạn đã nhận được {1} từ người mua BTC chưa.\n\nID giao dịch (\"lý do thanh toán\" text) của giao dịch là: \"{2}\"
portfolio.pending.step3_seller.bank=Your trading partner has confirmed that they have initiated the {0} payment.\n\nPlease go to your online banking web page and check if you have received {1} from the BTC buyer.\n\nThe trade ID (\"reason for payment\" text) of the transaction is: \"{2}\"\n\n
portfolio.pending.step3_seller.cash=Vì thanh toán được thực hiện qua Tiền gửi tiền mặt nên người mua BTC phải viết rõ \"KHÔNG HOÀN LẠI\" trên giấy biên nhận, xé làm 2 phần và gửi ảnh cho bạn qua email.\n\nĐể tránh bị đòi tiền lại, chỉ xác nhận bạn đã nhận được email và bạn chắc chắn giấy biên nhận là có hiệu lực.\nNếu bạn không chắc chắn, {0}
portfolio.pending.step3_seller.moneyGram=Người mua phải gửi mã số xác nhận và ảnh chụp của hoá đơn qua email.\nHoá đơn cần ghi rõ họ tên đầy đủ, quốc gia, tiêu bang và số lượng. Vui lòng kiểm tra email nếu bạn nhận được số xác thực.\n\nSau khi popup đóng, bạn sẽ thấy tên người mua BTC và địa chỉ để nhận tiền từ MoneyGram.\n\nChỉ xác nhận hoá đơn sau khi bạn hoàn thành việc nhận tiền.
portfolio.pending.step3_seller.westernUnion=Người mua phải gửi cho bạn MTCN (số theo dõi) và ảnh giấy biên nhận qua email.\nGiấy biên nhận phải ghi rõ họ tên của bạn, thành phố, quốc gia và số tiền. Hãy kiểm tra email xem bạn đã nhận được MTCN chưa.\n\nSau khi đóng cửa sổ này, bạn sẽ thấy tên và địa chỉ của người mua BTC để nhận tiền từ Western Union.\n\nChỉ xác nhận giấy biên nhận sau khi bạn đã nhận tiền thành công!
@ -620,7 +622,7 @@ portfolio.pending.step5_seller.received=Bạn đã nhận
tradeFeedbackWindow.title=Chúc mừng giao dịch của bạn được hoàn thành.
tradeFeedbackWindow.msg.part1=Chúng tôi rất vui lòng được nghe phản hồi của bạn. Điều đó sẽ giúp chúng tôi cải thiện phần mềm và hoàn thiện trải nghiệm người dùng. Nếu bạn muốn cung cấp phản hồi, vui lòng điền vào cuộc khảo sát ngắn dưới đây (không yêu cầu đăng nhập) ở:
tradeFeedbackWindow.msg.part2=nếu bạn có câu hỏi hay vấn đề, vui lòng liên hệ với người dùng khác và các nhàn đóng góp qua Bisq forum ở:
tradeFeedbackWindow.msg.part2=nếu bạn có câu hỏi hay vấn đề, vui lòng liên hệ với người dùng khác và các nhàn đóng góp qua Bisq forum ở:
tradeFeedbackWindow.msg.part3=Cám ơn bạn đã sử dụng Bisq!
portfolio.pending.role=Vai trò của tôi
@ -829,7 +831,7 @@ settings.net.onionAddressLabel=Địa chỉ onion của tôi
settings.net.btcNodesLabel=Sử dụng nút Bitcoin Core thông dụng
settings.net.bitcoinPeersLabel=Các đối tác được kết nối
settings.net.useTorForBtcJLabel=Sử dụng Tor cho mạng Bitcoin
settings.net.bitcoinNodesLabel=nút Bitcoin Core để kết nối
settings.net.bitcoinNodesLabel=nút Bitcoin Core để kết nối
settings.net.useProvidedNodesRadio=Sử dụng các nút Bitcoin Core đã cung cấp
settings.net.usePublicNodesRadio=Sử dụng mạng Bitcoin công cộng
settings.net.useCustomNodesRadio=Sử dụng nút Bitcoin Core thông dụng
@ -926,10 +928,10 @@ account.arbitratorSelection.minOne=Bạn cần có ít nhất một trọng tài
account.altcoin.yourAltcoinAccounts=Tài khoản altcoin của bạn
account.altcoin.popup.wallet.msg=Please be sure that you follow the requirements for the usage of {0} wallets as described on the {1} web page.\nUsing wallets from centralized exchanges where (a) you don''t control your keys or (b) which don''t use compatible wallet software is risky: it can lead to loss of the traded funds!\nThe arbitrator is not a {2} specialist and cannot help in such cases.
account.altcoin.popup.wallet.confirm=Tôi hiểu và xác nhận rằng tôi đã biết loại ví mình cần sử dụng.
account.altcoin.popup.xmr.msg=Nếu bạn muốn giao dịch XMR trên Bisq, hãy chắc chắn bạn hiểu và tuân thủ các yêu cầu sau:\n\nĐể gửi XMR, bạn cần sử dụng hoặc là ví Monero GUI chính thức hoặc ví Monero CLI với nhãn luu-thongtin-tx được kích hoạt (mặc định trong phiên bản mới). Chắc chắn rằng bạn có thể truy cập khóa tx vì điều này là cần thiết trong trường hợp khiếu nại.\nví-monero-cli (dùng lệnh get_tx_key) \nví-monero-gui (đi đến tab lịch sử và nhấp vào nút (P) để lấy bằng chứng thanh toán)\n\nNgoài công cụ kiểm tra giao dịch XMR (https://xmr.llcoins.net/checktx.html) việc xác minh cũng có thể được thực hiện ngay trên ví.\nví-monero-cli: dùng lệnh (check_tx_key).\nví-monero-gui: ở trên Nâng cao>trang Chứng minh/Kiểm tra.\nVới những block explorer thông thường, chuyển khoản không thể xác minh được.\n\nBạn cần cung cấp cho trọng tài các dữ liệu sau trong trường hợp khiếu nại:\n- Khóa tx riêng\n- Hash của giao dịch\n- Địa chỉ công cộng của người nhận\n\nNếu bạn không thể cung cấp các dữ liệu trên hoặc nếu bạn sử dụng ví không thích hợp sẽ dẫn tới thua trong vụ khiếu nại. Người gửi XMR chịu trách nhiệm xác minh chuyển khoản XMR cho trọng tài trong trường hợp khiếu nại.\n\nKhông có ID thanh toán cầu thiết, chỉ là địa chỉ công cộng thông thường.\nNếu bạn không chắc chắn về quá trình, truy cập (https://www.getmonero.org/resources/user-guides/prove-payment.html) hoặc diễn đàn Monero (https://forum.getmonero.org) để tìm thêm thông tin.
account.altcoin.popup.blur.msg=Nếu bạn muốn giao dịch BLUR trên Bisq, hãy chắc chắn bạn hiểu và tuân thủ các yêu cầu sau:\n\nĐể gửi BLUR, bạn cần sử dụng ví CLI hoặc GUI của mạng BLUR. \n\nNếu bạn sử dụng ví CLI, sau khi chuyển tiền, ví sẽ hiển thị một mã giao dịch (tx ID). Bạn phải lưu thông tin này lại. Ngay sau khi chuyển tiền, bạn phải dùng lệnh 'get_tx_key' để lấy khóa riêng của giao dịch. Nếu bạn không thực hiện bước này, rất có thể sau này bạn sẽ không lấy được khóa giao dịch nữa. \n\nNếu bạn sử dụng ví GUI của mạng BLUR, khóa riêng giao dịch và tx ID sẽ được hiển thị ngay trên tab "Lịch sử". Ngay sau khi chuyển tiền, xác định vị trí của giao dịch mà bạn quan tâm. Nhấp chuột vào biểu tượng "?" ở góc phải bên dưới của hộp chứa giao dịch. Bạn cần phải lưu thông tin này lại. \n\nTrường hợp tranh chấp, bạn phải đưa ra cho trọng tài những thông tin sau:1.) mã giao dịch, 2.) khóa riêng của giao dịch, 3.) địa chỉ ví của người nhận. Trọng tài lúc đó sẽ sử dụng Blur Transaction Viewer (https://blur.cash/#tx-viewer) để xác minh giao dịch chuyển BLUR .\n\nNếu bạn không thể cung cấp các thông tin yêu cầu, bạn sẽ thua trong lần tranh chấp này. Trong tất cả mọi trường hợp tranh chấp, người chuyển BLUR chịu 100% trách nhiệm xác minh giao dịch với trọng tài.\n\nNếu bạn vẫn chưa hiểu rõ về những yêu cầu này, vui lòng vào Discord của BLUR (https://discord.gg/dMWaqVW) để được hỗ trợ.
account.altcoin.popup.ccx.msg=Nếu bạn muốn giao dịch CCX trên Bisq, hãy chắc chắn bạn hiểu các yêu cầu sau:\n\nĐể gửi CCX, bạn cần phải sử dụng ví chính thức của Conceal, ví CLI hay GUI đều được. Sau khi chuyển tiền, ví \nsẽ hiển thị khóa bí mật của giao dịch. Bạn phải lưu khóa bí mật này lại cùng với mã giao dịch (tx ID) và địa chỉ ví công khai \ncủa người nhận phòng khi có tranh chấp. Trường hợp có tranh chấp, bạn phải cung cấp cả ba thông tin này cho trọng tài , sau đó trọng tài sẽ dùng Conceal Transaction Viewer \n(https://explorer.conceal.network/txviewer).\nVì Conceal là một đồng coin riêng tư, nên các trang dò khối sẽ không thể xác minh giao dịch chuyển tiền.\n\nNếu bạn không thể cung cấp các thông tin yêu cầu cho trọng tài, bạn sẽ thua trong lần tranh chấp này.\nNếu bạn không lưu lại khóa giao dịch bí mật ngay sau khi thực hiện chuyển CCX, sau này bạn sẽ không lấy lại được nữa.\nNếu bạn vẫn chưa hiểu rõ về những yêu cầu này, vui lòng vào Discord của Conceal (http://discord.conceal.network) để được hỗ trợ.
account.altcoin.popup.drgl.msg=Để giao dịch Dragonglass trên Bisq, bạn cần phải hiểu và tuân thủ các yêu cầu sau:\n\nĐể đảm bảo tính riêng tư, những giao dịch do Dragonglass cung cấp không thể xác minh bằng blockchain công cộng. Nếu được yêu cầu, bạn có thể chứng minh giao dịch thanh toán của bạn bằng cách sử dụng khóa-riêng-TXN.\nKhóa riêng-TXN là khóa dùng một lần được tạo tự động cho mỗi giao dịch và chỉ có thể truy cập thông qua ví DRGL của bạn. \nDù là giao dịch được thực hiện trên ví DRGL GUI (trong hội thoại chi tiết giao dịch) hay bằng ví giản đơn Dragonglass CLI (dùng lệnh "get_tx_key"), thì đều cần phải có phiên bản Dragonglass 'Oathkeeper' hoặc cao hơn.\n\nTrường hợp tranh chấp, bạn cần phải cung cấp cho trọng tài những dữ liệu sau:\n- Khóa riêng-TXN\n- Mã giao dịch\n- Địa chỉ công cộng của người nhận\n\nViệc xác minh có thể được thực hiện bằng cách sử dụng những thông tin ở trên làm dữ liệu nhập tại \(http://drgl.info/#check_txn).\n\nNếu bạn không cung cấp được các thông tin trên, hoặc nếu bạn sử dụng một ví không hợp lệ, điều này có thể khiến bạn thua trong lần tranh chấp này. Người gửi Dragonglass chịu trách nhiệm xác minh giao dịch chuyển DRGL cho trọng tài trong trường hợp có tranh chấp. Việc sử dụng PaymentID không được yêu cầu. \n\nNếu như bạn vẫn chưa chắc chắn về bất cứ phần nào trong quá trình này,liên hệ Dragonglass trên Discord (http://discord.drgl.info) để được hỗ trợ.
account.altcoin.popup.xmr.msg=Trading XMR on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending XMR, you need to use either the official Monero GUI wallet or Monero CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nmonero-wallet-cli (use the command get_tx_key)\nmonero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nIn addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\nmonero-wallet-cli : using command (check_tx_key).\nmonero-wallet-gui : on the Advanced > Prove/Check page.\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The XMR sender is responsible for providing verification of the XMR transfer to the arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) or the Monero forum (https://forum.getmonero.org) to find more information.
account.altcoin.popup.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 arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The 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 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 arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW).
account.altcoin.popup.ccx.msg=Trading CCX on Bisq requires that you understand the following requirements:\n\nTo send CCX you must use an official Conceal wallet, either CLI or GUI. After sending a transfer payment, the wallets\ndisplay the transaction secret key. You must save it along with the transaction hash (ID) and the recipient's public\naddress in case arbitration is necessary. In such a case, you must give all three to the arbitrator, who will then\nverify the CCX transfer using the Conceal Transaction Viewer (https://explorer.conceal.network/txviewer).\nBecause Conceal is a privacy coin, block explorers cannot verify transfers.\n\nFailure to provide the required data to the arbitrator will result in losing the dispute case.\nIf you do not save the transaction secret key immediately after transferring CCX, it cannot be recovered later.\nIf you do not understand these requirements, seek help at the Conceal discord (http://discord.conceal.network).
account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides, a transaction is not verifiable on the public blockchain. If required, you can prove your payment through the use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at (http://drgl.info/#check_txn).\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The Dragonglass sender is responsible for providing verification of the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help.
account.altcoin.popup.ZEC.msg=Khi sử dụng {0} bạn chỉ có thể sử dụng địa chỉ rõ ràng (bắt đầu bằng t) không phải địa chỉ z (riêng tư), vì trọng tài sẽ không thể xác minh giao dịch với địa chỉ z.
account.altcoin.popup.XZC.msg=Khi sử dụng {0} bạn chỉ có thể sử dụng địa chỉ rõ ràng (có thể theo dõi) chứ không phải địa chỉ không thể theo dõi, vì trọng tài không thể xác minh giao dịch với địa chỉ không thể theo dõi tại một block explorer.
account.altcoin.popup.bch=Bitcoin Cash và Bitcoin Clashic được bảo vệ không chào lại. Nếu bạn sử dụng các coin này, phải chắc chắn bạn đã thực hiện đủ biện pháp phòng ngừa và hiểu rõ tất cả nội dung. Bạn có thể bị mất khi gửi một coin và vô tình gửi coin như vậy cho block chain khác. Do các "airdrop coins" này có cùng lịch sử với Bitcoin blockchain do đó có một số nguy cơ mất an toàn và quyền riêng tư.\n\nVui lòng đọc tại diễn đàn Bisq để biết thêm về chủ đề này: https://forum.bisq.io/t/airdrop-coins-information-thread-bch-btg-bchc
@ -1306,7 +1308,7 @@ dao.burnBsq.assets.lookBackPeriod=Giai đoạn xác minh
dao.burnBsq.assets.trialFee=Phí cho giai đoạn dùng thử
dao.burnBsq.assets.totalFee=Tổng số phí đã trả
dao.burnBsq.assets.days={0} ngày
dao.burnBsq.assets.toFewDays=Phí tài sản quá thấp. Số ngày tối thiểu cho giai đoạn dùng thử là {0}.
dao.burnBsq.assets.toFewDays=The asset fee is too low. The min. amount of days for the trial period is {0}.
# suppress inspection "UnusedProperty"
dao.assetState.UNDEFINED=Không xác định
@ -1322,7 +1324,7 @@ dao.assetState.REMOVED_BY_VOTING=Bị gỡ bỏ thông qua bỏ phiếu
dao.proofOfBurn.header=Bằng chứng đốt
dao.proofOfBurn.amount=Số tiền
dao.proofOfBurn.preImage=Pre-image
dao.proofOfĐốt.burn=Đốt
dao.proofOfBurn.burn=Đốt
dao.proofOfBurn.allTxs=Tất cả bằng chứng của các giao dịch đốt
dao.proofOfBurn.myItems=Bằng chứng giao dịch đốt của tôi
dao.proofOfBurn.date=Ngày
@ -1400,7 +1402,7 @@ dao.proposal.type.short.CONFISCATE_BOND=Tịch thu tài sản đảm bảo
dao.proposal.details=Thông tin về đề xuất
dao.proposal.selectedProposal=Đề xuất được chọn
dao.proposal.active.header=Các đề xuất có hiệu lực
dao.proposal.active.remove.confirm=Bạn có chắc bạn muốn gỡ bỏ đề xuất này?\nPhí đề xuất đã trả sẽ bị mất.
dao.proposal.active.remove.confirm=Bạn có chắc bạn muốn gỡ bỏ đề xuất này?\nPhí đề xuất đã trả sẽ bị mất.
dao.proposal.active.remove.doRemove=Vâng, xin hãy gở đề xuất của tôi
dao.proposal.active.remove.failed=Không thể gỡ bỏ đề xuất.
dao.proposal.myVote.accept=Chấp nhận đề xuất
@ -1562,7 +1564,7 @@ contractWindow.title=Thông tin khiếu nại
contractWindow.dates=Ngày chào giá / Ngày giao dịch
contractWindow.btcAddresses=Địa chỉ Bitcoin người mua BTC / người bán BTC
contractWindow.onions=Địa chỉ mạng người mua BTC / người bán BTC
contractWindow.numDisputes=Số khiếu nại người mua BTC / người bán BTC
contractWindow.numDisputes=Số khiếu nại người mua BTC / người bán BTC
contractWindow.contractHash=Hash của hợp đồng
displayAlertMessageWindow.headline=Thông tin quan trọng!
@ -1746,7 +1748,7 @@ popup.headline.error=Lỗi
popup.doNotShowAgain=Không hiển thị lại
popup.reportError.log=Mở log file
popup.reportError.gitHub=Báo cáo cho người theo dõi vấn đề GitHub
popup.reportError={0}\n\nTo help us to improve the software please report the bug on our issue tracker on GitHub (https://github.com/bisq-network/bisq-desktop/issues).\nThe error message will be copied to the clipboard when you click a button below.\nIt will make debugging easier if you can attach the bisq.log file as well.
popup.reportError={0}\n\nTo help us to improve the software please report this bug by opening a new issue at https://github.com/bisq-network/bisq/issues.\nThe above error message will be copied to the clipboard when you click either of the buttons below.\nIt will make debugging easier if you include the bisq.log file by pressing "Open log file", saving a copy, and attaching it to your bug report.
popup.error.tryRestart=Hãy khởi động lại ứng dụng và kiểm tra kết nối mạng để xem bạn có thể xử lý vấn đề này hay không.
popup.error.takeOfferRequestFailed=Có lỗi xảy ra khi ai đó cố gắng để nhận một trong các chào giá của bạn:\n{0}
@ -1787,7 +1789,7 @@ popup.info.securityDepositInfo=To ensure both traders follow the trade protocol,
popup.info.cashDepositInfo=Chắc chắn rằng khu vực của bạn có chi nhánh ngân hàng có thể gửi tiền mặt.\nID (BIC/SWIFT) ngân hàng của bên bán là: {0}.
popup.info.cashDepositInfo.confirm=Tôi xác nhận tôi đã gửi tiền
popup.info.shutDownWithOpenOffers=Bisq đang đóng, nhưng vẫn có các chào giá đang mở. \n\nNhững chào giá này sẽ không có tại mạng P2P khi Bisq đang đóng, nhưng chúng sẽ được công bố lại trên mạng P2P vào lần tiếp theo bạn khởi động Bisq.\nĐể giữ các chào giá luôn trực tuyến, vui lòng để Bisq chạy và đảm bảo là máy tính của bạn cũng đang trực tuyến(có nghĩa là đảm bảo là máy tính của bạn không chuyển về chế độ chờ...nếu màn hình về chế độ chờ thì không sao).
popup.info.shutDownWithOpenOffers=Bisq đang đóng, nhưng vẫn có các chào giá đang mở. \n\nNhững chào giá này sẽ không có tại mạng P2P khi Bisq đang đóng, nhưng chúng sẽ được công bố lại trên mạng P2P vào lần tiếp theo bạn khởi động Bisq.\nĐể giữ các chào giá luôn trực tuyến, vui lòng để Bisq chạy và đảm bảo là máy tính của bạn cũng đang trực tuyến(có nghĩa là đảm bảo là máy tính của bạn không chuyển về chế độ chờ...nếu màn hình về chế độ chờ thì không sao).
popup.privateNotification.headline=Thông báo riêng tư quan trọng!
@ -1805,6 +1807,9 @@ popup.attention.forTradeWithId=Cần chú ý khi giao dịch có ID {0}
popup.roundedFiatValues.headline=Tính năng bảo mật mới: Giá trị tiền pháp định đã làm tròn
popup.roundedFiatValues.msg=Để tăng tính bảo mật, lượng {0} đã được làm tròn.\n\nTùy vào bạn đang sử dụng phiên bản nào của ứng dụng mà bạn sẽ phải trả hay nhận được hoặc là giá trị thập phân hoặc là giá trị đã làm tròn. \n\nCả hai giá trị này từ đây sẽ tuân theo giao thức giao dịch.\n\nCũng nên lưu ý là giá trị BTC sẽ tự động thay đổi sao cho khớp nhất có thể với lượng tiền pháp định đã được làm tròn.
popup.info.multiplePaymentAccounts.headline=Multiple payment accounts available
popup.info.multiplePaymentAccounts.msg=You have multiple payment accounts available for this offer. Please make sure you've picked the right one.
####################################################################
# Notifications
@ -2065,7 +2070,7 @@ payment.emailOrMobile=Email hoặc số điện thoại
payment.useCustomAccountName=Sử dụng tên tài khoản thông dụng
payment.maxPeriod=Thời gian giao dịch cho phép tối đa
payment.maxPeriodAndLimit=Thời gian giao dịch tối đa: {0} / Giới hạn giao dịch tối đa: {1} / Tuổi tài khoản: {2}
payment.maxPeriodAndLimitCrypto=Thời gian giao dịch tối đa: {0} / Giới hạn giao dịch tối đa: {1}
payment.maxPeriodAndLimitCrypto=Thời gian giao dịch tối đa: {0} / Giới hạn giao dịch tối đa: {1}
payment.currencyWithSymbol=Tiền tệ: {0}
payment.nameOfAcceptedBank=Tên NH được chấp nhận
payment.addAcceptedBank=Thêm NH được chấp nhận
@ -2085,10 +2090,10 @@ payment.clearXchange.info=Chắc chắc bạn đáp ứng các yêu cầu khi s
payment.moneyGram.info=Khi dùng MoneyGram người mua BTC phải gửi số xác nhận và ảnh chụp hoá đơn đến emailnguoiwf bán. Hoá đơn phải chỉ rõ tên đầy đủ, quốc gia, tiểu bang và số lượng. Người mua sẽ trình email của người bán ra trong quá trình giao dịch
payment.westernUnion.info=Khi sử dụng Western Union, người mua BTC phải gửi MTCN (số theo dõi) và ảnh giấy biên nhận bằng email cho người bán BTC. Giấy biên nhận phải nêu rõ họ tên, thành phố, quốc gia của người bán và số tiền. Người mua sẽ được hiển thị email người bán trong quá trình giao dịch.
payment.halCash.info=Khi sử dụng HalCash người mua BTC cần phải gửi cho người bán BTC mã HalCash bằng tin nhắn điện thoại.\n\nVui lòng đảm bảo là lượng tiền này không vượt quá số lượng tối đa mà ngân hàng của bạn cho phép gửi khi dùng HalCash. Số lượng rút tối thiểu là 10 EUR và tối đa là 600 EUR. Nếu rút nhiều lần thì giới hạn sẽ là 3000 EUR/ người nhận/ ngày và 6000 EUR/người nhận/tháng. Vui lòng kiểm tra chéo những giới hạn này với ngân hàng của bạn để chắc chắn là họ cũng dùng những giới hạn như ghi ở đây.\n\nSố tiền rút phải là bội số của 10 EUR vì bạn không thể rút các mệnh giá khác từ ATM. Giao diện người dùng ở phần 'tạo chào giá' và 'chấp nhận chào giá' sẽ điều chỉnh lượng btc sao cho lượng EUR tương ứng sẽ chính xác. Bạn không thể dùng giá thị trường vì lượng EUR có thể sẽ thay đổi khi giá thay đổi.\n\nTrường hợp tranh chấp, người mua BTC cần phải cung cấp bằng chứng chứng minh mình đã gửi EUR.
payment.halCash.info=When using HalCash the BTC buyer needs to send the BTC seller the HalCash code via a text message from their mobile phone.\n\nPlease make sure to not exceed the maximum amount your bank allows you to send with HalCash. The min. amount per withdrawal is 10 EUR and the max. amount is 600 EUR. For repeated withdrawals it is 3000 EUR per receiver per day and 6000 EUR per receiver per month. Please cross check those limits with your bank to be sure they use the same limits as stated here.\n\nThe withdrawal amount must be a multiple of 10 EUR as you cannot withdraw other amounts from an ATM. The UI in the create-offer and take-offer screen will adjust the BTC amount so that the EUR amount is correct. You cannot use market based price as the EUR amount would be changing with changing prices.\n\nIn case of a dispute the BTC buyer needs to provide the proof that they sent the EUR.
payment.limits.info=Hãy hiểu rằng tất cả giao dịch chuyển khoản ngân hàng đều có thể có rủi ro bị đòi tiền lại.\n\nĐể hạn chế rủi ro này, Bisq đã đặt giới hạn trên mỗi giao dịch dựa trên hai yếu tố:\n\n1. Mức rủi ro đòi tiền lại ước tính cho mỗi phương thức thanh toán áp dụng\n2. Tuổi tài khoản của bạn đối với phương thức thanh toán\n\nTài khoản bạn đang tạo là mới và tuổi bằng không. Sau khi tài khoản của bạn được hai tháng tuổi, giới hạn trên mỗi giao dịch của bạn sẽ tăng lên theo:\n\n● Trong tháng đầu tiên, giới hạn trên mỗi giao dịch của bạn là {0}\n● Trong tháng thứ hai, giới hạn trên mỗi giao dịch của bạn là {1}\n● Sau hai tháng, giới hạn trên mỗi giao dịch của bạn là {2}\n\nLưu ý không có giới hạn trên tổng số lần bạn có thể giao dịch.
payment.cashDeposit.info=Vui lòng xác nhận rằng ngân hàng của bạn cho phép nạp tiền mặt vào tài khoản của người khác. Chẳng hạn, Ngân Hàng Mỹ và Wells Fargo không còn cho phép nạp tiền như vậy nữa.
payment.cashDeposit.info=Vui lòng xác nhận rằng ngân hàng của bạn cho phép nạp tiền mặt vào tài khoản của người khác. Chẳng hạn, Ngân Hàng Mỹ và Wells Fargo không còn cho phép nạp tiền như vậy nữa.
payment.f2f.contact=thông tin liên hệ
payment.f2f.contact.prompt=Bạn muốn liên hệ với đối tác giao dịch qua đâu? (email, địa chỉ, số điện thoại,....)
@ -2098,7 +2103,7 @@ payment.f2f.optionalExtra=Thông tin thêm tuỳ chọn.
payment.f2f.extra=thông tin thêm
payment.f2f.extra.prompt=Người tạo có thể đặt ‘ các điều khoản’ hoặc thêm thông tin liên hệ mở, để hiểnnthij trong báo giá
payment.f2f.info=Những giao dịch ‘mặt đối mặt’ đi kèm những quy tắc và rủi ro khác với giao dịch trực tuyến.\n\nNhững khác biệt chính đó là:\n● Bên mua và bán cần trao đổi thông tin về thời gian và địa điểm gặp mặt sử dụng những thông tin liên lạc mà họ cung cấp. \n● Bên mua và bán cần phải mang theo laptop và thực hiện việc xác nhận ‘đã gửi tiền’ và ‘đã nhận tiền’ tại nơi gặp.\n● Nếu bên chào giá có những ‘điều khoản và điều kiện’ đặc biệt, họ sẽ phải nêu ra ở phần ‘thông tin thêm’ trong tài khoản.\n● Chấp nhận chào giá tức là bên chấp nhận đã đồng ý với các ‘điều khoản và điều kiện’ của bên chào giá.\n● Trong trường hợp tranh chấp, trọng tài sẽ không giúp được gì nhiều bởi vì để cung cấp các bằng chứng không thể thay đổi về những việc xảy ra tại nơi gặp mặt thường là rất khó. Trong những trường hợp như vậy, số BTC này có thể sẽ bị khóa vô thời hạn hoặc khóa đến khi bên mua và bán đạt được thỏa thuận. \n\nĐể chắc chắn là bạn hiểu rõ sự khác nhau của các giao dịch ‘mặt đối mặt’vui lòng đọc hướng dẫn và khuyến nghị tại: 'https://docs.bisq.network/trading-rules.html#f2f-trading'
payment.f2f.info='Face to Face' trades have different rules and come with different risks than online transactions.\n\nThe main differences are:\n● The trading peers need to exchange information about the meeting location and time by using their provided contact details.\n● The trading peers need to bring their laptops and do the confirmation of 'payment sent' and 'payment received' at the meeting place.\n● If a maker has special 'terms and conditions' they must state those in the 'Additional information' text field in the account.\n● By taking an offer the taker agrees to the maker's stated 'terms and conditions'.\n● In case of a dispute the arbitrator cannot help much as it is usually hard to get tamper proof evidence of what happened at the meeting. In such cases the BTC funds might get locked indefinitely or until the trading peers come to an agreement.\n\nTo be sure you fully understand the differences with 'Face to Face' trades please read the instructions and recommendations at: 'https://docs.bisq.network/trading-rules.html#f2f-trading'
payment.f2f.info.openURL=Mở trang web
payment.f2f.offerbook.tooltip.countryAndCity=Đất nước và thành phố:{0}/{1}
payment.f2f.offerbook.tooltip.extra=Thông tin thêm: {0}

27
core/src/main/resources/i18n/displayStrings_zh.properties
View file

@ -299,6 +299,8 @@ market.trades.tooltip.candle.date=日期:
offerbook.createOffer=创建委托
offerbook.takeOffer=下单
offerbook.takeOfferToBuy=Take offer to buy {0}
offerbook.takeOfferToSell=Take offer to sell {0}
offerbook.trader=商人
offerbook.offerersBankId=卖家的银行 ID: {0}
offerbook.offerersBankName=卖家的银行名称: {0}
@ -560,12 +562,12 @@ portfolio.pending.step3_buyer.warn.part1b=在您的支付供应商(例如:银行
portfolio.pending.step3_buyer.warn.part2=BTC卖家仍然没有确认您的付款！\n如果付款发送成功，请检查{0}\n如果BTC卖家在{1}之前不确认收到您的付款，交易将由仲裁员进行调查。
portfolio.pending.step3_buyer.openForDispute=BTC卖家尚未确认您的付款！\n最大 交易期已过\n请联系仲裁员以争取解决纠纷。
# suppress inspection "TrailingSpacesInProperty"
portfolio.pending.step3_seller.part=您的贸易伙伴已确认他已发起{0}付款。\n\n
portfolio.pending.step3_seller.part=Your trading partner has confirmed that they have initiated the {0} payment.\n\n
portfolio.pending.step3_seller.altcoin.explorer=on your favorite {0} blockchain explorer
portfolio.pending.step3_seller.altcoin.wallet=at your {0} wallet
portfolio.pending.step3_seller.altcoin={0}Please check {1} if the transaction to your receiving address\n{2}\nhas already sufficient blockchain confirmations.\nThe payment amount has to be {3}\n\nYou can copy & paste your {4} address from the main screen after closing that popup.
portfolio.pending.step3_seller.postal={0}请检查您是否已经从BTC买家收到了{1} \"US Postal Money Order\" \n\n交易ID(“付款原因”文本)是：“{2}”
portfolio.pending.step3_seller.bank=Your trading partner has confirmed that he initiated the {0} payment.\n\nPlease go to your online banking web page and check if you have received {1} from the BTC buyer.\n\nThe trade ID (\"reason for payment\" text) of the transaction is: \"{2}\"\n\n
portfolio.pending.step3_seller.bank=Your trading partner has confirmed that they have initiated the {0} payment.\n\nPlease go to your online banking web page and check if you have received {1} from the BTC buyer.\n\nThe trade ID (\"reason for payment\" text) of the transaction is: \"{2}\"\n\n
portfolio.pending.step3_seller.cash=Because the payment is done via Cash Deposit the BTC buyer has to write \"NO REFUND\" on the paper receipt, tear it in 2 parts and send you a photo by email.\n\nTo avoid chargeback risk, only confirm if you received the email and if you are sure the paper receipt is valid.\nIf you are not sure, {0}
portfolio.pending.step3_seller.moneyGram=The buyer has to send you the Authorisation number and a photo of the receipt by email.\nThe receipt must clearly show your full name, country, state and the amount. Please check your email if you received the Authorisation number.\n\nAfter closing that popup you will see the BTC buyer's name and address for picking up the money from MoneyGram.\n\nOnly confirm receipt after you have successfully picked up the money!
portfolio.pending.step3_seller.westernUnion=买方必须发送MTCN(跟踪号码)和一张收据的照片。\n收据必须清楚地显示您的全名,城市,国家,数量。如果您收到MTCN，请查收邮件。\n\n关闭弹窗后，您将看到BTC买家的姓名和在西联的收钱地址。\n\n只有在您成功收到钱之后，再确认收据！\n
@ -926,10 +928,10 @@ account.arbitratorSelection.minOne=您至少需要选择一名仲裁员
account.altcoin.yourAltcoinAccounts=Your altcoin accounts
account.altcoin.popup.wallet.msg=Please be sure that you follow the requirements for the usage of {0} wallets as described on the {1} web page.\nUsing wallets from centralized exchanges where (a) you don''t control your keys or (b) which don''t use compatible wallet software is risky: it can lead to loss of the traded funds!\nThe arbitrator is not a {2} specialist and cannot help in such cases.
account.altcoin.popup.wallet.confirm=我了解并确定我知道我需要哪种钱包。
account.altcoin.popup.xmr.msg=If you want to trade XMR on Bisq please be sure you understand and fulfill the following requirements:\n\nFor sending XMR you need to use either the official Monero GUI wallet or Monero CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nmonero-wallet-cli (use the command get_tx_key)\nmonero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nIn addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\nmonero-wallet-cli : using command (check_tx_key).\nmonero-wallet-gui : on the Advanced > Prove/Check page.\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the 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\nIf you cannot provide the above data or if you used an incompatible wallet it would result in losing the dispute case. The XMR sender is responsible to be able to verify the XMR 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 (https://www.getmonero.org/resources/user-guides/prove-payment.html) or the Monero forum (https://forum.getmonero.org) to find more information.
account.altcoin.popup.blur.msg=If you want to trade BLUR on Bisq please be sure 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 arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nIf you cannot provide the required information to the arbitrator, you will lose the dispute. In all cases of dispute, the BLUR sender bears 100% of the burden of responsiblity in verifying transactions to an arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW).
account.altcoin.popup.ccx.msg=If you want to trade CCX on Bisq please be sure you understand the following requirements:\n\nTo send CCX you must use an official Conceal wallet, either CLI or GUI. After sending a transfer payment, the wallets\ndisplay the transaction secret key. You must save it along with the transaction hash (ID) and the recipient's public\naddress in case arbitration is necessary. In such a case, you must give all three to the arbitrator, who will then\nverify the CCX transfer using the Conceal Transaction Viewer (https://explorer.conceal.network/txviewer).\nBecause Conceal is a privacy coin, block explorers cannot verify transfers.\n\nIf you cannot provide the required data to the arbitrator, you will lose the dispute case.\nIf you do not save the transaction secret key immediately after transferring CCX, it cannot be recovered later.\nIf you do not understand these requirements, seek help at the Conceal discord (http://discord.conceal.network).
account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides a transaction is not verifyable on the public blockchain. If required you can prove your payment thru use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at \ (http://drgl.info/#check_txn).\n\nIf you cannot provide the above data or if you used an incompatible wallet it would result in losing the dispute case. The Dragonglass sender is responsible to be able to verify the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help.
account.altcoin.popup.xmr.msg=Trading XMR on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending XMR, you need to use either the official Monero GUI wallet or Monero CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nmonero-wallet-cli (use the command get_tx_key)\nmonero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nIn addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\nmonero-wallet-cli : using command (check_tx_key).\nmonero-wallet-gui : on the Advanced > Prove/Check page.\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The XMR sender is responsible for providing verification of the XMR transfer to the arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) or the Monero forum (https://forum.getmonero.org) to find more information.
account.altcoin.popup.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 arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The 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 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 arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW).
account.altcoin.popup.ccx.msg=Trading CCX on Bisq requires that you understand the following requirements:\n\nTo send CCX you must use an official Conceal wallet, either CLI or GUI. After sending a transfer payment, the wallets\ndisplay the transaction secret key. You must save it along with the transaction hash (ID) and the recipient's public\naddress in case arbitration is necessary. In such a case, you must give all three to the arbitrator, who will then\nverify the CCX transfer using the Conceal Transaction Viewer (https://explorer.conceal.network/txviewer).\nBecause Conceal is a privacy coin, block explorers cannot verify transfers.\n\nFailure to provide the required data to the arbitrator will result in losing the dispute case.\nIf you do not save the transaction secret key immediately after transferring CCX, it cannot be recovered later.\nIf you do not understand these requirements, seek help at the Conceal discord (http://discord.conceal.network).
account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides, a transaction is not verifiable on the public blockchain. If required, you can prove your payment through the use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at (http://drgl.info/#check_txn).\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The Dragonglass sender is responsible for providing verification of the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help.
account.altcoin.popup.ZEC.msg=当使用{0}时，您只能使用透明地址(以t开头)而不是z开头地址(私有)，因为仲裁者无法使用z地址验证事务。
account.altcoin.popup.XZC.msg=When using {0} you can only use the transparent (traceable) addresses not the untraceable addresses, because the arbitrator would not be able to verify the transaction with untraceable addresses at a block explorer.
account.altcoin.popup.bch=Bitcoin Cash and Bitcoin Clashic suffer from replay protection. If you use those coins be sure you take sufficient precautions and understand all implications.You can suffer losses by sending one coin and unintentionally send the same coins on the other block chain.Because those "airdrop coins" share the same history with the Bitcoin blockchain there are also security risks and a considerable risk for losing privacy.\n\nPlease read at the Bisq Forum more about that topic: https://forum.bisq.io/t/airdrop-coins-information-thread-bch-btg-bchc
@ -1306,7 +1308,7 @@ dao.burnBsq.assets.lookBackPeriod=Verification period
dao.burnBsq.assets.trialFee=Fee for trial period
dao.burnBsq.assets.totalFee=Total fees paid
dao.burnBsq.assets.days={0} days
dao.burnBsq.assets.toFewDays=The asset fee is too low. The min. amount of days for the trial perios is {0}.
dao.burnBsq.assets.toFewDays=The asset fee is too low. The min. amount of days for the trial period is {0}.
# suppress inspection "UnusedProperty"
dao.assetState.UNDEFINED=Undefined
@ -1584,7 +1586,7 @@ displayUpdateDownloadWindow.verify.failed=验证失败。\n请到 https://bisq.i
displayUpdateDownloadWindow.success=新版本成功下载并验证签名(s) 。\n\n请打开下载目录,关闭应用程序并安装最新版本。
displayUpdateDownloadWindow.download.openDir=打开下载目录
dispute概要Window.title=概要
disputeSummaryWindow.title=概要
disputeSummaryWindow.openDate=Ticket opening date
disputeSummaryWindow.role=Trader's role
disputeSummaryWindow.evidence=Evidence
@ -1746,7 +1748,7 @@ popup.headline.error=错误
popup.doNotShowAgain=不要再显示
popup.reportError.log=打开日志文件
popup.reportError.gitHub=报告至Github issue tracker
popup.reportError={0}\n\nTo help us to improve the software please report the bug on our issue tracker on GitHub (https://github.com/bisq-network/bisq-desktop/issues).\nThe error message will be copied to the clipboard when you click a button below.\nIt will make debugging easier if you can attach the bisq.log file as well.
popup.reportError={0}\n\nTo help us to improve the software please report this bug by opening a new issue at https://github.com/bisq-network/bisq/issues.\nThe above error message will be copied to the clipboard when you click either of the buttons below.\nIt will make debugging easier if you include the bisq.log file by pressing "Open log file", saving a copy, and attaching it to your bug report.
popup.error.tryRestart=请尝试重启您的应用程序或者检查您的网络连接。
popup.error.takeOfferRequestFailed=An error occurred when someone tried to take one of your offers:\n{0}
@ -1805,6 +1807,9 @@ popup.attention.forTradeWithId=交易ID {0}需要注意
popup.roundedFiatValues.headline=New privacy feature: Rounded fiat values
popup.roundedFiatValues.msg=To increase privacy of your trade the {0} amount was rounded.\n\nDepending on the client version you''ll pay or receive either values with decimals or rounded ones.\n\nBoth values do comply from now on with the trade protocol.\n\nAlso be aware that BTC values are changed automatically to match the rounded fiat amount as close as possible.
popup.info.multiplePaymentAccounts.headline=Multiple payment accounts available
popup.info.multiplePaymentAccounts.msg=You have multiple payment accounts available for this offer. Please make sure you've picked the right one.
####################################################################
# Notifications
@ -2085,7 +2090,7 @@ payment.clearXchange.info=Please be sure that you fulfill the requirements for t
payment.moneyGram.info=When using MoneyGram the BTC buyer has to send the Authorisation number and a photo of the receipt by email to the BTC seller. The receipt must clearly show the seller's full name, country, state and the amount. The buyer will get displayed the seller's email in the trade process.
payment.westernUnion.info=When using Western Union the BTC buyer has to send the MTCN (tracking number) and a photo of the receipt by email to the BTC seller. The receipt must clearly show the seller's full name, city, country and the amount. The buyer will get displayed the seller's email in the trade process.
payment.halCash.info=When using HalCash the BTC buyer need to send the BTC seller the HalCash code via a text message from the mobile phone.\n\nPlease make sure to not exceed the maximum amount your bank allows you to send with HalCash. The min. amount per withdrawal is 10 EUR and the max. amount is 600 EUR. For repeated withdrawals it is 3000 EUR per receiver per day and 6000 EUR per receiver per month. Please cross check those limits with your bank to be sure they use the same limits as stated here.\n\nThe withdrawal amount must be a multiple of 10 EUR as you cannot withdraw other amounts from an ATM. The UI in the create-offer and take-offer screen will adjust the BTC amount so that the EUR amount is correct. You cannot use market based price as the EUR amount would be changing with changing prices.\n\nIn case of a dispute the BTC buyer need to provide the proof that he sent the EUR.
payment.halCash.info=When using HalCash the BTC buyer needs to send the BTC seller the HalCash code via a text message from their mobile phone.\n\nPlease make sure to not exceed the maximum amount your bank allows you to send with HalCash. The min. amount per withdrawal is 10 EUR and the max. amount is 600 EUR. For repeated withdrawals it is 3000 EUR per receiver per day and 6000 EUR per receiver per month. Please cross check those limits with your bank to be sure they use the same limits as stated here.\n\nThe withdrawal amount must be a multiple of 10 EUR as you cannot withdraw other amounts from an ATM. The UI in the create-offer and take-offer screen will adjust the BTC amount so that the EUR amount is correct. You cannot use market based price as the EUR amount would be changing with changing prices.\n\nIn case of a dispute the BTC buyer needs to provide the proof that they sent the EUR.
payment.limits.info=Please be aware that all bank transfers carry a certain amount of chargeback risk.\n\nTo mitigate this risk, Bisq sets per-trade limits based on two factors:\n\n1. The estimated level of chargeback risk for the payment method used\n2. The age of your account for that payment method\n\nThe account you are creating now is new and its age is zero. As your account grows in age over a two-month period, your per-trade limits will grow along with it:\n\n● During the 1st month, your per-trade limit will be {0}\n● During the 2nd month, your per-trade limit will be {1}\n● After the 2nd month, your per-trade limit will be {2}\n\nPlease note that there are no limits on the total number of times you can trade.
payment.cashDeposit.info=Please confirm your bank allows you to send cash deposits into other peoples' accounts. For example, Bank of America and Wells Fargo no longer allow such deposits.
@ -2098,7 +2103,7 @@ payment.f2f.optionalExtra=Optional additional information
payment.f2f.extra=Additional information
payment.f2f.extra.prompt=The maker can define 'terms and conditions' or add a public contact information. It will be displayed with the offer.
payment.f2f.info='Face to Face' trades have different rules and come with different risks than online transactions.\n\nThe main differences are:\n● The trading peers need to exchange information about the meeting location and time by using their provided contact details.\n● The trading peers need to bring their laptops and do the confirmation of 'payment sent' and 'payment received' at the meeting place.\n● If a maker has special 'terms and conditions' he needs to state those in the 'Addition information' text field in the account.\n● By taking an offer the taker agrees to the maker's stated 'terms and conditions'.\n● In case of a dispute the arbitrator cannot help much as it is usually hard to get tamper proof evidence of what happened at the meeting. In such cases the BTC funds might get locked indefinitely or until the trading peers come to an agreement.\n\nTo be sure you fully understand the differences with 'Face to Face' trades please read the instructions and recommendations at: 'https://docs.bisq.network/trading-rules.html#f2f-trading'
payment.f2f.info='Face to Face' trades have different rules and come with different risks than online transactions.\n\nThe main differences are:\n● The trading peers need to exchange information about the meeting location and time by using their provided contact details.\n● The trading peers need to bring their laptops and do the confirmation of 'payment sent' and 'payment received' at the meeting place.\n● If a maker has special 'terms and conditions' they must state those in the 'Additional information' text field in the account.\n● By taking an offer the taker agrees to the maker's stated 'terms and conditions'.\n● In case of a dispute the arbitrator cannot help much as it is usually hard to get tamper proof evidence of what happened at the meeting. In such cases the BTC funds might get locked indefinitely or until the trading peers come to an agreement.\n\nTo be sure you fully understand the differences with 'Face to Face' trades please read the instructions and recommendations at: 'https://docs.bisq.network/trading-rules.html#f2f-trading'
payment.f2f.info.openURL=Open web page
payment.f2f.offerbook.tooltip.countryAndCity=County and city: {0} / {1}
payment.f2f.offerbook.tooltip.extra=Additional information: {0}

2
core/src/test/java/bisq/core/user/PreferencesTest.java
View file

@ -124,9 +124,7 @@ public class PreferencesTest {
preferences.readPersisted();
assertEquals(13, preferences.getCryptoCurrenciesAsObservable().size());
assertTrue(preferences.getCryptoCurrenciesAsObservable().contains(dash));
}
@Test

2
desktop/package/linux/Dockerfile
View file

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

2
desktop/package/linux/package.sh
View file

@ -6,7 +6,7 @@
# - Update version below
# - Ensure JAVA_HOME below is pointing to OracleJDK 10 directory
version=0.9.1-SNAPSHOT
version=0.9.2-SNAPSHOT
version_base=$(echo $version | awk -F'[_-]' '{print $1}')
base_dir=$( cd "$(dirname "$0")" ; pwd -P )/../../..
src_dir=$base_dir/desktop/package

2
desktop/package/linux/release.sh
View file

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

4
desktop/package/macosx/Info.plist
View file

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

20
desktop/package/macosx/copy_dbs.sh Executable file
View file

@ -0,0 +1,20 @@
#!/bin/bash
cd $(dirname $0)/../../../
# Mainnet
dbDir=~/Library/Application\ Support/Bisq/btc_mainnet/db
resDir=p2p/src/main/resources
cp "$dbDir/TradeStatistics2Store" "$resDir/TradeStatistics2Store_BTC_MAINNET"
cp "$dbDir/AccountAgeWitnessStore" "$resDir/AccountAgeWitnessStore_BTC_MAINNET"
# Testnet
dbDir=~/Library/Application\ Support/bisq-BTC_PRODTEST/btc_testnet/db
cp "$dbDir/AccountAgeWitnessStore" "$resDir/AccountAgeWitnessStore_BTC_TESTNET"
cp "$dbDir/BlindVoteStore" "$resDir/BlindVoteStore_BTC_TESTNET"
cp "$dbDir/DaoStateStore" "$resDir/DaoStateStore_BTC_TESTNET"
cp "$dbDir/ProposalStore" "$resDir/ProposalStore_BTC_TESTNET"
cp "$dbDir/TempProposalStore" "$resDir/TempProposalStore_BTC_TESTNET"

6
desktop/package/macosx/create_app.sh
View file

@ -6,7 +6,7 @@ mkdir -p deploy
set -e
version="0.9.1"
version="0.9.2-SNAPSHOT"
cd ..
./gradlew :desktop:build -x test shadowJar
@ -38,8 +38,8 @@ java -jar ./package/tools-1.0.jar $EXE_JAR
echo SHA 256 after stripping jar file to get a deterministic jar:
shasum -a256 $EXE_JAR | awk '{print $1}' | tee deploy/Bisq-$version.jar.txt
vmPath=/Users/christoph/Documents/Workspaces/Java
#vmPath=/Volumes
#vmPath=/Users/christoph/Documents/Workspaces/Java
vmPath=/Volumes
linux64=$vmPath/vm_shared_ubuntu/desktop
linux64Package=$linux64/package/linux
win64=$vmPath/vm_shared_windows/desktop

11
desktop/package/macosx/finalize.sh
View file

@ -2,14 +2,14 @@
cd ../../
version="0.9.1"
version="0.9.2-SNAPSHOT"
target_dir="releases/$version"
#vmPath=/Users/christoph/Documents/Workspaces/Java
vmPath=/Volumes
linux64=$vmPath/vm_shared_ubuntu
win64=$vmPath/vm_shared_windows
linux64=$vmPath/vm_shared_ubuntu/desktop/package/linux
win64=$vmPath/vm_shared_windows/desktop/package/windows
macOS=deploy
@ -33,10 +33,11 @@ cp "deploy/Bisq-$version.jar.txt" "$target_dir/"
dmg="Bisq-$version.dmg"
cp "$macOS/$dmg" "$target_dir/"
deb="Bisq-$version.deb"
deb64="Bisq-64bit-$version.deb"
cp "$linux64/$deb64" "$target_dir/"
cp "$linux64/$deb" "$target_dir/$deb64"
exe="Bisq.exe"
exe="Bisq-$version.exe"
exe64="Bisq-64bit-$version.exe"
cp "$win64/$exe" "$target_dir/$exe64"

2
desktop/package/windows/package.bat
View file

@ -8,7 +8,7 @@
@echo off
set version=0.9.1-SNAPSHOT
set version=0.9.2-SNAPSHOT
set package_dir=%~dp0..
for /F "tokens=1,2,3 delims=.-" %%a in ("%version%") do (
set file_version=%%a.%%b.%%c

2
desktop/package/windows/release.bat
View file

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

8
desktop/src/main/java/bisq/desktop/components/paymentmethods/CryptoCurrencyForm.java
View file

@ -22,6 +22,7 @@ import bisq.desktop.util.FormBuilder;
import bisq.desktop.util.Layout;
import bisq.core.dao.governance.asset.AssetService;
import bisq.core.filter.FilterManager;
import bisq.core.locale.CurrencyUtil;
import bisq.core.locale.Res;
import bisq.core.locale.TradeCurrency;
@ -58,6 +59,7 @@ public class CryptoCurrencyForm extends PaymentMethodForm {
private final CryptoCurrencyAccount cryptoCurrencyAccount;
private final AltCoinAddressValidator altCoinAddressValidator;
private final AssetService assetService;
private final FilterManager filterManager;
private InputTextField addressInputTextField;
@ -77,11 +79,13 @@ public class CryptoCurrencyForm extends PaymentMethodForm {
GridPane gridPane,
int gridRow,
BSFormatter formatter,
AssetService assetService) {
AssetService assetService,
FilterManager filterManager) {
super(paymentAccount, accountAgeWitnessService, inputValidator, gridPane, gridRow, formatter);
this.cryptoCurrencyAccount = (CryptoCurrencyAccount) paymentAccount;
this.altCoinAddressValidator = altCoinAddressValidator;
this.assetService = assetService;
this.filterManager = filterManager;
}
@Override
@ -163,7 +167,7 @@ public class CryptoCurrencyForm extends PaymentMethodForm {
currencyComboBox.setPromptText("");
});
currencyComboBox.setItems(FXCollections.observableArrayList(CurrencyUtil.getActiveSortedCryptoCurrencies(assetService)));
currencyComboBox.setItems(FXCollections.observableArrayList(CurrencyUtil.getActiveSortedCryptoCurrencies(assetService, filterManager)));
currencyComboBox.setVisibleRowCount(Math.min(currencyComboBox.getItems().size(), 15));
currencyComboBox.setConverter(new StringConverter<TradeCurrency>() {
@Override

7
desktop/src/main/java/bisq/desktop/main/account/content/altcoinaccounts/AltCoinAccountsView.java
View file

@ -27,6 +27,7 @@ import bisq.desktop.util.FormBuilder;
import bisq.desktop.util.Layout;
import bisq.core.dao.governance.asset.AssetService;
import bisq.core.filter.FilterManager;
import bisq.core.locale.CryptoCurrency;
import bisq.core.locale.Res;
import bisq.core.locale.TradeCurrency;
@ -65,6 +66,7 @@ public class AltCoinAccountsView extends PaymentAccountsView<GridPane, AltCoinAc
private final AltCoinAddressValidator altCoinAddressValidator;
private final AccountAgeWitnessService accountAgeWitnessService;
private final AssetService assetService;
private final FilterManager filterManager;
private final BSFormatter formatter;
private PaymentMethodForm paymentMethodForm;
@ -78,6 +80,7 @@ public class AltCoinAccountsView extends PaymentAccountsView<GridPane, AltCoinAc
AltCoinAddressValidator altCoinAddressValidator,
AccountAgeWitnessService accountAgeWitnessService,
AssetService assetService,
FilterManager filterManager,
BSFormatter formatter) {
super(model);
@ -85,6 +88,7 @@ public class AltCoinAccountsView extends PaymentAccountsView<GridPane, AltCoinAc
this.altCoinAddressValidator = altCoinAddressValidator;
this.accountAgeWitnessService = accountAgeWitnessService;
this.assetService = assetService;
this.filterManager = filterManager;
this.formatter = formatter;
}
@ -103,6 +107,7 @@ public class AltCoinAccountsView extends PaymentAccountsView<GridPane, AltCoinAc
model.dataModel.exportAccounts((Stage) root.getScene().getWindow());
}
///////////////////////////////////////////////////////////////////////////////////////////
// UI actions
///////////////////////////////////////////////////////////////////////////////////////////
@ -251,7 +256,7 @@ public class AltCoinAccountsView extends PaymentAccountsView<GridPane, AltCoinAc
private PaymentMethodForm getPaymentMethodForm(PaymentAccount paymentAccount) {
return new CryptoCurrencyForm(paymentAccount, accountAgeWitnessService, altCoinAddressValidator,
inputValidator, root, gridRow, formatter, assetService);
inputValidator, root, gridRow, formatter, assetService, filterManager);
}
private void removeNewAccountForm() {

8
desktop/src/main/java/bisq/desktop/main/settings/preferences/PreferencesView.java
View file

@ -35,6 +35,7 @@ import bisq.core.app.BisqEnvironment;
import bisq.core.btc.BaseCurrencyNetwork;
import bisq.core.dao.DaoFacade;
import bisq.core.dao.governance.asset.AssetService;
import bisq.core.filter.FilterManager;
import bisq.core.locale.Country;
import bisq.core.locale.CountryUtil;
import bisq.core.locale.CryptoCurrency;
@ -118,6 +119,7 @@ public class PreferencesView extends ActivatableViewAndModel<GridPane, Preferenc
private final ReferralIdService referralIdService;
private final BisqEnvironment bisqEnvironment;
private final AssetService assetService;
private final FilterManager filterManager;
private final DaoFacade daoFacade;
private final BSFormatter formatter;
@ -149,13 +151,14 @@ public class PreferencesView extends ActivatableViewAndModel<GridPane, Preferenc
@Inject
public PreferencesView(PreferencesViewModel model, Preferences preferences, FeeService feeService,
ReferralIdService referralIdService, BisqEnvironment bisqEnvironment,
AssetService assetService, DaoFacade daoFacade, BSFormatter formatter) {
AssetService assetService, FilterManager filterManager, DaoFacade daoFacade, BSFormatter formatter) {
super(model);
this.preferences = preferences;
this.feeService = feeService;
this.referralIdService = referralIdService;
this.bisqEnvironment = bisqEnvironment;
this.assetService = assetService;
this.filterManager = filterManager;
this.daoFacade = daoFacade;
this.formatter = formatter;
}
@ -185,7 +188,7 @@ public class PreferencesView extends ActivatableViewAndModel<GridPane, Preferenc
@Override
protected void activate() {
// We want to have it updated in case an asset got removed
allCryptoCurrencies = FXCollections.observableArrayList(CurrencyUtil.getActiveSortedCryptoCurrencies(assetService));
allCryptoCurrencies = FXCollections.observableArrayList(CurrencyUtil.getActiveSortedCryptoCurrencies(assetService, filterManager));
allCryptoCurrencies.removeAll(cryptoCurrencies);
activateGeneralOptions();
@ -397,6 +400,7 @@ public class PreferencesView extends ActivatableViewAndModel<GridPane, Preferenc
final ImageView icon = ImageUtil.getImageViewById(ImageUtil.REMOVE_ICON);
final Button removeButton = new AutoTooltipButton("", icon);
final AnchorPane pane = new AnchorPane(label, removeButton);
{
label.setLayoutY(5);
removeButton.setId("icon-button");

BIN
p2p/src/main/resources/AccountAgeWitnessStore_BTC_MAINNET
View file

Binary file not shown.

BIN
p2p/src/main/resources/AccountAgeWitnessStore_BTC_TESTNET
View file

Binary file not shown.

BIN
p2p/src/main/resources/BlindVoteStore_BTC_TESTNET
View file

Binary file not shown.

BIN
p2p/src/main/resources/DaoStateStore_BTC_TESTNET
View file

Binary file not shown.

BIN
p2p/src/main/resources/ProposalStore_BTC_TESTNET
View file

Binary file not shown.

BIN
p2p/src/main/resources/TempProposalStore_BTC_TESTNET
View file

Binary file not shown.

BIN
p2p/src/main/resources/TradeStatistics2Store_BTC_MAINNET
View file

Binary file not shown.

2
relay/src/main/resources/version.txt
View file

@ -1 +1 @@
0.9.1
0.9.2

2
seednode/src/main/java/bisq/seednode/SeedNodeMain.java
View file

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