| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2023-08-13 | merge nips 12, 16, 20 and 33 into nip 01 (#703) | fiatjaf_ | |
| Co-authored-by: Viktor Vsk <me@viktorvsk.com> | |||
| 2023-06-04 | Specify replacement behaviour when replaceable events have the same timestamp | Doug Hoyte | |
| - This is so that relays can converge on a deterministic sets of events, no matter the order they were received - Otherwise, clients or relays that sync their sets of events could continually retransmit events they think are missing on the other side, wasting bandwidth | |||
| 2023-03-26 | events cannot really be replaced | Leo Wandersleb | |
| clarifying what it means to "replace an event" | |||
| 2022-12-08 | Clarify use of kind 1 and kind 1000-10000 | Jonathan Staab | |
| 2022-11-11 | nip16: clarify about the signers of replaceable events | alex | |
| A newer replaceable event must be signed by the same key. | |||
| 2022-10-16 | nip16: small fix | Semisol | |
| 2022-07-26 | nip16: small fix | Semisol | |
| 2022-05-27 | nip16: kind ranges instead of tags | Semisol | |
| 2022-05-26 | nip16: add newlines | Semisol | |
| 2022-05-26 | nip16: create draft | Semisol | |