Hi goatpig,

I am running the test build on Win7 with a HDD for both core and armory. 11.2, 93.3.999.

The hard drive isnt a powerful one so the scan and build took 3178.56 sec. The scan was concerning at first because it kept updating at 31%, 63% 95% and then starting over at 0%. According to the log file this must of happened when the blockchainScanner scanned from intermediate heights. (Eg. #397557 to #398370, #398371 to #399115, etc, etc)

Now i have run into problems with viewing previous transactions. (Mainnet). Receiving transactions no longer contain the sending addresses or any info about that. Sending transactions error out unless the transaction was sent with change or sent to another armory wallet. The GUI error states:
"Invalid Tx. The transaction you requested be displayed does not exist in Armory's database. This is unusual..." According to the log: \lmdb_wrapper.cpp:707  txhash is less than 4 bytes long.

I have yet to test sending or receiving and coins yet, but this is what i have encountered so far.

Hi goatpig,

I'm concerned about the ability to just simply change the license for the program. I believe that if you still use parts of the old Armory under the AGPL3 that forces you to release your program under the AGPL3.

I'm not a lawyer but what frightens me is that if the "powers that be" of Armory couldn't/wouldn't allow you to use the 0.94 code, I don't have a lot of faith that they might not allow you to continue to work on the program under a different license.

I want Armory to continue, and I would not like to see your work shutdown/removed/destroyed by the copyright holders. Admittedly if they couldn't get the rights to the program for the community before this shut down, they probably wont easily be able to claim a copyright violation.

I don't know how Armory (the company) is structured, but maybe you can see if they will give you the right to license the program differently that doesn't force this AGPL3 upon you.

Its very saddening to hear from Alan about Armory taking this turn. I know the work that Alan, you, knightDK, (and all of the testers and others idk off the top of my head currently) has been fantastic and hope to keep seeing great things from all including the community.

Hey Armory folks,

In my occasional view of both bitcoin core and armory's code, I noticed that a recent commit to armory's ffreeze branch that put it in a gitian branch. I'm curious if this means that we are getting close to getting pre-built test builds of 0.94?

Thanks goatpig!

Ive already clicked receive bitcoins enough to catchup, but if it happens again i will try that.

Thanks again!

Hi All,

So I have 2 Watching only Armory sessions. (On different computers) One I use as my primary online session, the other is used, just to watch my balances from work. The one that does all the interactions with the actual cold-storage system works just fine. The other one while showing the correct updated balances does not automatically list the addresses that are used for the total balances. In order for me to see those address i have to keep clicking Receive Bitcoins, until I get to the addresses that are up to date. The wallet has already pre-computed enough addresses that it should show them in the wallet.

I don't know if this is a bug or just something that's not programed to happen.

I'm using Bitcoin Core 0.10 and Armory 0.93

On a side note, I love version 93 beta. It loads up so fast that sometimes I'm concerned it even did anything. Great job devs!

I was wondering if it would be possible for armory to show the previous balance of a wallet in the transaction history. So for every transaction it could show what the balance of the wallet was at the time the transaction took place. It would help me with accounting and me not having to manually do the math to calculate it. (Yeah I'm lazy like that)

On another note, I have been using Armory for about a year now and I love it. Other than the annoyance of having to double the storage requirement for a full node, I have had no issues and have felt that my bitcoins are useable and safe.