|
Title: Added specific 'connect' peers (not addnode), now armory doesn't launch Post by: Automatic on January 25, 2014, 12:35:54 PM Long story short, I added two nodes I 100% trust to relay my bitcoin traffic for me (They're both on 24/7), like so:-
https://i.imgur.com/WQTESrW.png But, now Armory gets stuck at 0 blocks, it manages to sync up from however many blocks it was back by (E.G., if it I was 55 blocks behind, it syncs to 0, then hangs):- https://i.imgur.com/DG0wW87.png Launching Bitcoin-QT manually works fine:- https://i.imgur.com/ggj74r9.png And help with why Armory refuses to go onto step 2? EDIT:- Reason why I want to relay my traffic is I've noticed that my legitimate IP address seems to be attached to all of my transactions on blockchain.info, I could firewall blockchain.info, but, then I'm sure there's other companies that also log data like that. I'd prefer just to relay it through someone who I'm sure isn't publicly logging me. I know I could relay it through tor (or any other sock proxy), but, I care less about my anonymity (I.E. that everything that goes through those two nodes is me) than I do about people just not having my IP. Title: Re: Added specific 'connect' peers (not addnode), now armory doesn't launch Post by: goatpig on January 25, 2014, 06:58:24 PM scratch that, its bind=127.0.0.1 that you need Title: Re: Added specific 'connect' peers (not addnode), now armory doesn't launch Post by: Automatic on January 25, 2014, 09:12:03 PM scratch that, its bind=127.0.0.1 that you need This solved it, unsure why (As wouldn't it already have to be connected to get the amount of remaining blocks?), but, it did, thank you :-* Title: Re: Added specific 'connect' peers (not addnode), now armory doesn't launch Post by: goatpig on January 25, 2014, 09:44:06 PM There are actually 3 places where Armory gets its data in that regard:
1) The block height is fetched straight from the raw blockchain files 2) Assuming you let Armory manage bitcoind, it will query bitcoind's status through the RPC, mainly for the progress bar. Armory won't use the RPC at all if you manage BitcoinQt yourself. 3) Armory connects as a network node on localhost to your (local, obviously) bitcoin instance to monitor the network and push its transactions. |
