One OB, two currencies.
How a buyer with Dash only will pay for a good that's sold for BTC?
One OB, two currencies.
How a buyer with Dash only will pay for a good that's sold for BTC?
@yidakee , I know how shapeshift works.
My thesis is that going to other site to pay for the good breaks UX and only hardcore dash users like yourself (and me) will do this.
End user always wants smooth experience: see, click, bang. My friends refuse to adopt dash because it doesn't offer mixing on mobile, and you're here breaking user flow even more.
What I am defending is precisely a more elegant solution of actually integrating Dash into OB so it is native and doesn't have to jump through hoops.
There is no solution except the port of code of OB to Dash and submitting to the devs to merge.
Ah, you mean price indexing?
Bob sells a gold watch on OB for 2 BTC.
Alice executes a buy request.
Alice gets Bob's BTC multisig payment address
Alice wants to use Dash, so goes to Shapeshift to exchange and feeds Bob's BTC address + amount of 2 BTC
At that moment you'll lose 95% of users. They simply won't use the service, unless it's a single click.
But the final solution will depend on the ability of buyers and sellers to go through shapeshift to exchange funds!
Are we in agreement on this?
If you can create this so that only Dash can be used, I am in full agreement, but you specified that no, it will only open the doors to other coins.
The ultimate solution is porting OB code to include Dash natively.
.
Are there some obstacles to integrate DASH into OB-client-mainnet?
If you can create this so that only Dash can be used, I am in full agreement, but you specified that no, it will only open the doors to other coins.
The ultimate solution is porting OB code to include Dash natively
If you manage to do this for Dash only, I am 100% behind this, one way or another.