AboutDialog About Bitcoin Core Bitcoin Core version This is experimental software. Distributed under the MIT/X11 software license, see the accompanying file COPYING or http://www.opensource.org/licenses/mit-license.php. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/) and cryptographic software written by Eric Young (eay@cryptsoft.com) and UPnP software written by Thomas Bernard. Ce logiciel est en phase expérimentale. Distribué sous licence MIT/X11, voir le fichier COPYING ou http://www.opensource.org/licenses/mit-license.php. Ce produit comprend des logiciels développés par le projet OpenSSL pour être utilisés dans la boîte à outils OpenSSL (http://www.openssl.org/), un logiciel cryptographique écrit par Eric Young (eay@cryptsoft.com) et un logiciel UPnP écrit par Thomas Bernard. Copyright The Bitcoin Core developers (%1-bit) AddressBookPage Double-click to edit address or label Double-cliquez afin de modifier l'adress ou l'étiquette Create a new address Créer une nouvelle adresse &New Copy the currently selected address to the system clipboard Copier l'adresse surligné a votre presse-papier &Copy C&lose &Copy Address Delete the currently selected address from the list Export the data in the current tab to a file &Export &Delete &Supprimer 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 receiving payments. It is recommended to use a new receiving address for each transaction. Copy &Label &Edit Export Address List Comma separated file (*.csv) Exporting Failed There was an error trying to save the address list to %1. AddressTableModel Label Address (no label) AskPassphraseDialog Passphrase Dialog Enter passphrase New passphrase Repeat new passphrase Enter the new passphrase to the wallet. Please use a passphrase of 10 or more random characters, or eight or more words. Encrypt wallet This operation needs your wallet passphrase to unlock the wallet. Unlock wallet This operation needs your wallet passphrase to decrypt the wallet. Decrypt wallet Change passphrase Enter the old and new passphrase to the wallet. Confirm wallet encryption 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? 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 encrypted Bitcoin 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. Wallet encryption failed Wallet encryption failed due to an internal error. Your wallet was not encrypted. The supplied passphrases do not match. Wallet unlock failed The passphrase entered for the wallet decryption was incorrect. Wallet decryption failed Wallet passphrase was successfully changed. BitcoinGUI Sign &message... Synchronizing with network... &Overview Node Show general overview of wallet &Transactions Browse transaction history E&xit Quit application Show information about Bitcoin About &Qt Show information about Qt &Options... &Encrypt Wallet... &Backup Wallet... &Change Passphrase... &Sending addresses... &Receiving addresses... Open &URI... Importing blocks from disk... Reindexing blocks on disk... Send coins to a Bitcoin address Modify configuration options for Bitcoin Backup wallet to another location Change the passphrase used for wallet encryption &Debug window Open debugging and diagnostic console &Verify message... Bitcoin Wallet &Send &Receive &Show / Hide Show or hide the main Window Encrypt the private keys that belong to your wallet Sign messages with your Bitcoin addresses to prove you own them Verify messages to ensure they were signed with specified Bitcoin addresses &File &Settings &Help Tabs toolbar [testnet] Bitcoin Core Request payments (generates QR codes and bitcoin: URIs) &About 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 Bitcoin client %n active connection(s) to Bitcoin network No block source available... Processed %1 of %2 (estimated) blocks of transaction history. Processed %1 blocks of transaction history. %n hour(s) %n day(s) %n week(s) %1 and %2 %n year(s) %1 behind Last received block was generated %1 ago. Transactions after this will not yet be visible. Error Warning Information Up to date Catching up... Sent transaction Incoming transaction Date: %1 Amount: %2 Type: %3 Address: %4 Wallet is encrypted and currently unlocked Wallet is encrypted and currently locked A fatal error occurred. Bitcoin can no longer continue safely and will quit. ClientModel Network Alert CoinControlDialog Coin Control Address Selection Quantity: Bytes: Amount: Priority: Fee: Low Output: After Fee: Change: (un)select all Tree mode List mode Amount Address Date Confirmations Confirmed Priority Copy address Copy label Copy amount Copy transaction ID Lock unspent Unlock unspent Copy quantity Copy fee Copy after fee Copy bytes Copy priority Copy low output Copy change highest higher high medium-high medium low-medium low lower lowest (%1 locked) none Dust yes no This label turns red, if the transaction size is greater than 1000 bytes. 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. This label turns red, if the priority is smaller than "medium". This label turns red, if any recipient receives an amount smaller than %1. This means a fee of at least %1 is required. Amounts below 0.546 times the minimum relay fee are shown as dust. This label turns red, if the change is smaller than %1. (no label) change from %1 (%2) (change) EditAddressDialog Edit Address &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 New receiving address New sending address Edit receiving address Edit sending address The 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. FreespaceChecker A new data directory will be created. name Directory 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. HelpMessageDialog Bitcoin Core - Command-line options Bitcoin Core version Usage: command-line options UI options Set language, for example "de_DE" (default: system locale) Start minimized Set SSL root certificates for payment request (default: -system-) Show splash screen on startup (default: 1) Choose data directory on startup (default: 0) Intro 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 a custom data directory: Bitcoin Error: Specified data directory "%1" can not be created. Error GB of free space available (of %1GB needed) OpenURIDialog Open URI Open payment request from URI or file URI: Select payment request file Select payment request file to open OptionsDialog Options &Main Optional transaction fee per kB that helps make sure your transactions are processed quickly. Most transactions are 1 kB. Pay transaction &fee Automatically start Bitcoin after logging in to the system. &Start Bitcoin on system login Size of &database cache MB Number of script &verification threads Connect to the Bitcoin network through a SOCKS proxy. &Connect through SOCKS proxy (default proxy): IP address of the proxy (e.g. IPv4: 127.0.0.1 / IPv6: ::1) Active command-line options that override above options: Reset all client options to default. &Reset Options &Network (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. Map port using &UPnP Proxy &IP: &Port: Port of the proxy (e.g. 9050) SOCKS &Version: SOCKS version of the proxy (e.g. 5) &Window Show only a tray icon after minimizing the window. &Minimize to the tray instead of the taskbar Minimize instead of exit the application when the window is closed. When this option is enabled, the application will be closed only after selecting Quit in the menu. M&inimize on close &Display User Interface &language: The user interface language can be set here. This setting will take effect after restarting Bitcoin. &Unit to show amounts in: Choose the default subdivision unit to show in the interface and when sending coins. Whether to show Bitcoin addresses in the transaction list or not. &Display addresses in transaction list Whether to show coin control features or not. &OK &Cancel default none Confirm options reset Client restart required to activate changes. Client will be shutdown, do you want to proceed? This change would require a client restart. The supplied proxy address is invalid. OverviewPage 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. Wallet Available: Your current spendable balance Pending: Total of transactions that have yet to be confirmed, and do not yet count toward the spendable balance Immature: Mined balance that has not yet matured Total: Your current total balance Recent transactions out of sync PaymentServer URI handling URI can not be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. Requested payment amount of %1 is too small (considered dust). Payment request error Cannot start bitcoin: click-to-pay handler Net manager warning Your active proxy doesn't support SOCKS5, which is required for payment requests via proxy. Payment request fetch URL is invalid: %1 Payment request file handling Payment request file can not be read or processed! This can be caused by an invalid payment request file. Unverified payment requests to custom payment scripts are unsupported. Refund from %1 Error communicating with %1: %2 Payment request can not be parsed or processed! Bad response from server %1 Payment acknowledged Network request error QObject Bitcoin Error: Specified data directory "%1" does not exist. Error: Cannot parse configuration file: %1. Only use key=value syntax. Error: Invalid combination of -regtest and -testnet. Enter a Bitcoin address (e.g. 1NS17iag9jJgTHD1VXjvLCEnZuQ3rJDE9L) QRImageWidget &Save Image... &Copy Image Save QR Code PNG Image (*.png) RPCConsole Client name N/A Client version &Information Debug window General Using OpenSSL version Startup time Network Name Number of connections Block chain Current number of blocks Estimated total blocks Last block time &Open &Console &Network Traffic &Clear Totals In: Out: Build date Debug log file Open the Bitcoin debug log file from the current data directory. This can take a few seconds for large log files. Clear console Welcome to the Bitcoin RPC console. Use up and down arrows to navigate history, and Ctrl-L to clear screen. Type help for an overview of available commands. %1 B %1 KB %1 MB %1 GB %1 m %1 h %1 h %2 m ReceiveCoinsDialog &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 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 message Copy amount ReceiveRequestDialog QR Code Copy &URI Copy &Address &Save Image... Request payment to %1 Payment information URI Address Amount Label Message Resulting URI too long, try to reduce the text for label / message. Error encoding URI into QR Code. RecentRequestsTableModel Date Label Message Amount (no label) (no message) (no amount) SendCoinsDialog Send Coins Coin Control Features Inputs... automatically selected Insufficient funds! Quantity: Bytes: Amount: Priority: Fee: Low Output: 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 Send to multiple recipients at once Add &Recipient Clear all fields of the form. Clear &All Balance: Confirm the send action S&end Confirm send coins %1 to %2 Copy quantity Copy amount Copy fee Copy after fee Copy bytes Copy priority Copy low output Copy change Total Amount %1 (= %2) or The 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, can only send to each address once per send operation. 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. Warning: Invalid Bitcoin address (no label) Warning: Unknown change address Are you sure you want to send? added as transaction fee Payment request expired Invalid payment address %1 SendCoinsEntry A&mount: Pay &To: The address to send the payment to (e.g. 1NS17iag9jJgTHD1VXjvLCEnZuQ3rJDE9L) Enter a label for this address to add it to your address book &Label: Choose previously used address This is a normal payment. Alt+A Paste address from clipboard Alt+P Remove this entry Message: This is a verified 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. This is an unverified payment request. 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 &Sign Message You can sign messages with your addresses to prove you own them. Be careful not to sign anything vague, as phishing attacks may try to trick you into signing your identity over to them. Only sign fully-detailed statements you agree to. The address to sign the message with (e.g. 1NS17iag9jJgTHD1VXjvLCEnZuQ3rJDE9L) Choose previously used address Alt+A Paste address from clipboard Alt+P Enter the message you want to sign here Signature Copy the current signature to the system clipboard Sign the message to prove you own this Bitcoin address Sign &Message Reset all sign message fields Clear &All &Verify Message Enter the signing 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. The address the message was signed with (e.g. 1NS17iag9jJgTHD1VXjvLCEnZuQ3rJDE9L) Verify the message to ensure it was signed with the specified Bitcoin address Verify &Message Reset all verify message fields Enter a Bitcoin address (e.g. 1NS17iag9jJgTHD1VXjvLCEnZuQ3rJDE9L) Click "Sign Message" to generate signature The 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 Bitcoin Core The Bitcoin Core developers [testnet] TrafficGraphWidget KB/s TransactionDesc Open until %1 conflicted %1/offline %1/unconfirmed %1 confirmations Status , broadcast through %n node(s) Date Source Generated From To own address label Credit matures in %n more block(s) not accepted Debit Transaction fee Net amount Message Comment 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 Transaction Inputs Amount true false , has not been successfully broadcast yet Open for %n more block(s) unknown TransactionDescDialog Transaction details This pane shows a detailed description of the transaction TransactionTableModel Date Type Address Amount Immature (%1 confirmations, will be available after %2) Open for %n more block(s) Open until %1 Confirmed (%1 confirmations) This block was not received by any other nodes and will probably not be accepted! Generated but not accepted Offline Unconfirmed Confirming (%1 of %2 recommended confirmations) Conflicted Received with Received from Sent to Payment to yourself Mined (n/a) Transaction status. Hover over this field to show number of confirmations. Date and time that the transaction was received. Type of transaction. Destination address of transaction. Amount removed from or added to balance. TransactionView All Today This week This month Last month This year Range... Received with Sent to To yourself Mined Other Enter address or label to search Min amount Copy address Copy label Copy amount Copy transaction ID Edit label Show transaction details Export Transaction History 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) Confirmed Date Type Label Address Amount ID Range: to WalletFrame No wallet has been loaded. WalletModel Send Coins WalletView &Export Export the data in the current tab to a file Backup Wallet Wallet Data (*.dat) Backup Failed There was an error trying to save the wallet data to %1. The wallet data was successfully saved to %1. Backup Successful bitcoin-core Usage: List commands Get help for a command Options: Specify configuration file (default: bitcoin.conf) Specify pid file (default: bitcoind.pid) Specify data directory Listen for connections on <port> (default: 8333 or testnet: 18333) Maintain at most <n> connections to peers (default: 125) Connect to a node to retrieve peer addresses, and disconnect Specify your own public address Threshold for disconnecting misbehaving peers (default: 100) Number of seconds to keep misbehaving peers from reconnecting (default: 86400) An error occurred while setting up the RPC port %u for listening on IPv4: %s Listen for JSON-RPC connections on <port> (default: 8332 or testnet: 18332) Accept command line and JSON-RPC commands Bitcoin Core RPC client version Run in the background as a daemon and accept commands Use the test network Accept connections from outside (default: 1 if no -proxy or -connect) %s, you must set a 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 Acceptable ciphers (default: TLSv1.2+HIGH:TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!3DES:@STRENGTH) An error occurred while setting up the RPC port %u for listening on IPv6, falling back to IPv4: %s 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:15) Enter regression test mode, which uses a special chain in which blocks can be solved instantly. This is intended for regression testing tools and app development. Enter regression test mode, which uses a special chain in which blocks can be solved instantly. Error: Listening for incoming connections failed (listen returned error %d) Error: 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. Error: This transaction requires a transaction fee of at least %s because of its amount, complexity, or use of recently received funds! Execute command when a wallet transaction changes (%s in cmd is replaced by TxID) Fees smaller than this are considered zero fee (for transaction creation) (default: Flush database activity from memory pool to disk log every <n> megabytes (default: 100) How thorough the block verification of -checkblocks is (0-4, default: 3) In this mode -genproclimit controls how many blocks are generated immediately. Set the number of script verification threads (%u to %d, 0 = auto, <0 = leave that many cores free, default: %d) Set the processor limit for when generation is on (-1 = unlimited, default: -1) 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. Use separate SOCKS5 proxy to reach peers via Tor hidden services (default: -proxy) Warning: -paytxfee is set very high! This is the transaction fee you will pay if you send a transaction. Warning: Please check that your computer's date and time are correct! If your clock is wrong Bitcoin will not work properly. 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: 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. (default: 1) (default: wallet.dat) <category> can be: Attempt to recover private keys from a corrupt wallet.dat Bitcoin Core Daemon Block creation options: Clear list of wallet transactions (diagnostic tool; implies -rescan) Connect only to the specified node(s) Connect through SOCKS proxy Connect to JSON-RPC on <port> (default: 8332 or testnet: 18332) Connection options: Corrupted block database detected Debugging/Testing options: Disable safemode, override a real safe mode event (default: 0) Discover own IP address (default: 1 when listening and no -externalip) Do not load the wallet and disable wallet RPC calls Do you want to rebuild the block database now? Error initializing block database Error initializing wallet database environment %s! Error loading block database Error opening block database Error: Disk space is low! Error: Wallet locked, unable to create transaction! Error: system error: Failed to listen on any port. Use -listen=0 if you want this. Failed to read block info Failed to read block Failed to sync block index Failed to write block index Failed to write block info Failed to write block Failed to write file info Failed to write to coin database Failed to write transaction index Failed to write undo data Fee per kB to add to transactions you send Fees smaller than this are considered zero fee (for relaying) (default: Find peers using DNS lookup (default: 1 unless -connect) Force safe mode (default: 0) Generate coins (default: 0) How many blocks to check at startup (default: 288, 0 = all) If <category> is not supplied, output all debugging information. Incorrect or no genesis block found. Wrong datadir for network? Invalid -onion address: '%s' Not enough file descriptors available. Prepend debug output with timestamp (default: 1) RPC client options: Rebuild block chain index from current blk000??.dat files Select SOCKS version for -proxy (4 or 5, default: 5) Set database cache size in megabytes (%d to %d, default: %d) Set maximum block size in bytes (default: %d) Set the number of threads to service RPC calls (default: 4) Specify wallet file (within data directory) Spend unconfirmed change when sending transactions (default: 1) This is intended for regression testing tools and app development. Usage (deprecated, use bitcoin-cli): Verifying blocks... Verifying wallet... Wait for RPC server to start Wallet %s resides outside data directory %s Wallet options: Warning: Deprecated argument -debugnet ignored, use -debug=net You need to rebuild the database using -reindex to change -txindex Imports blocks from external blk000??.dat file Cannot obtain a lock on data directory %s. Bitcoin Core is probably already running. Execute command when a relevant alert is received or we see a really long fork (%s in cmd is replaced by message) Output debugging information (default: 0, supplying <category> is optional) Set maximum size of high-priority/low-fee transactions in bytes (default: %d) Information Invalid amount for -minrelaytxfee=<amount>: '%s' Invalid amount for -mintxfee=<amount>: '%s' Limit size of signature cache to <n> entries (default: 50000) Log transaction priority and fee per kB when mining blocks (default: 0) Maintain a full transaction index (default: 0) Maximum per-connection receive buffer, <n>*1000 bytes (default: 5000) Maximum per-connection send buffer, <n>*1000 bytes (default: 1000) Only accept block chain matching built-in checkpoints (default: 1) Only connect to nodes in network <net> (IPv4, IPv6 or Tor) Print block on startup, if found in block index Print block tree on startup (default: 0) RPC SSL options: (see the Bitcoin Wiki for SSL setup instructions) RPC server options: Randomly drop 1 of every <n> network messages Randomly fuzz 1 of every <n> network messages Run a thread to flush wallet periodically (default: 1) SSL options: (see the Bitcoin Wiki for SSL setup instructions) Send command to Bitcoin Core Send trace/debug info to console instead of debug.log file Set minimum block size in bytes (default: 0) Sets the DB_PRIVATE flag in the wallet db environment (default: 1) Show all debugging options (usage: --help -help-debug) Show benchmark information (default: 0) Shrink debug.log file on client startup (default: 1 when no -debug) Signing transaction failed Specify connection timeout in milliseconds (default: 5000) Start Bitcoin Core Daemon System error: Transaction amount too small Transaction amounts must be positive Transaction too large Use UPnP to map the listening port (default: 0) Use UPnP to map the listening port (default: 1 when listening) Username for JSON-RPC connections Warning Warning: This version is obsolete, upgrade required! Zapping all transactions from wallet... on startup version wallet.dat corrupt, salvage failed Password for JSON-RPC connections Allow JSON-RPC connections from specified IP address Send commands to node running on <ip> (default: 127.0.0.1) Execute command when the best block changes (%s in cmd is replaced by block hash) Upgrade wallet to latest format Set key pool size to <n> (default: 100) Rescan the block chain for missing wallet transactions Use OpenSSL (https) for JSON-RPC connections Server certificate file (default: server.cert) Server private key (default: server.pem) This help message Unable to bind to %s on this computer (bind returned error %d, %s) Allow DNS lookups for -addnode, -seednode and -connect Loading addresses... Error loading wallet.dat: Wallet corrupted Error loading wallet.dat: Wallet requires newer version of Bitcoin Wallet needed to be rewritten: restart Bitcoin to complete Error loading wallet.dat Invalid -proxy address: '%s' Unknown network specified in -onlynet: '%s' Unknown -socks proxy version requested: %i Cannot resolve -bind address: '%s' Cannot resolve -externalip address: '%s' Invalid amount for -paytxfee=<amount>: '%s' Invalid amount Insufficient funds Loading block index... Add a node to connect to and attempt to keep the connection open Loading wallet... Cannot downgrade wallet Cannot write default address Rescanning... Done loading To use the %s option Error You must set rpcpassword=<password> in the configuration file: %s If the file does not exist, create it with owner-readable-only file permissions.