Create a gist now Instantly share code, notes, and snippets.$ bitcoin-qt --help Bitcoin-Qt version v0.7.2-beta Usage: bitcoin-qt [command-line options] Options: -?This help message -conf= Specify configuration file (default: bitcoin.conf) -pid= Specify pid file (default: bitcoind.pid) -gen Generate coins -gen=0 Don't generate coins -datadir= Specify data directory -dbcache= Set database cache size in megabytes (default: 25) -dblogsize= Set database disk log size in megabytes (default: 100) -timeout= Specify connection timeout in milliseconds (default: 5000) -proxy= Connect through socks proxy -socks= Select the version of socks proxy to use (4-5, default: 5) -tor= Use proxy to reach tor hidden services (default: same as -proxy) -dns Allow DNS lookups for -addnode, -seednode and -connect -port= Listen for connections on (default: 8333 or testnet: 18333) -maxconnections= Maintain at most connections to peers (default: 125) -addnode= Add a node to connect to and attempt to keep the connection open -connect= Connect only to the specified node(s) -seednode= Connect to a node to retrieve peer addresses, and disconnect -externalip= Specify your own public address -onlynet= Only connect to nodes in network (IPv4, IPv6 or Tor) -discover Discover own IP address (default: 1 when listening and no -externalip) -irc Find peers using internet relay chat (default: 0) -listen Accept connections from outside (default: 1 if no -proxy or -connect) -bind= Bind to given address.

Use [host]:port notation for IPv6 -dnsseed Find peers using DNS lookup (default: 1 unless -connect) -banscore= Threshold for disconnecting misbehaving peers (default: 100) -bantime= Number of seconds to keep misbehaving peers from reconnecting (default: 86400) -maxreceivebuffer= Maximum per-connection receive buffer, *1000 bytes (default: 5000) -maxsendbuffer= Maximum per-connection send buffer, *1000 bytes (default: 1000) -upnp Use UPnP to map the listening port (default: 1 when listening) -detachdb Detach block and address databases.Increases shutdown time (default: 0) -paytxfee= Fee per KB to add to transactions you send -server Accept command line and JSON-RPC commands -testnet Use the test network -debug Output extra debugging information.Implies all other -debug* options -debugnet Output extra network debugging information -logtimestamps Prepend debug output with timestamp -shrinkdebugfile Shrink debug.log file on client startup (default: 1 when no -debug) -printtoconsole Send trace/debug info to console instead of debug.log file -rpcuser= Username for JSON-RPC connections -rpcpassword= Password for JSON-RPC connections -rpcport= Listen for JSON-RPC connections on (default: 8332 or testnet: 18332) -rpcallowip= Allow JSON-RPC connections from specified IP address -rpcconnect= Send commands to node running on (default: 127.0.0.1) -blocknotify= Execute command when the best block changes (%s in cmd is replaced by block hash) -upgradewallet Upgrade wallet to latest format -keypool= Set key pool size to (default: 100) -rescan Rescan the block chain for missing wallet transactions -salvagewallet Attempt to recover private keys from a corrupt wallet.dat -checkblocks= How many blocks to check at startup (default: 2500, 0 = all) -checklevel= How thorough the block verification is (0-6, default: 1) -loadblock= Imports blocks from external blk000?.dat file Block creation options: -blockminsize= Set minimum block size in bytes (default: 0) -blockmaxsize= Set maximum block size in bytes (default: 250000) -blockprioritysize= Set maximum size of high-priority/low-fee transactions in bytes (default: 27000) SSL options: (see the Bitcoin Wiki for SSL setup instructions) -rpcssl Use OpenSSL (https) for JSON-RPC connections -rpcsslcertificatechainfile= Server certificate file (default: server.cert) -rpcsslprivatekeyfile= Server private key (default: server.pem) -rpcsslciphers= Acceptable ciphers (default: TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH) UI options: -lang= Set language, for example "de_DE" (default: system locale) -min Start minimized -splash Show splash screen on startup (default: 1) Sign up for free to join this conversation on GitHub.

