Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Buyer payouts on-chain with on-the-fly reverse submarine swaps. #128

Closed
Reckless-Satoshi opened this issue May 8, 2022 · 1 comment
Closed
Assignees
Labels
enhancement 🆙 New feature or request

Comments

@Reckless-Satoshi
Copy link
Collaborator

Reckless-Satoshi commented May 8, 2022

Observation:
New users on lightning seem to be confused about how they can move the Sats to an on-chain address or cold wallet. Usually, after buying sats in LN using RoboSats, they resort to some thrid party service (CoinOS, FxedFloat, Muun...) that charges a relatively large fee.

The swap service, however, might be easy to implement in RoboSats. A user could select to receive the Sats on-chain for an extra fee, and RoboSats will on-the-fly swap the LN Sats received from the seller. The user experience will greatly improve from the seamless swap, while RoboSats service becomes more vertically integrated and can generate revenue from the swaps improving the service sustainability.

Feature requested:
Add the option to submit an on-chain address instead of an invoice for buyer payouts.

Some challenges
Will have to be faced regarding liquidity management. When RoboSats works 100% in Lightning, there is no need to close/open channels often. However, if users start to withdraw liquidity on-chain, the platform node will become a net sink. That will increase the cost of operating the node. There has to be a clear incentive for users to stay in lightning. therefore this feature will at first have a larger fee (~1-2%) to de incentivize its use.

This will be a large feature that will need active maintainance. Many checks will have to be implemented (is this a valid on-chain address? Is there enough on-chain balance to allow this user the new option? Is this order large enough to be offered the option for seamless swap?) Also a new model "OnChainPayment" will be needed and a full fork of the Send Payment to Buyer pipeline both in backend and frontend.

@Reckless-Satoshi
Copy link
Collaborator Author

Implemented and live
#160

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement 🆙 New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant