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

Clarify use of ambiguous terminology in spec of bunker token

Browse Source 
It's very confusing as to whether it refers to remote user pubkey vs remote signer pubkey. This is complicated further by the typo in the explanation of "remote signer pubkey".
This commit is contained in:
kuiperanon 2024-04-09 11:25:05 -05:00 committed by fiatjaf_
parent b224f6d05d
commit b765b3c030
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: 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-user-pubkey>?relay=<wss://relay-to-connect-on>&relay=<wss://another-relay-to-connect-on>&secret=<optional-secret-value>
``` ```
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). 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).