I don't understand how exactly the client forces the fee. I set paytxfee=0.00 in the config. Then I have launched bitcoind without args, sent a little amount to myself and saw 0.0005 BTC fee though I explicitly set 0.00 (or should I add zeroes and make it 0.0000?). Then I've restarted the daemon with the option -addnode=173.242.112.53 And my next tx has gone without the fee. Is the client somehow negotiate to its peers about the fee and forces 0.0005 if no one accepts free tx? Isn't it wrong? If I want not to pay the fee the client should notify me that no peers accept the free tx instead of silently wasting my money (yes, it's less than 1 cent but anyway it's money).
As I see on the block explorer most of txs are done without fees so either the free transaction policy is very popular or there's a way to set really zero fee in the client and I'm doing something wrong. Please explain this.

As we know from some point clients start to refuse transactions without fee. A friend of mine sent me 0.1 BTC as a donation using old client (0.3.20 or so) which doesn't include fee. So that transaction was never confirmed but money can't be lost either because it wasn't included in any block. How can we recover it back to spend using the newer version? Or maybe I'm wrong somewhere because I have transactions with no fee but I use -addnode=173.242.112.53 and he obviously doesn't because he's not so good in bitcoin even having an older client.

P.S. there is a little possibility that he had fooled me and sent nothing but let's think of it as it really happened.

Хороший пиар биткоин, пусть и от Ализара: http://habrahabr.ru/blogs/crypto/113569/
Призываю туда всех, имеющих аккаунт на хабре и желание пояснить нубам суть™, а то как по нотам разыгрывают композицию «биткоин ничем не подкреплён» и «биткоин == процессорное время», а ещё «ботнет с вычислением инопланетян». Ну и прочий феерический бред. Есть возможность вызвать новый всплеск, пока тред не ушёл с главной.

Congratulations! Bitcoin becomes widely spread since famous anonymizing and security-related projects start to accept them.

I've seen it in the news section of i2p router but didn't find such on the site. Here it is:

   * 2010-12-14: I2P accept bitcoins

From today on I2P does accept donations in form of bitcoins. Just transfer your amount of coins to the account with the ID <a href='bitcoin:?addr=1HkJCceXf7of1sTNRVJbXiZHfDTLL71Siy' id='lnk01HkJCceXf7of1sTNRVJbXiZHfDTLL71Siy'>1HkJCceXf7of1sTNRVJbXiZHfDTLL71Siy</a> and it will be used for the benefit of I2P. If you want to be noted on the I2P hall of fame drop a note to echelon with needed information.

http://www.i2p2.de/donate.html

Довольно очевидное применение биткоинов. Меня интересуют инвайты на habrahabr.ru и what.cd, кто на самом деле может продать — пишите вашу цену. Если вы достаточно давно на форуме и с хорошей репутацией, могу перевести сумму первым (биткоины не отзываются, так что тут либо на доверии, либо через третье доверяемое лицо).

I heard some guy has 25% of all bitcoins. What happens if he will trade it for dollars on the market? He has LOTS of coins so he may offer low price for them and everybody will buy it from him. Then it will cause inflation and lowering the exchange rate greatly for many months if not years. Will bitcoin cope with such a disease? We don't talk about motives of that dude. He may do it just for lulz or whatever. He might get all those bitcoins when the difficulty was low or he has a large cluster that generates blocks on a large scale. The same goes to all large generating clusters which may ruin the economics instantly.

Any thoughts on it?

Целый вечер протрахался, но собрал его. Попутно понадобилось изучить конпеляцию CUDA-кода и установить два SDK, чтобы без лишних костылей оно собралось. Судя по логам, работает. Скорость 5230 килохэшей на GF 8600GTS, на процессоре E6750 в два потока — всего 2300. Жаль, что автор кода не предусмотрел параллельную работу CPU и GPU майнеров, хотя я сомневаюсь, что при этом можно было бы вообще работать на компьютере. Сейчас с параметром -responsive процесс иксов жрёт около 20% CPU, сам bitcoind — 95%. Работать не очень комфортно, окна несколько залипают при переключении. Пробовал запускать с -aggressive, так иксы вообще встали намертво, пришлось с другой машины останавливать bitcoind. Без -responsive переключение между окнами может занимать более минуты, тоже не вариант.

Зависимости:

%[homecomp]:[~/svn-soft/bitcoin/trunk]> ldd bitcoind
   linux-gate.so.1 =>  (0xffffe000)
   libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0xb777f000)
   libdl.so.2 => /lib/libdl.so.2 (0xb777a000)
   libz.so.1 => /lib/libz.so.1 (0xb7766000)
   libcudart.so.3 => /usr/local/lib/libcudart.so.3 (0xb7712000)
   libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb7621000)
   libm.so.6 => /lib/libm.so.6 (0xb75f7000)
   libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb75d9000)
   libc.so.6 => /lib/libc.so.6 (0xb746e000)
   libpthread.so.0 => /lib/libpthread.so.0 (0xb7453000)
   librt.so.1 => /lib/librt.so.1 (0xb7449000)
   libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0xb7362000)
   /lib/ld-linux.so.2 (0xb77ab000)
   libpcre.so.0 => /lib/libpcre.so.0 (0xb7333000)

Автор кода оказался какашкой, и не выложил модифицированный под этот клиент makefile, так что пришлось разбираться самому. Если кому-то интересна тема, могу выложить бинарник и/или makefile для сборки. Также понадобится скачать CUDA Toolkit и GPU Computing SDK. Учитывая, какую оплеуху lzsaver дал жмоту puddinpop'у, думаю, было бы кошерно довести удар до конца и выпустить сборку под линукс раньше всех ^_^

PS: для сравнения собрал вариант от nelisky, он даёт порядка 5000к, т.е. немного меньше. Но зато, вроде как, мэйнтейнится и залипаний окон вообще не заметно.

I have an unusual configuration: on my headless gateway there is bitcoind running and on my desktop standart bitcoin is running (both Linux OpenSuSE, gateway 11.1, desktop 11.3, bitcoin 0.3.12 both). TCP port 8333 forwarded on gateway to the desktop (so gateway client can't has incoming connections). I don't know why but when I start desktop client after gateway's one the desktop client can't connect and flickers between 0 and 2 connections for a long time. Eventually it may connect but while it can't the memory leaks badly. About 200Kb/sec (each 0-2 change). It may not be noticed if the client connects instantly but in my case it doesn't. If I start first the desktop and then the headless client (after the desktop one has connected) everything is fine and no leaks (or they are little enough). I guess there is unfreed memory in bootstrap function or somewhere in the bootstrap process.

The number of bitcoins is limited (this number is big but anyway it's finite). So, I'm interested is there a way to recover lost coins by periodically pinging coins via special blocks? For example, your client once per month inserts pong packet with your coins numbers and if there were no pongs from particular coin within a month it's counted as lost and can be used again (generated?). Sorry, I don't fully understand the overall mechanic but maybe it's a way or at least a point to think of.

Another serious question is a snapshotting of coin state. The chain will grow long over time and the client should check it from the beginning to the end to validate each transaction. Things will be slower and slower and eat up diskspace and traffic. I guess each client can make a snapshot at any time and assign all bitcoins to their owners, then form a new basic state to start with. This state will be sent to all new clients (it won't grow so fast because it directly depends on owners number, not on transactions made). To prevent scamming this snapshots should be confirmed by lot of clients, which will make this snapshot individually (for example, each 100000 blocks) and the most complied will be accepted.

Let's discuss. I'm not sure if all of this possible, but anyway tell what you think about this.