--- Log opened Tue May 03 00:00:12 2022 06:42 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #secp256k1 07:49 -!- halosghost [~halosghos@user/halosghost] has joined #secp256k1 09:44 < jb55> nickler: thx will check it out 09:44 < sipa> What do you mean by hidden identities? 09:56 < jb55> sipa: in nostr notes are json blobs with a sha2 id that commits to {pubkey,created_at,kind,tags,content}. this id is bip340 signed with your key. 09:56 < jb55> so whenever you send a message this pubkey metadata is tied to you, and when you create an encrypted note you can see the pubkey who you're sending to. 09:57 < jb55> and encrypted note encrypts a message via a shared secret using ecdh(your sec,their pubkey) 09:58 < jb55> was just wondering if you could somehow create a new keypair for both parties using some shared secret, maybe establishing this via the first encrypted note 09:59 < jb55> so that your client could watch for notes on public relays that come to your original pubkey and some secret pubkey that was established via an initial message that only those two parties know about 09:59 < jb55> not sure if I'm explaining this well... 10:07 < jb55> the idea is that your main identity might have a web of trust associated with it with lots of followers that you use day to day (think something like an open twitter protocol with encryted DMs), and if your gf was monitoring the public relays and saw lots of messages going to and from your ex's pubkey that would be bad. 12:26 < jb55> hmm I guess each participant can do hidden_sec=h(sec + shared secret) and encrypt each other the new pubkeys and then use the ecdh shared secret on those for future encrypted messages? 19:04 -!- halosghost [~halosghos@user/halosghost] has quit [Quit: WeeChat 2.5-rc1] 23:53 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Ping timeout: 240 seconds] 23:54 -!- elsirion [~quassel@gateway/tor-sasl/elsirion] has quit [Ping timeout: 240 seconds] --- Log closed Wed May 04 00:00:13 2022