Topic: Boycott 0.8.2 - page 11. (Read 18974 times)

I declare a counter-boycott, with a .0005BTC value threshold for relays! Push the dusty bastards to LTC!

Any miner you can convince to boycott 0.8.2 is a miner you can also convince to change a line in their bitcoin.conf file.

There's still no excuse for all the whining and drama.

If you don't like the default value that ships with 0.8.2 all you have to do is add a line to your bitcoin.conf file with a different threshold. You can even set it to zero if you want. That's much better than previous versions because with them you had to patch the source code and recompile to change these values.

Problem solved - there is absolutely no legitimate reason to keep whining about this.

that's the definition of boycott

Don't have to boycott, for those who don't want it, just don't install.  Or better still fork your own coin.

for the moment...don't forget, we still are boot strapping.  The purpose is to limit block chain size growth while the network infrastructure matures. 

Your reasoning is backwards, if the price goes up the limit should be decreased to keep the balance, not the other way around.

Just saying.

A large enough fee can buy almost any valid transaction a place in the blockchain.  Why anyone would want to spend a high fee to insert an unspendable amount into the blockchain is unknown to me, but you are free to do it.  You can even send 0 BTC if you want to, but expect to pay a decent fee to get it mined.

When I started using Bitcoin, and Satoshi was still active, it was impossible to send less than 0.01 BTC using the standard client.  Looks like it was a big mistake to make it too liberal in later versions.  When the default client settings move back slightly towards what they used to be, due to the irresponsible spam of unspendable transactions, people who don't have a clue about how Bitcoin works start screaming and whining about censorship and whatnot.

If all your peers are running with the settings at 0.0001, then this happens as they drop it:
2013-05-06 20:29:16 ERROR: CTxMemPool::accept() : nonstandard transaction type
Your client will keep retrying and eventually it might find a peer that will relay it, and with luck it'll reach a miner that will mine it.

Of course, since 0.8.2 changes it from a hard coded, compiled in setting to a user-setting then who knows?  It can be lowered and 0.8.2 gives people the choice.  Heck, people can even increase the minimums on their p2p node if they wish.

Hi you can not transfer less than 0.001 bitcoin to be able to get in to the queue to get in to a block. So it is impossible already.
If am wrong please explain how i can transfer 0.00005395 from one of my wallet to an other ?
As it is now no one is willing to relay that transaction through the network.

If we refuse to upgrade will we be treated differently when it comes to making transactions with small amounts? Will we even be included in the blockchain?

Lets hope so. Point is, the decision will be made to do this even though it is wrong to do in the first place.

I'm no religious person by any means, but thank god for open source, no matter how this turns out there will now always be alternatives.

I explained this a hundred times and it is just going in a circle, you can get find my answer here or in another one of these threads.

You keep calling it censorship, and trying to control how you spend your btc... Well lets flip that around, as a miner you are telling me that I have to include every one of your transactions no matter what. And I should spend my resources confirming your transactions just because that's what you want. However if I choose to only include transactions that have a fee attached I'm censoring you? You (and anyone else) are free to broadcast as many transactions as you want, of whatever size you want, however you are not free to tell me which ones I have to process or the order in which I have to process them. So as a miner if I decide that from this point on any transaction I include in any block I process will have a 0.001 fee or I will not work it how am I censoring you? Sure I'll include your 0.00000001 transaction but it will cost you 0.001 for me to do so, why? Cause that's my cost to run this node, you don't like it? Run your own node or someone else can pick it up for less and once it's in a block everyone will carry it.

I also read where this is the first step in automating the minimum tx fee. At this point, seeing as this is not done, we can only speculate on how this will be implemented. I for one hope that whatever I pass as a command line argument or set in a config file will override the automated method. But I will reserve judgement on that.

It also calculates the threshold where a transaction can't be spent without costing so much in fees that it's not worth spending. This is derived at runtime from the values you quoted.

And if such a "dust" transaction comes through the p2p network, it ignores it.  If a miner mines it, then so be it, but the node itself won't contribute to propagation of the dust spam.

Miners can set this threshold at runtime easily instead of having it compiled in.

It is so much more than... so please read this thread and you will see where the problem lies.

I did, I read the code the only real change in the behavior is it's checking a run time variable vs a constant.. and said run time variable is different then the constant, if one wants the old behavior pass old value to new run time variable. Or if really concerned write a patch that changes that magic number back to the old magic number and put in a pull request.

If you actually read you understand but you are clueless, so I take pitty on you.

Storm in a teapot.