Yes, I think so, too. With anonymized IP and bitcoin payments, everybody can use their site without any problems, however they probably don't announce that in this way officially :-).

Btw are there some proxies4btc?

Version 0.4 released, fixes non-working streaming from MtGox. It is now using socket interface to bitcoincharts instead of MtGox's socket.io.

Download: http://mining.bitcoin.cz/media/download/sierrachartfeed-0.4.exe

Pros - sierrachart now supports live streaming of all bitcoin charts, not just MtGox.
Cons - there's currently implemented only polling between bitcoincharts and mtgox and chart updates are delayed 5 seconds in average. But tcatm is working on socket.io support on his side, so it will gets better soon.

Enjoy! :-)

Great. It's sad that your code for using qrcode in pygtk is actually longer than whole QR support patch :-). I didn't know that I can directly with Gtk so sorry to give you extra work on my patch. I need to learn Gtk a bit more.

I'm actually thinking about "coin selection" patch, so I may also redesign fee calculation. I wanted to know that you're aware of that and you also see it as "problem to be fixed". Calculating appropriate fees can be pretty tricky, because rising fee can rise size of transaction, which can rise fee again :-). Btw coin selection is yet another feature which I'm missing in official client.

Well, both toolkits can work, however I don't like splitting power in such early stage. Having two frontends needs 2x more gui development for every feature. So if you don't like Qt, then I'll try to code for that Gtk monster :-). However we should keep in mind that frontend *can* be changed in some step, so strictly isolating GUI and "backend" would be very nice. About keyboard accessibility - I'm not a fan of "rich" interfaces like skype so I don't see any problem with keeping keyboard accessibility also on Qt.


For push you don't need any open ports or some other games with firewall. Client just open persitent TCP connection to server and "subscribe" for some kind of events, like new transactions to some addresses etc. Then server route only necessary information to this socket. Keeping one open socket per one client is almost zero-cost, it brings instant updates and very low load on server (imagine that one server can serve for thousands or even tens of thousands clients; then polling and periodic database requests will be an issue).


lol, that's serious reason ;-). As far as I understand, almost all bitcoin developers are already on github, so hosting project here will lower barrier to get some occasional patches to electrum as well. And as far as I understand github has some very nice features for "social coding" like on-site merging of trees, patching etc. But well, it's absolutely your choice.

I don't think /etc/electrum.conf is good place, because client need write access to that (as it contains private keys). And give any non-root user access to /etc/ is imho bad thing (tm).

Pretty nice deals. Is possibility to use SSD disks in your configurations?

Edit: Btw I see pretty big gap between low-cost offers and high-cost. For example, 2GB RAM on server is nothing if you need to run some memory eating applications (like bitcoind, heh). However 24GB RAM is quite oposite. Some offer with 8-12GB RAM would be pretty nice.

I think using eval is really bad idea as it literally open the door for mitm attackers (you can do almost everything with eval like accessing local filesystem). I still re-read documentation for ast yesterday to be sure there's no possibility to attack clients with modified payload and so far it looks safe.

Module AST has been introduced into standard python library in version 2.6, which is the reason why python 2.5 throws such error. I think electrum can safely expect python 2.6 as minimal version, as 2.5 is beeing obsolete in almost every distribution.

One more finding: As far as I understand fee calculations in official client, it is "fee per kB", not "fee per transaction" as is implemented in Electrum. Normal transaction is usually under 1kB, however sometimes there are strange multi-kB transactions - especially when miners are consolidating their 0.01 payouts from pool to one address. Then static fee in Electrum can lead to some unexpected behaviour.

I knocked up first version of QR code support, feature which I'm missing in official client. It is using 3rd party library from googlecode, which isn't available thru easy_install, so I decided to add it directly to sources and do not create some weird dependency. Alsp PIL (python imaging library) is necessary for rendering image.

QR code is displaying in separate window instead directly in GUI because I'm lacking some high-level concept of GUI (and, honestly, I feel like GUI need a lot of work ). I just made it as simple as possible, but I'm open to make QR code as part of main window if you tell me where you want to show it. But I still hope you decide to go to Qt so I won't need to fiddle with Gtk (and I'll finally learn Qt instead).

http://mining.bitcoin.cz/media/download/qrsupport.tgz

Thomas, excellent work! I finally found some time to test everything and read (most of) the code. I really appreciate small footprint of client. There's lot of things which I like on your client, namely deterministic wallet (no need for periodic backup is awesome feature) and client-server architecture, which makes client really lightweight and very fast to use.

Few comment though.

1. Consider to switch to Qt. It's much modern gui toolkit and looks better especially on Windows. Thanks to minimalistic GUI it's still pretty easy to switch. Your client has great potential but GTK looks weird on Win and it's wrong to focus only on linux users (although I'm 100% linux user).

2. Consider better network interface and wallet format. Using 'repr' may break things in future as this isn't supposed to be platform-independent serializing method ;-). I see potential in using server side with some mobile clients, however implementing repr in java might be real hell. Although I don't recommend Json, it would be better than repr and it does not need new dependency as json parser is in stock python. Also thinking about pub/sub mechanism which can avoid server polling would be great. pubsub can make updates on client instant and yet vastly save server resources (as common client does not receive transaction all day long).

3. Consider to move to Github. I'd like to submit some fixes time to time and I finally need to learn with Git & Github :-). So migration to github would be good reason for me to go thru git manual (I'm mercurial user for years).

I can imagine that I'll install electrum to my friends instead of standard client when electrum matures a bit, because handling blockchain is simply big overhead for occasional users. Once again - really good work so far!

OT: If I remember well, we made OTC trade on 1st January together, right? It was my first sell-off and your first buy :-D.

I agree with DAT. There's no reason why centralized company or government should run it's own blockchain. P2P currency is good only for P2P audience.

I can imagine that two projects of p2p cryptocurrency can live together only if their features will be completely different. However I don't see any point in those aternative scamcoins or coins which are different only in technical details (like only cpu mining).

Also Bitcoin has huge advantage because it is first p2p currency. Every new project, even with significantly better features, will fight with "why xxxcoin when we already have bitcoin".

I mean some direct way for deposit/withdraw in Europe. So SEPA transfers or cash deposits in some European banks. As far as I understand, those cash deposits in Citibank and ING are only working in USA, right?

I have 1.05 BTC. What is correct answer for me?

Any plans for deposits/withdrawals in Europe?

I bet it's some problem with mailing system, configuring it is my nightmare. I'll check...


Looks like it's problem of btcstats.net. You can see that hashrate in API is correct...

You forgot to Mystery Miner, it was big topic months ago :-).

It was just - LOL. I'm sending few cents for making my life longer.


Definitely the best part.

That read only access is great. Ryland, can you add some notice on homepage as howto for people who want write access to forum?