AddressBookPage Right-click to edit address or label Create a new address Create a new address &New Copy the currently selected address to the system clipboard Copy the currently selected address to the system clipboard &Copy C&lose &Copy Address &Copy Address Delete the currently selected address from the list Delete the currently selected address from the list Export the data in the current tab to a file Export the data in the current tab to a file &Export &Export &Delete &Delete Choose the address to send coins to Choose the address to receive coins with C&hoose Sending addresses Receiving addresses These are your Bitcoin addresses for sending payments. Always check the amount and the receiving address before sending coins. These 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 Copy &Label &Edit &Edit Export Address List Comma separated file (*.csv) Comma separated file (*.csv) Exporting Failed There was an error trying to save the address list to %1. Please try again. AddressTableModel Label Label Address Address (no label) (no label) AskPassphraseDialog Passphrase Dialog Passphrase Dialog Enter passphrase Enter passphrase New passphrase New passphrase Repeat new passphrase Repeat new passphrase Encrypt wallet Encrypt wallet This operation needs your wallet passphrase to unlock the wallet. This operation needs your wallet passphrase to unlock the wallet. Unlock wallet Unlock wallet This operation needs your wallet passphrase to decrypt the wallet. This operation needs your wallet passphrase to decrypt the wallet. Decrypt wallet Decrypt wallet Change passphrase Change passphrase Confirm wallet encryption Confirm wallet encryption Warning: If you encrypt your wallet and lose your passphrase, you will LOSE ALL OF YOUR BITCOINS! Warning: If you encrypt your wallet and lose your passphrase, you will LOSE ALL OF YOUR BITCOINS! Are you sure you wish to encrypt your wallet? 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. 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! Warning: The Caps Lock key is on! Wallet encrypted Wallet encrypted Enter the new passphrase to the wallet. Please use a passphrase of ten or more random characters, or eight or more words. Enter the old passphrase and new passphrase to the wallet. Wallet encryption failed Wallet encryption failed Wallet encryption failed due to an internal error. Your wallet was not encrypted. Wallet encryption failed due to an internal error. Your wallet was not encrypted. The supplied passphrases do not match. The supplied passphrases do not match. Wallet unlock failed Wallet unlock failed The passphrase entered for the wallet decryption was incorrect. The passphrase entered for the wallet decryption was incorrect. Wallet decryption failed Wallet decryption failed Wallet passphrase was successfully changed. Wallet passphrase was successfully changed. BitcoinGUI Sign &message... Sign &message... Synchronizing with network... Synchronizing with network... &Overview &Overview Node Show general overview of wallet Show general overview of wallet &Transactions &Transactions Browse transaction history Browse transaction history E&xit E&xit Quit application Quit application About &Qt About &Qt Show information about Qt Show information about Qt &Options... &Options... &Encrypt Wallet... &Encrypt Wallet... &Backup Wallet... &Backup Wallet... &Change Passphrase... &Change Passphrase... &Sending addresses... &Receiving addresses... Open &URI... Bitcoin Core client Importing blocks from disk... Importing blocks from disk... Reindexing blocks on disk... Reindexing blocks on disk... Send coins to a Bitcoin address Send coins to a Bitcoin address Backup wallet to another location Backup wallet to another location Change the passphrase used for wallet encryption Change the passphrase used for wallet encryption &Debug window &Debug window Open debugging and diagnostic console Open debugging and diagnostic console &Verify message... &Verify message... Bitcoin Bitcoin Wallet Wallet &Send &Send &Receive &Receive Show information about Bitcoin Core &Show / Hide &Show / Hide Show or hide the main Window Show or hide the main Window Encrypt the private keys that belong to your wallet Encrypt the private keys that belong to your wallet Sign messages with your Bitcoin addresses to prove you own them Sign messages with your Bitcoin addresses to prove you own them Verify messages to ensure they were signed with specified Bitcoin addresses Verify messages to ensure they were signed with specified Bitcoin addresses &File &File &Settings &Settings &Help &Help Tabs toolbar Tabs toolbar Bitcoin Core Bitcoin Core Request payments (generates QR codes and bitcoin: URIs) &About Bitcoin Core Modify configuration options for Bitcoin Core Show the list of used sending addresses and labels Show the list of used receiving addresses and labels Open a bitcoin: URI or payment request &Command-line options Show the Bitcoin Core help message to get a list with possible Bitcoin command-line options %n active connection(s) to Bitcoin network %n active connection to Bitcoin network %n active connections to Bitcoin network No block source available... No block source available... Processed %n block(s) of transaction history. Processed %n block of transaction history. Processed %n blocks of transaction history. %n hour(s) %n hour %n hours %n day(s) %n day %n days %n week(s) %n week %n weeks %1 and %2 %n year(s) %n year %n years %1 behind %1 behind Last received block was generated %1 ago. Last received block was generated %1 ago. Transactions after this will not yet be visible. Transactions after this will not yet be visible. Error Error Warning Warning Information Information Up to date Up to date Catching up... Catching up... Date: %1 Amount: %1 Type: %1 Label: %1 Address: %1 Sent transaction Sent transaction Incoming transaction Incoming transaction Wallet is encrypted and currently unlocked Wallet is encrypted and currently unlocked Wallet is encrypted and currently locked Wallet is encrypted and currently locked ClientModel Network Alert Network Alert CoinControlDialog Coin Selection Quantity: Bytes: Amount: Priority: Fee: Dust: After Fee: Change: (un)select all Tree mode List mode Amount Amount Received with label Received with address Date Date Confirmations Confirmed Confirmed Priority Copy address Copy address Copy label Copy label Copy amount Copy amount Copy transaction ID Copy transaction ID Lock unspent Unlock unspent Copy quantity Copy fee Copy after fee Copy bytes Copy priority Copy dust Copy change highest higher high medium-high medium low-medium low lower lowest (%1 locked) none This 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. yes no This 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) (no label) change from %1 (%2) (change) EditAddressDialog Edit Address Edit Address &Label &Label The label associated with this address list entry The address associated with this address list entry. This can only be modified for sending addresses. &Address &Address New receiving address New receiving address New sending address New sending address Edit receiving address Edit receiving address Edit sending address Edit sending address The entered address "%1" is already in the address book. The entered address "%1" is already in the address book. The entered address "%1" is not a valid Bitcoin address. The entered address "%1" is not a valid Bitcoin address. Could not unlock wallet. Could not unlock wallet. New key generation failed. New key generation failed. FreespaceChecker A new data directory will be created. A new data directory will be created. name name Directory already exists. Add %1 if you intend to create a new directory here. Directory already exists. Add %1 if you intend to create a new directory here. Path already exists, and is not a directory. Path already exists, and is not a directory. Cannot create data directory here. Cannot create data directory here. HelpMessageDialog Bitcoin Core Bitcoin Core version version (%1-bit) About Bitcoin Core Command-line options Usage: Usage: command-line options command-line options Intro Welcome Welcome Welcome 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 directory Use the default data directory Use a custom data directory: Use a custom data directory: Bitcoin Core Bitcoin Core Error: Specified data directory "%1" cannot be created. Error Error %n GB of free space available (of %n GB needed) OpenURIDialog Open URI Open payment request from URI or file URI: Select payment request file Select payment request file to open OptionsDialog Options Options &Main &Main Size of &database cache MB Number of script &verification threads Accept connections from outside Allow incoming connections IP address of the proxy (e.g. IPv4: 127.0.0.1 / IPv6: ::1) 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. 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 URLs Active command-line options that override above options: Reset all client options to default. Reset all client options to default. &Reset Options &Reset Options &Network &Network Automatically start Bitcoin Core after logging in to the system. &Start Bitcoin Core on system login (0 = auto, <0 = leave that many cores free) W&allet Expert Enable coin &control features 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. &Spend unconfirmed change Automatically open the Bitcoin client port on the router. This only works when your router supports UPnP and it is enabled. Automatically open the Bitcoin client port on the router. This only works when your router supports UPnP and it is enabled. Map port using &UPnP Map port using &UPnP Connect to the Bitcoin network through a SOCKS5 proxy. &Connect through SOCKS5 proxy (default proxy): Proxy &IP: Proxy &IP: &Port: &Port: Port of the proxy (e.g. 9050) Port of the proxy (e.g. 9050) &Window &Window Show only a tray icon after minimizing the window. Show only a tray icon after minimizing the window. &Minimize to the tray instead of the taskbar &Minimize to the tray instead of the taskbar M&inimize on close M&inimize on close &Display &Display User Interface &language: User Interface &language: &Unit to show amounts in: &Unit to show amounts in: Choose the default subdivision unit to show in the interface and when sending coins. Choose the default subdivision unit to show in the interface and when sending coins. Whether to show coin control features or not. &OK &OK &Cancel &Cancel default default none Confirm options reset Confirm options reset Client 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. The supplied proxy address is invalid. OverviewPage Form 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 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 out of sync out of sync PaymentServer URI handling URI handling Invalid payment address %1 Payment request rejected Payment request network doesn't match client network. Payment request is not initialized. Requested payment amount of %1 is too small (considered dust). Payment request error Cannot start bitcoin: click-to-pay handler Payment request fetch URL is invalid: %1 URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. Payment request file handling Payment 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 %1 Payment request %1 is too large (%2 bytes, allowed %3 bytes). Payment request DoS protection Error communicating with %1: %2 Payment request cannot be parsed! Bad response from server %1 Payment acknowledged Network request error PeerTableModel User Agent Node/Service Ping Time QObject Amount Amount Enter a Bitcoin address (e.g. %1) %1 d %1 h %1 m %1 s None N/A N/A %1 ms QRImageWidget &Save Image... &Copy Image Save QR Code Save QR Code PNG Image (*.png) RPCConsole Client name Client name N/A N/A Client version Client version &Information &Information Debug window General Using OpenSSL version Using OpenSSL version Using BerkeleyDB version Startup time Startup time Network Network Name Number of connections Number of connections Block chain Block chain Current number of blocks Current number of blocks Open the Bitcoin Core debug log file from the current data directory. This can take a few seconds for large log files. Received Sent &Peers Select a peer to view detailed information. Direction Version User Agent Services Starting Height Sync Height Ban Score Connection Time Last Send Last Receive Bytes Sent Bytes Received Ping Time Time Offset Last block time Last block time &Open &Open &Console &Console &Network Traffic &Clear Totals In: Out: Build date Build date Debug log file Debug log file Clear console Clear console Welcome to the Bitcoin Core RPC console. Use up and down arrows to navigate history, and Ctrl-L to clear screen. Use up and down arrows to navigate history, and Ctrl-L to clear screen. Type help for an overview of available commands. Type help for an overview of available commands. %1 B %1 KB %1 MB %1 GB via %1 never Inbound Outbound Unknown Fetching... ReceiveCoinsDialog &Amount: &Label: &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 optional. An optional amount to request. Leave this empty or zero to not request a specific amount. Clear all fields of the form. Clear Requested payments history &Request payment Show the selected request (does the same as double clicking an entry) Show Remove the selected entries from the list Remove Copy label Copy label Copy message Copy amount Copy amount ReceiveRequestDialog QR Code Copy &URI Copy &Address &Save Image... Request payment to %1 Payment information URI Address Address Amount Amount Label Label Message Message Resulting URI too long, try to reduce the text for label / message. Resulting URI too long, try to reduce the text for label / message. Error encoding URI into QR Code. Error encoding URI into QR Code. RecentRequestsTableModel Date Date Label Label Message Message Amount Amount (no label) (no label) (no message) (no amount) SendCoinsDialog Send Coins Send Coins Coin Control Features Inputs... automatically selected Insufficient 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 address Transaction Fee: Choose... collapse fee-settings per kilobyte If 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. Hide total at least 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 bitcoin transactions than the network can process. (read the tooltip) Recommended: Custom: (Smart fee not initialized yet. This usually takes a few blocks...) Confirmation time: normal fast Send as zero-fee transaction if possible (confirmation may take longer) Send to multiple recipients at once Send to multiple recipients at once Add &Recipient Add &Recipient Clear all fields of the form. Dust: Clear &All Clear &All Balance: Balance: Confirm the send action Confirm the send action S&end S&end Confirm send coins Confirm send coins %1 to %2 Copy quantity Copy amount Copy amount Copy fee Copy after fee Copy bytes Copy priority Copy change Total Amount %1 (= %2) or The amount to pay must be larger than 0. The amount to pay must be larger than 0. The amount exceeds your balance. The amount exceeds your balance. The total exceeds your balance when the %1 transaction fee is included. 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. Estimated to begin confirmation within %n block(s). Estimated to begin confirmation within %n block. Estimated to begin confirmation within %n blocks. Pay only the minimum fee of %1 The recipient address is not valid. Please recheck. Duplicate address found: addresses should only be used once each. Warning: Invalid Bitcoin address (no label) (no label) Warning: Unknown change address Copy dust Are you sure you want to send? added as transaction fee SendCoinsEntry A&mount: A&mount: Pay &To: Pay &To: Enter a label for this address to add it to your address book Enter a label for this address to add it to your address book &Label: &Label: Choose previously used address This is a normal payment. The Bitcoin address to send the payment to Alt+A Alt+A Paste address from clipboard Paste address from clipboard Alt+P Alt+P Remove this entry 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. S&ubtract fee from amount Message: 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 addresses 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. Pay To: Memo: ShutdownWindow Bitcoin Core is shutting down... Do not shut down the computer until this window disappears. SignVerifyMessageDialog Signatures - Sign / Verify a Message Signatures - Sign / Verify a Message &Sign Message &Sign Message You 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 with Choose previously used address Alt+A Alt+A Paste address from clipboard Paste address from clipboard Alt+P Alt+P Enter the message you want to sign here Enter the message you want to sign here Signature Signature Copy the current signature to the system clipboard Copy the current signature to the system clipboard Sign the message to prove you own this Bitcoin address Sign the message to prove you own this Bitcoin address Sign &Message Sign &Message Reset all sign message fields Reset all sign message fields Clear &All Clear &All &Verify Message &Verify Message 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! The Bitcoin address the message was signed with Verify the message to ensure it was signed with the specified Bitcoin address Verify the message to ensure it was signed with the specified Bitcoin address Verify &Message Verify &Message Reset all verify message fields Reset all verify message fields Click "Sign Message" to generate signature Click "Sign Message" to generate signature The entered address is invalid. The entered address is invalid. Please check the address and try again. Please check the address and try again. The entered address does not refer to a key. The entered address does not refer to a key. Wallet unlock was cancelled. Wallet unlock was cancelled. Private key for the entered address is not available. Private key for the entered address is not available. Message signing failed. Message signing failed. Message signed. Message signed. The signature could not be decoded. The signature could not be decoded. Please check the signature and try again. Please check the signature and try again. The signature did not match the message digest. The signature did not match the message digest. Message verification failed. Message verification failed. Message verified. Message verified. SplashScreen Bitcoin Core Bitcoin Core The Bitcoin Core developers [testnet] [testnet] TrafficGraphWidget KB/s TransactionDesc Open until %1 Open until %1 conflicted %1/offline %1/offline %1/unconfirmed %1/unconfirmed %1 confirmations %1 confirmations Status Status , broadcast through %n node(s) , broadcast through %n node , broadcast through %n nodes Date Date Source Source Generated Generated From From To To own address own address watch-only label label Credit Credit matures in %n more block(s) matures in %n more block matures in %n more blocks not accepted not accepted Debit Debit Total debit Total credit Transaction fee Transaction fee Net amount Net amount Message Message Comment Comment Transaction ID Transaction ID Merchant 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. Debug information Debug information Transaction Transaction Inputs Inputs Amount Amount true true false false , has not been successfully broadcast yet , has not been successfully broadcast yet Open for %n more block(s) Open for %n more block Open for %n more blocks unknown unknown TransactionDescDialog Transaction details Transaction details This pane shows a detailed description of the transaction This pane shows a detailed description of the transaction TransactionTableModel Date Date Type Type Immature (%1 confirmations, will be available after %2) Open for %n more block(s) Open for %n more block Open for %n more blocks Open until %1 Open until %1 Confirmed (%1 confirmations) Confirmed (%1 confirmations) This block was not received by any other nodes and will probably not be accepted! This block was not received by any other nodes and will probably not be accepted! Generated but not accepted Generated but not accepted Offline Label Label Unconfirmed Confirming (%1 of %2 recommended confirmations) Conflicted Received with Received with Received from Received from Sent to Sent to Payment to yourself Payment to yourself Mined Mined watch-only (n/a) (n/a) Transaction status. Hover over this field to show number of confirmations. Transaction status. Hover over this field to show number of confirmations. Date and time that the transaction was received. Date and time that the transaction was received. Type of transaction. 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. Amount removed from or added to balance. TransactionView All All Today Today This week This week This month This month Last month Last month This year This year Range... Range... Received with Received with Sent to Sent to To yourself To yourself Mined Mined Other Other Enter address or label to search Enter address or label to search Min amount Min amount Copy address Copy address Copy label Copy label Copy amount Copy amount Copy transaction ID Copy transaction ID Edit label Edit label Show transaction details Show transaction details Export Transaction History Watch-only Exporting Failed There was an error trying to save the transaction history to %1. Exporting Successful The transaction history was successfully saved to %1. Comma separated file (*.csv) Comma separated file (*.csv) Confirmed Confirmed Date Date Type Type Label Label Address Address ID ID Range: Range: to to UnitDisplayStatusBarControl Unit to show amounts in. Click to select another unit. WalletFrame No wallet has been loaded. WalletModel Send Coins Send Coins WalletView &Export &Export Export the data in the current tab to a file Export the data in the current tab to a file Backup Wallet Backup Wallet Wallet Data (*.dat) Wallet Data (*.dat) Backup Failed Backup Failed There was an error trying to save the wallet data to %1. The wallet data was successfully saved to %1. Backup Successful Backup Successful bitcoin-core Options: Options: Specify data directory Specify data directory Connect to a node to retrieve peer addresses, and disconnect Connect to a node to retrieve peer addresses, and disconnect Specify your own public address Specify your own public address Accept command line and JSON-RPC commands Accept command line and JSON-RPC commands Run in the background as a daemon and accept commands Run in the background as a daemon and accept commands Use the test network Use the test network Accept connections from outside (default: 1 if no -proxy or -connect) Accept connections from outside (default: 1 if no -proxy or -connect) Bind to given address and always listen on it. Use [host]:port notation for IPv6 Bind to given address and always listen on it. Use [host]:port notation for IPv6 Continuously rate-limit free transactions to <n>*1000 bytes per minute (default: %u) Delete all wallet transactions and only recover those parts of the blockchain through -rescan on startup Distributed under the MIT software license, see the accompanying file COPYING or <http://www.opensource.org/licenses/mit-license.php>. Enter regression test mode, which uses a special chain in which blocks can be solved instantly. Execute command when a wallet transaction changes (%s in cmd is replaced by TxID) Execute command when a wallet transaction changes (%s in cmd is replaced by TxID) In this mode -genproclimit controls how many blocks are generated immediately. Maximum total fees to use in a single wallet transaction; setting this too low may abort large transactions (default: %s) Reduce storage requirements by pruning (deleting) old blocks. This mode disables wallet support and is incompatible with -txindex. 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) Set the number of script verification threads (%u to %d, 0 = auto, <0 = leave that many cores free, default: %d) This is a pre-release test build - use at your own risk - do not use for mining or merchant applications This is a pre-release test build - use at your own risk - do not use for mining or merchant applications Unable to bind to %s on this computer. Bitcoin Core is probably already running. Warning: -paytxfee is set very high! This is the transaction fee you will pay if you send a transaction. Warning: -paytxfee is set very high! This is the transaction fee you will pay if you send a transaction. Warning: The network does not appear to fully agree! Some miners appear to be experiencing issues. 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. Warning: We do not appear to fully agree with our peers! You may need to upgrade, or other nodes may need to upgrade. Warning: error reading wallet.dat! All keys read correctly, but transaction data or address book entries might be missing or incorrect. Warning: error reading wallet.dat! All keys read correctly, but transaction data or address book entries might be missing or incorrect. 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. 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. (default: 1) <category> can be: Attempt to recover private keys from a corrupt wallet.dat Attempt to recover private keys from a corrupt wallet.dat Block creation options: Block creation options: Connect only to the specified node(s) Connect only to the specified node(s) Connection options: Corrupted block database detected Corrupted block database detected Debugging/Testing options: Do not load the wallet and disable wallet RPC calls Do you want to rebuild the block database now? Do you want to rebuild the block database now? Error initializing block database Error initializing block database Error initializing wallet database environment %s! Error initializing wallet database environment %s! Error loading block database Error loading block database Error opening block database Error opening block database Error: A fatal internal error occured, see debug.log for details Error: Disk space is low! Error: Disk space is low! Failed to listen on any port. Use -listen=0 if you want this. Failed to listen on any port. Use -listen=0 if you want this. If <category> is not supplied, output all debugging information. Importing... Incorrect or no genesis block found. Wrong datadir for network? Incorrect or no genesis block found. Wrong datadir for network? Invalid -onion address: '%s' Not enough file descriptors available. Not enough file descriptors available. Only connect to nodes in network <net> (ipv4, ipv6 or onion) Prune 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) Specify wallet file (within data directory) This is intended for regression testing tools and app development. Use UPnP to map the listening port (default: %u) Verifying blocks... Verifying blocks... Verifying wallet... Verifying wallet... Wallet %s resides outside data directory %s Wallet %s resides outside data directory %s Wallet options: Warning: This version is obsolete; upgrade required! You need to rebuild the database using -reindex to change -txindex You need to rebuild the database using -reindex to change -txindex Imports blocks from external blk000??.dat file Imports blocks from external blk000??.dat file 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 times An error occurred while setting up the RPC address %s port %u for listening: %s Bind to given address and whitelist peers connecting to it. Use [host]:port notation for IPv6 Bind 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) Error: Unsupported argument -socks found. Setting SOCKS version isn't possible anymore, only SOCKS5 proxies are supported. Execute command when a relevant alert is received or we see a really long fork (%s in cmd is replaced by message) Execute command when a relevant alert is received or we see a really long fork (%s in cmd is replaced by message) Fees (in BTC/Kb) smaller than this are considered zero fee for relaying (default: %s) Fees (in BTC/Kb) smaller than this are considered zero fee for 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) Prune configured below the minimum of %d MB. Please use a higher number. Query for peer addresses via DNS lookup, if low on addresses (default: 1 unless -connect) Randomize credentials for every proxy connection. This enables Tor stream isolation (default: %u) Require high priority for relaying free or low-fee transactions (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 deducted This 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. To use bitcoind, or the -server option to bitcoin-qt, you must set an rpcpassword in the configuration file: %s It is recommended you use the following random password: rpcuser=bitcoinrpc rpcpassword=%s (you do not need to remember this password) The username and password MUST NOT be the same. If the file does not exist, create it with owner-readable-only file permissions. It is also recommended to set alertnotify so you are notified of problems; for example: alertnotify=echo %%s | mail -s "Bitcoin Alert" admin@foo.com Warning: -maxtxfee is set very high! Fees this large could be paid on a single transaction. Warning: Please check that your computer's date and time are correct! If your clock is wrong Bitcoin Core will not work properly. 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 gateway You 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... Allow self signed root certificates (default: 0) Can't run with a wallet in prune mode. Cannot resolve -whitebind address: '%s' Choose data directory on startup (default: 0) Choose data directory on startup (default: 0) Connect through SOCKS5 proxy Copyright (C) 2009-%i The Bitcoin Core Developers Could not parse -rpcbind value %s as network address Error loading wallet.dat: Wallet requires newer version of Bitcoin Core Error reading from database, shutting down. Error: Unsupported argument -tor found, use -onion. Fee (in BTC/kB) to add to transactions you send (default: %s) Information Information Initialization sanity check failed. Bitcoin Core is shutting down. Invalid amount for -maxtxfee=<amount>: '%s' Invalid amount for -minrelaytxfee=<amount>: '%s' Invalid amount for -minrelaytxfee=<amount>: '%s' Invalid amount for -mintxfee=<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 SSL options: (see the Bitcoin Wiki for SSL setup instructions) RPC server options: RPC support for HTTP persistent connections (default: %d) Randomly drop 1 of every <n> network messages Randomly fuzz 1 of every <n> network messages Send trace/debug info to console instead of debug.log file Send trace/debug info to console instead of debug.log file Send transactions as zero-fee transactions if possible (default: %u) Set SSL root certificates for payment request (default: -system-) Set language, for example "de_DE" (default: system locale) Set language, for example "de_DE" (default: system locale) Show all debugging options (usage: --help -help-debug) Show splash screen on startup (default: 1) Show splash screen on startup (default: 1) Shrink debug.log file on client startup (default: 1 when no -debug) Shrink debug.log file on client startup (default: 1 when no -debug) Signing transaction failed Signing transaction failed Start minimized Start minimized The transaction amount is too small to pay the fee This is experimental software. Transaction amount too small Transaction amount too small Transaction amounts must be positive Transaction amounts must be positive Transaction too large for fee policy Transaction too large Transaction too large UI Options: Unable to bind to %s on this computer (bind returned error %s) Use UPnP to map the listening port (default: 1 when listening) Use UPnP to map the listening port (default: 1 when listening) Username for JSON-RPC connections Username for JSON-RPC connections Wallet needed to be rewritten: restart Bitcoin Core to complete Warning Warning Warning: Unsupported argument -benchmark ignored, use -debug=bench. Warning: Unsupported argument -debugnet ignored, use -debug=net. Zapping all transactions from wallet... on startup wallet.dat corrupt, salvage failed wallet.dat corrupt, salvage failed Password for JSON-RPC connections Password for JSON-RPC connections Execute command when the best block changes (%s in cmd is replaced by block hash) Execute command when the best block changes (%s in cmd is replaced by block hash) Upgrade wallet to latest format Upgrade wallet to latest format Rescan the block chain for missing wallet transactions Rescan the block chain for missing wallet transactions Use OpenSSL (https) for JSON-RPC connections Use OpenSSL (https) for JSON-RPC connections This help message This help message Allow DNS lookups for -addnode, -seednode and -connect Allow DNS lookups for -addnode, -seednode and -connect Loading addresses... Loading addresses... Error loading wallet.dat: Wallet corrupted Error loading wallet.dat: Wallet corrupted (1 = keep tx meta data e.g. account owner and payment request information, 2 = drop tx meta data) Flush database activity from memory pool to disk log every <n> megabytes (default: %u) How thorough the block verification of -checkblocks is (0-4, default: %u) Log transaction priority and fee per kB when mining blocks (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) Use separate SOCKS5 proxy to reach peers via Tor hidden services (default: %s) (default: %s) Acceptable ciphers (default: %s) Always query for peer addresses via DNS lookup (default: %u) Disable safemode, override a real safe mode event (default: %u) Error loading wallet.dat Error loading wallet.dat Force safe mode (default: %u) Generate 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' Invalid -proxy address: '%s' Limit size of signature cache to <n> entries (default: %u) 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 transactions Maximum per-connection receive buffer, <n>*1000 bytes (default: %u) Maximum per-connection send buffer, <n>*1000 bytes (default: %u) Only accept block chain matching built-in checkpoints (default: %u) Prepend debug output with timestamp (default: %u) Relay and mine data carrier transactions (default: %u) Relay non-P2SH multisig (default: %u) Run a thread to flush wallet periodically (default: %u) Server certificate file (default: %s) Server private key (default: %s) 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) Sets the DB_PRIVATE flag in the wallet db environment (default: %u) 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) Stop running after importing blocks from disk (default: %u) Threshold for disconnecting misbehaving peers (default: %u) Unknown network specified in -onlynet: '%s' Unknown network specified in -onlynet: '%s' Cannot resolve -bind address: '%s' Cannot resolve -bind address: '%s' Cannot resolve -externalip address: '%s' Cannot resolve -externalip address: '%s' Invalid amount for -paytxfee=<amount>: '%s' Invalid amount for -paytxfee=<amount>: '%s' Insufficient funds Insufficient funds Loading block index... Loading block index... Add a node to connect to and attempt to keep the connection open Add a node to connect to and attempt to keep the connection open Loading wallet... Loading wallet... Cannot downgrade wallet Cannot downgrade wallet Cannot write default address Cannot write default address Rescanning... Rescanning... Done loading Done loading Error Error