Pages:
Author

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

legendary
Activity: 1498
Merit: 1000
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?

Paper wallets protect you from if your backups get deleted or corrupted and can't be read. They don't protect against sending bitcoin bugs. I would suggest you don't armory unless you know what you are doing.
legendary
Activity: 2030
Merit: 1000
My money; Our Bitcoin.
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.   Smiley
newbie
Activity: 24
Merit: 0
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.
hero member
Activity: 547
Merit: 500
Decor in numeris
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 Smiley
legendary
Activity: 1904
Merit: 1007
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!
legendary
Activity: 3738
Merit: 1360
Armory Developer
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
legendary
Activity: 1428
Merit: 1093
Core Armory Developer
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.
legendary
Activity: 1904
Merit: 1007
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?
hero member
Activity: 496
Merit: 500
Wow. This latest version is super fast on Windows 7. Like, 15-30 second startup time fast.
els
newbie
Activity: 41
Merit: 0
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
legendary
Activity: 1428
Merit: 1093
Core Armory Developer
pvz
newbie
Activity: 53
Merit: 0
Top post links now link to the fixed .deb installers!
Check! Works.
Thanks Alan!
legendary
Activity: 1428
Merit: 1093
Core Armory Developer
Fix coming in 3... 2...

... 1!

Top post links now link to the fixed .deb installers!
legendary
Activity: 1428
Merit: 1093
Core Armory Developer
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
    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...
pvz
newbie
Activity: 53
Merit: 0
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
    from dialogs.toolsDialogs import MessageSigningVerificationDialog
ImportError: No module named dialogs.toolsDialogs

EDIT: same error like reported a few posts earlier.
legendary
Activity: 1148
Merit: 1018
So happy that OSX builds are included by default... Great job Alan, godspeed!!!
member
Activity: 125
Merit: 10
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.
legendary
Activity: 1428
Merit: 1093
Core Armory Developer
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!
legendary
Activity: 1428
Merit: 1093
Core Armory Developer
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)
member
Activity: 125
Merit: 10
I've been running armory on osx for awhile now. Initially before there was a pre built app, I built it from the testing source on github following the instructions on the site. It worked fine. Then v9 and v10 came out as pre built app. It still worked fine. Now with v14 and armory will not load. Here is a paste from the log:

2013-11-14 14:44 (INFO) -- armoryengine.py:625 - Executing popen: sysctl hw.memsize
2013-11-14 14:44 (INFO) -- armoryengine.py:625 - Executing popen: sysctl -n machdep.cpu.brand_string
2013-11-14 14:44 (INFO) -- armoryengine.py:806 -
2013-11-14 14:44 (INFO) -- armoryengine.py:807 -
2013-11-14 14:44 (INFO) -- armoryengine.py:808 -
2013-11-14 14:44 (INFO) -- armoryengine.py:809 - ************************************************************
2013-11-14 14:44 (INFO) -- armoryengine.py:810 - Invoked: /Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/ArmoryQt.py
2013-11-14 14:44 (INFO) -- armoryengine.py:811 - ************************************************************
2013-11-14 14:44 (INFO) -- armoryengine.py:812 - Loading Armory Engine:
2013-11-14 14:44 (INFO) -- armoryengine.py:813 -    Armory Version        : 0.89.99.14
2013-11-14 14:44 (INFO) -- armoryengine.py:814 -    PyBtcWallet  Version  : 1.35
2013-11-14 14:44 (INFO) -- armoryengine.py:815 - Detected Operating system: MacOSX
2013-11-14 14:44 (INFO) -- armoryengine.py:816 -    OS Variant            : ('10.8.5', ('', '', ''), 'x86_64')
2013-11-14 14:44 (INFO) -- armoryengine.py:817 -    User home-directory   : /Users/xxxx/Library/Application Support
2013-11-14 14:44 (INFO) -- armoryengine.py:818 -    Satoshi BTC directory : /Users/xxxx/Library/Application Support/Bitcoin/
2013-11-14 14:44 (INFO) -- armoryengine.py:819 -    Armory home dir       : /Users/xxxx/Library/Application Support/Armory/
2013-11-14 14:44 (INFO) -- armoryengine.py:820 - Detected System Specs    :
2013-11-14 14:44 (INFO) -- armoryengine.py:821 -    Total Available RAM   : 16.00 GB
2013-11-14 14:44 (INFO) -- armoryengine.py:822 -    CPU ID string         : Intel(R) Core(TM) i7-3720QM CPU @ 2.60GHz

2013-11-14 14:44 (INFO) -- armoryengine.py:823 -    Number of CPU cores   : 8 cores
2013-11-14 14:44 (INFO) -- armoryengine.py:824 -    System is 64-bit      : True
2013-11-14 14:44 (INFO) -- armoryengine.py:825 -    Preferred Encoding    : US-ASCII
2013-11-14 14:44 (INFO) -- armoryengine.py:826 -
2013-11-14 14:44 (INFO) -- armoryengine.py:827 - Network Name: Main Network
2013-11-14 14:44 (INFO) -- armoryengine.py:828 - Satoshi Port: 8333
2013-11-14 14:44 (INFO) -- armoryengine.py:829 - Named options/arguments to armoryengine.py:
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     maxOpenFiles    : 0
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     nettimeout      : 2
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     rescan          : False
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     leveldbDir      : DEFAULT
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     port            : None
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     interport       : 8223
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     coverageOutputDir: None
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     rebuild         : False
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     datadir         : DEFAULT
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     offline         : False
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     satoshiPort     : DEFAULT
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     netlog          : False
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     keypool         : 100
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     coverageInclude : None
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     forceOnline     : False
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     logDisable      : False
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     mtdebug         : False
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     skipVerCheck    : False
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     settingsPath    : /Users/xxxx/Library/Application Support/Armory/ArmorySettings.txt
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     verbosity       : None
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     doDebug         : False
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     testnet         : False
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     rpcport         : DEFAULT
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     satoshiHome     : DEFAULT
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     logFile         : /Users/xxxx/Library/Application Support/Armory/ArmoryQt.py.log.txt
2013-11-14 14:44 (INFO) -- armoryengine.py:832 - Other arguments:
2013-11-14 14:44 (INFO) -- armoryengine.py:835 - ************************************************************
2013-11-14 14:44 (INFO) -- armoryengine.py:1041 - C++ block utilities loaded successfully
2013-11-14 14:44 (INFO) -- armoryengine.py:13507 - Using the asynchronous/multi-threaded BlockDataManager.
2013-11-14 14:44 (INFO) -- armoryengine.py:13508 - Blockchain operations will happen in the background. 
2013-11-14 14:44 (INFO) -- armoryengine.py:13509 - Devs: check TheBDM.getBDMState() before asking for data.
2013-11-14 14:44 (INFO) -- armoryengine.py:13510 - Registering addresses during rescans will queue them for
2013-11-14 14:44 (INFO) -- armoryengine.py:13511 - inclusion after the current scan is completed.
2013-11-14 14:44 (ERROR) -- Traceback (most recent call last):
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/ArmoryQt.py", line 42, in
    from dialogs.toolsDialogs import MessageSigningVerificationDialog
ImportError: No module named dialogs.toolsDialogs

Can you please help me figure out why it's not working anymore now?
Pages:
Jump to: