simple problem more mixing more fee
0 mixing
0.005
10 mixing
0.05
100 mixing
0.5

As a general rule, any new sister thread shall be moderated. Reason 1 is all our thread (even the FAQ) are filled with shills. Reason 2 is we have for long a reputation of not abusing of the self-moderation feature, so we shall not fear rejection anymore on this ground. Reason 3 of course is that it will be saner to read for anyone.

As well as two contractants: a chef and a servant (although it was only partially paid in XMR).

It should be fee-per-kb since the amount of data is more fundamental and adaptive than what the data is. Dust attack have been used on the blockchains of Bitcoin, Litecoin, Dogecoin and many others in the past. It's easy to put a stop to with a fee that's fine for a normal user but quickly adds up for a malicious attacker. Monero's is currently unusually low -- I don't think going even an order of magnitude higher would have much effect on regular users.

Not directly. They pay out multiple users at one time, which means one fee, not one fee for each 0.1 XMR payment. When users spend the 0.1 payments, they generally combine several of them into one payment, so again one fee. So the higher fee is still possible workable without other changes. Pools may wish to increase their minimum payouts or let users set higher minimum payouts to reduce fees though.

For those that lurk in #monero-dev -


[23:12:40] monero (~monero@192.30.252.43) joined the channel.
[23:12:40] monero: [bitmonero] fluffypony opened pull request #104: Fees temporarily bumped to 0.1 XMR per tx to prevent spam attack (master...master) http://git.io/9_lUdA
[23:12:40] monero (~monero@192.30.252.43) left the channel.
[23:12:55] monero (~monero@192.30.252.32) joined the channel.
[23:12:56] monero: [bitmonero] fluffypony closed pull request #104: Fees temporarily bumped to 0.1 XMR per tx to prevent spam attack (master...master) http://git.io/9_lUdA
[23:12:56] monero (~monero@192.30.252.32) left the channel.
[23:13:01] @fluffypony: oh well, at least they tried

aye aye capn'

Monero devs kick ass noone can even deny it anymore. Attack the block chain and they are on it within minutes, a whole team of them. Fuck yes

Over and above updating, either from my repo (http://github.com/fluffypony/bitmonero) which I won't rebase for the next couple of weeks or from the main repo, if pool operators and solo miners could also delete their poolstate.bin before restarting the daemon. This will ensure that the several hundred silly spammy tx's already in the mempool are kicked out by virtue of being silly.

To wit: update and compile; stop the daemon and simplewallet; delete poolstate.bin from ~/.bitmonero or the Windows equivalent; replace the daemon and simplewallet; restart the daemon and simplewallet.

Ok, dude, we are pool ops and we are paying tx fees from our profits. Now, when fee raised 20 times, it's significant impact. We just not ready.
BTW, you can donate to https://github.com/zone117x/node-cryptonote-pool so he will collaborate with devs in order to provide smooth migration for both miners and pool ops when major update to tx fees come.