There has been some discussion in the "Armory - Discussion Thread" on how to setup Armory to work while Bitcoin Core runs through Tor.  However, it has kinda gotten lost in the mountain of information there.  I've noticed some more questions about this subject pop up and thought I'd post a how to here.

Tor Browser Bundle setup:
1) Download and extract Tor Browser Bundle (no need to change any settings, you can just run Tor Browser Bundle as default)

Bitcoin Core setup:
1) Download and install Bitcoin Core
2) Run Bitcoin Core and deselect "Map port using UPnP" and select "Connect through SOCKS proxy".
3) Make sure you settings match these:  (Proxy IP: 127.0.0.1, Port: 9150, SOCKS Version: 5)(replaced with some lines in bitcoin.conf to make setup easier)
4) Close Bitcoin Core and wait for the "Bitcoin Core is shutting down..." message to disappear
5) Navigate to the bitcoin data directory (if you don't know where this is look here:https://en.bitcoin.it/wiki/Data_directory)
6) If bitcoin.conf doesn't already exist, create a text file and rename it to bitcoin.conf.  (You may have to show file extensions to make sure you didn't accidentally name the file bitcion.conf.txt.  For windows users follow these steps to show file extensions:http://malektips.com/windows-7-view-file-extensions.html#.U4Dxk1PLfN4 *If you are using a Mac see note below.)
7) Add this code to your bitcoin.conf file:

Code:

bind=127.0.0.1
port=8333
upnp=0
proxy=127.0.0.1:9150

Armory setup:
1) Download and install Armory
2) Open Armory and navigate to File, Settings, Privacy Settings.  Then select "Enable settings for proxies/Tor"
3) Close Armory

Now to run Armory while Bitcoin Core runs through Tor, simply start Tor Browser Bundle, Bitcoin Core, and Armory!

Let me know if you have any questions, or if this setup does not work for you!

WARNING: This setup does not guarantee complete anonymity from Armory, but all external Bitcoin Core traffic should run through Tor.

Edit: Removed Bitcoin Core from the list of programs to run since Bitcoind is automatically run in the background by Armory.
Edit 2: Replaced listen=1 with port=8333 in bitcoin.conf as "port=" serves the same purpose as "listen=" but only listens on port 8333.
Edit 3: Added information involving bitcoin.conf to help Mac users (courtesy of NewBTCGuy).
Edit 4: Changed various instructions to reflect changes in Bitcoin Core and Armory.

*For Mac users:

Answer for those who come after me (thanks to key help from picobit):

The Mac OS text editor is setup to operate with rich text and if one changes the bitcoin file extension to .conf from .rtf it won't change the format of the content.  Thus one must:

1.  Set TextEdit for plain text in the New Document pane of TextEdit preferences AND...
2.  Open the Save dialog, choose Customize Encoding List from the drop-down menu for Plain-Text Encoding, add Western (ASCII) as an option, and choose that option for saving the bitcoin.conf file in Users/<Username>/Library/Application Support/Bitcoin

Here is the scenario, I'm solo mining with bitcoin qt and I manage to mine a block:
To which address do the coins go?  
Is it to one of my existing addresses or to the an address in my keypool?  
If I mine another block will it be sent to the same address?

Is there something wrong with this?    http://testing_1:123@stratum.btcguild.com:3333/

or this?     http://testing_1:123@btcguild.com:3332/

If I'm not inputting the pool info wrong then I have no clue as to why it isn't working.

I can access the internet so that isn't the issue.  I don't know what stratum is so there may be something wrong there, but the second address should have worked if this was the case.

EDIT: Figured out what stratum was and decided to try out cgminer on Linux Mint.

If I put keypool=500 in bitcoin.conf, then are 500 new address created for the keypool?  Or are the existing 100 preserved and 400 added to reach 500?

Questions and thoughts appreciated,
BookLover

From what I've read it seems the devs decided this without a really big community consensus and I wanted to see what the common thought was.  Please post your thoughts and discussion on the miner compensation is encouraged.

upgrade info: http://bitcoin.org/may15.html
compensation info: https://bitcointalk.org/index.php?topic=156641.0

Generally when one sends coins two transactions are made, one to the desired recipient, and one to a "change" address.  For example:

Lets say I have 10 coins in address A.  I send 7 coins to Bob.  Now Bob has 7 coins, address A has zero coins, and I have a "change" address with 3 coins.

So the transaction is signed with A's private key and now everyone knows the private key for address A.  What happens if someone sends 10 more coins to Address A?  Can anyone access the coins in address A now?

Thanks for spending your time reading and hopefully answering this question!

I'm trying to get a Rosewill RNX-G1LX wireless usb adapter to work on BAMT.  I've downloaded and installed both ndiswrapper and ndisgtk because I could not find any linux drivers for this adapter.  I believe I have successfully installed a driver from the CD provided by Rosewill with ndisgtk/ndiswrapper and have restarted networking using "/etc/init.d/networking restart", but when I run "iwlist wlan0 scanning" I get an error message saying interface doesn't support scanning.

I'm not very used to linux and I've hit a wall.  Any suggestions, ideas or thoughts that might help would be greatly appreciated.  

[Edit]  This is a list of more information if you have any questions please post:
When I use the command "lsusb" I see the wireless usb adapter.
When I use the command "iwconfig" I do not see wlan0.  However, before using ndisgtk I did.
BAMT is currently working via ethernet to a windows machine with a Rosewill RNX-G1LX wireless usb adapter installed.

Thanks,
BookLover

Today I unencrypted a wallet to send some BTC but when I booted up the client some of my BTC coins were missing.

Here is the background/technical information:

I had previously used the wallet and not bothered to make a new encrypted backup because I figured I could just use the rescan function.
I only used it two or three times without making a new encrypted backup, so I doubt the key pool ran out.
The version is 0.3.15.4 beta
I did the math on the transactions and it doesn't add up.
The client is on a Windows7 computer.
I didn't create any new addresses.

I have no idea what went wrong and I hope there is a simple answer to this.

P.S. Before you ask I have all the blocks.

I have searched the threads and have not found enough information for to accomplish this.  I already have the BTC client running through TOR, I have a static IP address, and I know where to go to alter settings on my router.  What I don't know is how to configure the router and what to change on TOR and/or the client for this to work  I'm not sure if it is even possible to forward port 8333 through TOR so any input would appreciated.

Thanks for even reading this thread.

BookLover

If this topic is already somewhere else please point me to it, thanks.

      I am running bitcoin server 19 with a couple miners it works great but occasionally the miners say they cannot connect to bitcoin RPC even though the server looks like it is working fine.  When I restart the bitcoin program every works just fine again. What is going on?

P.S. I do NOT restart the miners when I restart the bitcoin server.
P.P.S. This problem occurred my previous bitcoin server as well.


I downloaded the new bitcoin version 3.20 and the glitches stopped.