Here is Diego from Southamerica. We love Bisq and his descentralized exchange… but here in the region there are a lot of cultural differences between Europe, USA and us.
So, I want to hire somebody who go to github and put WU as an option into the Bisq code.
If Bisq don’t want it, I am willing to pay someone to do a fork and create an Bisq option (new brand) to Latam
Hi Diego,
This question has been discussed, have you read the topics? The thing is that you can’t risk charge backs. What people will think about Bisq if they start to get scammed?
What about Localbitcoins? They have WU. And here is no chargeback. When the person who sell, collected the money, then WU can`t do nothing about it and the bitcoins are safe because they were before in bisq
I have not looked closer to WU but I think it should be ok to add it (I assume chargeback risk is acceptable and arbitrator could verify payment in case of a dispute).
I just have to much other hi-prio work to do so I cannot work on that. If you find a dev who implements that would be great.
Today Chris will publish the plan for out phase 0 of the Bisq DAO and any contributor can earn BSQ for their work. So no need to fork, just add value to Bisq and get rewarded.
It’s not about allowing, it’s also about being compatible with the “Bisq transaction framework” (no chargebacks, secure, privacy…)
But hey look, if you can afford to “hard fork” wouldn’t it be wiser to pay your devs to submit a PR on github and then if it doesn’t get merged after some time, you hard fork?
I would suggest to wait until Chris has released the phase 0 document (today), that will explain very well the process how the DAO will work.
@diegotco:
You will not need to pay. The network will pay the contributor. But if you are the “driver” of a feature you are also a contributor, so you can even earn BSQ. Of course you can hire a dev and earn instead of him the BSQ… all options are ok.
@Nolaan: Would be cool if we have a dev for the payment methods. There are several other requests but I am the bottleneck and don’t have time to check and implement.
It requires first to analyze if it meets our requirements (chargeback risk, required data, arbitrator need to be able to verify,…) and if that is met, to implement it in code. It is not very difficult but involves a few different areas (UI, data, translations,…). First time it will take much more effort to learn all, then second time should be much easier…
Before you start coding ping me so I can give you some pointers, so its easier…
As far as I remember, the problem with WU is that in case of a dispute, there’s no digital proof of payment. The only thing you get when making a transfer is the receipt which can easily be faked.