Jump to content

leobel

New Member
  • Content Count

    3
  • Joined

  • Last visited

  1. @Dogowner5 I think you are right, I was looking into the wrong layer of the stack. I was trying to get access to liquidity using DEX on XRPLedger and after reading this: https://ripple.com/ripplenet/on-demand-liquidity/? I notice ODL from the Ripple point of view is something quite different . Looking to @jn_r example, steps 7 and 10 seems to me are critical in a business model since the company who provided the services (Moneygram on this example) could end without liquidity if there is no such offer by the time it'll try to take it on both steps (loosing the transaction atomicity) or could end with a total different exchange rate than the one presented to the client initially. When I was thinking on get liquidity using DEX upon XRPLedger that was the main concern, though we won't have the atomic issue, we will have the problem to guaranteed the execution of the transaction at the given exchange rate. We can preserve the exchenge rate with tfLimitQuality flag but we can't guaranteed that the execution will be executed successfully. Thanks for the time to reply to me, I'm just starting to understand all this technology and I don't have any previuos experience in the field, so I really appreciate your effort and explanation.
  2. @jn_r thanks for the response. If I get it right ODL is basically obtained by offers that will provide you the asset the offer is trying to exchange whether XRP or IOU's. How would you get access to an asset X if there isn't anyone else trying to exchange it? If you get ODL through a XRP transfer that means there is someone "out there" wanting to exchange/offer those XRP. By "out there" I mean there is a path you can follow to get to that exhange/offer without generating undesired debts along the way. What do you mean with Like IOU/DEX mechanism, you have XRP/DEX mechanism and both together give you all the possibilities to have ODL.
  3. Hi. Recently I started learning about XRP ledger and reading the documentation I found this line from the Default Paths section: I'd like to someone explain me the reason behind this statement. I guess that if a gateway A (an issuer) wants to get access to the on demand liquidity that other gateways (supposing they allow ripple) could provide, there are two options to accomplish that. Create trust lines directly to those gateways. Wait until an account create trust lines (maybe indirectly through an offer) with those gateways and with gateway A. It seems to me options 2 is out of gateways A control since it cannot force other accounts (I'm thinking about customers from the gateway A perspective) to create trust lines with other gateways and the better they can do is provide a sort of list of gateways for the accounts to choose from, but it'll be a more complex and extra step process. Also if the account decide to (or have) disable ripple, you won't get access to the other gateway on demand liquidity right? Maybe there are more ways to get access to other market on demand liquidity and I'm not seen it?
×
×
  • Create New...