Topic: Armory - Discussion Thread - page 116. (Read 521829 times)

I can't get Armory to work any more.

It just sits at "99% - Synchronizing with Network - 0 blocks". My log looks like this: http://pastebin.com/PmncB0AB

Ie. these lines just keep repeating in the log:

Make sure you are using the latest 64-bit version of the software available at the downloads page.  If not, make sure you uninstall the old version first, before installing the new version.  Your wallets are safe through an uninstall-reinstall cycle.

I'm working on the "persistent blockchain" stuff that will resolve all these issues.  I have been completely consumed by other important things, so this has been slower than I expected.  But it's top of my priority list, for when I do eventually get enough development time to do it.

Probably you have been hit by some of the data structures used to represent the block chain are now to big to be addressed in a 32-bit application.  You suddently need a 64 bit version of Armory.  That is very unfortunate, and unfortunately only one of many problems caused by the exploding size of the block chain.

I haven't opened armory for a while because I use bitcoin qt for day to day use. Now I was going to transfer funds to my qt wallet, but I can't connect armory up to the blockchain. It scans the chain for 5-10 minutes, then I get a runtime error from windows, and it shuts down. Anyone have a clue what might be the problem?

Sorry CanadianGuy,

I'm super overwhelmed with things, I think I will have time to return to being more responsive soon.   My apologies. 

It sounds like there is a bug.  Perhaps someone who has this problem, who isn't so concerned about the privacy, could make a watching-only copy of their wallet for me, so that I could catch the select-coins bug in a debugger.  This would help me find the problem, because I've never actually had this happen to me before.

For now, you might consider moving the coins in a couple transactions, perhaps 0.5 BTC each.  I don't know if there's a specific input that is a problem, or if it's just the overall size (in kB) of the resulting tx.    You'll pay a few extra cents in tx fees, but at least you'll get access to those coins...

Even better.

olkay this is getting frustrating.  answer me please

well, you can put "onlynet=tor" also in the config...

You're going to need a bitcoin.conf file in order for Armory to be able to talk to Bitcoin-Qt.

If you want to use Armory and Bitcoin-Qt completely anonymously via Tor here is how I'd set it up:

1. Open Bitcoin-Qt, set it use your Tor proxy, then shutdown Bitcoin-Qt.

2. Configure Tor to create a hidden service that forwards to 127.0.0.1:8333 (Assuming you're running Tor on the same machine). Note the hidden service hostname.

3. Find the directory that contains peers.dat and wallet.dat. Delete peers.dat

4. In this same directory create a bitcoin.conf file with the following contents:


5. Start Bitcoin-Qt with the "-onlynet=tor" command line option.

In this way you will only connect to hidden services and Armory will be able to communicate with Bitcoin-Qt.

awesome job man

Yes, but when it starts up it still won't show the balance or transactions of my wallet.

There is an option in Armory called "Skip online check". Are you using that?

Just QT

Do you use Armory with bitcoind or bitcoin-qt? If bitcoin-qt: Both at the same time?

Ente

You'll need to play around with the configurations a bit for everything to work with proxies: I think I had to add "listen=1" to my bitcoin.conf for armory to be able to connect to it again.

This bug is still a problem, and this has not yet been responded to.  I have 1.5 bitcoins that are spread into such tiny chunks amongst about a hundred keys that I can't access them with one transfer. 

I like to run Bitcoin-QT through Tor. But I can't operate Armory when QT has Tor running. So, I have to open QT, disable Tor proxy, restart it, then I can use Armory. Is there a better way to do this?

All these proposals lack to use carry-overs. In all professionel bookkeeping this is the ALWAYS used, QUITE EASY way to avoid ALL size problems:

https://bitcointalksearch.org/topic/m.2307474

BTC in its present state and DB structure certainly cannot be helped by workarounds of bloody beginners knowing not even the basics of financial management.

Btw. since this is the Armory Thread: The dev of Armory (etotheipi) also has a proposal to overcome some of the blockchain-storage-limits (https://bitcointalksearch.org/topic/ultimate-blockchain-compression-w-trust-free-lite-nodes-88208).
An implementation for current bitcoin is in work here: https://bitcointalksearch.org/topic/fundraising-finish-ultimate-blockchain-compression-204283
A similiar idea for a new blockchain is also in work here: https://bitcointalksearch.org/topic/white-paper-purely-p2p-crypto-currency-with-finite-mini-blockchain-195275

@K1773R: You are right. sorry for that.

@Chrisrico: Just to download and store 9GB of data might be very easy for you, as you probably have high speed broadband internet access with a very nice computer. Good for you. Now go back to the use case of money transfers where immigrants will send money back home. IMHO money transfers are at the moment one of the very few REAL economic uses of Bitcoins, besides hoarding.

If you go to China, Korea, Brazil, Africa, Middle East, India you will discover that the ability to download 9GB of data through a mobile network (yes, decent fixed networks do hardly exist in these parts of the world) will cost at around US$40/month. In these countries we often talk about a month salary. The remittance market is huge, massively under served by good solutions and extremely expensive to use. Bitcoin (or things like ripple or open transaction ) is well positioned to take over the role of Moneygram, Hawala systems, banks and Western Union). However, it needs to be cheap and designed in such a way it is extremely resource efficient (energy, memory, storage, bandwidth).

Ignoring the problem because you are not affected by it is not the right approach: Think customer!!!!

I know it is extremely challenging for the current generation of coders to write programs in a low-memory footprint environment. However, if we really want to bring Bitcoin in mainstream area, we should have a light-weight Armory client.