Nostr Web Client

Is that so the events on the signer relay doesnt reveal the user pubkey? So is NostrSigner::pubic_key the signer pubkey or the user pubkey? I cache the user pubkey locally so I'd like to optionally supply this (any the signer pubkey if i need to store this too) to prevent blocking if reusing the signer info. If the user info gets changed I'd like it to error when signing.

Yuki Kishimoto 1y ago

In new version (for now in master branch) `NostrSigner::public_key` return the user public key.

In the last release depends by the signer, but during my tests I saw that the same key is used (so the signer key match the user one), at least in amber and nsec.app.

Reply to this note

Please Login to reply.

Discussion

DanConwayDev 1y ago

Ok, ill check it out but it looks like I have some refactoring to do now that NostrSigner is now a dynamic trait.

brugeman 1y ago

Please also check part 2 of the last upgrade, might be easier to read and add some clarifications: https://github.com/nostr-protocol/nips/pull/1553

Yuki Kishimoto 1y ago

Thanks!