12 Commits

Author	SHA1	Message	Date
Vitor Pamplona	36cbdead62	adds line breaks	2024-08-19 15:07:52 -04:00
Vitor Pamplona	e0d16a0a99	Adds a LIMITS payload with strict definitions on how clients should work.	2024-08-19 14:53:42 -04:00
fiatjaf	37f6cbb775	remove all NIP authors.	2023-11-16 10:24:53 -03:00
fiatjaf_	72bb8a128b	merge nips 12, 16, 20 and 33 into nip 01 (#703) ... Co-authored-by: Viktor Vsk <me@viktorvsk.com>	2023-08-13 13:47:45 -03:00
ennmichael	ab6308c29a	NIP-20: fix a typo	2023-03-02 21:36:15 -03:00
sgmoore	da6a7d0ee3	Minor grammar fixes ... Minor grammar fix at lines 22 and 93.	2022-12-17 22:34:29 -03:00
William Casarin	c510e646d0	NIP-20: server errors happen!	2022-11-10 13:14:23 -08:00
William Casarin	ff26b959f8	NIP-20: More clarity around malformed vs invalid events	2022-11-10 12:55:44 -08:00
William Casarin	7569773ad6	NIP-20: add a note about client handling	2022-11-10 12:20:32 -08:00
William Casarin	e7f74d21c4	NIP-20: pow suggestion	2022-11-10 12:02:14 -08:00
William Casarin	a0b0a021a8	NIP-20: add "invalid" message suggestion	2022-11-10 11:57:52 -08:00
William Casarin	15514283f3	NIP-20: Command Results ... 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.	2022-11-10 10:29:11 -08:00