mirror of
https://github.com/nostr-protocol/nips.git
synced 2025-01-10 00:01:34 +00:00
commit
e42aae6184
6
47.md
6
47.md
@ -107,7 +107,7 @@ The content of notifications is encrypted with [NIP04](https://github.com/nostr-
|
|||||||
## Nostr Wallet Connect URI
|
## Nostr Wallet Connect URI
|
||||||
**client** discovers **wallet service** by scanning a QR code, handling a deeplink or pasting in a URI.
|
**client** discovers **wallet service** by scanning a QR code, handling a deeplink or pasting in a URI.
|
||||||
|
|
||||||
The **wallet service** generates this connection URI with protocol `nostr+walletconnect://` and base path it's hex-encoded `pubkey` with the following query string parameters:
|
The **wallet service** generates this connection URI with protocol `nostr+walletconnect://` and base path its hex-encoded `pubkey` with the following query string parameters:
|
||||||
|
|
||||||
- `relay` Required. URL of the relay where the **wallet service** is connected and will be listening for events. May be more than one.
|
- `relay` Required. URL of the relay where the **wallet service** is connected and will be listening for events. May be more than one.
|
||||||
- `secret` Required. 32-byte randomly generated hex encoded string. The **client** MUST use this to sign events and encrypt payloads when communicating with the **wallet service**.
|
- `secret` Required. 32-byte randomly generated hex encoded string. The **client** MUST use this to sign events and encrypt payloads when communicating with the **wallet service**.
|
||||||
@ -175,7 +175,7 @@ Request:
|
|||||||
Response:
|
Response:
|
||||||
|
|
||||||
For every invoice in the request, a separate response event is sent. To differentiate between the responses, each
|
For every invoice in the request, a separate response event is sent. To differentiate between the responses, each
|
||||||
response event contains a `d` tag with the id of the invoice it is responding to, if no id was given, then the
|
response event contains a `d` tag with the id of the invoice it is responding to; if no id was given, then the
|
||||||
payment hash of the invoice should be used.
|
payment hash of the invoice should be used.
|
||||||
|
|
||||||
```jsonc
|
```jsonc
|
||||||
@ -247,7 +247,7 @@ Request:
|
|||||||
Response:
|
Response:
|
||||||
|
|
||||||
For every keysend in the request, a separate response event is sent. To differentiate between the responses, each
|
For every keysend in the request, a separate response event is sent. To differentiate between the responses, each
|
||||||
response event contains an `d` tag with the id of the keysend it is responding to, if no id was given, then the
|
response event contains a `d` tag with the id of the keysend it is responding to; if no id was given, then the
|
||||||
pubkey should be used.
|
pubkey should be used.
|
||||||
|
|
||||||
```jsonc
|
```jsonc
|
||||||
|
Loading…
Reference in New Issue
Block a user