Quote from: DarkDays on August 26, 2016, 12:05:27 AM

Quote from: Quickseller on August 25, 2016, 11:25:24 PM

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.

It's exactly how it should work. If I say "take 300 bits out of my withdraw and use it to sent it", they should take exactly 300 bits and use it for the fees. If it takes longer than a block, that's on me.

Based on many people I've spoken to, it doesn't appear that this is possible. BTC fees are based on transaction size and nothing else. The client lets you pick your fee per kb. The issue is you don't know how many kb you're using (or bytes) until after it's been created. Look at the Bitcoin Core code yourself for further verification, since you don't want to believe anyone else.