Interoperability with Liquidity Pools / AMMs #129
Replies: 3 comments 1 reply
-
I'm not sure how we could do this without there being some minimum amount guaranteed at withdrawal. However, I think we could have payment channels support deposit to and withdrawal from liquidity pools as coordinated activities, and if there are pool shares in the disbursement at close, the participants can then withdraw the original assets using the pool shares after the channel closes. This idea requires support for transferrable pool shares, which I believe is not currently supported by CAP-38. |
Beta Was this translation helpful? Give feedback.
-
Just adding a bit more context here for others, I think the main rationale here is that "locking" funds in a liquidity pool is better than simply "locking" them in a Payment Channel: by locking funds, in theory you're losing money due to inflation, whereas in a liq pool you're accruing interest. I think this is a good problem to solve, but I'm not sure this is the layer in which we'll solve it. I would love to keep the PC protocol as simple as possible, since even at its essence it already has a non-trivial number of possible states. A "simple" way to solve this one abstraction layer above would be to instead of locking |
Beta Was this translation helpful? Give feedback.
-
Some initial ideas/use cases:
|
Beta Was this translation helpful? Give feedback.
-
Update 2021-11-03: Liquidity pools / AMMs were introduced to Stellar in Protocol v18 via CAP-38.
@nickgilbert suggested we think about how this payment channel design could interact with liquidity pools to hold the assets in the payment channel in a liquidity pool.
How could we support holding the assets of the payment channel in a liquidity pool for the duration of the channel?
Beta Was this translation helpful? Give feedback.
All reactions