I would trust liquid over random mints any day. still too much of a custody maxi to use liquid though lol
Discussion
Lol, yeah. I see liquid as my pocket money where I can side-step onchain fee spikes like we had during the halving. I’m not religious about any particular tech though and will use whatever has the best trade-offs and UX. If we can solve zaps with self-custody tech, that would be ideal obv.
my biggest concern is losing the *option* for self-custody. when you build a protocol that excludes easy ways to do self-custody for people who want that, then that's a problem.
Well users can swap to onchain self-custody with integrated boltz. But I agree it’s not as seemless as hosted channels.
This was my original plan with the damus wallet. Occasionally swap to onchain when you hit a certain balance, but you lose the ability to spend those funds after you do that. Hosted + graduated channels are cool but require bolt12 for good ux and nothing is really built out yet 🥲
nostr:npub185h9z5yxn8uc7retm0n6gkm88358lejzparxms5kmy9epr236k2qcswrdp are we correct to assume that hosted channels would require async payments (and broad bolt12 adoption) to allow self-custodial zaps?
I mean hosted channels are just custodial wallets, they don’t *need* anything :). Still, I don’t think async payments are *that* required even for non-custodial - they solve an important problem but for apps people use, the on-notification hooks provide relatively good results, and the upgrade path to async means we can improve it as we go.
Yeah, if the receiver phone has an internet connection receiving on phoenix works relatively well while the app is in the background. I guess async solves for the cases where the phone is offline for extended periods of time. But since zaps are mostly not mission critical, but tipping for shitposts, it might work fine without async payments.
