Private messenger with seed-phrase identity and zero-knowledge authentication
The client got a version 1.0 scope, an architecture and a team plan ready for development.
Stack and topics
| Industry | Secure communications |
|---|---|
| Region | Global |
Context
The client and the problem
A founder team wanted a messenger in which no server, operator or third party can read messages, or even see who talks to whom and when. Most private messengers still tie an account to a phone number or an email, and still leave metadata on the server.
Before spending on development, the team needed a clear version 1.0: what the product does, how the cryptography fits together, and what it takes to build.
What we built
What did we build?
We ran an eight-week discovery with a solution architect, technical and business analysts and a project manager.
- Seed-phrase identity. Accounts created and recovered from a seed phrase on the TON blockchain, with no phone number or email.
- End-to-end encryption. Messages encrypted on the Signal Protocol model.
- Encrypted metadata. Sender, recipient and time are encrypted too, so the server does not learn who talks to whom.
- Zero-knowledge authentication. Zero-knowledge proofs to authenticate users and check data without revealing it.
- Product features. Self-destructing messages, screenshot blocking and wallet payments inside the chat.
How we worked
Team and process
The discovery produced the documents a development team needs on day one: data-flow, user-flow and technical architecture diagrams, functional and non-functional requirements, testing requirements and a backlog of user stories.
Each feature was checked against the privacy goal: if it would leak who talks to whom, it was redesigned or dropped.
Facts
Project facts
| Fact | Detail |
|---|---|
| Client | A founder team in secure communications |
| Our role | Discovery: architecture, requirements, backlog, team plan |
| Team | Solution architect, technical analyst, business analyst, project manager |
| Topics | Signal Protocol model, metadata encryption, zero-knowledge proofs, TON, seed-phrase identity |
Result
Where it stands
The client got a version 1.0 scope, an architecture and a team plan ready for development.
Next step
Building something similar?
A 30 minute call with Oleg. You leave with a clear view of scope, risks and the next step.
Oleg Pun
CEO, Vareger
