Just to clarify two points:
> The good part is that it does not have to be adopted by exchanges. If popular
> exchanges do not adopt it, it is trivial to make an adapter service which
> translate COX to whatever proprietary API of the exchange.
Be sure to elaborate on the difference in trust
Thanks a lot for the feedback
> I think this could be quite useful, although I don’t know if it will get
adopted.
The good part is that it does not have to be adopted by exchanges. If
popular exchanges do not adopt it, it is trivial to make an adapter service
which translate COX to whatever
I think this could be quite useful, although I don’t know if it will get
adopted. If any such small local exchanges want to weigh in on this proposal,
that would help. Same goes for shopping cart integrators, e.g. the folks
writing WooCommerce and Shopify plugins.
Consider adding some
currencyCode and cryptoCurrencyCode seem to assume that merchants will
always want to sell for fiat. But a merchant might want to sell for
another cryptocurrency instead.
Why not make it more generic, like buySymbol and sellSymbol?
> "currencyCode" : "CAD",
>
Hi everyone,
As some of you know, I am working on a complete open source replacement of
Bitpay for allowing merchant to accept cryptocurrency payments while having
a way to sell automatically.
A crucial, missing part, is fiat conversion. And I figured out a simple
protocol that exchanges (or
