| 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-03-02 | NIP-20: fix a typo | ennmichael | |
| 2022-12-17 | Minor grammar fixes | sgmoore | |
| Minor grammar fix at lines 22 and 93. | |||
| 2022-11-10 | NIP-20: server errors happen! | William Casarin | |
| 2022-11-10 | NIP-20: More clarity around malformed vs invalid events | William Casarin | |
| 2022-11-10 | NIP-20: add a note about client handling | William Casarin | |
| 2022-11-10 | NIP-20: pow suggestion | William Casarin | |
| 2022-11-10 | NIP-20: add "invalid" message suggestion | William Casarin | |
| 2022-11-10 | NIP-20: Command Results | William Casarin | |
| When submitting events to relays, clients currently have no way to know if an event was successfully committed to the database. This NIP introduces the concept of command results which are like NOTICE's except provide more information about if an event was accepted or rejected. | |||