New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add additional information for security deposit #1216
Comments
Actually on this screen I think we should write:
instead of:
I don't think it makes it easier for the user to understand what this security deposit is all about by talking about the user in the third person IMO. |
looks good, some suggestions:
|
I wasn't sure if you'll loose the security deposit in any case you cancel an ongoing trade. |
loosing => losing
…On 9 February 2018 at 13:45, Christoph Atteneder ***@***.***> wrote:
And here is the version for creating a sell offer:
[image: security deposit seller]
<https://user-images.githubusercontent.com/170962/36028468-5a5011bc-0d9f-11e8-8ddc-2c37f0bac525.png>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1216 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABZb3gPptAUTXYWA3zrdUwejk9bBe1bIks5tTD36gaJpZM4RirLi>
.
|
Thanks for pointing out the typo! I'm also not sure if we should talk about "canceling a trade" as there is no real "cancel" button, but more a not following of the trade protocol. Not following the trade protocol on the other hand sounds very complicated to me and I would immediately be afraid, that I could lose my deposit if I'm doing little mistakes. |
That may happen depending on the circumstances and details of the case. I'd leave it out here for that reason. But perhaps more importantly, I'd leave it out because it's irrelevant and confusing to talk about it here at all. In the screenshot shown at #1216 (comment), the maker-as-seller is specifying the security deposit that the buyer must pay in order to take this offer. Telling the seller that they will lose their security deposit if the cancel after the trade is taken is a non-sequitur here; I mean, even if it were perfectly true, it doesn't have anything to do with the decision that the seller needs to make here, which is all about the buyer's security deposit, not their own. Likewise, I'd kill the note about the security deposit being returned after the trade completes. That is again true enough, but irrelevant in this context. Also, it's "lose" your security deposit not "loose"—this is a common error, even for native speakers. I really like the way the hover looks by the way, with regard to color, iconography and slider! |
By the way, @ripcurlx, I'd be happy to chat about this topic sometime next week. Real-time discussion might be most efficient in sorting some of this stuff out. Just let me know if you'd like to do that. |
@cbeams and @ManfredKarrer: Yes, maybe it would be best to discuss everything regrading the security deposit in a quick call today. Would 6pm (CET) work for you guys? |
I’ll take this to Slack for coordinating a call, thanks.
… On Feb 12, 2018, at 9:05 AM, Christoph Atteneder ***@***.***> wrote:
@cbeams <https://github.com/cbeams> and @ManfredKarrer <https://github.com/manfredkarrer>: Yes, maybe it would be best to discuss everything regrading the security deposit in a quick call today. Would 6pm (CET) work for you guys?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#1216 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AASa8s9yhebEB3SAxCtPf9hzjLtMKCzbks5tT_DkgaJpZM4RirLi>.
|
@ripcurlx There is still some missing context: I think the deposit should not be shown in the payment method as that is the users payment method (he can have multiple - then there is a dropdown). |
Re: warning if outside of recommendation: |
A high deposit means more security for seller. A low deposit means less money locked up for buyer. A maker as seller who wants to attract buyers can set it low, taking more risk of cancellations. |
I think we should use the volatility alone and remove the option that the user can set it. See #1346 |
Yes, I would also prefer a solution, where we don't have to educate the user about the correct usage. |
This issue is blocked until the automatic deposit setting is implemented. |
Btw. We should change the defautl sec. deposit to a % value based on the trade amount. That wooudl reflect then the volatility. E.g. if you expect that the BTC price will go up or down 5-10% then you should set the deposit to that % value. Default might be about 10% but should be delivered by a service anyway. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
1 similar comment
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because of inactivity. Feel free to reopen it if you think it is still relevant. |
Still relevant. |
I profit from this thread. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because of inactivity. Feel free to reopen it if you think it is still relevant. |
At some screens we don't explain the reasoning behind the security deposit (e.g. Create offer). On all screens where we require the user to accept or change a security deposit we should display a information icon, that explains the reasoning behind it and what value a user should go for.
Create offer to sell
The text was updated successfully, but these errors were encountered: