diff options
| author | Jose Mateo <jmateo6@gmail.com> | 2023-05-28 05:58:48 -0400 |
|---|---|---|
| committer | fiatjaf_ <fiatjaf@gmail.com> | 2023-05-28 10:16:36 -0300 |
| commit | b12c93c452814ffa5f06aef95b60775bc86eaf58 (patch) | |
| tree | 3bc0f0100a5505e53ce06cd03295f51461a1cb24 | |
| parent | 4f04de2afda831ef339ad225e4e08a5b1d075e3c (diff) | |
Fix nip-57 typo
| -rw-r--r-- | 57.md | 2 |
1 files changed, 1 insertions, 1 deletions
| @@ -168,7 +168,7 @@ A client can retrieve `zap receipt`s on events and pubkeys using a NIP-01 filter | |||
| 168 | 168 | ||
| 169 | ### Appendix G: `zap` tag on zapped event | 169 | ### Appendix G: `zap` tag on zapped event |
| 170 | 170 | ||
| 171 | When an event includes a `zap` tag, clients SHOULD calculate the lnurl pay request based on it's value instead of the profile's field. An optional third argument on the tag specifies the type of value, either `lud06` or `lud16`. | 171 | When an event includes a `zap` tag, clients SHOULD calculate the lnurl pay request based on its value instead of the profile's field. An optional third argument on the tag specifies the type of value, either `lud06` or `lud16`. |
| 172 | 172 | ||
| 173 | ```json | 173 | ```json |
| 174 | { | 174 | { |