Avatar
Waklaf ∞/21M
c81870b2fb8b36376bf58d0acf02c775c7527f21edb8f6e51415c564b2fb9fcb
Fulltime rabbit hole explorer

That would be great. I am proud I live in the state where so many innovations happen first time in the world.

Replying to Avatar Waklaf ∞/21M

I know there is a problem with metadata leaking who chats with who in nostr protocol when sending messages (both individual or group messages).

So I was thinking about it fow a while and I came up with an idea that could maybe at least partially help to solve or minimize this problem.

What if we implemented hierachic deterministic accounts and their derivation from one master key (seed, nsec...) and it would then allow you to generate new pair of keys for each conversation. Then you wouldn't have any connection between the people in conversation and their "real" (publicly known) pseudonyms they use for other nostr things.

I would like to explain whole process in detail:

First, the sender of the first message (or message request) sends message from his newly generated account to recipient's publicly-known npub (sender encrypts the message with recipient's npub). The message contains his publicly-known npub signed by his corresponding nsec, so the recipient can verify who send message request and it also contains another new npub to break the link between original contacting message and upcoming conversation. Then as a reply original recipient sends message from his newly generated account also containing publicly-known npub signed by corresponding nsec. This way they both know they are talking with the person who they wanted to talk with. They can know freely send each other message from new accounts and there is a very little link to original identity.

Only thing publicly visible to others on relays, is the fact somebody contacted this exact person and after a while "somebody else" contacted somebody who is completely unknown to other members of network. There is no way of connecting these two events if many people would chat at the same time and there could also occur slight delay (maybe even hours, days) between first contact (message request) and reply (accepting message request.

Only one entity that can now connect two events (or two accounts) is, I think, sender's and recipient's client.

Let me know, if this idea already exists or anything in it doesn't make sense to you. If it is useful maybe we could add another NIP...

#nostr #nip #message #messages #chat #chats #relays #nometadata #plebchain #grownostr

I've been thinking about leaking no metadata in chats. Can you check it out please?

nostr:note1g9qwtw9keqxu02wmzaj3szhktm3c6d6rucwvcx7zndxw4nv47vnqwdw2g0

#asknostr #plebchain #grownostr #suggestion

Replying to Avatar Waklaf ∞/21M

I know there is a problem with metadata leaking who chats with who in nostr protocol when sending messages (both individual or group messages).

So I was thinking about it fow a while and I came up with an idea that could maybe at least partially help to solve or minimize this problem.

What if we implemented hierachic deterministic accounts and their derivation from one master key (seed, nsec...) and it would then allow you to generate new pair of keys for each conversation. Then you wouldn't have any connection between the people in conversation and their "real" (publicly known) pseudonyms they use for other nostr things.

I would like to explain whole process in detail:

First, the sender of the first message (or message request) sends message from his newly generated account to recipient's publicly-known npub (sender encrypts the message with recipient's npub). The message contains his publicly-known npub signed by his corresponding nsec, so the recipient can verify who send message request and it also contains another new npub to break the link between original contacting message and upcoming conversation. Then as a reply original recipient sends message from his newly generated account also containing publicly-known npub signed by corresponding nsec. This way they both know they are talking with the person who they wanted to talk with. They can know freely send each other message from new accounts and there is a very little link to original identity.

Only thing publicly visible to others on relays, is the fact somebody contacted this exact person and after a while "somebody else" contacted somebody who is completely unknown to other members of network. There is no way of connecting these two events if many people would chat at the same time and there could also occur slight delay (maybe even hours, days) between first contact (message request) and reply (accepting message request.

Only one entity that can now connect two events (or two accounts) is, I think, sender's and recipient's client.

Let me know, if this idea already exists or anything in it doesn't make sense to you. If it is useful maybe we could add another NIP...

#nostr #nip #message #messages #chat #chats #relays #nometadata #plebchain #grownostr

I also think our discussion requires a lot thinking behind it because we are trying to solve many problems and inconviences in our protocol by thinking outside the box and coming up with innovative solutions.

Can you please check out my NIP suggestion nostr:note1g9qwtw9keqxu02wmzaj3szhktm3c6d6rucwvcx7zndxw4nv47vnqwdw2g0

I would say their discussion is shallow... Why? Because they are talking about crypto and that's not what the signal is.

Replying to Avatar ChainCampCZ

Přátelé, kamarádi, mám na vás prosbu. Neříká se mi to snadno, ale do začátku 4. ročníku bitcoinové akce Chaincamp zbývá už jen týden a ještě stále máme spousty vstupenek k mání.

Bitcoinové konference už pořádáme pár let, takže dobře víme, že je to vždycky sázka na nejistotu. Pokaždé do toho ale jdeme naplno a ani letos tomu není jinak.

Máme opět pronajaté krásné prostory v ostravském Gongu. Na akci zavítají špičky v oboru jako jsou třeba zakladatelé Trezoru. K tomu potkáte Braiins, Anycoin, GeneralBytes... Chybět samozřejmě nebude ani Kicom, Daniel Steigerwald, Lukáš Kovanda, Juraj Bednár a mnoho dalších. Opět pořádáme prvotřídní akci. Dáváme do toho všechno. To jediné, co moc neovlivníme, je to, jestli přijdou lidi. Zvláště teď před koncem bear marketu.

Chaincamp jsem základal s myšlenkou, aby se bitcoinová komunita mohla setkávat. Abychom se zvedli od počítačů a mluvili spolu. Aby se nováčci potkali se zkušenějšími a nenaletěli tak hned na první scam, který uvidí.

Proto vás chci poprosit o sdílení mezi své přátelé. Pokud víte o někom, kdo má 9. září čas a zajímá se o bitcoin, budeme moc rádi, když jim o Chaincampu řeknete. Už máme pár akcí za sebou a víme, že letošní Chaincamp bude opět nezapomenutelný. Záleží jen pro kolik z nás. Pro všechny vaše známé a kamarády nabízíme slevu ve výši 21 %. Stačí se na web prokliknout tímto odkazem: https://www.chaincamp.cz/?promo=NEJDUSAM

Mnohokrát děkuji za podporu.

Vážím si toho a těším se na vás!

Martin

Doražte na letošní ročník nostr:npub1fc6nyvwm8y3enmy26rekaer8p5q8xhy9ujx06sdngk7d7k2258qs52zyq0 a odnesete si mnoho nových zážitků i znalostí. Pomozte podpořit českou #bitcoin komunitu, která je nejlepší na světě💪

nostr:note1ufj659mu0k90uds4cx85sdtm2l5e26hqdps404ql0hncrydg2u4smxtcju

I know there is a problem with metadata leaking who chats with who in nostr protocol when sending messages (both individual or group messages).

So I was thinking about it fow a while and I came up with an idea that could maybe at least partially help to solve or minimize this problem.

What if we implemented hierachic deterministic accounts and their derivation from one master key (seed, nsec...) and it would then allow you to generate new pair of keys for each conversation. Then you wouldn't have any connection between the people in conversation and their "real" (publicly known) pseudonyms they use for other nostr things.

I would like to explain whole process in detail:

First, the sender of the first message (or message request) sends message from his newly generated account to recipient's publicly-known npub (sender encrypts the message with recipient's npub). The message contains his publicly-known npub signed by his corresponding nsec, so the recipient can verify who send message request and it also contains another new npub to break the link between original contacting message and upcoming conversation. Then as a reply original recipient sends message from his newly generated account also containing publicly-known npub signed by corresponding nsec. This way they both know they are talking with the person who they wanted to talk with. They can know freely send each other message from new accounts and there is a very little link to original identity.

