Was going to switch sig campaigns, then I realized this was still the only campaigns with no minimum post requirement  . BitMixer still promotes spam less than any other sig campain on bitcointalk.org (although I still wish the payment model hadn't changed  ). |
|
|
|
OK, I'll try it.
How do you call up this -reindex option ?
Do you run the thing from the command prompt bitcoin-qt.exe-reindex ?
Yes, running "bitcoin-qt.exe -reindex" from the command line should work. Modifying a shortcut would as well, but you only want to do the reindex once, not every time you start it. You can remove the -reindex after you start it, so it's really just personal preference to which you use. |
|
|
|
|
Just right click on your bitcoin-qt shortcut, select "properties", then add " -reindex" (without the quotes) to the end of the target line.
|
|
|
|
Oddly enough though if I have adequately "aged" UTXOs I can send txs (that involve a large enough BTC amount) with *no fee* and they will appear generally in the very next block!
priority = sum(input_value_in_base_units * input_age)/size_in_bytes (source: https://en.bitcoin.it/wiki/Transaction_fees#Technical_info) Input age (number of confirmations) and number of coins sent have a huge affect on transaction priority. (assuming the pools haven't changed the relevant settings too much.) |
|
|
|
|
You could use Tor as a temporary solution to accessing blockchain.info.
|
|
|
|
|
Could you explain what you mean by it doesn't work? Does it throw an error message? Does Bitcoin-qt just use the default directory?
|
|
|
|
How do i do it on my mac. that works for windows.
From what I've found the easiest way is to create a script. Open terminal and type: then add the code #! /bin/bash
open /path/to/BitcoinCore.app -datadir=/path/to/new/directory Hit control+x, then y, then return. (Exit, save file, confirm filename) Run chmod 711 bitcoin.command Now you can run Bitcoin Core with the datadir option by double clicking on the bitcoin.command file. |
|
|
|
|
Right-click on the shortcut you want to edit then left-click "properties".
|
|
|
|
Thanks! The only reason I know is because I wanted to do the same thing myself, but found out it doesn't work.  |
|
|
|
The sensible thing to do in that case would be to keep two different wallet files, one for personal, and one for business. You can use the -datadir parameter for the client to point it at a different folder for storing one or the other. It takes a bit more disk space, but that's relatively cheap these days, and it's a lot less hassle than trying to keep it all separate manually.
-wallet=<file> would be more useful in this case. OP could simply create two shortcuts, one label business and one labeled personal, each one pointing to their respective wallet file. Source for command line options: https://en.bitcoin.it/wiki/Running_Bitcoin#Command-line_arguments |
|
|
|
Who actually uses Tor as their main browser? Tor is used to fulfill "illegal" or"blackhat" needs for most users, instead of regular use.
Tor is not a broswer for illegal activities. Saying Tor is only used for illegal activities is like saying the dollar is only used for illegal activities because someone used it to purchase illegal items. What Tor is: "Tor is free software and an open network that helps you defend against traffic analysis, a form of network surveillance that threatens personal freedom and privacy, confidential business activities and relationships, and state security." (torproject.org) |
|
|
|
I was expecting to see a larger portion of Tor users.  Maybe most of them just don't want to advertise their browser choices. |
|
|
|
Shut down, restarted Bitcoin-Qt. New error message on dialog: "Warning: displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."
Maybe the error is merely because it already knows that it is not caught up with the tip? If so, perhaps the db is OK? Should I just wait it out?
The message simply means you are not completely synced. The db is fine. Let me know if Bitcoin Core starts syncing once you let it run for a bit. Funny thing there... way back when, I set Armory to autostart bitcoind - but it never did. I still need to run it (well, Bitcoin-Qt) manually.
Are you sure Armory won't autostart bitcoind? Bitcoind is Bitcoin Core without the user interface. It won't show up on your desktop, but you can confirm it is running through Activity Monitor (Mac version of Task Manager). I am still somewhat confused by the interaction between bitcoin.conf, and the fields in Bitcoin-Qt>Preferences. I had already changed some of those through the GUI. I was puzzled that invoking 'touch bitcoin.conf' at the prompt did not revert all the settings in the GUI to defaults. Yes, I had terminated Bitcoin-Qt before creating the file.
From my experience the bitcoin.conf only affects the settings which are set in the file. If you don't have an option for it in bitcoin.conf file it will stay as it is. |
|
|
|
Looks like your using my bitcoin.conf file from here (minus the update I just made): https://bitcointalk.org/index.php?topic=623868.msg6917399#msg6917399Can I also assume that all other configuration is the same (besides Armory not being set to start Bitcoind on it own)? I have been sitting at 'Current number of blocks: 312933', 'Estimated total blocks 313044' since launch about an hour ago.
This isn't normal but I don't believe the problem is your config file. Here's what each option actually does(source= https://en.bitcoin.it/wiki/Running_Bitcoin: bind=127.0.0.1 (Bind to given address and always listen on it. In other words Bitcoin Core only communicates with your computer and thus only with Armory or through Tor.) port=8333 (Listen for connections on port 8333. This allows Bitcoin Core to talk to Armory on port 8333 while talking to Tor on port 9150.) upnp=0 (Turns off UPnP. Not sure what UPnP is, but this needs to be turned of to properly use Tor) proxy=127.0.0.1:9150 (Connect through SOCKS proxy. This is what tells Bitcoin Core to connect to Tor.) None of the options should prevent you from syncin while your connected. Try restarting your computer and see if that helps. If that doesn't work try running Bitcoin Core without Tor. You'll have to remove the config file in order to run Bitcoin Core without Tor. I reallize this is a lot of information without an actual solution, but hopefully this helps you or someone else solve your problem. |
|
|
|
|
I replaced listen=1 with port=8333 in bitcoin.conf as port serves the same purpose as listen but only listens on port 8333.
|
|
|
|
|
What settings or options are you using to connect Armory to Bitcoin Core while Bitcoin Core is connected through Tor?
|
|
|
|
|
Show Posts
