pull down to refresh
There's been solid progress with these main approaches in the past year, hopefully the same ones you referred as "suggested ways":
Trampoline / LSP-mediated approach where an intermediate node holds the HTLC until the recipient comes back online. Éclair has had implementation work here for a while.
PTLC-based async payments that is the fully trustless approach favored by Matt Corallo. It uses Point Time Locked Contracts so the holding node can't steal funds.
Onion message signaling where the sender's LSP holds the payment and waits for an onion message from the recipient's LSP indicating they're back online to release the payment. This is the approach LDK has been building toward and Bitcoin Optech has a great topic page tracking all of this here https://bitcoinops.org/en/topics/async-payments.
Voltage also has a good overview here: #295133, and a more recent post on why this matters for mobile/self-custody nodes #1287485.
A broader look here by @roy and team #399604
Here few more:
But do not exclude:
"There's no such thing and never will be, anything above the chain is inherently interactive. These are immutable physics."
—@justin_shocknet#1287707
... that somehow is right, we can perhaps just simulate it, giving the user the illusion "Async" or "Offline" payments in Lightning. Good UX~design can do that.
@chess d4 not invited?
Good one. Open Source https://github.com/Quizzicarol/Bro
Few movies are worth watching these days, this is one of them with unexpected ending! Anyone else has seen it?
let's try...
Call upon @Salomonsatoshi in the posts of trouble; the penultimate ruler of downzaps. She will deliver thy request and honor us all.
live stream link?