Hide who, when, how
The metadata-private messenger
Encryption hides what you say. Metadata - who, when and how often - is what surveillance actually runs on. PrivaMesh hides that too.
Stealth addresses
A fresh one-time address per message hides the social graph.
Cover traffic
Decoy messages hide when you actually send.
Gas wallet
A throwaway fee payer hides who pays for a message.
Two people can exchange perfectly encrypted messages and still be fully exposed. If an observer knows that address A messaged address B at 2:14am, then again after B replied, they’ve learned the relationship, the rhythm, and the timing - without reading a single word. That is metadata, and on a public blockchain it would normally be trivial to collect. PrivaMesh is engineered so it isn’t. This is what makes it a genuine messenger that doesn’t collect metadata: there is no collector, and the on-chain trail is deliberately unlinkable.
Stealth addresses - hide who
Every message is sent to a fresh one-time stealth address derived so that only the intended recipient can recognize and spend it. Two messages to the same person go to two unrelated-looking addresses. Anyone scanning Solana sees a scatter of one-off addresses with no way to cluster them into a conversation or a social graph. The who talks to whom simply isn’t written down anywhere.
Cover traffic - hide when
Timing is its own leak. If your real messages are the only transactions you ever produce, their timing reveals your activity pattern. PrivaMesh mixes in cover traffic - decoy messages indistinguishable from real ones - so that an observer watching the chain cannot tell a genuine send from noise. Frequency analysis and timing correlation lose their signal.
Gas wallet - hide who pays
Solana transactions need a fee payer, and a naive design would let the paying wallet unmask the sender. PrivaMesh uses a throwaway gas wallet as the fee payer, so the wallet funding a transaction is never the wallet sending the message. Combined with unlinkable multi-accounts - you can run several identities that can’t be tied together - the payment trail stops pointing back at you.
Why this needs no server to work
None of this relies on a trusted party promising not to look. It is built into how messages are addressed and paid for on-chain. Because there is no PrivaMesh server, there is also no server-side log of IP addresses, timestamps, or contact lists - the metadata most apps leak first.
The honest trade-off
Metadata protection is strong but not magic. Your anonymity still depends on wallet funding hygiene: if you fund your gas wallet from an exchange account tied to your identity, you create a link the app can’t erase. Good practice matters. We’d rather tell you where the edges are than pretend they don’t exist.
