The only way to have Armory working with Tor is to have listen=1 on bitcoin.conf, or to start bitcoin with the -listen=1 argument, right?
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.
|
|
|
|
apparently you havent understood my issue , since i have to be able to have armory autodetect the already running bitcoin-qt.exe in order for it to be able to connect over tor since armory uses the connection from the bitcoin core client that way , and setting it in armorys settings to let armory run it in the background it uses its own process , completely ignoring my bitcoin client settings aka not using the proxy settings in bitcoin core aka not using tors connection
if you dont believe me go and try this>
download tor browser bundle latest , got to settings in tor bundle and go to preferences by clicking on the tor button , then select the custom proxy settings , then enter as SOCKS host this 127.0.0.1 and enter 9150 in port and select socks v5
then go to your bitcoin core settings and do as following > go to network and select connect through socks proxy and enter above settings and you got it all setup to only connect whenever your running tor , wich in turn would have armory only connect through tor as well since it would then be properly using the available instance of bitcoin-qt.exe , thats if it would work as it has , but as of latest build of bitcoin core be it 32bit or 64bit dont matter and armory its broken wich needs to be fixed this is an crucial security and anonymity issue and i wont be able to use armory , hell i wont be able to manage my bitcoins at all until then since armory is the only secure software i trust to manage my bitcoins
Are you saying your setup worked with older versions of Armory? Bitcoin Core's arch build is irrelevant here. Im going to speculate since you didn't give me your settings specifics. 1) Ima assume you have turn off auto manage bitcoind in Armory, and that Armory just shows offline. If as you seem to pretend, Armory is just running its own instance of bitcoind, that setting is on and you need to turn it off. 2) Ima assume you have pointed Armory at Bitcoin's datadir folder through the --satoshi-datadir switch, or that you let BitcoinQt create that folder in its default location. 3) Ima assume you're not trying to run Armory in testnet while BitcoinQt is running on the mainnet, or vice versa. 4) Ima assume you turned off the torrent and "check online" options in File -> Settings 5) Ima assume you have a custom bitcoin.conf 6) Ima assume you commented the announcement code out of ArmoryQt.py, seeing that you don't want any of your traffic going through something else than Tor. If all these assumptions hold true and Armory is showing offline, then add this line to your bitcoin.conf: addnode=127.0.0.1 Restart BitcoinQt and let me know. |
|
|
|
|
You can force the Bitcoin core installation path, going to File -> Settings
|
|
|
|
You're probably building the master branch, which doesn't have the changes made to the cryptopp makefile. |
|
|
|
I have an Armory USB stick. I think I got it at the San Jose Bitcoin Conference in 2013. It's 256 MB. Is it live? I thought it was just a blank drive.
We came up with the live image a day before the 2014 NYC conference. We were showcasing it there and passed a few copies for people to test out. The maintainer is out on a vacation currently, he'll be back soon to polish the image, which will then be signed and available through Armory's download system. |
|
|
|
Hi, i had the same problem before and ended up building 0.90 from the source on the Pi  This new version seems to work, at least it starts without problem and shows the same wallets as before. (I just started/ended it on the Pi, nothing more) Hope this helps. You could try something like creating a paperback up of one of your wallets. If it gets that far (unlocking and all) it should be sound for signing. |
|
|
|
|
I think you're confusing a few things.
Armory doesn't download anything per say. It piggy back on BitcoinQt's blockchain download, and builds a database off of it. What you need to copy is the ~/.bitcoin hidden folder.
As for Armory's DB, you can just copy the files and point Armory to the folder, but that won't work in your case, as the 0.91 DB isn't compatible with the 0.90 one.
|
|
|
|
|
I dont think we put out a 0.91 RPi package yet. The debian/ubuntu packages certainly won't run on a Pi, different CPU arch.
|
|
|
|
Ok perfect will have a look into it.
Have you already some date in prevision when to start with revision of armoryd?
Sorry to say but there are 2 items in front of armoryd on the priority list currently. CircusPeanut, who maintains armoryd, is going over our unit tests right now so he won't be dealing with it yet. The other priority is multisig, and it makes sense for us to first polish multisig and p2sh, then fix armoryd, and add multisig support with it. |
|
|
|
|
Try the --nospendzeroconfchange switch to prevent that. Otherwise check the amount on of confirmations the transactions has, or the block it was mined in.
|
|
|
|
goatpig's the real deal.  I can't thank him enough for sorting this all out and recovering my addresses. The forethought and thoroughness that has gone into Armory's design is incredible. Happy to hear this is over. Thanks for the tip =P |
|
|
|
|
This shouldn't happen. Your backups protect your keys so no need to panic. Submit a ticket linking to this thread, we'll get you through this.
|
|
|
|
|
Does BitcoinQt starts? Does it fully sync?
If Armory refuses to start, start it in offline mode, go to Help -> Rebuild and Rescan Databases, then restart it without --offline
|
|
|
|
I just updated to Armory 0.91 on OS X Mavericks 10.9.2 and got the same error right after opening Armory.
"Wallet Corruption Found!!!"
Now it's scanning the blockchain, only then can I try to 'fix the wallet'.
Im taking care of mcippolito's wallet. Make a ticket for yours. |
|
|
|
Thanks that was just the trick its working perfectly now.
I was wondering if updating the bitcoin-qt caused this as it seemed to work fine before i did that. Or is it just good practice to rebuild the database after an undate of either bitcoin or armoury? Or maybe it was something else i did around the same time that threw everything off......
Away it working fine now. Thanks soo much!
Not necessarely. The previous release (0.90) was the first version using LevelDB as our background engine for the DB. In this release (0.91) we tweaked LevelDB's settings to squeeze some extra speed. This is what made the older DBs incompatible with the newer ones. Chances are we won't touch these settings again, or at least not in the near future. |
|
|
|
|
Take it easy with this for now.
We're pretty confident it'll work but its still under testing, as it was finished right before the conference.
We should release a stable, signed version in a couple weeks, that you'll be able to grab off of the website or from Armory's downloader.
|
|
|
|
|
Looks like you got the live USB stick. Try to boot from that USB, it should take you to a stripped down live Debian with an Armory install.
|
|
|
|
Yes i get to see the GUI, and its appears to crash towards the end of the scan about 93%. And yes i can use it in offline mode.
In both offline and normal mode my wallet balance is blank - is this normal until its completed the download of the block chain?
it used to work fine and it was around the time i upgrade to bitcoin 0.9. so i downgraded which didnt help, also tried reinstalling both bitcoin and armory, and the runtime c++ library files. bitcoin is x64 - also tried the x86 build of bitcoin no joy.
EDIT:: it crashes at 95%
First thing to do is to rebuild the database. Go to help -> Rebuild and Rescan Databases In offline mode you will never see your balance. You dont get to see your balance when trying to get online because it never finishes loading. If deleting the DB doesnt get you any further, create a ticket. |
|
|
|
|
Show Posts
