Topic: RAM-Reduction & Backup Center Testing (version 0.89.99.16) - page 5. (Read 41311 times)

POSTED SIGNED INSTALLERS:

https://bitcoinarmory.com/download/

Since the installers are now posted on the official website, I decided I should go through the effort of offline-signing everything, even though it's not the final release.    You can download the SHA256 hashes file here (now with a note to reduce confusion about which hash function to use):

https://s3.amazonaws.com/bitcoinarmory-releases/armory_sha256sum_hashes_0.89.99.14.txt.asc

Note that the .deb files changed hashes since yesterday, because I took the liberty to GPG-sign (using dpkg-sig) the .deb files.  You can use "dpkg-sig --verify *.deb" to check them.  If the signature is good, you don't need to mess with the hashes file.

Re: (2) I think it might be related to freshness of outputs: it may only happen when you are spending outputs that were just received a few confirmations ago.  And I think only without a restart between receiving and spending.

When I was able to reproduce it all of the outputs that I was working with were old.

Also, I reproduced the bug, on the first try, but then I had trouble making it happen again.

Please help me find the disappearing-tx bug!  
I'll give 0.2 BTC to someone who finds the pattern!

I need your help with this one!  I'm going insane trying to figure out the pattern behind this bug.  90% of my tx go through fine.  It seems to only happen when I'm not paying attention.  

Symptoms:

(1) Transaction is created and broadcast
(2) Tx shows up in ledger/history with zero-confirmations, wallet balance is reduced
(3) As soon as the tx is included in a block, the tx disappears completely.  Wallet balance returns to previous value, as if the tx never happened
(4) Restarting Armory doesn't help.  The only way to fix/find it is to do a rescan ("Help"->"Rescan Databases").


What I know about this bug:

(1) I'm fairly certain that the bug only occurs when the transaction has no outputs to any of your wallets.  Every time I've triggered it, has been with a tx that has a single output to an external address (i.e. the target address is not in any of your wallets, and there is no change output).  I suspect the number of inputs doesn't matter, but I think I've only seen it when there was a single input as well.

(2) I think it might be related to freshness of outputs: it may only happen when you are spending outputs that were just received a few confirmations ago.  And I think only without a restart between receiving and spending.

(3) It definitely happened before on a run where I did a rescan.  It may have to do with fresh-rescan-on-load vs read-stored-histories-from-last-load (but I'm somewhat certain this is not a requirement to trigger the bug).

(4) The fee does not appear to matter (seen it with

In order to test this, knowing that you need perfect-sized inputs, you'll need to use coin-control.  Deselect all but one address in the coin-control window, then use the "MAX" button to send the entire input to an external address not part of any of your wallets.  When the tx is in your ledger, you can double click on it to verify that there is only a single output and a blank in the "Wallet ID" column.

This is the last major bug that needs to be fixed before I can do a release.   Once I find a pattern and can reproduce it reliably, I can debug it and verify it's fixed.  Right now I can't reproduce or verify.  Tell me the pattern and you get 0.1 BTC!

P.S. if you want to run Armory on testnet, see the instructions here:  https://bitcointalksearch.org/topic/running-armory-on-testnet-341252

im getting stuck @ 77% scanning transaction history....

I just got around to trying out your Win XP build and it works! Thanks for your hard work mate.

Thanks for the testing guys =) Keep it up =P

runs fine for me on win xp 32-bit and a very vanilla win 7.  both are syncing/building db.  will report if anything comes up, but looks great!!

You can change your shortcut to point to your blockchain and where you want the database to be kept:
"C:\Program Files (x86)\Armory-testing\ArmoryQt.exe" --satoshi-datadir=I:\bitcoin --datadir=I:\armory

This one seems to be working on my production XP computer. It runs. Version 0.89.99.8-beta according to the about page.

I will test again on my other bare-bones XP laptop.

Now, all I need is to wait for importing and using compressed private keys.

Since Armory doesn't save any registry settings, there's not a good way to signal to it that you want to change your --datadir.   If you move your --datadir, there's no way for Armory to know where it is when you start it.   The only way to do it is really to modify the shortcut as you did.  Technically, all other options could be put in a armory.conf file in the Armory --datadir, but haven't gotten to that yet.  Similarly, I could just write a registry setting for Windows.  Meh.

Armory works great for me on Windows 7 64-bit. I did encounter a nuisance though: If Bitcoin-QT isn't installed in the C:\Program Files\, Armory had trouble locating it. I tried to give the correct location in settings, though that didn't seem to work. I also found it difficult to remove the blockchain from my C drive as Armory keeps it's own copy there (which is a problem when working from an SSD with limited space). The solution was to open command prompt and make symbolic links for both Armory and Bitcoin, though it would have been easier if this could be done from settings.

This might add some complexity to the release process, but can you start bundling bitcoind with the OSX version of Armory, since they don't have any other way of getting a precompiled version?

Reinstalled Armory. OS: Win7 64bit.


I was wrong. I see that i am connected but 0 blocks.

Where can i find an earlier version? 0.89.99.8 was just much better for me

Edit: Forgot OS!

Second Edit: Ok now final version works ok if i run bitcoin-qt client! Finally!

Reinstalled bitcoind or Armory? OS?

Nobody else having the issue that i have? I even reinstalled and still the same problem.

And we have a winner! Armory now runs on my XP system also! Thanks Goatpig! Here I come cold wallets!

Thanks for testing guys. Need a few more tests plz, Win7+ as well =)

Just as a suggestion, it might be a good idea to not have the root key bolded in print backup for clarity or possible ink spillage. Or perhaps allow it to be customisable?

I have installed the latest version 0.89.99.14 over my existing one 0.89.99.8 and now it just can't find my bitcoin installation. Double checked settings and everything seems ok. Suggestions?

Edit: I ran it with default settings(meaning that i'm running the bitcoin-qt client) seems to work just fine so there must be a problem with the "Let Armory run Bitcoin-Qt in the background"
And the loading time now just rock! Great job!

I did. Sadly, same results. Immediate crash. OS X 10.7.5