https://github.com/nostr-protocol/nips/pull/831#issuecomment-1821474706

> but it may be better to use a random key for the session or a persistent signer-key.

永続的な pubkey でも良さげ。まあ、そうですよね

> ```

> #?relay=wss://...&relay=wss://...

> ```

`optional-secret` は OTP (ワンタイム パスワード)

参考: https://ndk.fyi/docs/classes/NDKNip46Signer.html#constructor

> The signer scans the QR code and sends a connect message to the client in the specified relays.

NIP を素直に解釈すると、`"ack"` を送信すれば良さそう

> And the events the remote signer sends to the client have the following format:

>

> ```js

> "pubkey": ""

> "kind": 24133,

> "tags": [

> ["p", ""]

> ],

> "content": "nip04_encrypted_json({id: , result: , error: })",

> ...

> ```

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

https://github.com/nostr-protocol/nips/pull/831#discussion_r1372968659

会話の流れから察すると、`connect` を送信する必要はなさそう

> The signer key will always be the key of the user who controls the signer device.

これは何でも良さそう

> - **connect**

> - params: [`pubkey`, `secret`]

なるほど、わからん

https://github.com/nostr-protocol/nips/pull/831#discussion_r1401571254

なんとなく理解できた気がする

https://github.com/nostr-protocol/nips/blob/1fd14b7cc9c4df1c18bda7050644449618727f6e/46.md?plain=1#L20

> bunker://?relay=wss://...&relay=wss://...&secret=

`hex-pubkey` は `signer-key-hex`？

https://github.com/nostr-protocol/nips/blob/1fd14b7cc9c4df1c18bda7050644449618727f6e/46.md?plain=1#L70

> - params: [`pubkey`, `secret`]

`client-key-hex`？