nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-22 16:35:52 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

NIP-47: Clarify relay usage

Browse Source
This commit is contained in:
ok300 2023-06-18 19:56:12 +02:00 committed by GitHub
parent 9ffd3638d7
commit 82989a5c2b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
47.md
View File

@ -82,7 +82,7 @@ If the command was succesful, the `error` field must be null.
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:
- `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. The URL should have no trailing slash. Multiple relays can be specified by repeating the `relay` parameter.
- `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**.
- Authorization does not require passing keys back and forth.
- The user can have different keys for different applications. Keys can be revoked and created at will and have arbitrary constraints (eg. budgets).