The Communists say, equal labour entitles man to equal enjoyment. No, equal labour does not entitle you to it, but equal enjoyment alone entitles you to equal enjoyment. Enjoy, then you are entitled to enjoyment. But, if you have laboured and let the enjoyment be taken from you, then – ‘it serves you right.’ If you take the enjoyment, it is your right.

However, there will eventually be support for a JSON-RPC. You should be able to build whatever you want with javascript once that exists.

I don't think you'd want to move something that uses up 4GB of RAM to Javascript-- ever.

The client should only have to download the most recent blocks in the chain. This whole issue disappears once that happens.

The Communists say, equal labour entitles man to equal enjoyment. No, equal labour does not entitle you to it, but equal enjoyment alone entitles you to equal enjoyment. Enjoy, then you are entitled to enjoyment. But, if you have laboured and let the enjoyment be taken from you, then – ‘it serves you right.’ If you take the enjoyment, it is your right.

I have plans in the far future to allow for a headers-based implementation. As long as you have the headers, you wouldn't need the whole blockchain (after all, that's kind of what the headers are for). Thus, if you just created your wallet, you wouldn't need to download the old blocks.

But that's a non-negligible paradigm shift for Armory. Until then, I'll just focus on not loading the whole blockchain into RAM. While that's a significant paradigm shift, my upcoming solution will work on systems <1 GB of RAM and not run off to infinity with the size of the blockchain...

(P.S. - I'm talking about available system RAM -- Armory doesn't use 4 GB right now, but you'd have a tough time using it on a Win7 machine with less than 4GB)

However, there will eventually be support for a JSON-RPC. You should be able to build whatever you want with javascript once that exists.

I don't think you'd want to move something that uses up 4GB of RAM to Javascript-- ever.

The client should only have to download the most recent blocks in the chain. This whole issue disappears once that happens.

What benefit do you see in having the blockchain in javascript?

Build a web app that uses javascript to interact with the armory server's JSON-RPC. "Easy" web wallet with everything that Armory has. I say "easy" because it's a lot of work to build a good web wallet even if the logic is mostly in armory. It also definitely isn't easy for the armory dev.

Send you a small donation to your BTC address. It's not much, but it's also not nothing (it was all I had in my bitcoinspinner wallet on my phone, I'll send a "proper" donation when I get back to my main PC)

Looking forward to a compiled version for windows to get around the 64/32bit python issues

I hope you don't mind if we borrow some good ideas for the satoshi client

Bitcoin Core developer [PGP]Warning: For most, coin loss is a larger risk than coin theft. A disk can die any time. Regularly back up your wallet through File → Backup Wallet to an external storage or the (encrypted!) cloud. Use a separate offline wallet for storing larger amounts.

Nice job, looks great!I hope you don't mind if we borrow some good ideas for the satoshi client

John,

I'd be thrilled if I was responsible for encouraging some new features in the Satoshi client! Of course, I'd like to take credit for having done it first (like crowdfunding based on those features before anyone else has them ), but I really think the Satoshi client needs some goodies beyond security upgrades. Security is great and all, but the Satoshi client is both the security and the face of Bitcoin, and I think the face is starting to look kind of boring...

sirk390,

You are awesome! Thanks so much! Please email or PM me your email address and/or mailing address, if you'd like your rewards. I insist that everyone who deserves a USB key and/or Tshirt should get one... the bulk discounts I get for 50+ and 100+ are pretty substantial

On that note: I haven't gotten the shirts made yet. I was planning on doing something very simple like (btw, that's not me... I'm much paler than that )

My girlfriend says I should include the full logo on there, but I have a few arguments against it. I'm looking for feedback about it:(1) I am really happy with my logo/icon, and I think it looks great without needing to identify the brand behind it.(2) I think that identifying the brand is largely unnecessary: the Bitcoin community is small enough that if someone else is not part of the community, they won't care what brand is behind it (in fact, advertising a brand explicitly may be undesirable for some of us geeks). If they are part of the community, they will probably recognize it and it won't matter whether the "ARMORY" is there.

For instance, I own one of these XKCD shirts. I get all sorts of positive reactions to it regardless of whether the person knows what XKCD is. But, I know my logo isn't as cool as a velociraptor (I mean, what is cooler than a velociraptor?). Recommendations are accepted.

Security is great and all, but the Satoshi client is both the security and the face of Bitcoin, and I think the face is starting to look kind of boring...

Well, to be honest I created bitcoin-qt in the hope (beyond adding new features) that it would accelerate bitcoin UI development by making it more accessible. The code is set up to be readable and maintainable[1].

It has partially succeeded. There are more UI pull requests than ever before with the Wx UI. Still, things are going pretty slow. Maybe we should set up a crowdfunding too. Though I really prefer code, not cash... (unless it's enough to make it my day job then I could spend a lot of time on it)

[1] Sure, major functionality changes also require changes to Satoshi's code, which is as impenetrable as ever, though it is slowly being cleaned up and reorganized.

Bitcoin Core developer [PGP]Warning: For most, coin loss is a larger risk than coin theft. A disk can die any time. Regularly back up your wallet through File → Backup Wallet to an external storage or the (encrypted!) cloud. Use a separate offline wallet for storing larger amounts.

Security is great and all, but the Satoshi client is both the security and the face of Bitcoin, and I think the face is starting to look kind of boring...

Well, to be honest I created bitcoin-qt in the hope (beyond adding new features) that it would accelerate bitcoin UI development by making it more accessible. The code is set up to be readable and maintainable[1].

Unfortunately, I'm new to Qt, so my UI code is probably "suboptimal". On the other hand, this is mostly Python, so it should be uniformly more pleasant to deal with I'm hoping to kind of lock-down the C++ stuff, and then users can fork and modify the code-base strictly with python (and PyQt is delightful!)

Though I really prefer code, not cash... (unless it's enough to make it my day job then I could spend a lot of time on it)

I'm only motivated by money if it's enough to cut down my hours or pay off a significant portion of my house. So, I decided to see if I could pull off the first one with crowdfunding in exchange for keeping my software awesome and open source. I'll let you know how it goes