rich1.0npub1d7e068ud72v0au6xf53qvek44eccfhlgnhzuclf6za6hnxrvx89sc93exjhttps://nostr.ae/npub1d7e068ud72v0au6xf53qvek44eccfhlgnhzuclf6za6hnxrvx89sc93exjnjumphttps://nostr.ae📅 Original date posted:2021-12-15 📝 Original message: On Wed, Dec 15, 2021 at 01:59:49PM -0800, William Casarin wrote: >Hey Ronan, > >On Wed, Dec 15, 2021 at 05:33:51PM +0000, Ronan McGovern wrote: >>If not, what would be required to develop this? >>* A protocol change? >>* Could it be built with the current protocol (I see an app on LN Bits to >>split but it doesn't seem to work). > >This is typically done at the application level. The fountain podcasting >app works this way and it seems to work okish. The tricky part is what to do when the payment partially fails. Perhaps you keep trying with exponential backoff until the payment completes for all parties. If this was handled at the protocol level, would you fail the entire transaction if one of the channels failed? This is the kind of business logic that would be tricky when designing a protocol-level solution to this. I think it's reasonable to handle this at the application level for now, but perhaps some standard protocols might be useful in the future. Cheers, Will