Topic: Have you been waiting for Armory-Beta? Help me release it! - page 2. (Read 4378 times)

0.82.4 worked, but now with 0.85 I get this:

Trivial if you know what you're doing. Care to start a thread where you walk me step by step through the installation process? I'm sure somebody else down the road will get some use out of it.

Um. Because it's utterly trivial to do it I expect a lot of people don't talk about it much.

Fedora removes ECC support from OpenSSL because OpenSSL doesn't distinguish the stuff that no one argues isn't covered by valid patents and the stuff that no one argues is patented. RedHat's response was just to disable it all and let god sort it out.  So you need OpenSSL recompiled with the removed ECDSA re-added.  Once you have this it works like anywhere else (e.g. you need the suitable dependencies and development headers).

I've maintained suitable RPMs for my own usage for some time: https://people.xiph.org/~greg/openssl/

I'm happy with Fedora. Also, I don't have the Satoshi client running on my system. I couldn't install the RPM offered or compile it or anything. Somebody claimed that Fedora has restrictive licensing that prevents the use of the Satoshi client because the Satoshi client requires some sort of software that Fedora won't allow.

It's a real drag and it may be a while before that issue gets solved.

I'm hoping some day there's an Anarchy Linux that doesn't pay attention to licenses at all, period.

If this is your goal you might be better served by Gentoo or Linux From Scratch as opposed to Fedora.

If you have the dependencies installed, then you might have to change two characters in the makefile, then type "make".  Then it's done.  The dependencies are usually where the issues are, but Armory's dependencies are totally standard and not picky about version.  And I'm working on how to autodetect the condition when you have to change the two characters (I'm really bad with makefiles).

Please make a post in the discussion thread and I'm sure someone will give you step-by-step instructions, and my guess is it will only be a couple commands.  And when they do, I'll post them on the website.

On the other side, Bitcoin-Qt is a royal P.I.T.A to compile.  I believe it's very picky about versions, and trying to get those versions installed are likely to fail and/or break other things on your system.  While I can't help you compile it, you don't need to compile it yourself to use Armory (I assume since you are here that you have a pre-compiled version you are using already).

  

Good decision on keeping the Satoshi client for networking.

I'd really like to get in touch with these fellow RH users who compiled your software, because I've been completely unable to compile the Satoshi client on Fedora. There have been people who *claimed* it "could" be done, but none of them were people who actually DID it. There is one fellow who offered an RPM of the Satoshi client from his repository, but I never could get it to work. So, if you actually know people who could help me get the most recent stable version of the Satoshi client, and the mos recent version of the Armory client installed on Fedora, I'd be ecstatic.

On a side, I'm teaching myself programming right now. I got tired of not knowing how to do shit. Besides, it seems like a good career path. May be a long time though before I can produce anything of value.

To be fair, the compilation instructions are very easily translated to other *nix OS'es.  I have a few RH users who said it was quite easy to compile.  Unfortunately, my experience with other Linux distros is slim, but if you are using other distros, you're probably already familiar with copying a few commands into a terminal to get things to work.  However, I don't know if Bitcoin-Qt is the same...

FYI, I am the Armory developer.  I am the only one.  So, not only am I short on time, but my experience is limited to what I use.  I've spent quite a bit of time trying to accommodate other OS'es, but I really need other people (like you?) to help me figure out how to prepare it for other OS & architectures.  Red Emerald has basically taken the helm like this for OSX, and I would be thrilled if someone helped me figure out how to make an RPM, etc.

I know that's not the answer you're looking, but it's the best I can do by myself, at the moment...

As soon as there is an RPM Satoshi Client and RMP Armory client available, I'll be all over it.

I just added the "Ubuntu 10.04 Offline Bundle" to the "Get Armory" page.  Or here's the direct link:

Armory 0.84.5-alpha offline bundle for Ubuntu 10.04 32bit and
Detached GPG signature for offline bundle.

