Cryptix Messenger uses end-to-end encryption at wallet level for message content. Encryption is performed entirely inside the client/web wallet before the message is transmitted to a node. As a result, the blockchain stores not the plaintext, but only the encrypted message content (ciphertext). This architecture provides full end-to-end encryption for message content between sender and recipient.
The messenger uses its own dedicated messenger key. This key is separate from the normal wallet/spend key and is deterministically derived from the wallet mnemonic or seed. This ensures that the messenger key is:
Important: The private key, seed, and spend key are never shared. The protocol only uses the public messenger key.
Messenger keys are deterministically derived from the wallet recovery phrase (mnemonic), but in a separate derivation domain so they remain isolated from normal wallet spending keys.
Because messenger keys and wallet spending keys are derived in separate branches, messenger keys are never reused as spend keys. Messenger public keys therefore cannot be used to derive wallet private keys.
Messenger seed material is only made available to the messenger context during login, wallet creation, or wallet connect. It is cleared again on disconnect or wallet switch.
Cryptix separates on-chain signing and messenger encryption intentionally:
secp256k1 is used for wallet/address/transaction signing on the chain.curve25519 is used for messenger end-to-end encryption in the web wallet.This separation keeps payment signing and messenger encryption as two logically independent security domains.
Because wallet addresses in the Cryptix stack do not directly contain the key required for messenger encryption, the first contact is handled through a handshake.
In this first message, users exchange their public messenger keys. Once that key is known, all following messages can be sent as true end-to-end encrypted messages.
The handshake body also includes an explicit signature verification step to confirm key ownership before encrypted chat continues.
The fields are used as follows:
nonce = nonce used for encryptionbody = encrypted message content (ciphertext)sender_kind=1sender_data = sender's public messenger keyrecipient_tag = derived short identifier of the recipientmsg_type = distinguishes between handshake and encrypted messageThis model ensures that:
The encryption protects the message content, but not automatically all metadata. Depending on the chain context, it may still remain visible:
Cryptix Messenger and its encryption stack are currently in Version 1. Work on Version 2 is already in progress.
Version 2 is planned to include a special variant of the self-developed Frost Hash and an even stronger encryption model for messenger communication.