This can be solved by sandboxing and giving only specific API to task developers. I think it can be done easily, because I already did this for python scripts and it worked quite well. For commercial usage maybe Java is better (high level language but good performance, possibility for GPU processing and sandboxing).

By the way there were some commercial projects like this. It always finished on low demand for this kind of processing.

Bitcoin protocol is not stable yet. It could be problematic when incompatible change happen and thousands people have clients from their 'stable' distribution. This was also reason why Tor was not in repositories for many years.

Is transaction fee used for confirmation priorities? If yes, it would be cool to allow changes of fees directly on 'send coins' dialog. For some donations of few bitcoins I don't care about time, but if I want to send coins to somebody who is waiting to confirmation, it can help...

Dumb question: Why I should lend bitcoins to somebody who I don't know, when price of bitcoins itself rises due to its deflationary principle? I'm pressed to lend (and invest) when money lose its value by lying on my account, which is not an issue in bitcoin.

It can be profitable only when I lend on high percent (% deflation + % interest). In case of inflation, lending is everytime better than leave money on my account (even if interest < inflation). Am I right?

Does anybody have any experience with AlertPay? It is safer than PayPal for sellers? I mean chargebacks etc...

 Do you have any link or reference? I found only 3rd party ActiveX component here http://www.chilkatsoft.com/js-sha512-hash.asp.

Will be available if I finish that. It is just for curiosity because it will be slow as hell. Also network overhead will be significant.

I expect simple PHP proxy will do good work for hiding credentials to client. something like yourdomain.com/getwork.php which call rpc to localhost and return json encoded data.

There was update before 15 minutes. Did you receive it? It is always in text format. If you are interested, I can send you original json (there are the same data, but encoded as json dict).

Cool, I like simplicity of your code. I want to try similar implementation in javascript. Partially because of curiosity and partialy because (inspired by hashcash) it can generate few hashes by fighting comments spam :-).

I just made few tests. In four javascript threads I get ~4khash/s, which is EXTREMELY slow. Probably because javascript is interpreted and without any JIT yet. Would be great if javascript supports GPU. Flash will support GPU soon, so we will see .

This seems interesting, I did not know that. But hey! I'm missing "Bitcoin" as Default unit on ripplepay! :-) Are you somehow related to ripplepay developers? It would be nice to add Bitcoin as currency ;-).

Czech Republic

Well, there is no way how to implement unofficial clients for many users/programmers (like me), because they are not enough skilled in C++ and reverse engineering. But I'm capable to write alternate client with at least basic specification how whole thing works. Unfortunatelly because I'm not capable to write own client, I'm also not capable to help anybody with specs. At this time, I'm dependent to somebody else who starts specification process.

I'm absolutely not talking about any formal standard, wiki should help a lot in this stage.

Hi m0mchil, firstly thank you for your work. Is there any way to include getwork patch into official client? I'm using bitcoin on old centos server and compiling is pain here!

Let's imagine that eshop will tell customer to pay to address https://great-eshop.com/customernickname where link-rel is unique for every customer nickname. It is just alias for any bitcoin address.

It is nice to remember for customer, extremely easy to implementation and safe enough.

Hi Diablo, I just tried your miner on Nvidia ION; it is quite impressive machine, because your hashmeter showing me 43Ghash/s at this moment . I was playing with -v and -w parameters and because I don't have an idea what it means, after setting up -w 1024 it become crazy. With default settings I have 2000khash/s which is very poor, but reasonable for this machine.

Didn't miss anything important in your list.


I like a possibility to encode not just address and address, but also a periodicity. Why not to combine both methods - take standard format of URI and parameters for period payments from second obscure notation? Something like

bitcoin:<address of recipient>?acount=10.00&period=12,monthly&next_variable=

I vote for removing 'sender address'. We can discuss how often anybody needs to catch both side of transaction (seller address and buyer address) in constant URI? Paypal subscription links also contains only receiver's information and metainformation about payment (amount, period etc). It is on the client side which his wallet he will use for transaction.

So when you notice that URI format can also keep information about period payments, I think it is far best notation. But create poll and we will see if I'm not alone with my attitude .

Try bitcoin@jabber.cz for updates. I started bot on my desktop, but have also 24/7 server where can be bot online if it will be useful.

Also current algorithm is that polling is faster when market is active (first poll after market update is 0.5 second, next ~1.5 second) and is limitely going to poll every ~25 when market is dead (here is simple log function inside which make time between polls longer). It is absolutely no problem to modify algorithm to fit special requests.

The few most important hashes I already remember. I also have my website with simple hash calculator in javascript and virtual keyboard.


Of course, I absolutely agree. But do you prefer to use *nothing* than passwords? It is the main concern I'm speaking again and again here. I'm ABSULUTELY agree with you that passwords are not good enough and I use PAM and private/public keys everywhere it is possible. But I will use password rather than leaving my money in plaintext. Agree?


I didn't say it is not possible or that YOU cannot do that. I see that on bitcoin forum are 90% people geeks and 10% libertarians (which are not both geeks and libertarian). So you probably know how to do memory overflow. But I'm telling you there are tens of thousands of sysadmins which does not know how to do memory overflow but know how to do copy&paste. Again, passwords are better than nothing.

Gavin, I almost agree. But


is way how classic banks started its businesses. When some online wallet become popular, they will probably see that have too much bitcoins on account which nobody handle for long time....

By the way, when you have account bitcoins on some service, how they belong to you? Technically they are not yours. Do you ask for some paper that you have some deposit here? Do you see an analogy? :-)

Electronic currency can be safer than physical wallet. Because it can be encrypted in your pocket and you can make a backup to your home vault. So when we fix wallet security somehow, there will not be a space for 'trusted entities which manage your large amounts of bitcoins'.

I implemented jabber bot (python) which multicast changes on Mt.Gox in almost realtime fastion to all subscribed contacts, but it is currently off (it is working but I do not have reasonable usage yet). It is nice that the polling of mtgox API can be done only once for many many independent users.

I can publish my work or cooperate on this project, because it can be quite straightforward to add settings for each subscriber, which kind of price he is interested in (say 'send me just notification for movement above $0.3/USD).