diff options
| author | ekzyis <ekzyis@ekzyis.com> | 2024-01-18 23:32:36 +0100 |
|---|---|---|
| committer | fiatjaf_ <fiatjaf@gmail.com> | 2024-01-19 22:34:00 -0300 |
| commit | c766f8892b46b26a91ac1e570cb605a8074b78b2 (patch) | |
| tree | 71575812789fb42f82aa53c89a5414757977948e /47.md | |
| parent | 9b39fd5ef51eefc85af99b5aefac1a109bc17de3 (diff) | |
NIP-47: fix typo
Diffstat (limited to '47.md')
| -rw-r--r-- | 47.md | 2 |
1 files changed, 1 insertions, 1 deletions
| @@ -17,7 +17,7 @@ This NIP describes a way for clients to access a remote Lightning wallet through | |||
| 17 | * **wallet service**: Nostr app that typically runs on an always-on computer (eg. in the cloud or on a Raspberry Pi). This app has access to the APIs of the wallets it serves. | 17 | * **wallet service**: Nostr app that typically runs on an always-on computer (eg. in the cloud or on a Raspberry Pi). This app has access to the APIs of the wallets it serves. |
| 18 | 18 | ||
| 19 | ## Theory of Operation | 19 | ## Theory of Operation |
| 20 | 1. **Users** who which to use this NIP to send lightning payments to other nostr users must first acquire a special "connection" URI from their NIP-47 compliant wallet application. The wallet application may provide this URI using a QR screen, or a pasteable string, or some other means. | 20 | 1. **Users** who wish to use this NIP to send lightning payments to other nostr users must first acquire a special "connection" URI from their NIP-47 compliant wallet application. The wallet application may provide this URI using a QR screen, or a pasteable string, or some other means. |
| 21 | 21 | ||
| 22 | 2. The **user** should then copy this URI into their **client(s)** by pasting, or scanning the QR, etc. The **client(s)** should save this URI and use it later whenever the **user** makes a payment. The **client** should then request an `info` (13194) event from the relay(s) specified in the URI. The **wallet service** will have sent that event to those relays earlier, and the relays will hold it as a replaceable event. | 22 | 2. The **user** should then copy this URI into their **client(s)** by pasting, or scanning the QR, etc. The **client(s)** should save this URI and use it later whenever the **user** makes a payment. The **client** should then request an `info` (13194) event from the relay(s) specified in the URI. The **wallet service** will have sent that event to those relays earlier, and the relays will hold it as a replaceable event. |
| 23 | 23 | ||