AddressBookPageRight-click to edit address or labelCreate a new address&NewCopy the currently selected address to the system clipboard&CopyC&lose&Copy AddressDelete 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 &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 passphraseEncrypt walletThis operation needs your wallet passphrase to unlock the wallet.Unlock walletThis operation needs your wallet passphrase to decrypt the wallet.Decrypt walletChange passphraseConfirm 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?Bitcoin Core 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.Warning: The Caps Lock key is on!Wallet encryptedEnter 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>.Enter the old passphrase and new passphrase to the 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.BanTableModelIP/NetmaskBanned UntilBitcoinGUISign &message...Synchronising with network...&OverviewNodeShow general overview of wallet&TransactionsBrowse transaction historyE&xitQuit applicationAbout &QtShow information about Qt&Options...&Encrypt Wallet...&Backup Wallet...&Change Passphrase...&Sending addresses...&Receiving addresses...Open &URI...Bitcoin Core clientImporting blocks from disk...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&ReceiveShow information about Bitcoin Core&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 toolbarBitcoin CoreRequest payments (generates QR codes and bitcoin: URIs)&About Bitcoin CoreModify configuration options for Bitcoin CoreShow the list of used sending addresses and labelsShow the list of used receiving addresses and labelsOpen a bitcoin: URI or payment request&Command-line optionsShow the Bitcoin Core help message to get a list with possible Bitcoin command-line options%n active connection to Bitcoin network%n active connections to Bitcoin networkNo block source available...Processed %n block of transaction history.Processed %n blocks of transaction history.%n hour%n hours%n day%n days%n week%n weeks%1 and %2%n year%n years%1 behindLast received block was generated %1 ago.Transactions after this will not yet be visible.ErrorWarningInformationUp to dateCatching up...Date: %1
Amount: %1
Type: %1
Label: %1
Address: %1
Sent transactionIncoming transactionWallet is <b>encrypted</b> and currently <b>unlocked</b>Wallet is <b>encrypted</b> and currently <b>locked</b>ClientModelNetwork AlertCoinControlDialogCoin SelectionQuantity:Bytes:Amount:Priority:Fee:Dust:After Fee:Change:(un)select allTree modeList modeAmountReceived with labelReceived with addressDateConfirmationsConfirmedPriorityCopy addressCopy labelCopy amountCopy transaction IDLock unspentUnlock unspentCopy quantityCopy feeCopy after feeCopy bytesCopy priorityCopy dustCopy changehighesthigherhighmedium-highmediumlow-mediumlowlowerlowest(%1 locked)noneThis label turns red if the transaction size is greater than 1000 bytes.This label turns red if the priority is smaller than "medium".This label turns red if any recipient receives an amount smaller than %1.Can vary +/- %1 satoshi(s) per input.yesnoThis means a fee of at least %1 per kB is required.Can vary +/- 1 byte per input.Transactions with higher priority are more likely to get included into a block.(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 already in the address book.The entered address "%1" is not a valid Bitcoin address.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.HelpMessageDialogBitcoin Coreversion(%1-bit)About Bitcoin CoreCommand-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 setting changes made via the GUIIntroWelcomeWelcome to Bitcoin Core.As this is the first time the program is launched, you can choose where Bitcoin Core will store its data.Bitcoin Core will download and store a copy of the Bitcoin block chain. At least %1GB of data will be stored in this directory, and it will grow over time. The wallet will also be stored in this directory.Use the default data directoryUse a custom data directory:Bitcoin CoreError: 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)OpenURIDialogOpen URIOpen payment request from URI or fileURI:Select payment request fileSelect payment request file to openOptionsDialogOptions&MainSize of &database cacheMBNumber of script &verification threadsAccept connections from outsideAllow incoming connectionsIP address of the proxy (e.g. IPv4: 127.0.0.1 / IPv6: ::1)Minimise 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.The user interface language can be set here. This setting will take effect after restarting Bitcoin Core.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 |.Third party transaction URLsActive command-line options that override above options:Reset all client options to default.&Reset Options&NetworkAutomatically start Bitcoin Core after logging in to the system.&Start Bitcoin Core on system login(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 &UPnPConnect 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:Shows, if the supplied default SOCKS5 proxy is used to reach peers via this network type.IPv4IPv6TorConnect to the Bitcoin network through a separate SOCKS5 proxy for Tor hidden services.Use separate SOCKS5 proxy to reach peers via 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:&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.&OK&CanceldefaultnoneConfirm options resetClient restart required to activate changes.Client will be shut down. Do you want to proceed?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 addressesPaymentServerURI handlingInvalid payment address %1Payment request rejectedPayment request network doesn't match client network.Payment request is not initialised.Requested payment amount of %1 is too small (considered dust).Payment request errorCannot start bitcoin: click-to-pay handlerPayment request fetch URL is invalid: %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 expired.Unverified payment requests to custom payment scripts are unsupported.Invalid payment request.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 %1Payment acknowledgedNetwork request errorPeerTableModelUser AgentNode/ServicePing TimeQObjectAmountEnter a Bitcoin address (e.g. %1)%1 d%1 h%1 m%1 sNoneN/A%1 msQRImageWidget&Save Image...&Copy ImageSave QR CodePNG Image (*.png)RPCConsoleClient nameN/AClient version&InformationDebug windowGeneralUsing BerkeleyDB versionStartup timeNetworkNameNumber of connectionsBlock chainCurrent number of blocksMemory PoolCurrent number of transactionsMemory usageOpen the Bitcoin Core debug log file from the current data directory. This can take a few seconds for large log files.ReceivedSent&PeersBanned peersSelect a peer to view detailed information.WhitelistedDirectionVersionStarting BlockSynced HeadersSynced BlocksUser AgentServicesBan ScoreConnection TimeLast SendLast ReceivePing TimeThe duration of a currently outstanding ping.Ping WaitTime OffsetLast block time&Open&Console&Network Traffic&ClearTotalsIn:Out:Build dateDebug log fileClear console&Disconnect NodeBan Node for1 &hour1 &day1 &week1 &year&Unban NodeWelcome to the Bitcoin Core RPC console.Use up and down arrows to navigate history, and <b>Ctrl-L</b> to clear screen.Type <b>help</b> for an overview of available commands.%1 B%1 KB%1 MB%1 GB(node id: %1)via %1neverInboundOutboundYesNoUnknownReceiveCoinsDialog&Amount:&Label:&Message:Reuse one of the previously used receiving addresses. Reusing addresses has security and privacy issues. Do not use this unless re-generating a payment request made before.R&euse an existing receiving address (not recommended)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 paymentShow the selected request (does the same as double clicking an entry)ShowRemove the selected entries from the listRemoveCopy 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.RecentRequestsTableModelDateLabelMessageAmount(no label)(no message)(no amount)SendCoinsDialogSend CoinsCoin Control FeaturesInputs...automatically selectedInsufficient funds!Quantity:Bytes:Amount:Priority: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...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.Hidetotal at leastPaying 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...)Confirmation time:normalfastSend as zero-fee transaction if possible(confirmation may take longer)Send to multiple recipients at onceAdd &RecipientClear all fields of the form.Dust:Clear &AllBalance:Confirm the send actionS&endConfirm send coins%1 to %2Copy quantityCopy amountCopy feeCopy after feeCopy bytesCopy priorityCopy changeTotal Amount %1orThe 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.Transaction creation failed!The transaction was rejected! This might happen if some of the coins in your wallet were already spent, such as if you used a copy of wallet.dat and coins were spent in the copy but not marked as spent here.A 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.The recipient address is not valid. Please recheck.Duplicate address found: addresses should only be used once each.Warning: Invalid Bitcoin address(no label)Warning: Unknown change addressCopy dustAre you sure you want to send?added as transaction feeSendCoinsEntryA&mount:Pay &To:Enter a label for this address to add it to your address book&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 amountMessage: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:ShutdownWindowBitcoin Core 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.SplashScreenBitcoin CoreThe Bitcoin Core developers[testnet]TrafficGraphWidgetKB/sTransactionDescOpen until %1conflicted%1/offline%1/unconfirmed%1 confirmationsStatus, broadcast through %n node, broadcast through %n nodesDateSourceGeneratedFromToown addresswatch-onlylabelCreditmatures in %n more blockmatures in %n more blocksnot acceptedDebitTotal debitTotal creditTransaction feeNet amountMessageCommentTransaction IDMerchantGenerated 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 informationTransactionInputsAmounttruefalse, has not been successfully broadcast yetOpen for %n more blockOpen for %n more blocksunknownTransactionDescDialogTransaction detailsThis pane shows a detailed description of the transactionTransactionTableModelDateTypeImmature (%1 confirmations, will be available after %2)Open for %n more blockOpen for %n more blocksOpen until %1Confirmed (%1 confirmations)This block was not received by any other nodes and will probably not be accepted!Generated but not acceptedOfflineLabelUnconfirmedConfirming (%1 of %2 recommended confirmations)ConflictedReceived withReceived fromSent toPayment to yourselfMinedwatch-only(n/a)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 or label to searchMin amountCopy addressCopy labelCopy amountCopy transaction IDCopy raw transactionEdit labelShow transaction detailsExport Transaction HistoryWatch-onlyExporting FailedThere was an error trying to save the transaction history to %1.Exporting SuccessfulThe transaction history was successfully saved to %1.Comma separated file (*.csv)ConfirmedDateTypeLabelAddressIDRange:toUnitDisplayStatusBarControlUnit to show amounts in. Click to select another unit.WalletFrameNo wallet has been loaded.WalletModelSend CoinsWalletView&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.The wallet data was successfully saved to %1.Backup Successfulbitcoin-coreOptions:Specify data directoryConnect to a node to retrieve peer addresses, and disconnectSpecify your own public addressAccept command line and JSON-RPC commandsIf <category> is not supplied or if <category> = 1, output all debugging information.Maximum total fees (in %s) to use in a single wallet 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 Bitcoin Core will not work properly.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)Reduce storage requirements by pruning (deleting) old blocks. This mode is incompatible with -txindex and -rescan. Warning: Reverting this setting requires re-downloading the entire blockchain. (default: 0 = disable pruning blocks, >%u = target size in MiB to use for block files)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.Accept connections from outside (default: 1 if no -proxy or -connect)-fallbackfee is set very high! This is the transaction fee you may pay when fee estimates are not available.A 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)Bind to given address and always listen on it. Use [host]:port notation for IPv6Delete all wallet transactions and only recover those parts of the blockchain through -rescan on startupDistributed under the MIT software license, see the accompanying file COPYING or <http://www.opensource.org/licenses/mit-license.php>.Execute command when a wallet transaction changes (%s in cmd is replaced by TxID)Force relay of transactions from whitelisted peers even they violate local relay policy (default: %d)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 applicationsUnable to bind to %s on this computer. Bitcoin Core is probably already running.Unsupported argument -whitelistalwaysrelay ignored, use -whitelistrelay and/or -whitelistforcerelay.Use UPnP to map the listening port (default: 1 when listening and no -proxy)WARNING: abnormally high number of blocks generated, %d blocks received in the last %d hours (%d expected)WARNING: check your network connection, %d blocks received in the last %d hours (%d expected)Warning: The network does not appear to fully agree! Some miners appear to be experiencing issues.Warning: Unknown block versions being mined! It's possible unknown rules are in effectWarning: We do not appear to fully agree with our peers! You may need to upgrade, or other nodes may need to upgrade.Warning: wallet.dat corrupt, data salvaged! Original wallet.dat saved as wallet.{timestamp}.bak in %s; if your balance or transactions are incorrect you should restore from a backup.Whitelist peers connecting from the given netmask or IP address. Can be specified multiple times.-maxmempool must be at least %d MB<category> can be:Append comment to the user agent stringBlock creation options:Connect only to the specified node(s)Connection options:Corrupted 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 initialising block databaseError initialising wallet database environment %s!Error loading block databaseError opening block databaseError: Disk space is low!Failed to listen on any port. Use -listen=0 if you want this.Importing...Incorrect or no genesis block found. Wrong datadir for network?Invalid -onion address: '%s'Invalid amount for -fallbackfee=<amount>: '%s'Keep the transaction memory pool below <n> megabytes (default: %u)Location of the auth cookie (default: data dir)Minimum bytes per sigop in transactions we relay and mine (default: %u)Not enough file descriptors available.Only connect to nodes in network <net> (ipv4, ipv6 or onion)Print version and exitPrune cannot be configured with a negative value.Prune mode is incompatible with -txindex.Set database cache size in megabytes (%d to %d, default: %d)Set maximum block size in bytes (default: %d)Specify wallet file (within data directory)Unsupported argument -benchmark ignored, use -debug=bench.Unsupported argument -debugnet ignored, use -debug=net.Unsupported argument -tor found, use -onion.Use UPnP to map the listening port (default: %u)User Agent comment (%s) contains unsafe characters.Verifying blocks...Verifying wallet...Wallet %s resides outside data directory %sWallet options:You need to rebuild the database using -reindex to change -txindexAllow 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 IPv6Bind to given address to listen for JSON-RPC connections. Use [host]:port notation for IPv6. This option can be specified multiple times (default: bind to all interfaces)Cannot obtain a lock on data directory %s. Bitcoin Core is probably already running.Create 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)Query for peer addresses via DNS lookup, if low on addresses (default: 1 unless -connect)Randomise credentials for every proxy connection. This enables Tor stream isolation (default: %u)Set maximum size of high-priority/low-fee transactions in bytes (default: %d)Set the number of threads for coin generation if enabled (-1 = all cores, default: %d)The transaction amount is too small to send after the fee has been deductedThis product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit <https://www.openssl.org/> and cryptographic software written by Eric Young and UPnP software written by Thomas Bernard.Whitelisted 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)Activating best chain...Attempt to recover private keys from a corrupt wallet.dat on startupAutomatically create Tor hidden service (default: %d)Cannot resolve -whitebind address: '%s'Connect through SOCKS5 proxyCopyright (C) 2009-%i The Bitcoin Core DevelopersError loading wallet.dat: Wallet requires newer version of Bitcoin CoreError reading from database, shutting down.Imports blocks from external blk000??.dat file on startupInformationInitialisation sanity check failed. Bitcoin Core is shutting down.Invalid amount for -maxtxfee=<amount>: '%s'Invalid amount for -minrelaytxfee=<amount>: '%s'Invalid amount for -mintxfee=<amount>: '%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:Rebuild block chain index from current blk000??.dat files on startupReceive and display P2P network alerts (default: %u)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 fileSend transactions as zero-fee transactions if possible (default: %u)Show all debugging options (usage: --help -help-debug)Shrink debug.log file on client startup (default: 1 when no -debug)Signing transaction failedThe 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 amounts must be positiveTransaction too large for fee policyTransaction too largeUnable to bind to %s on this computer (bind returned error %s)Upgrade wallet to latest format on startupUsername for JSON-RPC connectionsWallet needed to be rewritten: restart Bitcoin Core to completeWarningWarning: unknown new rules activated (versionbit %i)Whether to operate in a blocks only mode (default: %u)Zapping all transactions from wallet...ZeroMQ notification options:wallet.dat corrupt, salvage failedPassword for JSON-RPC connectionsExecute command when the best block changes (%s in cmd is replaced by block hash)This help messageAllow DNS lookups for -addnode, -seednode and -connectLoading addresses...Error loading wallet.dat: Wallet corrupted(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.-paytxfee is set very high! This is the transaction fee you will pay if you send a transaction.Do not keep transactions in the mempool longer than <n> hours (default: %u)Error reading wallet.dat! All keys read correctly, but transaction data or address book entries might be missing or incorrect.Fees (in %s/kB) smaller than this are considered zero fee for transaction creation (default: %s)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)Support filtering of blocks and transaction with bloom filters (default: %u)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.Use separate SOCKS5 proxy to reach peers via Tor hidden services (default: %s)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. This option can be specified multiple times(default: %s)Always query for peer addresses via DNS lookup (default: %u)Error loading wallet.datGenerate coins (default: %u)How many blocks to check at startup (default: %u, 0 = all)Include IP addresses in debug output (default: %u)Invalid -proxy address: '%s'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 minimum block size in bytes (default: %u)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)Threshold for disconnecting misbehaving peers (default: %u)Unknown network specified in -onlynet: '%s'Cannot resolve -bind address: '%s'Cannot resolve -externalip address: '%s'Invalid amount for -paytxfee=<amount>: '%s'Insufficient fundsLoading block index...Add a node to connect to and attempt to keep the connection openLoading wallet...Cannot downgrade walletCannot write default addressRescanning...Done loadingError