diff options
| author | fiatjaf <fiatjaf@gmail.com> | 2022-05-27 13:50:33 -0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-05-27 13:50:33 -0300 |
| commit | c120b1746f63d2b70a0ce59873a460d77cada909 (patch) | |
| tree | 6b0528f22ceaff5277fb88e20e6c3765a5624231 | |
| parent | c3d3a706881e7a733cc8373737b02aafa38a5024 (diff) | |
| parent | 12f6e9ee625ae2743e10dec16c7eec85e5a8f150 (diff) | |
Merge pull request #10 from Semisol/master
NIP15: End of Stored Events Notice
| -rw-r--r-- | 15.md | 21 |
1 files changed, 21 insertions, 0 deletions
| @@ -0,0 +1,21 @@ | |||
| 1 | NIP-15 | ||
| 2 | ====== | ||
| 3 | |||
| 4 | End of Stored Events Notice | ||
| 5 | --------------------------- | ||
| 6 | |||
| 7 | `draft` `optional` `author:Semisol` | ||
| 8 | |||
| 9 | Relays may support notifying clients when all stored events have been sent. | ||
| 10 | |||
| 11 | If a relay supports this NIP, the relay SHOULD send the client a `EOSE` message in the format `["EOSE", <subscription_id>]` after it has sent all the events it has persisted and it indicates all the events that come after this message are newly published. | ||
| 12 | |||
| 13 | Client Behavior | ||
| 14 | --------------- | ||
| 15 | |||
| 16 | Clients SHOULD use the `supported_nips` field to learn if a relay supports end of stored events notices. | ||
| 17 | |||
| 18 | Motivation | ||
| 19 | ---------- | ||
| 20 | |||
| 21 | The motivation for this proposal is to reduce uncertainty when all events have been sent by a relay to make client code possibly less complex. | ||