diff options
| author | jiftechnify <jiftech.stlfy@gmail.com> | 2023-05-14 13:16:10 +0900 |
|---|---|---|
| committer | jiftechnify <jiftech.stlfy@gmail.com> | 2023-05-14 13:16:10 +0900 |
| commit | 89e3c01b1438cedfb8d1ebbed3e320b8a6f3a582 (patch) | |
| tree | 9b19b2e71002f2f65d1d3e9c8faf50adc3bd773f /57.md | |
| parent | 9076b8486da293f56e725ec593fcfb09a7bc2edf (diff) | |
fix description of nostr query param
Diffstat (limited to '57.md')
| -rw-r--r-- | 57.md | 2 |
1 files changed, 1 insertions, 1 deletions
| @@ -102,7 +102,7 @@ The lnurl server will need some additional pieces of information so that clients | |||
| 102 | 102 | ||
| 103 | ### Appendix D: LNURL Server Zap Request Validation | 103 | ### Appendix D: LNURL Server Zap Request Validation |
| 104 | 104 | ||
| 105 | When a client sends a `zap request` event to a server's lnurl-pay callback URL, there will be a `nostr` query parameter where the contents of the event are URI- and JSON-encoded. If present, the `zap request` event must be validated in the following ways: | 105 | When a client sends a `zap request` event to a server's lnurl-pay callback URL, there will be a `nostr` query parameter whose value is that event which is URI- and JSON-encoded. If present, the `zap request` event must be validated in the following ways: |
| 106 | 106 | ||
| 107 | 1. It MUST have a valid nostr signature | 107 | 1. It MUST have a valid nostr signature |
| 108 | 2. It MUST have tags | 108 | 2. It MUST have tags |