diff --git a/src/qt/bitcoinstrings.cpp b/src/qt/bitcoinstrings.cpp index 1b54ca08e8..eaf4db5f34 100644 --- a/src/qt/bitcoinstrings.cpp +++ b/src/qt/bitcoinstrings.cpp @@ -40,6 +40,12 @@ QT_TRANSLATE_NOOP("bitcoin-core", "" "upgrading to support pre-split keypool. Please use version %i or no version " "specified."), QT_TRANSLATE_NOOP("bitcoin-core", "" +"Change output could not be blinded as there are no blinded inputs and no " +"other blinded outputs."), +QT_TRANSLATE_NOOP("bitcoin-core", "" +"Could not locate mainchain RPC credentials. No authentication cookie could " +"be found, and no mainchainrpcpassword is set in the configuration file (%s)"), +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", "" @@ -132,9 +138,6 @@ QT_TRANSLATE_NOOP("bitcoin-core", "" "No wallet file format provided. To use createfromdump, -format= must " "be provided."), QT_TRANSLATE_NOOP("bitcoin-core", "" -"Option '-upnp' is set but UPnP support was dropped in version 29.0. Consider " -"using '-natpmp' instead."), -QT_TRANSLATE_NOOP("bitcoin-core", "" "Outbound connections restricted to CJDNS (-onlynet=cjdns) but -" "cjdnsreachable is not provided"), QT_TRANSLATE_NOOP("bitcoin-core", "" @@ -213,6 +216,9 @@ QT_TRANSLATE_NOOP("bitcoin-core", "" "Total length of network version string (%i) exceeds maximum length (%i). " "Reduce the number or size of uacomments."), QT_TRANSLATE_NOOP("bitcoin-core", "" +"Transaction output could not be blinded as there are no blinded inputs and " +"no other blinded outputs."), +QT_TRANSLATE_NOOP("bitcoin-core", "" "Transaction requires one destination of non-0 value, a non-0 feerate, or a " "pre-selected input"), QT_TRANSLATE_NOOP("bitcoin-core", "" @@ -243,15 +249,6 @@ QT_TRANSLATE_NOOP("bitcoin-core", "" "Unsupported chainstate database format found. Please restart with -reindex-" "chainstate. This will rebuild the chainstate database."), QT_TRANSLATE_NOOP("bitcoin-core", "" -"Wallet created successfully. The legacy wallet type is being deprecated and " -"support for creating and opening legacy wallets will be removed in the " -"future."), -QT_TRANSLATE_NOOP("bitcoin-core", "" -"Wallet loaded successfully. The legacy wallet type is being deprecated and " -"support for creating and opening legacy wallets will be removed in the " -"future. Legacy wallets can be migrated to a descriptor wallet with " -"migratewallet."), -QT_TRANSLATE_NOOP("bitcoin-core", "" "Warning: Dumpfile wallet format \"%s\" does not match command line specified " "format \"%s\"."), QT_TRANSLATE_NOOP("bitcoin-core", "" @@ -285,6 +282,7 @@ QT_TRANSLATE_NOOP("bitcoin-core", "%s is set very high!"), QT_TRANSLATE_NOOP("bitcoin-core", "-maxmempool must be at least %d MB"), 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", "Awaiting mainchain RPC warmup"), QT_TRANSLATE_NOOP("bitcoin-core", "Block verification was interrupted"), QT_TRANSLATE_NOOP("bitcoin-core", "Cannot obtain a lock on directory %s. %s is probably already running."), QT_TRANSLATE_NOOP("bitcoin-core", "Cannot resolve -%s address: '%s'"), @@ -383,10 +381,12 @@ QT_TRANSLATE_NOOP("bitcoin-core", "Missing amount"), QT_TRANSLATE_NOOP("bitcoin-core", "Missing solving data for estimating transaction size"), QT_TRANSLATE_NOOP("bitcoin-core", "Need to specify a port with -whitebind: '%s'"), QT_TRANSLATE_NOOP("bitcoin-core", "No addresses available"), +QT_TRANSLATE_NOOP("bitcoin-core", "No asset provided for recipient"), QT_TRANSLATE_NOOP("bitcoin-core", "Not enough file descriptors available. %d available, %d required."), 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", "Peg-in input has invalid proof."), QT_TRANSLATE_NOOP("bitcoin-core", "Prune cannot be configured with a negative value."), QT_TRANSLATE_NOOP("bitcoin-core", "Prune mode is incompatible with -txindex."), QT_TRANSLATE_NOOP("bitcoin-core", "Pruning blockstore…"), @@ -397,7 +397,6 @@ QT_TRANSLATE_NOOP("bitcoin-core", "SQLiteDatabase: Failed to execute statement t QT_TRANSLATE_NOOP("bitcoin-core", "SQLiteDatabase: Failed to prepare statement to verify database: %s"), QT_TRANSLATE_NOOP("bitcoin-core", "SQLiteDatabase: Failed to read database verification error: %s"), QT_TRANSLATE_NOOP("bitcoin-core", "SQLiteDatabase: Unexpected application id. Expected %u, got %u"), -QT_TRANSLATE_NOOP("bitcoin-core", "Section [%s] is not recognized."), QT_TRANSLATE_NOOP("bitcoin-core", "Settings file could not be read"), QT_TRANSLATE_NOOP("bitcoin-core", "Settings file could not be written"), QT_TRANSLATE_NOOP("bitcoin-core", "Signer did not echo address"), @@ -426,11 +425,14 @@ QT_TRANSLATE_NOOP("bitcoin-core", "Transaction %s does not belong to this wallet QT_TRANSLATE_NOOP("bitcoin-core", "Transaction amount too small"), QT_TRANSLATE_NOOP("bitcoin-core", "Transaction amounts must not be negative"), QT_TRANSLATE_NOOP("bitcoin-core", "Transaction change output index out of range"), +QT_TRANSLATE_NOOP("bitcoin-core", "Transaction is missing an output for input asset %s"), QT_TRANSLATE_NOOP("bitcoin-core", "Transaction must have at least one recipient"), QT_TRANSLATE_NOOP("bitcoin-core", "Transaction needs a change address, but we can't generate it."), QT_TRANSLATE_NOOP("bitcoin-core", "Transaction too large"), +QT_TRANSLATE_NOOP("bitcoin-core", "Unable to allocate memory for -maxsigcachesize: '%s' MiB"), QT_TRANSLATE_NOOP("bitcoin-core", "Unable to bind to %s on this computer (bind returned error %s)"), QT_TRANSLATE_NOOP("bitcoin-core", "Unable to bind to %s on this computer. %s is probably already running."), +QT_TRANSLATE_NOOP("bitcoin-core", "Unable to blind the transaction properly. This should not happen."), QT_TRANSLATE_NOOP("bitcoin-core", "Unable to create the PID file '%s': %s"), QT_TRANSLATE_NOOP("bitcoin-core", "Unable to find UTXO for external input"), QT_TRANSLATE_NOOP("bitcoin-core", "Unable to generate initial keys"), @@ -448,6 +450,7 @@ QT_TRANSLATE_NOOP("bitcoin-core", "Unrecognised option \"%s\" provided in -test= QT_TRANSLATE_NOOP("bitcoin-core", "Unsupported global logging level %s=%s. Valid values: %s."), QT_TRANSLATE_NOOP("bitcoin-core", "Unsupported logging category %s=%s."), QT_TRANSLATE_NOOP("bitcoin-core", "User Agent comment (%s) contains unsafe characters."), +QT_TRANSLATE_NOOP("bitcoin-core", "Value or asset is not explicit for pre-selected input %s"), 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"), diff --git a/src/qt/locale/bitcoin_en.ts b/src/qt/locale/bitcoin_en.ts index 6a245d1d72..09bc18dccf 100644 --- a/src/qt/locale/bitcoin_en.ts +++ b/src/qt/locale/bitcoin_en.ts @@ -76,12 +76,12 @@ - These are your Bitcoin addresses for sending payments. Always check the amount and the receiving address before sending coins. + These are your %1 addresses for sending payments. Always check the amount and the receiving address before sending coins. - These are your Bitcoin addresses for receiving payments. Use the 'Create new receiving address' button in the receive tab to create new addresses. + These are your %1 addresses for receiving payments. Use the 'Create new receiving address' button in the receive tab to create new addresses. Signing is only possible with addresses of the type 'legacy'. @@ -337,15 +337,23 @@ Signing is only possible with addresses of the type 'legacy'. + + BitcoinAmountField + + + Custom asset (%1) + + + BitcoinApplication - + Settings file %1 might be corrupt or invalid. - + Runaway exception @@ -378,7 +386,17 @@ Signing is only possible with addresses of the type 'legacy'. Show general overview of wallet - + + Send coins to a %1 address + + + + + Request payments (generates QR codes and %1 addresses) + + + + &Transactions &Transactions @@ -423,12 +441,47 @@ Signing is only possible with addresses of the type 'legacy'. - + + Sign messages with your %1 addresses to prove you own them + + + + + Verify messages to ensure they were signed with specified %1 addresses + + + + + &Load PSET from file… + + + + + Load Partially Signed Elements Transaction + + + + + Load PSET from &clipboard… + + + + + Load Partially Signed Elements Transaction from clipboard + + + + Create a new wallet - + + Show the %1 help message to get a list with possible command-line options + + + + &Minimize @@ -437,24 +490,28 @@ Signing is only possible with addresses of the type 'legacy'. Wallet: + + + %n active connection(s) to %1 network + A substring of the tooltip. + + + + + - + Network activity disabled. A substring of the tooltip. - + Proxy is <b>enabled</b>: %1 - - Send coins to a Bitcoin address - Send coins to a Bitcoin address - - - + Backup wallet to another location Backup wallet to another location @@ -504,32 +561,12 @@ Signing is only possible with addresses of the type 'legacy'. - - Sign messages with your Bitcoin addresses to prove you own them - Sign messages with your Bitcoin addresses to prove you own them - - - + &Verify message… - - Verify messages to ensure they were signed with specified Bitcoin addresses - Verify messages to ensure they were signed with specified Bitcoin addresses - - - - &Load PSBT from file… - - - - - Open &URI… - - - - + Close Wallet… @@ -544,7 +581,7 @@ Signing is only possible with addresses of the type 'legacy'. - + &File &File @@ -564,7 +601,7 @@ Signing is only possible with addresses of the type 'legacy'. Tabs toolbar - + Syncing Headers (%1%)… @@ -589,12 +626,7 @@ Signing is only possible with addresses of the type 'legacy'. - - Request payments (generates QR codes and bitcoin: URIs) - - - - + Show the list of used sending addresses and labels @@ -604,12 +636,12 @@ Signing is only possible with addresses of the type 'legacy'. - + &Command-line options - + Processed %n block(s) of transaction history. Processed %n block of transaction history. @@ -657,27 +689,12 @@ Signing is only possible with addresses of the type 'legacy'. Up to date - + Ctrl+Q - - Load Partially Signed Bitcoin Transaction - - - - - Load PSBT from &clipboard… - - - - - Load Partially Signed Bitcoin Transaction from clipboard - - - - + Node window @@ -697,12 +714,7 @@ Signing is only possible with addresses of the type 'legacy'. - - Open a bitcoin: URI - - - - + Open Wallet @@ -744,12 +756,7 @@ Signing is only possible with addresses of the type 'legacy'. - - Show the %1 help message to get a list with possible Bitcoin command-line options - - - - + &Mask values @@ -759,7 +766,7 @@ Signing is only possible with addresses of the type 'legacy'. - + No wallets available @@ -809,7 +816,7 @@ Signing is only possible with addresses of the type 'legacy'. - + %1 client @@ -823,17 +830,8 @@ Signing is only possible with addresses of the type 'legacy'. S&how - - - %n active connection(s) to Bitcoin network. - A substring of the tooltip. - - %n active connection to Bitcoin network. - %n active connections to Bitcoin network. - - - + Click for more actions. A substring of the tooltip. "More actions" are available via the context menu. @@ -928,7 +926,7 @@ Signing is only possible with addresses of the type 'legacy'. Incoming transaction - + HD key generation is <b>enabled</b> @@ -1130,7 +1128,7 @@ Signing is only possible with addresses of the type 'legacy'. CreateWalletActivity - + Create Wallet Title of window indicating the progress of creation of a new wallet. @@ -1289,12 +1287,7 @@ Signing is only possible with addresses of the type 'legacy'. - - The entered address "%1" is not a valid Bitcoin address. - - - - + Address "%1" already exists as a receiving address with label "%2" and so cannot be added as a sending address. @@ -1309,7 +1302,12 @@ Signing is only possible with addresses of the type 'legacy'. - + + The entered address "%1" is not a valid %2 address. + + + + New key generation failed. @@ -1417,13 +1415,8 @@ Signing is only possible with addresses of the type 'legacy'. Use a custom data directory: Use a custom data directory: - - - Bitcoin - Bitcoin - - + %n GB of space available %n GB of space available @@ -1471,8 +1464,8 @@ Signing is only possible with addresses of the type 'legacy'. - - %1 will download and store a copy of the %2 block chain. + + %1 will download and store a copy of the Bitcoin block chain. @@ -1486,7 +1479,12 @@ Signing is only possible with addresses of the type 'legacy'. - + + Liquid + + + + Error Error @@ -1571,17 +1569,7 @@ The migration process will create a backup of the wallet before migrating. This Form - - 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. - - - - - Attempting to spend bitcoins that are affected by not-yet-displayed transactions will not be accepted by the network. - - - - + Number of blocks left @@ -1604,7 +1592,17 @@ The migration process will create a backup of the wallet before migrating. This Last block time - + + 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 Liquid network, as detailed below. + + + + + Attempting to spend assets that are affected by not-yet-displayed transactions will not be accepted by the network. + + + + Progress @@ -1747,7 +1745,12 @@ The migration process will create a backup of the wallet before migrating. This - + + Connect to the Liquid network through a SOCKS5 proxy. + + + + IP address of the proxy (e.g. IPv4: 127.0.0.1 / IPv6: ::1) @@ -1760,7 +1763,12 @@ The migration process will create a backup of the wallet before migrating. This - + + Connect to the Liquid network through a separate SOCKS5 proxy for Tor onion services. + + + + 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. @@ -1912,12 +1920,7 @@ The migration process will create a backup of the wallet before migrating. This - - Connect to the Bitcoin network through a SOCKS5 proxy. - - - - + &Connect through SOCKS5 proxy (default proxy): @@ -2031,12 +2034,7 @@ The migration process will create a backup of the wallet before migrating. This - - Connect to the Bitcoin network through a separate SOCKS5 proxy for Tor onion services. - - - - + Use separate SOCKS&5 proxy to reach peers via Tor onion services: @@ -2051,7 +2049,7 @@ The migration process will create a backup of the wallet before migrating. This &Cancel - + Compiled without external signing support (required for external signing) "External signing" means using devices such as hardware wallets. @@ -2150,93 +2148,93 @@ The migration process will create a backup of the wallet before migrating. This Form - - - 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. - 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. - - - + Watch-only: - + Available: - + Your current spendable balance Your current spendable balance - + Pending: - + Total of transactions that have yet to be confirmed, and do not yet count toward the spendable balance Total of transactions that have yet to be confirmed, and do not yet count toward the spendable balance - + Immature: Immature: - + Mined balance that has not yet matured Mined balance that has not yet matured - + Balances - + + + The displayed information may be out of date. Your wallet automatically synchronizes with the Liquid network after a connection is established, but this process has not completed yet. + + + + Total: Total: - + Your current total balance Your current total balance - + Your current balance in watch-only addresses - + Spendable: - + Recent transactions - + Unconfirmed transactions to watch-only addresses - + Mined balance in watch-only addresses that has not yet matured - + Current total balance in watch-only addresses - + Privacy mode activated for the Overview tab. To unmask the values, uncheck Settings->Mask values. @@ -2340,7 +2338,7 @@ The migration process will create a backup of the wallet before migrating. This - + Sends %1 to %2 @@ -2355,7 +2353,7 @@ The migration process will create a backup of the wallet before migrating. This - + Pays transaction fee: @@ -2445,7 +2443,7 @@ If you are receiving this error you should request the merchant provide a BIP21 - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid address or malformed URI parameters. @@ -2532,22 +2530,22 @@ If you are receiving this error you should request the merchant provide a BIP21 QObject - + Amount Amount - - Enter a Bitcoin address (e.g. %1) + + Enter a Liquid address (e.g. %1) - + Ctrl+W - + Unroutable @@ -2629,7 +2627,7 @@ If you are receiving this error you should request the merchant provide a BIP21 - + %1 d @@ -2729,7 +2727,7 @@ If you are receiving this error you should request the merchant provide a BIP21 - + %1 kB @@ -2751,7 +2749,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. @@ -2763,12 +2761,12 @@ If you are receiving this error you should request the merchant provide a BIP21 - + Error: %1 - + %1 didn't yet exit safely… @@ -2778,7 +2776,7 @@ If you are receiving this error you should request the merchant provide a BIP21 - + Embedded "%1" @@ -2816,7 +2814,7 @@ If you are receiving this error you should request the merchant provide a BIP21 - + QR code support not available. @@ -3316,7 +3314,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. @@ -3409,7 +3407,7 @@ If you are receiving this error you should request the merchant provide a BIP21 - + &Copy address Context menu action to copy the address of a peer. @@ -3618,12 +3616,7 @@ For more information on using this console, type %6. - - Copy &URI - - - - + &Copy address @@ -3643,7 +3636,7 @@ For more information on using this console, type %6. - + Base58 (Legacy) @@ -3701,7 +3694,7 @@ For more information on using this console, type %6. - + Address: @@ -3751,12 +3744,12 @@ For more information on using this console, type %6. - + Request payment to %1 - + Payment information @@ -3773,11 +3766,6 @@ For more information on using this console, type %6. Label - - - Message - - (no label) @@ -3794,7 +3782,7 @@ For more information on using this console, type %6. - + Requested @@ -3836,7 +3824,7 @@ For more information on using this console, type %6. SendCoinsDialog - + Send Coins Send Coins @@ -3921,7 +3909,13 @@ For more information on using this console, type %6. - + + + Paying only the minimum fee is just fine as long as there is less transaction volume than space in the blocks. But be aware that this can end up in a never confirming transaction once there is more demand for transactions than the network can process. + + + + Recommended: @@ -3946,7 +3940,7 @@ For more information on using this console, type %6. - + Inputs… @@ -3968,12 +3962,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - - 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. - - - - + A too low fee might result in a never confirming transaction (read the tooltip) @@ -4018,7 +4007,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 S&end - + Copy quantity @@ -4080,7 +4069,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - + %1 to '%2' @@ -4090,12 +4079,12 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - + To review recipient list click "Show Details…" - + Sign failed @@ -4129,17 +4118,17 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - + External balance: - + or - + You can increase the fee later (signals Replace-By-Fee, BIP-125). @@ -4190,12 +4179,17 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - + Total Amount - + + and + + + + Unsigned Transaction PSBT copied Caption of "PSBT has been copied" messagebox @@ -4207,17 +4201,17 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - + PSBT saved to disk - + Confirm send coins - + Watch-only balance: @@ -4257,7 +4251,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - + %1/kvB @@ -4271,8 +4265,8 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - - Warning: Invalid Bitcoin address + + Warning: Invalid address @@ -4291,7 +4285,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - + (no label) @@ -4383,7 +4377,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 SendConfirmationDialog - + Send @@ -4607,7 +4601,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 SplashScreen - + (press q to shutdown and continue later) @@ -4698,39 +4692,39 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - + To - - + + own address - + - + watch-only - + label - + - + Credit - + matures in %n more block(s) matures in %n more block @@ -4743,7 +4737,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - + Debit @@ -4821,7 +4815,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - + Transaction @@ -4864,7 +4858,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 TransactionTableModel - + Date Date @@ -4879,7 +4873,12 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - + + Amount + Amount + + + Unconfirmed @@ -4934,17 +4933,27 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - + + Fee + + + + + Issuance + + + + watch-only - + (n/a) - + (no label) @@ -5028,7 +5037,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - + Other @@ -5043,12 +5052,22 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - + Range… - + + Fee + + + + + Issuance + + + + &Copy address @@ -5191,7 +5210,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 WalletController - + Close wallet @@ -5266,7 +5285,7 @@ Go to File > Open Wallet to load a wallet. WalletModel - + Send Coins Send Coins @@ -5433,7 +5452,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. @@ -5517,11 +5536,6 @@ Go to File > Open Wallet to load a wallet. No wallet file format provided. To use createfromdump, -format=<format> must be provided. - - - Option '-upnp' is set but UPnP support was dropped in version 29.0. Consider using '-natpmp' instead. - - Please contribute if you find %s useful. Visit %s for further information about the software. @@ -5593,7 +5607,7 @@ Go to File > Open Wallet to load a wallet. - + Unable to replay blocks. You will need to rebuild the database using -reindex-chainstate. @@ -5614,16 +5628,6 @@ Go to File > Open Wallet to load a wallet. - Wallet created successfully. The legacy wallet type is being deprecated and support for creating and opening legacy wallets will be removed in the future. - - - - - Wallet loaded successfully. The legacy wallet type is being deprecated and support for creating and opening legacy wallets will be removed in the future. Legacy wallets can be migrated to a descriptor wallet with migratewallet. - - - - Warning: Dumpfile wallet format "%s" does not match command line specified format "%s". @@ -5658,7 +5662,7 @@ Go to File > Open Wallet to load a wallet. - + Cannot obtain a lock on directory %s. %s is probably already running. @@ -5678,7 +5682,7 @@ Go to File > Open Wallet to load a wallet. - + %s is set very high! Fees this large could be paid on a single transaction. @@ -5688,7 +5692,17 @@ Go to File > Open Wallet to load a wallet. - + + Change output could not be blinded as there are no blinded inputs and no other blinded outputs. + + + + + Could not locate mainchain RPC credentials. No authentication cookie could be found, and no mainchainrpcpassword is set in the configuration file (%s) + + + + Error loading %s: External signer wallet being loaded without external signer support compiled @@ -5764,7 +5778,7 @@ Go to File > Open Wallet to load a wallet. - + Outbound connections restricted to CJDNS (-onlynet=cjdns) but -cjdnsreachable is not provided @@ -5820,6 +5834,11 @@ Go to File > Open Wallet to load a wallet. + Transaction output could not be blinded as there are no blinded inputs and no other blinded outputs. + + + + Transaction requires one destination of non-0 value, a non-0 feerate, or a pre-selected input @@ -5851,7 +5870,7 @@ Please try running the latest software version. - + 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. @@ -5882,6 +5901,11 @@ Unable to restore backup of wallet. Assumeutxo data not found for the given blockhash '%s'. + + + Awaiting mainchain RPC warmup + + Block verification was interrupted @@ -6327,6 +6351,11 @@ Unable to restore backup of wallet. No addresses available + + + No asset provided for recipient + + Not found pre-selected input %s @@ -6342,6 +6371,11 @@ Unable to restore backup of wallet. Only direction was set, no permissions: '%s' + + + Peg-in input has invalid proof. + + Prune cannot be configured with a negative value. @@ -6392,11 +6426,6 @@ Unable to restore backup of wallet. SQLiteDatabase: Unexpected application id. Expected %u, got %u - - - Section [%s] is not recognized. - - Signer did not echo address @@ -6527,6 +6556,11 @@ Unable to restore backup of wallet. Transaction change output index out of range + + + Transaction is missing an output for input asset %s + + Transaction must have at least one recipient @@ -6542,6 +6576,11 @@ Unable to restore backup of wallet. Transaction too large + + + Unable to allocate memory for -maxsigcachesize: '%s' MiB + + Unable to bind to %s on this computer (bind returned error %s) @@ -6552,6 +6591,11 @@ Unable to restore backup of wallet. Unable to bind to %s on this computer. %s is probably already running. + + + Unable to blind the transaction properly. This should not happen. + + Unable to create the PID file '%s': %s @@ -6628,7 +6672,12 @@ Unable to restore backup of wallet. - + + Value or asset is not explicit for pre-selected input %s + + + + Wallet file creation failed: %s @@ -6638,12 +6687,12 @@ Unable to restore backup of wallet. - + Unsupported logging category %s=%s. - + Do you want to rebuild the databases now? @@ -6668,17 +6717,17 @@ Unable to restore backup of wallet. - + Not enough file descriptors available. %d available, %d required. - + User Agent comment (%s) contains unsafe characters. - + Verifying blocks… @@ -6693,7 +6742,7 @@ Unable to restore backup of wallet. - + Settings file could not be read diff --git a/src/qt/locale/bitcoin_en.xlf b/src/qt/locale/bitcoin_en.xlf index 9e38f8f2b1..fa13fbde38 100644 --- a/src/qt/locale/bitcoin_en.xlf +++ b/src/qt/locale/bitcoin_en.xlf @@ -64,11 +64,11 @@ 89 - These are your Bitcoin addresses for sending payments. Always check the amount and the receiving address before sending coins. + These are your %1 addresses for sending payments. Always check the amount and the receiving address before sending coins. 95 - These are your Bitcoin addresses for receiving payments. Use the 'Create new receiving address' button in the receive tab to create new addresses. + These are your %1 addresses for receiving payments. Use the 'Create new receiving address' button in the receive tab to create new addresses. Signing is only possible with addresses of the type 'legacy'. 100 @@ -286,604 +286,604 @@ Signing is only possible with addresses of the type 'legacy'. + + + + Custom asset (%1) + 476 + + + - + Settings file %1 might be corrupt or invalid. - 260 + 253 - + Runaway exception - 444 + 422 - + A fatal error occurred. %1 can no longer continue safely and will quit. - 445 + 423 - + Internal error - 454 + 432 - + An internal error occurred. %1 will attempt to continue safely. This is an unexpected bug which can be reported as described below. - 455 + 433 - + Do you want to reset settings to default values, or to abort without making changes? 168 Explanatory text shown on startup when the settings file cannot be read. Prompts user to make a choice between resetting or aborting. - + A fatal error occurred. Check that settings file is writable, or try running with -nosettings. 188 Explanatory text shown on startup when the settings file could not be written. Prompts user to check that we have the ability to write to the file. Explains that the user has the option of running without a settings file. - + Error: %1 - 616 + 594 - + %1 didn't yet exit safely… - 689 + 648 - + &Overview 252 - + Show general overview of wallet 253 - + + Send coins to a %1 address + 260 + + + Request payments (generates QR codes and %1 addresses) + 267 + + &Transactions 273 - + Browse transaction history 274 - + E&xit 293 - + Quit application 294 - + &About %1 297 - + Show information about %1 298 - + About &Qt 301 - + Show information about Qt 302 - + Modify configuration options for %1 305 - + + Sign messages with your %1 addresses to prove you own them + 317 + + + Verify messages to ensure they were signed with specified %1 addresses + 319 + + + &Load PSET from file… + 320 + + + Load Partially Signed Elements Transaction + 321 + + + Load PSET from &clipboard… + 322 + + + Load Partially Signed Elements Transaction from clipboard + 323 + + Create a new wallet - 349 + 346 - + + Show the %1 help message to get a list with possible command-line options + 364 + + &Minimize - 533 + 529 - + Wallet: - 612 + 608 - + + 1013 + A substring of the tooltip. + + %n active connection(s) to %1 network + + + %n active connection(s) to %1 network + + + Network activity disabled. - 1030 + 1016 A substring of the tooltip. - + Proxy is <b>enabled</b>: %1 - 1481 + 1455 - - Send coins to a Bitcoin address - 260 - - + Backup wallet to another location 313 - + Change the passphrase used for wallet encryption 315 - + &Send 259 - + &Receive 266 - + &Options… 304 - + &Encrypt Wallet… 309 - + Encrypt the private keys that belong to your wallet 310 - + &Backup Wallet… 312 - + &Change Passphrase… 314 - + Sign &message… 316 - - Sign messages with your Bitcoin addresses to prove you own them - 317 - - + &Verify message… 318 - - Verify messages to ensure they were signed with specified Bitcoin addresses - 319 - - - &Load PSBT from file… - 320 - - - Open &URI… - 336 - - + Close Wallet… - 344 + 341 - + Create Wallet… - 347 + 344 - + Close All Wallets… - 357 + 354 - + &File - 499 + 495 - + &Settings - 520 + 516 - + &Help - 581 + 577 - + Tabs toolbar - 592 + 588 - + Syncing Headers (%1%)… - 1074 + 1060 - + Synchronizing with network… - 1132 + 1118 - + Indexing blocks on disk… - 1137 + 1123 - + Processing blocks on disk… - 1139 + 1125 - + Connecting to peers… - 1146 - - - Request payments (generates QR codes and bitcoin: URIs) - 267 + 1132 - + Show the list of used sending addresses and labels 332 - + Show the list of used receiving addresses and labels 334 - + &Command-line options - 365 + 362 - 1155 - + 1141 + Processed %n block(s) of transaction history. - + Processed %n block(s) of transaction history. - + %1 behind - 1178 + 1164 - + Catching up… - 1183 + 1169 - + Last received block was generated %1 ago. - 1202 + 1188 - + Transactions after this will not yet be visible. - 1204 + 1190 - + Error - 1244 + 1230 - + Warning - 1248 + 1234 - + Information - 1252 + 1238 - + Up to date - 1159 + 1145 - + Ctrl+Q 295 - - Load Partially Signed Bitcoin Transaction - 321 - - - Load PSBT from &clipboard… - 322 - - - Load Partially Signed Bitcoin Transaction from clipboard - 323 - - + Node window 325 - + Open node debugging and diagnostic console 326 - + &Sending addresses 331 - + &Receiving addresses 333 - - Open a bitcoin: URI - 337 - - + Open Wallet - 339 + 336 - + Open a wallet - 341 + 338 - + Close wallet - 345 + 342 - + Restore Wallet… - 352 + 349 Name of the menu item that restores wallet from a backup file. - + Restore a wallet from a backup file - 355 + 352 Status tip for Restore Wallet menu item - + Close all wallets - 358 + 355 - + Migrate Wallet - 360 + 357 - + Migrate a wallet - 362 - - - Show the %1 help message to get a list with possible Bitcoin command-line options - 367 + 359 &Mask values - 369 + 366 Mask the values in the Overview tab - 371 + 368 No wallets available - 422 - 481 + 418 + 477 Wallet Data - 428 + 424 Name of the wallet data file format. Load Wallet Backup - 431 + 427 The title for Restore Wallet File Windows Restore Wallet - 439 + 435 Title of pop-up window shown when the user is attempting to restore a wallet. Wallet Name - 441 + 437 Label of the input field where the name of the wallet is entered. &Window - 531 + 527 Ctrl+M - 534 + 530 Zoom - 543 + 539 Main Window - 561 + 557 %1 client - 840 + 835 &Hide - 908 + 903 S&how - 909 + 904 - - 1027 - A substring of the tooltip. - - %n active connection(s) to Bitcoin network. - - - %n active connection(s) to Bitcoin network. - - - + Click for more actions. - 1037 + 1023 A substring of the tooltip. "More actions" are available via the context menu. - + Show Peers tab - 1054 + 1040 A context menu item. The "Peers tab" is an element of the "Node window". - + Disable network activity - 1062 + 1048 A context menu item. - + Enable network activity - 1064 + 1050 A context menu item. The network activity was disabled previously. - + Pre-syncing Headers (%1%)… - 1081 + 1067 - + Error creating wallet - 1220 + 1206 - + Cannot create new wallet, the software was compiled without sqlite support (required for descriptor wallets) - 1220 + 1206 - + Error: %1 - 1245 + 1231 - + Warning: %1 - 1249 + 1235 - + Date: %1 - 1357 + 1343 - + Amount: %1 - 1358 + 1344 - + Wallet: %1 - 1360 + 1346 - + Type: %1 - 1362 + 1348 - + Label: %1 - 1364 + 1350 - + Address: %1 - 1366 + 1352 - + Sent transaction - 1367 + 1353 - + Incoming transaction - 1367 + 1353 - + HD key generation is <b>enabled</b> - 1419 + 1393 - + HD key generation is <b>disabled</b> - 1419 + 1393 - + Private key <b>disabled</b> - 1419 + 1393 - + Wallet is <b>encrypted</b> and currently <b>unlocked</b> - 1442 + 1416 - + Wallet is <b>encrypted</b> and currently <b>locked</b> - 1450 + 1424 - + Original message: - 1569 + 1543 - + Unit to show amounts in. Click to select another unit. - 1608 + 1582 - + 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 @@ -891,72 +891,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 @@ -964,156 +964,156 @@ Signing is only possible with addresses of the type 'legacy'. - + Create Wallet - 250 + 251 Title of window indicating the progress of creation of a new wallet. - + Creating Wallet <b>%1</b>… - 253 + 254 Descriptive text of the create wallet progress window which indicates to the user which wallet is currently being created. - + Create wallet failed - 285 + 286 - + Create wallet warning - 287 + 288 - + Can't list signers - 303 + 304 - + Too many external signers found - 306 + 307 - + Load Wallets - 380 + 381 Title of progress window which is displayed when wallets are being loaded. - + Loading wallets… - 383 + 384 Descriptive text of the load wallets progress window which indicates to the user that wallets are currently being loaded. - + Migrate wallet - 446 + 447 - + Are you sure you wish to migrate the wallet <i>%1</i>? - 447 + 448 - + 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 + 449 - + Migrate Wallet - 465 + 466 - + Migrating Wallet <b>%1</b>… - 465 + 466 - + The wallet '%1' was migrated successfully. - 471 + 472 - + Watchonly scripts have been migrated to a new wallet named '%1'. - 473 + 474 - + Solvable but not watched scripts have been migrated to a new wallet named '%1'. - 476 + 477 - + Migration failed - 490 + 491 - + Migration Successful - 492 + 493 - + Open wallet failed - 337 + 338 - + Open wallet warning - 339 + 340 - + Open Wallet - 353 + 354 Title of window indicating the progress of opening of a wallet. - + Opening Wallet <b>%1</b>… - 356 + 357 Descriptive text of the open wallet progress window which indicates to the user which wallet is currently being opened. - + Restore Wallet - 406 + 407 Title of progress window which is displayed when wallets are being restored. - + Restoring Wallet <b>%1</b>… - 409 + 410 Descriptive text of the restore wallets progress window which indicates to the user that wallets are currently being restored. - + Restore wallet failed - 428 + 429 Title of message box which is displayed when the wallet could not be restored. - + Restore wallet warning - 431 + 432 Title of message box which is displayed when the wallet is restored with some warning. - + Restore wallet message - 434 + 435 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 @@ -1121,59 +1121,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. 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 @@ -1181,11 +1181,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. @@ -1194,23 +1194,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 @@ -1218,35 +1218,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 - + + The entered address "%1" is not a valid %2 address. + 113 + + New key generation failed. 128 @@ -1254,94 +1254,94 @@ The migration process will create a backup of the wallet before migrating. This - + A new data directory will be created. 73 - + name 95 - + Directory already exists. Add %1 if you intend to create a new directory here. 97 - + Path already exists, and is not a directory. 100 - + Cannot create data directory here. 107 - - Bitcoin - 137 - 301 - + %n GB of space available - + %n GB of space available 303 - + (of %n GB needed) - + (of %n GB needed) 306 - + (%n GB needed for full chain) - + (%n GB needed for full chain) - + Choose data directory 323 - + At least %1 GB of data will be stored in this directory, and it will grow over time. 378 - + Approximately %1 GB of data will be stored in this directory. 381 390 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. 392 - + The wallet will also be stored in this directory. 394 - + Error: Specified data directory "%1" cannot be created. 250 - + + Liquid + 137 + + Error 280 @@ -1349,25 +1349,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 @@ -1375,47 +1375,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 @@ -1423,54 +1423,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 - + + 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 Liquid network, as detailed below. + 133 + + + Attempting to spend assets that are affected by not-yet-displayed transactions will not be accepted by the network. + 152 + + Progress 261 - + Progress increase per hour 285 - + Estimated time left until synced 305 - + Hide 342 - + Esc 345 @@ -1478,21 +1478,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 @@ -1500,15 +1500,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. @@ -1517,51 +1517,55 @@ 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 + + Connect to the Liquid network through a SOCKS5 proxy. + 341 + IP address of the proxy (e.g. IPv4: 127.0.0.1 / IPv6: ::1) 378 @@ -1574,132 +1578,132 @@ The migration process will create a backup of the wallet before migrating. This 493 + Connect to the Liquid network through a separate SOCKS5 proxy for Tor onion services. + 528 + + 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 @@ -1793,18 +1797,14 @@ The migration process will create a backup of the wallet before migrating. This 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 @@ -1812,85 +1812,85 @@ The migration process will create a backup of the wallet before migrating. This - + Compiled without external signing support (required for external signing) - 145 + 146 "External signing" means using devices such as hardware wallets. - + default - 157 + 158 - + none - 238 + 239 - + Confirm options reset - 346 + 347 Window title text of pop-up window shown when the user has chosen to reset options. - + Client restart required to activate changes. - 337 - 418 + 338 + 419 Text explaining that the settings changed will not come into effect until the client is restarted. - + Current settings will be backed up at "%1". - 341 + 342 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? - 344 + 345 Text asking the user to confirm if they would like to proceed with a client shutdown. - + Configuration options - 364 + 365 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. - 367 + 368 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 - 370 + 371 - + Cancel - 371 + 372 - + Error - 380 + 381 - + The configuration file could not be opened. - 380 + 381 - + This change would require a client restart. - 422 + 423 - + The supplied proxy address is invalid. - 450 + 451 - + Embedded "%1" 61 - + Default system font "%1" 62 - + Custom… 63 @@ -1898,7 +1898,7 @@ The migration process will create a backup of the wallet before migrating. This - + Could not read setting "%1", %2. 227 @@ -1906,112 +1906,112 @@ 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 - 411 - - + Watch-only: 284 - + Available: - 294 + 249 - + Your current spendable balance - 304 + 458 - + Pending: - 339 + 319 - + Total of transactions that have yet to be confirmed, and do not yet count toward the spendable balance - 139 + 268 - + Immature: - 239 + 229 - + Mined balance that has not yet matured - 210 + 303 - + Balances 60 - + + The displayed information may be out of date. Your wallet automatically synchronizes with the Liquid network after a connection is established, but this process has not completed yet. + 76 + 517 + + Total: - 200 + 239 - + Your current total balance - 249 + 389 - + Your current balance in watch-only addresses - 323 + 207 - + Spendable: - 346 + 188 - + Recent transactions - 395 + 501 - + Unconfirmed transactions to watch-only addresses - 120 + 408 - + Mined balance in watch-only addresses that has not yet matured - 158 + 433 - + Current total balance in watch-only addresses - 268 + 364 - + Privacy mode activated for the Overview tab. To unmask the values, uncheck Settings->Mask values. - 184 + 182 - + PSBT Operations 14 - + Sign Tx 86 - + Broadcast Tx 102 - + Copy to Clipboard 122 - + Save… 129 - + Close 136 @@ -2019,150 +2019,150 @@ 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 + 188 - + own address - 191 + 192 - + Unable to calculate transaction fee or total transaction amount. - 199 + 200 - + Pays transaction fee: - 201 + 203 - + Total Amount - 213 + 215 - + or - 216 + 218 - + Transaction has %1 unsigned inputs. - 222 + 224 - + Transaction is missing some information about inputs. - 268 + 270 - + Transaction still needs signature(s). - 272 + 274 - + (But no wallet is loaded.) - 275 + 277 - + (But this wallet cannot sign transactions.) - 278 + 280 - + (But this wallet does not have the right keys.) - 281 + 283 - + Transaction is fully signed and ready for broadcast. - 289 + 291 - + Transaction status is unknown. - 293 + 295 - + 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. + + URI cannot be parsed! This can be caused by an invalid address or malformed URI parameters. 224 - + Payment request file handling 233 @@ -2170,52 +2170,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. @@ -2224,12 +2224,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. @@ -2238,244 +2238,244 @@ If you are receiving this error you should request the merchant provide a BIP21 - + Amount - 197 + 226 - - Enter a Bitcoin address (e.g. %1) - 138 + + Enter a Liquid address (e.g. %1) + 140 - + Ctrl+W - 433 + 441 - + Unroutable - 690 + 704 - + IPv4 - 692 + 706 network name Name of IPv4 network in peer info - + IPv6 - 694 + 708 network name Name of IPv6 network in peer info - + Onion - 696 + 710 network name Name of Tor network in peer info - + I2P - 698 + 712 network name Name of I2P network in peer info - + CJDNS - 700 + 714 network name Name of CJDNS network in peer info - + Inbound - 714 + 728 An inbound connection from a peer. An inbound connection is a connection initiated by a peer. - + Outbound - 717 + 731 An outbound connection to a peer. An outbound connection is a connection initiated by us. - + Full Relay - 722 + 736 Peer connection type that relays all network information. - + Block Relay - 725 + 739 Peer connection type that relays network information about blocks and not transactions or addresses. - + Manual - 727 + 741 Peer connection type established manually through one of several methods. - + Feeler - 729 + 743 Short-lived peer connection type that tests the aliveness of known addresses. - + Address Fetch - 731 + 745 Short-lived peer connection type that solicits known addresses from a peer. - + %1 d - 743 - 755 + 819 + 831 - + %1 h - 744 - 756 + 820 + 832 - + %1 m - 745 - 757 + 821 + 833 - + %1 s - 747 - 758 - 784 + 823 + 834 + 860 - + None - 772 + 848 - + N/A - 778 + 854 - + %1 ms - 779 + 855 - 797 - + 873 + %n second(s) - + %n second(s) - 801 - + 877 + %n minute(s) - + %n minute(s) - 805 - + 881 + %n hour(s) - + %n hour(s) - 809 - + 885 + %n day(s) - + %n day(s) - 813 - 819 - + 889 + 895 + %n week(s) - + %n week(s) - + %1 and %2 - 819 + 895 - 819 - + 895 + %n year(s) - + %n year(s) - + %1 B - 827 + 903 - + %1 kB - 829 - ../rpcconsole.cpp1023 + 905 + ../rpcconsole.cpp1025 - + %1 MB - 831 - ../rpcconsole.cpp1024 - ../rpcconsole.cpp1025 + 907 + ../rpcconsole.cpp1026 + ../rpcconsole.cpp1027 - + %1 GB - 833 + 909 - + default wallet - 1013 + 1089 - + &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 + 91 - + Save QR Code - 118 + 121 - + PNG Image - 121 + 124 Expanded name of the PNG file format. See: https://en.wikipedia.org/wiki/Portable_Network_Graphics. - + N/A 75 101 @@ -2518,323 +2518,323 @@ If you are receiving this error you should request the merchant provide a BIP21 1824 ../rpcconsole.h145 - + 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 - + &Peers 901 - + Banned peers 977 - + Select a peer to view detailed information. 1053 - ../rpcconsole.cpp1191 + ../rpcconsole.cpp1193 - + 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 1402 - + Synced Headers 1425 - + Synced Blocks 1448 - + Last Transaction 1523 - + The mapped Autonomous System used for diversifying peer selection. 1733 - + Mapped AS 1736 - + Whether we relay addresses to this peer. 1759 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 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 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 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 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 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 - + Last block time 325 - + &Open 435 - + &Console 461 - + &Network Traffic 648 - + Totals 716 - + Debug log file 425 - + Clear console 550 @@ -2842,162 +2842,162 @@ If you are receiving this error you should request the merchant provide a BIP21 - + In: - 975 + 977 - + Out: - 976 + 978 - + Inbound: initiated by peer 499 Explanatory text for an inbound peer connection. - + Outbound Full Relay: default 503 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 506 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 511 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 517 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 520 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 525 Explanatory text for "detecting" transport type. - + v1: unencrypted, plaintext transport protocol 527 Explanatory text for v1 transport type. - + v2: BIP324 encrypted transport protocol 529 Explanatory text for v2 transport type. - + we selected the peer for high bandwidth relay 533 - + the peer selected us for high bandwidth relay 534 - + no high bandwidth relay selected 535 - + Ctrl++ 548 Main shortcut to increase the RPC console font size. - + Ctrl+= 550 Secondary shortcut to increase the RPC console font size. - + Ctrl+- 554 Main shortcut to decrease the RPC console font size. - + Ctrl+_ 556 Secondary shortcut to decrease the RPC console font size. - + &Copy address - 710 + 712 Context menu action to copy the address of a peer. - + &Disconnect - 714 + 716 - + 1 &hour - 715 + 717 - + 1 d&ay - 716 + 718 - + 1 &week - 717 + 719 - + 1 &year - 718 + 720 - + &Copy IP/Netmask - 744 + 746 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 - 748 + 750 - + Network activity disabled - 979 + 981 - + None - 992 + 994 - + Executing command without any wallet - 1071 + 1073 - + Ctrl+I - 1397 + 1399 - + Ctrl+T - 1398 + 1400 - + Ctrl+N - 1399 + 1401 - + Ctrl+P - 1400 + 1402 - + Node window - [%1] - 1418 + 1420 - + Executing command using "%1" wallet - 1069 + 1071 - + 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. @@ -3005,51 +3005,51 @@ 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 - 908 + 910 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… - 1079 + 1081 A console message indicating an entered command is currently being executed. - + (peer: %1) - 1197 + 1199 - + via %1 - 1199 + 1201 - + Yes 144 - + No 144 - + To 144 - + From 144 - + Ban for 145 - + Never 187 - + Unknown 145 @@ -3057,72 +3057,72 @@ For more information on using this console, type %6. - + &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 @@ -3130,115 +3130,111 @@ For more information on using this console, type %6. - - Copy &URI - 46 - - + &Copy address - 47 + 51 - + Copy &label - 48 + 52 - + Copy &message - 49 + 53 - + Copy &amount - 50 + 54 - + Base58 (Legacy) - 96 + 102 - + Not recommended due to higher fees and less protection against typos. - 96 + 102 - + Base58 (P2SH-SegWit) - 97 + 103 - + Generates an address compatible with older wallets. - 97 + 103 - + Bech32 (SegWit) - 98 + 104 - + Generates a native segwit address (BIP-173). Some old wallets don't support it. - 98 + 104 - + Bech32m (Taproot) - 100 + 106 - + Bech32m (BIP-350) is an upgrade to Bech32, wallet support is still limited. - 100 + 106 - + Could not unlock wallet. - 175 + 181 - + Could not generate new %1 address - 180 + 186 - + Request payment to … 14 - + Address: - 90 + 55 - + Amount: - 119 + 84 - + Label: - 148 + 113 - + Message: - 180 + 145 - + Wallet: - 212 + 177 - + Copy &URI - 240 + 205 - + Copy &Address - 250 + 215 - + &Verify - 260 + 225 - + Verify this address on e.g. a hardware wallet screen - 263 + 228 - + &Save Image… - 273 + 238 - + Payment information 39 @@ -3246,491 +3242,492 @@ For more information on using this console, type %6. - + Request payment to %1 - 46 + 49 - + Date 34 - + Label 34 - - Message - 34 - - + (no label) 72 - + (no message) 81 - + (no amount requested) 89 - + Requested - 132 + 130 - + Send Coins 14 - ../sendcoinsdialog.cpp763 + ../sendcoinsdialog.cpp776 - + 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 - + + Paying only the minimum fee is just fine as long as there is less transaction volume than space in the blocks. But be aware that this can end up in a never confirming transaction once there is more demand for transactions than the network can process. + 860 + 873 + + Recommended: - 892 + 902 - + Custom: - 922 + 932 - + Send to multiple recipients at once - 1137 + 1147 - + Add &Recipient - 1140 + 1150 - + Clear all fields of the form. - 1120 + 1130 - + 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 + 876 - + (Smart fee not initialized yet. This usually takes a few blocks…) - 971 + 981 - + Confirmation time target: - 997 + 1007 - + Enable Replace-By-Fee - 1055 + 1065 - + 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 + 1068 - + Clear &All - 1123 + 1133 - + Balance: - 1178 + 1188 - + Confirm the send action - 1094 + 1104 - + S&end - 1097 + 1107 - + Copy quantity - 95 + 96 - + Copy amount - 96 + 97 - + Copy fee - 97 + 98 - + Copy after fee - 98 + 99 - + Copy bytes - 99 + 100 - + Copy change - 100 + 101 - + %1 (%2 blocks) - 172 + 173 - + Sign on device - 202 + 203 "device" usually means a hardware wallet. - + Connect your hardware wallet first. - 205 + 206 - + Set external signer script path in Options -> Wallet - 209 + 210 "External signer" means using devices such as hardware wallets. - + Cr&eate Unsigned - 212 + 213 - + Creates a Partially Signed Bitcoin Transaction (PSBT) for use with e.g. an offline %1 wallet, or a PSBT-compatible hardware wallet. - 213 + 214 - + %1 to '%2' - 316 + 320 - + %1 to %2 - 321 + 325 - + To review recipient list click "Show Details…" - 388 + 397 - + Sign failed - 451 + 461 - + External signer not found - 456 + 466 "External signer" means using devices such as hardware wallets. - + External signer failure - 462 + 472 "External signer" means using devices such as hardware wallets. - + Save Transaction Data - 426 + 436 - + Partially Signed Transaction (Binary) - 428 + 438 Expanded name of the binary PSBT file format. See: BIP 174. - + PSBT saved - 436 + 446 Popup message when a PSBT has been saved to a file - + External balance: - 709 + 722 - + or - 384 + 389 - + You can increase the fee later (signals Replace-By-Fee, BIP-125). - 366 + 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. - 335 + 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' - 305 + 309 - + Do you want to create this transaction? - 329 + 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. - 340 + 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. - 343 + 347 Text to prompt a user to review the details of the transaction they are attempting to send. - + Transaction fee - 351 + 355 - + %1 kvB - 356 + 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. - 368 + 372 - + Total Amount - 381 + 386 - + + and + 392 + + Unsigned Transaction - 405 + 414 PSBT copied Caption of "PSBT has been copied" messagebox - + The PSBT has been copied to the clipboard. You can also save it. - 406 + 415 - + PSBT saved to disk - 436 + 446 - + Confirm send coins - 485 + 496 - + Watch-only balance: - 712 + 725 - + The recipient address is not valid. Please recheck. - 736 + 749 - + The amount to pay must be larger than 0. - 739 + 752 - + The amount exceeds your balance. - 742 + 755 - + The total exceeds your balance when the %1 transaction fee is included. - 745 + 758 - + Duplicate address found: addresses should only be used once each. - 748 + 761 - + Transaction creation failed! - 751 + 764 - + A fee higher than %1 is considered an absurdly high fee. - 755 + 768 - + %1/kvB - 834 - 869 + 851 + 886 - 883 - + 900 + Estimated to begin confirmation within %n block(s). - + Estimated to begin confirmation within %n block(s). - - Warning: Invalid Bitcoin address - 978 + + Warning: Invalid address + 997 - + Warning: Unknown change address - 983 + 1002 - + Confirm custom change address - 986 + 1005 - + 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? - 986 + 1005 - + (no label) - 1007 + 1028 - + 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 @@ -3738,117 +3735,117 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - + Send - 146 + 148 - + Create Unsigned - 148 + 150 - + 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 system 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 @@ -3856,59 +3853,59 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - + The entered address is invalid. 120 219 - + Please check the address and try again. 120 220 - + 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. 127 225 - + Wallet unlock was cancelled. 135 - + No error 146 - + Private key for the entered address is not available. 149 - + Message signing failed. 152 - + Message signed. 164 - + The signature could not be decoded. 230 - + Please check the signature and try again. 231 238 - + The signature did not match the message digest. 237 - + Message verification failed. 243 - + Message verified. 214 @@ -3916,19 +3913,19 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - + (press q to shutdown and continue later) - 175 + 176 - + press q to shutdown - 176 + 177 - + kB/s 74 @@ -3936,194 +3933,194 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - + conflicted with a transaction with %1 confirmations 40 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 47 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 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 unconfirmed transaction that is not in the memory pool. - + abandoned 58 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 66 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 71 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 121 - + Date 124 - + Source 131 - + Generated 131 - + From 136 150 222 - + unknown 150 - + To 151 171 - 241 + 242 - + own address 153 - 248 + 249 - + watch-only 153 222 - 250 + 251 - + label 155 - + Credit 191 203 - 257 - 287 - 347 + 258 + 288 + 349 193 - + matures in %n more block(s) - + matures in %n more block(s) - + not accepted 195 - + Debit - 255 - 281 - 344 + 256 + 282 + 345 - + Total debit - 265 + 266 - + Total credit - 266 + 267 - + Transaction fee - 271 + 272 - + Net amount - 293 + 294 - + Message - 299 - 311 + 300 + 312 - + Comment - 301 + 302 - + Transaction ID - 303 + 304 - + Transaction total size - 304 + 305 - + Transaction virtual size - 305 + 306 - + Output index - 306 + 307 - + %1 (Certificate was not verified) - 322 + 323 - + Merchant - 325 + 326 - + 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. - 333 + 334 - + Debug information - 341 + 342 - + Transaction - 349 + 353 - + Inputs - 352 + 356 - + Amount - 371 + 375 - + true - 372 - 373 + 376 + 377 - + false - 372 - 373 + 376 + 377 - + This pane shows a detailed description of the transaction 20 @@ -4131,7 +4128,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - + Details for %1 18 @@ -4139,298 +4136,318 @@ Note: Since the fee is calculated on a per-byte basis, a fee rate of "100 - + Date - 258 + 260 - + Type - 258 + 260 - + Label - 258 + 260 - + + Amount + 260 + + Unconfirmed - 318 + 314 - + Abandoned - 321 + 317 - + Confirming (%1 of %2 recommended confirmations) - 324 + 320 - + Confirmed (%1 confirmations) - 327 + 323 - + Conflicted - 330 + 326 - + Immature (%1 confirmations, will be available after %2) - 333 + 329 - + Generated but not accepted - 336 + 332 - + Received with - 375 + 371 - + Received from - 377 + 373 - + Sent to - 380 + 376 - + Mined - 382 + 378 + + + Fee + 380 - watch-only - 410 + Issuance + 382 - (n/a) - 424 + watch-only + 412 - (no label) - 629 + (n/a) + 427 - Transaction status. Hover over this field to show number of confirmations. - 668 + (no label) + 633 - Date and time that the transaction was received. - 670 + Transaction status. Hover over this field to show number of confirmations. + 672 - Type of transaction. - 672 + Date and time that the transaction was received. + 674 - Whether or not a watch-only address is involved in this transaction. - 674 + Type of transaction. + 676 - User-defined intent/purpose of the transaction. - 676 + Whether or not a watch-only address is involved in this transaction. + 678 + User-defined intent/purpose of the transaction. + 680 + + Amount removed from or added to balance. - 678 + 682 - + All 73 89 - + Today 74 - + This week 75 - + This month 76 - + Last month 77 - + This year 78 - + Received with 90 - + Sent to 92 - + Mined 94 - + Other - 95 + 97 - + Enter address, transaction id, or label to search - 100 + 102 - + Min amount - 104 + 106 - + Range… 79 - + + Fee + 95 + + + Issuance + 96 + + &Copy address - 168 + 170 - + Copy &label - 169 + 171 - + Copy &amount - 170 + 172 - + Copy transaction &ID - 171 + 173 - + Copy &raw transaction - 172 + 174 - + Copy full transaction &details - 173 + 175 - + &Show transaction details - 174 + 176 - + Increase transaction &fee - 176 + 178 - + A&bandon transaction - 179 + 181 - + &Edit address label - 180 + 182 - + Show in %1 - 239 + 241 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 - 358 + 360 - + Comma separated file - 361 + 363 Expanded name of the CSV file format. See: https://en.wikipedia.org/wiki/Comma-separated_values. - + Confirmed - 370 + 372 - + Watch-only - 372 + 374 - + Date - 373 + 375 - + Type - 374 + 376 - + Label - 375 + 377 - + Address - 376 + 378 - + ID - 378 + 380 - + Exporting Failed - 381 + 383 - + There was an error trying to save the transaction history to %1. - 381 + 383 - + Exporting Successful - 385 + 387 - + The transaction history was successfully saved to %1. - 385 + 387 - + Range: - 558 + 560 - + to - 566 + 568 - + 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 @@ -4438,113 +4455,113 @@ Go to File > Open Wallet to load a wallet. - + Send Coins - 224 - 237 + 264 + 277 - + Fee bump error - 491 - 540 - 560 - 565 + 531 + 580 + 600 + 605 - + Increasing transaction fee failed - 491 + 531 - + Do you want to increase the fee? - 498 + 538 Asks a user if they would like to manually increase the fee of a transaction that has already been created. - + Current fee: - 502 + 542 - + Increase: - 506 + 546 - + New fee: - 510 + 550 - + 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. - 518 + 558 - + Confirm fee bump - 523 + 563 - + Can't draft transaction. - 540 + 580 - + PSBT copied - 547 + 587 - + Fee-bump PSBT copied to clipboard - 547 + 587 - + Can't sign transaction. - 560 + 600 - + Could not commit transaction - 565 + 605 - + Signer error - 578 + 618 - + Can't display address - 581 + 621 - + &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 @@ -4552,225 +4569,213 @@ Go to File > Open Wallet to load a wallet. - + The %s developers 12 - + %s corrupt. Try using the wallet tool bitcoin-wallet to salvage or restoring a backup. 13 - + %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. 16 - + %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. 28 - + Cannot downgrade wallet from version %i to version %i. Wallet version unchanged. 32 - + Cannot upgrade a non HD split wallet from version %i to version %i without upgrading to support pre-split keypool. Please use version %i or no version specified. 38 - + Disk space for %s may not accommodate the block files. Approximately %u GB of data will be stored in this directory. - 42 + 48 - + Distributed under the MIT software license, see the accompanying file %s or %s - 45 + 51 - + 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 - 51 + 57 - + Error reading %s! Transaction data may be missing or incorrect. Rescanning wallet. - 59 + 65 - + Error starting/committing db txn for wallet transactions removal process - 62 + 68 - + Error: Dumpfile format record is incorrect. Got "%s", expected "format". - 67 + 73 - + Error: Dumpfile identifier record is incorrect. Got "%s", expected "%s". - 69 + 75 - + Error: Dumpfile version is not supported. This version of bitcoin-wallet only supports version 1 dumpfiles. Got dumpfile with version %s - 71 + 77 - + Error: Legacy wallets only support the "legacy", "p2sh-segwit", and "bech32" address types - 77 + 83 - + Error: Unable to produce descriptors for this legacy wallet. Make sure to provide the wallet's passphrase if it is encrypted. - 83 + 89 - + File %s already exists. If you are sure this is what you want, move it out of the way first. - 98 + 104 - + 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. - 112 + 118 - + Invalid value detected for '-wallet' or '-nowallet'. '-wallet' requires a string value, while '-nowallet' accepts only '1' to disable all wallets - 116 + 122 - + More than one onion bind address is provided. Using %s for the automatically created Tor onion service. - 123 + 129 - + No dump file provided. To use createfromdump, -dumpfile=<filename> must be provided. - 126 + 132 - + No dump file provided. To use dump, -dumpfile=<filename> must be provided. - 129 + 135 - + No wallet file format provided. To use createfromdump, -format=<format> must be provided. - 131 - - - Option '-upnp' is set but UPnP support was dropped in version 29.0. Consider using '-natpmp' instead. - 134 + 137 - + Please contribute if you find %s useful. Visit %s for further information about the software. - 150 + 153 - + Prune configured below the minimum of %d MiB. Please use a higher number. - 153 + 156 - + Prune mode is incompatible with -reindex-chainstate. Use full -reindex instead. - 155 + 158 - + Prune: last wallet synchronisation goes beyond pruned data. You need to -reindex (download the whole blockchain again in case of pruned node) - 158 + 161 - + 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. - 164 + 167 - + SQLiteDatabase: Unknown sqlite wallet schema version %d. Only version %d is supported - 168 + 171 - + 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 - 179 + 182 - + The transaction amount is too small to send after the fee has been deducted - 195 + 198 - + This error could occur if this wallet was not shutdown cleanly and was last loaded using a build with a newer version of Berkeley DB. If so, please use the software that last loaded this wallet - 197 + 200 - + This is a pre-release test build - use at your own risk - do not use for mining or merchant applications - 201 + 204 - + This is the maximum transaction fee you pay (in addition to the normal fee) to prioritize partial spend avoidance over regular coin selection. - 204 + 207 - + This is the transaction fee you may discard if change is smaller than dust at this level - 207 + 210 - + This is the transaction fee you may pay when fee estimates are not available. - 210 + 213 - + Total length of network version string (%i) exceeds maximum length (%i). Reduce the number or size of uacomments. - 212 - - - Unable to replay blocks. You will need to rebuild the database using -reindex-chainstate. - 221 - - - Unknown wallet file format "%s" provided. Please provide one of "bdb" or "sqlite". - 231 + 215 - Unsupported category-specific logging level %1$s=%2$s. Expected %1$s=<category>:<loglevel>. Valid categories: %3$s. Valid loglevels: %4$s. - 239 + Unable to replay blocks. You will need to rebuild the database using -reindex-chainstate. + 227 - Unsupported chainstate database format found. Please restart with -reindex-chainstate. This will rebuild the chainstate database. - 242 + Unknown wallet file format "%s" provided. Please provide one of "bdb" or "sqlite". + 237 - Wallet created successfully. The legacy wallet type is being deprecated and support for creating and opening legacy wallets will be removed in the future. + Unsupported category-specific logging level %1$s=%2$s. Expected %1$s=<category>:<loglevel>. Valid categories: %3$s. Valid loglevels: %4$s. 245 - Wallet loaded successfully. The legacy wallet type is being deprecated and support for creating and opening legacy wallets will be removed in the future. Legacy wallets can be migrated to a descriptor wallet with migratewallet. - 249 + Unsupported chainstate database format found. Please restart with -reindex-chainstate. This will rebuild the chainstate database. + 248 Warning: Dumpfile wallet format "%s" does not match command line specified format "%s". - 254 + 251 Warning: Private keys detected in wallet {%s} with disabled private keys - 257 + 254 Warning: We do not appear to fully agree with our peers! You may need to upgrade, or other nodes may need to upgrade. - 259 + 256 Witness data for blocks after height %d requires validation. Please restart with -reindex. - 262 + 259 You need to rebuild the database using -reindex to go back to unpruned mode. This will redownload the entire blockchain - 265 + 262 %s is set very high! - 284 + 281 -maxmempool must be at least %d MB - 285 + 282 Cannot obtain a lock on directory %s. %s is probably already running. - 289 + 287 Cannot resolve -%s address: '%s' - 290 + 288 Cannot set -forcednsseed to true when setting -dnsseed to false. - 291 + 289 Cannot set -peerblockfilters without -blockfilterindex. - 292 + 290 %s is set very high! Fees this large could be paid on a single transaction. @@ -4781,818 +4786,854 @@ Go to File > Open Wallet to load a wallet. 35 - Error loading %s: External signer wallet being loaded without external signer support compiled - 48 + Change output could not be blinded as there are no blinded inputs and no other blinded outputs. + 42 - Error reading %s! All keys read correctly, but transaction data or address metadata may be missing or incorrect. - 56 + Could not locate mainchain RPC credentials. No authentication cookie could be found, and no mainchainrpcpassword is set in the configuration file (%s) + 45 - Error: Address book data in wallet cannot be identified to belong to migrated wallets - 64 + Error loading %s: External signer wallet being loaded without external signer support compiled + 54 - Error: Duplicate descriptors created during migration. Your wallet may be corrupted. - 74 + Error reading %s! All keys read correctly, but transaction data or address metadata may be missing or incorrect. + 62 - Error: Transaction %s in wallet cannot be identified to belong to migrated wallets - 80 + Error: Address book data in wallet cannot be identified to belong to migrated wallets + 70 - Failed to calculate bump fees, because unconfirmed UTXOs depend on enormous cluster of unconfirmed transactions. - 86 + Error: Duplicate descriptors created during migration. Your wallet may be corrupted. + 80 - Failed to remove snapshot chainstate dir (%s). Manually remove it before restarting. - - 89 + Error: Transaction %s in wallet cannot be identified to belong to migrated wallets + 86 - Failed to rename invalid peers.dat file. Please move or delete it and try again. + Failed to calculate bump fees, because unconfirmed UTXOs depend on enormous cluster of unconfirmed transactions. 92 - Fee estimation failed. Fallbackfee is disabled. Wait a few blocks or enable %s. + Failed to remove snapshot chainstate dir (%s). Manually remove it before restarting. + 95 - Flushing block file to disk failed. This is likely the result of an I/O error. - 101 + Failed to rename invalid peers.dat file. Please move or delete it and try again. + 98 - Flushing undo file to disk failed. This is likely the result of an I/O error. - 104 + Fee estimation failed. Fallbackfee is disabled. Wait a few blocks or enable %s. + 101 - Incompatible options: -dnsseed=1 was explicitly specified, but -onlynet forbids connections to IPv4/IPv6 - 106 + Flushing block file to disk failed. This is likely the result of an I/O error. + 107 - Invalid amount for %s=<amount>: '%s' (must be at least the minrelay fee of %s to prevent stuck transactions) - 109 + Flushing undo file to disk failed. This is likely the result of an I/O error. + 110 - Maximum transaction weight is less than transaction weight without inputs - 119 + Incompatible options: -dnsseed=1 was explicitly specified, but -onlynet forbids connections to IPv4/IPv6 + 112 - Maximum transaction weight is too low, can not accommodate change output - 121 + Invalid amount for %s=<amount>: '%s' (must be at least the minrelay fee of %s to prevent stuck transactions) + 115 - Outbound connections restricted to CJDNS (-onlynet=cjdns) but -cjdnsreachable is not provided - 137 + Maximum transaction weight is less than transaction weight without inputs + 125 - Outbound connections restricted to Tor (-onlynet=onion) but the proxy for reaching the Tor network is explicitly forbidden: -onion=0 - 140 + Maximum transaction weight is too low, can not accommodate change output + 127 - 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 - 143 + Outbound connections restricted to CJDNS (-onlynet=cjdns) but -cjdnsreachable is not provided + 140 - Outbound connections restricted to i2p (-onlynet=i2p) but -i2psam is not provided - 147 + Outbound connections restricted to Tor (-onlynet=onion) but the proxy for reaching the Tor network is explicitly forbidden: -onion=0 + 143 - Rename of '%s' -> '%s' failed. Cannot clean up the background chainstate leveldb directory. - 161 + 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 + 146 - Specified -blockmaxweight (%d) exceeds consensus maximum block weight (%d) - 171 + Outbound connections restricted to i2p (-onlynet=i2p) but -i2psam is not provided + 150 - Specified -blockreservedweight (%d) exceeds consensus maximum block weight (%d) - 173 + Rename of '%s' -> '%s' failed. Cannot clean up the background chainstate leveldb directory. + 164 - Specified -blockreservedweight (%d) is lower than minimum safety value of (%d) - 176 + Specified -blockmaxweight (%d) exceeds consensus maximum block weight (%d) + 174 - 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 - 184 + Specified -blockreservedweight (%d) exceeds consensus maximum block weight (%d) + 176 - The inputs size exceeds the maximum weight. Please try sending a smaller amount or manually consolidating your wallet's UTXOs - 188 + Specified -blockreservedweight (%d) is lower than minimum safety value of (%d) + 179 - The preselected coins total amount does not cover the transaction target. Please allow other inputs to be automatically selected or include more coins manually - 191 + 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 + 187 - Transaction requires one destination of non-0 value, a non-0 feerate, or a pre-selected input - 215 + The inputs size exceeds the maximum weight. Please try sending a smaller amount or manually consolidating your wallet's UTXOs + 191 - UTXO snapshot failed to validate. Restart to resume normal initial block download, or try loading a different snapshot. - 218 + The preselected coins total amount does not cover the transaction target. Please allow other inputs to be automatically selected or include more coins manually + 194 - Unconfirmed UTXOs are available, but spending them creates a chain of transactions that will be rejected by the mempool - 224 + Transaction output could not be blinded as there are no blinded inputs and no other blinded outputs. + 218 + Transaction requires one destination of non-0 value, a non-0 feerate, or a pre-selected input + 221 + + + UTXO snapshot failed to validate. Restart to resume normal initial block download, or try loading a different snapshot. + 224 + + + Unconfirmed UTXOs are available, but spending them creates a chain of transactions that will be rejected by the mempool + 230 + + Unexpected legacy entry in descriptor wallet found. Loading wallet %s The wallet might have been tampered with or created with malicious intent. - 227 + 233 - + Unrecognized descriptor found. Loading wallet %s The wallet might had been created on a newer version. Please try running the latest software version. - 234 + 240 - + 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. - 268 + 265 - + Unable to cleanup failed migration - 276 + 273 - + Unable to restore backup of wallet. - 279 + 276 - + whitebind may only be used for incoming connections ("out" was passed) - 282 + 279 - + A fatal internal error occurred, see debug.log for details: - 286 + 283 - + Assumeutxo data not found for the given blockhash '%s'. - 287 + 284 - + + Awaiting mainchain RPC warmup + 285 + + Block verification was interrupted - 288 + 286 - + Cannot write to directory '%s'; check permissions. - 293 + 291 - + Config setting for %s only applied on %s network when in [%s] section. - 294 + 292 - + Copyright (C) %i-%i - 295 + 293 - + Corrupt block found indicating potential hardware failure. - 296 + 294 - + Corrupted block database detected - 297 + 295 - + Could not find asmap file %s - 298 + 296 - + Could not parse asmap file %s - 299 + 297 - + Disk space is too low! - 300 + 298 - + Done loading - 302 + 300 - + Dump file %s does not exist. - 303 + 301 - + Elliptic curve cryptography sanity check failure. %s is shutting down. - 304 + 302 - + Error creating %s - 305 + 303 - + Error initializing block database - 306 + 304 - + Error initializing wallet database environment %s! - 307 + 305 - + Error loading %s - 308 + 306 - + Error loading %s: Private keys can only be disabled during creation - 309 + 307 - + Error loading %s: Wallet corrupted - 310 + 308 - + Error loading %s: Wallet requires newer version of %s - 311 + 309 - + Error loading block database - 312 + 310 - + Error loading databases - 313 + 311 - + Error opening block database - 314 + 312 - + Error opening coins database - 315 + 313 - + Error reading configuration file: %s - 316 + 314 - + Error reading from database, shutting down. - 317 + 315 - + Error reading next record from wallet database - 318 + 316 - + Error: Cannot extract destination from the generated scriptpubkey - 319 + 317 - + Error: Couldn't create cursor into database - 322 + 320 - + Error: Disk space is low for %s - 323 + 321 - + Error: Dumpfile checksum does not match. Computed %s, expected %s - 324 + 322 - + Error: Failed to create new watchonly wallet - 325 + 323 - + Error: Got key that was not hex: %s - 326 + 324 - + Error: Got value that was not hex: %s - 327 + 325 - + Error: Keypool ran out, please call keypoolrefill first - 328 + 326 - + Error: Missing checksum - 329 + 327 - + Error: No %s addresses available. - 330 + 328 - + Error: This wallet already uses SQLite - 331 + 329 - + Error: This wallet is already a descriptor wallet - 332 + 330 - + Error: Unable to begin reading all records in the database - 333 + 331 - + Error: Unable to make a backup of your wallet - 334 + 332 - + Error: Unable to parse version %u as a uint32_t - 335 + 333 - + Error: Unable to read all records in the database - 336 + 334 - + Error: Unable to read wallet's best block locator record - 337 + 335 - + Error: Unable to remove watchonly address book data - 338 + 336 - + Error: Unable to write data to disk for wallet %s - 339 + 337 - + Error: Unable to write record to new wallet - 340 + 338 - + Error: Unable to write solvable wallet best block locator record - 341 + 339 - + Error: Unable to write watchonly wallet best block locator record - 342 + 340 - + Error: database transaction cannot be executed for wallet %s - 345 + 343 - + Failed to connect best block (%s). - 346 + 344 - + Failed to disconnect block. - 347 + 345 - + Failed to listen on any port. Use -listen=0 if you want this. - 348 + 346 - + Failed to read block. - 349 + 347 - + Failed to rescan the wallet during initialization - 350 + 348 - + Failed to start indexes, shutting down.. - 351 + 349 - + Failed to verify database - 352 + 350 - + Failed to write block. - 353 + 351 - + Failed to write to block index database. - 354 + 352 - + Failed to write to coin database. - 355 + 353 - + Failed to write undo data. - 356 + 354 - + Failure removing transaction: %s - 357 + 355 - + Fee rate (%s) is lower than the minimum fee rate setting (%s) - 358 + 356 - + Ignoring duplicate -wallet %s. - 359 + 357 - + Importing… - 360 + 358 - + Incorrect or no genesis block found. Wrong datadir for network? - 361 + 359 - + Initialization sanity check failed. %s is shutting down. - 362 + 360 - + Input not found or already spent - 363 + 361 - + Insufficient dbcache for block verification - 364 + 362 - + Insufficient funds - 365 + 363 - + Invalid -i2psam address or hostname: '%s' - 366 + 364 - + Invalid -onion address or hostname: '%s' - 367 + 365 - + Invalid -proxy address or hostname: '%s' - 368 + 366 - + Invalid P2P permission: '%s' - 369 + 367 - + Invalid amount for %s=<amount>: '%s' (must be at least %s) - 370 + 368 - + Invalid amount for %s=<amount>: '%s' - 371 + 369 - + Invalid amount for -%s=<amount>: '%s' - 372 + 370 - + Invalid netmask specified in -whitelist: '%s' - 373 + 371 - + Invalid port specified in %s: '%s' - 374 + 372 - + Invalid pre-selected input %s - 375 + 373 - + Listening for incoming connections failed (listen returned error %s) - 376 + 374 - + Loading P2P addresses… - 377 + 375 - + Loading banlist… - 378 + 376 - + Loading block index… - 379 + 377 - + Loading wallet… - 380 + 378 - + Maximum transaction weight must be between %d and %d - 381 + 379 - + Missing amount - 382 + 380 - + Missing solving data for estimating transaction size - 383 + 381 - + Need to specify a port with -whitebind: '%s' - 384 + 382 - + No addresses available - 385 + 383 - + + No asset provided for recipient + 384 + + Not found pre-selected input %s - 387 + 386 - + Not solvable pre-selected input %s - 388 + 387 - + Only direction was set, no permissions: '%s' + 388 + + + Peg-in input has invalid proof. 389 - + Prune cannot be configured with a negative value. 390 - + Prune mode is incompatible with -txindex. 391 - + Pruning blockstore… 392 - + Reducing -maxconnections from %d to %d, because of system limitations. 393 - + Replaying blocks… 394 - + Rescanning… 395 - + SQLiteDatabase: Failed to execute statement to verify database: %s 396 - + SQLiteDatabase: Failed to prepare statement to verify database: %s 397 - + SQLiteDatabase: Failed to read database verification error: %s 398 - + SQLiteDatabase: Unexpected application id. Expected %u, got %u 399 - - Section [%s] is not recognized. - 400 - - + Signer did not echo address - 403 + 402 - + Signer echoed unexpected address %s - 404 + 403 - + Signer returned error: %s - 405 + 404 - + Signing transaction failed - 406 + 405 - + Specified -walletdir "%s" does not exist - 407 + 406 - + Specified -walletdir "%s" is a relative path - 408 + 407 - + Specified -walletdir "%s" is not a directory - 409 + 408 - + Specified blocks directory "%s" does not exist. - 410 + 409 - + Specified data directory "%s" does not exist. - 411 + 410 - + Starting network threads… - 412 + 411 - + System error while flushing: %s - 413 + 412 - + System error while loading external block file: %s - 414 + 413 - + System error while saving block to disk: %s - 415 + 414 - + The source code is available from %s. - 416 + 415 - + The specified config file %s does not exist - 417 + 416 - + The transaction amount is too small to pay the fee - 418 + 417 - + The transactions removal process can only be executed within a db txn - 419 + 418 - + The wallet will avoid paying less than the minimum relay fee. - 420 + 419 - + There is no ScriptPubKeyManager for this address - 421 + 420 - + This is experimental software. - 422 + 421 - + This is the minimum transaction fee you pay on every transaction. - 423 + 422 - + This is the transaction fee you will pay if you send a transaction. - 424 + 423 - + Transaction %s does not belong to this wallet - 425 + 424 - + Transaction amount too small - 426 + 425 - + Transaction amounts must not be negative - 427 + 426 - + Transaction change output index out of range + 427 + + + Transaction is missing an output for input asset %s 428 - + Transaction must have at least one recipient 429 - + Transaction needs a change address, but we can't generate it. 430 - + Transaction too large 431 - - Unable to bind to %s on this computer (bind returned error %s) + + Unable to allocate memory for -maxsigcachesize: '%s' MiB 432 - - Unable to bind to %s on this computer. %s is probably already running. + + Unable to bind to %s on this computer (bind returned error %s) 433 - - Unable to create the PID file '%s': %s + + Unable to bind to %s on this computer. %s is probably already running. 434 - - Unable to find UTXO for external input + + Unable to blind the transaction properly. This should not happen. 435 - - Unable to generate initial keys + + Unable to create the PID file '%s': %s 436 - - Unable to generate keys + + Unable to find UTXO for external input 437 - - Unable to open %s for writing + + Unable to generate initial keys 438 - - Unable to parse -maxuploadtarget: '%s' + + Unable to generate keys 439 - - Unable to start HTTP server. See debug log for details. + + Unable to open %s for writing 440 - - Unable to unload the wallet before migrating + + Unable to parse -maxuploadtarget: '%s' 441 - - Unknown -blockfilterindex value %s. + + Unable to start HTTP server. See debug log for details. 442 - - Unknown address type '%s' + + Unable to unload the wallet before migrating 443 - - Unknown change type '%s' + + Unknown -blockfilterindex value %s. 444 - - Unknown network specified in -onlynet: '%s' + + Unknown address type '%s' 445 - - Unknown new rules activated (versionbit %i) + + Unknown change type '%s' 446 - - Unrecognised option "%s" provided in -test=<option>. + + Unknown network specified in -onlynet: '%s' 447 - - Unsupported global logging level %s=%s. Valid values: %s. + + Unknown new rules activated (versionbit %i) 448 - - Wallet file creation failed: %s + + Unrecognised option "%s" provided in -test=<option>. + 449 + + + Unsupported global logging level %s=%s. Valid values: %s. + 450 + + + Value or asset is not explicit for pre-selected input %s 453 - + + Wallet file creation failed: %s + 456 + + acceptstalefeeestimates is not supported on %s chain. - 455 + 458 - + Unsupported logging category %s=%s. - 449 + 451 - + Do you want to rebuild the databases now? - 301 + 299 - + Error: Could not add watchonly tx %s to watchonly wallet - 320 + 318 - + Error: Could not delete watchonly transactions. - 321 + 319 - + Error: Wallet does not exist - 343 + 341 - + Error: cannot remove legacy wallet records - 344 + 342 - + Not enough file descriptors available. %d available, %d required. - 386 + 385 - + User Agent comment (%s) contains unsafe characters. - 450 + 452 - + Verifying blocks… - 451 + 454 - + Verifying wallet(s)… - 452 + 455 - + Wallet needed to be rewritten: restart %s to complete - 454 + 457 - + Settings file could not be read - 401 + 400 - + Settings file could not be written - 402 + 401 diff --git a/src/wallet/rpc/wallet.cpp b/src/wallet/rpc/wallet.cpp index bc37a3790a..e4f9063971 100644 --- a/src/wallet/rpc/wallet.cpp +++ b/src/wallet/rpc/wallet.cpp @@ -361,9 +361,7 @@ static RPCHelpMan createwallet() {"blank", RPCArg::Type::BOOL, RPCArg::Default{false}, "Create a blank wallet. A blank wallet has no keys or HD seed. One can be set using sethdseed."}, {"passphrase", RPCArg::Type::STR, RPCArg::Optional::OMITTED, "Encrypt the wallet with this passphrase."}, {"avoid_reuse", RPCArg::Type::BOOL, RPCArg::Default{false}, "Keep track of coin reuse, and treat dirty and clean coins differently with privacy considerations in mind."}, - {"descriptors", RPCArg::Type::BOOL, RPCArg::Default{true}, "Create a native descriptor wallet. The wallet will use descriptors internally to handle address creation." - " Setting to \"false\" will create a legacy wallet; This is only possible with the -deprecatedrpc=create_bdb setting because, the legacy wallet type is being deprecated and" - " support for creating and opening legacy wallets will be removed in the future."}, + {"descriptors", RPCArg::Type::BOOL, RPCArg::Default{true}, "Create a native descriptor wallet. The wallet will use descriptors internally to handle address creation."}, {"load_on_startup", RPCArg::Type::BOOL, RPCArg::Optional::OMITTED, "Save wallet name to persistent settings and load on startup. True to add wallet to startup list, false to remove, null to leave unchanged."}, {"external_signer", RPCArg::Type::BOOL, RPCArg::Default{false}, "Use an external signer such as a hardware wallet. Requires -signer to be configured. Wallet creation will fail if keys cannot be fetched. Requires disable_private_keys and descriptors set to true."}, }, diff --git a/src/wallet/wallet.cpp b/src/wallet/wallet.cpp index 24e42a9470..0321defcf0 100644 --- a/src/wallet/wallet.cpp +++ b/src/wallet/wallet.cpp @@ -296,11 +296,6 @@ std::shared_ptr LoadWalletInternal(WalletContext& context, const std::s return nullptr; } - // Legacy wallets are being deprecated, warn if the loaded wallet is legacy - if (!wallet->IsWalletFlagSet(WALLET_FLAG_DESCRIPTORS)) { - warnings.emplace_back(_("Wallet loaded successfully. The legacy wallet type is being deprecated and support for creating and opening legacy wallets will be removed in the future. Legacy wallets can be migrated to a descriptor wallet with migratewallet.")); - } - NotifyWalletLoaded(context, wallet); AddWallet(context, wallet); wallet->postInitProcess(); @@ -489,11 +484,6 @@ std::shared_ptr CreateWallet(WalletContext& context, const std::string& // Write the wallet settings UpdateWalletSetting(*context.chain, name, load_on_start, warnings); - // Legacy wallets are being deprecated, warn if a newly created wallet is legacy - if (!(wallet_creation_flags & WALLET_FLAG_DESCRIPTORS)) { - warnings.emplace_back(_("Wallet created successfully. The legacy wallet type is being deprecated and support for creating and opening legacy wallets will be removed in the future.")); - } - status = DatabaseStatus::SUCCESS; return wallet; } diff --git a/test/functional/wallet_createwallet.py b/test/functional/wallet_createwallet.py index 06386bbbe9..2809183719 100755 --- a/test/functional/wallet_createwallet.py +++ b/test/functional/wallet_createwallet.py @@ -161,7 +161,7 @@ def run_test(self): assert_equal(walletinfo['keypoolsize_hd_internal'], keys) # Allow empty passphrase, but there should be a warning resp = self.nodes[0].createwallet(wallet_name='w7', disable_private_keys=False, blank=False, passphrase='') - assert_equal(resp["warnings"], [EMPTY_PASSPHRASE_MSG] if self.options.descriptors else [EMPTY_PASSPHRASE_MSG, LEGACY_WALLET_MSG]) + assert_equal(resp["warnings"], [EMPTY_PASSPHRASE_MSG]) w7 = node.get_wallet_rpc('w7') assert_raises_rpc_error(-15, 'Error: running with an unencrypted wallet, but walletpassphrase was called.', w7.walletpassphrase, '', 60) @@ -175,19 +175,6 @@ def run_test(self): self.log.info('Using a passphrase with private keys disabled returns error') assert_raises_rpc_error(-4, 'Passphrase provided but private keys are disabled. A passphrase is only used to encrypt private keys, so cannot be used for wallets with private keys disabled.', self.nodes[0].createwallet, wallet_name='w9', disable_private_keys=True, passphrase='thisisapassphrase') - if self.is_bdb_compiled(): - self.log.info("Test legacy wallet deprecation") - result = self.nodes[0].createwallet(wallet_name="legacy_w0", descriptors=False, passphrase=None) - assert_equal(result, { - "name": "legacy_w0", - "warnings": [LEGACY_WALLET_MSG], - }) - result = self.nodes[0].createwallet(wallet_name="legacy_w1", descriptors=False, passphrase="") - assert_equal(result, { - "name": "legacy_w1", - "warnings": [EMPTY_PASSPHRASE_MSG, LEGACY_WALLET_MSG], - }) - self.log.info("Check that the version number is being logged correctly") with node.assert_debug_log(expected_msgs=[], unexpected_msgs=["Last client version = ", "Wallet file version = "]): node.createwallet("version_check")