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

It might be worth setting up a recurring option to see what happens, in addition to any other plans you have coming down the pipe.

as i've always said, don't be afraid to build add ons or special services or an Android client.  charge for them.

Unfortunately, donations have not worked out.  I don't think I can count on that for monetization.  I get about $100/mo in donations.  Don't get me wrong, I do appreciate it (and I've bought my fiancee a lot of very nice dinners ), but even if that went up 20x, I would have a tough time justifying doing Armory full time...

You might start with one of these:

http://redonate.net/

Yeah... I need to monetize it in some way  I've actually got some ideas that I think will not "corrupt" it.  Some more on that soon...

---

Check it out!




Finally got signing Windows installers working on my offline computer.  The only problem is that .msi... not sure what's causing that.  But the signature is valid.  If someone knows how to avoid that thing... let me know!

I updated the link on the previous update with the signed version.

A bit off-topic, etotheipi, I am fairly sure your software is becoming the basis of a potentially multi-billion dollars industry--bitcoin cold storage, consider the recent price.

It was randomly generated, across all characters, I think - it was a long time ago. I missed the "=", otherwise I wouldn't use it, but I guess it doesn't hurt if it's not a problem it parsing it in a way that it's accepted.

Anyway, I tired both letting armory handle things and using a standalone bitcoinqt, it has been working perfectly fine for me.

Where did that password come from?  Should I expect other users to have '=' signs in their password?

EDIT: nevermind ... it was a fairly easy update to accommodate that.  Not pushed into the latest testing version yet, but it will be.

Yup, I deleted my conf and just let armory make another one, it works perfectly now.

@prezbo

Ack, I see the problem!  You actually did have the rpcpassword in there... but the password contains '=' signs, which throws off the python reading of the password, assuming that line.split('=')[-1] is the password.  In your case, there's an '=' in the password, so it only reads the last 1/3 and tries to use that as the password.

Okay, good bug.  I'll make a note of that!  Armory creates a 128-bit password for you, in base58, so that wouldn't happen if Armory created the bitcoin.conf file for you.

Ahh, the first problem.  I assumed they either don't have bitcoin.conf file (in which case I create it), or I expect to find it and have rpcuser and rpcpassword fields.   I hadn't considered that they have a bitcoin.conf already and do not have rpcuser and rpcpassword.

Now that you posted your RPC conf, I recommend you delete and let Armory create a new one for you (with a new randomly generated password).  You can add your extra lines after that...

This time it doesn't crash, but it just says "Armory is offline". There's still an exception thrown in the log.

edit: Ok, I am so stupid. Obviously it won't work without an rpc password. Removed the config and now it seems to be working fine. Or is it supposed to read the password from the config file? This was my bitcoin.conf, if it's of any use.

P.S. -- This is the 2,000th message in this thread!  Wow!

Okay, I continue to battle this stupid auto-manage-satoshi upgrade.  It's a real pain in the @$$.  So far, only a couple people have tried it and claimed 0% success.  But in all my testing, I can't find out where it fails.  I know that non-standard configurations are like to mess this up.  And I've done a bit of testing.  Apparently not enough, though.

PLEASE help me figure this out!  I have just released the latest, 0.87.92, installation instructions below.  Note that more than just auto-management has been added.  I also made the little "(?)" icons clickable, and reduced the number of windows you have to click through to use offline wallets. 

Linux:
-- Pull and switch branches: "git checkout managesatoshi"
-- Must install python-psutil package.  This is a new dependency to help with managing the background process.  It will be added to the next offline bundle.
-- Recompile

Windows:
-- http://dl.dropbox.com/u/1139081/ArmoryTestingReleases/armory_0.87.9-testing_win64.msi
-- http://dl.dropbox.com/u/1139081/ArmoryTestingReleases/armory_0.87.9-testing_windows_all.msi

There's a good set of debugging output that happens automatically.  If it doesn't work for you, send me a log file! 

Please try it and let me know!  Try it on a new computer without Bitcoin-Qt ever installed. Try it on a system with Bitcoin-Qt already installed and sync'd.  With Bitcoin running, without it.  With non-standard Bitcoin-Qt directories. With the option to run it yourself instead of letting Armory do it (in the settings).  Etc.

So your macbook's memory will probably be too small for now. But the netbook for offline usage should be sufficient.

Sorry if this has been answered somewhere (as i'm sure it has).

I have just bought a Asus EEE to use offline .96GB RAM and have just read that 2GB of RAM on the online one isnt really sufficient.

I have an old macbook with 2GB 1067 MHz DDR3. Not sure if that is the RAM or not, does that mean 2GB RAM?

Also, can i go about setting this up with a mac as an online computer or do i need to buy a PC for my online computer too?

Thanks

Emailed it to: [email protected] I hope that was right.

Why not?     If it doesn't work right, even a few percent of the time, I should still investigate.

Ok after a reboot and another 10 minute scan it synced up.  You still want to see a log file sir?

Try loading Armory in offline mode (there's a link in your Start menu), and then export a log file for me.  Email or PM.

Of course, you can try stopping it and starting it again.  Sometimes, it just gets stuck scanning (though quite infrequently... it's usually just being slow).   There's a few known stability issues, that result in Armory crashing every week or so.  When the new blockchain utilities go in, that will go away.