diff options
| author | fiatjaf <fiatjaf@gmail.com> | 2024-09-28 12:26:48 -0300 |
|---|---|---|
| committer | fiatjaf <fiatjaf@gmail.com> | 2024-09-28 12:29:03 -0300 |
| commit | a736e629be5c4c9125d98bdb4965851d8110c483 (patch) | |
| tree | 3674e4f23c873dca200904e2893fc842e74ea342 /75.md | |
| parent | 4438b892d8abd189afc75f9f54532ec95f108d9f (diff) | |
complete renaming to "addressable" events.
as noticed by @bezysoftware at https://github.com/nostr-protocol/nips/pull/1437#issuecomment-2380626514.
I don't know how so many of these instances were left from the original PR at following ca3c52e3e74f0a4679f1c6c0d9ac6461ea748d2d.
Diffstat (limited to '75.md')
| -rw-r--r-- | 75.md | 2 |
1 files changed, 1 insertions, 1 deletions
| @@ -77,7 +77,7 @@ Clients MAY display funding goals on user profiles. | |||
| 77 | 77 | ||
| 78 | When zapping a goal event, clients MUST include the relays in the `relays` tag of the goal event in the zap request `relays` tag. | 78 | When zapping a goal event, clients MUST include the relays in the `relays` tag of the goal event in the zap request `relays` tag. |
| 79 | 79 | ||
| 80 | When zapping a parameterized replaceable event with a `goal` tag, clients SHOULD tag the goal event id in the `e` tag of the zap request. | 80 | When zapping an addressable event with a `goal` tag, clients SHOULD tag the goal event id in the `e` tag of the zap request. |
| 81 | 81 | ||
| 82 | ## Use cases | 82 | ## Use cases |
| 83 | 83 | ||