Sidzedze ƒe gɔmeɖoanyi / Adzame

Nusuɖeɖe

Wò ƒe kpɔkpɔkpɔwo kple wo ƒe ɖeesiwo nye end-to-end encrypted, eye wònye post-quantum layer si le classical layer la dzi. Esia ƒe ƒe nye nu si wòɖogbe ɖe nya sia me.

Woɖe axa sia gɔme to mɔ̃ dzi be wòanɔ bɔbɔe. Eŋlisigbe me gbãtɔae nye gɔmeɖeɖe si sɔ.

Gbãtɔ tso ɖeka me ɖeka me ɖeɖe gbã

Dzesi aɖe si wòɖea ɖe ɖeɖe o. Ŋɔŋlɔ siameame ɖeka le dɔwɔwɔ siameame me la, wɔa ɖe e ƒe kɔnu le wòƒe dzigbe si me la ɖe eƒe mɔ ɖe ɖaɖe la, eye wòanya ɖe e ƒe kɔnu le eƒe nuɖuɖu bubu la me. Kplɔla siwo ɖo e ɖe la meɖe e ɖe, eye nu siameame ɖe e la me o ɖe e ƒe nya la.

"Nɔɖeke bubu" le fia la me la nye Nymbot ƒe xɔlɔ̃la, si ƒe nye eye wòava ɖe ŋu be wòɖe eŋu nya si wòɖo la be wòaɖe eŋu. End-to-end ƒe nya la nye be amesi ɖeɖe menye ɖekaɖe eɖe — eɖe o eye eɖeɖe mɔ o be dɔwɔla la ɖo nu si eɖeɖe ɖo o. Anonymity mode nye ɖe nya bubui si nye nyea be eƒe nɔa xɔ xɔ̃a nya la gbɔa ɖe nye ɖeka? ɖe ɖe kpɔ.

Xɔɣu ɖe nuɖatɔƒe ƒe xɔɣuwo me

Mesafewo ƒe ɖekaɖeka ƒe ɖokuiwo ɖi ƒo ɖi Nostr gift wraps. Eve ɖeka ɖeka ƒe ɖokuiwo wònye etɔ̃:

• a nyaʋiʋli — xɔmesẽ la ɖeɖe la, si ɖe ɖe si me anyigbeɖeɖe le eme la, be emaɖe nanyaɖe nɛ na gbɔgbɔɖeaɖe bubu aɖe gbɔ o;
• a nutrenu, si wò ɖe dzigbe eye wò ɖe eƒe dzigbe ɖe ame si nye nuɖuɖuwo ƒe nuɖuɖu ɖe, si nye nene ame si nye nuɖuɖuwo ƒe nuɖuɖu la nyui be ame si ɖe e la ɖe;
• a ɖu, eyeɖeɖe eye wòɖe dzesi ɖe aksɔm si si ƒe wòɖeɖe ɖe ɖeka ko eye wòtsɔ ɖe eɖokui me, si nye nu gbɔɖe si relay la ɖo agbe.

So a relay holding your traffic sees an event from a key that exists only for that message, with a random timestamp — it can tell a message is for Nymbot, not who sent it. Metadata analysis over the wraps gets very little.

A copy of each message is also wrapped to your own key, which is how your history restores on a new device from the relays rather than from any server-side transcript.

Post-quantum hybrid

ɖokununɔtɔ ƒe ƒeɖeɖe la ɖe nuŋɔŋlɔ ƒe xɔnu (elliptic-curve) si nye. Ŋutsuɖasiɖeɖe ƒe komputa si ƒe ŋusẽ le ɖe nuɖeɖe lɔ̃ɖeɖe la natsɔ ɖe nuŋɔŋlɔ la ɖe ɣeɖe — nuɖuɖu siwowo ɖe ɖe ɖe ɣeɖe egbe la, naxɔɖeɖe nya la ɖe ɣeɖe ƒe ƒeɖeɖe gbɔ. Eyã aleɖe ɖe nuŋɔŋlɔ siwowo ƒe dzesi la gbɔ nɔnɔme ƒe ɖeɖe: an ML-KEM key encapsulation is combined with the classical exchange, and an attacker has to break both to read anything.

ML-KEM nye NIST-ɖokui la ɖo nu si nye lattice KEM. Nu ɖe ɖe ɖeka me rather than nu ɖe nu ɖeka me nye nu si me wogblɔ na: ɖe wòɖɔ ɖeka me be ɣeɖeɖe (lattice) ɖokui la ƒe nuɖonyenye la gblẽ la, nɔa xɔxɔ ƒe ɖokui la me gɔme, eye ɖe nu ɖeka me be ɣeɖeɖe la le gbɔ la, nɔa xɔxɔ ƒe ɖokui la me gɔme.

Nymbot publishes a signed capability announcement carrying its KEM key, so your app can seal to it without a lookup race that would quietly leave a message classical-only. Your app publishes one too, which is how replies come back hybrid.

Zɔli si dɔmeaɖuɖu (server) ɖoe ɖo

Kpɔkpɔ kpɔkpɔ kaba de dze ɖe sia dzi la, ɖe dzesi ɖe sia dzi la gbɔ wu.

Conversation titles are generated on your device, never by the model, and only cross the wire encrypted to your own key, so your other devices can show them.