Already have an account?Sign in to comment You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Over the past year, I have been hanging out on various Bitcoin forums, the most frequented being Bitcointalk, and helping people out with various tech support issues with Bitcoin Core.I decided to compile the most frequent issues and troubleshooting tips into this post here, partially to help people troubleshoot their install, and partially to help me not have to keep posting the same thing over and over again.ethereal projection guideThis document will continue to grow as I hear of more and more troubleshooting issues.bitcoin norway apartmentIn Bitcoin Core, it is fairly easy to remove a transaction from your wallet so that you can resend the transaction with a higher fee.bitcoin 2013 fork

There are two methods to do so, the abandontransaction command and the -zapwallettxes startup option.To use the abandontransaction RPC, you first must be running Bitcoin Core 0.12 or later.Then open up the debug console and use the command where is the transaction id of your stuck transaction.Do this for every stuck transaction.If the command is successful, there will be no error and no output.If abandontransaction did not work or if you do not have Bitcoin Core 0.12 or later, then you can use the -zapwallettxes startup option.bitcoin tem futuroTo do so, just follow the instrucionts to start Bitcoin Core with an option where the option you want to use is -zapwallettxes.bitcoin mining mac usbIf your wallet balance is incorrect, a number of things could have gone wrong.bitcoin qt key

First double check that you are fully synced.Check a block explorer to see the latest block height.Next open Bitcoin Core and hover your mouse over the check mark at the bottom right hand corner.It should pop up with a little info box that says how many blocks Bitcoin Core has processed.This number should match the latest block height in the block explorer.If it does not, wait for Bitcoin Core to finish syncing.If you are synced, try starting Bitcoin Core with the -rescan option.If that does not fix the problem, next check your receiving addresses at File > Receiving addresses.Make sure that you are not missing any addresses.If you are, check whether the addresses you are missing are still in your wallet.If the address is missing from your wallet, then you will have to restore from a recent backup in order to recover it.Otherwise there is nothing that can be done.If your wallet is empty and you see no familiar transactions or addresses, it is likely that the wallet file Bitcoin Core is currently using is not your actual wallet.

If you had recently pressed the Reset Options button in Settings > Options, then your data directory may have been reverted to the default.To check, go to Help > Debug Window and go to the Information tab.In the field labeled Datadir, the path to your data directory will be listed.If that is not what you expect (custom if it was set, or default if not), then this is why your wallet is empty.If you had a custom data directory, you must start Bitcoin Core with the -datadir= option where is the path to your data directory.To open the debug console, go to Help > Debug Window in Bitcoin Core.In the new window that pops up, click on the Console tab.This is the debug console.You type the commands in the small box at the bottom of the window.The command help will give you a list of all commands available.Typing help , where is one of the commands, will give you the usage for that command.The debug window will let you know if something was successful through the output of each command.

Most of the commands will have an output.If the output is in black text, then your command was successfully run.If the output is in red text and has some sort of error code, then the command failed and there was an error.The commands also take arguments in JSON format, so entering the commands with proper JSON format and escaping is essential.Starting Bitcoin Core with startup options can be very useful.The method of doing so is dependent on your Operating System Right click the shortcut that you use for starting Bitcoin Core.Click on Properties in that menu.In the Properties window, go to the box labeled Target.Click the box and move your cursor all the way to the right, past what is already in there.Then just type the options you want, making sure that there is a space between what is already in the box and your option, and a space between each option.Then just click OK and double click the shortcut to start Bitcoin Core.When Bitcoin Core is fully started, you can repeat this process and remove the options that you added.

Open the terminal in Linux.If you did not install Bitcoin Core and are just running the binary, navigate to the directory you have the bitcoin-qt file in.Then type where are your startup options.Just make sure to have a space between each option.Press enter and Bitcoin Core will start with those options.Disclaimer: I don’t have a Mac so I am not 100% sure that this works, but it should.Open the Mac terminal.Open the debug console and use the command where

is the Bitcoin address whose private key you want to check is in the wallet.If the command was successful, it will print the private key to the console.DO NOT SHARE THE PRIVATE KEY WITH ANYONE.This key should begin with a ‘5’, ‘K’, or ‘L’.If it does not, it is not a private key.If the command failed with an error, the private key to the address is not in your wallet.The debug.log file is a log file that is very useful for troubleshooting.It does not leak any information about your private keys so your Bitcoin is always safe.