Replying to Avatar Matt Corallo

I interpreted your design as “hold funds in a custodial lightning wallet until they get big enough, then pull them on chain”. The problem with step two is now to send them back out over lightning you first have to do an on-chain transaction to set up a swap, which will be a terrible UX for paying lightning invoices.

The design makes a hell of a lot of sense otherwise (it’s kinda the old mutiny model), just have to hold the funds in lightning channels.
Avatar
jb55 1y ago

that's not how https://boltz.exchange/ worked when I tried it. I just pay a lightning invoice and they send bitcoin to my onchain address. I'm not sure what the UX issue is. This can be streamlined with NWC as well. Would just need to create the swap with an API call somehow.

Reply to this note

Please Login to reply.

Discussion

Avatar
Matt Corallo 1y ago

Right, the lightning -> on-chain direction is instant, but the issue is the other way.

Avatar
jb55 1y ago

oh I wasn't thinking about the other way, I was just thinking of ways to custody received zaps. I am optimizing for the non-bitcoiner use case at the moment. most will not have bitcoin to begin with and will be earning it via zaps.

Avatar
Matt Corallo 1y ago

Sure, but once you have given them a bitcoin wallet and they have some bitcoin and are used to bitcoin transactions being instant, suddenly them sending their funds back out being super slow is gonna piss them off :(

Avatar
overpass.network 1y ago

Thanks for clearing that up I couldn't find much for documentation. Still working progress but you're welcome to see what I've got baking in the kitchen websites on my page