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

@v0l improvements.

Browse Source
This commit is contained in:
fiatjaf 2023-11-21 22:31:13 -03:00
parent e4bddbee7b
commit 6c35537ca4
No known key found for this signature in database
GPG Key ID: BAD43C4BE5C1A3A1
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
46.md
View File

@ -10,7 +10,7 @@ This NIP describes a method for 2-way communication between a **remote signer**
## Signer Discovery
The client must somehow be able to contact the signer through a common relay.
The client always starts by generating a random key which is used to communicate with the signer, then it one of the methods below is used to allow the client to know what is the signer public key for the session and which relays to use.
### Started by the signer
@ -27,7 +27,7 @@ The user copies that token and pastes it in the client UI somehow. Then the clie
The client generates a QR code in the following form (URL-encoded):
```
nostrconnect://<client-key-hex>?relay=wss://...&metadata={"name":"client-name"}
nostrconnect://<client-key-hex>?relay=wss://...&metadata={"name":"...", "url": "...", "description": "..."}
```
The signer scans the QR code and sends a `connect` message to the client in the specified relays.