Revive ripple-client-desktop

Update: as of Jan 15, 2019, trading is working.

The first goal is to make it fully functional with RippleAPI.

Current status is most read only operations are working except order book.

Please follow this twitter thread for the most recent updates:
This weekend I tried to revive ripple-client-desktop. l I have reached a point at which I can run gulp without any warning on the command line. However, the app stuck at loading. Then I figured out that the client uses an ancient ripple-lib API. — r0bertz (@r0bertz) December 17, 2018

How exactly is XRP going to work as a bridging digital asset?

Maybe this is obvious all along to some people. Anyway, I just figured this out. So I thought maybe it's worth sharing.

Previously I thought the bridging consists of two transactions, both on XRP ledger. One from fiat currency A IOU to XRP, the other from XRP to fiat currency B IOU.

Then I saw this:

So Miguel Vias said in the pilot they used liquidity on bitstamp and bitso. However it's seems the trading volume of XRP/bitso.MXN since the beginning of 2017 is so low that it's virtually no liquidity there. See this:

Then I realized, just like bitstamp, bitso has its own exchange and the liquidity there is much better.

So now it's clear to me there is another way for XRP to bridge cross-border payments. The originating party acquires XRP however it wants, buy XRP on XRP ledger using source fiat currency IOU or buy XRP on an exchange then withdraw to its ripple wallet on XRP ledger. Then it deposit the XRP to an exchange. This happens on XRP ledger. Then buy the destination fiat currency using XRP on that exchange. All of these can happen very quickly since transactions on exchanges are also fast.

Does this make sense? Let me know your thoughts. Thanks!


Popular posts from this blog