Quote from: DarkDays on August 25, 2016, 10:23:33 PM

Quote from: Dogedigital on August 25, 2016, 09:49:40 PM

Quote from: DarkDays on August 25, 2016, 09:27:13 PM

Quote from: Dogedigital on August 25, 2016, 09:23:12 PM

You're more than free to voice your opinion (I don't think it really warrants negative trust however).

The issue at hand has been explained multiple times. I don't believe I can find a new way to put it that will be to your satisfaction, but I just want to stress again that it is not setup for us to profit.

I do admit that we have fallen behind on schedule, but by no means are we losing focus or effort (I've been dedicating the majority of my waking hours to Moneypot).

We are here to build a long lasting product and service in the cryptocurrency space.

If you give the user the option to choose how much to take from their withdraw to use on fees, you need to make sure that you use that money on fees.

What if we take 300 bits, and the fee ends up being 3000? Do we go after the user for that as well?

It's a 2 way street. We sometimes profit (a negligible amount), and sometimes we lose. This version is much simpler, fluctuates with the blockchain, and the user only has to pay the fixed fee regardless of what it actually happens to be (bigger or smaller).

If you take 300 bits as the fee, you should send the payment with 300 bits as the fee. It's so simple. Why would you do anything else? If you give the user the option to choose how much they want to pay...out of THEIR MONEY...as a fee, just send the payment using that as the fee. You should never be profiting off of your users in this way, that's horrible.

That is not how it works. If MP were to take 300 bits as a fee, and include a 300 bit fee, they could potentially take a very large number of inputs, and use them to fund your withdrawal - this would result in your withdrawal transaction taking several blocks to confirm verses if only one input was used. It is also possible that the mempool is almost empty, and could include a transaction fee of 50 bits that results in the transaction confirming the very next block.

It is also possible that MP could contract with several of the major mining pools, never attach any transaction fee to their withdrawal transactions, yet their withdrawal transactions would almost always confirm within 1-2 blocks (they would most likely pay to get their transactions confirmed separately). For the super paranoid, it is also possible that MP charges you 300 bits on your withdrawal, contract with several mining pools, then receive a 100 bit refund from the pool that confirms the transaction (I do not think they are doing this).

I am not sure how the various transaction fees are described on the withdrawal page, however IMO they should be described that a withdrawal transaction that is estimated to be confirmed within 1-2 blocks will cost 300 bits, a withdrawal transaction that is estimated to be confirmed within 3-4 blocks will cost 200 bits, and so on. MP can charge amounts that they feel is most appropriate, and they might want to charge their prices occasionally depending on the long term costs of getting transactions confirmed.