Only thing publicly visible to others on relays, is the fact somebody contacted this exact person and after a while "somebody else" contacted somebody who is completely unknown to other members of network. There is no way of connecting these two events if many people would chat at the same time and there could also occur slight delay (maybe even hours, days) between first contact (message request) and reply (accepting message request.

Only one entity that can now connect two events (or two accounts) is, I think, sender's and recipient's client.

Let me know, if this idea already exists or anything in it doesn't make sense to you. If it is useful maybe we could add another NIP...

#nostr #nip #message #messages #chat #chats #relays #nometadata #plebchain #grownostr

I have only a few of them by Braiins Publishing but plan to do something with it at this year's nostr:npub1fc6nyvwm8y3enmy26rekaer8p5q8xhy9ujx06sdngk7d7k2258qs52zyq0 . And also Velká Kniha O Bitcoinu by Kamil Bouška is missing because I lend it to friends.

https://nostrcheck.me/media/public/nostrcheck.me_6982153516976219241693426609.webp

nostr:npub1llkvd2zh596r437k5guqqpvktn0jtz4tasn3zfqnjuktue33wagqm2ftee nostr:npub120ze59w0y479ak07xnfz7nw00dzmg80remyk3gns4dkd8sujwcrscvjqsm #bitcoin #bookstr

Ahoj Jednadvacítko!

Váháte někdo, jestli jet na Chaincamp? Už příští týden 9.9. Je to skvělá příležitost, abychom se tam potkali a zároveň ukázali bitcoin dalším lidem. Co nejvíc to otevřít. Momentálně je přihlášených méně lidí než vloni a to mi připadá jako veliká škoda.

Máte někoho blízkého, koho byste chtěli vzít s sebou? Můžu Vám nějak pomoc?

nostr:npub1fc6nyvwm8y3enmy26rekaer8p5q8xhy9ujx06sdngk7d7k2258qs52zyq0 podporuje lokální komunity, a proto se rozhodli, že z každého lístku zakoupeného přes link nostr:npub18csp5akqc4dfz9acspxqpg6ptx23gcjaapds0th7a7n6muux3fdqfjy4jv nebo s kódem "JEDNADVACET", dají donate 21% zpět komunitě, aby měla prostředky na zaplacení výdajů na šíření osvěty o bitcoinu.

Pokud tedy chcete pomoci bitcoinu, kupte lístek přes tento link pro své známé, rodinu, kamarády, a vemte je na výlet do Ostravy.

Kdy jindy než teď?! Halving se blíží. Připravme se na budoucnost :)

👇👇👇

https://www.chaincamp.cz/?promo=JEDNADVACET

There is a new #bitcoin nostr:npub18csp5akqc4dfz9acspxqpg6ptx23gcjaapds0th7a7n6muux3fdqfjy4jv community on nostr:npub1864jglrrhv6alguwql9pqtmd5296nww5dpcewapmmcazk8vq4mks0tt2tq . Go check it out and also build your own communities💊

https://btcmap.org/community/jednadvacet-liberec

There is a new #bitcoin Jednadvacet community on nostr:npub1864jglrrhv6alguwql9pqtmd5296nww5dpcewapmmcazk8vq4mks0tt2tq . Go check it out and also build your own communities💊

https://btcmap.org/community/jednadvacet-liberec

I just created second account to regulate amount of content I see on the follow page because I don't wanna miss anything from my favourite 🇨🇿 bitcoiners.I will do that with Amethyst but hope nostr:npub1plstrz6dhu8q4fq0e4rjpxe2fxe5x87y2w6xpm70gh9qh5tt66kqkgkx8j soon integrates multiple account feature. Do you know any client that can create lists (like on twitter)?