AddressBookPageRight-click to edit address or labelCreate a new address&NewCopy the currently selected address to the system clipboard&CopyC&loseDelete the currently selected address from the listExport the data in the current tab to a file&Export&DeleteChoose the address to send coins toChoose the address to receive coins withC&hooseSending addressesReceiving addressesThese are your Bitcoin addresses for sending payments. Always check the amount and the receiving address before sending coins.These are your Bitcoin addresses for receiving payments. It is recommended to use a new receiving address for each transaction.&Copy AddressCopy &Label&EditExport Address ListComma separated file (*.csv)Exporting FailedThere was an error trying to save the address list to %1. Please try again.AddressTableModelLabelAddress(no label)AskPassphraseDialogPassphrase DialogEnter passphraseNew passphraseRepeat new passphraseShow passwordEnter the new passphrase to the wallet.<br/>Please use a passphrase of <b>ten or more random characters</b>, or <b>eight or more words</b>.Encrypt walletThis operation needs your wallet passphrase to unlock the wallet.Unlock walletThis operation needs your wallet passphrase to decrypt the wallet.Decrypt walletChange passphraseEnter the old passphrase and new passphrase to the wallet.Confirm wallet encryptionWarning: If you encrypt your wallet and lose your passphrase, you will <b>LOSE ALL OF YOUR BITCOINS</b>!Are you sure you wish to encrypt your wallet?Wallet encrypted%1 will close now to finish the encryption process. Remember that encrypting your wallet cannot fully protect your bitcoins from being stolen by malware infecting your computer.IMPORTANT: Any previous backups you have made of your wallet file should be replaced with the newly generated, encrypted wallet file. For security reasons, previous backups of the unencrypted wallet file will become useless as soon as you start using the new, encrypted wallet.Wallet encryption failedWallet encryption failed due to an internal error. Your wallet was not encrypted.The supplied passphrases do not match.Wallet unlock failedThe passphrase entered for the wallet decryption was incorrect.Wallet decryption failedWallet passphrase was successfully changed.Warning: The Caps Lock key is on!BanTableModelIP/NetmaskBanned UntilBitcoinGUISign &message...Synchronising with network...&OverviewNodeShow general overview of wallet&TransactionsBrowse transaction historyE&xitQuit application&About %1Show information about %1About &QtShow information about Qt&Options...Modify configuration options for %1&Encrypt Wallet...&Backup Wallet...&Change Passphrase...&Sending addresses...&Receiving addresses...Open &URI...Click to disable network activity.Network activity disabled.Click to enable network activity again.Syncing Headers (%1%)...Reindexing blocks on disk...Send coins to a Bitcoin addressBackup wallet to another locationChange the passphrase used for wallet encryption&Debug windowOpen debugging and diagnostic console&Verify message...BitcoinWallet&Send&Receive&Show / HideShow or hide the main WindowEncrypt the private keys that belong to your walletSign messages with your Bitcoin addresses to prove you own themVerify messages to ensure they were signed with specified Bitcoin addresses&File&Settings&HelpTabs toolbarRequest payments (generates QR codes and bitcoin: URIs)Show the list of used sending addresses and labelsShow the list of used receiving addresses and labelsOpen a bitcoin: URI or payment request&Command-line options%n active connection to Bitcoin network%n active connections to Bitcoin networkIndexing blocks on disk...Processing blocks on disk...Processed %n block of transaction history.Processed %n blocks of transaction history.%1 behindLast received block was generated %1 ago.Transactions after this will not yet be visible.ErrorWarningInformationUp to dateShow the %1 help message to get a list with possible Bitcoin command-line options%1 clientConnecting to peers...Catching up...Date: %1
Amount: %1
Type: %1
Label: %1
Address: %1
Sent transactionIncoming transactionHD key generation is <b>enabled</b>HD key generation is <b>disabled</b>Wallet is <b>encrypted</b> and currently <b>unlocked</b>Wallet is <b>encrypted</b> and currently <b>locked</b>A fatal error occurred. Bitcoin can no longer continue safely and will quit.CoinControlDialogCoin SelectionQuantity:Bytes:Amount:Fee:Dust:After Fee:Change:(un)select allTree modeList modeAmountReceived with labelReceived with addressDateConfirmationsConfirmedCopy addressCopy labelCopy amountCopy transaction IDLock unspentUnlock unspentCopy quantityCopy feeCopy after feeCopy bytesCopy dustCopy change(%1 locked)yesnoThis label turns red if any recipient receives an amount smaller than the current dust threshold.Can vary +/- %1 satoshi(s) per input.(no label)change from %1 (%2)(change)EditAddressDialogEdit Address&LabelThe label associated with this address list entryThe address associated with this address list entry. This can only be modified for sending addresses.&AddressNew receiving addressNew sending addressEdit receiving addressEdit sending addressThe entered address "%1" is not a valid Bitcoin address.The entered address "%1" is already in the address book.Could not unlock wallet.New key generation failed.FreespaceCheckerA new data directory will be created.nameDirectory already exists. Add %1 if you intend to create a new directory here.Path already exists, and is not a directory.Cannot create data directory here.HelpMessageDialogversion(%1-bit)About %1Command-line optionsUsage:command-line optionsUI Options:Choose data directory on startup (default: %u)Set language, for example "de_DE" (default: system locale)Start minimisedSet SSL root certificates for payment request (default: -system-)Show splash screen on startup (default: %u)Reset all settings changed in the GUIIntroWelcomeWelcome to %1.As this is the first time the program is launched, you can choose where %1 will store its data.When you click OK, %1 will begin to download and process the full %4 block chain (%2GB) starting with the earliest transactions in %3 when %4 initially launched.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.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.Use the default data directoryUse a custom data directory:BitcoinAt least %1 GB of data will be stored in this directory, and it will grow over time.Approximately %1 GB of data will be stored in this directory.%1 will download and store a copy of the Bitcoin block chain.The wallet will also be stored in this directory.Error: Specified data directory "%1" cannot be created.Error%n GB of free space available%n GB of free space available(of %n GB needed)(of %n GB needed)ModalOverlayFormRecent 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 synchronising 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 leftUnknown...Last block timeProgressProgress increase per hourcalculating...Estimated time left until syncedHideUnknown. Syncing Headers (%1)...OpenURIDialogOpen URIOpen payment request from URI or fileURI:Select payment request fileSelect payment request file to openOptionsDialogOptions&MainAutomatically start %1 after logging in to the system.&Start %1 on system loginSize of &database cacheMBNumber of script &verification threadsIP address of the proxy (e.g. IPv4: 127.0.0.1 / IPv6: ::1)Shows if the supplied default SOCKS5 proxy is used to reach peers via this network type.Use separate SOCKS&5 proxy to reach peers via Tor hidden services:Hide the icon from the system tray.&Hide tray iconMinimise 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.Third party URLs (e.g. a block explorer) that appear in the transactions tab as context menu items. %s in the URL is replaced by transaction hash. Multiple URLs are separated by vertical bar |.Active command-line options that override above options:Open the %1 configuration file from the working directory.Open Configuration FileReset all client options to default.&Reset Options&Network(0 = auto, <0 = leave that many cores free)W&alletExpertEnable coin &control featuresIf 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.&Spend unconfirmed changeAutomatically open the Bitcoin client port on the router. This only works when your router supports UPnP and it is enabled.Map port using &UPnPAccept connections from outside.Allow incomin&g connectionsConnect to the Bitcoin network through a SOCKS5 proxy.&Connect through SOCKS5 proxy (default proxy):Proxy &IP:&Port:Port of the proxy (e.g. 9050)Used for reaching peers via:IPv4IPv6TorConnect to the Bitcoin network through a separate SOCKS5 proxy for Tor hidden services.&WindowShow on a tray icon after minimising the window.&Minimise to the tray instead of the task barM&inimise on close&DisplayUser Interface &language:The user interface language can be set here. This setting will take effect after restarting %1.&Unit to show amounts in:Choose the default subdivision unit to show in the interface and when sending coins.Whether to show coin control features or not.&Third party transaction URLs&OK&CanceldefaultnoneConfirm options resetClient restart required to activate changes.Client will be shut down. Do you want to proceed?Configuration optionsThe configuration file is used to specify advanced user options which override GUI settings. Additionally, any command-line options will override this configuration file.ErrorThe configuration file could not be opened.This change would require a client restart.The supplied proxy address is invalid.OverviewPageFormThe displayed information may be out of date. Your Wallet automatically synchronises with the Bitcoin Network after a connection is established, but this process has not been completed yet.Watch-only:Available:Your current spendable balancePending:Total of transactions that have yet to be confirmed, and do not yet count toward the spendable balanceImmature:Mined balance that has not yet maturedBalancesTotal:Your current total balanceYour current balance in watch-only addressesSpendable:Recent transactionsUnconfirmed transactions to watch-only addressesMined balance in watch-only addresses that has not yet maturedCurrent total balance in watch-only addressesPaymentServerPayment request errorCannot start Bitcoin: click-to-pay handlerURI handlingPayment request fetch URL is invalid: %1Invalid payment address %1URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters.Payment request file handlingPayment request file cannot be read! This can be caused by an invalid payment request file.Payment request rejected.Payment request network doesn't match client network.Payment request expired.Payment request is not initialised.Unverified payment requests to custom payment scripts are unsupported.Invalid payment request.Requested payment amount of %1 is too small (considered dust).Refund from %1Payment request %1 is too large (%2 bytes, allowed %3 bytes).Error communicating with %1: %2Payment request cannot be parsed!Bad response from server %1Network request errorPayment acknowledgedPeerTableModelUser AgentNode/ServiceNodeIdPingSentReceivedQObjectAmountEnter a Bitcoin address (e.g. %1)%1 d%1 h%1 m%1 sNoneN/A%1 ms%n second%n seconds%n minute%n minutes%n hour%n hours%n day%n days%n week%n weeks%1 and %2%n year%n years%1 B%1 KB%1 MB%1 GB%1 didn't yet exit safely...unknownQObject::QObjectError: Specified data directory "%1" does not exist.Error: Cannot parse configuration file: %1. Only use key=value syntax.Error: %1QRImageWidget&Save Image...&Copy ImageSave QR CodePNG Image (*.png)RPCConsoleN/AClient version&InformationDebug windowGeneralUsing BerkeleyDB versionDatadirStartup timeNetworkNameNumber of connectionsBlock chainCurrent number of blocksMemory PoolCurrent number of transactionsMemory usage&ResetReceivedSent&PeersBanned peersSelect a peer to view detailed information.WhitelistedDirectionVersionStarting BlockSynced HeadersSynced BlocksUser AgentOpen the %1 debug log file from the current data directory. This can take a few seconds for large log files.Decrease font sizeIncrease font sizeServicesBan ScoreConnection TimeLast SendLast ReceivePing TimeThe duration of a currently outstanding ping.Ping WaitMin PingTime OffsetLast block time&Open&Console&Network TrafficTotalsIn:Out:Debug log fileClear console1 &hour1 &day1 &week1 &year&DisconnectBan for&UnbanWelcome to the %1 RPC console.Use up and down arrows to navigate history, and %1 to clear screen.Type %1 for an overview of available commands.For more information on using this console type %1.WARNING: Scammers have been active, telling users to type commands here and stealing their wallet contents. Do not use this console without fully understanding the ramifications of a command.Network activity disabled(node id: %1)via %1neverInboundOutboundYesNoUnknownReceiveCoinsDialog&Amount:&Label:&Message: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.An optional label to associate with the new receiving address.Use this form to request payments. All fields are <b>optional</b>.An optional amount to request. Leave this empty or zero to not request a specific amount.Clear all fields of the form.ClearRequested payments history&Request paymentBech32 addresses (BIP-173) are cheaper to spend from and offer better protection against typos. When unchecked a P2SH wrapped SegWit address will be created, compatible with older wallets.Generate Bech32 addressShow the selected request (does the same as double clicking an entry)ShowRemove the selected entries from the listRemoveCopy URICopy labelCopy messageCopy amountReceiveRequestDialogQR CodeCopy &URICopy &Address&Save Image...Request payment to %1Payment informationURIAddressAmountLabelMessageResulting URI too long, try to reduce the text for label / message.Error encoding URI into QR Code.RecentRequestsTableModelDateLabelMessage(no label)(no message)(no amount requested)RequestedSendCoinsDialogSend CoinsCoin Control FeaturesInputs...automatically selectedInsufficient funds!Quantity:Bytes:Amount:Fee:After Fee:Change:If this is activated, but the change address is empty or invalid, change will be sent to a newly generated address.Custom change addressTransaction Fee:Choose...Using the fallback fee 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.Warning: Fee estimation is currently not possible.collapse fee-settingsper kilobyteIf the custom fee is set to 1000 satoshis and the transaction is only 250 bytes, then "per kilobyte" only pays 250 satoshis in fee, while "total at least" pays 1000 satoshis. For transactions bigger than a kilobyte both pay by kilobyte.HidePaying 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 bitcoin transactions than the network can process.(read the tooltip)Recommended:Custom:(Smart fee not initialised yet. This usually takes a few blocks...)Send to multiple recipients at onceAdd &RecipientClear all fields of the form.Dust:Confirmation time target:Enable Replace-By-FeeWith 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.Clear &AllBalance:Confirm the send actionS&endCopy quantityCopy amountCopy feeCopy after feeCopy bytesCopy dustCopy change%1 (%2 blocks)%1 to %2Are you sure you want to send?added as transaction feeTotal Amount %1orYou can increase the fee later (signals Replace-By-Fee, BIP-125).Not signalling Replace-By-Fee, BIP-125.Confirm send coinsThe recipient address is not valid. Please recheck.The amount to pay must be larger than 0.The amount exceeds your balance.The total exceeds your balance when the %1 transaction fee is included.Duplicate address found: addresses should only be used once each.Transaction creation failed!The transaction was rejected with the following reason: %1A fee higher than %1 is considered an absurdly high fee.Payment request expired.Pay only the required fee of %1Estimated to begin confirmation within %n block.Estimated to begin confirmation within %n blocks.Warning: Invalid Bitcoin addressWarning: Unknown change addressConfirm custom change addressThe 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?(no label)SendCoinsEntryA&mount:Pay &To:&Label:Choose previously used addressThis is a normal payment.The Bitcoin address to send the payment toAlt+APaste address from clipboardAlt+PRemove this entryThe 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.S&ubtract fee from amountUse available balanceMessage:This is an unauthenticated payment request.This is an authenticated payment request.Enter a label for this address to add it to the list of used addressesA 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.Pay To:Memo:Enter a label for this address to add it to your address bookSendConfirmationDialogYesShutdownWindow%1 is shutting down...Do not shut down the computer until this window disappears.SignVerifyMessageDialogSignatures - Sign / Verify a Message&Sign MessageYou can sign messages/agreements with your 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.The Bitcoin address to sign the message withChoose previously used addressAlt+APaste address from clipboardAlt+PEnter the message you want to sign hereSignatureCopy the current signature to the system clipboardSign the message to prove you own this Bitcoin addressSign &MessageReset all sign message fieldsClear &All&Verify MessageEnter 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!The Bitcoin address the message was signed withVerify the message to ensure it was signed with the specified Bitcoin addressVerify &MessageReset all verify message fieldsClick "Sign Message" to generate signatureThe entered address is invalid.Please check the address and try again.The entered address does not refer to a key.Wallet unlock was cancelled.Private key for the entered address is not available.Message signing failed.Message signed.The signature could not be decoded.Please check the signature and try again.The signature did not match the message digest.Message verification failed.Message verified.SplashScreen[testnet]TrafficGraphWidgetKB/sTransactionDescOpen for %n more blockOpen for %n more blocksOpen until %1conflicted with a transaction with %1 confirmations%1/offline0/unconfirmed, %1in memory poolnot in memory poolabandoned%1/unconfirmed%1 confirmationsStatus, has not been successfully broadcast yet, broadcast through %n node, broadcast through %n nodesDateSourceGeneratedFromunknownToown addresswatch-onlylabelCreditmatures in %n more blockmatures in %n more blocksnot acceptedDebitTotal debitTotal creditTransaction feeNet amountMessageCommentTransaction IDTransaction total sizeOutput indexMerchantGenerated 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.Debug informationTransactionInputsAmounttruefalseTransactionDescDialogThis pane shows a detailed description of the transactionDetails for %1TransactionTableModelDateTypeLabelOpen for %n more blockOpen for %n more blocksOpen until %1OfflineUnconfirmedAbandonedConfirming (%1 of %2 recommended confirmations)Confirmed (%1 confirmations)ConflictedImmature (%1 confirmations, will be available after %2)This block was not received by any other nodes and will probably not be accepted!Generated but not acceptedReceived withReceived fromSent toPayment to yourselfMinedwatch-only(n/a)(no label)Transaction status. Hover over this field to show number of confirmations.Date and time that the transaction was received.Type of transaction.Whether or not a watch-only address is involved in this transaction.User-defined intent/purpose of the transaction.Amount removed from or added to balance.TransactionViewAllTodayThis weekThis monthLast monthThis yearRange...Received withSent toTo yourselfMinedOtherEnter address, transaction id or label to search.Min amountAbandon transactionIncrease transaction feeCopy addressCopy labelCopy amountCopy transaction IDCopy raw transactionCopy full transaction detailsEdit labelShow transaction detailsExport Transaction HistoryComma separated file (*.csv)ConfirmedWatch-onlyDateTypeLabelAddressIDExporting FailedThere was an error trying to save the transaction history to %1.Exporting SuccessfulThe transaction history was successfully saved to %1.Range:toUnitDisplayStatusBarControlUnit to show amounts in. Click to select another unit.WalletFrameNo wallet has been loaded.WalletModelSend CoinsFee bump errorIncreasing transaction fee failed.Do you want to increase the fee?Current fee:Increase:New fee:Confirm fee bumpCan't sign transaction.Could not commit transaction.WalletView&ExportExport the data in the current tab to a fileBackup WalletWallet Data (*.dat)Backup FailedThere was an error trying to save the wallet data to %1.Backup SuccessfulThe wallet data was successfully saved to %1.bitcoin-coreOptions:Specify data directoryConnect to a node to retrieve peer addresses, and disconnectSpecify your own public addressAccept command line and JSON-RPC commandsDistributed under the MIT software license, see the accompanying file %s or %s.If <category> is not supplied or if <category> = 1, output all debugging information.Prune configured below the minimum of %d MiB. Please use a higher number.Prune: last wallet synchronisation goes beyond pruned data. You need to -reindex (download the whole blockchain again in case of pruned node)Rescans are not possible in pruned mode. You will need to use -reindex which will download the whole blockchain again.Error: A fatal internal error occurred, see debug.log for detailsFee (in %s/kB) to add to transactions you send (default: %s)Pruning blockstore...Run in the background as a daemon and accept commandsUnable to start HTTP server. See debug log for details.Bitcoin CoreThe %s developersA fee rate (in %s/kB) that will be used when fee estimation has insufficient data (default: %s)Accept relayed transactions received from whitelisted peers even when not relaying transactions (default: %d)Add a node to connect to and attempt to keep the connection open (see the `addnode` RPC command help for more info).Bind to given address and always listen on it. Use [host]:port notation for IPv6Cannot obtain a lock on data directory %s. %s is probably already running.Cannot provide specific connections and have addrman find outgoing connections at the same.Connect only to the specified node(s); -connect=0 disables automatic connections (the rules for this peer are the same as for -addnode).Delete all wallet transactions and only recover those parts of the blockchain through -rescan on startupError reading %s! All keys read correctly, but transaction data or address book entries might be missing or incorrect.Exclude debugging information for a category. Can be used in conjunction with -debug=1 to output debug logs for all categories except one or more specified categories.Execute command when a wallet transaction changes (%s in cmd is replaced by TxID)Extra transactions to keep in memory for compact block reconstructions (default: %u).If this block is in the chain assume that it and its ancestors are valid and potentially skip their script verification (0 to verify all, default: %s, testnet: %s).Maximum allowed median peer time offset adjustment. Local perspective of time may be influenced by peers forward or backward by this amount. (default: %u seconds)Maximum total fees (in %s) to use in a single wallet transaction or raw transaction; setting this too low may abort large transactions (default: %s)Please check that your computer's date and time are correct! If your clock is wrong, %s will not work properly.Please contribute if you find %s useful. Visit %s for further information about the software.Query for peer addresses via DNS lookup, if low on addresses (default: 1 unless -connect used).Reduce storage requirements by enabling pruning (deleting) of old blocks. This allows the pruneblockchain RPC to be called to delete specific blocks and enables automatic pruning of old blocks if a target size in MiB is provided. This mode is incompatible with -txindex and -rescan. Warning: Reverting this setting requires re-downloading the entire blockchain. (default: 0 = disable pruning blocks, 1 = allow manual pruning via RPC, >%u = automatically prune block files to stay under the specified target size in MiB)Set lowest fee rate (in %s/kB) for transactions to be included in block creation (default: %s).Set the number of script verification threads (%u to %d, 0 = auto, <0 = leave that many cores free, default: %d)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 correctThis is a pre-release test build - use at your own risk - do not use for mining or merchant applicationsThis is the transaction fee you may discard if change is smaller than dust at this level.Unable to replay blocks. You will need to rebuild the database using -reindex-chainstate.Unable to rewind the database to a pre-fork state. You will need to re-download the blockchainUse UPnP to map the listening port (default: 1 when listening and no -proxy)Username and hashed password for JSON-RPC connections. The field <userpw> comes in the format: <USERNAME>:<SALT>$<HASH>. A canonical python script is included in share/rpcuser. The client then connects normally using the rpcuser=<USERNAME>/rpcpassword=<PASSWORD> pair of arguments. This option can be specified multiple times.Wallet will not create transactions that violate mempool chain limits (default: %u).Warning: The network does not appear to fully agree! Some miners appear to be experiencing issues.Warning: We do not appear to fully agree with our peers! You may need to upgrade, or other nodes may need to upgrade.Whether to save the mempool on shutdown and load on restart (default: %u).%d of last 100 blocks have unexpected version.%s corrupt, salvage failed-maxmempool must be at least %d MB<category> can be:Accept connections from outside (default: 1 if no -proxy or -connect)Append comment to the user agent stringAttempt to recover private keys from a corrupt wallet on startupBlock creation options:Cannot resolve -%s address: '%s'Chain selection options:Change index out of rangeConnection options:Copyright (C) %i-%iCorrupted block database detectedDebugging/Testing options:Do not load the wallet and disable wallet RPC callsDo you want to rebuild the block database now?Enable publish hash block in <address>Enable publish hash transaction in <address>Enable publish raw block in <address>Enable publish raw transaction in <address>Enable transaction replacement in the memory pool (default: %u)Error creating %s: You can't create non-HD wallets with this version.Error initialising block databaseError initialising wallet database environment %s!Error loading %sError loading %s: Wallet corruptedError loading %s: Wallet requires newer version of %sError loading block databaseError opening block databaseError: Disk space is low!Failed to listen on any port. Use -listen=0 if you want this.Failed to rescan the wallet during initialisation.Importing...Incorrect or no genesis block found. Wrong datadir for network?Initialisation sanity check failed. %s is shutting down.Invalid amount for -%s=<amount>: '%s'Invalid amount for -discardfee=<amount>: '%s'Invalid amount for -fallbackfee=<amount>: '%s'Keep the transaction memory pool below <n> megabytes (default: %u)Loading P2P addresses...Loading banlist...Location of the auth cookie (default: data dir)Not enough file descriptors available.Only connect to nodes in network <net> (ipv4, ipv6 or onion)Print this help message and exitPrint version and exitPrune cannot be configured with a negative value.Prune mode is incompatible with -txindex.Rebuild chain state and block index from the blk*.dat files on diskRebuild chain state from the currently indexed blocksReplaying blocks...Rewinding blocks...Send transactions with full-RBF opt-in enabled (RPC only, default: %u).Set database cache size in megabytes (%d to %d, default: %d)Specify wallet file (within data directory)The source code is available from %s.Transaction fee and change calculation failed.Unable to bind to %s on this computer. %s is probably already running.Unsupported argument -benchmark ignored, use -debug=bench.Unsupported argument -debugnet ignored, use -debug=net.Unsupported argument -tor found, use -onion.Unsupported logging category %s=%s.Upgrading UTXO databaseUse UPnP to map the listening port (default: %u)Use the test chainUser Agent comment (%s) contains unsafe characters.Verifying blocks...Wallet debugging/testing options:Wallet needed to be rewritten: restart %s to completeWallet options:Allow JSON-RPC connections from specified source. Valid for <ip> are a single IP (e.g. 1.2.3.4), a network/netmask (e.g. 1.2.3.4/255.255.255.0) or a network/CIDR (e.g. 1.2.3.4/24). This option can be specified multiple timesBind to given address and whitelist peers connecting to it. Use [host]:port notation for IPv6Create new files with system default permissions, instead of umask 077 (only effective with disabled wallet functionality)Discover own IP addresses (default: 1 when listening and no -externalip or -proxy)Error: Listening for incoming connections failed (listen returned error %s)Execute command when a relevant alert is received or we see a really long fork (%s in cmd is replaced by message)Fees (in %s/kB) smaller than this are considered zero fee for relaying, mining and transaction creation (default: %s)If paytxfee is not set, include enough fee so transactions begin confirmation on average within n blocks (default: %u)Invalid amount for -maxtxfee=<amount>: '%s' (must be at least the minrelay fee of %s to prevent stuck transactions)Maximum size of data in data carrier transactions we relay and mine (default: %u)Randomise credentials for every proxy connection. This enables Tor stream isolation (default: %u)The transaction amount is too small to send after the fee has been deductedWhitelisted peers cannot be DoS banned and their transactions are always relayed, even if they are already in the mempool, useful e.g. for a gatewayYou need to rebuild the database using -reindex to go back to unpruned mode. This will redownload the entire blockchain(default: %u)Accept public REST requests (default: %u)Automatically create Tor hidden service (default: %d)Connect through SOCKS5 proxyError loading %s: you can't disable HD on an already existing HD wallet.Error reading from database, shutting down.Error upgrading chainstate database.Imports blocks from external blk000??.dat file on startupInformationInvalid -onion address or hostname: '%s'Invalid -proxy address or hostname: '%s'Invalid amount for -paytxfee=<amount>: '%s' (must be at least %s)Invalid netmask specified in -whitelist: '%s'Keep at most <n> unconnectable transactions in memory (default: %u)Need to specify a port with -whitebind: '%s'Node relay options:RPC server options:Reducing -maxconnections from %d to %d, because of system limitations.Rescan the block chain for missing wallet transactions on startupSend trace/debug info to console instead of debug.log fileShow all debugging options (usage: --help -help-debug)Shrink debug.log file on client startup (default: 1 when no -debug)Signing transaction failedSpecified -walletdir "%s" does not exist.Specified -walletdir "%s" is a relative path.Specified -walletdir "%s" is not a directory.The transaction amount is too small to pay the feeThis is experimental software.Tor control port password (default: empty)Tor control port to use if onion listening enabled (default: %s)Transaction amount too smallTransaction too large for fee policyTransaction too largeUnable to bind to %s on this computer (bind returned error %s)Unable to generate initial keys.Upgrade wallet to latest format on startupUsername for JSON-RPC connectionsVerifying wallet(s)...Wallet %s resides outside wallet directory %sWarningWarning: unknown new rules activated (versionbit %i)Whether to operate in a blocks only mode (default: %u)You need to rebuild the database using -reindex to change -txindexZapping all transactions from wallet...ZeroMQ notification options:Password for JSON-RPC connectionsExecute command when the best block changes (%s in cmd is replaced by block hash)Allow DNS lookups for -addnode, -seednode and -connect(1 = keep tx meta data e.g. account owner and payment request information, 2 = drop tx meta data)-maxtxfee is set very high! Fees this large could be paid on a single transaction.Bind to given address to listen for JSON-RPC connections. This option is ignored unless -rpcallowip is also passed. Port is optional and overrides -rpcport. Use [host]:port notation for IPv6. This option can be specified multiple times (default: 127.0.0.1 and ::1 i.e., localhost, or if -rpcallowip has been specified, 0.0.0.0 and :: i.e., all addresses).Do not keep transactions in the mempool longer than <n> hours (default: %u)Equivalent bytes per sigop in transactions for relay and mining (default: %u)Error loading %s: you can't enable HD on an already existing non-HD wallet.Error loading wallet %s. The -wallet parameter must only specify a filename (not a path).Fees (in %s/kB) smaller than this are considered zero fee for transaction creation (default: %s)Force relay of transactions from whitelisted peers, even if they violate local relay policy (default: %d).How thorough the block verification of -checkblocks is (0-4, default: %u)Maintain a full transaction index, used by the getrawtransaction rpc call (default: %u)Number of seconds to keep misbehaving peers from reconnecting (default: %u)Output debugging information (default: %u, supplying <category> is optional)Set maximum BIP141 block weight to this * 4. Deprecated, use blockmaxweight.Sets the serialisation of raw transaction or block hex returned in non-verbose mode, non-segwit(0) or segwit(1) (default: %d).Specify directory to hold wallets (default: <datadir>/wallets if it exists, otherwise <datadir>).Specify location of debug log file: this can be an absolute path or a path relative to the data directory (default: %s).Support filtering of blocks and transaction with bloom filters (default: %u)The fee rate (in %s/kB) that indicates your tolerance for discarding change by adding it to the fee (default: %s). Note: An output is discarded if it is dust at this rate, but we will always discard up to the dust relay fee and a discard fee above that is limited by the fee estimate for the longest target.This is the transaction fee you may pay when fee estimates are not available.This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit %s and cryptographic software written by Eric Young and UPnP software written by Thomas Bernard.Total length of network version string (%i) exceeds maximum length (%i). Reduce the number or size of uacomments.Tries to keep outbound traffic under the given target (in MiB per 24h), 0 = no limit (default: %d)Unsupported argument -socks found. Setting SOCKS version isn't possible anymore, only SOCKS5 proxies are supported.Unsupported argument -whitelistalwaysrelay ignored, use -whitelistrelay and/or -whitelistforcerelay.Use separate SOCKS5 proxy to reach peers via Tor hidden services (default: %s)Warning: Unknown block versions being mined! It's possible unknown rules are in effectWarning: Wallet file corrupt, data salvaged! Original %s saved as %s in %s; if your balance or transactions are incorrect you should restore from a backup.Whitelist peers connecting from the given IP address (e.g. 1.2.3.4) or CIDR notated network (e.g. 1.2.3.0/24). Can be specified multiple times.%s is set very high!(default: %s)Always query for peer addresses via DNS lookup (default: %u)Error loading wallet %s. The -wallet filename must be a regular file.Error loading wallet %s. Duplicate -wallet filename specified.Error loading wallet %s. Invalid characters in -wallet filename.How many blocks to check at startup (default: %u, 0 = all)Include IP addresses in debug output (default: %u)Keypool ran out, please call keypoolrefill first.Listen for JSON-RPC connections on <port> (default: %u or testnet: %u)Listen for connections on <port> (default: %u or testnet: %u)Maintain at most <n> connections to peers (default: %u)Make the wallet broadcast transactionsMaximum per-connection receive buffer, <n>*1000 bytes (default: %u)Maximum per-connection send buffer, <n>*1000 bytes (default: %u)Prepend debug output with timestamp (default: %u)Relay and mine data carrier transactions (default: %u)Relay non-P2SH multisig (default: %u)Set key pool size to <n> (default: %u)Set maximum BIP141 block weight (default: %d)Set the number of threads to service RPC calls (default: %d)Specify configuration file (default: %s)Specify connection timeout in milliseconds (minimum: 1, default: %d)Specify pid file (default: %s)Spend unconfirmed change when sending transactions (default: %u)Starting network threads...The wallet will avoid paying less than the minimum relay fee.This is the minimum transaction fee you pay on every transaction.This is the transaction fee you will pay if you send a transaction.Threshold for disconnecting misbehaving peers (default: %u)Transaction amounts must not be negative.Transaction has too long of a mempool chain.Transaction must have at least one recipient.Unknown network specified in -onlynet: '%s'Insufficient fundsLoading block index...Loading wallet...Cannot downgrade walletRescanning...Done loadingError