AboutDialogAbout Dash Core<b>Dash Core</b> 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.CopyrightThe Bitcoin Core developersThe Dash Core developers(%1-bit)AddressBookPageDouble-click to edit address or labelCreate a new address&NewCopy the currently selected address to the system clipboard&CopyDelete the currently selected address from the list&DeleteExport the data in the current tab to a file&ExportC&loseChoose the address to send coins toChoose the address to receive coins withC&hooseSending addressesReceiving addressesThese are your Dash addresses for sending payments. Always check the amount and the receiving address before sending coins.These are your Dash addresses for receiving payments. It is recommended to use a new receiving address for each transaction.&Copy AddressCopy &Label&EditExport Address ListComma separated file (*.csv)Exporting FailedThere was an error trying to save the address list to %1.AddressTableModelLabelAddress(no label)AskPassphraseDialogPassphrase DialogEnter passphraseNew passphraseRepeat new passphraseServes to disable the trivial sendmoney when OS account compromised. Provides no real security.For anonymization onlyEnter the new passphrase to the wallet.<br/>Please use a passphrase of <b>10 or more random characters</b>, or <b>eight or more words</b>.Encrypt walletThis operation needs your wallet passphrase to unlock the wallet.Unlock walletThis operation needs your wallet passphrase to decrypt the wallet.Decrypt walletChange passphraseEnter the old and new passphrase to the wallet.Confirm wallet encryptionWarning: If you encrypt your wallet and lose your passphrase, you will <b>LOSE ALL OF YOUR DASHS</b>!Are you sure you wish to encrypt your wallet?Wallet encryptedDash will close now to finish the encryption process. Remember that encrypting your wallet cannot fully protect your dashs 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 failedWallet encryption failed due to an internal error. Your wallet was not encrypted.The supplied passphrases do not match.Wallet unlock failedThe passphrase entered for the wallet decryption was incorrect.Wallet decryption failedWallet passphrase was successfully changed.Warning: The Caps Lock key is on!BitcoinGUIDash CoreWalletNode[testnet]&OverviewShow general overview of wallet&SendSend coins to a Dash address&ReceiveRequest payments (generates QR codes and dash: URIs)&TransactionsBrowse transaction historyE&xitQuit application&About Dash CoreShow information about DashAbout &QtShow information about Qt&Options...Modify configuration options for Dash&Show / HideShow or hide the main Window&Encrypt Wallet...Encrypt the private keys that belong to your wallet&Backup Wallet...Backup wallet to another location&Change Passphrase...Change the passphrase used for wallet encryption&Unlock Wallet...Unlock wallet&Lock WalletSign &message...Sign messages with your Dash addresses to prove you own them&Verify message...Verify messages to ensure they were signed with specified Dash addresses&InformationShow diagnostic information&Debug consoleOpen debugging console&Network MonitorShow network monitor&Sending addresses...Show the list of used sending addresses and labels&Receiving addresses...Show the list of used receiving addresses and labelsOpen &URI...Open a dash: URI or payment request&Command-line optionsShow the Dash Core help message to get a list with possible Dash command-line options&File&Settings&Tools&HelpTabs toolbarDash client%n active connection(s) to Dash network%n active connection(s) to Dash networkSynchronizing with network...Importing blocks from disk...Reindexing blocks on disk...No block source available...Processed %1 blocks of transaction history.Up to date%n hour(s)%n hour(s)%n day(s)%n day(s)%n week(s)%n week(s)%1 and %2%n year(s)%n year(s)%1 behindCatching up...Last received block was generated %1 ago.Transactions after this will not yet be visible.DashErrorWarningInformationSent transactionIncoming transactionDate: %1
Amount: %2
Type: %3
Address: %4
Wallet is <b>encrypted</b> and currently <b>unlocked</b>Wallet is <b>encrypted</b> and currently <b>unlocked</b> for anonimization onlyWallet is <b>encrypted</b> and currently <b>locked</b>A fatal error occurred. Dash can no longer continue safely and will quit.ClientModelNetwork AlertCoinControlDialogCoin Control Address SelectionQuantity:Bytes:Amount:Priority:Fee:Low Output:After Fee:Change:(un)select allTree modeList modeAmountLabelAddressDarksend RoundsDateConfirmationsConfirmedPriorityCopy addressCopy labelCopy amountCopy transaction IDLock unspentUnlock unspentCopy quantityCopy feeCopy after feeCopy bytesCopy priorityCopy low outputCopy changehighesthigherhighmedium-highn/amediumlow-mediumlowlowerlowest(%1 locked)noneDustyesnoThis 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)DarksendConfigConfigure DarksendBasic PrivacyHigh PrivacyMaximum PrivacyPlease select a privacy level.Use 2 separate masternodes to mix funds up to 1000 DASHUse 8 separate masternodes to mix funds up to 1000 DASHUse 16 separate masternodesThis option is the quickest and will cost about ~0.025 DASH to anonymize 1000 DASHThis option is moderately fast and will cost about 0.05 DASH to anonymize 1000 DASH0.1 DASH per 1000 DASH you anonymize.This is the slowest and most secure option. Using maximum anonymity will costDarksend ConfigurationDarksend was successfully set to basic (%1 and 2 rounds). You can change this at any time by opening Dash's configuration screen.Darksend was successfully set to high (%1 and 8 rounds). You can change this at any time by opening Dash's configuration screen.Darksend was successfully set to maximum (%1 and 16 rounds). You can change this at any time by opening Dash's configuration screen.EditAddressDialogEdit Address&LabelThe label associated with this address list entry&AddressThe address associated with this address list entry. This can only be modified for sending addresses.New receiving addressNew sending addressEdit receiving addressEdit sending addressThe entered address "%1" is not a valid Dash address.The entered address "%1" is already in the address book.Could not unlock wallet.New key generation failed.FreespaceCheckerA new data directory will be created.nameDirectory already exists. Add %1 if you intend to create a new directory here.Path already exists, and is not a directory.Cannot create data directory here.HelpMessageDialogDash Core - Command-line optionsDash CoreversionUsage:command-line optionsUI optionsChoose data directory on startup (default: 0)Set language, for example "de_DE" (default: system locale)Start minimizedSet SSL root certificates for payment request (default: -system-)Show splash screen on startup (default: 1)IntroWelcomeWelcome to Dash Core.As this is the first time the program is launched, you can choose where Dash Core will store its data.Dash Core will download and store a copy of the Dash block chain. At least %1GB of data will be stored in this directory, and it will grow over time. The wallet will also be stored in this directory.Use the default data directoryUse a custom data directory:DashError: Specified data directory "%1" can not be created.ErrorGB of free space available(of %1GB needed)OpenURIDialogOpen URIOpen payment request from URI or fileURI:Select payment request fileSelect payment request file to openOptionsDialogOptions&MainAutomatically start Dash after logging in to the system.&Start Dash on system loginSize of &database cacheMBNumber of script &verification threads(0 = auto, <0 = leave that many cores free)<html><head/><body><p>This setting determines the amount of individual masternodes that an input will be anonymized through. More rounds of anonymization gives a higher degree of privacy, but also costs more in fees.</p></body></html>Darksend rounds to useAmount of Dash to keep anonymizedW&alletOptional transaction fee per kB that helps make sure your transactions are processed quickly. Most transactions are 1 kB.Pay transaction &feeExpertWhether to show coin control features or not.Enable coin &control featuresIf you disable the spending of unconfirmed change, the change from a transaction cannot be used until that transaction has at least one confirmation. This also affects how your balance is computed.&Spend unconfirmed change&NetworkAutomatically open the Dash client port on the router. This only works when your router supports UPnP and it is enabled.Map port using &UPnPConnect to the Dash network through a SOCKS proxy.&Connect through SOCKS proxy (default proxy):Proxy &IP:IP address of the proxy (e.g. IPv4: 127.0.0.1 / IPv6: ::1)&Port:Port of the proxy (e.g. 9050)SOCKS &Version:SOCKS version of the proxy (e.g. 5)&WindowShow only a tray icon after minimizing the window.&Minimize to the tray instead of the taskbarMinimize 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&DisplayUser Interface &language:The user interface language can be set here. This setting will take effect after restarting Dash.&Unit to show amounts in:Choose the default subdivision unit to show in the interface and when sending coins.Whether to show Dash addresses in the transaction list or not.&Display addresses in transaction listThird party URLs (e.g. a block explorer) that appear in the transactions tab as context menu items. %s in the URL is replaced by transaction hash. Multiple URLs are separated by vertical bar |.Third party transaction URLsActive command-line options that override above options:Reset all client options to default.&Reset Options&OK&CanceldefaultnoneConfirm options resetClient 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.OverviewPageFormWalletThe displayed information may be out of date. Your wallet automatically synchronizes with the Dash network after a connection is established, but this process has not completed yet.Available:Your current spendable balancePending:Total of transactions that have yet to be confirmed, and do not yet count toward the spendable balanceImmature:Mined balance that has not yet maturedTotal:Your current total balanceStatus:Enabled/DisabledCompletion:Darksend Balance:0 DASHAmount and Rounds:0 DASH / 0 RoundsSubmitted Denom:The denominations you submitted to the Masternode. To mix, other users must submit the exact same denominations.n/aDarksendStart/Stop Mixing(Last Message)Try to manually submit a Darksend request.Try MixReset the current status of Darksend (can interrupt Darksend if it's in the process of Mixing, which can cost you money!)Reset<b>Recent transactions</b>out of syncDisabledStart Darksend MixingStop Darksend MixingNo inputs detectedFound unconfirmed denominated outputs, will wait till they confirm to recalculate.RoundsEnabledLast Darksend message:
Darksend is idle.Darksend request complete: Your transaction was accepted into the pool!Submitted following entries to masternode:Submitted to masternode, Waiting for more entriesFound enough users, signing ...Found enough users, signing ( waiting. )Found enough users, signing ( waiting.. )Found enough users, signing ( waiting... )Transmitting final transaction.Finalizing transaction.Darksend request incomplete:Will retry...Darksend request complete:Submitted to masternode, waiting in queue .Submitted to masternode, waiting in queue ..Submitted to masternode, waiting in queue ...Unknown state:N/ADarksend was successfully reset.Darksend requires at least %1 to use.Wallet is locked and user declined to unlock. Disabling Darksend.PaymentServerPayment request errorCannot start dash: click-to-pay handlerNet manager warningYour active proxy doesn't support SOCKS5, which is required for payment requests via proxy.URI handlingPayment request fetch URL is invalid: %1URI can not be parsed! This can be caused by an invalid Dash address or malformed URI parameters.Payment request file handlingPayment 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.Requested payment amount of %1 is too small (considered dust).Refund from %1Error communicating with %1: %2Payment request can not be parsed or processed!Bad response from server %1Network request errorPayment acknowledgedQObjectDashError: Specified data directory "%1" does not exist.Error: Cannot parse configuration file: %1. Only use key=value syntax.Error reading masternode configuration file: %1Error: Invalid combination of -regtest and -testnet.Dash Core didn't yet exit safely...Enter a Dash address (e.g. XwnLY9Tf7Zsef8gMGL2fhWA9ZmMjt4KPwg)QRImageWidget&Save Image...&Copy ImageSave QR CodePNG Image (*.png)RPCConsoleTools window&InformationMasternode CountGeneralNameClient nameN/ANumber of connectionsOpen the Dash debug log file from the current data directory. This can take a few seconds for large log files.&OpenStartup timeNetworkLast block timeDebug log fileUsing OpenSSL versionBuild dateCurrent number of blocksClient versionBlock chain&ConsoleClear console&Network Traffic&ClearTotalsIn:Out:Welcome to the Dash RPC console.Use up and down arrows to navigate history, and <b>Ctrl-L</b> to clear screen.Type <b>help</b> for an overview of available commands.%1 B%1 KB%1 MB%1 GB%1 m%1 h%1 h %2 mReceiveCoinsDialogReuse 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 Dash network.&Message:An optional label to associate with the new receiving address.Use this form to request payments. All fields are <b>optional</b>.&Label:An optional amount to request. Leave this empty or zero to not request a specific amount.&Amount:&Request paymentClear all fields of the form.ClearRequested payments historyShow the selected request (does the same as double clicking an entry)ShowRemove the selected entries from the listRemoveCopy labelCopy messageCopy amountReceiveRequestDialogQR CodeCopy &URICopy &Address&Save Image...Request payment to %1Payment informationURIAddressAmountLabelMessageResulting URI too long, try to reduce the text for label / message.Error encoding URI into QR Code.RecentRequestsTableModelDateLabelMessageAmount(no label)(no message)(no amount)SendCoinsDialogSend CoinsCoin Control FeaturesInputs...automatically selectedInsufficient funds!Quantity:Bytes:Amount:Priority:mediumFee:Low Output:noAfter 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 addressConfirm the send actionS&endClear all fields of the form.Clear &AllSend to multiple recipients at onceAdd &RecipientDarksendInstantXBalance:Copy quantityCopy amountCopy feeCopy after feeCopy bytesCopy priorityCopy low outputCopy change(darksend requires this amount to be rounded up to the nearest %1).%1 to %2Are you sure you want to send?are added as transaction feeTotal Amount %1 (= %2)orConfirm send coinsPayment request expiredInvalid payment address %1The 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.Error: The wallet was unlocked only to anonymize coins.Warning: Invalid Dash addressWarning: Unknown change address(no label)SendCoinsEntryThis is a normal payment.Pay &To:The address to send the payment to (e.g. XwnLY9Tf7Zsef8gMGL2fhWA9ZmMjt4KPwg)Choose previously used addressAlt+APaste address from clipboardAlt+PRemove this entry&Label:Enter a label for this address to add it to the list of used addressesA&mount:Message:A message that was attached to the dash: URI which will be stored with the transaction for your reference. Note: This message will not be sent over the Dash network.This is an unverified payment request.Pay To:Memo:This is a verified payment request.Enter a label for this address to add it to your address bookShutdownWindowDash Core is shutting down...Do not shut down the computer until this window disappears.SignVerifyMessageDialogSignatures - Sign / Verify a Message&Sign MessageYou 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. XwnLY9Tf7Zsef8gMGL2fhWA9ZmMjt4KPwg)Choose previously used addressAlt+APaste address from clipboardAlt+PEnter the message you want to sign hereSignatureCopy the current signature to the system clipboardSign the message to prove you own this Dash addressSign &MessageReset all sign message fieldsClear &All&Verify MessageEnter 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. XwnLY9Tf7Zsef8gMGL2fhWA9ZmMjt4KPwg)Verify the message to ensure it was signed with the specified Dash addressVerify &MessageReset all verify message fieldsClick "Sign Message" to generate signatureEnter a Dash address (e.g. XwnLY9Tf7Zsef8gMGL2fhWA9ZmMjt4KPwg)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.SplashScreenDash CoreVersion %1The Bitcoin Core developersThe Dash Core developers[testnet]TrafficGraphWidgetKB/sTransactionDescOpen for %n more block(s)Open for %n more block(s)Open until %1conflicted%1/offline (verified via instantx)%1/confirmed (verified via instantx)%1 confirmations (verified via instantx)%1/offline%1/unconfirmed%1 confirmations%1/offline (InstantX verification in progress - %2 of %3 signatures)%1/confirmed (InstantX verification in progress - %2 of %3 signatures )%1 confirmations (InstantX verification in progress - %2 of %3 signatures)%1/offline (InstantX verification failed)%1/confirmed (InstantX verification failed)Status, has not been successfully broadcast yet, broadcast through %n node(s), broadcast through %n node(s)DateSourceGeneratedFromunknownToown addresslabelCreditmatures in %n more block(s)matures in %n more block(s)not acceptedDebitTransaction feeNet amountMessageCommentTransaction IDMerchantGenerated coins must mature %1 blocks before they can be spent. When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.Debug informationTransactionInputsAmounttruefalseTransactionDescDialogTransaction detailsThis pane shows a detailed description of the transactionTransactionTableModelDateTypeAddressAmountOpen for %n more block(s)Open for %n more block(s)Open until %1OfflineUnconfirmedConfirming (%1 of %2 recommended confirmations)Confirmed (%1 confirmations)ConflictedImmature (%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 acceptedReceived withReceived fromReceived via DarksendSent toPayment to yourselfMinedDarksend DenominateDarksend Collateral PaymentDarksend Make Collateral InputsDarksend Create DenominationsDarksent(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.TransactionViewAllTodayThis weekThis monthLast monthThis yearRange...Received withSent toDarksentDarksend Make Collateral InputsDarksend Create DenominationsDarksend DenominateDarksend Collateral PaymentTo yourselfMinedOtherEnter address or label to searchMin amountCopy addressCopy labelCopy amountCopy transaction IDEdit labelShow transaction detailsExport Transaction HistoryComma separated file (*.csv)ConfirmedDateTypeLabelAddressAmountIDExporting FailedThere was an error trying to save the transaction history to %1.Exporting SuccessfulThe transaction history was successfully saved to %1.Range:toWalletFrameNo wallet has been loaded.WalletModelSend CoinsWalletView&ExportExport the data in the current tab to a fileBackup WalletWallet Data (*.dat)Backup FailedThere was an error trying to save the wallet data to %1.Backup SuccessfulThe wallet data was successfully saved to %1.dash-core%s, you must set a rpcpassword in the configuration file:
%s
It is recommended you use the following random password:
rpcuser=dashrpc
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 "Dash 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 IPv4: %sAn error occurred while setting up the RPC port %u for listening on IPv6, falling back to IPv4: %sBind to given address and always listen on it. Use [host]:port notation for IPv6Cannot obtain a lock on data directory %s. Dash Core is probably already running.Continuously rate-limit free transactions to <n>*1000 bytes per minute (default:15)Darksend uses exact denominated amounts to send funds, you might simply need to anonymize some more coins.Disable all Masternode and Darksend related functionality (0-1, default: 0)Enable instantx, show confirmations for locked transactions (bool, default: true)Enable use of automated darksend for funds stored in this wallet (0-1, default: 0)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 %s)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!Error: Wallet unlocked for anonymization only, unable to create transaction.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 wallet transaction changes (%s in cmd is replaced by TxID)Execute command when the best block changes (%s in cmd is replaced by block hash)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)Found unconfirmed denominated outputs, will wait till they confirm to continue.How thorough the block verification of -checkblocks is (0-4, default: 3)In this mode -genproclimit controls how many blocks are generated immediately.InstantX requires inputs with at least 6 confirmations, you might need to wait a few minutes and try again.Listen for JSON-RPC connections on <port> (default: 9998 or testnet: 19998)Name to construct url for KeePass entry that stores the wallet passphraseNumber of seconds to keep misbehaving peers from reconnecting (default: 86400)Output debugging information (default: 0, supplying <category> is optional)Provide liquidity to Darksend by infrequently mixing coins on a continual basis (0-100, default: 0, 1=very frequent, high fees, 100=very infrequent, low fees)Query for peer addresses via DNS lookup, if low on addresses (default: 1 unless -connect)Set external address:port to get to this masternode (example: address:port)Set maximum size of high-priority/low-fee transactions in bytes (default: %d)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)Show N confirmations for a successfully locked transaction (0-9999, default: 1)This is a pre-release test build - use at your own risk - do not use for mining or merchant applicationsUnable to bind to %s on this computer. Dash Core is probably already running.Unable to locate enough Darksend denominated funds for this transaction.Unable to locate enough Darksend non-denominated funds for this transaction that are not equal 1000 DASH.Unable to locate enough Darksend non-denominated funds for this transaction.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 Dash 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.You must set rpcpassword=<password> in the configuration file:
%s
If the file does not exist, create it with owner-readable-only file permissions.You must specify a masternodeprivkey in the configuration. Please see documentation for help.(default: 1)(default: wallet.dat)<category> can be:Accept command line and JSON-RPC commandsAccept connections from outside (default: 1 if no -proxy or -connect)Add a node to connect to and attempt to keep the connection openAllow DNS lookups for -addnode, -seednode and -connectAllow JSON-RPC connections from specified IP addressAlready have that input.Always query for peer addresses via DNS lookup (default: 0)Attempt to recover private keys from a corrupt wallet.datBlock creation options:Can't denominate: no compatible inputs left.Cannot downgrade walletCannot resolve -bind address: '%s'Cannot resolve -externalip address: '%s'Cannot write default addressClear list of wallet transactions (diagnostic tool; implies -rescan)Collateral is not valid.Collateral not valid.Connect only to the specified node(s)Connect through SOCKS proxyConnect to JSON-RPC on <port> (default: 9998 or testnet: 19998)Connect to KeePassHttp on port <port> (default: 19455)Connect to a node to retrieve peer addresses, and disconnectConnection options:Corrupted block database detectedDash Core DaemonDash Core RPC client versionDarksend is disabled.Darksend options: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 callsDo you want to rebuild the block database now?Done loadingEnable the client to act as a masternode (0-1, default: 0)Entries are full.Error connecting to masternode.Error initializing block databaseError initializing wallet database environment %s!Error loading block databaseError loading wallet.datError loading wallet.dat: Wallet corruptedError loading wallet.dat: Wallet requires newer version of DashError opening block databaseError reading from database, shutting down.Error recovering public key.ErrorError: Disk space is low!Error: Wallet locked, unable to create transaction!Error: You already have pending entries in the Darksend poolError: system error: Failed to listen on any port. Use -listen=0 if you want this.Failed to read block infoFailed to read blockFailed to sync block indexFailed to write block indexFailed to write block infoFailed to write blockFailed to write file infoFailed to write to coin databaseFailed to write transaction indexFailed to write undo dataFee per kB to add to transactions you sendFees smaller than this are considered zero fee (for relaying) (default:Force safe mode (default: 0)Generate coins (default: 0)Get help for a commandHow many blocks to check at startup (default: 288, 0 = all)If <category> is not supplied, output all debugging information.Ignore masternodes less than version (example: 70050; default : 0)Importing...Imports blocks from external blk000??.dat fileIncompatible mode.Incompatible version.Incorrect or no genesis block found. Wrong datadir for network?InformationInitialization sanity check failed. Dash Core is shutting down.Input is not valid.InstantX options:Insufficient fundsInsufficient funds.Invalid -onion address: '%s'Invalid -proxy address: '%s'Invalid amount for -minrelaytxfee=<amount>: '%s'Invalid amount for -mintxfee=<amount>: '%s'Invalid amount for -paytxfee=<amount>: '%s'Invalid amountInvalid masternodeprivkey. Please see documenation.Invalid private key.Invalid script detected.KeePassHttp id for the established associationKeePassHttp key for AES encrypted communication with KeePassKeep N dash anonymized (default: 0)Keep at most <n> unconnectable blocks in memory (default: %u)Keep at most <n> unconnectable transactions in memory (default: %u)Last Darksend was too recent.Last successful darksend action was too recent.Limit size of signature cache to <n> entries (default: 50000)List commandsListen for connections on <port> (default: 9999 or testnet: 19999)Loading addresses...Loading block index...Loading wallet... (%3.2f %%)Loading wallet...Log transaction priority and fee per kB when mining blocks (default: 0)Maintain a full transaction index (default: 0)Maintain at most <n> connections to peers (default: 125)Masternode options:Masternode queue is full.Masternode:Maximum per-connection receive buffer, <n>*1000 bytes (default: 5000)Maximum per-connection send buffer, <n>*1000 bytes (default: 1000)Missing input transaction information.No compatible masternode found.No funds detected in need of denominating.No masternodes detected.No matching denominations found for mixing.Non-standard public key detected.Not compatible with existing transactions.Not enough file descriptors available.Not in the masternode list.Only accept block chain matching built-in checkpoints (default: 1)Only connect to nodes in network <net> (IPv4, IPv6 or Tor)Options:Password for JSON-RPC connectionsPrepend debug output with timestamp (default: 1)Print block on startup, if found in block indexPrint block tree on startup (default: 0)RPC SSL options: (see the Bitcoin Wiki for SSL setup instructions)RPC client options:RPC server options:Randomly drop 1 of every <n> network messagesRandomly fuzz 1 of every <n> network messagesRebuild block chain index from current blk000??.dat filesRescan the block chain for missing wallet transactionsRescanning...Run a thread to flush wallet periodically (default: 1)Run in the background as a daemon and accept commandsSSL options: (see the Bitcoin Wiki for SSL setup instructions)Select SOCKS version for -proxy (4 or 5, default: 5)Send command to Dash CoreSend commands to node running on <ip> (default: 127.0.0.1)Send trace/debug info to console instead of debug.log fileServer certificate file (default: server.cert)Server private key (default: server.pem)Session not complete!Session timed out (30 seconds), please resubmit.Set database cache size in megabytes (%d to %d, default: %d)Set key pool size to <n> (default: 100)Set maximum block size in bytes (default: %d)Set minimum block size in bytes (default: 0)Set the masternode private keySet the number of threads to service RPC calls (default: 4)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 failed.Signing timed out, please resubmit.Signing transaction failedSpecify configuration file (default: dash.conf)Specify connection timeout in milliseconds (default: 5000)Specify data directorySpecify masternode configuration file (default: masternode.conf)Specify pid file (default: dashd.pid)Specify wallet file (within data directory)Specify your own public addressSpend unconfirmed change when sending transactions (default: 1)Start Dash Core DaemonSystem error: This help messageThis is intended for regression testing tools and app development.This is not a masternode.Threshold for disconnecting misbehaving peers (default: 100)To use the %s optionTransaction amount too smallTransaction amounts must be positiveTransaction created successfully.Transaction fees are too high.Transaction not valid.Transaction too largeUnable to bind to %s on this computer (bind returned error %s)Unable to sign masternode payment winner, wrong key?Unable to sign spork message, wrong key?Unknown -socks proxy version requested: %iUnknown network specified in -onlynet: '%s'Upgrade wallet to latest formatUsage (deprecated, use dash-cli):Usage:Use KeePass 2 integration using KeePassHttp plugin (default: 0)Use N separate masternodes to anonymize funds (2-8, default: 2)Use OpenSSL (https) for JSON-RPC connectionsUse UPnP to map the listening port (default: 0)Use UPnP to map the listening port (default: 1 when listening)Use the test networkUsername for JSON-RPC connectionsValue more than Darksend pool maximum allows.Verifying blocks...Verifying wallet...Wait for RPC server to startWallet %s resides outside data directory %sWallet is locked.Wallet needed to be rewritten: restart Dash to completeWallet options:WarningWarning: Deprecated argument -debugnet ignored, use -debug=netWarning: This version is obsolete, upgrade required!Wrong state.You need to rebuild the database using -reindex to change -txindexZapping all transactions from wallet...on startupversionwallet.dat corrupt, salvage failed