bLIP-0066, Static Invoice Server Protocol #66
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
valentinewallace
force-pushed
the
2025-10-static-inv-server
branch
from
38e3f54 to
cb8228c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This bLIP defines a protocol for always-online nodes acting as "static invoice servers" to assist
often-offline lightning recipients in receiving async payments. This protocol enables mobile wallets
and other frequently-offline nodes to delegate the task of responding to invoice requests from
payers, while maintaining custody of funds. The aforementioned invoice servers will respond to these
invoice requests with a static or payment-hash-less invoice, which can then be paid via the async
payments protocol.