Do you have any documentation as to how your Nostr remote signer works? I would like to know the mechanics of how it works. How/Why should i trust Primal, or others in the growing field of signers, to not know my nsec? How do i NOT paste my nsec around the Nostr clients and other parts of this new, fascinating and hopeful world? This is an honest question and i am greatful that there are other options like your new addition. I recently had challenges accessing internet in my normal route and wondered about the fragility of relying on the Alby extension which is only (mostly) available in certain browsers. Also, a related question is, how can i be sure that my first revelation of my nsec--which happened through Primal--has not compromised the sovereignty of my Nostr life? Many thanks for all that you have done for the Nostr world, which will make this world more solid, and also thank you for having introduced this new and other way of signing Nostr events.

Replies (1)

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.