Damus
Ben Weeks ⚡ profile picture
Ben Weeks ⚡
@BenGWeeks
Do we have a way to do non-custodial lightning split payments currently? Either Nostr or Lightning native? By non-custodial here, I mean you pay for a jar of coffee, and a split goes to the bean grower without the seller have to custody the full payment and forward a percentage to the farmer themselves (which the LNbits pay split extension does allow for already today which is cool, but the payer can verify the split).

Currently I think we have presenting the user with multiple invoices to pay (a la @Plebeian Market ), or using something like the zap split extension running on the sellers infrastructure.

I'm thinking NIP-57 splits meets NIP-99 ... although looks to be many limitations of NIP-57 zap splits (no "all-of-nothing", not much privacy, ...).

Perhaps CLINK could integrate a solution for this (at least a partially better solution)?

#ZapSplits #Markets #NostrMarkets #GammaMarkets

@Plebeian Market @Conduit.Market @Ben Arc @Jake⚡️ @Richard @LightningPiggy @Gamma Markets @Justin (shocknet) ⚡ @Chiefmonkey @jb55 @Vitor Pamplona
8❤️5👀1
Jurjen de Vries · 5d
Following this, looking for this solution for some years now
Justin (shocknet) ⚡ · 5d
Could possibly add a split payload to CLINK offers responses that loads n additional invoices or offers for other parties. The primary offer publisher is still trusted to serve those though, but, never holds the funds themselves. Alternatively, chain n offers together into one string, with a delimi...
Ben Arc · 4d
I think that with the cafe selling the bag of coffee, its impossible to avoid trust. I bet there is something clever you could do with the supply chain, as in get a proof, attached to an identity, for all the people who were paid at point of sale. We have LN and nostr, it must be possible.
Johnny · 2d
nostr:nprofile1qqsfw9s4ku9dnmyfd7x4hg8j6qt99uwluhuuakq6e9rfefl6emaddzc54hau0 the all or nothing gap is the real blocker, zap splits fire as independent zaps so one leg failing just underpays the farmer. atomic multiparty needs something like ptlcs or a hold-invoice coordinator that settles every leg...