Turn off auto bitcoind management in File -> Settings. If you can't get there, start Armory in offline mode. Then start BitcoinQt manually (let it sync) and Armory afterwards.

Upgrade to this:

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

Post your logs, use pastebin.

Delete this folder: E:\Files\Digital Currency\databases

and upgrade to this: https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.0.3-testing

Post your full logs. Use pastebin.

You need at least 0.95 to be able to sync a SW aware chain.

You can try to build the testing branch if you want to use the fix right now. Otherwise, sometimes this weekend.

After log file inspection, you will have to wait for new testing build to get the fix.

So your tx still appears as unconfirmed in Armory?

TimR: use pastebin!

What about you use the wallet's properties dialog instead?

Post your logs.

You're trailing over 1000 blocks.

The chain derivation code has not change. SecurePrint encrypts the root key, the derivation code applies on decrypted keys to begin with.

Printing the SecurePrint code is a bit more demanding. You would have to print out the key derivation function code as well as the parameters used and the code providing the initiation vector.

At this rate you are better off dodging SecurePrint and using the fragment backups instead, which just use Shamir's secret sharing to break down the root key into several pieces. You could also grab the raw key, apply some common encryption to it and write down those parameters on the backup (instead of relying on Armory's custom KDF and IV).

Not when it triggers this issue.



I don't know that they are related yet.


Once it's ready and tested. Can't tell you more.

No that means you synced your chain with a super old version of Core and never had to nuke it since. Nothing wrong with that, but the size of the early block files is a tell.


No this means your computer is so weak that you can 100% trigger this issue even on top of a completed build. I've got a VM gimped enough that I ran in the issue every other 5 scans now (I've never managed to reproduce the issue before), so I think I can get it under control. You'll have to wait for testing build with the fix or build it yourself once I push.

You have an old copy of the chain, that explains it. Just start Armory the regular way now, see how that goes.

Are you using a very old copy of the chain? How big are the first blkXXXXX.dat files in your blockchain data folder?

You are short like 5GB worth of block data.

Yes