Quote from: DarkDays on August 26, 2016, 07:03:15 AM

...

Thanks for killing my action.

My only issue is that if I say "send my transaction paying 300 bits for the fee" and you send the transaction with 240 bits for the fee, that rubs me the wrong way. Even if the transaction gets confirmed in the next block. It's the appearance of impropriety. Even if 240 was all it took, and even if sometimes you charge me 300 and you spend 500, if I say "use 300", you should be using 300.

It seems to me that a better way of doing it would be to say "do you want this medium priority or high priority" and showing the average fees each option takes, and then deducting the exact amount of the fees you pay (as directed by the customer) from the withdraw.

It's not about that. MoneyPot is using a flat rate, because they have to bundle inputs for a transaction. Sometimes a transaction consists of just one input, which doesn't cost much, fee wise. Sometimes it consists of many small inputs, what would result in a very large fee. In that case you are still only paying the flat rate fee.

So over all the transactoins that MoneyPot processes, it averages out to about that flat fee. It's a win/win for both MoneyPot and it's costumers. Because the transactions with a lot of small inputs can be a big pain in the ass sometimes. It just gives the best user experience. Most of the time it is already included in the next block, so it is a good system. For the times it isn't included in the next block, you have to wait a bit more. Even with a higher fee, you have no guarantees.

Btw, people complained about this before. That's understandable, because the way they handle this, was not mentioned anywhere. Now you can read it on the 'Send' tab. It is just a implementation choice. And the best one in my opinion.