It should be exactly everything you to install and run offline Armory on the first boot of a fresh Ubuntu 10.04 32-bit installation.  I have tested this with a fresh VM, but I do need others to try it to make sure that I didn't "cheat" by accident while testing it

---

P.S. - I just realized that the webpage (and the links above) suggest that they only way to have an offline computer is through Ubuntu 10.04 32-bit.  I should clarify that any offline system running Armory without an internet connection is an "offline system," and as long as Armory runs, it will serve its purpose.  This means that you can use a Windows machine and just copy the installer over there, detach it from the internet, and you're good to go.  The only reason why there's a special bundle for Linux is because Armory requires some dependencies to be installed -- which are downloaded and installed automatically when Armory is installed -- but those dependencies are not accessible if you do a fresh offline-installation of Linux without it ever touching the internet.

So, don't think that you need any special version of Armory to run offline.  The bundle only helps you get it setup on an Ubuntu machine that started offline and can't get the dependencies.  Without it, if you install Ubuntu, you might want to put it online long enough to install Armory and its dependencies, then detach the network cable... but it's clearly much better if you can do a fresh Ubuntu installation without ever touching the internet, even at the start.  

I'm actually out of town right now and can't update the webpage yet.  So I wanted to clarify this for users before then.

Thanks for the explanation.
Concerns alleviated.

Oh, I guess I missed some polishing... "Private Key" options are supposed to be disabled for watching-only wallets.  Private keys are always displayed with a 4-byte checksum after them, so it's easy for the system reading it to recognize if it was copied correctly.  In this case, since the wallet doesn't have private keys, it's showing you a zero-byte private key (i.e. nothing) with a four-byte checksum after it (checksum of an empty string).  That's why it's the same few characters for all private keys on that screen -- they're all the same empty string.   Don't worry, there's no private key data in the wallet to be leaked

If you're really interested, I documented the wallet format:  http://bitcoinarmory.com/index.php/armory-wallet-files.  You can use it to manually check your watching-only wallet file... you can dig through the binary and verify that the private-key fields are really empty.

I'll add that to my list of things to polish for the official beta release.

Newbie type question...

The private key fields are empty in the watching only wallet for both BE and LE formats but why are there a few numbers/letters listed for my Private Key (Plain Base58) in my watching only wallet for all of the addresses?

I compared these numbers/letters to the Private Key (Plain Base 58) listed in my offline wallet and they are different.

I am confident that the offline wallet has the actual Private Key but got a bit spooked when I saw a combination of numbers/letters listed in the watching only version.

Thanks,
xcsler



 

Glad you found the tap useful.  As soon as treading is on master, I'll update the tap. This makes it essentially 2 commands that can be copy/pasted to install. I've been experimenting with the "--framework" flag when installing python with brew and hoping this makes building a .app work. I tried doing something similar to electrum's Mac steps, but kept getting errors. I've been really busy with non-btc stuff, but I should have some time this weekend to play more.

Also Red Emerald has a brew formula that makes installing it for mac insanely easy.
https://bitcointalksearch.org/topic/m.1136230

Unfortunately, my Mac-fu is really weak.  Before a 2 months ago, I had never even seen what OSX looks like.  After doing some research, I determined that creating an official package is a lot of work, and probably a bit of money (for the code-signing key). 

However, I have received some tips from others, about creating .dmg/.app bundles.  The problem is the dependencies -- I might have to do something creative to make it work as a standalone application without the users installing a bunch of stuff.  On the other hand, RedEmerald's instructions involving brew have been good enough that it worked on my first try when I finally got a 10.7.4 OSX VM running (it does download and install all the dependencies, which is why it's not terribly difficult).  There's more here in case you want to try it.

On the other hand, maybe Red Emerald would like to respond here with his latest walk-thru, to make sure that those users who want to try it, can see it.  While I've had reasonably good response to people compiling in OSX, I have personally tested it very little there.  Again, maybe RE would comment on its limitations (if any) compared to the Windows/Linux.

