UTF-8 AboutDialog About Bitcoin બીટકોઈન વિષે Bitcoin 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. Copyright The Bitcoin developers AddressBookPage Address Book Double-click to edit address or label Create a new address Copy the currently selected address to the system clipboard &New Address These are your Bitcoin addresses for receiving payments. You may want to give a different one to each sender so you can keep track of who is paying you. &Copy Address Show &QR Code Sign a message to prove you own a Bitcoin address Sign &Message Delete the currently selected address from the list Export the data in the current tab to a file &Export Verify a message to ensure it was signed with a specified Bitcoin address &Verify Message &Delete These are your Bitcoin addresses for sending payments. Always check the amount and the receiving address before sending coins. Copy &Label &Edit Send &Coins Export Address Book Data Comma separated file (*.csv) Error exporting Could not write to file %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 Show general overview of wallet &Transactions Browse transaction history Edit the list of stored addresses and labels Show the list of addresses for receiving payments E&xit Quit application Show information about Bitcoin About &Qt Show information about Qt &Options... &Encrypt Wallet... &Backup Wallet... &Change Passphrase... 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 &Addresses &About Bitcoin &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 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 behind Last received block was generated %1 ago. Transactions after this will not yet be visible. Error Warning Information This transaction is over the size limit. You can still send it for a fee of %1, which goes to the nodes that process your transaction and helps to support the network. Do you want to pay the fee? Up to date Catching up... Confirm transaction fee Sent transaction Incoming transaction Date: %1 Amount: %2 Type: %3 Address: %4 URI handling URI can not be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. 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 EditAddressDialog Edit Address &Label The label associated with this address book entry &Address The address associated with this address book entry. This can only be modified for sending addresses. 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. GUIUtil::HelpMessageBox Bitcoin-Qt version Usage: command-line options UI options Set language, for example "de_DE" (default: system locale) Start minimized Show splash screen on startup (default: 1) OptionsDialog Options &Main Optional transaction fee per kB that helps make sure your transactions are processed quickly. Most transactions are 1 kB. Fee 0.01 recommended. Pay transaction &fee Automatically start Bitcoin after logging in to the system. &Start Bitcoin on system login Reset all client options to default. &Reset Options &Network 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 Connect to the Bitcoin network through a SOCKS proxy (e.g. when connecting through Tor). &Connect through SOCKS proxy: Proxy &IP: IP address of the proxy (e.g. 127.0.0.1) &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 &OK &Cancel &Apply default Confirm options reset Some settings may require a client restart to take effect. Do you want to proceed? Warning This setting will take effect after restarting Bitcoin. 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. Balance: Unconfirmed: Wallet Immature: Mined balance that has not yet matured Recent transactions Your current balance Total of transactions that have yet to be confirmed, and do not yet count toward the current balance out of sync PaymentServer Cannot start bitcoin: click-to-pay handler QRCodeDialog QR Code Dialog Request Payment Amount: Label: Message: &Save As... Error encoding URI into QR Code. The entered amount is invalid, please check. Resulting URI too long, try to reduce the text for label / message. Save QR Code PNG Images (*.png) RPCConsole Client name N/A Client version &Information Using OpenSSL version Startup time Network Number of connections On testnet Block chain Current number of blocks Estimated total blocks Last block time &Open Command-line options Show the Bitcoin-Qt help message to get a list with possible Bitcoin command-line options. &Show &Console Build date Bitcoin - Debug window Bitcoin Core 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. SendCoinsDialog Send Coins Send to multiple recipients at once Add &Recipient Remove all transaction fields Clear &All Balance: 123.456 BTC Confirm the send action S&end %1 to %2 (%3) Confirm send coins Are you sure you want to send %1? and 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. Error: Transaction creation failed! 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. SendCoinsEntry Form 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 address from address book Alt+A Paste address from clipboard Alt+P Remove this recipient Enter a Bitcoin address (e.g. 1NS17iag9jJgTHD1VXjvLCEnZuQ3rJDE9L) 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 an address from the address book 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 Enter Bitcoin 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 The Bitcoin developers [testnet] TransactionDesc Open until %1 %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 Generated coins must mature 120 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 Open for %n more block(s) Open until %1 Offline (%1 confirmations) Unconfirmed (%1 of %2 confirmations) Confirmed (%1 confirmations) Mined balance will be available when it matures in %n more block(s) 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 (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 Data Comma separated file (*.csv) Confirmed Date Type Label Address Amount ID Error exporting Could not write to file %1. Range: to WalletView 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 the new location. Backup Successful The wallet data was successfully saved to the new location. bitcoin-core Bitcoin version Usage: Send command to -server or bitcoind List commands Get help for a command Options: Specify configuration file (default: bitcoin.conf) Specify pid file (default: bitcoind.pid) Generate coins Don't generate coins Specify data directory Set database cache size in megabytes (default: 25) 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 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 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 Cannot obtain a lock on data directory %s. Bitcoin is probably already running. Error initializing database environment %s! To recover, BACKUP THAT DIRECTORY, then remove everything from it except for wallet.dat. 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 relevant alert is received (%s in cmd is replaced by message) Execute command when a wallet transaction changes (%s in cmd is replaced by TxID) Set maximum size of high-priority/low-fee transactions in bytes (default: 27000) Set the number of script verification threads (1-16, 0=auto, default: 0) This is a pre-release test build - use at your own risk - do not use for mining or merchant applications Warning: -paytxfee is set very high! This is the transaction fee you will pay if you send a transaction. Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade. Warning: Please check that your computer's date and time are correct! If your clock is wrong Bitcoin will not work properly. 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. Attempt to recover private keys from a corrupt wallet.dat Block creation options: Connect only to the specified node(s) Corrupted block database detected Discover own IP address (default: 1 when listening and no -externalip) 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: Transaction creation failed! 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 Find peers using DNS lookup (default: 1 unless -connect) How many blocks to check at startup (default: 288, 0 = all) How thorough the block verification is (0-4, default: 3) Rebuild block chain index from current blk000??.dat files Set the number of threads to service RPC calls (default: 4) Verifying blocks... Verifying wallet... Imports blocks from external blk000??.dat file Information Invalid -tor address: '%s' 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) Output extra debugging information. Implies all other -debug* options Output extra network debugging information Prepend debug output with timestamp SSL options: (see the Bitcoin Wiki for SSL setup instructions) Select the version of socks proxy to use (4-5, default: 5) Send trace/debug info to console instead of debug.log file Send trace/debug info to debugger Set maximum block size in bytes (default: 250000) Set minimum block size in bytes (default: 0) Shrink debug.log file on client startup (default: 1 when no -debug) Specify connection timeout in milliseconds (default: 5000) System error: Use UPnP to map the listening port (default: 0) Use UPnP to map the listening port (default: 1 when listening) Use proxy to reach tor hidden services (default: same as -proxy) Username for JSON-RPC connections Warning Warning: This version is obsolete, upgrade required! You need to rebuild the databases using -reindex to change -txindex 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) Acceptable ciphers (default: TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH) This help message Unable to bind to %s on this computer (bind returned error %d, %s) Connect through socks proxy 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 Unable to bind to %s on this computer. Bitcoin is probably already running. Fee per KB to add to transactions you send Loading wallet... Cannot downgrade wallet Cannot initialize keypool 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.