Doug Hoyte
fe9ed69dc3
Specify replacement behaviour when replaceable events have the same timestamp
...
- 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-06-04 18:34:17 -03:00
Asai Toshiya
a56d1c2877
Add description for d tag value
2023-05-26 08:15:08 -03:00
Leo Wandersleb
dced433f9c
events cannot really be replaced
...
clarifying what it means to "replace an event"
2023-03-26 13:52:08 -03:00
lapulpeta
f938923258
Fixed example with multiple values
2023-03-09 12:51:41 -03:00
fiatjaf
b4493aa56a
rename coordinates: nitem->naddr, "i"->"a"
2023-02-13 08:47:23 -03:00
fiatjaf
16b50a481f
rename nref to nitem and use the i tag.
2023-02-05 20:23:59 -03:00
fiatjaf
0acfd0e84b
declare nref on NIP-33. remove need for NIP-01 bridge event.
2023-02-04 07:16:16 -03:00
Semisol
d179cd9758
NIP-33: d tag requirements
2023-01-24 15:54:57 -03:00
Semisol
54b6c0090d
NIP-33: Add example for more than one value
2023-01-24 15:54:57 -03:00
fiatjaf
4472f9bbd9
add NIP-33 to README.
2023-01-04 10:26:08 -03:00
Semisol
018c45966e
Add NIP-33 Parameterized replaceable events ( #54 )
...
Co-authored-by: Semisol <45574030+Semisol@users.noreply.github.com>
Co-authored-by: Ricardo Arturo Cabral Mejía <me@ricardocabral.io>
2023-01-04 10:20:27 -03:00
