A P2P messenger with dual network modes (Fast and Tor)

Hello HN,I have been working on a desktop P2P messenger called Kiyeovo for the last ~8 months, and I just published its beta version.Quick backstory: It started out as a CLI application for my Graduate Thesis, where I tried to make the most secure and private messenger application possible. Then, I transformed it into a desktop application, gave it "clearnet" support and added a bunch of features.Short summary:The app runs in 2 completely isolated modes:- fast mode: relay/DCUtR -> lower latency, calls support- anonymous mode: Tor message routing -> slower, anonymousThese modes use different protocol IDs, DHT namespaces, pubsub topics and storage scopes so there’s no data crossover between them.Messaging works peer-to-peer when both parties are online, but falls back to DHT "offline buckets" when one of them is not. To ensure robustness, messages are ACK-ed and deleted after being read.Group chats use GossipSub for realtime messaging. Group messages are also saved to offline buckets in order for offline users to be able to read them upon logging in. Kick/Join/Leave events are also propagated using the DHT. Group metadata and all offline data is of course encrypted.Other features: Chats are E2E, file sharing is supported, 1:1 audio/video calls are supported (only in fast mode though, using WebRTC)Tradeoffs: Tor has noticeable latency, offline delivery is not immediately guaranteed, but rather "eventually consistent"; beta version does not have group calls yet.I’d appreciate feedback, that's why I posted this as a beta versionRepo: https://github.com/Realman78/Kiyeovo

Hacker NewsToolEducationSource
0Sign in to voteCopy link

FL score

52

out of 100

Verdict

VALIDATE

high confidence

Competition

5

competitors found, emerging market

Trend

No signal yet

A technically impressive P2P messenger with dual fast/Tor modes for privacy, but faces immense challenges in user adoption and monetization against entrenched, free competitors.

The pain

Users suffer from a lack of digital privacy, data collection by mainstream messengers, spam, scams, and limited end-to-end encryption. There's a strong desire for more secure and anonymous communication.

The gap

The gap is for a messenger offering both high-speed, feature-rich communication (like calls) and high-anonymity (Tor) within a single, secure application, without data crossover. Existing secure messengers often optimize for one or the other, or lack the dual-mode flexibility. However, it's not clear there's a strong *demand* for this specific dual-mode gap, rather than just 'better privacy'.

Build angle

Build a P2P messenger with distinct 'Fast' (relay/DCUtR, WebRTC calls) and 'Anonymous' (Tor routing, no calls) modes, ensuring strict isolation between them. Focus on robust E2E encryption, file sharing, and eventually consistent offline delivery with offline buckets.

Strengths

  • Addresses a real and growing pain point: digital privacy and security.
  • Unique technical differentiator with dual network modes (Fast and Tor).
  • Strong technical execution demonstrated by the beta and thesis background.
  • Market for decentralized/Web3 messaging is projected to grow significantly.
  • No funded competitors directly for 'dual-mode P2P messenger' specifically, though many free privacy apps exist.

Risks

  • Massive network effect in messaging makes user acquisition extremely difficult.
  • Expectation of free secure messengers (Signal, Tox, Session) severely limits monetization potential.
  • Lack of clear, specific market demand for the 'dual-mode' feature beyond general privacy concerns.
  • High build complexity and ongoing maintenance for a solo builder.
  • Difficulty in achieving feature parity and user experience of well-resourced incumbents.
  • 'Eventually consistent' offline delivery and Tor latency are trade-offs users might not accept.

Next steps

  1. Conduct in-depth user interviews with privacy-conscious individuals to validate the specific pain point that the 'dual network mode' solves, rather than just 'general privacy'.
  2. Explore niche audiences who *desperately* need both fast and anonymous communication modes within a single app (e.g., journalists, activists, specific businesses) and if they would pay.
  3. Investigate potential monetization models that don't rely on per-user subscription for core messaging, perhaps pro features for specific use cases or enterprise licenses.
  4. Focus on a single, compelling use case or feature to overcome the network effect rather than a broad messaging app.
  5. Validate if the technical trade-offs (Tor latency, eventual consistency) are acceptable for the target niche.

Questions about this idea?

FlyBot reads the scoring and gives you a second opinion on “A P2P messenger with dual network modes (Fast and Tor)”.

Open FlyBot