First of all, download the latest Bitcoin Core, let it sync in full. Next, don't PM me over basic support.

Your coins are fine, your issue is that you have not properly synchronized Armory with the Bitcoin network. Armory can't show you your up-to-date transaction history without looking at the up-to-date blockchain.

make install installs to $(DESTDIR)$(PREFIX):

https://github.com/goatpig/BitcoinArmory/blob/testing/Makefile.am#L39

For info, $(DESTDIR) is empty, only $(PREFIX) has anything in it, which defaults to /usr/local

You could either set a DESTDIR or use a custom PREFIX during ./configure and build yourself.

If you insist on having a built package that fits your setup, I would consider doing that for the gcc4.7 build, but you'd have to research how to force the different install path with dh-make (which calls ./configure each run). This is the script used to package .deb:

https://github.com/goatpig/BitcoinArmory/blob/testing/dpkgfiles/make_deb_package.py

Ask droak about OSX ailments. 0.93 tx are fine.

0.93's database is not compatible with 0.95's. Either delete it or use a different dbdir.

Looks something like this:


0.96 can create transactions for the previous bracket as long as the UTXOs are for the right script type.

ugh this is supposed to work... I'll try one more thing to get the deb going. What's your CPU on that machine btw?

Try the .deb

Can you try the .3 gcc4.7 deb on a Ubuntu machine?

What worked? The .deb, the txsigcollect, or both?

I'm not telling you to install an older GCC, I'm telling you to try the 0.95.99.3 gcc4.7 testing build.


Fixed on 0.95.99.3. You need it on your online machine to create proper txsigcollect packets.

3rd testing build has the fix for the txsigcollet issue. I was assuming you were using that.

You can get the gcc4.7 build in the usual place:

https://github.com/goatpig/BitcoinArmory/releases/tag/v0.95.99.3-testing

1) What is the signer's version?

2) The .deb packages work, I got no idea what kind of Ubuntu you are using that it can't get them to run. Try the gcc4.7 I made just in case you are using some weird distro.

On your low RAM machine, you should use:


On your other machine, you shouldn't need any of these extra settings at all. If it's still failing to build & scan, use DB_BARE. DB_BARE is an initialization setting, you can't swap it around after the DB has been created. Once you create a DB_BARE db, that setting will stick for the db's lifetime, so manage it accordingly.

The fact that your machines require DB_BARE suggests some sort of system instability (by default the build phase will max out your CPU).


Plenty changed, courtesy of autotools. All binaries now go to /usr/local/bin, libs and python code files go to /usr/local/lib/armory. Desktop files still go to /usr/share/applications. The .deb does not distribute CPP code files anymore.

You can try the 0.96 testing builds with it, should be fine.

Add this line to the .conf:


Then start from the top.

How much RAM do you have? If you have less than 8GB, also add ram-usage=1

Don't run ArmoryQt with the arg. Just run ArmoryDB with the arg, then run the client on its own. It will find the db.

First, delete the databases folder again. Then, in F:\Armory, create a armorydb.conf text file. Fill it with this:


Save and close, then run:


Then in another cmd prompt, run the client (while the DB is still running):



dbLog.txt in your datadir.

Don't run auto bitcoind if your setup isn't stable. Run BitcoinQt and make sure it's sync'd before running anything else. The fact that it's eating 40% CPU implies it's not done syncing.

That's what I hope to reveal


Not yet, I wanna see what's messed with it.

Are you using the same block file data on the Windows machine than on the Ubuntu one?


Delete the database and try again from the top with --thread-count=1. Does it always fail at the same spot now?