As soon as there's an OSX installer suitable for command-line-o-phobes I'll be installing this quickly. It looks like exactly what I've been waiting. Thanks for all the work so far.

I'm sure most of you have at least heard of Armory by now.  Many folks donated to the Armory call for crowdfunding back in March.  And many other folks claimed they would try it when it was no longer alpha.   And even while it has been alpha,  Armory has been getting about 1,500 downloads per month!  

Well, after 8 months and probably another 1,000 hours of development, I believe that Armory is about ready for its official Beta release!  

However, I want to release the latest release candidate to a smaller crowd of people, before doing it officially -- Armory now has so many features, that no level of personal testing is sufficient for such a major release.  I just need people to get out there and use it!  If you've always wanted to try it, then please use it and give me feedback!


Get Armory version 0.84.5-almost-beta
(there's a very good chance that this will be the final beta release)



For those who like to compile their own, you can check it out from the github repo:  "git clone git://github.com/etotheipi/BitcoinArmory.git" and the switch to the threading branch "git checkout threading".  It will be merged into master when the release is official.  (more detailed instructions at the Building Armory from Source page)

---

What's new since crowdfunding phase?   (Answer: everything)

• Armory now works on 32-bit and 64-bit Windows and Linux (Mac/OSX users have been successful at compiling it themselves, but I have failed at packaging it properly; there are links on the "Get Armory" page linked above)
• Installers with uninstallers for both Windows and Linux
• Bulk address importing/sweeping
• Multi-threaded blockchain scanning so you can still user Armory while it is scanning.
• System tray icon, with notifications!
• Full "bitcoin:" URL handling in both Windows and Linux (and a place to enter the URL manually if clicking the links don't work for some reason)
• Create clickable payment requests to be copied into emails or wepages.
• GPG-signed installers for using the Armory Signing Key (the first link on that page)
• Export your transaction histories
• Minimize to system tray
• Manually pecify change address for each transaction (expert usermode only)
• Version checking and notification
• Endless polishing (table sorting, formatting, preferences, filtering, warning windows, action verification checks, tooltips/mouseover text on everything, etc)

And of course, that is only what is new to Armory!  Don't forget that Armory gives you:

• Painless offline wallets (cold storage)
• Multiple-wallet interface
• GPU-resistant wallet encryption
• Deterministic wallets
• Only-one-time-needed-ever backups!  Print one off when you create the wallet, protect it forever!
• Watching-only wallets
• Key importing and sweeping
• Message signing
• And lots more I can't even remember!

If you haven't tried Armory in a while, it probably looks completely different.

Remaining issues (what you can expect):

• Still requires Bitcoin-Qt to be running.  But I made a page explaining why
• Still long load times, but at least Armory is running while it is loading
• RAM usage is dramatically reduced from the original, full-blockchain-in-RAM implementation.  But SatoshiDice has bloated the blockchain so much, that even my indexing scheme consumes a lot of RAM (>=1.0GB).  After Beta, I will be switching to having Armory manage its own blockchain data using LevelDB, which will trade RAM consumption for HDD consumption.  However, I wanted beta to be a stable release with the current HDD-lite architecture.  (a lot of power users have a lot of RAM and like the small HDD footprint)
• Windows 32-bit still sometimes has issues.  Until the upgrade mentioned above, Win32 users may not have a pleasant ride.
• Some crashes may still exist under combinations of events.  If you experience this, please send me a log file
• Compressed public keys not supported.

P.S. - In case anyone is wondering:  There have only been two reports, ever, of users losing money with Armory.  Both cases were due to users side-stepping Armory's built-in protections -- they manually deleted files in the application directory -- and both would've been prevented if they had made paper backups! (a digital backup would've been fine, too)  

Make a paper backup of your wallet and keep it safe!  Only one backup is necessary to protect all private keys, forever! (except private keys, back those up separately).   Even if you later decide you don't like Armory, you can use the "Backup Individual Keys" dialog to export all private keys to be imported into another application or service.