It's great that foolazz22 raised this question, I know it's not the mixer's fault but what happens when fees are pretty high, in other words, in order to refund him his $15 at least $10 of it will go in fees, on the other hand, setting low fees might make the transaction stuck for a very long period of time.
What I propose instead, if possible, is to give the user enough time to add a second transfer to bring the total of his deposit to 0.001BTC.
If we had to choose between convenience and security we would choose the latter every single time. We considered allowing more than 1 transfer to the same deposit address but ultimately decided against it because we do not want to introduce any possible attack vectors. Right now there are <20 BTC in the multi-sig, but once the balance grows to hundreds we will certainly become a very attractive target for hackers so we simply do not want to take any chances.
The minimum amount is clearly stated so it's the user's responsibility to carefully read all the information and warnings. If the system was decentralized already there would be no refunds in cases like this, or if the user lost the private key. Since that's where Whirlwind is going we believe it's best if we handle support cases same as if the service was already decentralized so users get accustomed to it.
Unless users make mistakes there is simply no way for any 'errors' to happen, so we have no reason to fix something that is not broken, especially if it means that the entire service would become less secure.
I have a concern regarding on my recent action, Is it safe attaching my unique link on support email? Also why does the Guarantee Letter keeps changing whenever I download it. I downloaded it twice and it gives me 2 different Guarantee Letter .txt files. Are both letter valid?
If I assume correctly you used the Clearnet website, and if you did then it's normal. It's the same Guarantee Letter, but the .txt file is named differently because of our extra encryption layer.
@whirlwind.money not that I’m worried about my balance but there’s no reply on my email acknowledging that someone already received it for almost 24hrs when the email sent. What’s the typical duration for a support to handle cases on email?
If the case doesen't involve any manual intervention from our side then the response time is usually under 6 hours, if it does then it's usually 24 hours or more.
Also I’m already the second one here that forgot to download private key when mixing since this is not the norm on mixing. Is it possible to have a simple mixing process just like before that doesn’t need to deposit the balance on note so that we can mix directly without going to the dashboard to mix. I have a plan to use the note for anonymity mining but not using the current funds.
Saving the private key may not be the norm, at least on Bitcoin, because no other service works in the same way. We certainly do not see this as a valid argument for why it would be a good idea to adhere to the current 'norm'. If we were to go down that route then Whirlwind wouldn't be what it is today, and we would simply be just another 'traditional mixer'. Considering we believe those systems are fundamentally flawed and that's the sole reason why Whirlwind even exists, it would be quite hypocritical from our side to back down right now just because 2 users didn't properly read the many warnings displayed on the website. Only at the first step there are 3 warnings displayed, let alone the FAQ:
1. The first step is named 'Generate and Save Note Private Key'
2. Immediately after you click 'Generate' you see this text under the Private Key: Save this note someplace safe. | Losing this note means losing access to your deposited funds.
3. If you hover over the 'info' button you will read this: IMPORTANT! | Make sure you store your Note properly, it is a private key and therefore support can't help if you lose it.
It would be possible to introduce the 'Fast' mode again, but that wouldn't make much sense because as soon as we transition to the zk-SNARK based Note system we would have to scrape it again, and that would only add more confusion.