Our fee policy is published (you didn't read it), we are trying to protect the blockchain from flooding (and optimizing our blocks).
Did read it, but I'll include it here for those who didn't.
Deepbit's transaction fee policy
(This is not related to the pool's payments to our users)
We think that free transactions are very important for the Bitcoin system so we are including as much free transactions as possible into our blocks, possibly more than anyone else. But sometimes a fee may be useful, so here is our fee policy:
A transaction is considered to be 'free' if the offered fee is less than 0.01 BTC. Free transactions are only accepted if they are less than 2000 bytes in size and have no more than 5 outputs. Outputs less than 0.01 BTC are not allowed in free transactions. The minimum fee for non-free transaction is 0.01 BTC for each started 1000 bytes.
As I read that policy, anything less than 0.01BTC transaction fee (200x greater than what the bitcoin client considers the minimum) is considered "free" (unless it's payments to your users) falling into a bin of indeterminate behavior on Deepbit's part. Today you process a percentage of "free", choosing to not process some percentage of "free".
You're correct. That's your right. It's your hardware, it's your bandwidth, it's your money spend to offer the pool as a service to your users.
I'm just saying, given the current distribution of transaction fees, this choice is causing some transactions to take a lot longer than others, because somewhere between 30%-40% of the networks hashing rate (depending on the day) may choose not to process your transaction, because it doesn't pay them well enough.
Not saying evil, just saying.. It is what it is.
And people should be aware
