You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is no need for a user registration screen, nor for the user to be asked if they want to use a previously generated private key, or if they want to keep one as such
For each new order that a user creates or takes, the client must generate a new private key, which will be used to sign the seal of the nip59 messages sent to Mostro for that order.
In others words: Mostro uses nip59 to exchange messages with users, always generating an ephemeral key to sign each message. Additionally, the Mostro client creates a new key for each order, linking it specifically to that order. Once the order is completed, that key is no longer used. Each new order will generate its own ephemeral key.
This way, it will be very difficult for an external agent attempting to analyze Nostr events to track the interactions between Mostro and its users.
No login screen required
The text was updated successfully, but these errors were encountered:
There is no need for a user registration screen, nor for the user to be asked if they want to use a previously generated private key, or if they want to keep one as such
For each new order that a user creates or takes, the client must generate a new private key, which will be used to sign the seal of the nip59 messages sent to Mostro for that order.
In others words: Mostro uses nip59 to exchange messages with users, always generating an ephemeral key to sign each message. Additionally, the Mostro client creates a new key for each order, linking it specifically to that order. Once the order is completed, that key is no longer used. Each new order will generate its own ephemeral key.
This way, it will be very difficult for an external agent attempting to analyze Nostr events to track the interactions between Mostro and its users.
No login screen required
The text was updated successfully, but these errors were encountered: