RAM-Reduction & Backup Center Testing (version 0.89.99.16)

[etotheipi]

Ack!  The installer script didn't copy over all the files, whoops!

I'll work on that...

(updated the first post with the old 0.89.99.10 OSX app until I fix that)

Well that was easy.  Just rebuilt 0.89.99.14-testing on OSX with the updated Makefile and re-posted it to the main thread.  Please try it again!

[Allaboutbit]

Ack!  The installer script didn't copy over all the files, whoops!

I'll work on that...

(updated the first post with the old 0.89.99.10 OSX app until I fix that)

Well that was easy.  Just rebuilt 0.89.99.14-testing on OSX with the updated Makefile and re-posted it to the main thread.  Please try it again!

Awesome. Thanks it works perfect now and loads in less than 30 seconds.

[Rampion]

So happy that OSX builds are included by default... Great job Alan, godspeed!!!

[pvz]

Linux 64bit .deb does not start.
Next error after manual start:

Code:

sudo python /usr/lib/armory/ArmoryQt.py %u

(ERROR) Traceback (most recent call last):
  File "/usr/lib/armory/ArmoryQt.py", line 42, in <module>
    from dialogs.toolsDialogs import MessageSigningVerificationDialog
ImportError: No module named dialogs.toolsDialogs

EDIT: same error like reported a few posts earlier.

[etotheipi]

Linux 64bit .deb do not start.
Next error after manual start:

Code:

sudo python /usr/lib/armory/ArmoryQt.py %u

(ERROR) Traceback (most recent call last):
  File "/usr/lib/armory/ArmoryQt.py", line 42, in <module>
    from dialogs.toolsDialogs import MessageSigningVerificationDialog
ImportError: No module named dialogs.toolsDialogs

Argh, same problem as on OSX.  I must've accidentally tested the new version in the development directory instead of through the installer.

Fix coming in 3... 2...

[etotheipi]

Fix coming in 3... 2...

... 1!

Top post links now link to the fixed .deb installers!

[pvz]

Top post links now link to the fixed .deb installers!

Check! Works.
Thanks Alan!

[etotheipi]

New bug-bounty thread!


[BOUNTY] Help test next major release of Armory! [0.04 BTC/bug]

Help me test, make money!  

[els]

Here's a new tentative build to try and get Armory running on Vista and XP.

Disclaimer: This my build (goatpig), not etotheipi's. This is only for testing purpose on older Windows platforms. A lot of optimizations have been taken out in an attempt to achieve a failsafe build, so this will be slow. Starting Armory in offline mode is enough to prove compatibility. Adventurous ones, you may wanna try and build the DB (at your own risk)

https://mega.co.nz/#!0chE2J4C!RoE8WUfmPPqU1HStumsfh3bKGtJPu-toxzRhcM7_zVY

Still not working on XP. Same error message in the log.

(finally got the download to complete and) got the same failure on XP 32-bit as well

[chrisrico]

Wow. This latest version is super fast on Windows 7. Like, 15-30 second startup time fast.

[RoadStress]

New bug-bounty thread!


[BOUNTY] Help test next major release of Armory! [0.04 BTC/bug]

Help me test, make money!  

While i know the risks of using Beta software i just want to be sure of something. Having a paper backup makes me safe from any Armory/wallet problems/bugs/disasters right? Also please tell me how paper wallets work. If i make a paper backup of an encrypted wallet will it require the password when importing the backup or not?

[etotheipi]

New bug-bounty thread!


[BOUNTY] Help test next major release of Armory! [0.04 BTC/bug]

Help me test, make money!  

While i know the risks of using Beta software i just want to be sure of something. Having a paper backup makes me safe from any Armory/wallet problems/bugs/disasters right? Also please tell me how paper wallets work. If i make a paper backup of an encrypted wallet will it require the password when importing the backup or not?

I can't go into technical details exactly about how the paper backup works (for time reasons).  The gist of it is that the wallet derives all its private keys in a deterministic (and secure!) manner from a seed.  That seed is what's on the paper backup: root key (and chaincode on wallets created with 0.88.1 and earlier).  That seed can be used to generate trillions of addresses.  You'll get the same trillion addresses the next time you restore from that seed.  The seed is all that matters.

So yes, you are totally protected from your coins being lost due to fire, HDD failure, and forgetting your password.  You do not need your password to use your paper backup.  That's by design: 95% of coin loss I've seen is due to forgetting your password and not having a paper backup.

