--- Log opened Mon May 02 00:00:11 2022
00:06 -!- elsirion [~quassel@gateway/tor-sasl/elsirion] has quit [Remote host closed the connection]
00:06 -!- elsirion [~quassel@gateway/tor-sasl/elsirion] has joined #secp256k1
01:56 -!- jb55 [~jb55@user/jb55] has quit [Ping timeout: 256 seconds]
01:57 -!- jb55 [~jb55@user/jb55] has joined #secp256k1
05:34 -!- laanwj [~laanwj@user/laanwj] has joined #secp256k1
06:44 -!- halosghost [~halosghos@user/halosghost] has joined #secp256k1
08:37 < jb55> hey guys, question since I'm a crypto noob: in nostr we establish a shared secret via secp_ecdh for sending messages back and forth over public store-and-forward relays, but notes still leak metadata via to/from pubkeys. is there a way to tweak our keypairs with the shared secret so that we can create hidden identities to communicate with?
08:43 < jb55> this is the spec we're currently using and it leaves much to be desired: https://github.com/nostr-protocol/nips/blob/master/04.md
16:09 -!- halosghost [~halosghos@user/halosghost] has quit [Quit: WeeChat 2.5-rc1]
23:55 < nickler> jb55: This is a difficult problem to solve. You may want to look into what Signal does (https://signal.org/blog/sealed-sender/).
--- Log closed Tue May 03 00:00:12 2022