Skip to content

LSPS5: clarify per-method cooldown to minutes #64

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Aug 12, 2025
Merged

LSPS5: clarify per-method cooldown to minutes #64

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
41feecd
LSPS5: clarify per-method cooldown to minutes.
martinsaposnic Aug 11, 2025
670ce70
Fix tiny typos on LSPS5 spec
martinsaposnic Aug 11, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 11 additions & 5 deletions blip-0055.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -73,7 +73,7 @@ push notifications to be sent to actual mobile devices.
Depending on architecture, the 'notification delivery service'
and the 'mobile OS server' may not exist.
For instance, a client running on a desktop environment might
be able to periodically wake up and pool a 'notification
be able to periodically wake up and poll a 'notification
delivery service' without help from any kind of 'mobile OS
server'.
A client running on an environment where some DNS-resolvable
Expand Down Expand Up @@ -274,12 +274,12 @@ via the `lsps5.remove_webhook` call, which takes the parameters:

```JSON
{
"app_name": "Another Wallet With The Same Signig Device"
"app_name": "Another Wallet With The Same Signing Device"
}
```

The following error is defined for `remove_webhook` (error
`code` in parantheses):
`code` in parentheses):

* `app_name_not_found` (1010) - The specified `app_name` was
not found.
Expand Down Expand Up @@ -626,16 +626,22 @@ For example, if a payment arrives and the LSP thus
wants to send `lsps5.payment_incoming` notification to a
registered webhook, and another payment arrives before the
client comes online, the LSP must not send another
`lsps5.payment_incoming` notification.
`lsps5.payment_incoming` notification within its cooldown window.

If the client does not come online after some time that a
particular `method` was sent via a webhook, then the LSP
may raise it again.
This timeout must be measurable in hours or days.
This timeout should be on the order of minutes.

The timeout should be reset once the client comes online
and then goes offline.

> **Rationale** Mobile devices and networks are transient.
> A device might ignore a wakeup due to battery or connectivity,
> then accept one a short time later.
> A cooldown on the order of minutes protects
> against floods while improving delivery in practice.

[LSPS0.ln_signature]: ./blip-0050.md#link-lsps0ln_signature
[LSPS0.datetime]: ./blip-0050.md#link-lsps0datetime
[RFC 1738]: https://datatracker.ietf.org/doc/html/rfc1738
Expand Down