From 4b9f5beafe9ee77209014093cc5318e037809126 Mon Sep 17 00:00:00 2001 From: Hennadii Stepanov <32963518+hebasto@users.noreply.github.com> Date: Fri, 6 Feb 2026 13:40:59 +0000 Subject: [PATCH 1/2] Update Transifex slug for 31.x Update the Transifex slug to match the new resource created for the upcoming 31.x branch. --- .tx/config | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.tx/config b/.tx/config index a7550d0884d..41051254f32 100644 --- a/.tx/config +++ b/.tx/config @@ -1,7 +1,7 @@ [main] host = https://www.transifex.com -[o:bitcoin:p:bitcoin:r:qt-translation-030x] +[o:bitcoin:p:bitcoin:r:qt-translation-031x] file_filter = src/qt/locale/bitcoin_.xlf source_file = src/qt/locale/bitcoin_en.xlf source_lang = en From 576f8920279820bca0caf2c32362ab9eb6e4ac1a Mon Sep 17 00:00:00 2001 From: Hennadii Stepanov <32963518+hebasto@users.noreply.github.com> Date: Fri, 6 Feb 2026 13:45:34 +0000 Subject: [PATCH 2/2] qt: Update the `src/qt/locale/bitcoin_en.xlf` translation source file Steps to reproduce the diff on Ubuntu 25.10: ``` cmake --preset dev-mode cmake --build build_dev_mode --target translate ``` --- src/qt/bitcoinstrings.cpp | 20 +- src/qt/locale/bitcoin_en.ts | 315 ++- src/qt/locale/bitcoin_en.xlf | 4454 +++++++++++++++++----------------- 3 files changed, 2466 insertions(+), 2323 deletions(-) diff --git a/src/qt/bitcoinstrings.cpp b/src/qt/bitcoinstrings.cpp index 2b10c64cfa0..8878600c054 100644 --- a/src/qt/bitcoinstrings.cpp +++ b/src/qt/bitcoinstrings.cpp @@ -13,14 +13,15 @@ QT_TRANSLATE_NOOP("bitcoin-core", "%s failed to validate the -assumeutxo snapsho QT_TRANSLATE_NOOP("bitcoin-core", "%s is set very high!"), QT_TRANSLATE_NOOP("bitcoin-core", "%s is set very high! Fees this large could be paid on a single transaction."), QT_TRANSLATE_NOOP("bitcoin-core", "%s request to listen on port %u. This port is considered \"bad\" and thus it is unlikely that any peer will connect to it. See doc/p2p-bad-ports.md for details and a full list."), +QT_TRANSLATE_NOOP("bitcoin-core", "-asmap requires a file path. Use -asmap=."), QT_TRANSLATE_NOOP("bitcoin-core", "-maxmempool must be at least %d MB"), QT_TRANSLATE_NOOP("bitcoin-core", "-paytxfee is deprecated and will be fully removed in v31.0."), +QT_TRANSLATE_NOOP("bitcoin-core", "A %zu MiB dbcache may be too large for a system memory of only %zu MiB."), QT_TRANSLATE_NOOP("bitcoin-core", "A fatal internal error occurred, see debug.log for details: "), QT_TRANSLATE_NOOP("bitcoin-core", "Assumeutxo data not found for the given blockhash '%s'."), QT_TRANSLATE_NOOP("bitcoin-core", "Block verification was interrupted"), QT_TRANSLATE_NOOP("bitcoin-core", "Can't spend unconfirmed version %d pre-selected input with a version 3 tx"), QT_TRANSLATE_NOOP("bitcoin-core", "Can't spend unconfirmed version 3 pre-selected input with a version %d tx"), -QT_TRANSLATE_NOOP("bitcoin-core", "Cannot add WalletDescriptor to a non-descriptor wallet"), QT_TRANSLATE_NOOP("bitcoin-core", "Cannot obtain a lock on directory %s. %s is probably already running."), QT_TRANSLATE_NOOP("bitcoin-core", "Cannot provide specific connections and have addrman find outgoing connections at the same time."), QT_TRANSLATE_NOOP("bitcoin-core", "Cannot resolve -%s address: '%s'"), @@ -35,18 +36,19 @@ QT_TRANSLATE_NOOP("bitcoin-core", "Could not find asmap file %s"), QT_TRANSLATE_NOOP("bitcoin-core", "Could not generate scriptPubKeys (cache is empty)"), QT_TRANSLATE_NOOP("bitcoin-core", "Could not parse asmap file %s"), QT_TRANSLATE_NOOP("bitcoin-core", "Could not top up scriptPubKeys"), +QT_TRANSLATE_NOOP("bitcoin-core", "Creating wallet…"), QT_TRANSLATE_NOOP("bitcoin-core", "Disk space for %s may not accommodate the block files. Approximately %u GB of data will be stored in this directory."), QT_TRANSLATE_NOOP("bitcoin-core", "Disk space is too low!"), QT_TRANSLATE_NOOP("bitcoin-core", "Distributed under the MIT software license, see the accompanying file %s or %s"), QT_TRANSLATE_NOOP("bitcoin-core", "Do you want to rebuild the databases now?"), QT_TRANSLATE_NOOP("bitcoin-core", "Done loading"), QT_TRANSLATE_NOOP("bitcoin-core", "Dump file %s does not exist."), +QT_TRANSLATE_NOOP("bitcoin-core", "Duplicate binding configuration for address %s. Please check your -bind, -bind=...=onion and -whitebind settings."), QT_TRANSLATE_NOOP("bitcoin-core", "Elliptic curve cryptography sanity check failure. %s is shutting down."), -QT_TRANSLATE_NOOP("bitcoin-core", "Error creating %s"), +QT_TRANSLATE_NOOP("bitcoin-core", "Error creating %s: Could not write version metadata."), QT_TRANSLATE_NOOP("bitcoin-core", "Error initializing block database"), QT_TRANSLATE_NOOP("bitcoin-core", "Error loading %s"), QT_TRANSLATE_NOOP("bitcoin-core", "Error loading %s: External signer wallet being loaded without external signer support compiled"), -QT_TRANSLATE_NOOP("bitcoin-core", "Error loading %s: Private keys can only be disabled during creation"), QT_TRANSLATE_NOOP("bitcoin-core", "Error loading %s: Wallet corrupted"), QT_TRANSLATE_NOOP("bitcoin-core", "Error loading %s: Wallet is a legacy wallet. Please migrate to a descriptor wallet using the migration tool (migratewallet RPC)."), QT_TRANSLATE_NOOP("bitcoin-core", "Error loading %s: Wallet requires newer version of %s"), @@ -102,7 +104,6 @@ QT_TRANSLATE_NOOP("bitcoin-core", "Failed to acquire rescan reserver during wall QT_TRANSLATE_NOOP("bitcoin-core", "Failed to calculate bump fees, because unconfirmed UTXOs depend on an enormous cluster of unconfirmed transactions."), QT_TRANSLATE_NOOP("bitcoin-core", "Failed to close block undo file."), QT_TRANSLATE_NOOP("bitcoin-core", "Failed to close file when writing block."), -QT_TRANSLATE_NOOP("bitcoin-core", "Failed to connect best block (%s)."), QT_TRANSLATE_NOOP("bitcoin-core", "Failed to disconnect block."), QT_TRANSLATE_NOOP("bitcoin-core", "Failed to listen on any port. Use -listen=0 if you want this."), QT_TRANSLATE_NOOP("bitcoin-core", "Failed to read block."), @@ -112,8 +113,6 @@ QT_TRANSLATE_NOOP("bitcoin-core", "Failed to rescan the wallet during initializa QT_TRANSLATE_NOOP("bitcoin-core", "Failed to start indexes, shutting down…"), QT_TRANSLATE_NOOP("bitcoin-core", "Failed to verify database"), QT_TRANSLATE_NOOP("bitcoin-core", "Failed to write block."), -QT_TRANSLATE_NOOP("bitcoin-core", "Failed to write to block index database."), -QT_TRANSLATE_NOOP("bitcoin-core", "Failed to write to coin database."), QT_TRANSLATE_NOOP("bitcoin-core", "Failed to write undo data."), QT_TRANSLATE_NOOP("bitcoin-core", "Failure removing transaction: %s"), QT_TRANSLATE_NOOP("bitcoin-core", "Fee estimation failed. Fallbackfee is disabled. Wait a few blocks or enable %s."), @@ -161,13 +160,16 @@ QT_TRANSLATE_NOOP("bitcoin-core", "Not found pre-selected input %s"), QT_TRANSLATE_NOOP("bitcoin-core", "Not solvable pre-selected input %s"), QT_TRANSLATE_NOOP("bitcoin-core", "Only direction was set, no permissions: '%s'"), QT_TRANSLATE_NOOP("bitcoin-core", "Option '-checkpoints' is set but checkpoints were removed. This option has no effect."), -QT_TRANSLATE_NOOP("bitcoin-core", "Option '-maxorphantx' is set but no longer has any effect (see release notes). Please remove it from your configuration."), -QT_TRANSLATE_NOOP("bitcoin-core", "Options '-datacarrier' or '-datacarriersize' are set but are marked as deprecated. They will be removed in a future version."), +QT_TRANSLATE_NOOP("bitcoin-core", "Option '-limitancestorsize' is given but ancestor size limits have been replaced with cluster size limits (see -limitclustersize). This option has no effect."), +QT_TRANSLATE_NOOP("bitcoin-core", "Option '-limitdescendantsize' is given but descendant size limits have been replaced with cluster size limits (see -limitclustersize). This option has no effect."), QT_TRANSLATE_NOOP("bitcoin-core", "Outbound connections restricted to CJDNS (-onlynet=cjdns) but -cjdnsreachable is not provided"), QT_TRANSLATE_NOOP("bitcoin-core", "Outbound connections restricted to Tor (-onlynet=onion) but the proxy for reaching the Tor network is explicitly forbidden: -onion=0"), QT_TRANSLATE_NOOP("bitcoin-core", "Outbound connections restricted to Tor (-onlynet=onion) but the proxy for reaching the Tor network is not provided: none of -proxy, -onion or -listenonion is given"), QT_TRANSLATE_NOOP("bitcoin-core", "Outbound connections restricted to i2p (-onlynet=i2p) but -i2psam is not provided"), QT_TRANSLATE_NOOP("bitcoin-core", "Please contribute if you find %s useful. Visit %s for further information about the software."), +QT_TRANSLATE_NOOP("bitcoin-core", "Private broadcast of own transactions requested (-privatebroadcast) and -proxyrandomize is disabled. Tor circuits for private broadcast connections may be correlated to other connections over Tor. For maximum privacy set -proxyrandomize=1."), +QT_TRANSLATE_NOOP("bitcoin-core", "Private broadcast of own transactions requested (-privatebroadcast), but -connect is also configured. They are incompatible because the private broadcast needs to open new connections to randomly chosen Tor or I2P peers. Consider using -maxconnections=0 -addnode=... instead"), +QT_TRANSLATE_NOOP("bitcoin-core", "Private broadcast of own transactions requested (-privatebroadcast), but none of Tor or I2P networks is reachable"), QT_TRANSLATE_NOOP("bitcoin-core", "Prune cannot be configured with a negative value."), QT_TRANSLATE_NOOP("bitcoin-core", "Prune configured below the minimum of %d MiB. Please use a higher number."), QT_TRANSLATE_NOOP("bitcoin-core", "Prune mode is incompatible with -reindex-chainstate. Use full -reindex instead."), @@ -260,8 +262,8 @@ QT_TRANSLATE_NOOP("bitcoin-core", "Verifying blocks…"), QT_TRANSLATE_NOOP("bitcoin-core", "Verifying wallet(s)…"), QT_TRANSLATE_NOOP("bitcoin-core", "Wallet file creation failed: %s"), QT_TRANSLATE_NOOP("bitcoin-core", "Wallet needed to be rewritten: restart %s to complete"), +QT_TRANSLATE_NOOP("bitcoin-core", "Warning: Found invalid chain more than 6 blocks longer than our best chain. This could be due to database corruption or consensus incompatibility with peers."), QT_TRANSLATE_NOOP("bitcoin-core", "Warning: Private keys detected in wallet {%s} with disabled private keys"), -QT_TRANSLATE_NOOP("bitcoin-core", "Warning: We do not appear to fully agree with our peers! You may need to upgrade, or other nodes may need to upgrade."), QT_TRANSLATE_NOOP("bitcoin-core", "Witness data for blocks after height %d requires validation. Please restart with -reindex."), QT_TRANSLATE_NOOP("bitcoin-core", "You need to rebuild the database using -reindex to go back to unpruned mode. This will redownload the entire blockchain"), QT_TRANSLATE_NOOP("bitcoin-core", "Your computer's date and time appear to be more than %d minutes out of sync with the network, this may lead to consensus failure. After you've confirmed your computer's clock, this message should no longer appear when you restart your node. Without a restart, it should stop showing automatically after you've connected to a sufficient number of new outbound peers, which may take some time. You can inspect the `timeoffset` field of the `getpeerinfo` and `getnetworkinfo` RPC methods to get more info."), diff --git a/src/qt/locale/bitcoin_en.ts b/src/qt/locale/bitcoin_en.ts index 39d84639536..61013e0821f 100644 --- a/src/qt/locale/bitcoin_en.ts +++ b/src/qt/locale/bitcoin_en.ts @@ -345,7 +345,7 @@ Signing is only possible with addresses of the type 'legacy'. - + Runaway exception @@ -368,7 +368,7 @@ Signing is only possible with addresses of the type 'legacy'. BitcoinGUI - + &Overview &Overview @@ -428,7 +428,7 @@ Signing is only possible with addresses of the type 'legacy'. - + &Minimize @@ -449,7 +449,7 @@ Signing is only possible with addresses of the type 'legacy'. - + Send coins to a Bitcoin address Send coins to a Bitcoin address @@ -544,7 +544,7 @@ Signing is only possible with addresses of the type 'legacy'. - + &File &File @@ -589,7 +589,7 @@ Signing is only possible with addresses of the type 'legacy'. - + Request payments (generates QR codes and bitcoin: URIs) @@ -609,7 +609,7 @@ Signing is only possible with addresses of the type 'legacy'. - + Processed %n block(s) of transaction history. Processed %n block of transaction history. @@ -657,7 +657,7 @@ Signing is only possible with addresses of the type 'legacy'. Up to date - + Ctrl+Q @@ -760,18 +760,19 @@ Signing is only possible with addresses of the type 'legacy'. - + No wallets available - + + Wallet Data Name of the wallet data file format. - + Load Wallet Backup The title for Restore Wallet File Windows @@ -784,12 +785,39 @@ Signing is only possible with addresses of the type 'legacy'. + Wallet Name Label of the input field where the name of the wallet is entered. - + + Invalid Wallet Name + + + + + Wallet name cannot be empty + + + + + Restore and Migrate Wallet File... + + + + + Restore and Migrate Wallet Backup + + + + + Restore and Migrate Wallet + Title of pop-up window shown when the user is attempting to restore a wallet. + + + + &Window &Window @@ -1206,7 +1234,7 @@ Signing is only possible with addresses of the type 'legacy'. - Make a blank wallet. Blank wallets do not initially have private keys or scripts. Private keys and addresses can be imported, or an HD seed can be set, at a later time. + Make a blank wallet. Blank wallets do not initially have private keys or scripts. Private keys and addresses can be imported using descriptors at a later time. @@ -1499,7 +1527,7 @@ Signing is only possible with addresses of the type 'legacy'. MigrateWalletActivity - + Migrate wallet @@ -1518,7 +1546,7 @@ The migration process will create a backup of the wallet before migrating. This - + Migrate Wallet @@ -1542,8 +1570,41 @@ The migration process will create a backup of the wallet before migrating. This Solvable but not watched scripts have been migrated to a new wallet named '%1'. + + + Restore and Migrate wallet + + + + + Are you sure you wish to restore the wallet file <i>%1</i> to <i>%2</i> and migrate it? + + + + + Restoring the wallet will copy the backup file to the wallets directory and place it in the standard wallet directory layout. The original file will not be modified. + +Migrating the wallet will convert the restored wallet to one or more descriptor wallets. A new wallet backup will need to be made. +If this wallet contains any watchonly scripts, a new wallet will be created which contains those watchonly scripts. +If this wallet contains any solvable but not watched scripts, a different and new wallet will be created which contains those scripts. + +The migration process will create a backup of the wallet before migrating. This backup file will be named <wallet name>-<timestamp>.legacy.bak and can be found in the directory for this wallet. In the event of an incorrect migration, the backup can be restored with the "Restore Wallet" functionality. + + + Restore Wallet + Title of progress window which is displayed when wallets are being restored. + + + + + Restoring Wallet <b>%1</b>… + Descriptive text of the restore wallets progress window which indicates to the user that wallets are currently being restored. + + + + Migration failed @@ -1656,7 +1717,7 @@ The migration process will create a backup of the wallet before migrating. This OpenWalletActivity - + Open wallet failed @@ -2502,7 +2563,7 @@ If you are receiving this error you should request the merchant provide a BIP21 - + Ctrl+W @@ -2588,6 +2649,12 @@ If you are receiving this error you should request the merchant provide a BIP21 Short-lived peer connection type that solicits known addresses from a peer. + + + Private Broadcast + Short-lived peer connection type that is used for broadcasting privacy-sensitive data. + + @@ -2689,7 +2756,7 @@ If you are receiving this error you should request the merchant provide a BIP21 - + %1 kB @@ -2711,7 +2778,7 @@ If you are receiving this error you should request the merchant provide a BIP21 - + Do you want to reset settings to default values, or to abort without making changes? Explanatory text shown on startup when the settings file cannot be read. Prompts user to make a choice between resetting or aborting. @@ -2723,7 +2790,7 @@ If you are receiving this error you should request the merchant provide a BIP21 - + Error: %1 @@ -2819,7 +2886,6 @@ If you are receiving this error you should request the merchant provide a BIP21 - @@ -2834,12 +2900,12 @@ If you are receiving this error you should request the merchant provide a BIP21 - + N/A N/A - + Client version Client version @@ -2941,18 +3007,18 @@ If you are receiving this error you should request the merchant provide a BIP21 - + Received - - + + Sent - + &Peers @@ -3009,11 +3075,6 @@ If you are receiving this error you should request the merchant provide a BIP21 - Starting Block - - - - Synced Headers @@ -3074,7 +3135,7 @@ If you are receiving this error you should request the merchant provide a BIP21 - + User Agent @@ -3145,7 +3206,7 @@ If you are receiving this error you should request the merchant provide a BIP21 - + Connection Time @@ -3201,7 +3262,7 @@ If you are receiving this error you should request the merchant provide a BIP21 - + Last block time Last block time @@ -3276,7 +3337,7 @@ If you are receiving this error you should request the merchant provide a BIP21 - + Inbound: initiated by peer Explanatory text for an inbound peer connection. @@ -3311,6 +3372,12 @@ If you are receiving this error you should request the merchant provide a BIP21 Explanatory text for a short-lived outbound peer connection that is used to request addresses from a peer. + + + Private broadcast: short-lived, for broadcasting privacy-sensitive transactions + Explanatory text for a short-lived outbound peer connection that is used to broadcast privacy-sensitive data (like our transactions). + + detecting: peer could be v1 or v2 @@ -3426,7 +3493,7 @@ If you are receiving this error you should request the merchant provide a BIP21 - + Ctrl+I @@ -3451,7 +3518,7 @@ If you are receiving this error you should request the merchant provide a BIP21 - + Executing command using "%1" wallet @@ -4583,7 +4650,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 TransactionDesc - + conflicted with a transaction with %1 confirmations Text explaining the current status of a transaction, shown in the status field of the details window for this transaction. This status represents an unconfirmed transaction that conflicts with a confirmed transaction. @@ -4640,7 +4707,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - + From @@ -4652,32 +4719,32 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - + To - - + + own address - + label - + Credit - + matures in %n more block(s) matures in %n more block @@ -4690,7 +4757,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - + Debit @@ -5113,7 +5180,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 UnitDisplayStatusBarControl - + Unit to show amounts in. Click to select another unit. @@ -5333,12 +5400,12 @@ Go to File > Open Wallet to load a wallet. bitcoin-core - + The %s developers - + %s failed to validate the -assumeutxo snapshot state. This indicates a hardware problem, or a bug in the software, or a bad software modification that allowed an invalid snapshot to be loaded. As a result of this, the node will shut down and stop using any state that was built on the snapshot, resetting the chain height from %d to %d. On the next restart, the node will resume syncing from %d without using any snapshot data. Please report this incident to %s, including how you obtained the snapshot. The invalid snapshot chainstate will be left on disk in case it is helpful in diagnosing the issue that caused this error. @@ -5348,7 +5415,7 @@ Go to File > Open Wallet to load a wallet. - + Disk space for %s may not accommodate the block files. Approximately %u GB of data will be stored in this directory. @@ -5393,7 +5460,7 @@ Go to File > Open Wallet to load a wallet. - + File %s already exists. If you are sure this is what you want, move it out of the way first. @@ -5428,7 +5495,7 @@ Go to File > Open Wallet to load a wallet. - + Prune configured below the minimum of %d MiB. Please use a higher number. @@ -5498,15 +5565,10 @@ Go to File > Open Wallet to load a wallet. - + Warning: Private keys detected in wallet {%s} with disabled private keys - - - Warning: We do not appear to fully agree with our peers! You may need to upgrade, or other nodes may need to upgrade. - - Witness data for blocks after height %d requires validation. Please restart with -reindex. @@ -5518,12 +5580,12 @@ Go to File > Open Wallet to load a wallet. - + %s is set very high! - + -maxmempool must be at least %d MB @@ -5548,22 +5610,22 @@ Go to File > Open Wallet to load a wallet. - + %s is set very high! Fees this large could be paid on a single transaction. - + Cannot provide specific connections and have addrman find outgoing connections at the same time. - + Error loading %s: External signer wallet being loaded without external signer support compiled - + Error reading %s! All keys read correctly, but transaction data or address metadata may be missing or incorrect. @@ -5583,7 +5645,7 @@ Go to File > Open Wallet to load a wallet. - + Failed to remove snapshot chainstate dir (%s). Manually remove it before restarting. @@ -5594,7 +5656,7 @@ Go to File > Open Wallet to load a wallet. - + Fee estimation failed. Fallbackfee is disabled. Wait a few blocks or enable %s. @@ -5634,17 +5696,7 @@ Go to File > Open Wallet to load a wallet. - - Option '-maxorphantx' is set but no longer has any effect (see release notes). Please remove it from your configuration. - - - - - Options '-datacarrier' or '-datacarriersize' are set but are marked as deprecated. They will be removed in a future version. - - - - + Outbound connections restricted to CJDNS (-onlynet=cjdns) but -cjdnsreachable is not provided @@ -5664,7 +5716,7 @@ Go to File > Open Wallet to load a wallet. - + Prune: last wallet synchronisation goes beyond pruned data. You need to -reindex (download the whole blockchain again in case of a pruned node) @@ -5749,12 +5801,12 @@ Unable to restore backup of wallet. - + -paytxfee is deprecated and will be fully removed in v31.0. - + A fatal internal error occurred, see debug.log for details: @@ -5778,11 +5830,6 @@ Unable to restore backup of wallet. Can't spend unconfirmed version 3 pre-selected input with a version %d tx - - - Cannot add WalletDescriptor to a non-descriptor wallet - - Cannot write to directory '%s'; check permissions. @@ -5829,7 +5876,7 @@ Unable to restore backup of wallet. - + Disk space is too low! @@ -5844,17 +5891,12 @@ Unable to restore backup of wallet. - + Elliptic curve cryptography sanity check failure. %s is shutting down. - - Error creating %s - - - - + Error initializing block database @@ -5865,11 +5907,6 @@ Unable to restore backup of wallet. - Error loading %s: Private keys can only be disabled during creation - - - - Error loading %s: Wallet corrupted @@ -6053,11 +6090,6 @@ Unable to restore backup of wallet. Failed to close file when writing block. - - - Failed to connect best block (%s). - - Failed to disconnect block. @@ -6088,16 +6120,6 @@ Unable to restore backup of wallet. Failed to write block. - - - Failed to write to block index database. - - - - - Failed to write to coin database. - - Failed to write undo data. @@ -6173,8 +6195,33 @@ Unable to restore backup of wallet. Invalid amount for %s=<amount>: '%s' + + + -asmap requires a file path. Use -asmap=<file>. + + + A %zu MiB dbcache may be too large for a system memory of only %zu MiB. + + + + + Creating wallet… + + + + + Duplicate binding configuration for address %s. Please check your -bind, -bind=...=onion and -whitebind settings. + + + + + Error creating %s: Could not write version metadata. + + + + Invalid amount for -%s=<amount>: '%s' @@ -6254,7 +6301,32 @@ Unable to restore backup of wallet. - + + Option '-limitancestorsize' is given but ancestor size limits have been replaced with cluster size limits (see -limitclustersize). This option has no effect. + + + + + Option '-limitdescendantsize' is given but descendant size limits have been replaced with cluster size limits (see -limitclustersize). This option has no effect. + + + + + Private broadcast of own transactions requested (-privatebroadcast) and -proxyrandomize is disabled. Tor circuits for private broadcast connections may be correlated to other connections over Tor. For maximum privacy set -proxyrandomize=1. + + + + + Private broadcast of own transactions requested (-privatebroadcast), but -connect is also configured. They are incompatible because the private broadcast needs to open new connections to randomly chosen Tor or I2P peers. Consider using -maxconnections=0 -addnode=... instead + + + + + Private broadcast of own transactions requested (-privatebroadcast), but none of Tor or I2P networks is reachable + + + + Prune cannot be configured with a negative value. @@ -6534,7 +6606,12 @@ Unable to restore backup of wallet. - + + Warning: Found invalid chain more than 6 blocks longer than our best chain. This could be due to database corruption or consensus incompatibility with peers. + + + + acceptstalefeeestimates is not supported on %s chain. @@ -6598,12 +6675,12 @@ Please try running the latest software version. - + Failed to start indexes, shutting down… - + Invalid -proxy address or hostname, ends with '=': '%s' @@ -6613,7 +6690,7 @@ Please try running the latest software version. - + Unrecognized network in -proxy='%s': '%s' diff --git a/src/qt/locale/bitcoin_en.xlf b/src/qt/locale/bitcoin_en.xlf index cfa6442e722..a9c042a8dc7 100644 --- a/src/qt/locale/bitcoin_en.xlf +++ b/src/qt/locale/bitcoin_en.xlf @@ -294,19 +294,19 @@ Signing is only possible with addresses of the type 'legacy'. Runaway exception - 435 + 436 A fatal error occurred. %1 can no longer continue safely and will quit. - 436 + 437 Internal error - 445 + 446 An internal error occurred. %1 will attempt to continue safely. This is an unexpected bug which can be reported as described below. - 446 + 447 @@ -322,11 +322,11 @@ Signing is only possible with addresses of the type 'legacy'. Error: %1 - 601 + 597 %1 didn't yet exit safely… - 674 + 670 @@ -334,199 +334,199 @@ Signing is only possible with addresses of the type 'legacy'. &Overview - 252 + 258 Show general overview of wallet - 253 + 259 &Transactions - 273 + 279 Browse transaction history - 274 + 280 E&xit - 293 + 299 Quit application - 294 + 300 &About %1 - 297 + 303 Show information about %1 - 298 + 304 About &Qt - 301 + 307 Show information about Qt - 302 + 308 Modify configuration options for %1 - 305 + 311 Create a new wallet - 349 + 355 &Minimize - 537 + 573 Wallet: - 616 + 652 Network activity disabled. - 1034 + 1070 A substring of the tooltip. Proxy is <b>enabled</b>: %1 - 1480 + 1516 Send coins to a Bitcoin address - 260 + 266 Backup wallet to another location - 313 + 319 Change the passphrase used for wallet encryption - 315 + 321 &Send - 259 + 265 &Receive - 266 + 272 &Options… - 304 + 310 &Encrypt Wallet… - 309 + 315 Encrypt the private keys that belong to your wallet - 310 + 316 &Backup Wallet… - 312 + 318 &Change Passphrase… - 314 + 320 Sign &message… - 316 + 322 Sign messages with your Bitcoin addresses to prove you own them - 317 + 323 &Verify message… - 318 + 324 Verify messages to ensure they were signed with specified Bitcoin addresses - 319 + 325 &Load PSBT from file… - 320 + 326 Open &URI… - 336 + 342 Close Wallet… - 344 + 350 Create Wallet… - 347 + 353 Close All Wallets… - 357 + 363 &File - 503 + 539 &Settings - 524 + 560 &Help - 585 + 621 Tabs toolbar - 596 + 632 Syncing Headers (%1%)… - 1078 + 1114 Synchronizing with network… - 1136 + 1172 Indexing blocks on disk… - 1141 + 1177 Processing blocks on disk… - 1143 + 1179 Connecting to peers… - 1150 + 1186 Request payments (generates QR codes and bitcoin: URIs) - 267 + 273 Show the list of used sending addresses and labels - 332 + 338 Show the list of used receiving addresses and labels - 334 + 340 &Command-line options - 365 + 371 - 1159 + 1195 Processed %n block(s) of transaction history. @@ -536,346 +536,369 @@ Signing is only possible with addresses of the type 'legacy'. %1 behind - 1182 + 1218 Catching up… - 1187 + 1223 Last received block was generated %1 ago. - 1206 + 1242 Transactions after this will not yet be visible. - 1208 + 1244 Error - 1243 + 1279 Warning - 1247 + 1283 Information - 1251 + 1287 Up to date - 1163 + 1199 Ctrl+Q - 295 + 301 Load Partially Signed Bitcoin Transaction - 321 + 327 Load PSBT from &clipboard… - 322 + 328 Load Partially Signed Bitcoin Transaction from clipboard - 323 + 329 Node window - 325 + 331 Open node debugging and diagnostic console - 326 + 332 &Sending addresses - 331 + 337 &Receiving addresses - 333 + 339 Open a bitcoin: URI - 337 + 343 Open Wallet - 339 + 345 Open a wallet - 341 + 347 Close wallet - 345 + 351 Restore Wallet… - 352 + 358 Name of the menu item that restores wallet from a backup file. Restore a wallet from a backup file - 355 + 361 Status tip for Restore Wallet menu item Close all wallets - 358 + 364 Migrate Wallet - 360 + 366 Migrate a wallet - 362 + 368 Show the %1 help message to get a list with possible Bitcoin command-line options - 367 + 373 &Mask values - 369 + 375 Mask the values in the Overview tab - 371 + 377 No wallets available - 426 - 485 + 432 + 495 Wallet Data - 432 + 438 + 503 Name of the wallet data file format. Load Wallet Backup - 435 + 441 The title for Restore Wallet File Windows Restore Wallet - 443 + 449 Title of pop-up window shown when the user is attempting to restore a wallet. Wallet Name - 445 + 451 + 514 Label of the input field where the name of the wallet is entered. - &Window - 535 + Invalid Wallet Name + 455 - Ctrl+M - 538 + Wallet name cannot be empty + 455 - Zoom - 547 + Restore and Migrate Wallet File... + 499 - Main Window - 565 + Restore and Migrate Wallet Backup + 504 - %1 client - 844 + Restore and Migrate Wallet + 512 + Title of pop-up window shown when the user is attempting to restore a wallet. - &Hide - 912 + &Window + 571 + Ctrl+M + 574 + + + Zoom + 583 + + + Main Window + 601 + + + %1 client + 880 + + + &Hide + 948 + + S&how - 913 + 949 - 1031 + 1067 A substring of the tooltip. - + %n active connection(s) to Bitcoin network. - + %n active connection(s) to Bitcoin network. - + Click for more actions. - 1041 + 1077 A substring of the tooltip. "More actions" are available via the context menu. - + Show Peers tab - 1058 + 1094 A context menu item. The "Peers tab" is an element of the "Node window". - + Disable network activity - 1066 + 1102 A context menu item. - + Enable network activity - 1068 + 1104 A context menu item. The network activity was disabled previously. - - Pre-syncing Headers (%1%)… - 1085 - - - Error: %1 - 1244 - - - Warning: %1 - 1248 - - - Date: %1 - - 1356 - - - Amount: %1 - - 1357 - - Wallet: %1 - - 1359 + Pre-syncing Headers (%1%)… + 1121 - Type: %1 - - 1361 + Error: %1 + 1280 - Label: %1 - - 1363 + Warning: %1 + 1284 - Address: %1 + Date: %1 - 1365 + 1392 - Sent transaction - 1366 + Amount: %1 + + 1393 - Incoming transaction - 1366 + Wallet: %1 + + 1395 - HD key generation is <b>enabled</b> - 1418 + Type: %1 + + 1397 - HD key generation is <b>disabled</b> - 1418 + Label: %1 + + 1399 - Private key <b>disabled</b> - 1418 + Address: %1 + + 1401 - Wallet is <b>encrypted</b> and currently <b>unlocked</b> - 1441 + Sent transaction + 1402 - Wallet is <b>encrypted</b> and currently <b>locked</b> - 1449 + Incoming transaction + 1402 + HD key generation is <b>enabled</b> + 1454 + + + HD key generation is <b>disabled</b> + 1454 + + + Private key <b>disabled</b> + 1454 + + + Wallet is <b>encrypted</b> and currently <b>unlocked</b> + 1477 + + + Wallet is <b>encrypted</b> and currently <b>locked</b> + 1485 + + Original message: - 1568 + 1604 - + Unit to show amounts in. Click to select another unit. - 1607 + 1650 - + Coin Selection 14 - + Quantity: 51 - + Bytes: 80 - + Amount: 125 - + Fee: 170 - + After Fee: 218 - + Change: 250 - + (un)select all 306 - + Tree mode 322 - + List mode 335 - + Amount 391 - + Received with label 396 - + Received with address 401 - + Date 406 - + Confirmations 411 - + Confirmed 414 @@ -883,72 +906,72 @@ Signing is only possible with addresses of the type 'legacy'. - + Copy amount 65 - + &Copy address 54 - + Copy &label 55 - + Copy &amount 56 - + Copy transaction &ID and output index 57 - + L&ock unspent 59 - + &Unlock unspent 60 - + Copy quantity 64 - + Copy fee 66 - + Copy after fee 67 - + Copy bytes 68 - + Copy change 69 - + (%1 locked) 363 - + Can vary +/- %1 satoshi(s) per input. 528 - + (no label) 573 627 - + change from %1 (%2) 620 - + (change) 621 @@ -956,156 +979,184 @@ Signing is only possible with addresses of the type 'legacy'. - + Create Wallet 250 Title of window indicating the progress of creation of a new wallet. - + Creating Wallet <b>%1</b>… 253 Descriptive text of the create wallet progress window which indicates to the user which wallet is currently being created. - + Create wallet failed 285 - + Create wallet warning 287 - + Can't list signers 303 - + Too many external signers found 306 - + Load Wallets 380 Title of progress window which is displayed when wallets are being loaded. - + Loading wallets… 383 Descriptive text of the load wallets progress window which indicates to the user that wallets are currently being loaded. - + Migrate wallet - 446 + 477 - + Are you sure you wish to migrate the wallet <i>%1</i>? - 447 + 478 - + Migrating the wallet will convert this wallet to one or more descriptor wallets. A new wallet backup will need to be made. If this wallet contains any watchonly scripts, a new wallet will be created which contains those watchonly scripts. If this wallet contains any solvable but not watched scripts, a different and new wallet will be created which contains those scripts. The migration process will create a backup of the wallet before migrating. This backup file will be named <wallet name>-<timestamp>.legacy.bak and can be found in the directory for this wallet. In the event of an incorrect migration, the backup can be restored with the "Restore Wallet" functionality. - 448 - - - Migrate Wallet - 465 - - - Migrating Wallet <b>%1</b>… - 465 - - - The wallet '%1' was migrated successfully. - 471 - - - Watchonly scripts have been migrated to a new wallet named '%1'. - 473 - - - Solvable but not watched scripts have been migrated to a new wallet named '%1'. - 476 + 479 - Migration failed - 490 + Migrate Wallet + 451 + Migrating Wallet <b>%1</b>… + 451 + + + The wallet '%1' was migrated successfully. + 457 + + + Watchonly scripts have been migrated to a new wallet named '%1'. + 459 + + + Solvable but not watched scripts have been migrated to a new wallet named '%1'. + 462 + + + Restore and Migrate wallet + 496 + + + Are you sure you wish to restore the wallet file <i>%1</i> to <i>%2</i> and migrate it? + 497 + + + Restoring the wallet will copy the backup file to the wallets directory and place it in the standard wallet directory layout. The original file will not be modified. + +Migrating the wallet will convert the restored wallet to one or more descriptor wallets. A new wallet backup will need to be made. +If this wallet contains any watchonly scripts, a new wallet will be created which contains those watchonly scripts. +If this wallet contains any solvable but not watched scripts, a different and new wallet will be created which contains those scripts. + +The migration process will create a backup of the wallet before migrating. This backup file will be named <wallet name>-<timestamp>.legacy.bak and can be found in the directory for this wallet. In the event of an incorrect migration, the backup can be restored with the "Restore Wallet" functionality. + 498 + + + Restore Wallet + 512 + Title of progress window which is displayed when wallets are being restored. + + + Restoring Wallet <b>%1</b>… + 515 + Descriptive text of the restore wallets progress window which indicates to the user that wallets are currently being restored. + + + Migration failed + 534 + + Migration Successful - 492 + 536 - + Open wallet failed 337 - + Open wallet warning 339 - + Open Wallet 353 Title of window indicating the progress of opening of a wallet. - + Opening Wallet <b>%1</b>… 356 Descriptive text of the open wallet progress window which indicates to the user which wallet is currently being opened. - + Restore Wallet 406 Title of progress window which is displayed when wallets are being restored. - + Restoring Wallet <b>%1</b>… 409 Descriptive text of the restore wallets progress window which indicates to the user that wallets are currently being restored. - + Restore wallet failed 428 Title of message box which is displayed when the wallet could not be restored. - + Restore wallet warning 431 Title of message box which is displayed when the wallet is restored with some warning. - + Restore wallet message 434 Title of message box which is displayed when the wallet is successfully restored. - + Close wallet 93 - + Are you sure you wish to close the wallet <i>%1</i>? 94 - + Closing the wallet for too long can result in having to resync the entire chain if pruning is enabled. 95 - + Close all wallets 105 - + Are you sure you wish to close all wallets? 106 @@ -1113,59 +1164,59 @@ The migration process will create a backup of the wallet before migrating. This - + Create Wallet 14 - + You are one step away from creating your new wallet! 29 - + Please provide a name and, if desired, enable any advanced options 42 - + Wallet Name 67 - + Wallet 80 - + Encrypt the wallet. The wallet will be encrypted with a passphrase of your choice. 89 - + Encrypt Wallet 92 - + Advanced Options 118 - + Disable private keys for this wallet. Wallets with private keys disabled will have no private keys and cannot have an HD seed or imported private keys. This is ideal for watch-only wallets. 139 - + Disable Private Keys 142 - - Make a blank wallet. Blank wallets do not initially have private keys or scripts. Private keys and addresses can be imported, or an HD seed can be set, at a later time. + + Make a blank wallet. Blank wallets do not initially have private keys or scripts. Private keys and addresses can be imported using descriptors at a later time. 149 - + Make Blank Wallet 152 - + Use an external signing device such as a hardware wallet. Configure the external signer script in wallet preferences first. 159 - + External signer 162 @@ -1173,11 +1224,11 @@ The migration process will create a backup of the wallet before migrating. This - + Create 20 - + Compiled without external signing support (required for external signing) 88 "External signing" means using devices such as hardware wallets. @@ -1186,23 +1237,23 @@ The migration process will create a backup of the wallet before migrating. This - + Edit Address 14 - + &Label 25 - + The label associated with this address list entry 35 - + The address associated with this address list entry. This can only be modified for sending addresses. 52 - + &Address 42 @@ -1210,35 +1261,35 @@ The migration process will create a backup of the wallet before migrating. This - + New sending address 29 - + Edit receiving address 32 - + Edit sending address 36 - + The entered address "%1" is not a valid Bitcoin address. 113 - + Address "%1" already exists as a receiving address with label "%2" and so cannot be added as a sending address. 146 - + The entered address "%1" is already in the address book with label "%2". 151 - + Could not unlock wallet. 123 - + New key generation failed. 128 @@ -1246,23 +1297,23 @@ The migration process will create a backup of the wallet before migrating. This - + A new data directory will be created. 21 - + name 43 - + Directory already exists. Add %1 if you intend to create a new directory here. 45 - + Path already exists, and is not a directory. 48 - + Cannot create data directory here. 55 @@ -1270,25 +1321,25 @@ The migration process will create a backup of the wallet before migrating. This - + version 36 - + About %1 40 - + Command-line options 58 - + %1 is shutting down… 147 - + Do not shut down the computer until this window disappears. 148 @@ -1296,47 +1347,47 @@ The migration process will create a backup of the wallet before migrating. This - + Welcome 14 - + Welcome to %1. 23 - + As this is the first time the program is launched, you can choose where %1 will store its data. 49 - + Limit block chain storage to 238 - + Reverting this setting requires re-downloading the entire blockchain. It is faster to download the full chain first and prune it later. Disables some advanced features. 241 - + GB 248 - + This initial synchronisation is very demanding, and may expose hardware problems with your computer that had previously gone unnoticed. Each time you run %1, it will continue downloading where it left off. 216 - + When you click OK, %1 will begin to download and process the full %4 block chain (%2 GB) starting with the earliest transactions in %3 when %4 initially launched. 206 - + If you have chosen to limit block chain storage (pruning), the historical data must still be downloaded and processed, but will be deleted afterward to keep your disk usage low. 226 - + Use the default data directory 66 - + Use a custom data directory: 73 @@ -1344,72 +1395,72 @@ The migration process will create a backup of the wallet before migrating. This - + Bitcoin 54 218 - + %n GB of space available - + %n GB of space available 220 - + (of %n GB needed) - + (of %n GB needed) 223 - + (%n GB needed for full chain) - + (%n GB needed for full chain) - + Choose data directory 240 - + At least %1 GB of data will be stored in this directory, and it will grow over time. 295 - + Approximately %1 GB of data will be stored in this directory. 298 307 Explanatory text on the capability of the current prune target. - + (sufficient to restore backups %n day(s) old) - + (sufficient to restore backups %n day(s) old) - + %1 will download and store a copy of the Bitcoin block chain. 309 - + The wallet will also be stored in this directory. 311 - + Error: Specified data directory "%1" cannot be created. 167 - + Error 197 @@ -1417,54 +1468,54 @@ The migration process will create a backup of the wallet before migrating. This - + Form 14 - + Recent transactions may not yet be visible, and therefore your wallet's balance might be incorrect. This information will be correct once your wallet has finished synchronizing with the bitcoin network, as detailed below. 133 - + Attempting to spend bitcoins that are affected by not-yet-displayed transactions will not be accepted by the network. 152 - + Number of blocks left 215 - + Unknown… 222 248 ../modaloverlay.cpp160 - + calculating… 292 312 - + Last block time 235 - + Progress 261 - + Progress increase per hour 285 - + Estimated time left until synced 305 - + Hide 342 - + Esc 345 @@ -1472,21 +1523,21 @@ The migration process will create a backup of the wallet before migrating. This - + %1 is currently syncing. It will download headers and blocks from peers and validate them until reaching the tip of the block chain. 34 - + Unknown. Syncing Headers (%1, %2%)… 166 - + Unknown. Pre-syncing Headers (%1, %2%)… 171 - + unknown 131 @@ -1494,15 +1545,15 @@ The migration process will create a backup of the wallet before migrating. This - + Open bitcoin URI 14 - + URI: 22 - + Paste address from clipboard 36 Tooltip text for button that allows you to paste an address that is in your clipboard. @@ -1511,294 +1562,294 @@ The migration process will create a backup of the wallet before migrating. This - + Options 14 - + &Main 27 - + Automatically start %1 after logging in to the system. 33 - + &Start %1 on system login 36 - + Enabling pruning significantly reduces the disk space required to store transactions. All blocks are still fully validated. Reverting this setting requires re-downloading the entire blockchain. 58 - + Maximum database cache size. Make sure you have enough RAM. A larger cache can contribute to faster sync, after which the benefit is less pronounced for most use cases. Lowering the cache size will reduce memory usage. Unused mempool memory is shared for this cache. 108 Tooltip text for Options window setting that sets the size of the database cache. Explains the corresponding effects of increasing/decreasing this value. - + Size of &database cache 111 - + Number of script &verification threads 157 - + Full path to a %1 compatible script (e.g. C:\Downloads\hwi.exe or /Users/you/Downloads/hwi.py). Beware: malware can steal your coins! 289 - + Automatically open the Bitcoin client port on the router. This only works when your router supports PCP or NAT-PMP and it is enabled. The external port could be random. 321 - + Map port using PCP or NA&T-PMP 324 - + IP address of the proxy (e.g. IPv4: 127.0.0.1 / IPv6: ::1) 378 565 - + Shows if the supplied default SOCKS5 proxy is used to reach peers via this network type. 447 470 493 - + Minimize instead of exit the application when the window is closed. When this option is enabled, the application will be closed only after selecting Exit in the menu. 662 - + Font in the Overview tab: 769 - + Options set in this dialog are overridden by the command line: 814 - + Open the %1 configuration file from the working directory. 859 - + Open Configuration File 862 - + Reset all client options to default. 872 - + &Reset Options 875 - + &Network 315 - + Prune &block storage to 61 - + GB 71 - + Reverting this setting requires re-downloading the entire blockchain. 96 - + MiB 127 - + Set the number of script verification threads. Negative values correspond to the number of cores you want to leave free to the system. 154 Tooltip text for Options window setting that sets the number of script verification threads. Explains that negative values mean to leave these many cores free to the system. - + (0 = auto, <0 = leave that many cores free) 170 - + This allows you or a third party tool to communicate with the node through command-line and JSON-RPC commands. 192 Tooltip text for Options window setting that enables the RPC server. - + Enable R&PC server 195 An Options window setting to enable the RPC server. - + W&allet 216 - + Whether to set subtract fee from amount as default or not. 222 Tooltip text for Options window setting that sets subtracting the fee from a sending amount as default. - + Subtract &fee from amount by default 225 An Options window setting to set subtracting the fee from a sending amount as default. - + Expert 232 - + Enable coin &control features 241 - + If you disable the spending of unconfirmed change, the change from a transaction cannot be used until that transaction has at least one confirmation. This also affects how your balance is computed. 248 - + &Spend unconfirmed change 251 - + Enable &PSBT controls 258 An options window setting to enable PSBT controls. - + Whether to show PSBT controls. 261 Tooltip text for options window setting that enables PSBT controls. - + External Signer (e.g. hardware wallet) 271 - + &External signer script path 279 - + Accept connections from outside. 331 - + Allow incomin&g connections 334 - + Connect to the Bitcoin network through a SOCKS5 proxy. 341 - + &Connect through SOCKS5 proxy (default proxy): 344 - + Proxy &IP: 353 540 - + &Port: 385 572 - + Port of the proxy (e.g. 9050) 410 597 - + Used for reaching peers via: 434 - + IPv4 457 - + IPv6 480 - + Tor 503 - + &Window 633 - + Show the icon in the system tray. 639 - + &Show tray icon 642 - + Show only a tray icon after minimizing the window. 652 - + &Minimize to the tray instead of the taskbar 655 - + M&inimize on close 665 - + &Display 686 - + User Interface &language: 694 - + The user interface language can be set here. This setting will take effect after restarting %1. 707 - + &Unit to show amounts in: 718 - + Choose the default subdivision unit to show in the interface and when sending coins. 731 - + Third-party URLs (e.g. a block explorer) that appear in the transactions tab as context menu items. %s in the URL is replaced by transaction hash. Multiple URLs are separated by vertical bar |. 742 755 - + &Third-party transaction URLs 745 - + Whether to show coin control features or not. 238 - + Connect to the Bitcoin network through a separate SOCKS5 proxy for Tor onion services. 528 - + Use separate SOCKS&5 proxy to reach peers via Tor onion services: 531 - + &OK 955 - + &Cancel 968 @@ -1806,85 +1857,85 @@ The migration process will create a backup of the wallet before migrating. This - + Compiled without external signing support (required for external signing) 145 "External signing" means using devices such as hardware wallets. - + default 157 - + none 234 - + Confirm options reset 342 Window title text of pop-up window shown when the user has chosen to reset options. - + Client restart required to activate changes. 333 414 Text explaining that the settings changed will not come into effect until the client is restarted. - + Current settings will be backed up at "%1". 337 Text explaining to the user that the client's current settings will be backed up at a specific location. %1 is a stand-in argument for the backup location's path. - + Client will be shut down. Do you want to proceed? 340 Text asking the user to confirm if they would like to proceed with a client shutdown. - + Configuration options 360 Window title text of pop-up box that allows opening up of configuration file. - + The configuration file is used to specify advanced user options which override GUI settings. Additionally, any command-line options will override this configuration file. 363 Explanatory text about the priority order of instructions considered by client. The order from high to low being: command-line, configuration file, GUI settings. - + Continue 366 - + Cancel 367 - + Error 376 - + The configuration file could not be opened. 376 - + This change would require a client restart. 418 - + The supplied proxy address is invalid. 446 - + Embedded "%1" 61 - + Default system font "%1" 62 - + Custom… 63 @@ -1892,7 +1943,7 @@ The migration process will create a backup of the wallet before migrating. This - + Could not read setting "%1", %2. 226 @@ -1900,52 +1951,52 @@ The migration process will create a backup of the wallet before migrating. This - + Form 14 - + The displayed information may be out of date. Your wallet automatically synchronizes with the Bitcoin network after a connection is established, but this process has not completed yet. 76 296 - + Available: 208 - + Your current spendable balance 218 - + Pending: 234 - + Total of transactions that have yet to be confirmed, and do not yet count toward the spendable balance 120 - + Immature: 182 - + Mined balance that has not yet matured 153 - + Balances 60 - + Total: 143 - + Your current total balance 192 - + Recent transactions 280 @@ -1953,7 +2004,7 @@ The migration process will create a backup of the wallet before migrating. This - + Privacy mode activated for the Overview tab. To unmask the values, uncheck Settings->Mask values. 176 @@ -1961,27 +2012,27 @@ The migration process will create a backup of the wallet before migrating. This - + PSBT Operations 14 - + Sign Tx 86 - + Broadcast Tx 102 - + Copy to Clipboard 122 - + Save… 129 - + Close 136 @@ -1989,112 +2040,112 @@ The migration process will create a backup of the wallet before migrating. This - + Failed to load transaction: %1 64 - + Failed to sign transaction: %1 89 - + Cannot sign inputs while wallet is locked. 97 - + Could not sign any more inputs. 99 - + Signed %1 inputs, but more signatures are still required. 101 - + Signed transaction successfully. Transaction is ready to broadcast. 104 - + Unknown error processing transaction. 116 - + Transaction broadcast successfully! Transaction ID: %1 126 - + Transaction broadcast failed: %1 129 - + PSBT copied to clipboard. 138 - + Save Transaction Data 161 - + Partially Signed Transaction (Binary) 163 Expanded name of the binary PSBT file format. See: BIP 174. - + PSBT saved to disk. 170 - + Sends %1 to %2 187 - + own address 191 - + Unable to calculate transaction fee or total transaction amount. 199 - + Pays transaction fee: 201 - + Total Amount 213 - + or 216 - + Transaction has %1 unsigned inputs. 222 - + Transaction is missing some information about inputs. 268 - + Transaction still needs signature(s). 272 - + (But no wallet is loaded.) 275 - + (But this wallet cannot sign transactions.) 278 - + (But this wallet does not have the right keys.) 281 - + Transaction is fully signed and ready for broadcast. 289 - + Transaction status is unknown. 293 @@ -2102,37 +2153,37 @@ The migration process will create a backup of the wallet before migrating. This - + Payment request error 145 - + Cannot start bitcoin: click-to-pay handler 146 - + URI handling 194 210 216 223 - + 'bitcoin://' is not a valid URI. Use 'bitcoin:' instead. 194 - + Cannot process payment request because BIP70 is not supported. Due to widespread security flaws in BIP70 it's strongly recommended that any merchant instructions to switch wallets be ignored. If you are receiving this error you should request the merchant provide a BIP21 compatible URI. 211 234 - + URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. 224 - + Payment request file handling 233 @@ -2140,52 +2191,52 @@ If you are receiving this error you should request the merchant provide a BIP21 - + User Agent 112 Title of Peers Table column which contains the peer's User Agent string. - + Ping 103 Title of Peers Table column which indicates the current latency of the connection with the peer. - + Peer 85 Title of Peers Table column which contains a unique number used to identify a connection. - + Age 88 Title of Peers Table column which indicates the duration (length of time) since the peer connection started. - + Direction 94 Title of Peers Table column which indicates the direction the peer connection was initiated from. - + Sent 106 Title of Peers Table column which indicates the total amount of network information we have sent to the peer. - + Received 109 Title of Peers Table column which indicates the total amount of network information we have received from the peer. - + Address 91 Title of Peers Table column which contains the IP/Onion/I2P address of the connected peer. - + Type 97 Title of Peers Table column which describes the type of peer connection. The "type" describes why the connection exists. - + Network 100 Title of Peers Table column which states the network the peer connected through. @@ -2194,12 +2245,12 @@ If you are receiving this error you should request the merchant provide a BIP21 - + Inbound 77 An Inbound Connection from a Peer. - + Outbound 79 An Outbound Connection to a Peer. @@ -2208,7 +2259,7 @@ If you are receiving this error you should request the merchant provide a BIP21 - + Amount 197 @@ -2216,227 +2267,232 @@ If you are receiving this error you should request the merchant provide a BIP21 - + Enter a Bitcoin address (e.g. %1) 138 - + Ctrl+W - 433 + 426 - + Unroutable - 690 + 683 - + IPv4 - 692 + 685 network name Name of IPv4 network in peer info - + IPv6 - 694 + 687 network name Name of IPv6 network in peer info - + Onion - 696 + 689 network name Name of Tor network in peer info - + I2P - 698 + 691 network name Name of I2P network in peer info - + CJDNS - 700 + 693 network name Name of CJDNS network in peer info - + Inbound - 714 + 707 An inbound connection from a peer. An inbound connection is a connection initiated by a peer. - + Outbound - 717 + 710 An outbound connection to a peer. An outbound connection is a connection initiated by us. - + Full Relay - 722 + 715 Peer connection type that relays all network information. - + Block Relay - 725 + 718 Peer connection type that relays network information about blocks and not transactions or addresses. - + Manual - 727 + 720 Peer connection type established manually through one of several methods. - + Feeler - 729 + 722 Short-lived peer connection type that tests the aliveness of known addresses. - + Address Fetch - 731 + 724 Short-lived peer connection type that solicits known addresses from a peer. - + + Private Broadcast + 726 + Short-lived peer connection type that is used for broadcasting privacy-sensitive data. + + %1 d - 743 - 755 + 738 + 750 - + %1 h - 744 - 756 + 739 + 751 - + %1 m - 745 - 757 + 740 + 752 - + %1 s - 747 - 758 - 784 - - - None - 772 - - - N/A - 778 - - - %1 ms + 742 + 753 779 - - 797 - - %n second(s) - - - %n second(s) - - - - 801 - - %n minute(s) - - - %n minute(s) - - - - 805 - - %n hour(s) - - - %n hour(s) - - - - 809 - - %n day(s) - - - %n day(s) - - - - 813 - 819 - - %n week(s) - - - %n week(s) - - - - %1 and %2 - 819 - - - 819 - - %n year(s) - - - %n year(s) - - - - %1 B - 827 - - %1 kB - 829 - ../rpcconsole.cpp979 + None + 767 - %1 MB - 831 - ../rpcconsole.cpp980 - ../rpcconsole.cpp981 + N/A + 773 - %1 GB - 833 + %1 ms + 774 - + + 792 + + %n second(s) + + + %n second(s) + + + + 796 + + %n minute(s) + + + %n minute(s) + + + + 800 + + %n hour(s) + + + %n hour(s) + + + + 804 + + %n day(s) + + + %n day(s) + + + + 808 + 814 + + %n week(s) + + + %n week(s) + + + + %1 and %2 + 814 + + + 814 + + %n year(s) + + + %n year(s) + + + + %1 B + 822 + + + %1 kB + 824 + ../rpcconsole.cpp985 + + + %1 MB + 826 + ../rpcconsole.cpp986 + ../rpcconsole.cpp987 + + + %1 GB + 828 + + default wallet - 992 + 987 - + &Save Image… 28 - + &Copy Image 29 - + Resulting URI too long, try to reduce the text for label / message. 40 - + Error encoding URI into QR Code. 47 - + QR code support not available. 88 - + Save QR Code 122 - + PNG Image 125 Expanded name of the PNG file format. See: https://en.wikipedia.org/wiki/Portable_Network_Graphics. @@ -2445,7 +2501,7 @@ If you are receiving this error you should request the merchant provide a BIP21 - + N/A 75 101 @@ -2471,340 +2527,335 @@ If you are receiving this error you should request the merchant provide a BIP21 1412 1435 1458 - 1481 - 1507 + 1484 + 1510 1533 1556 1579 1602 1625 - 1648 + 1651 1674 1697 - 1720 - 1746 - 1772 - 1798 - 1824 - ../rpcconsole.h144 + 1723 + 1749 + 1775 + 1801 + ../rpcconsole.h147 - + Client version 65 - + &Information 43 - + General 58 - + Datadir 114 - + To specify a non-default location of the data directory use the '%1' option. 124 - + Blocksdir 143 - + To specify a non-default location of the blocks directory use the '%1' option. 153 - + Startup time 172 - + Network 201 1255 - + Name 208 - + Number of connections 231 - + Local Addresses 254 - + Network addresses that your Bitcoin node is currently using to communicate with other nodes. 282 - + Block chain 295 - + Memory Pool 354 - + Current number of transactions 361 - + Memory usage 384 - + Wallet: 478 - + (none) 489 - + &Reset 700 - + Received 780 - 1615 - - - Sent - 860 1592 - + + Sent + 860 + 1569 + + &Peers 901 - + Banned peers 977 - + Select a peer to view detailed information. 1053 - ../rpcconsole.cpp1147 + ../rpcconsole.cpp1153 - + Hide Peers Detail 1105 - + Ctrl+X 1126 - + The transport layer version: %1 1200 - + Transport 1203 - + Session ID 1229 - + Version 1278 - + Whether we relay transactions to this peer. 1350 - + Transaction Relay 1353 - - Starting Block + + Synced Headers 1402 - - Synced Headers + + Synced Blocks 1425 - - Synced Blocks - 1448 - - + Last Transaction - 1523 + 1500 - + The mapped Autonomous System used for diversifying peer selection. - 1733 + 1710 - + Mapped AS - 1736 + 1713 - + Whether we relay addresses to this peer. - 1759 + 1736 Tooltip text for the Address Relay field in the peer details area, which displays whether we relay addresses to this peer (Yes/No). - + Address Relay - 1762 + 1739 Text title for the Address Relay field in the peer details area, which displays whether we relay addresses to this peer (Yes/No). - + The total number of addresses received from this peer that were processed (excludes addresses that were dropped due to rate-limiting). - 1785 + 1762 Tooltip text for the Addresses Processed field in the peer details area, which displays the total number of addresses received from this peer that were processed (excludes addresses that were dropped due to rate-limiting). - + The total number of addresses received from this peer that were dropped (not processed) due to rate-limiting. - 1811 + 1788 Tooltip text for the Addresses Rate-Limited field in the peer details area, which displays the total number of addresses received from this peer that were dropped (not processed) due to rate-limiting. - + Addresses Processed - 1788 + 1765 Text title for the Addresses Processed field in the peer details area, which displays the total number of addresses received from this peer that were processed (excludes addresses that were dropped due to rate-limiting). - + Addresses Rate-Limited - 1814 + 1791 Text title for the Addresses Rate-Limited field in the peer details area, which displays the total number of addresses received from this peer that were dropped (not processed) due to rate-limiting. - + User Agent 88 1301 - + Node window 14 - + Current block height 302 - + Open the %1 debug log file from the current data directory. This can take a few seconds for large log files. 432 - + Decrease font size 510 - + Increase font size 530 - + Permissions 1151 - + The direction and type of peer connection: %1 1174 - + Direction/Type 1177 - + The BIP324 session ID string in hex. 1226 - + The network protocol this peer is connected through: IPv4, IPv6, Onion, I2P, or CJDNS. 1252 - + Services 1324 - + High bandwidth BIP152 compact block relay: %1 1376 - + High Bandwidth 1379 - - Connection Time - 1471 - - - Elapsed time since a novel block passing initial validity checks was received from this peer. - 1494 - - - Last Block - 1497 - - - Elapsed time since a novel transaction accepted into our mempool was received from this peer. - 1520 - Tooltip text for the Last Transaction field in the peer details area. - - - Last Send - 1546 - - - Last Receive - 1569 - - - Ping Time - 1638 - - - The duration of a currently outstanding ping. - 1661 - - - Ping Wait - 1664 - - - Min Ping - 1687 - - Time Offset - 1710 + Connection Time + 1448 + Elapsed time since a novel block passing initial validity checks was received from this peer. + 1471 + + + Last Block + 1474 + + + Elapsed time since a novel transaction accepted into our mempool was received from this peer. + 1497 + Tooltip text for the Last Transaction field in the peer details area. + + + Last Send + 1523 + + + Last Receive + 1546 + + + Ping Time + 1615 + + + The duration of a currently outstanding ping. + 1638 + + + Ping Wait + 1641 + + + Min Ping + 1664 + + + Time Offset + 1687 + + Last block time 325 - + &Open 435 - + &Console 461 - + &Network Traffic 648 - + Totals 716 - + Debug log file 425 - + Clear console 550 @@ -2812,162 +2863,167 @@ If you are receiving this error you should request the merchant provide a BIP21 - - In: - 931 - - - Out: - 932 - - - Inbound: initiated by peer - 463 - Explanatory text for an inbound peer connection. - - - Outbound Full Relay: default - 467 - Explanatory text for an outbound peer connection that relays all network information. This is the default behavior for outbound connections. - - - Outbound Block Relay: does not relay transactions or addresses - 470 - Explanatory text for an outbound peer connection that relays network information about blocks and not transactions or addresses. - - - Outbound Manual: added using RPC %1 or %2/%3 configuration options - 475 - Explanatory text for an outbound peer connection that was established manually through one of several methods. The numbered arguments are stand-ins for the methods available to establish manual connections. - - - Outbound Feeler: short-lived, for testing addresses - 481 - Explanatory text for a short-lived outbound peer connection that is used to test the aliveness of known addresses. - - - Outbound Address Fetch: short-lived, for soliciting addresses - 484 - Explanatory text for a short-lived outbound peer connection that is used to request addresses from a peer. - - - detecting: peer could be v1 or v2 - 489 - Explanatory text for "detecting" transport type. - - - v1: unencrypted, plaintext transport protocol - 491 - Explanatory text for v1 transport type. - - v2: BIP324 encrypted transport protocol - 493 - Explanatory text for v2 transport type. + In: + 937 - we selected the peer for high bandwidth relay - 497 + Out: + 938 - the peer selected us for high bandwidth relay - 498 + Inbound: initiated by peer + 466 + Explanatory text for an inbound peer connection. - no high bandwidth relay selected - 499 + Outbound Full Relay: default + 470 + Explanatory text for an outbound peer connection that relays all network information. This is the default behavior for outbound connections. - Ctrl++ - 512 - Main shortcut to increase the RPC console font size. + Outbound Block Relay: does not relay transactions or addresses + 473 + Explanatory text for an outbound peer connection that relays network information about blocks and not transactions or addresses. - Ctrl+= - 514 - Secondary shortcut to increase the RPC console font size. + Outbound Manual: added using RPC %1 or %2/%3 configuration options + 478 + Explanatory text for an outbound peer connection that was established manually through one of several methods. The numbered arguments are stand-ins for the methods available to establish manual connections. - Ctrl+- - 518 - Main shortcut to decrease the RPC console font size. + Outbound Feeler: short-lived, for testing addresses + 484 + Explanatory text for a short-lived outbound peer connection that is used to test the aliveness of known addresses. - Ctrl+_ - 520 - Secondary shortcut to decrease the RPC console font size. + Outbound Address Fetch: short-lived, for soliciting addresses + 487 + Explanatory text for a short-lived outbound peer connection that is used to request addresses from a peer. - &Copy address - 666 - Context menu action to copy the address of a peer. + Private broadcast: short-lived, for broadcasting privacy-sensitive transactions + 490 + Explanatory text for a short-lived outbound peer connection that is used to broadcast privacy-sensitive data (like our transactions). - &Disconnect - 670 + detecting: peer could be v1 or v2 + 495 + Explanatory text for "detecting" transport type. - 1 &hour - 671 + v1: unencrypted, plaintext transport protocol + 497 + Explanatory text for v1 transport type. - 1 d&ay - 672 + v2: BIP324 encrypted transport protocol + 499 + Explanatory text for v2 transport type. - 1 &week - 673 + we selected the peer for high bandwidth relay + 503 - 1 &year - 674 + the peer selected us for high bandwidth relay + 504 - &Copy IP/Netmask - 700 - Context menu action to copy the IP/Netmask of a banned peer. IP/Netmask is the combination of a peer's IP address and its Netmask. For IP address, see: https://en.wikipedia.org/wiki/IP_address. + no high bandwidth relay selected + 505 - &Unban - 704 + Ctrl++ + 518 + Main shortcut to increase the RPC console font size. - Network activity disabled - 935 + Ctrl+= + 520 + Secondary shortcut to increase the RPC console font size. - None - 948 + Ctrl+- + 524 + Main shortcut to decrease the RPC console font size. - Executing command without any wallet - 1027 + Ctrl+_ + 526 + Secondary shortcut to decrease the RPC console font size. - Ctrl+I - 1353 + &Copy address + 672 + Context menu action to copy the address of a peer. - Ctrl+T - 1354 + &Disconnect + 676 - Ctrl+N - 1355 + 1 &hour + 677 - Ctrl+P - 1356 + 1 d&ay + 678 - Node window - [%1] - 1374 + 1 &week + 679 - Executing command using "%1" wallet - 1025 + 1 &year + 680 + &Copy IP/Netmask + 706 + Context menu action to copy the IP/Netmask of a banned peer. IP/Netmask is the combination of a peer's IP address and its Netmask. For IP address, see: https://en.wikipedia.org/wiki/IP_address. + + + &Unban + 710 + + + Network activity disabled + 941 + + + None + 954 + + + Executing command without any wallet + 1033 + + + Ctrl+I + 1354 + + + Ctrl+T + 1355 + + + Ctrl+N + 1356 + + + Ctrl+P + 1357 + + + Node window - [%1] + 1375 + + + Executing command using "%1" wallet + 1031 + + Welcome to the %1 RPC console. Use up and down arrows to navigate history, and %2 to clear screen. Use %3 and %4 to increase or decrease the font size. @@ -2975,124 +3031,124 @@ Type %5 for an overview of available commands. For more information on using this console, type %6. %7WARNING: Scammers have been active, telling users to type commands here, stealing their wallet contents. Do not use this console without fully understanding the ramifications of a command.%8 - 864 + 870 RPC console welcome message. Placeholders %7 and %8 are style tags for the warning content, and they are not space separated from the rest of the text intentionally. - + Executing… - 1035 + 1041 A console message indicating an entered command is currently being executed. - + (peer: %1) - 1153 + 1159 - + via %1 - 1155 + 1161 - + Yes - 143 + 146 - + No - 143 + 146 - + To - 143 + 146 - + From - 143 + 146 - + Ban for - 144 + 147 - + Never - 185 + 188 - + Unknown - 144 + 147 - + &Amount: 37 - + &Label: 83 - + &Message: 53 - + An optional message to attach to the payment request, which will be displayed when the request is opened. Note: The message will not be sent with the payment over the Bitcoin network. 50 - + An optional label to associate with the new receiving address. 80 - + Use this form to request payments. All fields are <b>optional</b>. 73 - + An optional amount to request. Leave this empty or zero to not request a specific amount. 34 193 - + An optional label to associate with the new receiving address (used by you to identify an invoice). It is also attached to the payment request. 66 - + An optional message that is attached to the payment request and may be displayed to the sender. 96 - + &Create new receiving address 111 - + Clear all fields of the form. 134 - + Clear 137 - + Requested payments history 273 - + Show the selected request (does the same as double clicking an entry) 298 - + Show 301 - + Remove the selected entries from the list 318 - + Remove 321 @@ -3100,63 +3156,63 @@ For more information on using this console, type %6. - + Copy &URI 46 - + &Copy address 47 - + Copy &label 48 - + Copy &message 49 - + Copy &amount 50 - + Base58 (Legacy) 96 - + Not recommended due to higher fees and less protection against typos. 96 - + Base58 (P2SH-SegWit) 97 - + Generates an address compatible with older wallets. 97 - + Bech32 (SegWit) 98 - + Generates a native segwit address (BIP-173). Some old wallets don't support it. 98 - + Bech32m (Taproot) 100 - + Bech32m (BIP-350) is an upgrade to Bech32, wallet support is still limited. 100 - + Could not unlock wallet. 175 - + Could not generate new %1 address 180 @@ -3164,51 +3220,51 @@ For more information on using this console, type %6. - + Request payment to … 14 - + Address: 90 - + Amount: 119 - + Label: 148 - + Message: 180 - + Wallet: 212 - + Copy &URI 240 - + Copy &Address 250 - + &Verify 260 - + Verify this address on e.g. a hardware wallet screen 263 - + &Save Image… 273 - + Payment information 39 @@ -3216,7 +3272,7 @@ For more information on using this console, type %6. - + Request payment to %1 46 @@ -3224,31 +3280,31 @@ For more information on using this console, type %6. - + Date 34 - + Label 34 - + Message 34 - + (no label) 72 - + (no message) 81 - + (no amount requested) 89 - + Requested 132 @@ -3256,150 +3312,150 @@ For more information on using this console, type %6. - + Send Coins 14 ../sendcoinsdialog.cpp764 - + Coin Control Features 90 - + automatically selected 120 - + Insufficient funds! 139 - + Quantity: 231 - + Bytes: 266 - + Amount: 314 - + Fee: 365 - + After Fee: 419 - + Change: 451 - + If this is activated, but the change address is empty or invalid, change will be sent to a newly generated address. 495 - + Custom change address 498 - + Transaction Fee: 704 - + Using the fallbackfee can result in sending a transaction that will take several hours or days (or never) to confirm. Consider choosing your fee manually or wait until you have validated the complete chain. 742 - + Warning: Fee estimation is currently not possible. 751 - + per kilobyte 833 - + Hide 780 - + Recommended: 892 - + Custom: 922 - + Send to multiple recipients at once 1137 - + Add &Recipient 1140 - + Clear all fields of the form. 1120 - + Inputs… 110 - + Choose… 718 - + Hide transaction fee settings 777 - + Specify a custom fee per kB (1,000 bytes) of the transaction's virtual size. Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 satoshis per kvB" for a transaction size of 500 virtual bytes (half of 1 kvB) would ultimately yield a fee of only 50 satoshis. 828 - + When there is less transaction volume than space in the blocks, miners as well as relaying nodes may enforce a minimum fee. Paying only this minimum fee is just fine, but be aware that this can result in a never confirming transaction once there is more demand for bitcoin transactions than the network can process. 863 - + A too low fee might result in a never confirming transaction (read the tooltip) 866 - + (Smart fee not initialized yet. This usually takes a few blocks…) 971 - + Confirmation time target: 997 - + Enable Replace-By-Fee 1055 - + With Replace-By-Fee (BIP-125) you can increase a transaction's fee after it is sent. Without this, a higher fee may be recommended to compensate for increased transaction delay risk. 1058 - + Clear &All 1123 - + Balance: 1178 - + Confirm the send action 1094 - + S&end 1097 @@ -3407,227 +3463,227 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - + Copy quantity 99 - + Copy amount 100 - + Copy fee 101 - + Copy after fee 102 - + Copy bytes 103 - + Copy change 104 - + %1 (%2 blocks) 176 - + Sign on device 206 "device" usually means a hardware wallet. - + Connect your hardware wallet first. 209 - + Set external signer script path in Options -> Wallet 213 "External signer" means using devices such as hardware wallets. - + Cr&eate Unsigned 216 - + Creates a Partially Signed Bitcoin Transaction (PSBT) for use with e.g. an offline %1 wallet, or a PSBT-compatible hardware wallet. 217 - + %1 to '%2' 320 - + %1 to %2 325 - + To review recipient list click "Show Details…" 392 - + Sign failed 455 - + External signer not found 460 "External signer" means using devices such as hardware wallets. - + External signer failure 466 "External signer" means using devices such as hardware wallets. - + Save Transaction Data 430 - + Partially Signed Transaction (Binary) 432 Expanded name of the binary PSBT file format. See: BIP 174. - + PSBT saved 440 Popup message when a PSBT has been saved to a file - + External balance: 713 - + or 388 - + You can increase the fee later (signals Replace-By-Fee, BIP-125). 370 - + Please, review your transaction proposal. This will produce a Partially Signed Bitcoin Transaction (PSBT) which you can save or copy and then sign with e.g. an offline %1 wallet, or a PSBT-compatible hardware wallet. 339 Text to inform a user attempting to create a transaction of their current options. At this stage, a user can only create a PSBT. This string is displayed when private keys are disabled and an external signer is not available. - + %1 from wallet '%2' 309 - + Do you want to create this transaction? 333 Message displayed when attempting to create a transaction. Cautionary text to prompt the user to verify that the displayed transaction details represent the transaction the user intends to create. - + Please, review your transaction. You can create and send this transaction or create a Partially Signed Bitcoin Transaction (PSBT), which you can save or copy and then sign with, e.g., an offline %1 wallet, or a PSBT-compatible hardware wallet. 344 Text to inform a user attempting to create a transaction of their current options. At this stage, a user can send their transaction or create a PSBT. This string is displayed when both private keys and PSBT controls are enabled. - + Please, review your transaction. 347 Text to prompt a user to review the details of the transaction they are attempting to send. - + Transaction fee 355 - + %1 kvB 360 PSBT transaction creation When reviewing a newly created PSBT (via Send flow), the transaction fee is shown, with "virtual size" of the transaction displayed for context - + Not signalling Replace-By-Fee, BIP-125. 372 - + Total Amount 385 - + Unsigned Transaction 409 PSBT copied Caption of "PSBT has been copied" messagebox - + The PSBT has been copied to the clipboard. You can also save it. 410 - + PSBT saved to disk 440 - + Confirm send coins 489 - + The recipient address is not valid. Please recheck. 737 - + The amount to pay must be larger than 0. 740 - + The amount exceeds your balance. 743 - + The total exceeds your balance when the %1 transaction fee is included. 746 - + Duplicate address found: addresses should only be used once each. 749 - + Transaction creation failed! 752 - + A fee higher than %1 is considered an absurdly high fee. 756 - + %1/kvB 832 869 883 - + Estimated to begin confirmation within %n block(s). - + Estimated to begin confirmation within %n block(s). - + Warning: Invalid Bitcoin address 982 - + Warning: Unknown change address 987 - + Confirm custom change address 990 - + The address you selected for change is not part of this wallet. Any or all funds in your wallet may be sent to this address. Are you sure? 990 - + (no label) 1011 @@ -3635,68 +3691,68 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - + A&mount: 151 - + Pay &To: 35 - + &Label: 128 - + Choose previously used address 60 - + The Bitcoin address to send the payment to 53 - + Alt+A 76 - + Paste address from clipboard 83 - + Alt+P 99 - + Remove this entry 106 - + The amount to send in the selected unit 166 - + The fee will be deducted from the amount being sent. The recipient will receive less bitcoins than you enter in the amount field. If multiple recipients are selected, the fee is split equally. 173 - + S&ubtract fee from amount 176 - + Use available balance 183 - + Message: 192 - + Enter a label for this address to add it to the list of used addresses 141 144 - + A message that was attached to the bitcoin: URI which will be stored with the transaction for your reference. Note: This message will not be sent over the Bitcoin network. 202 @@ -3704,11 +3760,11 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - + Send 151 - + Create Unsigned 153 @@ -3716,105 +3772,105 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - + Signatures - Sign / Verify a Message 14 - + &Sign Message 27 - + You can sign messages/agreements with your legacy (P2PKH) addresses to prove you can receive bitcoins sent to them. Be careful not to sign anything vague or random, as phishing attacks may try to trick you into signing your identity over to them. Only sign fully-detailed statements you agree to. 33 - + The Bitcoin address to sign the message with 51 - + Choose previously used address 58 274 - + Alt+A 68 284 - + Paste address from clipboard 78 - + Alt+P 88 - + Enter the message you want to sign here 100 103 - + Signature 110 - + Copy the current signature to the clipboard 140 - + Sign the message to prove you own this Bitcoin address 161 - + Sign &Message 164 - + Reset all sign message fields 178 - + Clear &All 181 338 - + &Verify Message 240 - + Enter the receiver's address, message (ensure you copy line breaks, spaces, tabs, etc. exactly) and signature below to verify the message. Be careful not to read more into the signature than what is in the signed message itself, to avoid being tricked by a man-in-the-middle attack. Note that this only proves the signing party receives with the address, it cannot prove sendership of any transaction! 246 - + The Bitcoin address the message was signed with 267 - + The signed message to verify 296 299 - + The signature given when the message was signed 306 309 - + Verify the message to ensure it was signed with the specified Bitcoin address 318 - + Verify &Message 321 - + Reset all verify message fields 335 - + Click "Sign Message" to generate signature 125 @@ -3822,59 +3878,59 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - + The entered address is invalid. 122 221 - + Please check the address and try again. 122 222 - + The entered address does not refer to a legacy (P2PKH) key. Message signing for SegWit and other non-P2PKH address types is not supported in this version of %1. Please check the address and try again. 129 227 - + Wallet unlock was cancelled. 137 - + No error 148 - + Private key for the entered address is not available. 151 - + Message signing failed. 154 - + Message signed. 166 - + The signature could not be decoded. 232 - + Please check the signature and try again. 233 240 - + The signature did not match the message digest. 239 - + Message verification failed. 245 - + Message verified. 216 @@ -3882,11 +3938,11 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - + (press q to shutdown and continue later) 175 - + press q to shutdown 176 @@ -3894,7 +3950,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - + kB/s 74 @@ -3902,185 +3958,185 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - + conflicted with a transaction with %1 confirmations - 39 + 34 Text explaining the current status of a transaction, shown in the status field of the details window for this transaction. This status represents an unconfirmed transaction that conflicts with a confirmed transaction. - + 0/unconfirmed, in memory pool - 46 + 41 Text explaining the current status of a transaction, shown in the status field of the details window for this transaction. This status represents an unconfirmed transaction that is in the memory pool. - + 0/unconfirmed, not in memory pool - 51 + 46 Text explaining the current status of a transaction, shown in the status field of the details window for this transaction. This status represents an unconfirmed transaction that is not in the memory pool. - + abandoned - 57 + 52 Text explaining the current status of a transaction, shown in the status field of the details window for this transaction. This status represents an abandoned transaction. - + %1/unconfirmed - 65 + 60 Text explaining the current status of a transaction, shown in the status field of the details window for this transaction. This status represents a transaction confirmed in at least one block, but less than 6 blocks. - + %1 confirmations - 70 + 65 Text explaining the current status of a transaction, shown in the status field of the details window for this transaction. This status represents a transaction confirmed in 6 or more blocks. - + Status - 120 + 115 - + Date - 123 + 118 - + Source - 130 + 125 - + Generated - 130 + 125 - + From - 135 - 149 + 130 + 143 - + unknown - 149 + 143 - + To - 150 - 170 - 236 + 144 + 164 + 221 - + own address - 152 - 243 + 146 + 228 - + label - 154 + 148 - + Credit - 190 - 202 - 250 - 280 - 340 + 184 + 196 + 235 + 265 + 325 - 192 - + 186 + matures in %n more block(s) - + matures in %n more block(s) - - not accepted - 194 - - - Debit - 248 - 274 - 337 - - - Total debit - 258 - - - Total credit - 259 - - - Transaction fee - 264 - - - Net amount - 286 - - - Message - 292 - 304 - - - Comment - 294 - - - Transaction ID - 296 - - - Transaction total size - 297 - - - Transaction virtual size - 298 - - Output index - 299 + not accepted + 188 - %1 (Certificate was not verified) - 315 + Debit + 233 + 259 + 322 - Merchant - 318 + Total debit + 243 - Generated coins must mature %1 blocks before they can be spent. When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours. - 326 + Total credit + 244 - Debug information - 334 + Transaction fee + 249 - Transaction - 342 + Net amount + 271 - Inputs - 345 + Message + 277 + 289 - Amount - 364 + Comment + 279 - true - 365 + Transaction ID + 281 + Transaction total size + 282 + + + Transaction virtual size + 283 + + + Output index + 284 + + + %1 (Certificate was not verified) + 300 + + + Merchant + 303 + + + Generated coins must mature %1 blocks before they can be spent. When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours. + 311 + + + Debug information + 319 + + + Transaction + 327 + + + Inputs + 330 + + + Amount + 349 + + + true + 350 + + false - 365 + 350 - + This pane shows a detailed description of the transaction 20 @@ -4088,7 +4144,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - + Details for %1 18 @@ -4096,87 +4152,87 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - + Date 257 - + Type 257 - + Label 257 - + Unconfirmed 316 - + Abandoned 319 - + Confirming (%1 of %2 recommended confirmations) 322 - + Confirmed (%1 confirmations) 325 - + Conflicted 328 - + Immature (%1 confirmations, will be available after %2) 331 - + Generated but not accepted 334 - + Received with 373 - + Received from 375 - + Sent to 378 - + Mined 380 - + (n/a) 416 - + (no label) 604 - + Transaction status. Hover over this field to show number of confirmations. 643 - + Date and time that the transaction was received. 645 - + Type of transaction. 647 - + User-defined intent/purpose of the transaction. 649 - + Amount removed from or added to balance. 651 @@ -4184,158 +4240,158 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - + All 66 82 - + Today 67 - + This week 68 - + This month 69 - + Last month 70 - + This year 71 - + Received with 83 - + Sent to 85 - + Mined 87 - + Other 88 - + Enter address, transaction id, or label to search 93 - + Min amount 97 - + Range… 72 - + &Copy address 160 - + Copy &label 161 - + Copy &amount 162 - + Copy transaction &ID 163 - + Copy &raw transaction 164 - + Copy full transaction &details 165 - + &Show transaction details 166 - + Increase transaction &fee 168 - + A&bandon transaction 171 - + &Edit address label 172 - + Show in %1 231 Transactions table context menu action to show the selected transaction in a third-party block explorer. %1 is a stand-in argument for the URL of the explorer. - + Export Transaction History 327 - + Comma separated file 330 Expanded name of the CSV file format. See: https://en.wikipedia.org/wiki/Comma-separated_values. - + Confirmed 339 - + Date 340 - + Type 341 - + Label 342 - + Address 343 - + ID 345 - + Exporting Failed 348 - + There was an error trying to save the transaction history to %1. 348 - + Exporting Successful 352 - + The transaction history was successfully saved to %1. 352 - + Range: 527 - + to 535 @@ -4343,39 +4399,39 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - + No wallet has been loaded. Go to File > Open Wallet to load a wallet. - OR - 45 - + Create a new wallet 50 - + Error 201 211 229 - + Unable to decode PSBT from clipboard (invalid base64) 201 - + Load Transaction Data 207 - + Partially Signed Transaction (*.psbt) 208 - + PSBT file must be smaller than 100 MiB 211 - + Unable to decode PSBT 229 @@ -4383,72 +4439,72 @@ Go to File > Open Wallet to load a wallet. - + Send Coins 218 231 - + Fee bump error 476 525 545 550 - + Increasing transaction fee failed 476 - + Do you want to increase the fee? 483 Asks a user if they would like to manually increase the fee of a transaction that has already been created. - + Current fee: 487 - + Increase: 491 - + New fee: 495 - + Warning: This may pay the additional fee by reducing change outputs or adding inputs, when necessary. It may add a new change output if one does not already exist. These changes may potentially leak privacy. 503 - + Confirm fee bump 508 - + Can't draft transaction. 525 - + PSBT copied 532 - + Fee-bump PSBT copied to clipboard 532 - + Can't sign transaction. 545 - + Could not commit transaction 550 - + Signer error 563 - + Can't display address 566 @@ -4456,40 +4512,40 @@ Go to File > Open Wallet to load a wallet. - + &Export 50 - + Export the data in the current tab to a file 51 - + Backup Wallet 214 - + Wallet Data 216 Name of the wallet data file format. - + Backup Failed 222 - + There was an error trying to save the wallet data to %1. 222 - + Backup Successful 226 - + The wallet data was successfully saved to %1. 226 - + Cancel 263 @@ -4497,1059 +4553,1067 @@ Go to File > Open Wallet to load a wallet. - + The %s developers - 206 + 208 - + %s failed to validate the -assumeutxo snapshot state. This indicates a hardware problem, or a bug in the software, or a bad software modification that allowed an invalid snapshot to be loaded. As a result of this, the node will shut down and stop using any state that was built on the snapshot, resetting the chain height from %d to %d. On the next restart, the node will resume syncing from %d without using any snapshot data. Please report this incident to %s, including how you obtained the snapshot. The invalid snapshot chainstate will be left on disk in case it is helpful in diagnosing the issue that caused this error. 12 - + %s request to listen on port %u. This port is considered "bad" and thus it is unlikely that any peer will connect to it. See doc/p2p-bad-ports.md for details and a full list. 15 - + Disk space for %s may not accommodate the block files. Approximately %u GB of data will be stored in this directory. - 38 - - - Distributed under the MIT software license, see the accompanying file %s or %s 40 - - Error loading wallet. Wallet requires blocks to be downloaded, and software does not currently support loading wallets while blocks are being downloaded out of order when using assumeutxo snapshots. Wallet should be able to load successfully after node sync reaches height %s - 55 - - - Error reading %s! Transaction data may be missing or incorrect. Rescanning wallet. - 59 - - - Error starting/committing db txn for wallet transactions removal process - 63 - - - Error: Dumpfile format record is incorrect. Got "%s", expected "format". - 71 - - - Error: Dumpfile identifier record is incorrect. Got "%s", expected "%s". - 72 - - - Error: Dumpfile version is not supported. This version of bitcoin-wallet only supports version 1 dumpfiles. Got dumpfile with version %s - 74 - - - Error: Unable to produce descriptors for this legacy wallet. Make sure to provide the wallet's passphrase if it is encrypted. - 90 - - - File %s already exists. If you are sure this is what you want, move it out of the way first. - 121 - - - Invalid or corrupt peers.dat (%s). If you believe this is a bug, please report it to %s. As a workaround, you can move the file (%s) out of the way (rename, move, or delete) to have a new one created on the next start. - 141 - - - Invalid value detected for '-wallet' or '-nowallet'. '-wallet' requires a string value, while '-nowallet' accepts only '1' to disable all wallets - 143 - - More than one onion bind address is provided. Using %s for the automatically created Tor onion service. - 154 + Distributed under the MIT software license, see the accompanying file %s or %s + 42 - No dump file provided. To use createfromdump, -dumpfile=<filename> must be provided. - 157 + Error loading wallet. Wallet requires blocks to be downloaded, and software does not currently support loading wallets while blocks are being downloaded out of order when using assumeutxo snapshots. Wallet should be able to load successfully after node sync reaches height %s + 57 - No dump file provided. To use dump, -dumpfile=<filename> must be provided. - 158 + Error reading %s! Transaction data may be missing or incorrect. Rescanning wallet. + 61 - Please contribute if you find %s useful. Visit %s for further information about the software. - 170 + Error starting/committing db txn for wallet transactions removal process + 65 - Prune configured below the minimum of %d MiB. Please use a higher number. - 172 + Error: Dumpfile format record is incorrect. Got "%s", expected "format". + 73 - Prune mode is incompatible with -reindex-chainstate. Use full -reindex instead. - 173 + Error: Dumpfile identifier record is incorrect. Got "%s", expected "%s". + 74 - Rename of '%s' -> '%s' failed. You should resolve this by manually moving or deleting the invalid snapshot directory %s, otherwise you will encounter the same error again on the next startup. - 179 + Error: Dumpfile version is not supported. This version of bitcoin-wallet only supports version 1 dumpfiles. Got dumpfile with version %s + 76 - SQLiteDatabase: Unknown sqlite wallet schema version %d. Only version %d is supported - 186 + Error: Unable to produce descriptors for this legacy wallet. Make sure to provide the wallet's passphrase if it is encrypted. + 92 - The block database contains a block which appears to be from the future. This may be due to your computer's date and time being set incorrectly. Only rebuild the block database if you are sure that your computer's date and time are correct - 208 + File %s already exists. If you are sure this is what you want, move it out of the way first. + 120 - The transaction amount is too small to send after the fee has been deducted - 215 + Invalid or corrupt peers.dat (%s). If you believe this is a bug, please report it to %s. As a workaround, you can move the file (%s) out of the way (rename, move, or delete) to have a new one created on the next start. + 140 - This is a pre-release test build - use at your own risk - do not use for mining or merchant applications - 219 + Invalid value detected for '-wallet' or '-nowallet'. '-wallet' requires a string value, while '-nowallet' accepts only '1' to disable all wallets + 142 - This is the maximum transaction fee you pay (in addition to the normal fee) to prioritize partial spend avoidance over regular coin selection. - 221 + More than one onion bind address is provided. Using %s for the automatically created Tor onion service. + 153 - This is the transaction fee you may discard if change is smaller than dust at this level - 223 + No dump file provided. To use createfromdump, -dumpfile=<filename> must be provided. + 156 - This is the transaction fee you may pay when fee estimates are not available. - 224 + No dump file provided. To use dump, -dumpfile=<filename> must be provided. + 157 - Total length of network version string (%i) exceeds maximum length (%i). Reduce the number or size of uacomments. - 226 + Please contribute if you find %s useful. Visit %s for further information about the software. + 169 - Unable to replay blocks. You will need to rebuild the database using -reindex-chainstate. - 242 + Prune configured below the minimum of %d MiB. Please use a higher number. + 174 - Unsupported category-specific logging level %1$s=%2$s. Expected %1$s=<category>:<loglevel>. Valid categories: %3$s. Valid loglevels: %4$s. - 254 + Prune mode is incompatible with -reindex-chainstate. Use full -reindex instead. + 175 - Unsupported chainstate database format found. Please restart with -reindex-chainstate. This will rebuild the chainstate database. - 255 + Rename of '%s' -> '%s' failed. You should resolve this by manually moving or deleting the invalid snapshot directory %s, otherwise you will encounter the same error again on the next startup. + 181 - Warning: Private keys detected in wallet {%s} with disabled private keys - 263 + SQLiteDatabase: Unknown sqlite wallet schema version %d. Only version %d is supported + 188 - Warning: We do not appear to fully agree with our peers! You may need to upgrade, or other nodes may need to upgrade. - 264 + The block database contains a block which appears to be from the future. This may be due to your computer's date and time being set incorrectly. Only rebuild the block database if you are sure that your computer's date and time are correct + 210 - Witness data for blocks after height %d requires validation. Please restart with -reindex. - 265 + The transaction amount is too small to send after the fee has been deducted + 217 - You need to rebuild the database using -reindex to go back to unpruned mode. This will redownload the entire blockchain - 266 + This is a pre-release test build - use at your own risk - do not use for mining or merchant applications + 221 + This is the maximum transaction fee you pay (in addition to the normal fee) to prioritize partial spend avoidance over regular coin selection. + 223 + + + This is the transaction fee you may discard if change is smaller than dust at this level + 225 + + + This is the transaction fee you may pay when fee estimates are not available. + 226 + + + Total length of network version string (%i) exceeds maximum length (%i). Reduce the number or size of uacomments. + 228 + + + Unable to replay blocks. You will need to rebuild the database using -reindex-chainstate. + 244 + + + Unsupported category-specific logging level %1$s=%2$s. Expected %1$s=<category>:<loglevel>. Valid categories: %3$s. Valid loglevels: %4$s. + 256 + + + Unsupported chainstate database format found. Please restart with -reindex-chainstate. This will rebuild the chainstate database. + 257 + + + Warning: Private keys detected in wallet {%s} with disabled private keys + 266 + + + Witness data for blocks after height %d requires validation. Please restart with -reindex. + 267 + + + You need to rebuild the database using -reindex to go back to unpruned mode. This will redownload the entire blockchain + 268 + + %s is set very high! 13 - + -maxmempool must be at least %d MB - 16 + 17 - + Cannot obtain a lock on directory %s. %s is probably already running. - 24 + 25 - + Cannot resolve -%s address: '%s' - 26 - - - Cannot set -forcednsseed to true when setting -dnsseed to false. 27 - - Cannot set -peerblockfilters without -blockfilterindex. + + Cannot set -forcednsseed to true when setting -dnsseed to false. 28 - + + Cannot set -peerblockfilters without -blockfilterindex. + 29 + + %s is set very high! Fees this large could be paid on a single transaction. 14 - - Cannot provide specific connections and have addrman find outgoing connections at the same time. - 25 - - - Error loading %s: External signer wallet being loaded without external signer support compiled - 48 - - - Error reading %s! All keys read correctly, but transaction data or address metadata may be missing or incorrect. - 58 - - - Error: Address book data in wallet cannot be identified to belong to migrated wallets - 64 - - - Error: Duplicate descriptors created during migration. Your wallet may be corrupted. - 75 - - - Error: Transaction %s in wallet cannot be identified to belong to migrated wallets - 86 - - - Failed to remove snapshot chainstate dir (%s). Manually remove it before restarting. - - 109 - - - Failed to rename invalid peers.dat file. Please move or delete it and try again. - 110 - - - Fee estimation failed. Fallbackfee is disabled. Wait a few blocks or enable %s. - 119 - - - Flushing block file to disk failed. This is likely the result of an I/O error. - 122 - - Flushing undo file to disk failed. This is likely the result of an I/O error. - 123 + Cannot provide specific connections and have addrman find outgoing connections at the same time. + 26 - Incompatible options: -dnsseed=1 was explicitly specified, but -onlynet forbids connections to IPv4/IPv6 - 125 + Error loading %s: External signer wallet being loaded without external signer support compiled + 51 - Invalid amount for %s=<amount>: '%s' (must be at least the minrelay fee of %s to prevent stuck transactions) - 138 + Error reading %s! All keys read correctly, but transaction data or address metadata may be missing or incorrect. + 60 - Maximum transaction weight is less than transaction weight without inputs - 149 + Error: Address book data in wallet cannot be identified to belong to migrated wallets + 66 - Maximum transaction weight is too low, can not accommodate change output - 150 + Error: Duplicate descriptors created during migration. Your wallet may be corrupted. + 77 - Option '-checkpoints' is set but checkpoints were removed. This option has no effect. - 163 + Error: Transaction %s in wallet cannot be identified to belong to migrated wallets + 88 - Option '-maxorphantx' is set but no longer has any effect (see release notes). Please remove it from your configuration. - 164 + Failed to remove snapshot chainstate dir (%s). Manually remove it before restarting. + + 110 - Options '-datacarrier' or '-datacarriersize' are set but are marked as deprecated. They will be removed in a future version. - 165 + Failed to rename invalid peers.dat file. Please move or delete it and try again. + 111 - Outbound connections restricted to CJDNS (-onlynet=cjdns) but -cjdnsreachable is not provided - 166 + Fee estimation failed. Fallbackfee is disabled. Wait a few blocks or enable %s. + 118 - Outbound connections restricted to Tor (-onlynet=onion) but the proxy for reaching the Tor network is explicitly forbidden: -onion=0 - 167 + Flushing block file to disk failed. This is likely the result of an I/O error. + 121 - Outbound connections restricted to Tor (-onlynet=onion) but the proxy for reaching the Tor network is not provided: none of -proxy, -onion or -listenonion is given - 168 + Flushing undo file to disk failed. This is likely the result of an I/O error. + 122 - Outbound connections restricted to i2p (-onlynet=i2p) but -i2psam is not provided - 169 + Incompatible options: -dnsseed=1 was explicitly specified, but -onlynet forbids connections to IPv4/IPv6 + 124 - Prune: last wallet synchronisation goes beyond pruned data. You need to -reindex (download the whole blockchain again in case of a pruned node) - 175 + Invalid amount for %s=<amount>: '%s' (must be at least the minrelay fee of %s to prevent stuck transactions) + 137 - Rename of '%s' -> '%s' failed. Cannot clean up the background chainstate leveldb directory. - 178 + Maximum transaction weight is less than transaction weight without inputs + 148 - Specified -blockmaxweight (%d) exceeds consensus maximum block weight (%d) - 194 + Maximum transaction weight is too low, can not accommodate change output + 149 - Specified -blockreservedweight (%d) exceeds consensus maximum block weight (%d) - 195 + Option '-checkpoints' is set but checkpoints were removed. This option has no effect. + 162 - Specified -blockreservedweight (%d) is lower than minimum safety value of (%d) - 196 + Outbound connections restricted to CJDNS (-onlynet=cjdns) but -cjdnsreachable is not provided + 165 - The combination of the pre-selected inputs and the wallet automatic inputs selection exceeds the transaction maximum weight. Please try sending a smaller amount or manually consolidating your wallet's UTXOs - 209 + Outbound connections restricted to Tor (-onlynet=onion) but the proxy for reaching the Tor network is explicitly forbidden: -onion=0 + 166 - The inputs size exceeds the maximum weight. Please try sending a smaller amount or manually consolidating your wallet's UTXOs - 210 + Outbound connections restricted to Tor (-onlynet=onion) but the proxy for reaching the Tor network is not provided: none of -proxy, -onion or -listenonion is given + 167 - The preselected coins total amount does not cover the transaction target. Please allow other inputs to be automatically selected or include more coins manually - 211 + Outbound connections restricted to i2p (-onlynet=i2p) but -i2psam is not provided + 168 - UTXO snapshot failed to validate. Restart to resume normal initial block download, or try loading a different snapshot. - 235 + Prune: last wallet synchronisation goes beyond pruned data. You need to -reindex (download the whole blockchain again in case of a pruned node) + 177 - Unconfirmed UTXOs are available, but spending them creates a chain of transactions that will be rejected by the mempool - 244 + Rename of '%s' -> '%s' failed. Cannot clean up the background chainstate leveldb directory. + 180 + Specified -blockmaxweight (%d) exceeds consensus maximum block weight (%d) + 196 + + + Specified -blockreservedweight (%d) exceeds consensus maximum block weight (%d) + 197 + + + Specified -blockreservedweight (%d) is lower than minimum safety value of (%d) + 198 + + + The combination of the pre-selected inputs and the wallet automatic inputs selection exceeds the transaction maximum weight. Please try sending a smaller amount or manually consolidating your wallet's UTXOs + 211 + + + The inputs size exceeds the maximum weight. Please try sending a smaller amount or manually consolidating your wallet's UTXOs + 212 + + + The preselected coins total amount does not cover the transaction target. Please allow other inputs to be automatically selected or include more coins manually + 213 + + + UTXO snapshot failed to validate. Restart to resume normal initial block download, or try loading a different snapshot. + 237 + + + Unconfirmed UTXOs are available, but spending them creates a chain of transactions that will be rejected by the mempool + 246 + + Unexpected legacy entry in descriptor wallet found. Loading wallet %s The wallet might have been tampered with or created with malicious intent. - 245 - - - Your computer's date and time appear to be more than %d minutes out of sync with the network, this may lead to consensus failure. After you've confirmed your computer's clock, this message should no longer appear when you restart your node. Without a restart, it should stop showing automatically after you've connected to a sufficient number of new outbound peers, which may take some time. You can inspect the `timeoffset` field of the `getpeerinfo` and `getnetworkinfo` RPC methods to get more info. - 267 - - - -Unable to cleanup failed migration - 268 - - - -Unable to restore backup of wallet. - 269 - - - default wallet - 271 - - - whitebind may only be used for incoming connections ("out" was passed) - 272 - - - -paytxfee is deprecated and will be fully removed in v31.0. - 17 - - - A fatal internal error occurred, see debug.log for details: - 18 - - - Assumeutxo data not found for the given blockhash '%s'. - 19 - - - Block verification was interrupted - 20 - - - Can't spend unconfirmed version %d pre-selected input with a version 3 tx - 21 - - - Can't spend unconfirmed version 3 pre-selected input with a version %d tx - 22 - - - Cannot add WalletDescriptor to a non-descriptor wallet - 23 - - - Cannot write to directory '%s'; check permissions. - 29 - - - Config setting for %s only applied on %s network when in [%s] section. - 30 - - - Copyright (C) %i-%i - 31 - - - Corrupt block found indicating potential hardware failure. - 32 - - - Corrupted block database detected - 33 - - - Could not find asmap file %s - 34 - - - Could not generate scriptPubKeys (cache is empty) - 35 - - - Could not parse asmap file %s - 36 - - - Could not top up scriptPubKeys - 37 - - - Disk space is too low! - 39 - - - Done loading - 42 - - - Dump file %s does not exist. - 43 - - - Elliptic curve cryptography sanity check failure. %s is shutting down. - 44 - - - Error creating %s - 45 - - - Error initializing block database - 46 - - - Error loading %s - 47 - - - Error loading %s: Private keys can only be disabled during creation - 49 - - - Error loading %s: Wallet corrupted - 50 - - - Error loading %s: Wallet requires newer version of %s - 52 - - - Error loading block database - 53 - - - Error loading databases - 54 - - - Error opening block database - 56 - - - Error opening coins database - 57 - - - Error reading configuration file: %s - 60 - - - Error reading from database, shutting down. - 61 - - - Error reading next record from wallet database - 62 - - - Error: Cannot extract destination from the generated scriptpubkey - 65 - - - Error: Couldn't create cursor into database - 68 - - - Error: Disk space is low for %s - 69 - - - Error: Dumpfile checksum does not match. Computed %s, expected %s - 70 - - - Error: Failed to create new watchonly wallet - 76 - - - Error: Got key that was not hex: %s - 77 - - - Error: Got value that was not hex: %s - 78 - - - Error: Keypool ran out, please call keypoolrefill first - 79 - - - Error: Missing checksum - 80 - - - Error: No %s addresses available. - 81 - - - Error: Not all address book records were migrated - 82 - - - Error: Not all transaction records were migrated - 83 - - - Error: This wallet already uses SQLite - 84 - - - Error: This wallet is already a descriptor wallet - 85 - - - Error: Unable to begin reading all records in the database - 87 - - - Error: Unable to make a backup of your wallet - 88 - - - Error: Unable to parse version %u as a uint32_t - 89 - - - Error: Unable to read all records in the database - 91 - - - Error: Unable to read wallet's best block locator record - 92 - - - Error: Unable to remove watchonly address book data - 93 - - - Error: Unable to write data to disk for wallet %s - 94 - - - Error: Unable to write record to new wallet - 95 - - - Error: Unable to write solvable wallet best block locator record - 96 - - - Error: Unable to write watchonly wallet best block locator record - 97 - - - Error: database transaction cannot be executed for wallet %s - 100 - - - Failed to acquire rescan reserver during wallet initialization - 101 - - - Failed to close block undo file. - 103 - - - Failed to close file when writing block. - 104 - - - Failed to connect best block (%s). - 105 - - - Failed to disconnect block. - 106 - - - Failed to listen on any port. Use -listen=0 if you want this. - 107 - - - Failed to read block. - 108 - - - Failed to rescan the wallet during initialization - 111 - - - Failed to verify database - 113 - - - Failed to write block. - 114 - - - Failed to write to block index database. - 115 - - - Failed to write to coin database. - 116 - - - Failed to write undo data. - 117 - - - Failure removing transaction: %s - 118 - - - Fee rate (%s) is lower than the minimum fee rate setting (%s) - 120 - - - Ignoring duplicate -wallet %s. - 124 - - - Incorrect or no genesis block found. Wrong datadir for network? - 126 - - - Initialization sanity check failed. %s is shutting down. - 127 - - - Input not found or already spent - 128 - - - Insufficient dbcache for block verification - 129 - - - Insufficient funds - 130 - - - Invalid -i2psam address or hostname: '%s' - 131 - - - Invalid -onion address or hostname: '%s' - 132 - - - Invalid -proxy address or hostname: '%s' - 134 - - - Invalid P2P permission: '%s' - 135 - - - Invalid amount for %s=<amount>: '%s' (must be at least %s) - 137 - - - Invalid amount for %s=<amount>: '%s' - 136 - - - Invalid amount for -%s=<amount>: '%s' - 139 - - - Invalid netmask specified in -whitelist: '%s' - 140 - - - Invalid port specified in %s: '%s' - 142 - - - Listening for incoming connections failed (listen returned error %s) - 144 - - - Loading P2P addresses… - 145 - - - Loading banlist… - 146 - - - Loading block index… - 147 - - - Loading wallet… - 148 - - - Maximum transaction weight must be between %d and %d - 151 - - - Missing amount - 152 - - - Missing solving data for estimating transaction size - 153 - - - Need to specify a port with -whitebind: '%s' - 155 - - - No addresses available - 156 - - - Not found pre-selected input %s - 160 - - - Not solvable pre-selected input %s - 161 - - - Only direction was set, no permissions: '%s' - 162 - - - Prune cannot be configured with a negative value. - 171 - - - Prune mode is incompatible with -txindex. - 174 - - - Pruning blockstore… - 176 - - - Reducing -maxconnections from %d to %d, because of system limitations. - 177 - - - Replaying blocks… - 180 - - - Rescanning… - 181 - - - SQLiteDatabase: Failed to execute statement to verify database: %s - 182 - - - SQLiteDatabase: Failed to prepare statement to verify database: %s - 183 - - - SQLiteDatabase: Failed to read database verification error: %s - 184 - - - SQLiteDatabase: Unexpected application id. Expected %u, got %u - 185 - - - Section [%s] is not recognized. - 187 - - - Signer did not echo address - 190 - - - Signer echoed unexpected address %s - 191 - - - Signer returned error: %s - 192 - - - Signing transaction failed - 193 - - - Specified -walletdir "%s" does not exist - 197 - - - Specified -walletdir "%s" is a relative path - 198 - - - Specified -walletdir "%s" is not a directory - 199 - - - Specified blocks directory "%s" does not exist. - 200 - - - Specified data directory "%s" does not exist. - 201 - - - Starting network threads… - 202 - - - System error while flushing: %s - 203 - - - System error while loading external block file: %s - 204 - - - System error while saving block to disk: %s - 205 - - - The %s path uses exFAT, which is known to have intermittent corruption problems on macOS. Move this directory to a different filesystem to avoid data loss. - 207 - - - The source code is available from %s. - 212 - - - The specified config file %s does not exist - 213 - - - The transaction amount is too small to pay the fee - 214 - - - The transactions removal process can only be executed within a db txn - 216 - - - The wallet will avoid paying less than the minimum relay fee. - 217 - - - There is no ScriptPubKeyManager for this address - 218 - - - This is experimental software. - 220 - - - This is the minimum transaction fee you pay on every transaction. - 222 - - - This is the transaction fee you will pay if you send a transaction. - 225 - - - Transaction %s does not belong to this wallet - 227 - - - Transaction amount too small - 228 - - - Transaction amounts must not be negative - 229 - - - Transaction change output index out of range - 230 - - - Transaction must have at least one recipient - 231 - - - Transaction needs a change address, but we can't generate it. - 232 - - - Transaction too large - 234 - - - Unable to bind to %s on this computer (bind returned error %s) - 236 - - - Unable to bind to %s on this computer. %s is probably already running. - 237 - - - Unable to create the PID file '%s': %s - 238 - - - Unable to find UTXO for external input - 239 - - - Unable to open %s for writing - 240 - - - Unable to parse -maxuploadtarget: '%s' - 241 - - - Unable to start HTTP server. See debug log for details. - 243 - - - Unknown -blockfilterindex value %s. - 246 - - - Unknown address type '%s' 247 - - Unknown change type '%s' - 248 + + Your computer's date and time appear to be more than %d minutes out of sync with the network, this may lead to consensus failure. After you've confirmed your computer's clock, this message should no longer appear when you restart your node. Without a restart, it should stop showing automatically after you've connected to a sufficient number of new outbound peers, which may take some time. You can inspect the `timeoffset` field of the `getpeerinfo` and `getnetworkinfo` RPC methods to get more info. + 269 - - Unknown network specified in -onlynet: '%s' - 249 - - - Unknown new rules activated (versionbit %i) - 250 - - - Unrecognised option "%s" provided in -test=<option>. - 251 - - - Unsupported global logging level %s=%s. Valid values: %s. - 256 - - - Wallet file creation failed: %s - 261 - - - acceptstalefeeestimates is not supported on %s chain. + + +Unable to cleanup failed migration 270 - - Unsupported logging category %s=%s. - 257 + + +Unable to restore backup of wallet. + 271 - - Error loading %s: Wallet is a legacy wallet. Please migrate to a descriptor wallet using the migration tool (migratewallet RPC). - 51 + + default wallet + 273 - - Error: Dumpfile specifies an unsupported database format (%s). Only sqlite database dumps are supported - 73 + + whitebind may only be used for incoming connections ("out" was passed) + 274 - - Failed to calculate bump fees, because unconfirmed UTXOs depend on an enormous cluster of unconfirmed transactions. + + -paytxfee is deprecated and will be fully removed in v31.0. + 18 + + + A fatal internal error occurred, see debug.log for details: + 20 + + + Assumeutxo data not found for the given blockhash '%s'. + 21 + + + Block verification was interrupted + 22 + + + Can't spend unconfirmed version %d pre-selected input with a version 3 tx + 23 + + + Can't spend unconfirmed version 3 pre-selected input with a version %d tx + 24 + + + Cannot write to directory '%s'; check permissions. + 30 + + + Config setting for %s only applied on %s network when in [%s] section. + 31 + + + Copyright (C) %i-%i + 32 + + + Corrupt block found indicating potential hardware failure. + 33 + + + Corrupted block database detected + 34 + + + Could not find asmap file %s + 35 + + + Could not generate scriptPubKeys (cache is empty) + 36 + + + Could not parse asmap file %s + 37 + + + Could not top up scriptPubKeys + 38 + + + Disk space is too low! + 41 + + + Done loading + 44 + + + Dump file %s does not exist. + 45 + + + Elliptic curve cryptography sanity check failure. %s is shutting down. + 47 + + + Error initializing block database + 49 + + + Error loading %s + 50 + + + Error loading %s: Wallet corrupted + 52 + + + Error loading %s: Wallet requires newer version of %s + 54 + + + Error loading block database + 55 + + + Error loading databases + 56 + + + Error opening block database + 58 + + + Error opening coins database + 59 + + + Error reading configuration file: %s + 62 + + + Error reading from database, shutting down. + 63 + + + Error reading next record from wallet database + 64 + + + Error: Cannot extract destination from the generated scriptpubkey + 67 + + + Error: Couldn't create cursor into database + 70 + + + Error: Disk space is low for %s + 71 + + + Error: Dumpfile checksum does not match. Computed %s, expected %s + 72 + + + Error: Failed to create new watchonly wallet + 78 + + + Error: Got key that was not hex: %s + 79 + + + Error: Got value that was not hex: %s + 80 + + + Error: Keypool ran out, please call keypoolrefill first + 81 + + + Error: Missing checksum + 82 + + + Error: No %s addresses available. + 83 + + + Error: Not all address book records were migrated + 84 + + + Error: Not all transaction records were migrated + 85 + + + Error: This wallet already uses SQLite + 86 + + + Error: This wallet is already a descriptor wallet + 87 + + + Error: Unable to begin reading all records in the database + 89 + + + Error: Unable to make a backup of your wallet + 90 + + + Error: Unable to parse version %u as a uint32_t + 91 + + + Error: Unable to read all records in the database + 93 + + + Error: Unable to read wallet's best block locator record + 94 + + + Error: Unable to remove watchonly address book data + 95 + + + Error: Unable to write data to disk for wallet %s + 96 + + + Error: Unable to write record to new wallet + 97 + + + Error: Unable to write solvable wallet best block locator record + 98 + + + Error: Unable to write watchonly wallet best block locator record + 99 + + + Error: database transaction cannot be executed for wallet %s 102 - - Transaction requires one destination of non-zero value, a non-zero feerate, or a pre-selected input + + Failed to acquire rescan reserver during wallet initialization + 103 + + + Failed to close block undo file. + 105 + + + Failed to close file when writing block. + 106 + + + Failed to disconnect block. + 107 + + + Failed to listen on any port. Use -listen=0 if you want this. + 108 + + + Failed to read block. + 109 + + + Failed to rescan the wallet during initialization + 112 + + + Failed to verify database + 114 + + + Failed to write block. + 115 + + + Failed to write undo data. + 116 + + + Failure removing transaction: %s + 117 + + + Fee rate (%s) is lower than the minimum fee rate setting (%s) + 119 + + + Ignoring duplicate -wallet %s. + 123 + + + Incorrect or no genesis block found. Wrong datadir for network? + 125 + + + Initialization sanity check failed. %s is shutting down. + 126 + + + Input not found or already spent + 127 + + + Insufficient dbcache for block verification + 128 + + + Insufficient funds + 129 + + + Invalid -i2psam address or hostname: '%s' + 130 + + + Invalid -onion address or hostname: '%s' + 131 + + + Invalid -proxy address or hostname: '%s' + 133 + + + Invalid P2P permission: '%s' + 134 + + + Invalid amount for %s=<amount>: '%s' (must be at least %s) + 136 + + + Invalid amount for %s=<amount>: '%s' + 135 + + + -asmap requires a file path. Use -asmap=<file>. + 16 + + + A %zu MiB dbcache may be too large for a system memory of only %zu MiB. + 19 + + + Creating wallet… + 39 + + + Duplicate binding configuration for address %s. Please check your -bind, -bind=...=onion and -whitebind settings. + 46 + + + Error creating %s: Could not write version metadata. + 48 + + + Invalid amount for -%s=<amount>: '%s' + 138 + + + Invalid netmask specified in -whitelist: '%s' + 139 + + + Invalid port specified in %s: '%s' + 141 + + + Listening for incoming connections failed (listen returned error %s) + 143 + + + Loading P2P addresses… + 144 + + + Loading banlist… + 145 + + + Loading block index… + 146 + + + Loading wallet… + 147 + + + Maximum transaction weight must be between %d and %d + 150 + + + Missing amount + 151 + + + Missing solving data for estimating transaction size + 152 + + + Need to specify a port with -whitebind: '%s' + 154 + + + No addresses available + 155 + + + Not found pre-selected input %s + 159 + + + Not solvable pre-selected input %s + 160 + + + Only direction was set, no permissions: '%s' + 161 + + + Option '-limitancestorsize' is given but ancestor size limits have been replaced with cluster size limits (see -limitclustersize). This option has no effect. + 163 + + + Option '-limitdescendantsize' is given but descendant size limits have been replaced with cluster size limits (see -limitclustersize). This option has no effect. + 164 + + + Private broadcast of own transactions requested (-privatebroadcast) and -proxyrandomize is disabled. Tor circuits for private broadcast connections may be correlated to other connections over Tor. For maximum privacy set -proxyrandomize=1. + 170 + + + Private broadcast of own transactions requested (-privatebroadcast), but -connect is also configured. They are incompatible because the private broadcast needs to open new connections to randomly chosen Tor or I2P peers. Consider using -maxconnections=0 -addnode=... instead + 171 + + + Private broadcast of own transactions requested (-privatebroadcast), but none of Tor or I2P networks is reachable + 172 + + + Prune cannot be configured with a negative value. + 173 + + + Prune mode is incompatible with -txindex. + 176 + + + Pruning blockstore… + 178 + + + Reducing -maxconnections from %d to %d, because of system limitations. + 179 + + + Replaying blocks… + 182 + + + Rescanning… + 183 + + + SQLiteDatabase: Failed to execute statement to verify database: %s + 184 + + + SQLiteDatabase: Failed to prepare statement to verify database: %s + 185 + + + SQLiteDatabase: Failed to read database verification error: %s + 186 + + + SQLiteDatabase: Unexpected application id. Expected %u, got %u + 187 + + + Section [%s] is not recognized. + 189 + + + Signer did not echo address + 192 + + + Signer echoed unexpected address %s + 193 + + + Signer returned error: %s + 194 + + + Signing transaction failed + 195 + + + Specified -walletdir "%s" does not exist + 199 + + + Specified -walletdir "%s" is a relative path + 200 + + + Specified -walletdir "%s" is not a directory + 201 + + + Specified blocks directory "%s" does not exist. + 202 + + + Specified data directory "%s" does not exist. + 203 + + + Starting network threads… + 204 + + + System error while flushing: %s + 205 + + + System error while loading external block file: %s + 206 + + + System error while saving block to disk: %s + 207 + + + The %s path uses exFAT, which is known to have intermittent corruption problems on macOS. Move this directory to a different filesystem to avoid data loss. + 209 + + + The source code is available from %s. + 214 + + + The specified config file %s does not exist + 215 + + + The transaction amount is too small to pay the fee + 216 + + + The transactions removal process can only be executed within a db txn + 218 + + + The wallet will avoid paying less than the minimum relay fee. + 219 + + + There is no ScriptPubKeyManager for this address + 220 + + + This is experimental software. + 222 + + + This is the minimum transaction fee you pay on every transaction. + 224 + + + This is the transaction fee you will pay if you send a transaction. + 227 + + + Transaction %s does not belong to this wallet + 229 + + + Transaction amount too small + 230 + + + Transaction amounts must not be negative + 231 + + + Transaction change output index out of range + 232 + + + Transaction must have at least one recipient 233 + + Transaction needs a change address, but we can't generate it. + 234 + + + Transaction too large + 236 + + + Unable to bind to %s on this computer (bind returned error %s) + 238 + + + Unable to bind to %s on this computer. %s is probably already running. + 239 + + + Unable to create the PID file '%s': %s + 240 + + + Unable to find UTXO for external input + 241 + + + Unable to open %s for writing + 242 + + + Unable to parse -maxuploadtarget: '%s' + 243 + + + Unable to start HTTP server. See debug log for details. + 245 + + + Unknown -blockfilterindex value %s. + 248 + + + Unknown address type '%s' + 249 + + Unknown change type '%s' + 250 + + + Unknown network specified in -onlynet: '%s' + 251 + + + Unknown new rules activated (versionbit %i) + 252 + + + Unrecognised option "%s" provided in -test=<option>. + 253 + + + Unsupported global logging level %s=%s. Valid values: %s. + 258 + + + Wallet file creation failed: %s + 263 + + + Warning: Found invalid chain more than 6 blocks longer than our best chain. This could be due to database corruption or consensus incompatibility with peers. + 265 + + + acceptstalefeeestimates is not supported on %s chain. + 272 + + + Unsupported logging category %s=%s. + 259 + + + Error loading %s: Wallet is a legacy wallet. Please migrate to a descriptor wallet using the migration tool (migratewallet RPC). + 53 + + + Error: Dumpfile specifies an unsupported database format (%s). Only sqlite database dumps are supported + 75 + + + Failed to calculate bump fees, because unconfirmed UTXOs depend on an enormous cluster of unconfirmed transactions. + 104 + + + Transaction requires one destination of non-zero value, a non-zero feerate, or a pre-selected input + 235 + + Unrecognized descriptor found. Loading wallet %s The wallet might have been created on a newer version. Please try running the latest software version. - 252 - - - Do you want to rebuild the databases now? - 41 - - - Error: Could not add watchonly tx %s to watchonly wallet - 66 - - - Error: Could not delete watchonly transactions. - 67 - - - Error: Wallet does not exist - 98 - - - Error: cannot remove legacy wallet records - 99 - - - Failed to start indexes, shutting down… - 112 - - - Invalid -proxy address or hostname, ends with '=': '%s' - 133 - - - Not enough file descriptors available. %d available, %d required. - 159 - - - Unrecognized network in -proxy='%s': '%s' - 253 - - - User Agent comment (%s) contains unsafe characters. - 258 - - - Verifying blocks… - 259 - - - Verifying wallet(s)… - 260 - - - Wallet needed to be rewritten: restart %s to complete - 262 + 254 - Settings file could not be read - 188 + Do you want to rebuild the databases now? + 43 + Error: Could not add watchonly tx %s to watchonly wallet + 68 + + + Error: Could not delete watchonly transactions. + 69 + + + Error: Wallet does not exist + 100 + + + Error: cannot remove legacy wallet records + 101 + + + Failed to start indexes, shutting down… + 113 + + + Invalid -proxy address or hostname, ends with '=': '%s' + 132 + + + Not enough file descriptors available. %d available, %d required. + 158 + + + Unrecognized network in -proxy='%s': '%s' + 255 + + + User Agent comment (%s) contains unsafe characters. + 260 + + + Verifying blocks… + 261 + + + Verifying wallet(s)… + 262 + + + Wallet needed to be rewritten: restart %s to complete + 264 + + + Settings file could not be read + 190 + + Settings file could not be written - 189 + 191