Honestly I'm not sure who came up with the idea of HD wallets first. In other ecosystems that require cryptographic material management (think CAs, DNS providers), it is common practice to create one root piece of secure material offline and derive lower schedule keys from that. With this in mind, you can't argue the use of HD wallets in the Bitcoin space is actually a novel invention, as there is prior art in other spheres, even though there was the need for some engineering to suit our use case.

Therefor, with the previous paragraph in mind, while I cannot tell you with certitude who brought the idea of HD wallets to Bitcoin first, I suspect it was floating in many devs mind if not yet in the mailing list, since the practice has been common place in other industries.

The only thing I know for sure is that Armory was the first implementation of this idea in the Bitcoin ecosystem. From what I know, it was ultimately Alan's solo take on the underlying principle. Bitcoin devs with sipa in the lead improved on it to birth BIP32 about a year later (give or take).

There's a better GUI option in the upcoming version. For now the best way for pathing is to use config files: https://btcarmory.com/docs/pathing

AFAIK, Armory introduced hierarchical deterministic wallets to the ecosystem. This in turn inspired BIP32 which improved the design while standardizing the feature.

Delete dbLog.txt and you databases folder. Start ArmoryDB.exe from the command line, then start ArmoryQt.py. Do not run BitcoinQt during this. If it fails, post the fresh dbLog.txt

That's dated stuff, removed that feature some time around 2015 because it hurts privacy. You can get the latest Core from bitcoin.org (not bitcoin.com, that's a scam).

It's hard to know where the issue originates from. Some of it could be poor resource management in multithreaded tasks on Armory's end, and some from LevelDB corruption at shutdown in Core. Both these issues have largely improved in later versions, but since he is using 0.96, I'm guessing he is also carrying a copy of the blockchain at least partly generated by some older version of Core. Therefor there's just no way to know who's the culprit, and isolating one potential source by upgrading Armory is the only sane way to get any clarity.

Chances are the shutdown error comes from 0.96 use of deprecated Core RPC calls (that interface received some changes this year). I'm treating it as a false positive for now.

Update Armory, delete the content of your databases folder (C:\Users\Frank\AppData\Roaming\Armory\databases) and try again.

Delete it if it gets past 2MB

What's the sync status on BitcoinQt?

It says your top block is #364461 and that your node sync is 20.2311%. You need to start BitcoinQt manually, let it sync all the way, delete the content of your databases folder (C:\Users\User\AppData\Roaming\Armory\databases) then you can start Armory.

This is a bug that opens for a chainsplit attack. It doesn't have anything to with integrity of block serialization on disk. The kind of issue it would create had this bug ever been exploited would be obvious in the db log.



His log says 0.17

I wrote this code. You want my help, you follow my instructions. Otherwise, good luck.

1) Delete the content of this folder: C:\Users\microsoft\AppData\Roaming\Armory\databases (only the content, not the folder itself)

2) In your Armory datadir folder (C:\Users\microsoft\AppData\Roaming\Armory\), create a file named armorydb.conf and put this in it:


3) Make sure neither ArmoryQt nor BitcoinQt are running, then start ArmoryDB.exe from the command line.

4) After starting ArmoryDB, start ArmoryQt.

Let it run all it can. If it fails, post dbLog again.

Post dblog.txt

post dbLog.txt

Download the depencencies and their dependencies from the repo yourself. There are plenty of guides in the wild for how to rip the list of dependencies with a simple script. You can then install those on your offline machine using dpkg -i

You need to elaborate

I see Chinese in your Core log. Are there non ASCII characters in your Armory data paths?

Start ArmoryDB.exe manually, post the log here.

Database isn't running at all