Topic: Armory - Discussion Thread - page 214. (Read 521829 times)

I think there is still a problem with releasing RAM.  I'm running Windows 7 Ultimate 64-bit. Armory worked great.  I quit it, and my system shows the RAM usage drop to normal.  However, I went to make a virtual machine with 4GB of RAM (My system has 6), and it kept crashing because it said the system did not have enough RAM.  Then I tried to open a video game, and it crashed.

A reboot seems to have fixed it. Of course, a reboot seems to fix a lot of things in Windows, so it may have nothing to do with Armory ;p  I'm pretty sure it is Armory's fault though.  I'll test to see if I can reproduce it soon.

Check address in something like blockchain.info -- looks like they go through, but don't display in Armory.

ETA for e-pi: Win7 x64

I tried this out earlier today. I had a lot of trouble getting my money back out of client. I only received invalid transaction messages when trying to send btc. 30 minutes later it appeared as send in the transaction history...

Fornit, I see you're learning quickly    Unfortunately, now that I'm distributing full binaries, I cannot just push new .py files, I have to do a full recompile and re-distribution of binaries.  So it sounds like Holliday is going to have to wait.  What a great time to leave town for a week!  


Yeah, the requirement is 1+ confirmation for tx from other people, 0 confirmations for change-back-to-self outputs.  It appears that I did introduce a bug recently, and now I'm out and won't be able to attend to it for a week  Glad to hear it's still usable, at least...

PS what OS are you in that you experience the same problems?

Is it possible to disable 2+ confirmation requirement and reduce it to the single confirmation req'd by Satoshi client? I trust the transactor's tx is valid. Keep thinking I only need one confirmation, then when I try to send, Armory declares tx invalid.

It could also be I'm mis-observing what's happening and am actually experiencing what etotheipi described earlier, given I'm using .55.


Cheers!


ETA: Yeah, pretty sure I'm experiencing the same thing as e-pi. Noticed it did go through, just not displayed in Armory.

i just looked into it and its like this when you have a different datadir:
no matter if the bitcoin client is running or not you end up with an armory client in offline mode, a wallet balance of "(...)" and -1 satoshi funds.
the armoryengine function for loading the blockchain already has a parameter for the path, armory is just lacking that one line in the optparse section + another line to pass the parameter along.
just tested it and it works like a charm 

P2Pool just uses Bitcoin's RPC.  It only deals with mining coins, nothing for wallets or any of that.

It sounds like just allowing the bitcoin data directory to be passed as a flag or put in a settings file would be enough to get everything working in non-standard setups.

just looked at the code, there is no such option, you can only specify a path for the armory settings file.

Holliday,  this is actually an interesting topic,  since I haven't dealt much with P2Pool.   Is there a reason that you have to run the server from a non-default location?   Is this going to be common among all P2Pool users?   Does the P2Pool server behave like a regular instance of Bitcoind?   I most definitely want to accommodate setups like this that I don't use,  but a lot of other people do.

I thought you said you were setting up an offline wallet,  so I was jumping ahead of you there... Definitely get you blk0001.dat file in the right place,  and this will go *a lot* smoother :-)  I'll check on the command line options,  later

Holliday,  the primary issue is that the blockchain is not being loaded.   I think all other problems will clear up when you get that.

Also, when you import a watching-only wallet, it will default to not being yours.  This is to prevent an inexperienced user from being persuaded to import someone else's wallet and believing the money is their own.

So,  once you import the watching only wallet,  you have to go into the wallet properties and change the belongs-to field.   I thought I had that in the instructions... I will add a pop-up windows for when you import a watching-only wallet, that asks whether it is yours,  or that this step can be skipped entirely.

Since I'm not in a position to check whether the is a blkdir option, maybe someone else who doesn't mind looking at the python code could check for me and report back.   I honestly can't remember if I implemented it!  If not,  then you'll have to put your bitcoin dir back to default,  or wait a couple days for me to get access to a development system and commit a fix :-(

Hi etotheipi,

Quick UI bug.   If you select the "Receive Bitcoins" button, but then press cancel on the "This is not your wallet" warning, it just pops up a big empy grey box that covers the UI

Sounds like there's a lot of little problems here.  Armory will probably go into offline mode of it can't find the blockchain maintained by bitcoind.  However I intended to put in a CLI option for specifying the dir holding the blockchain if it's not standard.   I don't remember if I ever implemented it,  and I'm on my phone right now not in a position to check.  But you can check yourself by going to the github project page and searchingfor "optparse" in Armory.py.   

As for the other issue,  I bet that you did not mark the wallet as your own.  Is the wallet identified on the main screen with a standard white background or with the dark blue?  Does it say "Watch-Only",  or "Offline"?  My guess is that it isn't marked as belonging to you,  and the default filter on the mainstream is set to "My Wallets. "  you can change the filter on the bottom left of the main screen to "All Wallets" which will start including "watch-only" wallets. 

To avoid this in the future,  click on the "Belongs to:" field in wallet properties and check the checbox.  The wallet will then appear with dark blue background and it's balance will be included in your main balance.

As for why it shows offline,  I'm not totally sure without more info.  My guess is that it's the lack of blockchain,  even though it's technically connected to bitcoind.

Red Emerald, thanks so much.  I like to think I am good at UI design, and I definitely have a high level of patience to polish everything,  catch every error,  and warn users about potentially stupid actions :-)  etc..
 
Maybe you could repeat that comment on my crowdfunding page...? :-)   It would give it a nice bump,  and I will modify the description to include the phrase "cold-storage. "  it sounds like "Bringing cold storage to the regular user" would be a much better marketing slogan than "offline wallets" and then having to describe what they are...  It sounds like slush saved himself a lot of money using cold-storage, so it makes a lot of sense to point out that's what Armory gives you...

you should be ok. from my limited testing i haven't found any serious bugs.

This client is beautiful.  The descriptions for what everything is and how to do things are built right into the application.  Best Desktop UI I think I've ever seen.  Great work!

I can't wait to setup my offline system!

I just released version 0.55 (final).  It can be found at http://bitcoinarmory.com/index.php/get-armory.  The only difference (from RC2) is a proactive security upgrade to the message signing.  But it was something that probably couldn't be exploited, anyway, so it's not critical if you are already operating with 0.55-RC2.

I noticed recently that some of my transacations are failing to be acknowledged by Armory, but do actually end up in the blockchain.  I witnessed the same thing when I went back to 0.55-RC1, so it's clearly not a completely fresh bug.  But I'm going out of town for a week, and it appears that Armory transactions still work: you will just get an error message, followed by seeing the transaction show up in the next block.   If this really bugs you, you can go back to Armory version 0.51.  Or maybe I'm the only person seeing it...?  I will investigate further in a week!

I don't have a Vista machine on which to test it... in fact I forgot that Vista even existed!   I would really love it if someone with a Vista 64 machine would test it, because I have no idea!


Congrats!  Please let me know how it works out for you, and especially if there's anything I can do to improve the interface.  And don't forget that you can append donations to offline wallet transactions, too

yeah, cold=offline.

eto, will Armory's offline main wallet run on Windows Vista?

I went for the reckless approach and just transferred it straight over     I feel....liberated

Yeah, I noticed that today, though I haven't been following the discussion.  I noticed slush using the term "cold storage," which probably refers to some custom-scripted offline wallet solution.  I wonder if I should somehow tie in the phrase "cold storage" into the Armory description:  I assume it's the same thing...