Did someone answer your ticket? Cause I cant find it.

Most likely BitcoinQt is updating the blockchain in another folder than the one Armory is pointed at.

On Armory's end? What version are you running?

Search for that txhash on blockchain.info

If you can find that transaction with 0 conf, then you just have to wait for it to be mined. If you cant see it, then BitcoinQt never relayed it for some reason. Clear your mempool and resend the coins.

--satoshi-port=9150

wrong port


Not sure what you mean by that

Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe

Obvisouly Armory isnt getting the command line switches. Are you starting Armory from that shortcut?

This is a trivial error, only a symptom of the real issue. Submit a ticket with a full log.

-maxconnections=8
-addnode=127.0.0.1

you are getting the switches all wrong...

--satoshi-datadir="*pathtomyblockchainfolder*" --satoshi-port=*mycustomport*

no parenthesis, spaces between each commands

delete this folder: /home/aditya/.armory/databases

I dont even know why I wrote something that stupid. it's --satoshi-port=8331 in the shortcut target, then start Armory from the shortcut.

Your problem is 2 fold. Connecting BitcoinQt to Tor and connecting Armory to Tor are in a sense separate yet connected issues. Setting BitcoinQt to connect through Tor will break Armory's connectivity, but getting BitcoinQt to connect through Tor is unrelated to Armory.


That doesnt mean Armory is necessarily looking at this folder. You may wanna try and force it through the --satoshi-datadir switch.

Did you send a log file? At this point I would like to look at one. Sorry if you already sent one and I missed it, kinda slammed lately.

Is your Tor router port 9051? Can you get BitcoinQt to connect through that? What folder is your copy of the blockchain in? It sounds to me like this is the issue.

Armory will show offline if one of these 2 requirements isn't met:

1) Connect to a Bitcoin Node on 127.0.0.1 and the port defined by --satoshi-port (8333) by default
2) Be pointed at a folder with a copy of the raw blockchain data, as produced by BitcoinQt. This folder is set by the --satoshi-datadir switch, and defaults to C:\Users\*currentuser*\AppData\Roaming\Bitcoin\blocks in Windows

Im curious if your issue isn't 2) rather than 1)

bitcoin.conf in Armory's datadir? That won't help you.

For Armory, create a shortcut, go the to shortcut properties and at the end of the 'target' input box add --satoshi-port=8331, then start from that shortcut.

Also block all traffic to that port in firewall settings.


I'm pretty sure I said Whonix cause it requires installation, which means persistence, so you can change the settings to fit your use case.

I dont know the range of connections listen=1 allows. Changing the default port and blocking all external traffic to it takes care of potential surprises.

Testing that now actually.

Armory doesnt verify the blocks it reads, it trusts Bitcoin Core to do that. Ill let you imagine how nasty that can get when an attacker gets to connect to your instance of Armory as its "good" node.

Got it work in a somewhat acceptable setting.

This is my bitcoin.conf:

proxy=127.0.0.1:9050
listen=1
port=8331

My Tor is set to run its proxy on 9050 by default.
8331 is a port I chose for Armory to connect to. Armory has to run with the --satoshi-port=8331 switch.

In my firewall, I added a rule to block all network traffic to port 8331. This way only localhost can connect to a socket listening on that port. This seems to work fine. Observing bitcoin, it only connects to nodes through the Tor proxy besides Armory, locally.

Do not use this port. You are letting Armory connect through the Tor proxy. That's bad, Armory could possibly connect to an outside node this way, and this is what I think you are seeing with the massive disconnect.

I'm busy right now but I'll setup the Tor proxy later tonight and figure out a proper setting.

I thought OSX has issues with command line arguments. Add it to the .conf and get back to me.

Also, why :9150? Is this your personal setting? If so you have to set Armory to use that port too.

addnode=127.0.0.1 will make bitcoind try to connect to Armory, which is what you want, and not more. listen=1 is more aggressive than necessary.

1) Copy and paste your bitcoin.conf content in here

2) Armory needs 2 things: To find a running instance of Bitcoin locally (on 127.0.0.1:8333) that it can connect to) and to be pointed at the folder where the blockchain is saved. Now I need a logfile to assert that. Make a ticket, attach the log and point at your post.

3) If you dont know it means you didnt mess with it.

4&6) Armory connects to Bitcoin locally and to our own servers for updates and announcements. This has been the case since... hell I dont remember but its been there alright. Look at your log file and watch all those connections to google.com and our s3 server. At this rate it would be simpler to install Whonix than go through all this pain. If you dont have any coding experience you're gonna have a hard time turning off all side channel in the from source. This isnt related to your issue btw, just assuming you want all that side channel stuff off or going through Tor.

5) Same as 1)

Also, you should be able to put all your settings in the bitcoin.conf file and let Armory auto manage it, but that's besides the point. Using 64 vs 32bit BitcoinQt has nothing to do with this, this is simply a setting issue. Give me the information I need and I'll sort it out.

Again consider using Whonix or that Tails + Armory attempt found somewhere on this sub section.

Something I forgot to answer: We dont put out a 64bit Windows version anymore because we dont need to. When Armory needed tons of RAM it had to be 64 bit. Now it doesn't anymore so we don't bother in a sense. The 32 bit version runs on every supported Windows, make our life easier.