To implement async payments to intermittently online channels, there just needs to be a notion of charging fees on this caching by time.

The last hop is where the problem usually lies, so the sender, or the invoice path onion generation needs a special layer type which makes the hop a short term custodian.

Getting this problem solved would be a huge boost for lighting adoption.

Reply to this note

Please Login to reply.

Discussion

No replies yet.