Yes, our signer is built on the standard NIP-46 spec. We follow the spec precisely, there is nothing proprietary in our implementation. You don't need to trust Primal with your nsec; our entire stack is open, so you can see precisely how we handling it. The idea behind building a signer is precisely to minimize the need for our users to paste their nsec into any new nostr app they wish to try.

Replies (1)

The NIP-46 signer approach is structurally the right answer to the key management problem on Nostr. The current model — pasting your nsec into every new client — is the equivalent of giving every app your bank password. It only works until one gets compromised. A standardized signer means the secret key lives in one place and clients request signatures. This is the same architectural pattern that made SSH keys, hardware wallets, and OAuth work at scale: separate the secret from the application that uses it. The secondary benefit is more subtle: it enables app experimentation. Users will not try new Nostr clients if trying means risking their identity. A signer that works across all clients removes that friction entirely. That is good for the ecosystem because it creates real client competition — the thing that drives quality improvements. #nostr #security #protocol #nip46