The "risk of losing coins" is that perhaps Armory computes an address incorrectly and you send money to the wrong address.  Maybe one that can't be recovered by anyone.  I've never seen such a bug in Armory in its two-year history, but other people have done this with other apps and custom scripts.

[goatpig]

Windows User, Vista and above only:

This build attempts to fix start up issues in Win Vista+. It implements some rather big changes in how the exe is produced, so please, Win7 and 8 users, try it as well.

Note: as usual, this my build (goatpig's), not etotheipi's. This is ran at your own risk. You only need to run Armory in offline mode to confirm the compatibility of the exe.

http://dfiles.eu/files/hff8gkt3b

WinXP Users:

http://dfiles.eu/files/maerajlp1

[RoadStress]

New bug-bounty thread!


[BOUNTY] Help test next major release of Armory! [0.04 BTC/bug]

Help me test, make money!  

While i know the risks of using Beta software i just want to be sure of something. Having a paper backup makes me safe from any Armory/wallet problems/bugs/disasters right? Also please tell me how paper wallets work. If i make a paper backup of an encrypted wallet will it require the password when importing the backup or not?

I can't go into technical details exactly about how the paper backup works (for time reasons).  The gist of it is that the wallet derives all its private keys in a deterministic (and secure!) manner from a seed.  That seed is what's on the paper backup: root key (and chaincode on wallets created with 0.88.1 and earlier).  That seed can be used to generate trillions of addresses.  You'll get the same trillion addresses the next time you restore from that seed.  The seed is all that matters.

So yes, you are totally protected from your coins being lost due to fire, HDD failure, and forgetting your password.  You do not need your password to use your paper backup.  That's by design: 95% of coin loss I've seen is due to forgetting your password and not having a paper backup.

The "risk of losing coins" is that perhaps Armory computes an address incorrectly and you send money to the wrong address.  Maybe one that can't be recovered by anyone.  I've never seen such a bug in Armory in its two-year history, but other people have done this with other apps and custom scripts.

So i should keep an encrypted digital backup in hot medias and unencrypted digital backup and paper wallet on cold medias. Got it!

[picobit]

So i should keep an encrypted digital backup in hot medias and unencrypted digital backup and paper wallet on cold medias. Got it!

+1

No, +1000

[Eylrid]

Windows User, Vista and above only:

This build attempts to fix start up issues in Win Vista+. It implements some rather big changes in how the exe is produced, so please, Win7 and 8 users, try it as well.

Note: as usual, this my build (goatpig's), not etotheipi's. This is ran at your own risk. You only need to run Armory in offline mode to confirm the compatibility of the exe.

http://dfiles.eu/files/hff8gkt3b

WinXP Users:

http://dfiles.eu/files/maerajlp1

This works on Win Vista 32-bit.

[Portnoy]

Windows User, Vista and above only:

This build attempts to fix start up issues in Win Vista+. It implements some rather big changes in how the exe is produced, so please, Win7 and 8 users, try it as well.

Note: as usual, this my build (goatpig's), not etotheipi's. This is ran at your own risk. You only need to run Armory in offline mode to confirm the compatibility of the exe.

http://dfiles.eu/files/hff8gkt3b

WinXP Users:

http://dfiles.eu/files/maerajlp1

This works on Win Vista 32-bit.

It also seems to be working on XP now.   

[jbreher]

Well that was easy.  Just rebuilt 0.89.99.14-testing on OSX with the updated Makefile and re-posted it to the main thread.  Please try it again!

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

Code:

Process:         Python [25536]
Path:            /Applications/Armory.app/Contents/MacOS/Python
Identifier:      com.armory.armory
Version:         ??? (???)
Code Type:       X86-64 (Native)
Parent Process:  bash [25532]

Date/Time:       2013-11-16 19:33:29.217 -0700
OS Version:      Mac OS X 10.7.5 (11G63)
Report Version:  9

Interval Since Last Report:          145305 sec
Crashes Since Last Report:           1
Per-App Crashes Since Last Report:   1
Anonymous UUID:                      2073DD49-7F33-4177-827A-9A4C34ABF7BA

Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000

VM Regions Near 0:
--> 
    __TEXT                 0000000100000000-0000000100001000 [    4K] r-x/rwx SM=COW  /Applications/Armory.app/Contents/MacOS/Python

Application Specific Information:
objc[25536]: garbage collection is OFF

[RoadStress]

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!

[Dragooon]

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?