From 6c35537ca425f154ca1c92897ab0eac599a80c87 Mon Sep 17 00:00:00 2001 From: fiatjaf Date: Tue, 21 Nov 2023 22:31:13 -0300 Subject: [PATCH] @v0l improvements. --- 46.md | 4 ++-- 1 file 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** ## 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://?relay=wss://...&metadata={"name":"client-name"} +nostrconnect://?relay=wss://...&metadata={"name":"...", "url": "...", "description": "..."} ``` The signer scans the QR code and sends a `connect` message to the client in the specified relays.