WraithLink messenger

WraithLink ships with its own messenger, also called WraithLink. It is end-to-end encrypted, peer-to-peer, verified before you can send a word, and it stores nothing anywhere - there is no server to store it on.

No server, no account, no phone number

Every install runs its own Tor v3 onion service to receive messages and dials peers through the local Tor proxy. Your address is an onion address, not a phone number or a username tied to an account. Because traffic rides Tor, neither peer learns the other's IP or location, and there is no central point to subpoena, breach, or shut down.

Mandatory verification (the "OTP")

You cannot message a contact until you have verified them. When you add someone, both phones compute the same short numeric code from your two identity keys (optionally salted with a one-time invite passcode you share out-of-band). You compare the codes - read them aloud, or check them in person - and confirm. If the codes don't match, someone is trying to sit in the middle, and the app refuses to proceed. Nothing about this is stored; it is recomputed each session.

Disappearing by default

Messages live only in the app's memory and disappear on a timer you set per conversation. There is a view-once mode that burns a message the instant it's read, and a background sweeper that purges anything past its lifetime even if you never open the chat. Locking the phone, logging out, or a duress event wipes the whole in-memory store immediately. Screenshots and screen recording are blocked.

Encryption

Your long-term identity key is generated inside the phone's secure element and never leaves hardware. Message encryption uses the audited Double Ratchet (the same construction behind Signal) for forward secrecy and post-compromise security - WraithLink does not invent its own ciphers.

"Blockchain", scoped honestly

You asked for a blockchain messenger. Here's the honest engineering: putting messages on a blockchain would make them permanent and world-readable, which is the exact opposite of "nothing stored anywhere". So messages never touch a ledger. The only place the blockchain idea appears is an optional, tamper-evident anchor that binds a human-readable handle to a public key, purely to stop impersonation. It never carries message content or metadata, and it's off by default - you can operate on onion address plus verified code alone.

Tradeoffs

• No history sync across devices - no logs means nothing to backfill.
• No cloud backup of conversations.
• Lose the device key and past messages are gone, by design.