upleb.uk

Public git repos — served from a NIP-34 GRASP relay at git.upleb.uk

summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorfiatjaf <fiatjaf@gmail.com>2023-11-21 22:31:13 -0300
committerfiatjaf <fiatjaf@gmail.com>2023-11-21 22:31:13 -0300
commit6c35537ca425f154ca1c92897ab0eac599a80c87 (patch)
tree7063bad7e12ec5e1fdb99b3b889ddb9544669509
parente4bddbee7b90b701ea2041532c88935f5176850e (diff)
@v0l improvements.
-rw-r--r--46.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/46.md b/46.md
index 6610e82..1a9be03 100644
--- a/46.md
+++ b/46.md
@@ -10,7 +10,7 @@ This NIP describes a method for 2-way communication between a **remote signer**
10 10
11## Signer Discovery 11## Signer Discovery
12 12
13The client must somehow be able to contact the signer through a common relay. 13The 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.
14 14
15### Started by the signer 15### Started by the signer
16 16
@@ -27,7 +27,7 @@ The user copies that token and pastes it in the client UI somehow. Then the clie
27The client generates a QR code in the following form (URL-encoded): 27The client generates a QR code in the following form (URL-encoded):
28 28
29``` 29```
30nostrconnect://<client-key-hex>?relay=wss://...&metadata={"name":"client-name"} 30nostrconnect://<client-key-hex>?relay=wss://...&metadata={"name":"...", "url": "...", "description": "..."}
31``` 31```
32 32
33The signer scans the QR code and sends a `connect` message to the client in the specified relays. 33The signer scans the QR code and sends a `connect` message to the client in the specified relays.