diff options
| author | Kieran <kieran@harkin.me> | 2024-10-15 11:15:54 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-10-15 11:15:54 +0100 |
| commit | 1e2f19863ca56754daa2466881eb22087a71b17d (patch) | |
| tree | 4f7be759dce290fea1d3ae10c403260b466ee16c /46.md | |
| parent | 53afaaece61f02e92b5ef9c3e9c32945c7ebf522 (diff) | |
| parent | e381b577c997b849fa544eea7dc9f08b360b4a33 (diff) | |
Merge branch 'master' into nip71-imeta
Diffstat (limited to '46.md')
| -rw-r--r-- | 46.md | 16 |
1 files changed, 10 insertions, 6 deletions
| @@ -1,4 +1,8 @@ | |||
| 1 | # NIP-46 - Nostr Remote Signing | 1 | NIP-46 |
| 2 | ====== | ||
| 3 | |||
| 4 | Nostr Remote Signing | ||
| 5 | -------------------- | ||
| 2 | 6 | ||
| 3 | ## Rationale | 7 | ## Rationale |
| 4 | 8 | ||
| @@ -28,7 +32,7 @@ The remote signer would provide a connection token in the form: | |||
| 28 | bunker://<remote-user-pubkey>?relay=<wss://relay-to-connect-on>&relay=<wss://another-relay-to-connect-on>&secret=<optional-secret-value> | 32 | bunker://<remote-user-pubkey>?relay=<wss://relay-to-connect-on>&relay=<wss://another-relay-to-connect-on>&secret=<optional-secret-value> |
| 29 | ``` | 33 | ``` |
| 30 | 34 | ||
| 31 | 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). | 35 | 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). Optional secret can be used for single successfully established connection only, remote signer SHOULD ignore new attempts to establish connection with old optional secret. |
| 32 | 36 | ||
| 33 | ### Direct connection initiated by the client | 37 | ### Direct connection initiated by the client |
| 34 | 38 | ||
| @@ -90,7 +94,7 @@ nostrconnect://<local-keypair-pubkey>?relay=<wss://relay-to-connect-on>&metadata | |||
| 90 | 94 | ||
| 91 | ## Request Events `kind: 24133` | 95 | ## Request Events `kind: 24133` |
| 92 | 96 | ||
| 93 | ```json | 97 | ```jsonc |
| 94 | { | 98 | { |
| 95 | "id": <id>, | 99 | "id": <id>, |
| 96 | "kind": 24133, | 100 | "kind": 24133, |
| @@ -101,7 +105,7 @@ nostrconnect://<local-keypair-pubkey>?relay=<wss://relay-to-connect-on>&metadata | |||
| 101 | } | 105 | } |
| 102 | ``` | 106 | ``` |
| 103 | 107 | ||
| 104 | The `content` field is a JSON-RPC-like message that is [NIP-04](https://github.com/nostr-protocol/nips/blob/master/04.md) encrypted and has the following structure: | 108 | The `content` field is a JSON-RPC-like message that is [NIP-04](04.md) encrypted and has the following structure: |
| 105 | 109 | ||
| 106 | ```json | 110 | ```json |
| 107 | { | 111 | { |
| @@ -148,7 +152,7 @@ The `connect` method may be provided with `optional_requested_permissions` for u | |||
| 148 | } | 152 | } |
| 149 | ``` | 153 | ``` |
| 150 | 154 | ||
| 151 | The `content` field is a JSON-RPC-like message that is [NIP-04](https://github.com/nostr-protocol/nips/blob/master/04.md) encrypted and has the following structure: | 155 | The `content` field is a JSON-RPC-like message that is [NIP-04](04.md) encrypted and has the following structure: |
| 152 | 156 | ||
| 153 | ```json | 157 | ```json |
| 154 | { | 158 | { |
| @@ -224,4 +228,4 @@ Coming soon... | |||
| 224 | 228 | ||
| 225 | ## References | 229 | ## References |
| 226 | 230 | ||
| 227 | - [NIP-04 - Encryption](https://github.com/nostr-protocol/nips/blob/master/04.md) | 231 | - [NIP-04 - Encryption](04.md) |