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 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 receiving payments. It is recommended to use a new receiving address for each transaction. &Copy Address Copy &Label &Edit Export Address List Comma separated file (*.csv) Exporting Failed There was an error trying to save the address list to %1. Please try again. AddressTableModel Label Address (no label) AskPassphraseDialog Passphrase Dialog Passphrase Dialog Enter passphrase Enter passphrase New passphrase New passphrase Repeat new passphrase Repeat new passphrase Enter the new passphrase to the wallet. Please use a passphrase of ten 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 passphrase 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? Wallet encrypted %1 will close now to finish the encryption process. Remember that encrypting your wallet cannot fully protect your bitcoins from being stolen by malware infecting your computer. IMPORTANT: Any previous backups you have made of your wallet file should be replaced with the newly generated, encrypted wallet file. For security reasons, previous backups of the unencrypted wallet file will become useless as soon as you start using the new, encrypted wallet. Wallet encryption 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. Warning: The Caps Lock key is on! BanTableModel IP/Netmask Banned Until 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 %1 Show information about %1 About &Qt About &Qt Show information about Qt Show information about Qt &Options... &Options... Modify configuration options for %1 &Encrypt Wallet... &Encrypt Wallet... &Backup Wallet... &Backup Wallet... &Change Passphrase... &Change Passphrase... &Sending addresses... &Receiving addresses... Open &URI... Click to disable network activity. Network activity disabled. Click to enable network activity again. 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 / 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 Request payments (generates QR codes and bitcoin: URIs) 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 %n active connection(s) to Bitcoin network %n active connection to Bitcoin network %n active connections to Bitcoin network Indexing blocks on disk... Processing blocks on disk... 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. %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 Show the %1 help message to get a list with possible Bitcoin command-line options %1 client Catching up... Catching up... Date: %1 Amount: %1 Type: %1 Label: %1 Address: %1 Sent transaction Sent transaction Incoming transaction Incoming transaction HD key generation is enabled HD key generation is disabled Wallet is encrypted and currently unlocked Wallet is encrypted and currently unlocked Wallet is encrypted and currently locked Wallet is encrypted and currently locked CoinControlDialog Coin Selection Quantity: Bytes: Amount: 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 Copy address Copy label Copy amount Copy transaction ID Lock unspent Unlock unspent Copy quantity Copy fee Copy after fee Copy bytes Copy dust Copy change (%1 locked) yes no This label turns red if any recipient receives an amount smaller than the current dust threshold. Can vary +/- %1 satoshi(s) per input. (no label) change from %1 (%2) (change) 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 sending address Edit receiving address Edit sending address The entered address "%1" is not a valid Bitcoin address. The entered address "%1" is already in the address book. Could not unlock wallet. New key generation failed. 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 version version (%1-bit) About %1 Command-line options Usage: Usage: command-line options command-line options UI Options: Choose data directory on startup (default: %u) 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: %u) Reset all settings changed in the GUI Intro Welcome Welcome Welcome to %1. As this is the first time the program is launched, you can choose where %1 will store its data. %1 will download and store a copy of the Bitcoin block chain. At least %2GB 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: Error: Specified data directory "%1" cannot be created. Error Error %n GB of free space available (of %n GB needed) ModalOverlay Form Form Recent transactions may not yet be visible, and therefore your wallet's balance might be incorrect. This information will be correct once your wallet has finished synchronizing with the bitcoin network, as detailed below. Attempting to spend bitcoins that are affected by not-yet-displayed transactions will not be accepted by the network. Number of blocks left Unknown... Last block time Last block time Progress ~ Progress increase per hour calculating... Estimated time left until synced Hide Unknown. Syncing Headers (%1)... 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 Automatically start %1 after logging in to the system. &Start %1 on system login 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. 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 (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) Used for reaching peers via: Shows, if the supplied default SOCKS5 proxy is used to reach peers via this network type. IPv4 IPv6 Tor Connect to the Bitcoin network through a separate SOCKS5 proxy for Tor hidden services. Use separate SOCKS5 proxy to reach peers via Tor hidden services: &Window &Window &Hide the icon from the system tray. Hide tray icon 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: The user interface language can be set here. This setting will take effect after restarting %1. &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 PaymentServer Payment request error Cannot start bitcoin: click-to-pay handler URI handling Payment request fetch URL is invalid: %1 Invalid payment address %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 rejected Payment request network doesn't match client network. Payment request expired. Payment request is not initialized. Unverified payment requests to custom payment scripts are unsupported. Invalid payment request. Requested payment amount of %1 is too small (considered dust). Refund from %1 Payment request %1 is too large (%2 bytes, allowed %3 bytes). Error communicating with %1: %2 Payment request cannot be parsed! Bad response from server %1 Network request error Payment acknowledged PeerTableModel User Agent Node/Service NodeId Ping 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 %n seconds(s) %n minutes(s) %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 QRImageWidget &Save Image... &Copy Image Save QR Code PNG Image (*.png) RPCConsole N/A N/A Client version Client version &Information &Information Debug window General Using BerkeleyDB version Datadir 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 Memory Pool Current number of transactions Memory usage Received Sent &Peers Banned peers Select a peer to view detailed information. Whitelisted Direction Version Starting Block Synced Headers Synced Blocks User Agent Open the %1 debug log file from the current data directory. This can take a few seconds for large log files. Decrease font size Increase font size Services Ban Score Connection Time Last Send Last Receive Ping Time The duration of a currently outstanding ping. Ping Wait Min Ping Time Offset Last block time Last block time &Open &Open &Console &Console &Network Traffic &Clear Totals In: Out: Debug log file Debug log file Clear console Clear console 1 &hour 1 &day 1 &week 1 &year &Disconnect Ban for &Unban Welcome to the %1 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. WARNING: Scammers have been active, telling users to type commands here, stealing their wallet contents. Do not use this console without fully understanding the ramification of a command. Network activity disabled %1 B %1 KB %1 MB %1 GB (node id: %1) via %1 never Inbound Outbound Yes No Unknown 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 URI Copy label Copy message Copy amount ReceiveRequestDialog QR Code Copy &URI Copy &Address &Save Image... Request payment to %1 Payment information URI Address Amount Amount Label Message Resulting URI too long, try to reduce the text for label / message. Error encoding URI into QR Code. RecentRequestsTableModel Date Date Label Message (no label) (no message) (no amount requested) Requested SendCoinsDialog Send Coins Send Coins Coin Control Features Inputs... automatically selected Insufficient funds! Quantity: Bytes: Amount: Fee: After Fee: Change: If this is activated, but the change address is empty or invalid, change will be sent to a newly generated address. Custom change 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...) normal fast Send to multiple recipients at once Send to multiple recipients at once Add &Recipient Add &Recipient Clear all fields of the form. Dust: Confirmation time target: (count) Clear &All Clear &All Balance: Balance: Confirm the send action Confirm the send action S&end S&end Copy quantity Copy amount Copy fee Copy after fee Copy bytes Copy dust Copy change %1 to %2 Are you sure you want to send? added as transaction fee Total Amount %1 or Confirm send coins 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: addresses should only be used once each. Transaction creation failed! The transaction was rejected with the following reason: %1 A fee higher than %1 is considered an absurdly high fee. Payment request expired. %n block(s) Pay only the required fee of %1 Estimated to begin confirmation within %n block(s). Warning: Invalid Bitcoin address Warning: Unknown change address (no label) SendCoinsEntry A&mount: A&mount: Pay &To: Pay &To: &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: Enter a label for this address to add it to your address book SendConfirmationDialog Yes ShutdownWindow %1 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 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 [testnet] [testnet] TrafficGraphWidget KB/s TransactionDesc Open for %n more block(s) Open until %1 conflicted with a transaction with %1 confirmations %1/offline 0/unconfirmed, %1 in memory pool not in memory pool abandoned %1/unconfirmed %1 confirmations Status , has not been successfully broadcast yet , broadcast through %n node(s) Date Date Source Generated From unknown To own address watch-only label Credit matures in %n more block(s) not accepted Debit Total debit Total credit Transaction fee Net amount Message Comment Transaction ID Transaction total size Output index 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 Amount true false TransactionDescDialog This pane shows a detailed description of the transaction This pane shows a detailed description of the transaction Details for %1 TransactionTableModel Date Date Type Label Open for %n more block(s) Open until %1 Offline Unconfirmed Abandoned Confirming (%1 of %2 recommended confirmations) Confirmed (%1 confirmations) Conflicted Immature (%1 confirmations, will be available after %2) This block was not received by any other nodes and will probably not be accepted! Generated but not accepted Received with Received from Sent to Payment to yourself Mined watch-only (n/a) (no label) Transaction status. Hover over this field to show number of confirmations. Date and time that the transaction was received. Type of transaction. Whether or not a watch-only address is involved in this transaction. User-defined intent/purpose of the transaction. Amount removed from or added to balance. 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 Abandon transaction Copy address Copy label Copy amount Copy transaction ID Copy raw transaction Copy full transaction details Edit label Show transaction details Export Transaction History Comma separated file (*.csv) Confirmed Confirmed Watch-only Date Date Type Label Address ID Exporting Failed There was an error trying to save the transaction history to %1. Exporting Successful The transaction history was successfully saved to %1. Range: 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 Wallet Data (*.dat) Backup Failed There was an error trying to save the wallet data to %1. Backup Successful The wallet data was successfully saved to %1. 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 Accept connections from outside (default: 1 if no -proxy or -connect/-noconnect) Connect only to the specified node(s); -noconnect or -connect=0 alone to disable automatic connections Distributed under the MIT software license, see the accompanying file %s or %s If <category> is not supplied or if <category> = 1, output all debugging information. Prune configured below the minimum of %d MiB. Please use a higher number. Prune: last wallet synchronisation goes beyond pruned data. You need to -reindex (download the whole blockchain again in case of pruned node) 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 details Fee (in %s/kB) to add to transactions you send (default: %s) Pruning blockstore... Run in the background as a daemon and accept commands Run in the background as a daemon and accept commands Unable to start HTTP server. See debug log for details. Bitcoin Core Bitcoin Core The %s developers 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 IPv6 Bind to given address and always listen on it. Use [host]:port notation for IPv6 Cannot obtain a lock on data directory %s. %s is probably already running. Delete all wallet transactions and only recover those parts of the blockchain through -rescan on startup Error loading %s: You can't enable HD on a already existing non-HD wallet Error reading %s! All keys read correctly, but transaction data or address book entries might be missing or incorrect. 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) Maximum allowed median peer time offset adjustment. Local perspective of time may be influenced by peers forward or backward by this amount. (default: %u seconds) Maximum total fees (in %s) to use in a single wallet transaction or raw transaction; setting this too low may abort large transactions (default: %s) Please check that your computer's date and time are correct! If your clock is wrong, %s will not work properly. Please contribute if you find %s useful. Visit %s for further information about the software. 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 correct Unable to rewind the database to a pre-fork state. You will need to redownload the blockchain Use UPnP to map the listening port (default: 1 when listening and no -proxy) You need to rebuild the database using -reindex-chainstate to change -txindex %s corrupt, salvage failed -maxmempool must be at least %d MB <category> can be: Append comment to the user agent string Attempt to recover private keys from a corrupt wallet on startup Block creation options: Block creation options: Cannot resolve -%s address: '%s' Change index out of range Connection options: Copyright (C) %i-%i 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? 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 initializing block database Error initializing block database Error initializing wallet database environment %s! Error initializing wallet database environment %s! Error loading %s Error loading %s: Wallet corrupted Error loading %s: Wallet requires newer version of %s Error loading %s: You can't disable HD on a already existing HD wallet Error loading block database Error loading block database Error opening block database Error opening block database 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. Importing... Incorrect or no genesis block found. Wrong datadir for network? Incorrect or no genesis block found. Wrong datadir for network? Initialization sanity check failed. %s is shutting down. Invalid -onion address: '%s' Invalid amount for -%s=<amount>: '%s' Invalid amount for -fallbackfee=<amount>: '%s' Keep the transaction memory pool below <n> megabytes (default: %u) Loading banlist... Location of the auth cookie (default: data dir) Not enough file descriptors available. Not enough file descriptors available. Only connect to nodes in network <net> (ipv4, ipv6 or onion) Print this help message and exit Print version and exit Prune cannot be configured with a negative value. Prune mode is incompatible with -txindex. Rebuild chain state and block index from the blk*.dat files on disk Rebuild chain state from the currently indexed blocks Rewinding blocks... 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) The source code is available from %s. Unable to bind to %s on this computer. %s is probably already running. Unsupported argument -benchmark ignored, use -debug=bench. Unsupported argument -debugnet ignored, use -debug=net. Unsupported argument -tor found, use -onion. Use UPnP to map the listening port (default: %u) User Agent comment (%s) contains unsafe characters. Verifying blocks... Verifying blocks... Verifying wallet... Verifying wallet... Wallet %s resides outside data directory %s Wallet %s resides outside data directory %s Wallet debugging/testing options: Wallet needed to be rewritten: restart %s to complete Wallet options: Allow JSON-RPC connections from specified source. Valid for <ip> are a single IP (e.g. 1.2.3.4), a network/netmask (e.g. 1.2.3.4/255.255.255.0) or a network/CIDR (e.g. 1.2.3.4/24). This option can be specified multiple times 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) 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) 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) Randomize 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) The transaction amount is too small to send after the fee has been deducted Use hierarchical deterministic key generation (HD) after BIP32. Only has effect during wallet creation/first start 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) Automatically create Tor hidden service (default: %d) Connect through SOCKS5 proxy Error reading from database, shutting down. Imports blocks from external blk000??.dat file on startup Information Information Invalid amount for -paytxfee=<amount>: '%s' (must be at least %s) Invalid netmask specified in -whitelist: '%s' Keep at most <n> unconnectable transactions in memory (default: %u) Need to specify a port with -whitebind: '%s' Node relay options: RPC server options: Reducing -maxconnections from %d to %d, because of system limitations. Rescan the block chain for missing wallet transactions on startup 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) Show all debugging options (usage: --help -help-debug) 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 The transaction amount is too small to pay the fee This is experimental software. Tor control port password (default: empty) Tor control port to use if onion listening enabled (default: %s) Transaction amount too small Transaction amount too small Transaction too large for fee policy Transaction too large Transaction too large Unable to bind to %s on this computer (bind returned error %s) Upgrade wallet to latest format on startup Username for JSON-RPC connections Username for JSON-RPC connections Warning Warning Warning: unknown new rules activated (versionbit %i) Whether to operate in a blocks only mode (default: %u) Zapping all transactions from wallet... ZeroMQ notification options: 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) Allow DNS lookups for -addnode, -seednode and -connect Allow DNS lookups for -addnode, -seednode and -connect Loading addresses... Loading addresses... (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. Do not keep transactions in the mempool longer than <n> hours (default: %u) Equivalent bytes per sigop in transactions for relay and mining (default: %u) Fees (in %s/kB) smaller than this are considered zero fee for transaction creation (default: %s) Force relay of transactions from whitelisted peers even if they violate local relay policy (default: %d) How thorough the block verification of -checkblocks is (0-4, default: %u) Maintain a full transaction index, used by the getrawtransaction rpc call (default: %u) Number of seconds to keep misbehaving peers from reconnecting (default: %u) Output debugging information (default: %u, supplying <category> is optional) Query for peer addresses via DNS lookup, if low on addresses (default: 1 unless -connect/-noconnect) Sets the serialization of raw transaction or block hex returned in non-verbose mode, non-segwit(0) or segwit(1) (default: %d) Support filtering of blocks and transaction with bloom filters (default: %u) This is the transaction fee you may pay when fee estimates are not available. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit %s and cryptographic software written by Eric Young and UPnP software written by Thomas Bernard. Total length of network version string (%i) exceeds maximum length (%i). Reduce the number or size of uacomments. Tries to keep outbound traffic under the given target (in MiB per 24h), 0 = no limit (default: %d) Unsupported argument -socks found. Setting SOCKS version isn't possible anymore, only SOCKS5 proxies are supported. Unsupported argument -whitelistalwaysrelay ignored, use -whitelistrelay and/or -whitelistforcerelay. Use separate SOCKS5 proxy to reach peers via Tor hidden services (default: %s) 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 Wallet will not create transactions that violate mempool chain limits (default: %u Warning: Unknown block versions being mined! It's possible unknown rules are in effect Warning: Wallet file corrupt, data salvaged! Original %s saved as %s in %s; if your balance or transactions are incorrect you should restore from a backup. Whitelist peers connecting from the given IP address (e.g. 1.2.3.4) or CIDR notated network (e.g. 1.2.3.0/24). Can be specified multiple times. %s is set very high! (default: %s) Always query for peer addresses via DNS lookup (default: %u) 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' Keypool ran out, please call keypoolrefill first Listen for JSON-RPC connections on <port> (default: %u or testnet: %u) Listen for connections on <port> (default: %u or testnet: %u) Maintain at most <n> connections to peers (default: %u) Make the wallet broadcast transactions Maximum 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) Send transactions with full-RBF opt-in enabled (default: %u) Set key pool size to <n> (default: %u) Set maximum BIP141 block weight (default: %d) Set the number of threads to service RPC calls (default: %d) Specify configuration file (default: %s) Specify connection timeout in milliseconds (minimum: 1, default: %d) Specify pid file (default: %s) Spend unconfirmed change when sending transactions (default: %u) Starting network threads... The wallet will avoid paying less than the minimum relay fee. This is the minimum transaction fee you pay on every transaction. This is the transaction fee you will pay if you send a transaction. Threshold for disconnecting misbehaving peers (default: %u) Transaction amounts must not be negative Transaction has too long of a mempool chain Transaction must have at least one recipient Unknown network specified in -onlynet: '%s' Unknown network specified in -onlynet: '%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