The new DB is about ready. It passes all C++ tests and runs *almost* fine. Turns out my own copy of the mainnet blockchain has a corrupt block (or at least some corner case that displays the same behavior), so I'll be taking extra time putting together a full diagnostic and repair code to get through that bad block. In the mean time I'd like some testing on what I have so far.

Haven't hooked the progress bars yet (so refer to your terminal/console output) but the rest should work (spends and ZC included). The code is in dev (https://github.com/goatpig/BitcoinArmory/tree/dev), pull away. I'm still pushing commits daily to that branch for now. Once it stabilizes and I put out the first testing builds, I'll move that code to a branch named testing.

If your scan fails please repeat and let me know if the error is random or deterministic.

EDIT: haven't tested rebuilds/rescans, they are probably broken. Delete the content of your DB folder manually if you want to rebuild. Obviously use a new folder (this db format is not compatible with ATI's 0.93/0.94 and coexist with it in the same folder). Expected DB size for mainnet is ~150MB.

Start Armory in offline mode with another datadir (--offline --datadir="someotherpath")

Go to Wallets -> Fix Damaged Wallets

Start with a consistency check and post the logs here.

disable auto bitcoind management.

I'll compare yours to what is in there already and take a decision. Only need one instruction file per OS, the rest I'll delete.

force your block file location using --satoshi-datadir

I won't accept a PR that has anything to do with Joseph's work for ATI until I can clear that with the shareholders first. Do not keep your hopes up. Use Joseph's work as reference as much as you'd like though.

For people interested in adding deterministic build support for Armory, please focus on a single Linux distro at first (ideally Debian 7 or 8 ).

For Linux packages, run this python script:

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

For Windows, run this .bat:

https://github.com/goatpig/BitcoinArmory/blob/master/cppForSwig/BitcoinArmory_SwigDLL/build_installer_64.bat

For OSX, it's one of these here:

https://github.com/goatpig/BitcoinArmory/tree/master/osxbuild

yes

I'll look into getting mod status once I go into the whole release/website dance. For now, I want to focus on coding. At the current rate, I could have a testing phase this week.

Since LevelDB and LMDB are unaware of each other, both DBs can coexist in the same folder. There was some extra checks in place to look for an old DB, but it was also possible to just click through it, so he could have 2 DBs in one folder. Otherwise, he rebuilt the DB so much it eventually bloated, i.e. it doesn't have actually 147GB of data, rather the premapped files are bloated up to that value.

AGPL3 is still an open source license. You can develop code on top of AGPL3 code, use any license you want that is compatible with AGPL3 (Boost isn't as an example, MIT is), and retain full ownership of your own work.

What you can't do is use AGPL3 licensed code commercially without a license issued from the owner. In the case of Armory, if someone wanted to use my version of Armory for commercial purposes, they need not ask my permission (my additions are MIT), but they will have to seek licensing from ATI (all their code is AGPL3).

ATI can't sue me because I am developing on top of their code base. The MIT license is compatible with AGPL3 after all. ATI can't sue me either if someone was to use my version of Armory commercially. They would have to sue the particular user/business who didn't get a license from them, and I am attaching ATI's AGPL3 text where due in my code (can't blame me for lying about the copyright).

In your /blocks folder, delete the last ~10 or so blkXXXXX.dat and revXXXXX.dat files. Start BitcoinQt, it will complain about that stuff, redownload the missing data and reverify the chain. (If you want to reduce the verification time, maybe it's a good occasion to try out Core 0.12 rc?)

Once BitcoinQt is fully sync'd, you can shut it down and start Armory as usual.

-ERROR - 1455537157: (BlockWriteBatcher.cpp:980) No block in DB at height 195803
-INFO  - 1455537160: (BlockUtils.cpp:1518) Scanned Block range in 411.828s

That's your error. Your copy of the blockchain is corrupt, you need to redownload it.

Indeed, no dedicated mods to this sub. I believe that leaves gmax in charge. Alan asked for moderator status some years ago and it never got to anything, so he gave up. Not sure if I want to go down that path too. I'm perfectly fine with an active member of the community getting mod status in this sub.

Again these log lines are irrelevant. You should clean up your armorycpplog.txt or all personal info and pastebin it so I can look at it. In the mean time, delete the content of Armory's database folder and try again.

Yes. I suggest once you get a functional one to back it up somewhere, so that you can pick up from that state if the issue happens later. I have some extra changes in the upcoming version that could get around those issues (no guarantees though).

I don't have moderator power in this sub forum. Afaik no Armory employee ever had.

None of these lines are relevant to your issue. You should start BitcoinQt manually and let it fully sync. In Armory, turn off auto bitcoind management then start it after BitcoinQt. Report what happens here.

Your blockchain data is corrupt.