Poll: Bitcoin-Qt Version 0.8.2

[The 4ner]

So the new version is out, and if I recall correctly there was some controversy regarding the exclusion of small payments. Now, from what it looks like, Gavin has released a stable version of 0.8.2 (https://bitcointalk.org/index.php?topic=219504.0), and I'd like to know how many in the community are upgrading and how many are still aroused about certain payments being excluded from the blockchain? Vote away!

[escrow.ms]

I'm upgrading as i hardly do small transactions.

[MysteryMiner]

Will upgrade eventually just for the little memory and performance gains (I'm using Pentium4 2.0GHz Socket423 768MB RD-RAM right now).

There should be user configurable options for the small transaction handling. Developer team dictating how software and network enforce arbitrary rules are bad.

The small inputs from faucets already were problematic on tx fees since version 0.3.21

[The 4ner]

Can I have this thread moved to Bitcoin Discussion? I feel that by me placing it under Off-Topic it will very likely be ignored and not receive sufficient votes to make the poll a worthy source of info.

[ikal]

Hi everyone

I use 0.8.3 with win 7

because 0.8.3 really reduce the p2pool "Bitcoind GetBlockTemplate Latency" limit in 1s, my pool is Getwork Latency
-Mean: 0.333s

so I accept 0.8.2

[escrow.ms]

Hi everyone

I use 0.8.3 with win 7

because 0.8.3 really reduce the p2pool "Bitcoind GetBlockTemplate Latency" limit in 1s, my pool is Getwork Latency
-Mean: 0.333s

so I accept 0.8.2

0.8.2 is the latest version, How can you use 0.8.3 O.o

[westkybitcoins]

It's a default setting that can be turned off (reduced to 0.00000001 BTC, anyway, IIRC.) There's no reason for me to not upgrade, especially since I'm pretty leery of SatoshiDice's benefit to Bitcoin.

Even refusing to upgrade in protest would do no more for me than just upgrading and reducing the minimum.

[Eri]

Since this thread is short ill add this in plain text.(for everyone saying No or Maybe or Yes and not understanding)

(simplified!!)This update prevents people from sending amounts that would cost you more BTC to send, then you just received.

A transaction doesnt just link to a number, it links to each source transaction. so sending BTC from many many tiny transactions will make the fee so high that your spending more to send it then you have.

Simplified example.

You receive  1$ in 1 penny transactions. the fee to send it is 1.25$ because of the size of the data included to make that transaction. if you had received 1$ in a 1$ transaction the fee to send that 1$ would have been 1 penny.

This update prevents you from losing money for work on random sites. But and i want to highly stress this. you shouldnt send(or want to receive) amounts near that amount anyway. since most of it will be lost via a transaction fee!

[cWq34#9tH-3]

I don't mine bitcoin. I just use the client as a wallet and I'm wondering that since I have to pay to process MY transactions... Is there a setting where I can set the client to refuse transactions unless I get paid? I apologize if this is a stupid question. I am new to this.

[BitcoinAshley]

I don't mine bitcoin. I just use the client as a wallet and I'm wondering that since I have to pay to process MY transactions... Is there a setting where I can set the client to refuse transactions unless I get paid? I apologize if this is a stupid question. I am new to this.

You are not a miner so this is not relevant. No worries. 


Consider the 0.8.2 dust tx change this way: The MAF sensor on your car might have some fancy security torx bit holding it on. The only reason it has this and not a normal philips screw or hex head is that the carmaker had some deal with Torx so that Torx could sell more proprietary bits. It was unnecessarily complicated and required a special tool.
Gavin took the car and replaced the fancy torx bit with a normal hex head. So now (to mix metaphors) instead of reconfiguring and recompiling the code, something many miners would have no idea how to do (Since they don't own a fancy torx bit) they can just stick the standard hex wrench into their .conf file and choose which size tx to accept.

Now, we can argue all we want about the default being set to a certain value, but the increased configurability is not as  controversial seeing as it already kind of existed... it was just a little obscure.

[kodo]

Yes it works fine