nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-11-09 22:09:06 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

nip46: &clientkey=...

Browse Source
This commit is contained in:
fiatjaf 2024-03-07 18:11:20 -03:00
parent 6871b3b334
commit 07c12528bb
No known key found for this signature in database
GPG Key ID: BAD43C4BE5C1A3A1
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
46.md
View File

@ -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).