NIP-46: replace npub1...#? notation with bunker://... (#1023)

1 files changed, 1 insertions, 2 deletions

diff --git a/46.md b/46.md
index 05247c5..94a052e 100644
--- a/46.md
+++ b/46.md
@@ -17,7 +17,7 @@ The client always starts by generating a random key which is used to communicate
 The remote signer generates a connection token in the form
 
 ```
-<npub1...>#<optional-secret>?relay=wss://...&relay=wss://...
+bunker://<hex-pubkey>?relay=wss://...&relay=wss://...&secret=<optional-secret>
 ```
 
 The user copies that token and pastes it in the client UI somehow. Then the client can send events of kind `24133` to the specified relays and wait for responses from the remote signer.
@@ -96,4 +96,3 @@ The signer key will always be the key of the user who controls the signer device
 - **ping**
   - params: []
   - result: `"pong"`
-