keychat on Nostr: In the NIP-46 protocol, the signer that stores the nsec does not expose the nsec. It ...
In the NIP-46 protocol, the signer that stores the nsec does not expose the nsec. It only receives signing requests, completes the signing, and then sends the result out.
quoting note1zhv…4mwhI don’t recall if I’ve been asked this question before.
The "Amber" you mentioned is likely referring to NIP-46 Nostr Remote Signing, right? We are very likely to support NIP-46.
NIP-46 requires a relay to facilitate signature requests and signatures between a third-party app and a signer app, even if both apps are on the same phone. Therefore, we feel that NIP-46 is not entirely perfect. Perhaps for this reason, NIP-55 Android Signer Application emerged.
In this approach, signature requests and signatures between a third-party app and a signer app (NIP-55) on the same Android phone are handled through internal system communication, without the need for a relay. This solution is better suited for most scenarios. However, iOS does not support NIP-55.
There’s no perfect solution yet, and we are still contemplating.
https://github.com/nostr-protocol/nips/blob/master/46.md#nostr-remote-signing
https://github.com/nostr-protocol/nips/blob/master/55.md