From 07c12528bb2095d36e2fd0690c078c4eef5c0385 Mon Sep 17 00:00:00 2001
From: fiatjaf <fiatjaf@gmail.com>
Date: Thu, 7 Mar 2024 18:11:20 -0300
Subject: [PATCH] nip46: &clientkey=...

---
 46.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/46.md b/46.md
index eb964942..bf3dbe5d 100644
--- a/46.md
+++ b/46.md
@@ -25,7 +25,7 @@ This is most common in a situation where you have your own nsecbunker or other t
 The remote signer would provide a connection token in the form:
 
 ```
-bunker://<remote-pubkey>?relay=<wss://relay-to-connect-on>&relay=<wss://another-relay-to-connect-on>&secret=<optional-secret-value>
+bunker://<remote-pubkey>?relay=<wss://relay-to-connect-on>&relay=<wss://another-relay-to-connect-on>&secret=<optional-secret-value>&clientkey=<optional-hex-key-to-use-as-the-clients-key>
 ```
 
 This token is pasted into the client by the user and the client then uses the details to connect to the remote signer via the specified relay(s).