[bisq-network/bisq] Chat between trading partners to end frustration during long trades (#2540)
notifications at github.com
Fri Mar 15 13:48:38 UTC 2019
Thanx for your quick answer.
Saw this as a feature request. If the issue tracker is not for feature requests i'm fine with closing it.
> After the DAO is out we will work on improvements for the trade protocol which includes that you can get in touch with the peer and that there is an mediator before it goes to arbitration.
> If you are sure that something went wrong you can open a dispute with cmd+o.
Thats the problem. I'n not sure at all. I'm waiting for 3 days and I have no idea if there is a problem and what it might be.
> But if the peer needs longer or the bank is slow there is unfortunately no good solution yet.
Thats not actually a problem for me. If I KNOW the peer needs longer, I can accept that. If I KNOW the bank needs longer, I can accept that. The problem is, that I have to wait one week before any communcation can take place.
If the trader tells me after 3 days, he hasn't received the money I know whats going on and I can wait. The frustration comes from the potential 7 days without any info or communication.
>The longer trade period for SEPA is required as some banks need 2-3 days and if there are holidays and weekends it gets longer. Though I think most trades gets settled much faster. Might be a bit of bad luck that you traded with a peer who had a slow banks or he was slow with sending the funds.
True. But you can compare it to the frustration if the subway isn't coming.
A) Without getting any info at alland
B) getting an explanation what happened and an estimated delay.
> Atm we have a few p2p network issues so it can be that you do not receive the confirmation of the peer that he sent the funds.
I read it. Thats ok. I restarted bisq several times.
> Regarding deleting data:
> You never have any proof that the peer has not made a copy. Deleting data is basically impossible from a conceptula point of view.
True. Just added this in case the argument was "We can't have any chat because of anon concerns". Don't think this is a problem.
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the bisq-github